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 Firmware revisions

Part Number: TUSB9261

Can you also explain the differences between the 1.05 firmware and the 1.06 firmware?

The product page lists 1.05 as the most recent firmware, however there is a forum post where 1.06 is listed as the most recent (https://e2e.ti.com/support/interface/usb/f/1008/p/679642/2504756?tisearch=e2e-sitesearch&keymatch=tusb9261%20uart#2504756 ). Which should I be using?

Are there any further firmware revisions that I should be aware of?

Thanks

Tim

  • Hi Tim,

    v1.05 is the latest released.  v1.06 is not yet available on ti.com but I am working on that.

    v1.06 change log:

    - Increased timeout for SATA device identification from 2 sec to 7 sec.

    - Disabled 4KB sector emulation to allow disk compatibility with other SATA hosts.
    - Added support for write FUA (Forced Unit Access).
    - Added support for ACTIVE, IDLE, and STANDBY power condition for START/STOP UNIT SCSI command.
    - Added support for SCSI READ CD command with transfer length > 64KB to fix audio CD reading under Linux operating system.
    - Added support for logical block provisioning management (LBPME) and LBPRZ bits in READ CAPACITY (16) response per SAT-4 spec.
    - Added support for ANC_SUP, LBPRZ, and LBPU bits in logical block provisioning VPD page per SAT-4 spec.

    Regards,

    Brian

  • So I downloaded 1.06 from the linked forum post and have been using it. Should I reprogram everything back to 1.05, or is it just a matter of time until that specific version is released?

    Asked another way, do you know of or expect any changes to the 1.06 firmware from the linked forum post?

    And thank you for the change notes.

    Tim
  • Tim,
    V1.06 should be released by end of August to the TUSB9261 product page. I would not use any FW posted to E2E posts as it may not be final or contain some special debug. The FW in that other post should be close or identical though.