How much memory is my program using, How do i determine the size of my actual hex code, Warning and error messages – Zilog EZ80F916 User Manual
Page 306
UM014423-0607
Using the Linker/Locator
ZiLOG Developer Studio II
eZ80Acclaim!
®
User Manual
286
17. From the Build menu, select Rebuild All to build the project.
18. From the Debug menu, select Connect to Target to connect to the target.
19. Continue debugging as usual.
NOTE: For the solution given here, it is assumed that the source and project files are available to
recreate the hex image with ZDS II and that the target can be reprogrammed. If the source
and project files are not available to recreate the hex image with ZDS II or the target cannot
be reprogrammed, a new project can be created for debugging at the disassembly level. In
that case, create a new project for the target that contains a blank source file.
How much memory is my program using?
Unless the Generate Map File check box is deselected in the Project Settings dialog box
(Output page), the linker creates a link map file each time it is run. The link map file name
is the same as your executable file with the
.map
extension and resides in the same direc-
tory as your project file. The link map has a wealth of information about the memory
requirements of your program. Views of memory usage from the space, segment, and
module perspective are given as are the names and locations of all public symbols. See
“Generate Map File” on page 93 and “MAP” on page 253.
How do I determine the size of my actual hex code?
Refer to the map file. Unless the Generate Map File check box is deselected in the Project
Settings dialog box (“Generate Map File” on page 93), the linker creates a link map file
each time it is run. The link map file name is the same as your executable file with the
.map
extension and resides in the same directory as your project file.
WARNING AND ERROR MESSAGES
NOTE: If you see an internal error message, please report it to Technical Support at
http://support.zilog.com
. ZiLOG staff will use the information to diagnose
or log the problem.
This section covers warning and error messages for the linker/locator.
700 Absolute segment "<name>" is not on a MAU boundary.
The named segment is not aligned on a Minimum Addressable Unit boundary.
Padding or a correctly aligned absolute location must be supplied.
701 <address range error message>.
A group, section, or address space is larger than is specified maximum length.
Do not establish a target connection using the Reset or Go commands/buttons
and do not invoke the Download Code command/button. Doing so might
corrupt the ROM/Flash device. The Reset and Go commands/buttons can be
used in all other cases.