I've read that some guys have bad blocks (0 - 1024 kb) and there is no place for flashing U-Boot in typical size (512 kb - 1 mb).
is it possible to "jump" to another working NAND position and start U-Boot there?
The loader (U-Boot) which can do this should be configured freely.
I remember that is was possible to start another U-Boot from stock U-Boot (Cloud Engines)
Is it possible to create a super small U-Boot binary (no shell, no env, no filesystems, no EFI, ...)
(<256k) with the ability to start another U-Boot?
compared with GRUB, this could be the stage 1 or 1,5
how many code is necessary to make that possible?
How small can we get it with standard functions?
is it possible to "jump" to another working NAND position and start U-Boot there?
The loader (U-Boot) which can do this should be configured freely.
I remember that is was possible to start another U-Boot from stock U-Boot (Cloud Engines)
Is it possible to create a super small U-Boot binary (no shell, no env, no filesystems, no EFI, ...)
(<256k) with the ability to start another U-Boot?
compared with GRUB, this could be the stage 1 or 1,5
how many code is necessary to make that possible?
How small can we get it with standard functions?