I'm trying to boot Beaglebone AI from SD with the latest image, but all the time getting this:
What I'm doing wrong?
I'm trying to boot Beaglebone AI from SD with the latest image, but all the time getting this:
What I'm doing wrong?
Either a bad SD card or a bad image. chkvsk What software did you use to build the image with?
I successfully used this image a couple of times now: https://www.element14.com/community/external-link.jspa?url=https%3A%2F%2Fdebian.beagleboard.org%2Fimages%2Fam57xx-debian…
It's from here: https://beagleboard.org/latest-images
I found a lot more is needed to get it rolling as a fully functioning microcontroller with GPIO - for instance, your filesystem may need to grow to meet your SD card capacity. So, I wrote it all down here:
See ya',
Sean
Make sure you are using the BB AI image (not the BB Black image). The BB AI image file name starts with am57xx
(use the link that Sean gave)
chkvsk, I would suggest you use this image (https://debian.beagleboard.org/images/am57xx-debian-9.9-lxqt-armhf-2019-08-03-4gb.img.xz ) for the BB-AI as Sean_Miller suggested. This is available here (https://beagleboard.org/latest-images ) the official webpage of Beaglebone.
Your snapshot says 'missing modules'. It might be a bad image. Try flashing the latest image again.
PS: In case your image that is pre-flashed iìon the eMMC is one of recent, you might only have to update it manually without going through the hurdle of flashing again.
I have about a dozen Beaglebone Black and Green. Had no issues updating firmware on BB and BBG. Every time using same brand 4GB SD cards something like this: microSDmicroSD
First time I had this issue when I was trying to update firmware on X15. Debian 8 updating was working fine, but Debian 9 updates - no success.
Same issue I have with AI.
Ok, tried am57xx-debian-9.11-iot-armhf-2019-11-02-4gb.img.xz.
No luck so far...
Starting kernel ...
[ 0.002525] /cpus/cpu@0 missing clock-frequency property
[ 0.002549] /cpus/cpu@1 missing clock-frequency property
[ 0.565444] omap-mailbox 4a0f4000.mailbox: no available mbox devices found
[ 0.565516] omap-mailbox 4883a000.mailbox: no available mbox devices found
[ 0.565582] omap-mailbox 4883c000.mailbox: no available mbox devices found
[ 0.565647] omap-mailbox 4883e000.mailbox: no available mbox devices found
[ 0.566341] omap-mailbox 48844000.mailbox: no available mbox devices found
[ 0.566408] omap-mailbox 48846000.mailbox: no available mbox devices found
[ 0.566473] omap-mailbox 4885e000.mailbox: no available mbox devices found
[ 0.566537] omap-mailbox 48860000.mailbox: no available mbox devices found
[ 0.566600] omap-mailbox 48862000.mailbox: no available mbox devices found
[ 0.566663] omap-mailbox 48864000.mailbox: no available mbox devices found
[ 0.566727] omap-mailbox 48802000.mailbox: no available mbox devices found
[ 0.996874] tpd12s015 encoder@0: failed to find video source
[ 1.002876] connector-hdmi connector@0: failed to find video source
[ 1.122231] dwc3 488d0000.usb: failed to initialize core
[ 1.142741] sdhci-omap 4809c000.mmc: failed to set system capabilities
[ 1.149990] sdhci-omap 480b4000.mmc: failed to set system capabilities
[ 1.173101] omap_voltage_late_init: Voltage driver support not added
[ 1.320221] sdhci-omap 4809c000.mmc: no pinctrl state for ddr_1_8v mode
[ 1.326891] sdhci-omap 4809c000.mmc: no pinctrl state for hs200_1_8v mode
[ 1.468036] mmc0: error -110 whilst initialising SD card
Gave up waiting for root file system device. Common problems:
- Boot args (cat /proc/cmdline)
- Check rootdelay= (did the system wait long enough?)
- Missing modules (cat /proc/modules; ls /dev)
ALERT! /dev/mmcblk0p1 does not exist. Dropping to a shell!
BusyBox v1.22.1 (Debian 1:1.22.0-19+b3) built-in shell (ash)
Enter 'help' for a list of built-in commands.
I've tried maybe 5 different (iot and lxqt) Images with no success. As I mentioned above, had no issues with flashing BBBs and BBGs before and now.
Did you ever boot and use it from the flash storage without the card installed?
Here's a post that describes /dev/mmcblk…:
If you didn't boot into flash and make any tweaks, my only thought left would be to be absolutely sure the card is seated. After try that, I'd have to assume there's a pin broken in the SD slot.
See ya',
Sean