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.

TMS570LS3137: ETHERNET Bootloader

Part Number: TMS570LS3137


Tool/software:

HI:
      
   
I'm currently debugging the TMS570LS3137 bootloader that uses Ethernet to load programs (from the TI SafetyMCU_Ethernet_Bootloader.zip package). Here's my situation:

  1. When loading the blink executable provided by TI (SafetyMCU_enet_bootloader\App Example\TMS570_Blinky.bin), the bootloader jumps to the application successfully, and the LED on the development board blinks normally.
  2. When I compile the LED_Blink_TMS570LS3137.zip project, the compiled application also starts correctly with the LED blinking as expected.
  3. However, after modifying the sys_link.cmd file in the LED_Blink_TMS570LS3137.zip project as follows and trying to load the modified application via the bootloader, the LED fails to blink.
    MEMORY
    {
        VECTORS (X) : origin=0x00020000 length=0x00000020
        FLASH0 (RX) : origin=0x00020020 length=0x0015FFE0
        FLASH1 (RX) : origin=0x00180000 length=0x00180000
        STACKS (RW) : origin=0x08000000 length=0x00001500
        RAM (RW) : origin=0x08001500 length=0x0003EB00

    }

        Question: 1  Why does the modified blink application fail to start correctly when loaded via the bootloader?  
                          2  
Could you provide the project corresponding to TMS570_Blinky.bin and compare the differences between this project and the LED_Blink_TMS570LS3137.zip project?

                          3 When loading an existing executable via a bootloader, what aspects should be paid attention to prevent the existing program from failing to start? 

0434.LED_Blink_TMS570LS3137.zip

SafetyMCU_Ethernet_Bootloader.zip

thanks