• State TI Thinks Resolved
  • Locked Locked
  • Replies 8 replies
  • Answers 2 answers
  • Subscribers 32 subscribers
  • Views 424 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.

IWR1843: 1843 SBL file Parsing Process

chao huang
Prodigy 230 points
Part Number: IWR1843

HI,recently,I've been testing the 1843 CAN SBL,I had a problem with RPRC Parsing Failure.I checked the forums for similar questions and the question doesn't seem to have been well answered.

So I want to write a  host computer for 1843 can sbl.so I'd like to clarify the following questions:

Normally a bootloader file verification process should look like this:

1.The host computer calculates the verification code of the file.

2.The host  computer transfers files and verification codes to the MCUr by some protocol.

3.MCU calculates the verification code of the file according to the file and compares it with the verification code calculated by the host  computer.

4.If the verification codes are consistent, the transmission succeeds. Otherwise, the transmission fails.

Is the lab0012_CAN_SBL verification process consistent with the above procedure?

If yes, what protocol is used to transmit the code and checksum code? If not, I hope you can tell me the specific implementation method

  • 0
    TI__Mastermind 23725 points

    Hello

    In order to expedite the help  on this front. It would be helpful to  know the  application and end solution you are seeking to implement as this will allow us to put you in touch with the right team.

    Thank you,

    Vaibhav

  • 0 in reply to Vaibhav Mahimkar
    Prodigy 230 points

    my ultimate goal is to implement the 1843 or 1642 CAN-based bootloader functionality ,Lab0012 CAN SBL has implemented most of the functions I wanted.but lab00012 has parsing errors when using CANFD to transmit data and the PC interface is not very good.So I decided to redo the PC interface and want to know the CAN based data transfer protocol between PC and MCU.

  • 0 in reply to chao huang
    TI__Mastermind 23725 points

    Hello

    Thank you for responding.  Is this implementation meant for  application that is in vehicles for ADAS applications  example -  Autonomous driving  or assisting while parking the vehicle.

    or

    Is this meant to be used inside the vehicle for  non-ADAS applications.

    Thank you,

    Vaibhav

  • 0 in reply to Vaibhav Mahimkar
    Prodigy 230 points

    It will be used inside the vehicle for  non-ADAS applications in after market.

  • 0 in reply to chao huang
    TI__Genius 17265 points

    Hi,

    The current SBL implementation does not perform any authentication beyond a CRC check. If you need authentication for your use case, we recommend that you add your own implementation to the SBL source code. This will ensure you have control over the protocol and type of authentication from both sides of the CAN bus. From the SBL source, you will likely want to look at image_validity.c and multicoreimage_parser.c, which are located under <mmwave_sdk_loc>\packages\ti\utils\sbl\src, as there contain the boilerplate code that you would want to add to. 

    Best Regards,
    Alec

  • 0 in reply to Alec May
    Prodigy 230 points

    Hi, I just want to know what protocol the CRC code is transmitted to MCU,something like Xmodel or Ymodel.

    For example, PC send the CRC code after all the data has been transmitted by canfd?  or some other way?

  • 0 in reply to chao huang
    TI__Genius 17265 points

    Hi,

    The CRC is built into the binary image during the image generation process, so there is so no protocol unique to SBL for it. You can read more about the image generation process at <mmWave_SDK_Loc>\packages\scripts\ImageCreator\Image_Creator_User_Guide.pdf

    Best Regards,
    Alec

  • 0 in reply to Alec May
    Prodigy 230 points

    Thank you, I got it.