Qorivva MPC5xxx/SPC5xx Debugger and NEXUS Trace
66
©1989-2021 Lauterbach GmbH
information from
can help to compare the current VLE setup in the MMU with
the information from the debug symbols. If the information in sYmbol.List.ATTRibute is wrong,
please check your linker configuration.
•
If the debugger lists VLE/FLE instructions as expected for the address ranges shown in
but there are still sporadic errors in the disassembly, then the used linker
is not properly configured to link VLE code. In this case it was observed that all debug symbols
were aligned to 4 byte boundaries, while the actual code was aligned at 2 byte boundaries.
Check linker version and linker configuration.
•
Early complier versions supporting VLE often had buggy VLE debug symbols. Check if a
compiler update is available.
As a workaround, it is also possible to override the information loaded from the debug symbols using
; Syntax:
; sYmbol.NEW.ATTRibute <FLE|VLE> <start-address>
; sYmbol.NEW.ATTRibute <FLE|VLE> <range>
; Example: override
Data.LOAD auto project.elf
sYmbol.NEW.ATTRibute FLE 0x00000000--0x0003ffff
sYmbol.NEW.ATTRibute VLE 0x00040000--0x00ffffff
;add new attribute FLE for BAM, which is not covered by debug symbols
sYmbol.NEW.ATTRibute FLE 0xFFFFF000
