Nothing is detected... is the OLED plugged in? That should be there as well at 0x3c.
Double check the soldering around everything on the i2c lines. Also make sure you CLEAN any excess flux off of all the pins on the i2c lines. It's very sensitive to extra capacitance. I've seen plenty of cases where nothing on i2c was working, but a simple clean of the board with alcohol fixes it.
Actually, looks at Scotts KiCad stuff, it looks like the I2C things are on the wrong pins. He put them on pins 17/18 but the I2C pins we use for I2C2 are 19/20.
You may be able to create a small solder bridge between 1719 and 1820 to get things to appear on i2c2. I believe that will work.
Can you also try logging in via ssh and running:
sudo config-pin P9_17 i2c
sudo config-pin P9_18 i2c
sudo i2cdetect -y -r 1
and seeing if anything appears there? 17/18 are technically i2c1, but I believe with recent kernels they default to gpio instead of i2c as no one really uses the i2c1 bus. If that works, we likely could update some code in a bunch of places to support the i2c1 bus, but it's not a trivial set of changes.
dkulp wrote:Nothing is detected... is the OLED plugged in? That should be there as well at 0x3c.Double check the soldering around everything on the i2c lines. Also make sure you CLEAN any excess flux off of all the pins on the i2c lines. It's very sensitive to extra capacitance. I've seen plenty of cases where nothing on i2c was working, but a simple clean of the board with alcohol fixes it.
The OLED does in fact work, at least i was working last night. I was fooling around remotely and changed that board over to Master this morning to see what v5.0 looks like. I will double check my soldering and clean the board with alcohol when I get home. For what it is worth, I don't recall in this thread many people using the BBB in this thread and getting it to write to eeprom from the ABOUT page.
The bin file works in the upload directory, albeit it has to be transferred via file explorer and not from the FPP UI.
I built the pocketbeagle version and it wrote the bin file to the eeprom chip fine. In any case I will double check and clean today. Thanks for your help.
dkulp wrote:Actually, looks at Scotts KiCad stuff, it looks like the I2C things are on the wrong pins. He put them on pins 17/18 but the I2C pins we use for I2C2 are 19/20.You may be able to create a small solder bridge between 1719 and 1820 to get things to appear on i2c2. I believe that will work.
Can you also try logging in via ssh and running:
sudo config-pin P9_17 i2c
sudo config-pin P9_18 i2c
sudo i2cdetect -y -r 1and seeing if anything appears there? 17/18 are technically i2c1, but I believe with recent kernels they default to gpio instead of i2c as no one really uses the i2c1 bus. If that works, we likely could update some code in a bunch of places to support the i2c1 bus, but it's not a trivial set of changes.
Thanks, I had a feeling it was mechanical since I have read a few posts where people were having issues writing to eeprom.
dkulp wrote:Actually, looks at Scotts KiCad stuff, it looks like the I2C things are on the wrong pins. He put them on pins 17/18 but the I2C pins we use for I2C2 are 19/20.You may be able to create a small solder bridge between 1719 and 1820 to get things to appear on i2c2. I believe that will work.
Can you also try logging in via ssh and running:
sudo config-pin P9_17 i2c
sudo config-pin P9_18 i2c
sudo i2cdetect -y -r 1and seeing if anything appears there? 17/18 are technically i2c1, but I believe with recent kernels they default to gpio instead of i2c as no one really uses the i2c1 bus. If that works, we likely could update some code in a bunch of places to support the i2c1 bus, but it's not a trivial set of changes.
How's that look?

