• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 32 subscribers
  • Views 156 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: AWR2243 firmware download rate

Srinivasan B
Prodigy 155 points
Part Number: AWR2243

Hi ,
We are using AWR2243 board  and connecting it to an external host. The DFP porting to the external host is done by following the TI dfp porting guidelines. The meta image v2.2.0.3 is used, which is of size 334656 bytes.

The firmware download is taking more time than expected in external host. To cross verify the timing this we checked the same AWR2243 board with the TDA2x board. We observed TDA board and the firmware download is happening significantly at a faster rate. 

The timing for the firmware download  with two boards are as follows,

With TDA board: 2.95s

With external host: 3 minutes and 20 secs.

We would like to know the reason why it is faster in TDA board and implement the same in external host. Please let us know how to resolve this issue.

Thanks and regards,

Srinivasan

  • 0
    TI__Guru*** 138349 points

    Hi,

    I checked the dfp release

    The size is under 8KB

    C:\ti\mmwave_dfp_02_02_03_01\firmware\xwr22xx_metaImage.bin

    Where did you see 334656 bytes?

    Thank you

    Cesar

  • 0 in reply to Cesar
    Prodigy 155 points

    Hi Cesar,

    Thanks for the reply. I have mentioned  that  we are using  DFP version 2.2.0.3 not 2.2.3.1.

    If you see the meta image file xwr22xx_metaImage.h from DFP 2.2.0.3,   which is 1163 KB.

    Thanks and regards,

    Srinivasan

  • 0 in reply to Srinivasan B
    TI__Guru*** 138349 points

    Hi,

    Thank you for this additional information.

    I assume that you are using an ES1.0 silicon which uses a RAM firmware.

    This explains the reason why the size is much larger.

    ES1.1 silicon uses a ROM firmware with patch only in RAM. This is the reason why the size is much smaller.

    Now, that being said I think there is some issues in the way the firmware load through SPI was implemented in the host.

    Usually SPI should run at a rate of several MBps. So the firmware load should definitely take at the most a few seconds

    Please review the host SPI implementation

    thank you

    Cesar