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.

AWR1642: Bootloader UART break questions.

Part Number: AWR1642
Other Parts Discussed in Thread: UNIFLASH

Hi,

We recently made a research in Awr1642 Bootloader Flow:http://www.ti.com/lit/an/swra551/swra551.pdf.

Paragraph 4.4 shows the flash programming sequence. 

Because we want use a secondary boot to handle several Images in flash, and will use CAN/CANFD as an image data transfer port.

So if this "Bootup" is part of Bootloader and "Bootup" is coded "wait for UART break", i had to ask for the source codes of Bootoader and change them myself?

Thanks

BrianZ  

  • Hello Brian,

    In case of the secondary bootloader (SBL) where it listens to image data over CAN/CANFD,  this task is independent of the primary bootloader.

    - Primary bootloader reads sFlash content which is SBL in your case and put it respective RAM and lets it execute.

    - Now SBL needs to be in the loop to listen to app-image data over CAN/CANFD. As it gets any data it needs to validate it and write it to sFlash (pre-defined sector).

    - Developer needs to define section on sFlash for a different type of images and define intelligence to verify receive data in case of any loss/mismatch. This intelligence can be done by following some specific protocol b/w device and CAN download tool.

    Here is the flow diagram to endorse my above statements-

    Next version of mmWave SDK will have an application to demonstrate SBL functionality, stay tuned for that.

    Regards,

    Jitendra

  • Hi Jitendra,

    Thank you for your reply. It really helps a lot.

    One more question :

    Is it UART port method (by UniFlash) that the secondary bootloader is programmed to Sflash?

    If so, do i have to change the UART method to CAN/CANFD method in programming secondary bootloader to Sflash?

    Thanks,
    Brian