try this:
i2cdetect -y -r 2
See what it returns. Someone posted that on the IRC channel.
yes it is. power is being supplied though the cape using a ATX power supply. i am connected though the Ethernet jack using bitvise to SSH in
I thought I was able to detect the board and flash over usb power but that was almost a month ago so I could be wrong. I know the PWM chip will not work over usb power.
i can flash the kamikaze image just fine. but the BBB is not picking up the replicape as a cape
Zachary, try and read back the EEPROM and tell us what it says.
cat /sys/bus/i2c/drivers/at24/2-0054/at24-1/nvmem
and ctrl+c to break the command when it gets to the “junk”
It should start like:
▒U3▒A0Replicape 3D printer cape00B3Intelligent AgenBB-BONE-REPLICAP00000000001(
By flash I mean write the replicape eeprom.
cat: /sys/bus/i2c/drivers/at24/2-0054/at24-1/nvmem: Connection timed out
I’m going to guess he gets a timeout.
i don’t even know how to get to the EEPROM?
must be a bad board or something. The eeprom is the 8 pin chip next to the T0 or rest thermistor input. Take the Replicape off and make sure no pins bent and missed the socket when it was plugged in.
i have reset the board several times. each time all pins were seated
how would i go about checking the board?
Did you do the i2cdetect command? It looks like the PCA (PWM) chip is on the I2C buss also. Maybe we can see if it is detecting that at all. Post results of the command:
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: – -- – -- – -- – --
I’m assuming that is showing something at 54,55,56,57 on the I2C addresses. I think the eeprom is at 54. I will have to fire mine up and see what it shows.
Here is mine. Pretty much the same except for something maybe on 70:
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: 70 – -- – -- – -- –
never mind. Docs say UU means probing was skipped because it was in use by a driver
anyone know what that 70 means
how about trying this command and seeing what is returned on 00: 0-3
sudo i2cdump -f 2 0x54 (answer yes)
Doesn’t look good. Should be numbers on 0-3 and ff on the rest. X probably means it couldn’t read or talk to the chip.