Yes, chain loading brings strange problems.
Now e.g. with the dreambox two/one.
The images here worked perfectly. Then I sent it to my developer colleague to try it out with the u-boot.ext packed and it doesn't work.
Curiously, it's because he didn't have a mini-usb cable on when he tried it out (debug terminal).
Of course, I didn't notice it because I always had a terminal on it.
I was able to adjust it here immediately, I don't even have to start the terminal (kermit).
Only the cable has to be connected to the PC?? - Very strange
large file transfer: With the exception of the LE, this happens with in all Linux distributions.
Unfortunately, no mainline boots with the original boot loader on the Dreamboxes.
With the Dreamboxes, software protection is built into the boot loader, without the manufacturer's operating system no longer works.
So flashing the boot loader for normal users makes no sense here.
There is no burnig img for Dreamboxes.
The box is also not recognized as a device by the Burning tool or the boot loader lacks the mode.
If I destroy the boot loader, I can only boot from an sd and restore the eMMC from an operating system from sd.
I tried to contact the developers in vain, I only found out that they are very busy at the moment.
I hope that I will reach someone someday.
The other box, dreamTV, is actually not in my main interest.
I would have thought, because the keymaps are the same, it would be a simple matter - thought wrong.
There is no burnig img here either.
I tried one from a custom developer and it worked, but restoring the original image was only possible by hand using the uboot console and fastboot.
This was the only way I could use the original recovery/update.zip again.
And by hand I have now put an AndroidTV10 on it, which is very important to me at the moment.
I'm already thinking about how I could secure that without twpr.
the Beelink bootloader is then only for the Dremboxes or would that work with both?