after testing a Apalis-iMX8 in our custom Carrierboard, i cannot boot the Apalis anymore in a Apalis-Evaluation Board.
As our Carrierboard has some known flaws, there is a good chance that it damaged the Apalis. Currently I am not sure whether the Apalis is actually damaged.
Now I observe the following behaviour (when inserted into a standard Apalis Eval-Board):
- I am able to flash the Toradex-Easyinstaller and I get an Image on DVI. But from here I am unable to a) erase the MMC and b) flash a new image from an SD Card, it simply quits.
- When accessing via Serial Console I have access to the Bootloader, but I receive the following message:
U-Boot 2020.04-5.7.2+git.33bb8e968332 (Jan 01 1970 - 00:00:00 +0000) CPU: NXP i.MX8QM RevB A53 at 1200 MHz DRAM: 4 GiB MMC: FSL_SDHC: 0, FSL_SDHC: 1, FSL_SDHC: 2 Loading Environment from MMC... OK In: serial Out: serial Err: serial Model: Toradex Apalis iMX8 QuadMax 4GB Wi-Fi / BT IT V1.1C, Serial# 07240432 BuildInfo: - SCFW 216a2c2e, SECO-FW c9de51c0, IMX-MKIMAGE 6a315dbc, ATF 2fa8c63 - U-Boot 2020.04-5.7.2+git.33bb8e968332 switch to partitions #0, OK mmc0(part 0) is current device flash target is MMC:0 Net: eth0: ethernet@5b040000 Fastboot: Normal Normal Boot Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0(part 0) is current device Scanning mmc 0:1... fs_devread read outside partition 280233472 Failed to iterate over directory boot.scr fs_devread read outside partition 1085539840 Failed to iterate over directory boot fs_devread read outside partition 1085670912 Failed to iterate over directory dtb fs_devread read outside partition 280233472 fs_devread read outside partition 1085670912 Apalis iMX8 #
I suspect that the internal MMC took damage in our Carrierboard.
My question is now wheter this is true, or if the error could be only in software.
Thanks for your efforts.