[beagleboard] Re: musb-hdrc musb-hdrc.1.auto: VBUS_ERROR in a_wait_vrise (88, <AValid), retry #3,d

[Riko]

Beaglebone Black


On 23/10/17 12:39, Robert Nelson wrote:



On Oct 22, 2017 10:52 PM, "Riko" > wrote:


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

Probably not.

Which board?

Regards,


--

*/*
Sent By
Ubuntu Linux 16.04 LTS
Kernel 4.4.0-92-generic
Kind Regards,
Riko Ho
==
谢谢从何金汉
*/*


--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/f244f7c8-23e3-ea2d-9096-6c10826b3285%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: musb-hdrc musb-hdrc.1.auto: VBUS_ERROR in a_wait_vrise (88, <AValid), retry #3,d

[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


On 23/10/17 12:39, Robert Nelson wrote:



On Oct 22, 2017 10:52 PM, "Riko" > wrote:


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

Probably not.

Which board?

Regards,


--

*/*
Sent By
Ubuntu Linux 16.04 LTS
Kernel 4.4.0-92-generic
Kind Regards,
Riko Ho
==
谢谢从何金汉
*/*


--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/080cd4e6-10ab-421d-5418-0fc9a097f386%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: musb-hdrc musb-hdrc.1.auto: VBUS_ERROR in a_wait_vrise (88, <AValid), retry #3,d

[Robert Nelson]

On Oct 22, 2017 10:52 PM, "Riko"  wrote:

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

Probably not.

Which board?

Regards,

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYg-OrJzNMOANyBaNpRixpj6yxbYRemByV2tE9GRv-Zffw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: musb-hdrc musb-hdrc.1.auto: VBUS_ERROR in a_wait_vrise (88, <AValid), retry #3,d

[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


On 23/10/17 11:44, Robert Nelson wrote:

On Sun, Oct 22, 2017 at 10:11 PM, Riko  wrote:

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.

So you have your own image, it was working, but not anymore..

First step, revert something you changed..

Regards,



--

*/*
Sent By
Ubuntu Linux 16.04 LTS
Kernel 4.4.0-92-generic
Kind Regards,
Riko Ho
==
谢谢从何金汉
*/*


--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/37bda6aa-e99e-df0e-4339-b2490582a9eb%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: musb-hdrc musb-hdrc.1.auto: VBUS_ERROR in a_wait_vrise (88, <AValid), retry #3,d

[Robert Nelson]

On Sun, Oct 22, 2017 at 10:11 PM, Riko  wrote:
> 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.

So you have your own image, it was working, but not anymore..

First step, revert something you changed..

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYhVmjaKZmdTpLtam9J78hSGzWyH-TDKuZd9yLSuNsPqcw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: musb-hdrc musb-hdrc.1.auto: VBUS_ERROR in a_wait_vrise (88, <AValid), retry #3,d

[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


On 23/10/17 09:05, Robert Nelson wrote:

sudo /opt/scripts/tools/version.sh


--

*/*
Sent By
Ubuntu Linux 16.04 LTS
Kernel 4.4.0-92-generic
Kind Regards,
Riko Ho
==
谢谢从何金汉
*/*


--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/89cf45cf-f903-0737-22a3-00e1ea069d9f%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: musb-hdrc musb-hdrc.1.auto: VBUS_ERROR in a_wait_vrise (88, <AValid), retry #3,d

[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 4806.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/4740.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 4831.rng: Random Number Generator ver. 20
musb-hdrc musb-hdrc.1.auto: VBUS_ERROR in a_wait_vrise (88,  wrote:

Dear Beagleboard Member,

I had this error so many times,

musb-hdrc musb-hdrc.1.auto: VBUS_ERROR in a_wait_vrise (88, 

[beagleboard] Re: PocketBeagle cape KiCad template?

[Daniel Kulp]

This is perfect.   Thanks!
Dan


On Sunday, October 22, 2017 at 9:08:50 AM UTC-4, mwell...@gmail.com wrote:
>
> https://github.com/mwelling/pocketbeagle-cape-template
>
> On Friday, October 20, 2017 at 11:29:49 AM UTC-5, Daniel Kulp wrote:
>>
>>
>> Has anyone started on (or has completed) a KiCad template for a 
>> PocketBeagle cape?I used the BeagleBone Black template from 
>> https://github.com/KiCad/kicad-library/tree/master/template as a 
>> starting point for a cape previously and it worked great.   Was hoping 
>> someone has done something similar for the PocketBeagle. 
>>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/4d399ffe-59ea-4849-bd1e-46b3ced15568%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: musb-hdrc musb-hdrc.1.auto: VBUS_ERROR in a_wait_vrise (88, <AValid), retry #3,d

[Robert Nelson]

On Sun, Oct 22, 2017 at 7:03 PM, Riko  wrote:
> Dear Beagleboard Member,
>
> I had this error so many times,
>
> musb-hdrc musb-hdrc.1.auto: VBUS_ERROR in a_wait_vrise (88,  #3,d
>
> Is there anyway fixing it ?

Sorry, not enough info, please share:

sudo /opt/scripts/tools/version.sh

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYhE1nuoL0Y1n70TYwh4B4T%2Bzf5FnntkHgSbpp-%2BveS95g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] 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, 

[beagleboard] Access to eMMC partition from SD with Debian

[Claudio La Rosa]

Hi to all,
 
I would use all IO pins on my BeagleBone Green card.

For this I boot from a SD card a Debian Linux distribution.
 
Now I should have access to eMMC memory and edit the /boot/uEnv.txt file.

I do:
mkdir /old
mount /dev/mmcblk0p1 /old

But now, in /old I find a **copy** of the SD partition and *not* the eMMC 
partition!
How can I fix the problem?

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/7d6f6f26-b5e4-40be-888e-25f157cce072%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Pocket Beagle breaks python-smbus

[Graham]

Please disregard...
I had a strange hardware grounding problem that allowed "i2cdetect" to see 
the part, but could not communicate with the part.
I2C working as expected on the PocketBeagle, now.

--- Graham

==

On Sunday, October 22, 2017 at 9:00:57 AM UTC-5, Graham wrote:
>
> I am trying to run some Python control of I2C devices on the Pocket Beagle 
> (PB)
> that already run on the BBB (Rev C).
>
> So, I set up the following comparison:
>
> 
>
> Load fresh "bone-debian-9.2-iot-armhf-2017-10-10-4gb.img" on the BBB Rev.C
>
> Linux beaglebone 4.4.91-ti-r133 #1 SMP Tue Oct 10 05:18:08 UTC 2017 armv7l 
> GNU/Linux
>
> sudo apt update
> sudo apt install python-smbus python3-smbus
>
> i2cdetect -y -r 2   # reveals target part at bus 2, addr = 0x18
>
> python2
> >>> import smbus
> >>> b = smbus.SMBus(2)
> >>> print b.read_word_data(0x18,0x06)
> 21504 
> # expected result (Manufacturer ID for MPC9808 temp sensor)
>
> python3
> >>> import smbus
> >>> b = smbus.SMBus(2)
> >>> print (b.read_word_data(0x18,0x06))
> 21504
> # expected result (Manufacturer ID for MPC9808 temp sensor)
>
> 
>
> Load fresh "bone-debian-9.2-iot-armhf-2017-10-15-4gb.img" on the PB.
>
> Linux beaglebone 4.4.91-ti-r133 #1 SMP Tue Oct 10 05:18:08 UTC 2017 armv7l 
> GNU/Linux
>
> i2cdetect -y -r 2   # reveals target part at bus 2, addr = 0x18
>
> sudo apt update
> sudo apt install python-smbus python3-smbus
>
> python
> >>> import smbus
> >>> b = smbus.SMBus(2)
> >>> print(b.read_word_data(0x18,0x06))
> Traceback (most recent call last):
>   File "", line 1, in 
> IOError: [Errno 121] Remote I/O error
>
>
> python3
> >>> import smbus
> >>> b = smbus.SMBus(2)
> >>> print(b.read_word_data(0x18,0x06))
> Traceback (most recent call last):
>   File "", line 1, in 
> OSError: [Errno 121] Remote I/O error
>
> The only thing unique about this PB is that I am using a USB-2 to Ethernet 
> interface for SSH access on USB1 port. Driver is already included in the 
> kernel/img.
> Should not have any impact on I2C operation. I2C is not used by the 
> Ethernet, just USB.
> 
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/dc0b1677-8563-4dca-be64-7c11c1d866c1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Beaglebone black SYS_5V giving 3V

[evilwulfie]

Either your on the wrong pin or its broke bad


On 10/22/2017 3:51 AM, jono...@gmail.com wrote:
>
> I have the beaglebone black connected to the PC via usb and I am
> trying to power an Ultrasonic sensor via the SYS_5V but i am only
> getting 3.1V from this.
> any possible reasons for this?
> -- 
> 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+unsubscr...@googlegroups.com
> .
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/b86602c8-94f0-4ca4-b836-0c551800dc41%40googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/a94bcdee-4053-4c36-4cec-271057bbcc07%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Pocket Beagle breaks python-smbus

[Graham]

I am trying to run some Python control of I2C devices on the Pocket Beagle 
(PB)
that already run on the BBB (Rev C).

So, I set up the following comparison:



Load fresh "bone-debian-9.2-iot-armhf-2017-10-10-4gb.img" on the BBB Rev.C

Linux beaglebone 4.4.91-ti-r133 #1 SMP Tue Oct 10 05:18:08 UTC 2017 armv7l 
GNU/Linux

sudo apt update
sudo apt install python-smbus python3-smbus

i2cdetect -y -r 2   # reveals target part at bus 2, addr = 0x18

python2
>>> import smbus
>>> b = smbus.SMBus(2)
>>> print b.read_word_data(0x18,0x06)
21504 
# expected result (Manufacturer ID for MPC9808 temp sensor)

python3
>>> import smbus
>>> b = smbus.SMBus(2)
>>> print (b.read_word_data(0x18,0x06))
21504
# expected result (Manufacturer ID for MPC9808 temp sensor)



Load fresh "bone-debian-9.2-iot-armhf-2017-10-15-4gb.img" on the PB.

Linux beaglebone 4.4.91-ti-r133 #1 SMP Tue Oct 10 05:18:08 UTC 2017 armv7l 
GNU/Linux

i2cdetect -y -r 2   # reveals target part at bus 2, addr = 0x18

sudo apt update
sudo apt install python-smbus python3-smbus

python
>>> import smbus
>>> b = smbus.SMBus(2)
>>> print(b.read_word_data(0x18,0x06))
Traceback (most recent call last):
  File "", line 1, in 
IOError: [Errno 121] Remote I/O error


python3
>>> import smbus
>>> b = smbus.SMBus(2)
>>> print(b.read_word_data(0x18,0x06))
Traceback (most recent call last):
  File "", line 1, in 
OSError: [Errno 121] Remote I/O error

The only thing unique about this PB is that I am using a USB-2 to Ethernet 
interface for SSH access on USB1 port. Driver is already included in the 
kernel/img.
Should not have any impact on I2C operation. I2C is not used by the 
Ethernet, just USB.


-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/1a7085c5-4d8b-4903-9dbc-386fc0744163%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Beaglebone black SYS_5V giving 3V

[jonop44]

I have the beaglebone black connected to the PC via usb and I am trying to 
power an Ultrasonic sensor via the SYS_5V but i am only getting 3.1V from 
this.
any possible reasons for this?

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/b86602c8-94f0-4ca4-b836-0c551800dc41%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: PocketBeagle cape KiCad template?

[mwelling79]

https://github.com/mwelling/pocketbeagle-cape-template

On Friday, October 20, 2017 at 11:29:49 AM UTC-5, Daniel Kulp wrote:
>
>
> Has anyone started on (or has completed) a KiCad template for a 
> PocketBeagle cape?I used the BeagleBone Black template from 
> https://github.com/KiCad/kicad-library/tree/master/template as a starting 
> point for a cape previously and it worked great.   Was hoping someone has 
> done something similar for the PocketBeagle. 
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/c9f6594b-5f49-4666-8fc7-767f02fe9bb0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Powering 5V devices from Beaglebone

[Jonathan Prinsloo]

Hi 

I am trying to power an HY - SRF05 ultrasonic sensor from my beaglebone. 
the Beaglebone is connected to PC via USB. 
the problem I have is the SYS_5V pin is only giving me 3.1V
Any ideas or possible causes of this proble?

Thanks

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/4f8b1d95-40d9-4212-8225-4a0c6461f290%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Restoring MLO and uboot to eMMC and microSD

['Luther Goh Lu Feng' via BeagleBoard]

Bump
On Thursday, October 19, 2017 at 3:03:12 PM UTC+8, Luther Goh Lu Feng wrote:
>
> I have a BBB which has the eMMC flashed from the microSD card using the 
> flasher script. Therefore, the MLO and the u-boot should be idenitical.
>
> Referencing the eewiki page[1]I backed up the MLO from the eMMC and the 
> microSD:
>
> sudo dd if=/dev/mmcblk0 of=./mmcblk0_MLO count=1 seek=1 bs=128k
> sudo dd if=/dev/mmcblk1 of=./mmcblk1_MLO count=1 seek=1 bs=128k
>
> The shasums are however different:
>
> debian@beaglebone:~$ sha256sum mmcblk0_MLO
> 493f8723705c73c3383898658ce2b1855bbca219825198d2a23b115ce30a4ada  
> mmcblk0_MLO
> debian@beaglebone:~$ sha256sum mmcblk1_MLO
> 51d7b68ec8eac56f6d04371c77885332e9eedc7c5434350750ba58f51e86fd56  
> mmcblk1_MLO
>
> Am I backing up the MLO correctly?
>
> [1] 
> https://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-SetupmicroSDcard
>
> On Thursday, October 19, 2017 at 10:35:11 AM UTC+8, Luther Goh Lu Feng 
> wrote:
>>
>> From https://groups.google.com/d/msg/beagleboard/4HTJt7J2M8w/3qdig-7hBQAJ
>>
>> >> Next question. If I flash the eMMC using the microSD card debian 
>> flasher 
>> >> script, and then dd out 1MB from the eMMC and microSD, do I expect 
>> both to 
>> >> have the same shasum? I expect yes, since they came from the same 
>> debian 
>> >> image, but unless I made a mistake or there are some false assumptions 
>> on my 
>> >> part, I seemed to be getting different checksums 
>>
>> > No... different drive geometries.. 
>>
>> Just to clarify, does the above still hold true? If yes, does it mean 
>> that different drive geometries means that the 1MB of each storage medium 
>> contains other drive specific stuff, together with the MLO and u-boot, and 
>> therefore results in differences in the 1MB content for each drive?
>>
>>
>> --Luther
>> On Thursday, October 19, 2017 at 3:45:14 AM UTC+8, RobertCNelson wrote:
>>>
>>> On Wed, Oct 18, 2017 at 2:41 PM, 'Luther Goh Lu Feng' via BeagleBoard 
>>>  wrote: 
>>> > Given that the eMMC and microSD has different drive geometries[1], 
>>> what is 
>>> > the correct way of backing up and restoring the MLO and u-boot from 
>>> one 
>>> > medium to another? eg from eMMC to microSD or from microSD to eMMC. 
>>>
>>> That's incorrect, the drive geometries doesn't affect MLO/u-boot.img 
>>> which are always in the same location on either eMMC/microSD. 
>>>
>>> you can use 'dd' to extract them or just grab the "backup" versions 
>>> found under: /opt/backup/uboot/ 
>>>
>>> Regards, 
>>>
>>> -- 
>>> Robert Nelson 
>>> https://rcn-ee.com/ 
>>>
>>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/4be40043-b5cd-426b-8303-a43f8e375807%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.