Other Parts Discussed in Thread: SK-AM64B
Tool/software:
Hello,
I have a sd card with a custom image that I would like to create an .img of so I can flash it onto other sd cards. Note that we have a mixture of GP and HS-FS devices that we would like to be able to use with this image.
The sd card that I've been developing on works perfectly fine. It will boot by default on a GP device and when I rename the proper tiboot3.bin file it will boot on a HS-FS device.
I've already attempted creating the .img using the Disks program in Ubuntu 22.04 (This is running in a virtualbox VM as our company laptops are Windows). I then used balena etcher on Windows to flash the .img to a new sd card (I've used this exact install of balena before to flash the TI .wic and it always works).
The clone SD card does boot on GP devices, but for some reason, even after renaming the tiboot3.bin file, it doesn't boot on the HSFS devices. This is the console output of the clone SD card after switching to the tiboot3.bin for hsfs and booting on the hsfs device
(It just stays like this forever)
HS-FS device: SK-AM64B EVM PROC100A
GP device: SK-AM64 EVM PROC100E3
One thing I noticed about the clone SD cards is that after flashing they have a 3rd partition with free space, but again this doesn't seem to affect booting on GP.
My question is, what is different in the boot process between the two devices that would make this image boot on GP and not the HSFS? How could I fix this?
Thanks,
Animesh