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.

TUSB9261: TUSB9261-Q1: Linux tool to load firmware directly to internal RAM via USB HID (no SPI flash on board)

Part Number: TUSB9261

Hello,

I would like to use the TUSB9261-Q1 without an external SPI flash, loading the firmware directly into the chip's internal RAM over USB at from a Linux host, using the HID boot loader described in the datasheet.

Two questions:

  1. Could you please send me the Linux flashburner tool over E2E PM.
  2. Does the Linux (or Windows SLLC414) flashburner expose the "download to RAM" option of the HID download report, allowing the firmware (SLLC416) to run from internal RAM without any SPI flash on the board? If yes, how is it selected? If no, is there sample code showing how to issue the HID "prepare for download" report with the RAM flag and the subsequent bulk transfer to endpoint 2?
  • Hi Yannick,

    Could you please send me the Linux flashburner tool over E2E PM.

    Please accept my E2E friend request and I can send that over.

    Does the Linux (or Windows SLLC414) flashburner expose the "download to RAM" option of the HID download report, allowing the firmware (SLLC416) to run from internal RAM without any SPI flash on the board? If yes, how is it selected? If no, is there sample code showing how to issue the HID "prepare for download" report with the RAM flag and the subsequent bulk transfer to endpoint 2?

    This Linux and Windows flashburner do not have the ability to "download to RAM". If no SPI flash is being used, the TUSB9261 will need to be flashed on start-up each time the device is reset. The TUSB9261 does not save the .bin/.hex when flashed, and typically requires a SPI Flash to hold these files and flash the TUSB9261 on start-up.

    Is there any reason you are avoiding using a SPI flash?

    Thanks,

    Ryan

  • Hello,

    Closing thread due to inactivity. If you have any follow-up questions or concerns, feel free to reply.

    Thanks,

    Ryan