08-02-2019, 02:44 PM
(08-02-2019, 08:09 AM)martinayotte Wrote: Are you sure that the eMMC is "completely blank" ?
If there is some kind of u-boot present in the boot sectors, it can be the cause of boot hanging ...
You can erase those boot sectors using "dd if=/dev/zero of=/dev/mmcblk2 bs=1024 count=1000" and try again to boot from SDCard.
Ah you are correct, if I write 0's to the eMMC I can boot from the SD card and then successfully run the `reboot` command with both eMMC and SD card present.
So the hanging after `reboot` command issue only occurs when the eMMC module with a boot sector is present.
One option could be keeping the /boot on the SD while leaving root partition on eMMC to get the best of both worlds (eMMC speed and a machine that can reboot).
However, since the board and eMMC are newly purchased, I am wondering if I should pursue an RMA with the vendor (AmeriDroid). Part of me thinks that it is not a hardware issue since I have seen the same issue from others as well, but it might be worth a shot to narrow this down?
