• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 82 subscribers
  • Views 386 views
  • Users 0 members are here
Support feedback
Options
Options

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.

TMS320F2800137: Issue with flash programming using serial boot (SCI_Boot) when booting in SCI boot mode from software itself (not using boot pins)

CastNX Pvt Ltd
Prodigy 40 points
Part Number: TMS320F2800137
Other Parts Discussed in Thread: C2000WARE

While programming F2800137 using serial flash programmer utility, it works fine when we boot (SCI Boot Mode) the device using boot pins ( GPIO32 and GPIO24)

We are able to program both the files (kernel and the application) properly. execution of the application file is also fine.

But when we boot the device from software itself, i.e. using SCI_Boot(0x01); we face some issue:

1. The device go to sci boot mode successfully

2. Programming of kernel file is also fine and the kernel boots properly.

3. While programming the application file we got following messages 

This seems to be some DCSM related issue, as when we change the the CMD file to use the flash up to sector 31 it works fine but when we use sector 32 and above we get the above message.

when we use sector 32 (address 0x088000) we get ERROR Address: 0x884a0

when we use sector 64 (address 0x090000) we get ERROR Address: 0x904a0

when we use sector 96 (address 0x098000) we get ERROR Address: 0x984a0

I am attaching the files as below for your reference

1. Kernel file used

7536.flash_kernel_ex3_sci_flash_kernel.txt

2. Application txt file (converter using .hex2000 utility)

LED_500.txt

3. cmd file used in the project

1351.cmd.txt

  • 0
    TI__Guru* 77510 points

    When you mention using SCI Boot via SW, are you calling directly into that function in the ROM, or have you used that content to replicate your own SCI Boot in RAM/Flash?  Just want to be sure of the source code here.  The Boot ROM has some initialization it does prior to jumping to the boot mode specified by the pins, I suspect the delta here between that code and when you call into the boot is creating some issues. Let me know how you are implementing in SW and we can look into this further.

    Best,

    Matthew

  • 0 in reply to MatthewPate
    Prodigy 40 points
    MatthewPate said:
    are you calling directly into that function in the ROM

    I am calling directly into the ROM, the SCI_Boot function is located at 0x003fe0c4 in ROM of 2800137, I am branching directly to this address, Below is the steps I am following for this:

    void Enter_Boot_Mode(void){
    int delay_loop=0;
    DINT;
    IER = 0x0000; // Interrupt should be disable before calling the boot loader
    IFR = 0x0000;

    for(delay_loop=0;delay_loop<15;delay_loop++){
    ms(200);
    }

    DisableDog();


    EALLOW;

    ((void (*)())0x003fe0c4)(0x01);    // Boot loader called here

    asm(" LB 0x000000");
    EDIS;
    }

    Few more observations:

    1. After calling SCI_boot function as above, and trying to use "C2prog" instead of "serial_flash_programer" (utility provided with C2000ware) then it works fine

    2. Calling the SCI_boot function at first in main, without doing anything (no clock configuration, no peripheral configuration, nothing) then the programming works fine even with "serial_flash_programer".

    I suspect it is something to do with the initialization to be done before calling the SCI_boot function.

    Can you please help me provide some documents or material to read and find out what kind of initialization, stack pointer re-init or any other thing to be done before calling SCI_boot function