• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 403 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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: Load firmware to AWR2243 through SPI interface and report error

Gary Lu
Intellectual 1660 points
Part Number: AWR2243

Hello,

I use STM32 as the MCU here, and configure AWR2243 through the SPI interface (set to single-chip mode), and the SPI communication function is normal (the sop of AWR2243 is set to SPI mode). According to the API documentation, related information can be read and written through SPI.

My workflow is as follows:

1. Control the AWR2243 reset through the reset pin, wait for the DEV_ASYNC_EVENT event, and confirm DEV MSS POWERUP DONE

2. Download the meta image file via SPI, file path: ti\mmwave_dfp_02_02_03_01\firmware\xwr22xx_metaImage.bin (whether to download this file, if not, which one should be downloaded)

3. Wait for the DEV_ASYNC_EVENT event after the file is downloaded, and confirm that AE_MSS_BOOTERRSTATE (0x5005) is generated, but AE_MSS_CPUFAULT (0x5002) is generated, and the error code is displayed as follows:

ba dc cd ab 36 a0 32 00 0c 00 00 00 01 00 8a 5f 02 50 24 00 05 00 00 00 80 00 00 fe 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0 0 00 ff ff ff ff ff ff 00 00 f4 b5

According to the manual, only 05 00 can be used to parse the information as MSS Processor Register read-back errors, and the information of other bits cannot be parsed according to the manual

May I ask what is the reason for this error? How should we solve it?

Note: This is the first packet of data I issued the xwr22xx_metaImage.bin file

34 12 21 43 05 81 fc 00 00 04 22 00 01 00 db 79 80 40 ec 00 00 00 00 00 04 1f 00 00 4d 53 54 52 02 00 00 00 37 00 00 00 7e bf a8 bd 61 24 53 25 00 1f 00 00 01 00 00 00 00 00 51 35 80 00 00 00 be e4 07 23 21 a0 d9 44 f8 07 00 00 00 00 00 00 00 00 00 00 01 00 00 00 00 00 51 b5 80 08 00 00 c2 7e 70 b0 d3 c8 df de 60 16 00 00 00 00 00 00 00 00 00 00 04 00 00 00 4d 45 4e 44 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 52 50 52 43 31 05 20 00 00 00 00 00 04 00 00 00 01 00 00 00 00 00 00 00 00 00 20 00 00 00 00 00 24 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e7 10 cf d0 ed ad 10 d0 02 02 01 07 14 03 11 00 00 00 00 00 31 05 20 00 02 02 02 00 14 07 1d 00 00 00 00 00 00 00 00 00 d0 00 20 00 00 00 00 00 fe 11 bf 36

  • 0
    TI__Mastermind 32725 points

    Hi,

    Can you use the file xwr22xx_metaImage.h file to download through SPI and let us know your observations. The DFP firmware is in this file.

    Thanks,

    Pradipta.

  • 0 in reply to Pradipta Bandyopadhyay
    TI__Intellectual 1660 points

    Hello,

    Hello, I used the xwr22xx_metaImage.h file to download, and no CPU Fault error was reported. I compared the .bin file and found that the .bin file has 4 more bytes at the end. Are these 4 bytes the check code? In addition, I did not receive the MSS_BOOTERRSTATUS event in the red box on the left after downloading. Our AWR2243 is connected to a piece of Flash through QSPI. Is it because of this that the MSS_BOOTERRSTATUS event is not generated? How should I tell if my firmware loading was successful?

    Regards，

    Gary

  • 0 in reply to Gary Lu
    TI__Mastermind 32725 points

    Hi,

    Can you try running the DFP examples provided in the SDK with your test setup and let us know your observations. 

    Gary Lu said:
    I did not receive the MSS_BOOTERRSTATUS event in the red box on the left after downloading. Our AWR2243 is connected to a piece of Flash through QSPI. Is it because of this that the MSS_BOOTERRSTATUS event is not generated?

    You should receive the async event. 

    It will easier if you try to run the examples with the verified flow and see if your setup is working. 

    Thanks,

    Pradipta.

  • 0 in reply to Pradipta Bandyopadhyay
    TI__Intellectual 1660 points

    Hello,

    I have followed the official routine steps for configuration. Additionally, I would like to confirm that we have an external Flash through QSPI. From both the chip manual and API application manual, it can be seen that this MSS will only be generated if the Flash is not connected_ BOOTERRSTATUS event. Are you sure to receive this event after successfully downloading the firmware? The version number I read on AWR2243 is ES1.1: '2.2.1.7'

    Regards，

    Gary

  • 0 in reply to Gary Lu
    TI__Mastermind 32725 points

    Hi Gary,

    Gary Lu said:
    I would like to confirm that we have an external Flash through QSPI. From both the chip manual and API application manual, it can be seen that this MSS will only be generated if the Flash is not connected_ BOOTERRSTATUS event. Are you sure to receive this event after successfully downloading the firmware?

    Yes, in any case you should receive the async event. The Note only describes our test case where we boot over SPI and external flash is not connected. Hence even if the flash is connected the async event should be received.  

    Thanks,

    Pradipta.