This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Troubles with the Flash (TMS570)

Hi TI Team,

For make it easier...

Tools

Hercules dev kit TMS570MCU

IAR 6.5

Segger J-LINK

Application

FreeRTOS

lwIP

Description of the problem:

My code goes to prefetch entry

When It happens

While trying to allocate a buffer, tries to enter in a critical task - > disable interrupt (and then crashes)

Clues

Seems to be a problem with the Bank 1 because complain after 0x0017FFF and ahead.

J-Link complains about unexpected value after erasing PC = 0x0001830C

This problem also appears after use a breakpoint

When I debug step by step pops a window "Erasing sector"

This issue only appears while being a thread, if its not a thread works fine.

FreeRTOS with small code like the blinkLED works fine.

Syslink.cmd remains original

When is working in the BANK1 the device can't abort the debug session or stop the core.

Everything configured following the Texas Instruments IAR integration steps

No using FEE or MPU

Definitions

#define configTOTAL_HEAP_SIZE  ( ( size_t ) 1024*8 )

#define conifgTCPIP_TASK_STACK_SIZE   8* configMINIMAL_STACK_SIZE //  940

#define configMINIMAL_STACK_SIZE  ( ( unsigned portSHORT ) 128 )

Screens:

Thanks for the help

  • Victor,

    Just a clue, when debugging from flash, breakpoint are using specific resources in the CPU (Hardware Break-Point)
    6 Hardware break point are available.
    J-Link allows to use "Unlimited" hardware break-point. This is done as following:
    Once the CPU Hardware Break-Point are all used, J-Link will use instruction replacement to use Software Break-Point. That means, J-Link will erase the Flash Sector where a software Break-point has to be setup and will reprogram the sector.
    This could explain the message "Erasing sector"
    What I will suggest to debug your problem is to be sure that you don't use more than 6 break-point and see how your debug is going.

    For further debug, we may need your project in order to reproduce this issue in our environment.

    Please have a try and let me know.