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.

AWR1243BOOST: Board initialization problems

Part Number: AWR1243BOOST
Other Parts Discussed in Thread: UNIFLASH

Hello,

We have a AWR1243BOOST (IC hardware is version 2.0) board connected to our host processor over SPI. 

We have issues with board initialization. 

  

If I foramat the flash with Uniflash tool (flash is empty), board SOP set to 4. Boards boot up correctly and I get the interrupt signal. When I read the Async messaged I get the expected MSSPOWERUPDONE reply message. 

(Received raw data: ba dc cd ab 36 a0 22 00 0c 00 00 00 01 00 9a 5f 00 50 14 00 00 00 00 00 ff 7c 0c 00 00 00 00 00 00 00 00 00 02 80).

The POWERUP_TIME is reported around 3ms, which look OK. But the MSS_POWERUP_ BIST_STATUS_ FLAGS is set to 0. Is this OK (Sflash is empty) ?

If it try to powerup the RF part with AWR_DEV_RFPOWERUP_MSG, AWR_DEV_RFPOWERUP_SB  ("raw data":  34 12 21 43 05 80 12 00 00 00 00 00 01 00 e7 7f 00 40 04 00 67 8b), I get the expected ACK ("Raw data": ba dc cd ab 16 80 0e 00 0c 00 00 00 00 00 cf 7f 6c 90) but the Async message never comes (interrupt signals doesn't go high). This is because Sflash is empty, right ?  

Now if I load Sflash on to the BOOST board (SOP is set to 5), with UNIflash tool using files in \mmwave_dfp_01_00_00_01\firmware\ (files: xwr12xx_xwr14xx_radarss.bin, xwr12xx_masterss.bin & xwr12xx_memswap.bin ).

The board boot correctly I get the interrupt signal, but the MSSPOWERUPDONE look strange (Raw data: ba dc cd ab 36 a0 26 00 0c 00 00 00 01 00 96 5f 00 50 18 00 10 aa 05 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 63 d6). 

First of all it is 4 bytes too long, the POWERUP_TIME is reported as 0 and the MSS_POWERUP_ BIST_STATUS_ FLAGS looks strange (0x5aa10).

But this time if i send AWR_DEV_RFPOWERUP_SB, I get the ACK the interrupt goes high but the response is subblock is missing, I only get the header. (raw data: ba dc cd ab 16 80 0e 00 0c 00 00 00 00 00 cf 7f 6c 90)

Question: Could this be a  hardware problem or are we doing something wrong ?

We are using our own implementation of your SPI communication protocol. We thing our implementation is correct as we are able to read Async messages and get proper response from  AWR_MSSVERSION_GET_SB.

Regards,

Rok V.