• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 78 subscribers
  • Views 426 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

MSP430FR5870: crypto bootloader

Viktorija Cecil
Genius 17961 points
Part Number: MSP430FR5870

Question: regarding the crypto bootloader from a code protection perspective, under the assumption I need this functionality.  

I do no see where the MSP430FR5870 supports this feature.  While our equipment is not networked and there is no way to connect to a remote system, we may perform firmware updates via boot strap loader from the main CPU board in the system indirectly from a USB stick.  Would / does the crypto boot loader function between our CPU mother board and the MSP430 based attached board and secure the “in system” transfer of firmware?

Thanks

Viktorija

  • 0
    TI__Expert 6635 points

    Hi Viktorija,

    Just want to make sure I understand your question - are you asking if the crypto bootloader will secure the transfer between the MSP and CPU mother board? Or are you asking if the crypto bootloader will act as a defense against the firmware given from the USB?

    Thanks,

    Mitch

  • 0 in reply to Mitch Ridgeway
    TI__Genius 17961 points

    I was primarily looking at the transfer between the CPU Mobo and the MSP.  How we accept the encrypted data on the USB drive, I think, is up to us to manage.  Not sure how the crypto bootloader mechanism would even be able to identify the data on the drive directly.

    The mention of the USB was solely to define the mechanism of interface to transfer the payload to the instrument and that the key items mentioned in the Crypto-bootloader document were not in play.  i.e. pushing firmware from a remote location through a “secured channel” or a packetized transfer.

  • 0 in reply to Viktorija Cecil
    TI__Genius 17961 points

    Mitch, additional question:

    In watching the crypt video 3 again, is It possible to create the firmware, encrypt it and transfer it to the USB stick.  Somehow, pass the data from the USB stick to a serial port that connects to the board with the MSP on it.  Then the MSP will receive the data via a serial port?

    Thanks

    Viktorija

  • 0 in reply to Viktorija Cecil
    TI__Expert 6635 points

    Hi Viktorija,

    Sorry for the delay - this is my first time digging into the crypto bootloader materials myself.

    Going back to the original question - the crypto bootloader is a custom BSL designed for FR59xx and FR69xx devices. Unfortunately there is no crypto bootloader implementation for the FR5870 device you are using. 

    "Would / does the crypto boot loader function between our CPU mother board and the MSP430 based attached board and secure the “in system” transfer of firmware?"

    If the firmware image was properly encrypted and if there was a crypto bootloader designed for the FR5870 device, yes, the crypto bootloader would secure the transfer of the firmware between the CPU mobo and MSP430. However, this is not possible since there is no crypto bootloader implementation for the FR5870 device.

    Viktorija Cecil said:
    In watching the crypt video 3 again, is It possible to create the firmware, encrypt it and transfer it to the USB stick.  Somehow, pass the data from the USB stick to a serial port that connects to the board with the MSP on it.  Then the MSP will receive the data via a serial port?

    The FR5870 device supports a UART BSL only:

    As long as you are transmitting the image via UART BSL, you should be able to upload the image. A simple solution would be to do what you previously mention - Upload the image on the USB to a CPU mobo and communicate via UART from the CPU mobo to the MSP430. Since the crypto bootloader is not implemented on this device, encryption is not necessary. 

    Thanks,

    Mitch

**Attention** This is a public forum