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

Part Number: MSP432E401Y

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.