• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 98 subscribers
  • Views 1263 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.

am3359 usb babble interrupt error

zhiheng wei
Intellectual 285 points
Other Parts Discussed in Thread: AM3359

I have developed an am3359 card . I use the USB1 as host. In schematic, usb_Bus5v is connected directly to the pcb   5v.

When plug the U disk to the 3359, it work well, and can read or write.

The question is, when unplug the u disk, occasionally, rarely （ 1/10） will give :usb1 babble interrupt  occured! please issue long reset to make the usb work functional !

I didn't use a power switch like the evm schematic, use  AM3559_USB1_DRVVBUS to control the switch to power off or on the u dsik, may this be the question? I tried umount the u disk and then unplug the disk, the error still will appear. beacause I dont use the DRWBUS pin, so maybe there is no differences between unmount and unplug the disk directly.

The capacity on the USBbus is 0.1 uF, maybe it‘s too small , I will solder a 10 uF on it later.

I really want to know  how the babble error appear.

Reason maybe The USB layout is not good, gets Signal integrity problem？But it can work well before unplug the usb disk.

Or when unplug the usb disk, makes lots of noise on the usb power pin,then make the babble? I have seen a test  

report said that when add noise to the usb 5v, then will make the usb report babble ? I later will test a usb hub. First plug a hub in 3359, and next plug or unplug u disk to the hub, to find the error appear or not.

Thank you for your reply!

  • 0
    Intellectual 285 points

    I put two 10uF/16V tan capacity in parallel on the USB5V, it does not show better. 

    //=============================================

     I later will test a usb hub. First plug a hub in 3359, and next plug or unplug u disk to the hub, to find the error appear or not.

    Today I test the 3359 board as above. I found it more stable than without the usb hub.

    But unfortunately, sometime it will give below:  and then the usb controller  can not work.

    =======================

    I also test the SBC8600B(  http://www.timll.com/chinese/OMAP/SBC8600B.asp ) board(also is am3359 board,but expand the usb1 with chip USB2512, it still will give below warning and then the usb can not work.

    ========================

    Things I do are just plug and unplug  the usb disk without unmount command.

     

    usb 1-1.7: New USB device found, idVendor=0951, idProduct=1666
    usb 1-1.7: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    usb 1-1.7: Product: DataTraveler 3.0
    usb 1-1.7: Manufacturer: Kingston
    usb 1-1.7: SerialNumber: 60A44C3FACDBBDC1596E6E7E
    scsi43 : usb-storage 1-1.7:1.0
    scsi 43:0:0:0: Direct-Access Kingston DataTraveler 3.0 PMAP PQ: 0 ANSI: 6
    sd 43:0:0:0: [sda] 30720000 512-byte logical blocks: (15.7 GB/14.6 GiB)
    sd 43:0:0:0: [sda] Write Protect is off
    sd 43:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
    sda: sda1
    sd 43:0:0:0: [sda] Attached SCSI removable disk
    usb 1-1.7: USB disconnect, device number 46
    sd 43:0:0:0: [sda] Unhandled error code
    sd 43:0:0:0: [sda] Result: hostbyte=0x01 driverbyte=0x00
    sd 43:0:0:0: [sda] CDB: cdb[0]=0x28: 28 00 00 00 1f 80 00 00 01 00
    end_request: I/O error, dev sda, sector 8064
    FAT-fs (sda1): unable to read boot sector
    Unable to handle kernel NULL pointer dereference at virtual address 00000004
    pgd = de154000
    [00000004] *pgd=9e3ef831, *pte=00000000, *ppte=00000000
    Internal error: Oops: 17 [#1]
    Modules linked in:
    CPU: 0 Not tainted (3.2.0 #1)
    PC is at sd_revalidate_disk+0x18/0x19d0
    LR is at rescan_partitions+0xa4/0x510
    pc : [<c025e4fc>] lr : [<c0103f40>] psr: a0000013
    sp : de583c50 ip : de583cd8 fp : de583cd4
    r10: 00000000 r9 : 00000083 r8 : 00000000
    r7 : 00000000 r6 : ffffff85 r5 : df37a400 r4 : de583d00
    r3 : c025e4e4 r2 : df37a400 r1 : 00000002 r0 : df37a400
    Flags: NzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user
    Control: 10c5387d Table: 9e154019 DAC: 00000015
    Process mount (pid: 15624, stack limit = 0xde5822f0)
    Stack: (0xde583c50 to 0xde584000)
    3c40: df37a468 df37a440 df37a400 ffffff85
    3c60: df37a468 de8023c0 de583c94 de583c78 00000000 df37a400 de583c94 de583c88
    3c80: de583cac de583c90 c00c3a20 c01d7878 de8023c0 00000000 ffffff85 00000000
    3ca0: de583cbc 00000000 c00dac1c de583d00 df37a400 ffffff85 00000000 de8023d0
    3cc0: 00000083 00000000 de583d3c de583cd8 c0103f40 c025e4f0 c024f6ac c0234cc0
    3ce0: c064e6fc de637800 de583d14 de8023c0 df37a400 df37a40c df37a468 00000000
    3d00: df37a400 00000000 00000002 00000002 c025df0c de8023c0 df37a400 ffffff85
    3d20: 00000000 de8023d0 00000083 00000000 de583d7c de583d40 c00db848 c0103ea8
    3d40: de583d4c 00000001 de583d64 00000000 c0234cd0 de802740 df37a400 de8023c0
    3d60: 00000000 de802750 00000083 de8023c0 de583dbc de583d80 c00db790 c00db614
    3d80: de583dac 00000000 c01d927c 00000001 c0234cd0 df37a400 de583dd0 de8023c0
    3da0: c00592e8 de802740 de582000 de583ddc de583e14 de583dc0 c00dbb38 c00db614
    3dc0: c00da2ec c063c004 00000083 de8023e4 de583df4 de583de0 c00b6c58 c00c7cdc
    3de0: de802740 00000001 de583e14 de802740 c063c004 00000083 00000083 00008000
    3e00: de583f38 00000000 de583e34 de583e18 c00dbd74 c00db984 de565d80 de07f380
    3e20: c063c004 00000083 de583e7c de583e38 c00b0504 c00dbd48 de583e9c de583e48
    3e40: c01d8244 c00a9a90 c0689328 de565df0 000080d0 df0111b8 de565d80 de07f380
    3e60: 00000000 c063c004 00000000 00008000 de583e94 de583e80 c012364c c00b04d8
    3e80: c01249e4 c0689304 de583ec4 de583e98 c00aff44 c0123638 c00c7260 c0092484
    3ea0: de565d80 de07f380 00008000 c063c004 00000000 00008000 de583eec de583ec8
    3ec0: c00c8c2c c00aff04 00008000 de07f380 00000000 de07f200 c063c004 de583f38
    3ee0: de583f14 de583ef0 c00c8cc4 c00c8be0 00000000 00008000 de07f380 de07f200
    3f00: 00000020 de583f38 de583f6c de583f18 c00c93a0 c00c8c94 00000000 0000000a
    3f20: 00001000 00000000 de583f54 de583f38 c0092414 c0092320 df010200 de98c798
    3f40: bec2dd15 00000000 de656000 bec2dd15 00008000 c0015328 de582000 00000000
    3f60: de583fa4 de583f70 c00c9534 c00c8d68 00000000 00000005 000000be 00000000
    3f80: de07f380 de07f200 00000000 bec2d844 4009d4b0 00000015 00000000 de583fa8
    3fa0: c0015180 c00c94a0 00000000 bec2d844 bec2dd15 bec2dd1f 0009f278 00008000
    3fc0: 00000000 bec2d844 4009d4b0 00000015 00000000 0009233a 0009ebe0 00082740
    3fe0: 00008000 bec2d3d4 0004b848 40411864 20000010 bec2dd15 00000000 00000000
    Backtrace:
    [<c025e4e4>] (sd_revalidate_disk+0x0/0x19d0) from [<c0103f40>] (rescan_partitions+0xa4/0x510)
    [<c0103e9c>] (rescan_partitions+0x0/0x510) from [<c00db848>] (__blkdev_get+0x240/0x370)
    [<c00db608>] (__blkdev_get+0x0/0x370) from [<c00db790>] (__blkdev_get+0x188/0x370)
    [<c00db608>] (__blkdev_get+0x0/0x370) from [<c00dbb38>] (blkdev_get+0x1c0/0x308)
    [<c00db978>] (blkdev_get+0x0/0x308) from [<c00dbd74>] (blkdev_get_by_path+0x38/0x70)
    [<c00dbd3c>] (blkdev_get_by_path+0x0/0x70) from [<c00b0504>] (mount_bdev+0x38/0x194)
    r7:00000083 r6:c063c004 r5:de07f380 r4:de565d80
    [<c00b04cc>] (mount_bdev+0x0/0x194) from [<c012364c>] (ext2_mount+0x20/0x28)
    [<c012362c>] (ext2_mount+0x0/0x28) from [<c00aff44>] (mount_fs+0x4c/0x188)
    [<c00afef8>] (mount_fs+0x0/0x188) from [<c00c8c2c>] (vfs_kern_mount+0x58/0x94)
    [<c00c8bd4>] (vfs_kern_mount+0x0/0x94) from [<c00c8cc4>] (do_kern_mount+0x3c/0xd4)
    r9:de583f38 r8:c063c004 r7:de07f200 r6:00000000 r5:de07f380
    r4:00008000
    [<c00c8c88>] (do_kern_mount+0x0/0xd4) from [<c00c93a0>] (do_mount+0x644/0x738)
    r9:de583f38 r8:00000020 r7:de07f200 r6:de07f380 r5:00008000
    r4:00000000
    [<c00c8d5c>] (do_mount+0x0/0x738) from [<c00c9534>] (sys_mount+0xa0/0xd0)
    [<c00c9494>] (sys_mount+0x0/0xd0) from [<c0015180>] (ret_fast_syscall+0x0/0x30)
    r7:00000015 r6:4009d4b0 r5:bec2d844 r4:00000000
    Code: e24cb004 e24dd05c e50b0060 e59081e8 (e5981004)
    ---[ end trace 955d58451dccad75 ]---
    usb 1-1.7: new high-speed USB device number 47 using musb-hdrc
    usb 1-1.7: New USB device found, idVendor=0951, idProduct=1666
    usb 1-1.7: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    usb 1-1.7: Product: DataTraveler 3.0
    usb 1-1.7: Manufacturer: Kingston
    usb 1-1.7: SerialNumber: 60A44C3FACDBBDC1596E6E7E
    scsi44 : usb-storage 1-1.7:1.0
    scsi 44:0:0:0: Direct-Access Kingston DataTraveler 3.0 PMAP PQ: 0 ANSI: 6
    sd 44:0:0:0: [sda] 30720000 512-byte logical blocks: (15.7 GB/14.6 GiB)
    sd 44:0:0:0: [sda] Write Protect is off
    sd 44:0:0:0: [sda] Mode Sense: 2b 80 00 08
    sd 44:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
    usb 1-1.7: USB disconnect, device number 47

     

  • 0 in reply to zhiheng wei
    TI__Guru**** 167961 points

    Which kernel do you use? This forum only supports TI Linux SDK.

    have you measured the signal integrity?

  • 0 in reply to Bin Liu
    Intellectual 285 points
    At last, I just add a usb hub chip to the am3359 usb port, and the problem nearly solved. I test about 100 times, babble none.
    Why I got this idea, cos I just test, I put a usb hub to the am3359 usb port, I find the babble gone.