• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 85 subscribers
  • Views 334 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.

TMS320F28069M: Remote Programming TMS320F28069M in Medical Device via Micro Memory/USB Flash

Bruce G
Intellectual 565 points
Part Number: TMS320F28069M
Other Parts Discussed in Thread: C2000WARE

Tool/software:

Dear E2E Community,

I am working on a medical device that utilizes the TMS320F28069M microcontroller, and I'm exploring options for remote firmware updates in the field. Due to the nature of the device and its intended use, direct JTAG or SCI (UART) access for programming is not always feasible or desirable for end-users.

My primary goal is to enable users to update the firmware using a common, user-friendly method, ideally involving a micro memory card (like an SD card or microSD card) or a USB flash drive. The update process needs to be robust, secure, and as simple as possible for the end-user.

Specifically, I'm looking for guidance and best practices on the following:

  1. Bootloader Implementation: What are the recommended approaches for implementing a custom bootloader on the TMS320F28069M that can read firmware images from a micro memory card (e.g., connected via SPI) or a USB flash drive (if USB host functionality is practical and available)? Are there existing TI examples, application notes, or libraries that would be good starting points for such a bootloader?

  2. Memory Interface (Micro Memory/USB):

    • For micro memory cards, what is the best way to interface with them (e.g., SPI, SDIO if supported)? Are there specific drivers or code examples for reading FAT32 formatted files from an SD card on the F28069M?

    • For USB flash drives, is it feasible to implement USB host functionality on the TMS320F28069M to read from a USB mass storage device? If so, what are the hardware requirements and software considerations?

  3. Firmware Image Management:

    • What is the recommended method for packaging the firmware image (e.g., binary, hex, encrypted)?

    • How can I ensure the integrity and authenticity of the firmware update (e.g., checksums, digital signatures)?

    • Are there any strategies for atomic updates to prevent bricking the device if power is lost during the update process?

  4. Security Considerations: Given this is a medical device, security is paramount. What are the key security considerations for remote updates, and how can they be addressed (e.g., encryption of firmware, secure boot, anti-rollback mechanisms)?

  5. TI Tools and Resources: Are there specific TI tools, development kits, or documentation that would be particularly helpful for this endeavor beyond the standard datasheet and technical reference manuals?

Any insights, examples, or pointers to relevant TI resources would be greatly appreciated. Thank you in advance for your time and expertise.

Best regards,