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.

SCI_Boot not working as stand-alone

Part Number: SCI Bootloader works with JTAG but not as standalone when loaded - F28035

I've written a serial program in VS2017 that uploads the SCI_Bootloader (so I can write a program to flash) and when I load the SCI_Bootloader to the F28035 with the JTAG, everything works as expected. It reenters the SCI_Bootloader as seen by a quick blink of an LED prior to entering the main(), goes thru some setup and then it sits and waits for the flash file to be uploaded. (I removed the autobaud function and reprogrammed it to operate at 9600 baud. This works as I see all my bytes echoed back.) I can then use the VS2017 tool to upload the flash firmware thru the SCI port and operate as expected.

So when I remove the JTAG and Gnd GPIO37 and pull up GPIO34 to put the F28035 into SCI boot mode, I can apparently upload the SCI_Bootloader flash utility but when it is complete, I do not see the quick flash of the LEDs I expect to prior to the entry of main() and therefore my attempt to upload the flash file fails. It's as if the 'ENTRY POINT SYMBOL: "_c_int00"  address: 000081c3' is not being entered

I pretty much follow the Figure 2-12. Overview of SCI_Boot Function in SPRUI10–December 2018 except for the autobaud. I have readjusted BRR for 9600 baud and it works fine.

I have tried to drop the map file into this ticket but it keeps disappearing. If any of that data is desired, I can copy it in.

  • Hi Jeffrey,

    Our expert on this is out of office today. Please expect a reply by tomorrow

    Regards,

    Peter

  • Jeffrey,

    take a look at this document and associated software examples and see if they help you debug the issue:

    www.ti.com/lit/SPRABV4

    Regards

    Lori

  • Thanks. I didn't realize the ROM boot loader had the auto baud. That is now working but still not seeing my LED turn on to indicate the new SCI flash bootloader is running. Will keep marking my progress. Again this is with the SCI Flash bootloader as a stand-alone file and no jtag connected.

  • And nothing else in that document helps. Here is some additional information:

    Linker Cmd File: 28035_RAM_lnk.cmd

    Hex utility flags: --diag_wrap=off --boot --sci8 --ascii

    Bin file beginning ignoring the STX: 

    AA 08 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 C3 81 02 00
    00 00 00 00 40 00 FB 82

    Bin file ending ignoring the ETX:

    1E 00 00 00 FE 00 FF FF 08 94 00 00 01 00 FE FF 0A 94 00 00 00 00 00 00
    FE FF 0C 94 00 00 00 00 00 00 FE FF 0E 94 00 00 FA 82 00 00 FE FF 10 94
    00 00 FA 82 00 00 FF FF 14 94 00 00 00 00 00 00 00 00
    00 00

    Data is written as bytes and all echoed data bytes from the F28035 are verified so there is no data corruption. This also proves its happy with the AA08 or else there would be no echoed data. It also proves autobaud lock and that we are in SCI boot mode based on GPIO pins.

    Any other thoughts please?

  • So we found an an issue with the auto baud checker - See if you can see the problem

    void establishAutoBaud() { } <== Burn't by these extra brackets

    {

      do{

         sp.write("A");

         sp.read(rdBuf, 0 , 1);

        } while (rdBuf[0] != 'A');

    }

    All the above was in a timer function. 

    Feel free to close the ticket. The issue was the auto baud missing in the VS2017 app.

  • Great!  Thank you for the feedback.