ΣSigmaStudio Ask AI Русский Log in

BlackFin 537 fails in debug but runs when flashed

Processors & DSP MrChampagne Jun 13, 2016 00:00 1 replies Original on forum ↗
Subscribe
MrChampagne Question
Jun 13, 2016 00:00

At a high level, the project compiles (with 1 warning, see below) and runs successfully on TinyBoard CM-BF537 when flashed, BUT won't allow trace in debug mode.

Details=========================

After a build, Linker provides a warning:

Li2131: .\*project*.ldf: 501 Input sections of incompatible init qualifier detected in the output section 'sdram_no_init'. For more details see linker_log.xml.

Of course, Linker_log.xml only repeats the warning without further details.

The project builds successfully then loads completely. The project runs into an infinite loop (most likely an exception handler, which? ) starting at address 0xEF0000E0 and ending at a JMP at location 0xEF000110.

Note in the Console window states core fault dectected at address 0xFFA00676. Attempting to reset processor.

The instruction at this address is SSYNC inside of 'nextcheck' function.

End Details===============

This behavior is suspicious bc when I use the Flash Tool. The code loads successfully and runs completely into user code. This is evident from status LED's lighting on the custom board.

Any ideas as to the cause of this behavior?

blackfin bf537

exception

tinyboard cm-bf537

debugger

ADIApproved Reply
Oct 7, 2016 00:00

Hi,

For the linker warning Li2131 please refer the below given help path:
CrossCore® Embedded Studio 2.3.0 > Blackfin® Development Tools Documentation > Linker and Utilities Manual > Linker and Archiver Messages > Linker Messages > Warnings>li2131

To locate the specific help topic is by searching on the keyword 'li2131' in VisualDSP++ Help

If the issue that you are encountering is happening on load, disable "Run to main after load" via 'Settings: Preferences: General', and load the DXE. It should load OK, and you can step through the startup code until the exception occurred. Typically, if there is an exception during the startup code it is an access to SDRAM that has not been correctly initialized. If that appears to be the case, please see the following FAQ:
https://ez.analog.com/docs/DOC-1783

Best Regards,

Kader