I vote for using a Powered USB Hub attached to the BeagleBone. I've had to do the same thing when using a separate Bluetooth and WiFi module and for just basic USB expansion. However, I found that not all Powered USB hubs worked with the BBB; at least not so a few years back.
I did have luck with the Belkin P-F4U041 though: https://www.belkin.com/us/p/P-F4U041/ Cheers, Jon On Sat, Sep 12, 2020 at 9:38 AM Ren W <[email protected]> wrote: > https://beagleboard.org/Support/FAQ > > > - *What power peripherals are required/desirable?* > - There are several ways to power a Beagle. The option exists to > feed the on-board regulators through either the 5V barrel connector > input > or USB input. When powered up over USB, the regulators are somewhat > limited > in what they can supply the system. Power over USB is sufficient as > long as > the software and system running perform some management to keep it under > the USB current limit threshold. For simplicity and maximum capability, > powering over the 5V barrel connector is typically recommended. > - The power adapter is required to provide 5V over a 5.5mm outer > diameter and 2.1mm inner diameter barrel connector (a barrel connector > length of 9.5mm is more than sufficient). The recommended supply > current is > at least 1.2A (or 6W), but at least 2A (or 10W) is recommended if you > are > going to connect up anything over the USB. The actual power consumption > will vary greatly with changes on the USB load. > > > > On Saturday, September 12, 2020 at 5:42:26 AM UTC-7 Dan and Ann Barber > wrote: > >> A further note of interest. I experienced this problem when the BBB >> itself was powered by USB connection to my laptop. However, I discovered >> that when I plugged the BBB in with the power adapter, the external USB >> drive spun up no problem. >> >> Is this expected behavior? Just curious. Thanks for the pointers. >> >> On Fri, Sep 11, 2020 at 9:47 AM Dan and Ann Barber <[email protected]> >> wrote: >> >>> Thanks for the help! I really appreciate it! I'll check out a powered hub >>> >>> On Thursday, September 10, 2020 at 10:55:10 AM UTC-7 >>> [email protected] wrote: >>> >>>> If it is drawing too much current, I suggest a powered hub between BBB >>>> and HDD >>>> >>>> The HDD is USB 2.0 which means max 500mA, but BBB can only supply 100mA >>>> https://github.com/beagleboard/beaglebone-black/wiki/System-Reference-Manual#usb1-host-port >>>> >>>> The format is Microsoft NTFS, which Linux cannot repair >>>> >>>> On Thursday, 10 September 2020 at 17:59:10 UTC+1 [email protected] >>>> wrote: >>>> >>>>> I have a WD 2TB external USB drive. It mounts fine on my linux laptop. >>>>> When I plug it into the beagleboneblack, it times out. Any help would be >>>>> appreciated! >>>>> >>>>> lsusb finds the device: >>>>> Bus 001 Device 003: ID 1058:2626 Western Digital Technologies, Inc. >>>>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub >>>>> >>>>> dmesg: >>>>> [ 3965.568158] musb-hdrc musb-hdrc.1: VBUS_ERROR in a_wait_bcon (89, >>>>> <AValid), retry #1, port1 00000104 >>>>> [ 3966.776484] usb 1-1: new high-speed USB device number 3 using >>>>> musb-hdrc >>>>> [ 3966.977419] usb 1-1: New USB device found, idVendor=1058, >>>>> idProduct=2626, bcdDevice=10.28 >>>>> [ 3966.977438] usb 1-1: New USB device strings: Mfr=1, Product=2, >>>>> SerialNumber=3 >>>>> [ 3966.977446] usb 1-1: Product: My Passport 2626 >>>>> [ 3966.977454] usb 1-1: Manufacturer: Western Digital >>>>> [ 3966.977461] usb 1-1: SerialNumber: 5758573245313048344E394B >>>>> [ 3966.985267] usb-storage 1-1:1.0: USB Mass Storage device detected >>>>> [ 3967.008783] scsi host0: usb-storage 1-1:1.0 >>>>> [ 3968.041574] scsi 0:0:0:0: Direct-Access WD My Passport >>>>> 2626 1028 PQ: 0 ANSI: 6 >>>>> [ 3968.042213] scsi 0:0:0:1: Enclosure WD SES >>>>> Device 1028 PQ: 0 ANSI: 6 >>>>> [ 3968.055140] sd 0:0:0:0: Attached scsi generic sg0 type 0 >>>>> [ 3968.061239] scsi 0:0:0:1: Attached scsi generic sg1 type 13 >>>>> [ 3968.063025] sd 0:0:0:0: [sda] Spinning up disk... >>>>> [ 3969.096578] ...not responding... >>>>> >>>>> >>>>> The BBB specs: >>>>> >>>>> System: Host: DataIntegrity-Secondary Kernel: 4.19.94-ti-r42 armv7l >>>>> bits: 32 compiler: gcc v: 8.3.0 Console: tty 1 dm: N/A >>>>> Distro: Debian GNU/Linux 10 (buster) >>>>> Machine: Type: ARM Device System: TI AM335x BeagleBone Black >>>>> details: Generic AM33XX rev: N/A serial: 1516BBBK13E1 >>>>> Memory: RAM: total: 483.4 MiB used: 128.3 MiB (26.5%) >>>>> RAM Report: unknown-error: dmidecode was unable to generate >>>>> data >>>>> PCI Slots: ARM: No ARM data found for this feature. >>>>> CPU: Topology: Single Core model: ARMv7 v7l variant: cortex-a8 >>>>> bits: 32 type: UP arch: v7l family: 7 model-id: 3 >>>>> stepping: 2 microcode: N/A bogomips: 995 >>>>> Speed: 1000 MHz min/max: 300/1000 MHz Core speed (MHz): 1: >>>>> 1000 >>>>> Features: edsp fastmult half neon thumb thumbee tls vfp >>>>> vfpd32 vfpv3 >>>>> Vulnerabilities: No CPU vulnerability/bugs data available. >>>>> Graphics: Message: No ARM data found for this feature. >>>>> Display: tty server: N/A driver: tty: 197x45 >>>>> Message: Advanced graphics data unavailable in console for >>>>> root. >>>>> Audio: Device-1: simple-audio-card driver: asoc_simple_card bus >>>>> ID: N/A chip ID: simple-audio-card:sound >>>>> Sound Server: ALSA v: k4.19.94-ti-r42 >>>>> Network: Message: No ARM data found for this feature. >>>>> IF-ID-1: can0 state: down mac: N/A >>>>> IF-ID-2: can1 state: down mac: N/A >>>>> IF-ID-3: eth0 state: up speed: 100 Mbps duplex: full mac: >>>>> 80:30:dc:53:f6:f6 >>>>> IP v4: 192.168.1.212/24 scope: global broadcast: >>>>> 192.168.1.255 >>>>> IP v6: 2600:1700:6d52:b1f0:8230:dcff:fe53:f6f6/64 type: >>>>> dynamic mngtmpaddr scope: global >>>>> IP v6: 2600:1700:6d52:b1f0::31/64 scope: global >>>>> IP v6: fe80::8230:dcff:fe53:f6f6/64 scope: link >>>>> IF-ID-4: usb0 state: up speed: N/A duplex: N/A mac: >>>>> 80:30:dc:53:f6:f8 >>>>> IP v4: 192.168.7.2/24 scope: global broadcast: >>>>> 192.168.7.255 >>>>> IP v6: fe80::8230:dcff:fe53:f6f8/64 scope: link >>>>> IF-ID-5: usb1 state: up speed: N/A duplex: N/A mac: >>>>> 80:30:dc:53:f6:fc >>>>> IP v4: 192.168.6.2/24 scope: global broadcast: >>>>> 192.168.6.255 >>>>> IP v6: fe80::8230:dcff:fe53:f6fc/64 scope: link >>>>> WAN IP: No WAN IP data found. Connected to the web? SSL >>>>> issues? >>>>> Drives: Local Storage: total: 3.56 GiB used: 2.34 GiB (65.6%) >>>>> ID-1: /dev/mmcblk1 model: S10004 size: 3.56 GiB block size: >>>>> physical: 512 B logical: 512 B serial: 0x7ae2584c >>>>> rev: 0x6 scheme: MBR >>>>> Message: No Optical or Floppy data was found. >>>>> RAID: Message: No RAID data was found. >>>>> Partition: ID-1: / raw size: 3.56 GiB size: 3.44 GiB (96.67%) used: >>>>> 2.34 GiB (67.9%) fs: ext4 block size: 4096 B >>>>> dev: /dev/mmcblk1p1 label: rootfs uuid: >>>>> 39168434-dd05-449f-aa8a-c455aec0e138 >>>>> Unmounted: Message: No unmounted partitions found. >>>>> USB: Hub: 1-0:1 info: Full speed (or root) Hub ports: 1 rev: 2.0 >>>>> speed: 480 Mb/s chip ID: 1d6b:0002 >>>>> Sensors: Message: No sensors data was found. Is sensors configured? >>>>> Repos: Active apt repos in: /etc/apt/sources.list >>>>> 1: deb http://deb.debian.org/debian buster main contrib >>>>> non-free >>>>> 2: deb http://deb.debian.org/debian buster-updates main >>>>> contrib non-free >>>>> 3: deb http://deb.debian.org/debian-security >>>>> buster/updates main contrib non-free >>>>> 4: deb [arch=armhf] http://repos.rcn-ee.com/debian/ buster >>>>> main >>>>> Active apt repos in: >>>>> /etc/apt/sources.list.d/plexmediaserver.list >>>>> 1: deb https://downloads.plex.tv/repo/deb public main >>>>> Processes: CPU top: 5 >>>>> 1: cpu: 1.6% command: -bash pid: 2205 mem: 3.02 MiB (0.6%) >>>>> 2: cpu: 1.5% command: [kworker/0:1h-mmc_complete] pid: 2210 >>>>> mem: 0.00 MiB (0.0%) >>>>> 3: cpu: 1.4% command: plex pid: 2016 mem: 30.9 MiB (6.3%) >>>>> 4: cpu: 1.0% command: sshd: pid: 2201 mem: 5.23 MiB (1.0%) >>>>> 5: cpu: 0.5% command: plex pid: 1863 mem: 40.9 MiB (8.4%) >>>>> Memory top: 5 >>>>> 1: mem: 40.9 MiB (8.4%) command: plex pid: 1863 cpu: 0.5% >>>>> 2: mem: 37.5 MiB (7.7%) command: nodejs pid: 668 cpu: 0.3% >>>>> 3: mem: 30.9 MiB (6.3%) command: plex pid: 2016 cpu: 1.4% >>>>> 4: mem: 12.0 MiB (2.4%) command: plex pid: 2059 cpu: 0.0% >>>>> 5: mem: 6.58 MiB (1.3%) command: init pid: 1 cpu: 0.1% >>>>> Info: Processes: 87 Uptime: 1h 05m Init: systemd v: 241 runlevel: >>>>> 5 Compilers: gcc: 8.3.0 alt: 8 Shell: bash v: 5.0.3 >>>>> running in: tty 1 (SSH) inxi: 3.0.32 >>>>> >>>>> >>>>> -- >>> For more options, visit http://beagleboard.org/discuss >>> --- >>> >> You received this message because you are subscribed to a topic in the >>> Google Groups "BeagleBoard" group. >>> To unsubscribe from this topic, visit >>> https://groups.google.com/d/topic/beagleboard/-efoh8y4Fh4/unsubscribe. >>> To unsubscribe from this group and all its topics, send an email to >>> [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/beagleboard/b6674a99-495c-471c-8e24-13720d004f36n%40googlegroups.com >>> <https://groups.google.com/d/msgid/beagleboard/b6674a99-495c-471c-8e24-13720d004f36n%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/beagleboard/7754f8b3-9635-4314-b066-ba4cd90116a5n%40googlegroups.com > <https://groups.google.com/d/msgid/beagleboard/7754f8b3-9635-4314-b066-ba4cd90116a5n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAG99bkp7G5nhYYs3vPMbK%2BTOA9X7Vq3KFCDzv0cqe6s3ZgvG2g%40mail.gmail.com.
