• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 31 subscribers
  • Views 488 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.

Original question:

AWR1843BOOST: CAN SBL - Error : RPRC Parsing Failure

AWR1843AOP: Error: RPRC Parsing Failure!!!

Bob van der Putten
Prodigy 180 points
Part Number: AWR1843AOP

Hi, 

I created an external application that is updating the software of the radar module AWR1843AOP over the CLI.
I flashed the second bootloader and can flash my modified overhead_3d_people_count_demo_default.bin with the teraterm X-modem-1k.
On the console I see Debug: Total data written = 0x99000.

My external application (running on a attached micro controller) should to the same. I can send all data of the overhead_3d_people_count_demo_default.bin to the radar module without receiving any NACK during data transmission.
However after sending all packages and sending EOT, the message Error: RPRC Parsing Failure!!! is printed on the console.
Browsing through the sbl code, I notice the Authentication check is ok, (I assume all data is transferred successfully..?) but the next stage, SBL_imageParser failed.
I can see that the final package I send is padded with 0 to get a package of 1024 bytes long. Also padding with CPMEOF ( = ^Z,  = 0x1A) is resulting in the same error.
What could go wrong here?

  • 0
    TI__Genius 14415 points

    Hello,

    Can you please let us know what connection to the device you are using for the SBL? Is it CAN like in your previous post? Also, does this loading work with any other code and the people counting code is failing? Or does this fail with all code including the OOB demo for the 1843AOP device?

    The overhead people counting binary was not made for the 1843 device and will need modifications before it will run. However, it seems that this error is actually in the SBL load instead.

    Regards,

    Jackson

  • 0 in reply to Jackson Thomas
    Prodigy 180 points

    Hi,
    I found the issue.
    The link was over Bluetooth (pc<=>and attached micro) and UART (attached micro<=>Radar). For the Bluetooth link, I needed to cut the file into 128byte pieces and used BAS64 encoding for transmission of the data. In the attached micro, I assembled the 8 pieces of 128 bytes into a 1024 byte package, added cntr, ~cntr and CRC16. If I was not able to create a full 1024 byte package, I used 0x1A as padding.
    However, while reading the bin file, the last package was only 64 bytes, and there (pc) I used 0x00 as padding instead of 0x1A..