Epson S5U1C17001C, Manual

Page: 609 / 742

10-158
EPSOn
S5U1C17001C ManUal
(C COMPilEr PaCkagE fOr S1C17 faMily) (Ver. 1.5.0)
10 DEBUggEr
10.8.3.4 restrictions
The following shows the restrictions for measurements.
・
Valid profiles cannot be obtained if the function name labels in assembler sources do not also have stab
information using “.type.”
Example) .type sub, @function
This is also required when creating a library.
* The above is not necessary for C sources because the C compiler automatically outputs “.type” statements.
・
Valid profiles cannot be obtained if the program counter (% PC) is forcibly changed using “set $pc = XXX” or
similar means while the program is in break mode.
・
Valid profiles cannot be obtained if a measurement is interrupted
̶
for example, executing the “
c17 pro-
filemd 0
” command while the program is in break mode, executing the program again, and then executing the
program once more after executing the “
c17 profilemd 1
” command in break mode.
・
The measurement range can be from RESET (boot address) to the address at which a break occurs.
It is not possible to perform measurements in a range from a specific address to the address at which a break
occurs. However, measurement will continue until the subsequent break even if “Go” is executed again without
changing “%PC” after a break.
・
A profile cannot be obtained from a program that transfers a program or function dynamically from the ROM
area to the RAM area and executes it (e.g., programs in which “.text” sessions are linked as LMA
≠
VMA).
・
A profile cannot be obtained if a program has more than 10,000 functions and made more than 10,000 calls.
・
A profile cannot be obtained if a program made more than 10,000 deep calls as viewed from RESET (boot
address).
・
Static functions without debug information (without assembler
−
gstabs option or compiler
−
gstabs option)
cannot be displayed in the form of “ function name + @ + filename ”; the filename section will not be displayed.