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.

IWR1443: Bootloader Close Command issues

Part Number: IWR1443

We have added features for reprogramming the IWR1443 SFlash from STM32 MCU via UART reference to SWRA561. The MSS and BSS are working fine without CLOSE FILE command at the end of file downloading,

However IWR1443 is working abnormal when we add CLOSE FILE command(AA 00 07 26 22 00 00 00 04 OR AA 00 07 24 22 00 00 00 02 ) at the end of WRITE FILE to SFLASH command.

Are there any timing requirements for CLOSE FILE command? What does it do at the end of file downloading?

  • Hi,

    To confirm, are you waiting for the response to WRITE FILE to SFLASH commands before sending the CLOSE FILE commands?

    Best Regards,
    Alec

  • We don't proceed until we confirmed ACK(00 04 CC 00 CC ) from IWR1443 after every WRITE FILE to SFLASH commands.

    We also send GET STATS command(AA 00 03 23 23) after ACK received. We can get succeed response(00 03 40 40)..

  • Hi,

    My sincerest apologies for the delays due to the holidays. I am investigating this a bit further from my end to ensure there are no special considerations for the CLOSE FILE command. Is it possible that the CRC is not matching when being sent? Have you tried this with a TI-provided binary, or just custom binaries? Lastly, when you say it behaves abnormally, could you provide additional detail? Does the device not provide an ack/nack for this command? Does the device entirely stop responding to commands? 



    Best Regards,
    Alec

  • CRC is correct for CLOSE FILE command,  and we can get ACK after CLOSE FILE command is sent.

    All the same when we tried with xwr14xx_mmw_demo.bin. Then IWR1443 entirely stop working after power reset.

    It is strange that IWR1443 seems to be working fine without CLOSE FILE command.

  • Hi,

    Understood, thank you for the clarification and additional details. Please allow me some time to look into this further. I will be sure to provide an update by no later than Friday.

    Best Regards,
    Alec

  • Hi,

    Actually, I have one additional follow-up question. You mentioned that you were sending the GET STATUS command after receiving the ack, was that after the ACK for writing to the SFLASH, or the ACK after you do the CLOSE FILE command? It would be good to know the status after the CLOSE FILE command.

    Best Regards,
    Alec

  • We send the GET STATUS command after receiving the ACK for both every WRITE FILE to SFLASH commands.and CLOSE FILE command.

  • Hi,

    My apologies for the delay here, could you please confirm the exact status code you receive after sending the GET STATUS after the CLOSE FILE command?

    Best Regards,
    Alec