Adafruit's BeagleBone IO Python Library 1.0.5

[tvan]

Hello,
I've been trying to get the Seeed Motor Bridge Cape to work with the above library. I sent the email below to the cape developer in hopes that he can help me out. It's been quite and enjoyable journey so far. I was wondering someone on your team might be able to provide some insight into my problem. Bottom line, I have two capes that are behaving in exactly the same way--not seeing the Motor Bridge Cape i2c address.

Jiankai,

I've been spending quite a bit of time trying to get the Motor Bridge Cape V 1.0 to work with my Beaglebone Black Rev C. I really enjoy making things so this isn't a complaint. However, I was wondering whether you might be able to help me figure out what could be wrong. I've purchased two of these Capes and they both behave in the same way. First I'll describe my configuration:

1. Beaglebone Black Rev C.
uname -a
Linux beaglebone 4.4.91-ti-r134 #1 SMP Tue Oct 24 00:58:12 UTC 2017 armv7l GNU/Linux
2. Memory Address Assignments for i2c:
root@beaglebone:/sys/bus/i2c/devices# ls -l i2c-*
lrwxrwxrwx 1 root root 0 Nov 4 04:10 i2c-0 -> ../../../devices/platform/ocp/44e0b000.i2c/i2c-0
lrwxrwxrwx 1 root root 0 Nov 4 04:10 i2c-1 -> ../../../devices/platform/ocp/4802a000.i2c/i2c-1
lrwxrwxrwx 1 root root 0 Nov 4 04:10 i2c-2 -> ../../../devices/platform/ocp/4819c000.i2c/i2c-2
3. WiFi -- I'm running a Panda Wireless Model Number PAU09 Wifi adapter.
4. Power--I've used several different power connections including BBB USB, BBB 5V connection and Motor Bridge Cape 12V battery input with no change in symptoms. With power connected, I see 14.00 VDC which is within the acceptable range for the device.

5. Initial indications after boot
root@beaglebone:~# i2cdetect -r -y 0
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- UU -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- UU -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: UU -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: UU -- -- -- -- -- -- --
root@beaglebone:~# i2cdetect -r -y 2
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- UU UU UU UU -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --

i2c-1 is not active after boot.
I've been able to activate i2c-1 with the following commands:
root@beaglebone:/var/lib/cloud9/BBG_MotorBridgeCape# config-pin P9_17 i2c
root@beaglebone:/var/lib/cloud9/BBG_MotorBridgeCape# config-pin P9_18 i2c
root@beaglebone:/var/lib/cloud9/BBG_MotorBridgeCape# i2cdetect -r -y 1
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --

I don't see the Motor Bridge Cape Address (0x4b)

When I try to run the Motor Bridge Software I get the following output:
root@beaglebone:/var/lib/cloud9/BBG_MotorBridgeCape# python MotorBridge.py
Error accessing 0x4B: Check your I2C address
Error accessing 0x4B: Check your I2C address
Error accessing 0x4B: Check your I2C address
Error accessing 0x4B: Check your I2C address
Error accessing 0x4B: Check your I2C address
Hello From MotorBridge
Error accessing 0x4B: Check your I2C address
Error accessing 0x4B: Check your I2C address
Error accessing 0x4B: Check your I2C address
Error accessing 0x4B: Check your I2C address
Error accessing 0x4B: Check your I2C address
Error accessing 0x4B: Check your I2C address
Hello From MotorBridge
Error accessing 0x4B: Check your I2C address
Error accessing 0x4B: Check your I2C address
Error accessing 0x4B: Check your I2C address
Error accessing 0x4B: Check your I2C address
Error accessing 0x4B: Check your I2C address
Error accessing 0x4B: Check your I2C address
Hello From MotorBridge
Error accessing 0x4B: Check your I2C address
Error accessing 0x4B: Check your I2C address
Error accessing 0x4B: Check your I2C address
Error accessing 0x4B: Check your I2C address
Error accessing 0x4B: Check your I2C address
Error accessing 0x4B: Check your I2C address
Hello From MotorBridge
Error accessing 0x4B: Check your I2C address
Error accessing 0x4B: Check your I2C address
Error accessing 0x4B: Check your I2C address
Error accessing 0x4B: Check your I2C address
Error accessing 0x4B: Check your I2C address
Error accessing 0x4B: Check your I2C address
Hello From MotorBridge
Error accessing 0x4B: Check your I2C address
Error accessing 0x4B: Check your I2C address
Error accessing 0x4B: Check your I2C address
Error accessing 0x4B: Check your I2C address
Error accessing 0x4B: Check your I2C address
Error accessing 0x4B: Check your I2C address
Hello From MotorBridge
Error accessing 0x4B: Check your I2C address
Error accessing 0x4B: Check your I2C address
Error accessing 0x4B: Check your I2C address
Error accessing 0x4B: Check your I2C address
Error accessing 0x4B: Check your I2C address
Error accessing 0x4B: Check your I2C address
Hello From MotorBridge

When I try to reflash the Motor Bridge Cape, I get the following:
root@beaglebone:/var/lib/cloud9/MotorBridgeCapeFirmware# make flash
./script/flasher MotorBridgeCapeFirmware.bin
/var/lib/cloud9/MotorBridgeCapeFirmware
sh: echo: I/O error
Reading data from MotorBridgeCapeFirmware.bin
Can't init. Ensure BOOT0=1, BOOT1=0, and reset device
Traceback (most recent call last):
File "./script/stm32loader.py", line 555, in <module>
bootversion = cmd.cmdGet()
File "./script/stm32loader.py", line 141, in cmdGet
if self.cmdGeneric(0x00):
File "./script/stm32loader.py", line 138, in cmdGeneric
return self._wait_for_ack(hex(cmd))
File "./script/stm32loader.py", line 89, in _wait_for_ack
raise CmdException("No response to %s" % info)
__main__.CmdException: No response to 0x0
./script/flasher: 19: ./script/flasher: [1==0]: not found
Reading data from MotorBridgeCapeFirmware.bin
Can't init. Ensure BOOT0=1, BOOT1=0, and reset device
Traceback (most recent call last):
File "./script/stm32loader.py", line 555, in <module>
bootversion = cmd.cmdGet()
File "./script/stm32loader.py", line 141, in cmdGet
if self.cmdGeneric(0x00):
File "./script/stm32loader.py", line 138, in cmdGeneric
return self._wait_for_ack(hex(cmd))
File "./script/stm32loader.py", line 89, in _wait_for_ack
raise CmdException("No response to %s" % info)
__main__.CmdException: No response to 0x0
haha

(I'm not sure what haha means :0) )
As a preliminary note to flash configuration, I'm unable to get UART 2 to work by editing /boot/uEnv.txt. I can activate it as shown below.
So I activate UART on J9 21 and 22:

root@beaglebone:/var/lib/cloud9/MotorBridgeCapeFirmware# config-pin P9_21 uart
root@beaglebone:/var/lib/cloud9/MotorBridgeCapeFirmware# config-pin P9_22 uart
root@beaglebone:/var/lib/cloud9/MotorBridgeCapeFirmware# make flash
./script/flasher MotorBridgeCapeFirmware.bin
/var/lib/cloud9/MotorBridgeCapeFirmware
sh: echo: I/O error
sh: echo: I/O error
Reading data from MotorBridgeCapeFirmware.bin
Bootloader version 0x31
Chip id 0x440, STM32F0, goood solution for BBG
Global mass erase; this may take a while
Writing 12800 bytes to start address 0x8000000
Write 256 bytes at 0x8000000
Write 256 bytes at 0x8000100
Write 256 bytes at 0x8000200
Write 256 bytes at 0x8000300
Write 256 bytes at 0x8000400
Write 256 bytes at 0x8000500
Write 256 bytes at 0x8000600
Write 256 bytes at 0x8000700
Write 256 bytes at 0x8000800
Write 256 bytes at 0x8000900
Write 256 bytes at 0x8000A00
Write 256 bytes at 0x8000B00
Write 256 bytes at 0x8000C00
Write 256 bytes at 0x8000D00
Write 256 bytes at 0x8000E00
Write 256 bytes at 0x8000F00
Write 256 bytes at 0x8001000
Write 256 bytes at 0x8001100
Write 256 bytes at 0x8001200
Write 256 bytes at 0x8001300
Write 256 bytes at 0x8001400
Write 256 bytes at 0x8001500
Write 256 bytes at 0x8001600
Write 256 bytes at 0x8001700
Write 256 bytes at 0x8001800
Write 256 bytes at 0x8001900
Write 256 bytes at 0x8001A00
Write 256 bytes at 0x8001B00
Write 256 bytes at 0x8001C00
Write 256 bytes at 0x8001D00
Write 256 bytes at 0x8001E00
Write 256 bytes at 0x8001F00
Write 256 bytes at 0x8002000
Write 256 bytes at 0x8002100
Write 256 bytes at 0x8002200
Write 256 bytes at 0x8002300
Write 256 bytes at 0x8002400
Write 256 bytes at 0x8002500
Write 256 bytes at 0x8002600
Write 256 bytes at 0x8002700
Write 256 bytes at 0x8002800
Write 256 bytes at 0x8002900
Write 256 bytes at 0x8002A00
Write 256 bytes at 0x8002B00
Write 256 bytes at 0x8002C00
Write 256 bytes at 0x8002D00
Write 256 bytes at 0x8002E00
Write 256 bytes at 0x8002F00
Write 256 bytes at 0x8003000
Write 256 bytes at 0x8003100
Read 256 bytes at 0x8000000
Read 256 bytes at 0x8000100
Read 256 bytes at 0x8000200
Read 256 bytes at 0x8000300
Read 256 bytes at 0x8000400
Read 256 bytes at 0x8000500
Read 256 bytes at 0x8000600
Read 256 bytes at 0x8000700
Read 256 bytes at 0x8000800
Read 256 bytes at 0x8000900
Read 256 bytes at 0x8000A00
Read 256 bytes at 0x8000B00
Read 256 bytes at 0x8000C00
Read 256 bytes at 0x8000D00
Read 256 bytes at 0x8000E00
Read 256 bytes at 0x8000F00
Read 256 bytes at 0x8001000
Read 256 bytes at 0x8001100
Read 256 bytes at 0x8001200
Read 256 bytes at 0x8001300
Read 256 bytes at 0x8001400
Read 256 bytes at 0x8001500
Read 256 bytes at 0x8001600
Read 256 bytes at 0x8001700
Read 256 bytes at 0x8001800
Read 256 bytes at 0x8001900
Read 256 bytes at 0x8001A00
Read 256 bytes at 0x8001B00
Read 256 bytes at 0x8001C00
Read 256 bytes at 0x8001D00
Read 256 bytes at 0x8001E00
Read 256 bytes at 0x8001F00
Read 256 bytes at 0x8002000
Read 256 bytes at 0x8002100
Read 256 bytes at 0x8002200
Read 256 bytes at 0x8002300
Read 256 bytes at 0x8002400
Read 256 bytes at 0x8002500
Read 256 bytes at 0x8002600
Read 256 bytes at 0x8002700
Read 256 bytes at 0x8002800
Read 256 bytes at 0x8002900
Read 256 bytes at 0x8002A00
Read 256 bytes at 0x8002B00
Read 256 bytes at 0x8002C00
Read 256 bytes at 0x8002D00
Read 256 bytes at 0x8002E00
Read 256 bytes at 0x8002F00
Read 256 bytes at 0x8003000
Read 256 bytes at 0x8003100
Verification OK
./script/flasher: 19: ./script/flasher: [0==0]: not found
Reading data from MotorBridgeCapeFirmware.bin
Bootloader version 0x31
Chip id 0x440, STM32F0, goood solution for BBG
Global mass erase; this may take a while
Writing 12800 bytes to start address 0x8000000
Write 256 bytes at 0x8000000
Write 256 bytes at 0x8000100
Write 256 bytes at 0x8000200
Write 256 bytes at 0x8000300
Write 256 bytes at 0x8000400
Write 256 bytes at 0x8000500
Write 256 bytes at 0x8000600
Write 256 bytes at 0x8000700
Write 256 bytes at 0x8000800
Write 256 bytes at 0x8000900
Write 256 bytes at 0x8000A00
Write 256 bytes at 0x8000B00
Write 256 bytes at 0x8000C00
Write 256 bytes at 0x8000D00
Write 256 bytes at 0x8000E00
Write 256 bytes at 0x8000F00
Write 256 bytes at 0x8001000
Write 256 bytes at 0x8001100
Write 256 bytes at 0x8001200
Write 256 bytes at 0x8001300
Write 256 bytes at 0x8001400
Write 256 bytes at 0x8001500
Write 256 bytes at 0x8001600
Write 256 bytes at 0x8001700
Write 256 bytes at 0x8001800
Write 256 bytes at 0x8001900
Write 256 bytes at 0x8001A00
Write 256 bytes at 0x8001B00
Write 256 bytes at 0x8001C00
Write 256 bytes at 0x8001D00
Write 256 bytes at 0x8001E00
Write 256 bytes at 0x8001F00
Write 256 bytes at 0x8002000
Write 256 bytes at 0x8002100
Write 256 bytes at 0x8002200
Write 256 bytes at 0x8002300
Write 256 bytes at 0x8002400
Write 256 bytes at 0x8002500
Write 256 bytes at 0x8002600
Write 256 bytes at 0x8002700
Write 256 bytes at 0x8002800
Write 256 bytes at 0x8002900
Write 256 bytes at 0x8002A00
Write 256 bytes at 0x8002B00
Write 256 bytes at 0x8002C00
Write 256 bytes at 0x8002D00
Write 256 bytes at 0x8002E00
Write 256 bytes at 0x8002F00
Write 256 bytes at 0x8003000
Write 256 bytes at 0x8003100
Read 256 bytes at 0x8000000
Read 256 bytes at 0x8000100
Read 256 bytes at 0x8000200
Read 256 bytes at 0x8000300
Read 256 bytes at 0x8000400
Read 256 bytes at 0x8000500
Read 256 bytes at 0x8000600
Read 256 bytes at 0x8000700
Read 256 bytes at 0x8000800
Read 256 bytes at 0x8000900
Read 256 bytes at 0x8000A00
Read 256 bytes at 0x8000B00
Read 256 bytes at 0x8000C00
Read 256 bytes at 0x8000D00
Read 256 bytes at 0x8000E00
Read 256 bytes at 0x8000F00
Read 256 bytes at 0x8001000
Read 256 bytes at 0x8001100
Read 256 bytes at 0x8001200
Read 256 bytes at 0x8001300
Read 256 bytes at 0x8001400
Read 256 bytes at 0x8001500
Read 256 bytes at 0x8001600
Read 256 bytes at 0x8001700
Read 256 bytes at 0x8001800
Read 256 bytes at 0x8001900
Read 256 bytes at 0x8001A00
Read 256 bytes at 0x8001B00
Read 256 bytes at 0x8001C00
Read 256 bytes at 0x8001D00
Read 256 bytes at 0x8001E00
Read 256 bytes at 0x8001F00
Read 256 bytes at 0x8002000
Read 256 bytes at 0x8002100
Read 256 bytes at 0x8002200
Read 256 bytes at 0x8002300
Read 256 bytes at 0x8002400
Read 256 bytes at 0x8002500
Read 256 bytes at 0x8002600
Read 256 bytes at 0x8002700
Read 256 bytes at 0x8002800
Read 256 bytes at 0x8002900
Read 256 bytes at 0x8002A00
Read 256 bytes at 0x8002B00
Read 256 bytes at 0x8002C00
Read 256 bytes at 0x8002D00
Read 256 bytes at 0x8002E00
Read 256 bytes at 0x8002F00
Read 256 bytes at 0x8003000
Read 256 bytes at 0x8003100
Verification OK
haha

The output looks better but I'm still getting errors:

This....
/var/lib/cloud9/MotorBridgeCapeFirmware
sh: echo: I/O error
sh: echo: I/O error

And this...
./script/flasher: 19: ./script/flasher: [0==0]: not found

I'm using Adafruit's BeagleBone IO Python Library 1.0.5

I have a Control Everything BBI2C PR19-6 REV.D Cape which allows me to connect i2c devices using a grove connector. The PRI19-6 can be strapped to operate on pins 17 and 18, 19 and 20, 21 and 22, and 22 and 23. I have been able to successfully access i2c devices using this device on both i2c 1 and 2 buss. This at least tells me that there nothing wrong with my BBB i2c buss and pins.

I noticed on your drawings (Motor Bridge Cape v1.0) what seems to be a couple of errors. On sheet 1 of 1, I believe J8 and J9 are reversed. I also noticed that pins 19 and 21 are labeled pb6 bb_i2c2_scl and pb7 bb_i2c2_sda respectively but on the second sheet 1 of 1 the corresponding pb6 and pb7 pins are labeled PB7/I2C1_SDA/USART1_RX and PB6/I2C1_SCL/USART1_TX respectively. Regardless, can we assume that J9_19 and J920 are the i2c pins used to communicate with the Motor Bridge Cape?

I've carefully read any and all postings I could find related to problems people where having with the cape.

Any help you can provide would be greatly appreciated. I've really been enjoying the experience. I find that I learn much more from failure than from success but I'd really like to get this to work so I can continue with my project.

Thanks in advance for any help you can provide.

Best regards,

Tom Van der Bloemen
Carlsbad, CA

[drewfustini]

Please paste the output of this command which will list detailed information on the system configuration of your beaglebone:
sudo /opt/scripts/tools/version.sh

I would also suggest posting this issue on the BeagleBoard.org community mailing list:
https://beagleboard.org/discuss

I don't have the Seeed Motor Bridge Cape to attempt to reproduce this issue, but someone on the mailing list might.

[drewfustini]

Also, please try scanning the I2C2 bus. I2C2 uses pins P9.19 (I2C2_SCL) and P9.20 (I2C2_SDA).
sudo i2cdetect -y -r 2

For reference, see this thread:
viewtopic.php?f=49&t=123147&p=620659&hi ... ne#p615314

[tvan]

Drew,
Thanks for the reply! The scans for i2c 2 are included in what I sent. I also enabled pins for i2c 1. I've also confirmed that the BBB works with another I2c cape. I provided uname output in the write up as well. I can run sudo /opt/scripts/tools/version.sh when I get home.

Best regards,

Tom

[tvan]

Drew,

Here's what I get when I run root@beaglebone:~# /opt/scripts/tools/version.sh

git:/opt/scripts/:[d36fe9a7be9ebfc872b10a470e904ab4c61c4516]
eeprom:[A335BNLT00C02016BBBK114F]
dogtag:[BeagleBoard.org Debian Image 2017-10-10]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2017.09-00002-g0f3f1c7907]
kernel:[4.4.91-ti-r133]
nodejs:[v6.11.4]
uboot_overlay_options:[enable_uboot_overlays=1]
uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-4-TI-00A0.dtbo]
uboot_overlay_options:[enable_uboot_cape_universal=1]
pkg:[bb-cape-overlays]:[4.4.20171009.0-0rcnee1~stretch+20171009]
pkg:[bb-wl18xx-firmware]:[1.20170829-0rcnee1~stretch+20170829]
pkg:[firmware-ti-connectivity]:[20170823-1rcnee0~stretch+20170830]

Sincere thanks again for helping out.

Best regards,

Tom

[tvan]

sudo i2cdetect -y -r 2

root@beaglebone:~# sudo i2cdetect -y -r 2
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- UU UU UU UU -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --

[drewfustini]

Ah, ok. If the Seeed Motor cape does not appear on the bus but other capes do, then I think there is likely an issue with the Seeed motor cape.

I'd suggest posting this issue on the BeagleBoard.org community mailing list as someone else might have to same hardware to test with:
http://beagleboard.org/discuss

[silver2row]

tvan,

Add a numerical value, e.g. "2" in the MotorBridge.py library.

So...

https://github.com/silver2row/MotorBrid ... rBridge.py

That is my gitHub.com account and you can see what I changed in the first couple of lines of the Python Library. If you made it to where it states:

Code: Select all

Hello From MotorBridge
Error accessing 0x4B: Check your I2C address
Error accessing 0x4B: Check your I2C address
Error accessing 0x4B: Check your I2C address
Error accessing 0x4B: Check your I2C address
Error accessing 0x4B: Check your I2C address
Error accessing 0x4B: Check your I2C address

Then:

All you need is the correct numerical value, "2," after the mentioned section. So...

Code: Select all

from Adafruit_I2C import Adafruit_I2C
import Adafruit_BBIO.GPIO as GPIO
import time
Reset = "P9_23"
MotorBridge = Adafruit_I2C(0x4b)
GPIO.setup(Reset, GPIO.OUT)

Instead use this and notice the numerical value "2" after MotorBridge = Adafruit_I2C(0x4b):

Code: Select all

from Adafruit_I2C import Adafruit_I2C
import Adafruit_BBIO.GPIO as GPIO
import time
Reset = "P9_23"
MotorBridge = Adafruit_I2C(0x4b, 2)
GPIO.setup(Reset, GPIO.OUT)

If this does not work, please work w/ me on gitHub.com under silver2row. I can sure use help at times and I am adding software and making patches to make things work better for everyone who uses this specific Cape. Motor Bridge Cape!

Seth

[silver2row]

tvan and Drew,

Seth here. Here is what I am running on a BBB to get the Motor Bridge Cape up and running w/ my "seeed Studio" started software and additions.

uname -a

Code: Select all

Linux beaglebone 4.9.59-ti-r74 #1 SMP PREEMPT Thu Nov 2 06:20:31 UTC 2017 armv7l GNU/Linux

cat /etc/dogtag

Code: Select all

BeagleBoard.org Debian Image 2017-11-05

Seth

P.S. If this helps, good. If you need more info, please let me know. I am sure I have other configurations I am not discussing here.

[silver2row]

Hello,

The numerical value "2" is the bus number, e.g. busnum.

Seth