• State Resolved
  • Locked Locked
  • Replies 9 replies
  • Subscribers 31 subscribers
  • Views 886 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

AWR2243: How to write/check firmware into external flash memory via AWR2243.

Tomotaroh Kohro
Genius 11615 points
Part Number: AWR2243
Other Parts Discussed in Thread: AWR1243, , UNIFLASH

Hello team.

Customer tried to boot AWR2243BOOST with firmware that is stored in external flash memory.

But it does not work yet.

 

Customer checked QSPI I/F that is connected with external flash memory.

But QSPI I/F is accessed about a few mSec. It seems to MMWL_SwapResetAndPowerOn cannot be completed.

(In case of AWR1243, about 70mSec is used for accessing QSPI I/F.)

 

Customer thinks that firmware may not be written in external flash memory correctly

They checked the below link:

e2e.ti.com/.../927832

 

So, AWR2243 cannot write firmware in external flash memory.

Then they selected “AWR1243” instead of “AWR2243”.

However, they cannot confirm firmware is written correctly.

 

1. Please share with us if you have document that describes how to write firmware in external flash memory via AWR2243.

2. Please tell us how to check if firmware is written correctly.

 

Br

KORO

  • 0
    TI__Guru 68160 points

    Hello Koro,

    AWR2243 supports a feature where firmware can be flashed to sFlash via SPI interface. In another option Uniflash tool can be used to flash the firmware but over UART interface.

    In DFP we provide an example to showcase how to load firmware to sflash by sending firmware data over SPI.

    C:\ti\mmwave_dfp_02_01_05_03\ti\example\mmWaveLink_SFlash_FW_Example

    In this application it first load the firmware over SPI to sFlash, then reset the device so device can load the firmware from sFlash to RAM and then Host configures the device.

    So now onward Host doesn't need to load the firmware over SPI every time, as device is booting firmware over sFLASH.

    Please go though this application and suggest customer to refer this for their implementation.

     

    Regards,

    Jitendra

  • 0 in reply to Jitendra Gupta
    TI__Genius 11615 points

    Hello Jitendra-san

    Thanks a lot !!!

    I am informing your suggestion to customer.

    Please wait for my next update.

    Tomorrow, I will discuss with customer.

    Br

    KORO

  • 0 in reply to Tomotaroh Kohro
    TI__Guru 68160 points

    Hello KORO,

    Meanwhile, I'll close this thread.

    You can reply back on this to reopen.

     

    Regards,

    Jitendra

  • 0 in reply to Jitendra Gupta
    TI__Genius 11615 points

    Hello Jitendra-san

    Thanks a lot.

    O.K.

    This ticket can be closed.

    Br

    KORO

  • 0 in reply to Jitendra Gupta
    TI__Genius 11615 points

    Hello Jitendra-san

    Thanks a lot for your support.

    Customer understand our suggestion about SFlash method.

    But customer mentioned that their using Flash Memory size is about 128K then SFlash binary cannot be stored.

    Then again they asked us how they confirm if DFP image could be written into Flash memory correctly.

    At the time of AWR1243, it took about 70mSec. I think this is because the Firmware is loaded.
    The current behavior is to access QSPI at boot time, but the access ends immediately.

    --QSPI configuration problem?
    --Does not detect Flash Memory?
    --Firmware is not stored correctly ?
    --Is there a problem with the DPF version?

    Br

    KORO

  • 0 in reply to Tomotaroh Kohro
    TI__Guru 68160 points

    Hello KORO,

    I don't fully understand customer concern here.

    Are they not able to flash the firmware to AWR2243 device??

    In AWR2243 ES1.0 firmware size is >300KB which will sit on their 128KB sFlash, whereas in AWR2243 ES2.0 this firmware will be just a patch content and size is less than 10KB. SO it can fit on sFlash.

     

    Regards,

    Jitendra

  • 0 in reply to Jitendra Gupta
    TI__Genius 11615 points

    Hello Jitendra-san.

    Thanks a lot for your quick reply.

    Customer is now using AWR2243P ES1.0. Therefore, they need to store Firmware in Flash Memory.

    They are migrating their system to AWR2243P from AWR1243P.

    Currently, they are having a hard time starting AWR2243P.

    They still cannot load and start the firmware from the external Flash Memory lick AWR1243P system.

    BTW, The board uses the same board and mounts the AWR2243P instead of the AWR1243P.

    Br

    KORO

  • 0 in reply to Tomotaroh Kohro
    TI__Guru 68160 points

    Hello KORO,

    As I mentioned for AWR2243P ES1.0 firmware size >300KB as it contains full ROM image instead of patch, whereas AWR2243P ES1.1 it will be just patch and size <20KB.

    Now as you mentioned that customer is limited by sFlash size (128K) then they need to download the firmware over SPI. Reference example is provided in the mmwave DFP.

    Boot sequence for AWR2243P ES1.0 is slightly different compare to AWR1243P which is explained in the DFP Example of v2.1.5.3.

    Could you check with customer if they have tried the correct sequence as mentioned in DFP example

    Even DFP user guide document mmwave_dfp_user_guide.pdf (section 8.1) shows the flow diagram as well for AWR2243P boot up.

    Regards,

    Jitendra

  • 0 in reply to Jitendra Gupta
    TI__Genius 11615 points

    Hello Jitendra-san.

    Thanks a lot.

    I will inform your advise.

    Br

    KORO