Hi,
I am trying to flash BB_AI with eMMC flasher with am57xx-eMMC-flasher-debian-10.3-iot-armhf-2020-04-06-4gb.img but it aborts flashing.
It comes with the following error:
Error: [/dev/mmcblk1] does not exist
Can you help please.
Thanks,
Pedro
Hi,
I am trying to flash BB_AI with eMMC flasher
with am57xx-eMMC-flasher-debian-10.3-iot-armhf-2020-04-06-4gb.img but it
aborts flashing.
I never use the pre-built flasher images. My normal procedure is to use
the "runable" image on the SD card, boot with it, perform any updates (10.3
is positively ancient*), and only after confirming the card is
working/configured do I go in and modify the last line of /boot/uEnv.txt --
which turns the card into a flasher; reboot to flash that image.
It comes with the following error:
Error: [/dev/mmcblk1] does not exist
Where does it "come" -- a proper flasher image takes control at the end
of u-Boot loading uEnv.txt, before any SSH type console is normally
available. That message seems to imply a problem with the SD card -- either
the socket is bad, the card is bad, or possibly it is not formatted for
Linux.
How did you put the image on the card? Balena Etcher has been the
recommended tool for creating working cards from img files, for a few years
now. If you just copied the img file onto a card, it will never work.
* the most recent testing build is
https://rcn-ee.net/rootfs/bb.org/testing/2021-04-19/buster-iot/am57xx-debian-10.9-iot-armhf-2021-04-19-4gb.img.xz
which is SIX minor versions of Debian newer. I'd suggest burning that to
the SD card, then booting it to ensure it works (runs). Only after that go
into the /boot/uEnv.txt and uncomment the last line. Reboot. It should
flash the eMMC Remove the SD card and reboot -- confirm the eMMC is up to
the current Debian. Note that this SD card is now a flasher image, and if
you boot with it installed, it will just reflash the eMMC.
Please share the full boot log of the "flasher" lots of good
information is dumped before it "failed"..
Regards,
Hello Robert,
Attached is a trace file. I am using the file am57xx-eMMC-flasher-debian-10.3-iot-armhf-2020-04-06-4gb.img and I burned it into SDCARD by using the balena tool.
If I boot with the regular card, I don’t see /dev/mmcblk1 in the ls /dev command.
Could it be a damaged nand flash memory?
Also, I see that the boot program doesn’t have any nand test utility which is common to other Linux uboot systems.
Best Regards,
Pedro
BB_AI_Trace.txt (31.8 KB)
Hello Dennis,
Attached is a trace file. I am using the file am57xx-eMMC-flasher-debian-10.3-iot-armhf-2020-04-06-4gb.img and I burned it into SDCARD by using the balena tool.
If I boot with the regular card, I don’t see /dev/mmcblk1 when I type the ls /dev command.
Could it be damaged nand flash memory?
Best Regards,
Pedro
BB_AI_Trace.txt (31.8 KB)
Hi Pedro,
There is something wrong with your eMMC, your log has a few issues:
In u-boot:
Card did not respond to voltage select!
invalid mmc device
(that's your eMMC)
in the boot log you have:
[ 2.859012] mmc1: SDHCI controller on 480b4000.mmc [480b4000.mmc] using ADMA
You should see:
[ 2.866958] mmc1: SDHCI controller on 480b4000.mmc [480b4000.mmc] using ADMA
[ 3.048201] mmc1: new HS200 MMC card at address 0001
[ 3.054153] mmcblk1: mmc1:0001 TB2916 14.6 GiB
[ 3.074388] mmcblk1boot0: mmc1:0001 TB2916 partition 1 4.00 MiB
[ 3.101629] mmcblk1boot1: mmc1:0001 TB2916 partition 2 4.00 MiB
[ 3.115591] mmcblk1rpmb: mmc1:0001 TB2916 partition 3 4.00 MiB,
chardev (245:0)
[ 3.157241] mmcblk1: p1
Here's a quick test with that image..
Regards,
bbai.log (35.6 KB)