I want to use Bela Gem that runs with PocketBeagle 2 with the new industrial version. I tried flashing the emmc with their image, but it did not work.
Then for testing, I tried flashing the emmc from the PocketBeagle 2 Debian 13 v6.12.x-ti IoT(Stable) image but it is not working as well.
I think there is an error while flashing. The output is here: beagler-flasher-log
Can anyone help?
Based on that flashing… It flashed…
this is fun to see..
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1338) [sender=3.4.1]
ERROR: writing to [destination=/dev/mmcblk0] failed...
Debug: Setting Heartbeat
You’ll need to ping GEM for PB2I industrial support, they really just need a rebuild..
Building now: bb-beagle-flasher (1.20260306.0) · beagleboard/repos-arm64@3201b10 · GitHub
Okay please run:
sudo apt update
sudo apt-get dist-upgrade
you should see this upgrade:
voodoo@am6232-pb2-88:~$ apt list --upgradable | grep flasher
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
bb-beagle-flasher/unknown 1.20260306.0-0~trixie+20260306 arm64 [upgradable from: 1.20240718.1-0~trixie+20250529]
Then try it.. again..
Thanks for looking into it.
Just to make sure I understand correctly: what exactly do you mean by “it flashed” in this case?
When I remove the SD card, I cannot reach the board via SSH anymore.
Booting with the SD card inserted works fine and I can SSH normally.
So from my perspective the flashing provess does not create usable system from eMMC.
yeah, part of it flashed… just not correctly, was debugging on my phone and pushed some changes, please see the updated 2nd half of my message..
Regards,
Thanks for the clarification and the quick fix.
I’ll upgrade and try the flashing process again shortly.
I’ll report back with the results.
I did that, I rebuilt and had them test the rebuilt image and it didn’t work. What’s the packages/versions that are required on 6.12 in particular, so I can double check that it’s the correct version in the latest build? (I don’t have a PB2I yet)
i still need to grab a production one… but that’ll be after next week.. (EW in Germany)..
Regards,
it’s just the version of u-boot that’s required for pb2i support..
bb-u-boot-pocketbeagle2 2026.01.20260105.1-0~trixie+20260210
The flasher just got an upgrade.. (fingers crossed)
bb-beagle-flasher 1.20260306.0-0~trixie+20260306
Regards,
our new image that @knabel has been testing has
ii bb-u-boot-pocketbeagle2 2026.01.20260105.1-0~bookworm+20260210 arm64 beagleboard.org u-boot for pocketbeagle2
but still shows only 512 MB with free.
Is that expected?
Nope… Best to get a serial boot log
This is their EEPROM, fwiw:
root@bela:~/Bela# hexdump -C /sys/bus/i2c/devices/0-0050/eeprom
00000000 aa 55 33 ee 01 37 00 10 2e 00 50 4f 43 4b 45 54 |.U3..7....POCKET|
00000010 42 45 41 47 4c 32 41 31 49 30 41 31 30 30 30 30 |BEAGL2A1I0A10000|
00000020 49 30 41 30 41 31 30 30 30 31 30 34 32 36 50 42 |I0A0A100010426PB|
00000030 32 49 30 30 32 35 36 36 11 02 00 a8 12 fe ff ff |2I002566........|
00000040 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................|
*
00001000
I assume that’s good enough because it’s recognised as 1GB with both “PocketBeagle 2 Debian 13 v6.18.x-k3 Io% (LTS-Dec-2027)” and “PocketBeagle 2 Debian 13 v6.12.x-ti IoT(Stable):”
@knabel have you got one of these https://www.digikey.com/en/products/detail/raspberry-pi/SC0889/17877576 to be able to connect to the JST on the PB2 and grab a boot log?
FYI, I should get a PB2I of my own in a couple of weeks then troubleshooting can be smoother.
That’s what Linux sees, but we need to see what u-boot does, to get the full 1gb
No, but I can get one. Should be able to test it in two days. Can you tell me what to do exactly?
Ok I tried to do this, but I think I do not have access to my internet connection on the PB2 when I connect via USB (Windows 11 Laptop).
Assuming it has brought up a network connection across USB (e.g. you aren’t just using the UART to connect), then probably the host machine isn’t doing forwarding. If linux you need something like
sudo sysctl 'net.ipv4.ip_forward = 1'
sudo sysctl 'net.ipv4.conf.all.forwarding = 1'
sudo sysctl 'net.ipv6.conf.all.forwarding = 1'
Your router may not like a machine inside its domain connecting from a number that isn’t in its domain (e.g. 192.168.7.*) if so you have set up a file wall, e.g if using nftables
table ip nat {
chain prerouting {
type nat hook prerouting priority filter; policy accept;
}
chain postrouting {
type nat hook postrouting priority srcnat; policy accept;
meta oiftype ether masquerade
}
}
You’ll have to work out how to do the equivalent in windows.
I did this now and it seems to be working fine. I can reach SSH now when my board is running from eMMC.
I have one now, but I am not sure how to grab a boot log.
Just plug it into the U port of your probe and set tio or picocom to 115200.