<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi Sven,<div><br><div><div>Am 29.11.2012 um 09:58 schrieb Sven Dyroff:</div><br class="Apple-interchange-newline"><blockquote type="cite"><font size="2" face="sans-serif">Hello Nikolaus,</font>
<br>
<br><font size="2" face="sans-serif">>> Wouldn't it be a good idea
to have two different penguin pictures? That means</font>
<br><font size="2" face="sans-serif">>> in addition to "splash.rgb16z"
we could have a "splash.rgb16z.flash". Bootloader</font>
<br><font size="2" face="sans-serif">>> would then use version "splash.rgb16z.flash"
in order to flash it to NAND and by</font>
<br><font size="2" face="sans-serif">>> the way give it the name "splash.rgb16z"
there. Then also dummies like me would</font>
<br><font size="2" face="sans-serif">>> see at one glance what's going
on, when the penguin for example wears a shirt</font>
<br><font size="2" face="sans-serif">>> with writing "NAND"
or "SD" on it or something like that. </font>
<br><font size="2" face="sans-serif">></font>
<br><font size="2" face="sans-serif">> Unfortunately it is already quite
a hack to have two different bitmaps... U-Boot can't</font>
<br><font size="2" face="sans-serif">> do any image processing or GUI.
So the trick is simply to copy a block of bytes from</font>
<br><font size="2" face="sans-serif">> NAND to RAM, unzip and set the
framebuffer base address to the RAM address.</font>
<br>
<br><font size="2" face="sans-serif">But I can't believe that in case when
booting from SD card, that then you'll first copy from SD to NAND before
copying from NAND to RAM. So I still suggest:</font>
<br>
<br><font size="2" face="sans-serif">a) In case you'll boot from SD card
and see that you want to flash the bootloader, copy image "splash.rgb16z.flash"
instead of "splash.rgb16z" from SD to NAND while displaying dark
red and empty screen.</font>
<br>
<br><font size="2" face="sans-serif">b) In case you'll boot from SD
card and see that you will not flash the bootloader, copy image "splash.rgb16z"
from SD to RAM and display this.</font>
<br>
<br><font size="2" face="sans-serif">c) In case you'll boot from NAND, you
don't have any other chance than displaying image "splash.rgb16z.flash"
from NAND.</font>
<br></blockquote><div><br></div>Ah, I get your idea.</div><div><br></div><div>Unfortuanately, U-Boot scripts can't find out where they or U-Boot itself were booted from.</div><div><br></div><div>So we have these rules (to some extent dictated by the limited programmability of u-boot and hardware):</div><div><br></div><div>1. if AUX is pressed -> u-boot.bin from SD</div><div> if AUX not pressed -> u-boot.flash from NAND</div><div><br></div><div>This is done by BootROM & MLO/X-Loader.</div><div><br></div><div>2. Boot.scr comes from SD if available, NAND else.</div><div><br></div><div>3. Boot.scr flashes if the version in NAND is different.</div><div><br></div><div>4. u-boot.bin (on SD) is hard-coded to erase the environment</div><div> so that it will flash because no version in NAND is known.</div><div><br></div><div><blockquote type="cite">
<br><font size="2" face="sans-serif">> This is why I recommend to have
a separate SD card for upgrading the bootloader. Then you will know...</font>
<br>
<br><font size="2" face="sans-serif">No, in case bootloader version of SD
card and NAND are identical, I will not know if I did something little
wrong with formatting the SD card or copying MLO and thus getting booted
from NAND instead of SD. But I want to know.</font>
<br></blockquote><div><br></div><div>My strong recommendation for everyone is to keep the bootloader identical,</div><div>and use a SD card with different bootloader only for flashing.</div><div><br></div><div>After flashing, use only the bootloader from NAND.</div><div><br></div>If you are not happy, restore the old bootloader on SD and reflash NAND.</div><div>But I expect that this works only smoothly with very recent and future versions.</div><div><br></div><div>Everything else makes a lot of trouble if users have different versions on SD</div><div>and NAND. This is something I want to avoid. And, U-Boot should be quite stable,</div><div>i.e. change only once or twice a year.</div><div><br></div><div>If you want a different behaviour, please modify the boot.scr before flashing</div><div>and please let us know about patches.</div><div><br><blockquote type="cite">
<br><font size="2" face="sans-serif">>> I can do the rebooting as often
as I want to. The new bootloader will never recognize</font>
<br><font size="2" face="sans-serif">>> that it already has flashed
itself. Later on I could even see this behaviour after a proper</font>
<br><font size="2" face="sans-serif">>> shutdown of QtMoko and soft
reboot. </font>
<br><font size="2" face="sans-serif">></font>
<br><font size="2" face="sans-serif">> Hm. This may be an issue by up-
and downgrading between different bootloaders. Please</font>
<br><font size="2" face="sans-serif">> insert the new-bootloader-SD and
boot with AUX button pressed.</font>
<br>
<br><font size="2" face="sans-serif">OK, I'll try what happens.</font>
<br>
<br><font size="2" face="sans-serif">Best regards</font>
<br><font size="2" face="sans-serif"> Sven</font>
<br>
<br></blockquote></div><br></div><div>BR,</div><div>Nikolaus</div><div><br></div></body></html>