Ok, so images will have to be built for eMMC or SD based on that? Or do they end up in different spots on the device? Using the "hurry up and plug it in afterr uboot launches method I've "nuked" the eMMC u-boot, so now I can try some different things, assuming I can get it to boot with the emmc plugged in (I got some strange bl checksum errors I'll have to look into) Now, my board does not have the boot button, I have a reset header instead (early board), so I can't try that directly. google the Amlogic usb burning tool and read up, it's not a tool without risk, the USB port that wakes up for me is the top-left, you will need a USB A to A cable, I made one. You should have a u-boot button, I think this may be the method of entering the proper amlogic burning mode (to avoid continuously inserting/removing that eMMC. The bootscript/etc need to point at the right device or else it will have no idea where to get the device tree/kernel/etc. SD uses ".bin" where eMMC simply uses "u-boot.bin"Īt this point the bootloader could be written to the eMMC and should at least attempt to boot. I have not yet attempted it, however, there is a different u-boot.bin between eMMC and SD. I've tried some Odroid images as well and they don't appear to boot.Ĭontacting Libre seems to yield no responses so far (on anything at all, not just this issue), but I do see some u-boot sources seemingly targeted at this board from another member of this forum here: Īnyone know what's involved in configuring/building this in a manner that can boot from eMMC and flashing it to the eMMC module, or if any additional steps are needed? I've found some instructions for dding u-boot bin files to cards for other boards, which seem to involve writing certain parts of the file to different offsets on the device, but I don't know what determines what gets written where. Is there some U-Boot build/customization work that needs to be done? I've tried editing the boot.scr file with a hex editor, and even updating the same string that appears toward the beginning of the drive setting the root device to /dev/mmcblk0p2 and none of it seems to help.
Other Amlogic-based boards seem to support the familiar boot.ini file for configuring the bootloader, but I don't see that in any images for this board.
#AMLOGIC USB BURN TOOL FOR EMMC ANDROID#
The only way I could get the card to a writable state was to attach it to the board between the time that the bootloader started reading the kernel and the time that the kernel started booting (otherwise it would just boot the Android image that came on it).
I've tried flashing all of the available Linux images I can find to mine (nightly and non-nightly debian and ubuntu from armbian and the official image from Libre).
0 kommentar(er)
