>Both of these images have to be flashed to boot0
NO, definitely not for idbloader,, STARTS at sector 64
Its really hard to tell where boot0 and boot1 are located,
don't show up in fdisk or cfdisk or gparted
So, you tell me
uboot STARTS at sector 16384, do the calculations, that is 8M
I think the location for idbloader is baked into chip,
where uboot is located is a config in idbloader,
in other arm devices uboot is in a different location
Oh, and BTW, I am still on the uboot from MJ19.12,
since everything works well, especially sleep
IOW, there is no problem needing fixing, why risk mucking it up
NO, definitely not for idbloader,, STARTS at sector 64
Its really hard to tell where boot0 and boot1 are located,
don't show up in fdisk or cfdisk or gparted
So, you tell me
uboot STARTS at sector 16384, do the calculations, that is 8M
I think the location for idbloader is baked into chip,
where uboot is located is a config in idbloader,
in other arm devices uboot is in a different location
Oh, and BTW, I am still on the uboot from MJ19.12,
since everything works well, especially sleep
IOW, there is no problem needing fixing, why risk mucking it up