musb-hdrc musb-hdrc.1.auto: VBUS_ERROR in a_wait_vrise (88, <AValid), retry #3,d
Riko
Dear Beagleboard Member,
I had this error so many times,
musb-hdrc musb-hdrc.1.auto: VBUS_ERROR in a_wait_vrise (88,
<AValid), retry #3,d
--
/*****
Sent By
Ubuntu Linux 16.04 LTS
Kernel 4.4.0-92-generic
Kind Regards,
Riko Ho
==========
谢谢从何金汉
*****/
Robert Nelson
> Dear Beagleboard Member,
>
> I had this error so many times,
>
> musb-hdrc musb-hdrc.1.auto: VBUS_ERROR in a_wait_vrise (88, <AValid), retry
> #3,d
>
> Is there anyway fixing it ?
sudo /opt/scripts/tools/version.sh
Regards,
--
Robert Nelson
https://rcn-ee.com/
Riko
Dear Beagleboard Members,
I'll find out that version.sh, it can't to command shell yet :
===============
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI)
Driver
ehci-omap: OMAP-EHCI Host Controller
driver
usbcore: registered new interface driver
usb-storage
47401300.usb-phy supply vcc not found, using dummy
regulator
musb-hdrc musb-hdrc.0.auto: Failed to request
rx1.
47401b00.usb-phy supply vcc not found, using dummy
regulator
musb-hdrc musb-hdrc.1.auto: Failed to request
rx1.
mousedev: PS/2 mouse device common for all
mice
omap_rtc 44e3e000.rtc: rtc core: registered 44e3e000.rtc as
rtc0
i2c /dev entries
driver
omap_wdt: OMAP Watchdog Timer Rev 0x01: initial timeout 60
sec
omap_hsmmc 48060000.mmc: Got CD
GPIO
mmc0: host does not support reading read-only switch, assuming
write-enable
mmc0: Problem switching card into high-speed
mode!
usbcore: registered new interface driver
usbhid
usbhid: USB HID core
driver
oprofile: using
arm/armv7
u32
classifier
Actions
configured
NET: Registered protocol family
10
Segment Routing with
IPv6
sit: IPv6, IPv4 and MPLS over IPv4 tunneling
driver
NET: Registered protocol family
17
Key type dns_resolver
registered
omap_voltage_late_init: Voltage driver support not
added
ThumbEE CPU extension
supported.
Btrfs loaded,
crc32c=crc32c-generic
Key type encrypted
registered
mmc0: new SDHC card at address
0001
mmcblk0: mmc0:0001 SD16G 14.6
GiB
mmcblk0: p1
p2
tps65217 0-0024: TPS65217 ID 0xe version
1.2
mmc1: new high speed MMC card at address
0001
mmcblk1: mmc1:0001 S10004 3.56
GiB
mmcblk1boot0: mmc1:0001 S10004 partition 1 4.00
MiB
mmcblk1boot1: mmc1:0001 S10004 partition 2 4.00
MiB
mmcblk1: p1
p2
tda998x 0-0070: found
TDA19988
tilcdc 4830e000.lcdc: bound 0-0070 (ops
tda998x_ops)
[drm] Supports vblank timestamp caching Rev 2
(21.10.2013).
[drm] No driver support for vblank timestamp
query.
[drm] Cannot find any crtc or sizes - going
1024x768
Console: switching to colour frame buffer device
128x48
tilcdc 4830e000.lcdc: fb0: frame buffer
device
omap_i2c 44e0b000.i2c: bus 0 rev0.11 at 400
kHz
omap_i2c 4819c000.i2c: bus 2 rev0.11 at 100
kHz
musb-hdrc musb-hdrc.1.auto: MUSB HDRC host
driver
musb-hdrc musb-hdrc.1.auto: new USB bus registered, assigned bus
number 1
hub 1-0:1.0: USB hub
found
hub 1-0:1.0: 1 port
detected
console [netcon0]
enabled
netconsole: network logging
started
omap_rtc 44e3e000.rtc: setting system clock to 2000-01-01 00:00:01
UTC (9466848)
OF: Duplicate name in testcase-data, renamed to
"duplicate-name#1"
### dt-test ### start of unittest - you will see error
messages
OF: /testcase-data/phandle-tests/consumer-a: could not get
#phandle-cells-missi1
OF: /testcase-data/phandle-tests/consumer-a: could not get
#phandle-cells-missi1
OF: /testcase-data/phandle-tests/consumer-a: could not find
phandle
OF: /testcase-data/phandle-tests/consumer-a: could not find
phandle
OF: /testcase-data/phandle-tests/consumer-a: arguments longer than
property
OF: /testcase-data/phandle-tests/consumer-a: arguments longer than
property
irq: no irq domain found for /testcase-data/interrupts/intc0
!
OF: overlay: overlay_is_topmost: #5 clashes #6
@/testcase-data/overlay-node/tes8
OF: overlay: overlay #5 is not
topmost
### dt-test ### end of unittest - 148 passed, 0
failed
EXT4-fs (mmcblk0p2): recovery
complete
EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode.
Opts: (null)
VFS: Mounted root (ext4 filesystem) on device
179:2.
devtmpfs:
mounted
Freeing unused kernel memory:
1024K
INIT: version 2.88
booting
usb 1-1: new full-speed USB device number 2 using
musb-hdrc
hub 1-1:1.0: USB hub
found
hub 1-1:1.0: 4 ports
detected
Starting
udev
usb 1-1.4: new full-speed USB device number 3 using
musb-hdrc
input: GeneralPlus USB Audio Device as
/devices/platform/ocp/47400000.usb/474010
hid-generic 0003:1B3F:2008.0001: input: USB HID v2.01 Device
[GeneralPlus USB A3
udev: Not using udev cache because of changes detected in the
following files:
udev: /proc/version /proc/cmdline
/proc/devices
udev: lib/udev/rules.d/*
etc/udev/rules.d/*
udev: The udev cache will be regenerated. To identify the detected
changes,
udev: compare the cached sysconf at
/etc/udev/cache.data
udev: against the current sysconf at
/dev/shm/udev.cache
udevd[124]: starting version
3.2.1
udevd[125]: starting
eudev-3.2.1
omap_rng 48310000.rng: Random Number Generator ver.
20
musb-hdrc musb-hdrc.1.auto: VBUS_ERROR in a_wait_vrise (88,
<AValid), retry #3,f
usb 1-1.4: 1:1: cannot set freq 48000 to ep
0x5
usb 1-1.4: 2:1: cannot set freq 48000 to ep
0x86
udevd[125]: worker [130]
/devices/platform/ocp/47400000.usb/47401c00.usb/musb-he
====================
Riko
Dear BeagleBoard Members,
root@beaglebone:~# sudo
/opt/scripts/tools/version.sh
-sh: sudo: command not
found
root@beaglebone:~#
I'm not using image from beaglebone website, it's my own image.
It was working properly, but not now.
Thanks
sudo /opt/scripts/tools/version.sh
Robert Nelson
> Dear BeagleBoard Members,
>
> root@beaglebone:~# sudo /opt/scripts/tools/version.sh
> -sh: sudo: command not found
> root@beaglebone:~#
>
>
> I'm not using image from beaglebone website, it's my own image.
>
> It was working properly, but not now.
First step, revert something you changed..
Riko
It's working until root shell but, always miss USB drive initialization.
I got no idea why, looks like there's a voltage drop.
Is it ok, if I remove FB8 from the board ? It's connected to T18
on the chip
Robert Nelson
It's working until root shell but, always miss USB drive initialization.
I got no idea why, looks like there's a voltage drop.
Is it ok, if I remove FB8 from the board ? It's connected to T18 on the chip
Riko
Beaglebone Black
Riko
Up and down,
usb 1-1.1: new full-speed USB device number 19 using musb-hdrc
usb 1-1.1: not running at top speed; connect to a high speed hub
usb-storage 1-1.1:1.0: USB Mass Storage device detected
scsi host1: usb-storage 1-1.1:1.0
scsi 1:0:0:0: Direct-Access 2.04 PQ:
0 ANSI: 0 CCS
sd 1:0:0:0: [sdb] 1015805 512-byte logical blocks: (520 MB/496
MiB)
sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] No Caching mode page found
sd 1:0:0:0: [sdb] Assuming drive cache: write through
sdb:
sd 1:0:0:0: [sdb] Attached SCSI removable disk
usb 1-1: USB disconnect, device number 17
usb 1-1.1: USB disconnect, device number 19
scsi 1:0:0:0: rejecting I/O to offline device
scsi 1:0:0:0: [sdb] killing request
scsi 1:0:0:0: [sdb] UNKNOWN(0x2003) Result: hostbyte=0x01
driverbyte=0x00
scsi 1:0:0:0: [sdb] CDB: opcode=0x28 28 00 00 00 03 28 00 00 d8 00
blk_update_request: I/O error, dev sdb, sector 808
Buffer I/O error on dev sdb, logical block 808, async page read
Buffer I/O error on dev sdb, logical block 809, async page read
Buffer I/O error on dev sdb, logical block 810, async page read
usb 1-1.4: USB disconnect, device number 18
Buffer I/O error on dev sdb, logical block 811, async page read
Buffer I/O error on dev sdb, logical block 812, async page read
Buffer I/O error on dev sdb, logical block 813, async page read
Buffer I/O error on dev sdb, logical block 814, async page read
Buffer I/O error on dev sdb, logical block 815, async page read
Buffer I/O error on dev sdb, logical block 512, async page read
Buffer I/O error on dev sdb, logical block 513, async page read
udevd[1036]: inotify_add_watch(6, /dev/sdb, 10) failed: No such
file or directory
usb 1-1: new full-speed USB device number 20 using musb-hdrc
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 4 ports detected
usb 1-1.4: new full-speed USB device number 21 using musb-hdrc
Riko
Dear BeagleBoard Member,
Looks like the board denies USB Hub,
====
root@beaglebone:~# udevd[125]: worker [133]
/devices/platform/ocp/47400000.usb/t
udevd[125]: seq 1103
'/devices/platform/ocp/47400000.usb/47401c00.usb/musb-hdrcd
udevd[125]: worker [130]
/devices/platform/ocp/47400000.usb/47401c00.usb/musb-ht
udevd[125]: seq 1109
'/devices/platform/ocp/47400000.usb/47401c00.usb/musb-hdrcd
udevd[125]: worker [130] terminated by signal 9 (Killed)
udevd[125]: worker [130] failed while handling
'/devices/platform/ocp/47400000.'
usb 1-1.4: 5:0: cannot get min/max values for control 2 (id 5)
usbcore: registered new interface driver snd-usb-audio
udevd[125]: worker [133] terminated by signal 9 (Killed)
udevd[125]: worker [133] failed while handling
'/devices/platform/ocp/47400000.'
=====
The hub is ok when I put it on my computer ?
Any clues ?
Riko
Dear BeagleBoard Member,
I got this message :
usb 1-1: device descriptor read/64, error -110
usb 1-1: new high-speed USB device number 6 using musb-hdrc
usb 1-1: device descriptor read/64, error -110
usb 1-1: device descriptor read/64, error -110
usb 1-1: new high-speed USB device number 7 using musb-hdrc
usb 1-1: device not accepting address 7, error -110
usb 1-1: new high-speed USB device number 8 using musb-hdrc
usb 1-1: device not accepting address 8, error -110
usb usb1-port1: unable to enumerate USB device
usb usb1-port1: over-current condition
I'm using 4 ports USB Hub, does it matter ?
Regards,
Gerald Coley
Sure, but I don't think making the resistence smaller will stop whatever you are plugging in from pulling too much current. Current limit is controlled by the switch itself.
How much current does the device you are plugging in require?
Gerald
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups "BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
beagleboard...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/beagleboard/ee80455a-f749-fbda-3c0e-49905299d92d%40gmail.com.
For more options, visit https://groups.google.com/d/optout.