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.

C2000 not running after SCI boot-up setup..

Hi all,
I was able to flash my 320F28335 when it was set to "Jump to Flash" option.

I am trying SCI bootloader option ( by changing GPIO to SCI-A boot option). After this change my processor does not boot up.

I downloaded my code using JTAG interface and it only works well until it has power. As soon as it restarts, it is unresponsive. ( Whereas it was was working well when I had "Jump to Flash" option. )

So far as i understand, SCI bootlaoder is built in to the processor and if dosen't get any serial data (0x08AA) it will jump to "FLASH_ENTRY_POINT" where it calls my Watchdog disable routine and runs the code.

I also tried loading my code with bootlader which successfully erases Flash and programs it but after power cycle same response, no any activity.


Can someone please help me with this.

Regards

  • Hi,

    As far as I know, the Bootloader will not jump to FLASH if it doesn't get anything from the SPI port. So you will need to send at least wrong data in order to make the processor boot.

    Best regards

    Andreas

  • Hi Andreas,

    Thanks for the reply but during normal operation mode, after reset shouldn't processor just wait for a boot sequence for certain time, and jump to user application if boot sequence is not present. 

    In my case this is not happening. I can connect to processor if i send boot ID. But it is not jumping to FLASH_ENTRY_POINT after that or after reset.

    Do we need to tweak some variables if we use bootloader option.

     

    Regards

     

  • Hi,

    Sandesh Joshi said:
    Thanks for the reply but during normal operation mode, after reset shouldn't processor just wait for a boot sequence for certain time, and jump to user application if boot sequence is not present. 

    If I understand the BOOT ROM Reference Guide correctly this is not true. TI Bootloader will sit and wait until it receives data via the SPI port. If the data is valid (0x08AA) it will start with SPI Bootload, if it is wrong, it will continue with a normal Boot by jumping to the FLASH ENTRY POINT. See the code listed in the bootrom guide; the method

    Uint16 SPIA_Transmit(Uint16 cmdData) 

     

     

    on page 81 shows that it will wait for an answer from SPI before continuing the bootloader process

    Best Regards

    Andreas

  • Andreas,

    I am using SCI ( serial port) and not SPI . And like you said i checked bootrom guide. According to this @ page 83 it says

     

    Uint32 SCI_Boot()
    {
    Uint32 EntryAddr;
    // Assign GetWordData to the SCI-A version of the
    // function. GetWordData is a pointer to a function.
    GetWordData = SCIA_GetWordData;
    SCIA_Init();
    SCIA_AutobaudLock();
    // If the KeyValue was invalid, abort the load
    // and return the flash entry point.
    if (SCIA_GetWordData() != 0x08AA) return FLASH_ENTRY_POINT;

     

    So far as i can understand, it tries to lock baud rate and if word read is not 0x08AA it returns FLASH_ENTRY_POINT.

    My question is, once that happens, should my native code run.  ( which was working fine when i had boot gpio as " Jump to Flash" option.) This is not happening in my case.

    Regards

  • OK, sorry I missread your first post. With SCI it still is the same bad story. See page 85 of the reference guide. The bootloader waits for data received by SCI and doesn't continue if no data comes...

    // Fetch the LSB and verify back to the host

    while(SciaRegs.SCIRXST.bit.RXRDY != 1) { }

    Best regards

    Andreas

  • Andreas, I think you are right. I does stay in that loop. Worst, even watchdog is disabled.

    Does that mean, even time processor boots, user has to send serial data to run the unit. ( this doesn't sound right).

    I also tried sending dummy data at startup. if I send 'A' it replies back but if i send anyting else it just stays quiet. I even doesn't jump to my program.

    Don;t know how can i solve this.....

    :(

     

    Thanks...

  • Among others this is the reason why I wrote my own bootloader...

    Best regards

    Andreas

  • Thanks Andreas for your time...

    Can someone please response to this problem.....

     

    Thanks in advance...

  • Desh,

    If you want the SCI to timeout after a particular time, then Andreas is correct - a custom loader is the way to go.  You can, for example, put a small loader in OTP that checks for data on the SCI.  If it doesn't see it, then it boots to flash.  If it does see it, then it calls into the boot ROM routines.  Then your boot would always be to the OTP routine which would do the check.

    Regards,

    Lori