I think I made a serious mistake in the middle of manipulating eMMC device. I ran something like following codes. Not exactly the same I am sure, since I was in the middle of making my own booting image.
echo 0 > /sys/block/mmcblk0boot0/force_ro
dd if=imx-boot of=/dev/mmcblk0boot0 bs=512 seek=2 skip=2
echo 1 > /sys/block/mmcblk0boot0/force_ro
Would you guide me how I can make the status of board return back to normal bootable state? Currently, now I can boot up the board by only using “uuu” command in JATG mode. eMMC booting naver comes back again… OMG.
Just use the Toradex Easy Installer loaded via USB recovery mode.
Actually I have no problem in running easy installer in JTAG mode and installing an image from network right now. In this case, the image would be installed into eMMC. Right? Nonetheless, after doing that, still the apalis board cannot boot up from eMMC at normal booting mode. I think that I crashed very important secured information in eMMC which greatly depends on system booting. Can you guess how I can happen and what things I need to do to make the apalis go back to original state?
Hi @toddhwang the Easy Installer will populate the mmcblk0boot* partitions with the U-Boot bootloader. I’m not sure what you could have done to make that failure persist across the Easy Installer setup. Do you get any output at all after running Easy Installer and then putting the device back into normal boot mode and powering up?
So sorry for disturbing you. I succeeded in booting with “multimedia reference image” right ago, but I swear that I just simply used the same steps which I walked through before. Apparently I kept failing at that time… Hmm… Anyway thanks…
** Please would you share with me any of guide about “how eMMC memory is parttitioned and managed in easy installer?” I wonder this…
Have a great day Drew ~
Hi @toddhwang the partitioning is all handled by the
image.json file that is part of the Easy Installer files. You can see the docs on the contents of that file here.