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: The 65,536 sec (16-bit Timer ?) downtime issue

Part Number: TUSB9261

Dear Team,

My customer has used TUSB9261PVP with "TUSB926x Default Firmware, U1/U2 Disabled" firmware. They have the 65,536 sec (16-bit Timer ?) downtime issue once in a long while. This issue happens during a command transmitting and receiving. While Host transmits a command, this issue happens and nor reply for the 65,536 sec, after the 65,536 sec past, Host receive a reply from the device (media drive) and resumes operation.

Q1. Is there any possibility of the 65,536 sec (16-bit Timer ?) downtime issue by "TUSB926x Default Firmware, U1/U2 Disabled" firmware?

Q2. Could you guess the root cause of this issue?

Thank you.

Best Regards,

Koshi Ninomiya

  • Hello,

    Can you please provide command logs of the event? Or protocol trace data?

    Thanks,
    JMMN
  • Hi JMMN,

    Their product keeps a log of data transfer status, but does not keep a command log. So, they knew that the data transfer was down for 65,536 sec and resumed the data transfer operation after that, but they did not know that what command was send to the TUSB9261 at that event. This issue happened very rarely, it is hard for them to catch the command at that event.

    ATA EPC (Extended Power Control) Command is suspected, but we are not sure right now.
    About the firmware, the customer has used the Firmware version 0.99, not the latest Firmware version 1.05.

    Does the TUSB9261 has a feature of the 16-bit Timer with bit count up by 1 sec?

    If the TUSB9261 has the 16-bit Timer with bit count up by 1 sec feature, under what condition does that feature work?

    Thank you.

    Best Regards,

    Koshi Ninomiya
  • Hi Koshi-san,

    The TUSB9261 does not have any 16-bit timer which would cause this issue. Any data transfer delays would be caused by the SATA device itself. You can try the latest v1.05 firmware as it has other improvements but I do not think it will affect this problem you are encountering.

    Regards,
    Brian