MSP432E401Y: Firmware Update Security & IP Protection Guidance (TI-TXT + BSL Scripter to Ethernet CRC Bootloader)

Part Number: MSP432E401Y
Other Parts Discussed in Thread: ARM-CGT, SEGGER

Tool/software:

Hi TI team,

I’m evaluating a production firmware-update flow on MSP432 devices that use the Ethernet bootloader with CRC enabled and enforced, with images in TI-TXT format (.out -> .bin -> .txt using bin2hex) programmed  via TI BSL Scripter. Before finalizing the rollout, I’d appreciate TI’s guidance on a few security and IP-protection points:

  1. Open file format & IP exposure

    • Can you please explain what type of file format TI-TXT is and what information it contains? From TI’s perspective, what are the practical IP risks of distributing updates in this format (e.g., ease of reverse-engineering strings/bytes), and what mitigations does TI recommend in production?

  2. Encryption / confidential delivery

    • Is there an official TI solution or tool to deliver encrypted firmware for MSP432 over the Ethernet BSL path so that recipients cannot read the application image?

  3. Alternative update tools / flows

    • Besides BSL Scripter, are there other TI-supported updaters or command-line options appropriate for Ethernet-based MSP432 updates?

  4. TI’s security best practices for MSP432 field updates

    • For a production environment, what are TI’s recommended best practices?

    • Are there application notes, reference implementations, or training materials you suggest for MSP432 specifically (preferably for the Ethernet BSL path)?

Summary of what I’m looking for:

  • TI’s position on whether TI-TXT is considered secure for cybersecurity purposes in production.

  • Whether TI offers an official encrypted/authenticated update flow for MSP432 over Ethernet BSL, and if not, the recommended approach (tools, examples, app notes).

  • Any supported alternatives to BSL Scripter for Ethernet updates and guidance on tool redistribution.

Thanks in advance for the information, docs, tools, or examples.

  • Hi, can I please get some support on this question?

  •  Hi,

    I have previously sent this question via email a few weeks ago and had no feedback. Please could we get an answer for the customer on this??

    Thanks

    Paul.

  • Hi Parryh,

    Open file format & IP exposure

    • Can you please explain what type of file format TI-TXT is and what information it contains? From TI’s perspective, what are the practical IP risks of distributing updates in this format (e.g., ease of reverse-engineering strings/bytes), and what mitigations does TI recommend in production?

    Some details about TI-TXT can be found in some documents that are mentioned in the link:
    https://software-dl.ti.com/ccs/esd/documents/sdto_cgt_A-Brief-History-of-TI-Object-File-Formats.html 
    I assume that you are using the TI ARM-CGT (and not the ARM-CGT-CLANG) so you will need to look in the 'HEX conversion utility' section of the ARM Assembly Language Tools User's Guide SPNU118.

    I assume it might be possible to reverse engineer the HEX format if you know the meaning of the formatting.
    See also my comments below about production programming.

    Encryption / confidential delivery

    • Is there an official TI solution or tool to deliver encrypted firmware for MSP432 over the Ethernet BSL path so that recipients cannot read the application image?

    The only security documents we have available for MSP432 are listed below:
    MSP432 Security Overview - https://www.ti.com/lit/pdf/slau697 
    It points to additional documents, but there is nothing specifically for the Ethernet BSL.

    TI’s security best practices for MSP432 field updates

    • For a production environment, what are TI’s recommended best practices?

    • Are there application notes, reference implementations, or training materials you suggest for MSP432 specifically (preferably for the Ethernet BSL path)?

    If you looking for tools for production programming then some companies like Goepel, Promik, Segger have tools to enable In-circuit-programming (and probably have some security layers that could encapsulate the MSP432 FW) as part of the tooling used for PCB production testing.
    Those company usually work with the EMS/CM to provide what is needed on the production lines.

    Some additional tools might be available for programming the on-chip flash before it is soldered on the PCB:
    https://dev.ti.com/tirex/explore/node?node=AMW2mmqkp8OzTm82nndsfg__FUz-xrs__LATEST 


    For field update (ie update systems deployed at end customers) then I assume that you will have to develop your own solution.

    Hope it helps,

    Anthony