• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 32 subscribers
  • Views 923 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.

TUSB9261 Firmware V1.05 - UART Error Codes / USB Powered Device

Aaron Liebold
Intellectual 380 points
Other Parts Discussed in Thread: TUSB9261

I'm working on a project with the TUSB9261 using the default firmware, v1.05, and I am experiencing problems trying to get it to connect with my computer as a hard drive. It had no problems communicating with the computer in bootloader mode and flashing the firmware. In the UART output I get the following when I connect power and then plug in the USB:

========================================================
|| TUSB926x Firmware v1.05 [Oct 3 2014 16:33:57] ||
|| Device ID: 0x0000 ||
========================================================

Reset Flag(s): [Power-Up]

[0000000001] Datapath RAM Usage: 80208 / 81920 bytes.
[0000000001] Supported NCQ Depth: 32
[0000000001] U1/U2 Transistions: OFF
[0000000001] USB PHY Suspend: ON
[0000000001] SATA LPM: OFF
[0000000001] Device is Bus-powered.
[0000000001] -> usb_hal_init()
[0000000001] USB Core Ver: 0x120a.
[0000000001] USB SSC is OFF.
[0000000051] -> usb_hal_connect()
[0000000051][0000000051] LTSSM state = (0x5) RX DETECT.
-> ahci_init()
[0000000051] -> ahci_hba_reset()
[0000000056] SATA Gen-2 speed negotiated.
[0000000150] HS/FS/LS state = (0x0) ON.
[0000000153] HS/FS/LS state = (0x5) EARLY SUSPEND.
[0000000156] HS/FS/LS state = (0x3) SUSPEND.
[0000002973]
[0000002973] ================================================
[0000002973] IDENTIFY DEVICE INFO
[0000002973] ================================================
[0000002973]
[0000002973] Model: WDC WD1600BEKT-66F3T2
[0000002973] FW Rev: 13.01A13
[0000002973] Serial: WD-WX80AA9H6844
[0000002973]
[0000002973] Spec Compliance: ATA-7
[0000002973] Removable Media: No
[0000002973] Rotational Speed = 7200 RPM
[0000002973] UDMA Modes = 0x003f
[0000002973] PIO Modes = 0x0003
[0000002973]
[0000002973] LBA48: Yes
[0000002973] Max LBA = 0x00000000 12a19eb0
[0000002973] Write FUA: No
[0000002973] World Wide Name = 0x50014ee2 03a7cf2b
[0000002973]
[0000002973] SATA Speed: Gen2
[0000002973] NCQ Support: Yes
[0000002973] Queue Depth = 31
[0000002973]
[0000002973] Logical Sector Size = 512 bytes
[0000002973] Physical Sector Size = 512 bytes
[0000002973] Logical Sector Offset = 0
[0000002974]
[0000002974] ================================================

[0000002977] Connected to 1 AHCI device(s).
[0000049047] Num of port resets = 6.
[0000049047] USB Reset event occurred.
[0000049047] -> ahci_reset_lun(0)
[0000049047] -> ahci_fatal_error_recovery() - dev_status = 0x00000080, outstanding_cmd_slots = 0x00000000, force_comreset = 0.
[0000049047] -> ahci_port_reset(0)
[0000049522] Connected at HIGH speed.
[0000049522] HS/FS/LS state = (0x0) ON.
[0000049522] -> gio_isr() - flags = 0x00000008.
[0000049522] Push button input detected.
[0000050025] HS/FS/LS state = (0x5) EARLY SUSPEND.
[0000050026] USB Reset event occurred.
[0000050026] -> ahci_reset_lun(0)
[0000050037] Connected at HIGH speed.
[0000050037] HS/FS/LS state = (0x0) ON.
[0000050054] -> usb_hal_set_address() - addr: 0x9.
[0000050082] -> handle_usb_set_configuration() - val = 1.
[0000050104] AHCI task file error! P0TFD error = 0x04, status = 0x51.
[0000050104] -> ums_bot_ata_error_callback() - gBOT_state = 3.
[0000050104] -> ums_bot_send_CSW() - status = FAILED. CDB[0] = 0xa2.
[0000050105] AHCI task file error! P0TFD error = 0x04, status = 0x51.
[0000050105] -> ums_bot_ata_error_callback() - gBOT_state = 3.
[0000050105] -> ums_bot_send_CSW() - status = FAILED. CDB[0] = 0xa2.
[0000050105] AHCI task file error! P0TFD error = 0x04, status = 0x51.
[0000050105] -> ums_bot_ata_error_callback() - gBOT_state = 3.
[0000050105] -> ums_bot_send_CSW() - status = FAILED. CDB[0] = 0xa2.
[0000050105] AHCI task file error! P0TFD error = 0x04, status = 0x51.
[0000050106] -> ums_bot_ata_error_callback() - gBOT_state = 3.
[0000050106] -> ums_bot_send_CSW() - status = FAILED. CDB[0] = 0xa2.
[0000050106] AHCI task file error! P0TFD error = 0x04, status = 0x51.
[0000050106] -> ums_bot_ata_error_callback() - gBOT_state = 3.
[0000050106] -> ums_bot_send_CSW() - status = FAILED. CDB[0] = 0xa2.
[0000050106] AHCI task file error! P0TFD error = 0x04, status = 0x51.
[0000050106] -> ums_bot_ata_error_callback() - gBOT_state = 3.
[0000050106] -> ums_bot_send_CSW() - status = FAILED. CDB[0] = 0xa2.
[0000050107] -> ums_bot_case_handler() - case 5.
[0000050107] -> ums_bot_case_handler() - case 5.
[0000050133] @Warning: scsi_handle_mode_sense_cmd() - page code 0x1c not supported.
[0000050133] -> ums_bot_send_CSW() - status = FAILED. CDB[0] = 0x1a.
[0000050133] -> ums_bot_case_handler() - case 5.
[0000050134] -> ums_bot_case_handler() - case 5.
[0000050134] -> ums_bot_case_handler() - case 5.
[0000050137] -> ums_bot_case_handler() - case 5.
[0000050139] -> ums_bot_case_handler() - case 5.
[0000050210] -> ums_bot_case_handler() - case 5.
[0000050210] -> ums_bot_case_handler() - case 5.
[0000050230] -> ums_bot_case_handler() - case 5.
[0000050230] -> ums_bot_case_handler() - case 5.
[0000050250] -> ums_bot_case_handler() - case 5.
[0000050250] -> ums_bot_case_handler() - case 5.
[0000050254] -> ums_bot_case_handler() - case 5.
[0000050254] -> ums_bot_case_handler() - case 5.
[0000050258] -> ums_bot_case_handler() - case 5.
[0000050258] -> ums_bot_case_handler() - case 5.
[0000050277] -> ums_bot_case_handler() - case 5.
[0000050278] -> ums_bot_case_handler() - case 5.
[0000050296] -> ums_bot_case_handler() - case 5.
[0000050296] -> ums_bot_case_handler() - case 5.

Where do I find the interpretation of these errors? Is there documentation for the Firmware itself?

Also, how do I configure the system to run the HDD solely from USB 2.0 or greater?

Thanks,

Aaron

  • 0
    TI__Genius 11255 points

    Hello Aaron,

    Could you send us more information about your problem?

    -What kernel version and Linux flavor are you using?

    -Is it reproducible using the TI's EVM?

    -What HDD are you attaching to the TUSB9261? it also happens using a different HDD?

    -is this problem present using Windows?

    -How are you configuring the TUSB9261 (UAS, HID, self/bus power...)?

    Best regards,

    Roberto.

  • 0 in reply to Roberto Diaz
    Intellectual 380 points
    That test was conducted with Windows 10. I have also connected the device to a Raspberry Pi running Raspbian (Debian) and the device did not appear in the list of USB devices (lsusb).

    I do not have the EVM.

    The HDD is:
    [0000002973] ================================================
    [0000002973] IDENTIFY DEVICE INFO
    [0000002973] ================================================
    [0000002973]
    [0000002973] Model: WDC WD1600BEKT-66F3T2
    [0000002973] FW Rev: 13.01A13
    [0000002973] Serial: WD-WX80AA9H6844
    [0000002973]
    [0000002973] Spec Compliance: ATA-7
    [0000002973] Removable Media: No
    [0000002973] Rotational Speed = 7200 RPM
    [0000002973] UDMA Modes = 0x003f
    [0000002973] PIO Modes = 0x0003
    [0000002973]
    [0000002973] LBA48: Yes
    [0000002973] Max LBA = 0x00000000 12a19eb0
    [0000002973] Write FUA: No
    [0000002973] World Wide Name = 0x50014ee2 03a7cf2b
    [0000002973]
    [0000002973] SATA Speed: Gen2
    [0000002973] NCQ Support: Yes
    [0000002973] Queue Depth = 31
    [0000002973]
    [0000002973] Logical Sector Size = 512 bytes
    [0000002973] Physical Sector Size = 512 bytes
    [0000002973] Logical Sector Offset = 0
    [0000002974]
    [0000002974] ================================================

    I will try to test with a different HDD tomorrow.

    I just tried connecting to a different computer. The other computer is also running Windows 10. Windows found the driver and installed the device as a Ti USB 3.0 to SATA Bridge, but the drive did not appear in the file system.

    I have the device configured with HID and UAS, and Self-Powered.
  • 0 in reply to Roberto Diaz
    Intellectual 380 points
    This morning I tried using a different HDD and it connected to the computer immediately, so it seems that the HDD was the culprit. However, I still cannot run the HDD from USB alone. A previous version of our design was able to do this. What are some parameters that can affect the unit's ability to run off of USB alone? When our device is powered solely from USB only the TUSB9261 and HDD are powered via USB 5V and a 3.3V and 1.1V buck converter. Do you have any reccomendations and maybe a reference design for a USB powered HDD?

    Thanks,
    Aaron