Bela Gem Multi - unrecognized from IDE

giuliomoro

Does the text from those commands print quickly or slowly over time, one '--' pair at a time ? After you run them, also show the output of dmesg | grep i2c please.

gugdia

this with the jumpers
root@bela:~/Bela# i2cdetect -y -r 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: -- -- -- -- -- -- -- -- root@bela:~/Bela# dmesg | grep i2c [ 2.114019] i2c_dev: i2c /dev entries driver [ 2.466435] /bus@f0000/bus@b00000/i2c@2b200000/pmic@30: Fixed dependency cycle(s) with /bus@f0000/bus@b00000/i2c@2b200000/pmic@30/regulators/buck2 [ 2.499595] omap_i2c 2b200000.i2c: bus 3 rev0.12 at 100 kHz [ 2.507813] omap_i2c 20000000.i2c: bus 0 rev0.12 at 400 kHz [ 2.515471] omap_i2c 20010000.i2c: bus 2 rev0.12 at 100 kHz [ 2.522670] omap_i2c 20020000.i2c: bus 1 rev0.12 at 400 kHz [ 2.767354] i2c-gpio bus@f0000:i2c_gpio: using lines 659 (SDA) and 660 (SCL)

this without
root@bela:~/Bela# 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: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- root@bela:~/Bela# dmesg | grep i2c [ 2.114019] i2c_dev: i2c /dev entries driver [ 2.466435] /bus@f0000/bus@b00000/i2c@2b200000/pmic@30: Fixed dependency cycle(s) with /bus@f0000/bus@b00000/i2c@2b200000/pmic@30/regulators/buck2 [ 2.499595] omap_i2c 2b200000.i2c: bus 3 rev0.12 at 100 kHz [ 2.507813] omap_i2c 20000000.i2c: bus 0 rev0.12 at 400 kHz [ 2.515471] omap_i2c 20010000.i2c: bus 2 rev0.12 at 100 kHz [ 2.522670] omap_i2c 20020000.i2c: bus 1 rev0.12 at 400 kHz [ 2.767354] i2c-gpio bus@f0000:i2c_gpio: using lines 659 (SDA) and 660 (SCL)

super fast with both

giuliomoro

Then I cannot help but conclude that it's a PB2 issue ...

gugdia

So I assume that I should ask for a replacement for that... Thank you for the patience

giuliomoro

I think so ... maybe if you want to be sure, you could try connecting some other I2C accessories to the PB2 and see if those are correctly detected, but it really seems like something's wrong with it. You could also, with the cape plugged in, verify that you get 5V and 3.3V at the pins indicated on the PCB, as well as 3.3V on P1.14.

gugdia

Hello Giulio,
After buying a new PocketBeagle 2 and plugging it into the Bela cape, the system has finally started to work — this seems solved on my end!

Meanwhile my school has purchased two Bela Gem Multi (cape + PocketBeagle 2) units with the SD already flashed. Both show the same symptom: red LED from the PB2 and blue LED from the Bela cape, both solid/steady, never entering the usual blinking heartbeat.

Checking from macOS (ioreg -p IOUSB -w0 -l), the PB2 enumerates on USB as "AM62x DFU" (Texas Instruments) rather than as a network device — no 192.168.7.2 interface ever appears. As far as I understand, this means the SoC's ROM bootloader isn't finding valid boot media and is falling back to USB DFU recovery mode, before Linux even starts.

I also tried reflashing via the BeagleBoard Imaging Utility, but it's not able to write to either unit.
Is this a known issue, and is there a recommended recovery procedure for this DFU state?

Thanks,
Guglielmo

giuliomoro

this sounds like the SD card may not be flashed properly. Can you try flashing it by inserting it on the host and using these instructions?

« Previous Page