Zilog EZ80F916 User Manual
Zilog developer studio ii— ez80acclaim
Advertising
This manual is related to the following products:
Table of contents
Document Outline
- ZiLOG Developer Studio II- eZ80Acclaim!®
- Revision History
- Table of Contents
- Introduction
- Getting Started
- Using the Integrated Development Environment
- Using the ANSI C-Compiler
- Language Extensions
- Type Sizes
- Predefined Macros
- Calling Conventions
- Calling Assembly Functions from C
- Calling C Functions from Assembly
- Command Line Options
- Run-Time Library
- Pseudoinstruction Macros Generated by the C-Compiler
- Startup Files
- Segment Naming
- Linker Command Files for C Programs
- ANSI Standard Compliance
- Locating Variables at Specific Addresses: Older Method
- Warning and Error Messages
- Using the Macro Assembler
- Using the Linker/Locator
- Using the Debugger
- ZiLOG Standard Library Notes and Tips
- What is ZSL?
- Which on-chip peripherals are supported?
- Where can I find the header files related to ZiLOG Standard Libraries?
- What is the zsldevinit.asm file?
- What initializations are performed in the zsldevinit.asm file?
- What calls the open_periphdevice() function?
- When I use ZiLOG Standard Libraries in my application and build from the command line, why do I see unresolved errors?
- I do not use the standard boot-up module, but I have manually included ZiLOG Standard Libraries. When I link my code with the library, why do I get an unresolved symbols error?
- Where can I get the ZSL source files?
- I need to change the ZSL source code. How can I generate a new library with these changes included?
- How can I use standard I/O calls like printf() and getch()?
- What is the difference between the Interrupt mode and the Poll mode in the UARTs?
- What are the default settings for the UART device?
- How can I change the default UART settings for my application?
- I am using the UART in the interrupt mode. Why do I seem to lose some of the data when I try to print or try to receive a large amount of data?
- When I call open_UARTx() function by configuring it in INTERRUPT mode, the control never comes back to my program and my program behaves indifferently. Why is this?
- Where can I find sample applications that demonstrate the use of ZSL?
- I have used init_uart() and other functions provided in the RTL. Do I need to change my source code because of ZSL?
- C Standard Library
- Standard Header Files
- Standard Functions
- abs
- acos
- asin
- assert
- atan
- atan2
- atof
- atoi
- atol
- bsearch
- calloc
- ceil
- cos
- cosh
- div
- exp
- fabs
- floor
- fmod
- free
- frexp
- getchar
- gets
- isalnum
- isalpha
- iscntrl
- isdigit
- isgraph
- islower
- isprint
- ispunct
- isspace
- isupper
- isxdigit
- labs
- ldexp
- ldiv
- log
- log10
- longjmp
- malloc
- memchr
- memcmp
- memcpy
- memmove
- memset
- modf
- pow
- printf
- putchar
- puts
- qsort
- rand
- realloc
- scanf
- setjmp
- sin
- sinh
- sprintf
- sqrt
- srand
- sscanf
- strcat
- strchr
- strcmp
- strcpy
- strcspn
- strlen
- strncat
- strncmp
- strncpy
- strpbrk
- strrchr
- strspn
- strstr
- strtod
- strtok
- strtol
- tan
- tanh
- tolower
- toupper
- va_arg
- va_end
- va_start
- vprintf
- vsprintf
- Running ZDS II from the Command Line
- Using the Command Processor
- Sample Command Script File
- Supported Script File Commands
- add file
- batch
- bp
- build
- cancel all
- cancel bp
- cd
- checksum
- debugtool copy
- debugtool create
- debugtool get
- debugtool help
- debugtool list
- debugtool save
- debugtool set
- debugtool setup
- defines
- delete config
- examine (?) for Expressions
- examine (?) for Variables
- exit
- fillmem
- go
- list bp
- loadmem
- log
- makfile or makefile
- new project
- open project
- option
- pwd
- quit
- rebuild
- reset
- savemem
- set config
- step
- stepin
- stepout
- stop
- target copy
- target create
- target get
- target help
- target list
- target options
- target save
- target set
- target setup
- wait
- wait bp
- Running the Flash Loader from the Command Processor
- Compatibility Issues
- Asssembler Compatibility Issues
- Compiler Compatibility Issues
- #pragma alias
- #pragma noalias
- #pragma cpu <cpu name>
- #pragma globalcopy
- #pragma noglobalcopy
- #pragma globalcse
- #pragma noglobalcse
- #pragma globaldeadvar
- #pragma noglobaldeadvar
- #pragma globalfold
- #pragma noglobalfold
- #pragma intrinsics: <state>
- #pragma nointrinsics
- #pragma nobss
- #pragma jumpopt
- #pragma nojumpopt
- #pragma localcopy
- #pragma nolocalcopy
- #pragma localcse
- #pragma nolocalcse
- #pragma localfold
- #pragma nolocalfold
- #pragma localopt
- #pragma nolocalopt
- #pragma noopt
- #pragma optlink
- #pragma nooptlink
- #pragma optsize
- #pragma optspeed
- #pragma peephole
- #pragma nopeephole
- #pragma promote
- #pragma nopromote
- #pragma sdiopt
- #pragma nosdiopt
- #pragma stkck
- #pragma nostkck
- #pragma strict
- #pragma nostrict
- Index