• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 99 subscribers
  • Views 474 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.

PROCESSOR-SDK-AM62X: USB Diconnect issue

Ryuuichi machida
Guru 13210 points

Part Number: PROCESSOR-SDK-AM62X
Other Parts Discussed in Thread: SK-AM62

Hello,

Let me confirm whether you have ever observed following condition or not.

* My customer use SK-AM62(ver E3) which provided by TI to evaluate their application.
Then they rarely got following condition.

- They connect USB memory to Type A port of EVM.
They continue to store image file approx 10MB to USB memory every per a few 10s of seconds.
In that case, they infrequently see USB memory is NOT recognize on Linux OS. (Of course, even though they do not disconnect USB memory physically.)

Do you have such condtion on your side ?

Best Regards,



  

  • 0
    TI__Guru**** 177851 points

    Hi Machida-san,

    Which version of the SDK is used? Please share the log showing the problem.

    How the image file is written to the USB memory, by Linux commands or custom program?

  • 0 in reply to Bin Liu
    Guru 13210 points

    Hello Bin-san,

    Thank you for your reply.
    Here is answer for your question.

    >Which version of the SDK is used? 
    => They are using Linux SDK ver 08_06_00_42.

    >Please share the log showing the problem.
    => Attached is part of dmesg when disconnect issue happen.
    For example, line 10, 21, 46, 64 show disconnect, however they wait certain time, they can confirm usb re-connection can be observed (line 11, 30, 48, 66).
    They do not perform any action even USB comes to "connect" state. (It seems state go back to "connect" state automatically.)

    >How the image file is written to the USB memory, by Linux commands or custom program?
    Yes, they are using their custom program.

    Best Regards,


    Fullscreen dmesg_E2E.log Download 
    [   23.192979] PVR_K:  1537: RGX Firmware image 'rgx.fw.33.15.11.3' loaded
[   23.224006] PVR_K:  1537: Shader binary image 'rgx.sh.33.15.11.3' loaded
[  129.134074] Initializing XFRM netlink socket
[  130.525709] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[  130.555942] Bridge firewalling registered
[  131.878265] process 'docker/tmp/qemu-check699046381/check' started with executable stack
[  156.866443] usb 1-1: reset high-speed USB device number 3 using xhci-hcd
[  157.023824] sd 0:0:0:0: [sda] 484362240 512-byte logical blocks: (248 GB/231 GiB)
[  304.439541] usb 1-1: USB disconnect, device number 3
[  304.790292] usb 1-1: new high-speed USB device number 4 using xhci-hcd
[  305.636296] usb 1-1: New USB device found, idVendor=18a5, idProduct=0243, bcdDevice= 1.00
[  305.644560] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  305.654299] usb 1-1: Product: STORE N GO
[  305.658357] usb 1-1: Manufacturer: Verbatim
[  305.670304] usb 1-1: SerialNumber: 0721214EB2055A24
[  305.677135] usb-storage 1-1:1.0: USB Mass Storage device detected
[  305.686345] scsi host0: usb-storage 1-1:1.0
[  307.172217] scsi 0:0:0:0: Direct-Access     Verbatim STORE N GO       PMAP PQ: 0 ANSI: 6
[  307.186193] sd 0:0:0:0: [sda] 484362240 512-byte logical blocks: (248 GB/231 GiB)
[  307.194802] usb 1-1: USB disconnect, device number 4
[  307.210451] sd 0:0:0:0: [sda] Write Protect is off
[  307.215456] sd 0:0:0:0: [sda] Mode Sense: 00 00 00 00
[  307.216800] sd 0:0:0:0: [sda] Asking for cache data failed
[  307.226373] sd 0:0:0:0: [sda] Assuming drive cache: write through
[  307.252789] sd 0:0:0:0: [sda] Read Capacity(10) failed: Result: hostbyte=0x07 driverbyte=0x00
[  307.261430] sd 0:0:0:0: [sda] Sense not available.
[  307.266387] sd 0:0:0:0: [sda] 0 512-byte logical blocks: (0 B/0 B)
[  307.272784] sd 0:0:0:0: [sda] Attached SCSI removable disk
[  307.618318] usb 1-1: new high-speed USB device number 5 using xhci-hcd
[  308.460358] usb 1-1: New USB device found, idVendor=18a5, idProduct=0243, bcdDevice= 1.00
[  308.468593] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  308.482260] usb 1-1: Product: STORE N GO
[  308.486264] usb 1-1: Manufacturer: Verbatim
[  308.490496] usb 1-1: SerialNumber: 0721214EB2055A24
[  308.497171] usb-storage 1-1:1.0: USB Mass Storage device detected
[  308.504103] scsi host0: usb-storage 1-1:1.0
[  309.984638] scsi 0:0:0:0: Direct-Access     Verbatim STORE N GO       PMAP PQ: 0 ANSI: 6
[  309.994633] sd 0:0:0:0: [sda] 484362240 512-byte logical blocks: (248 GB/231 GiB)
[  310.003359] sd 0:0:0:0: [sda] Write Protect is off
[  310.008257] sd 0:0:0:0: [sda] Mode Sense: 23 00 00 00
[  310.009340] sd 0:0:0:0: [sda] No Caching mode page found
[  310.014924] sd 0:0:0:0: [sda] Assuming drive cache: write through
[  310.050162]  sda: sda1
[  310.056895] sd 0:0:0:0: [sda] Attached SCSI removable disk
[  475.607052] usb 1-1: USB disconnect, device number 5
[  475.770814] FAT-fs (sda1): unable to read boot sector to mark fs as dirty
[  475.942497] usb 1-1: new high-speed USB device number 6 using xhci-hcd
[  476.785024] usb 1-1: New USB device found, idVendor=18a5, idProduct=0243, bcdDevice= 1.00
[  476.793948] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  476.801337] usb 1-1: Product: STORE N GO
[  476.805405] usb 1-1: Manufacturer: Verbatim
[  476.810276] usb 1-1: SerialNumber: 0721214EB2055A24
[  476.819704] usb-storage 1-1:1.0: USB Mass Storage device detected
[  476.826836] scsi host0: usb-storage 1-1:1.0
[  478.305642] scsi 0:0:0:0: Direct-Access     Verbatim STORE N GO       PMAP PQ: 0 ANSI: 6
[  478.315899] sd 0:0:0:0: [sda] 484362240 512-byte logical blocks: (248 GB/231 GiB)
[  478.324335] sd 0:0:0:0: [sda] Write Protect is off
[  478.329163] sd 0:0:0:0: [sda] Mode Sense: 23 00 00 00
[  478.330038] sd 0:0:0:0: [sda] No Caching mode page found
[  478.335624] sd 0:0:0:0: [sda] Assuming drive cache: write through
[  478.365554]  sda: sda1
[  478.370726] sd 0:0:0:0: [sda] Attached SCSI removable disk
[  833.431086] usb 1-1: USB disconnect, device number 6
[  833.610981] FAT-fs (sda1): unable to read boot sector to mark fs as dirty
[  833.766343] usb 1-1: new high-speed USB device number 7 using xhci-hcd
[  834.608111] usb 1-1: New USB device found, idVendor=18a5, idProduct=0243, bcdDevice= 1.00
[  834.616344] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3

  • 0 in reply to Ryuuichi machida
    TI__Guru**** 177851 points

    Hi Machida-san,

    Please try a couple tests:

    - instead of using their custom program, can you use a bash script which does the similar write access to the USB memory to see if the issue still happens?

    - please try different brand of USB devices to see if the issue still happens.

  • 0 in reply to Bin Liu
    Guru 13210 points

    Hello Lin-san,

    Thank you for your reply.

    instead of using their custom program, can you use a bash script which does the similar write access to the USB memory to see if the issue still happens?

    If you have any sample bash script for access USB, is it possible to share this as example ?

    I will check with customer about different brand of USB memory.

    BR, 



  • 0 in reply to Ryuuichi machida
    TI__Guru**** 177851 points

    Hi Machida-san,

    Please try the script attached below.

    https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/791/test_2D00_usb.sh

    Please modify the 3 variables defined at the beginning of the script accordingly:

    SRC_FILE is the name of the 10MB data file to be copied;
    TGT_DIR is the USB device mounting directory;
    max_loop defines how many times to copy the file; "-1" means infinitely;