Hi - I’ve a Pocket Beagle - that isn’t booting for last week. I can see from the flashing LEDs that it has booted, but it doesn’t bring up the usb gadget interface.
Now in order to debug, I’ve pulled the sd card, and inserted it into my BBB. Booting of the SD card fails in the usual way, but if I boot of the MMC, I can then mount the SD card, and chroot into it.
Checking the logs, last I have available there are 28th January - which is about when it last booted. So I can’t see evidence of whats failing.
Now on the BBB, I can easily attach a UART cable, and what the boot messages when the SD card is booting.
Question is which pins are the default UART (I’m guessing 3.3 V)?
Your tags are a little funny, considering your query, but I think what you want is here:
Ta - thanks. I ended up using BBB uart J1 - counting downward from the dot.
Back history - yes I was testing the pocket beagle SD card on the Beagle Bone Black. Back when the Pocket Beagle first came out - I modified the Arm Arch distribution for the BBB, to run on the pocket beagle. Crux on the pocket beagle is I never soldered the header onto the board, so you only know the machine is coming up from flashing LEDs, until the USB GPS gadget comes up - and ports start appearing on the usb. This meant when developing the OS, it was far easier on the BBB as it had ethernet, and pins on the board. The difference between PB and BB is only really in the device tree - and that is picked up in UART by reading the EEPROM, and Das U-Boot selects the device tree based on what is read from the EEPROM. In this way a single image can support a huge number of these TI boards though the ID on the EEPROM.
Anyway meant when the PB didn’t boot, it was far easier to debug the SD card on the BBB. Turns out the PB can’t have been shut down safely last time, and the file system had minor corruption. Arch Linux, when booting up, drops the machine into an emergency boot mode, where root can log on and correct whatever faults are on the machine. Problem is this happens before the USB Gadget is brought up - and so thats why I never saw the machine appear over USB.
On the BBB, it was easy to fsck the SD - and check the board was booting. Indeed could have done this by just plugging the SD card into my desktop - which I did, but forgot to fsck the file system!
Anyway the BBB now boots of the SD card, I’ll move it to the PB in next few minutes and check if that boots as well - but i expect it will.
These days, the PB has more life, as the BBB was one of the older ones with the 2GB MMC chip, and arch linux grew that you can no longer fit the current base OS on it. So that machine is now running an OS that is several years old - and has very little space left. One of these days I’ll do a cut down operating system for it - making sure it only has the minimal OS on it necessary. Hopefully then get some free space again. I kind sight for the days of Tomsrtbt - where an entire linux OS fitted on a floppy!
And managed to update the BBB after a few hours. Crux was removing linux-firmware which is huge, and I don’t think the am3359 depends on firmware, I still have the device tree blobs in /usr/lib/firmware …
Anyway probably power the PB and BB down in a mo, so I can move back to the PB2 where trying to get the PWM working from linux …