Re: manual image installation with the hh.org bootldr - was Bootldr updater image - for easy one-step installation!!
"Chris Martin" <[email protected]> Wed, 22 Dec 2004 12:12:56 +0100 (MET)
| Newsgroups | gmane.comp.handhelds.simpad.linux |
|---|---|
| Message-ID | <[email protected]> |
Hi, > > Well, that's quite nifty. The bootloader really kicks ass. > This stuff you just wrote should be copied to the wiki... Yeah, as soon as this is released to the public we can do that. The hh.org bootldr is pretty well documented at handhelds.org also. > Since hh.org bootloader can't boot wince images (will it > ever be able to?), The problem is not the bootldr itself. The problem as far as I understand it is that the CE Images were modified to work with the Siemens bootlader. So it seems there is something in the CE Images that isn't standard. The hh.org bootldr has been able to boot CE almost from the beginning (at least on the iPAQs). Walter, maybe you can explain this in detail and maybe you have a solution how we can get the CE Images to work with the hh.org bootldr. > would something like > > copy hda1:/siemens_bootloader.bl bootldr work? > Yes. But you have to use the original ROM that is also used when reviving a device via JTAG. AFAIK the Siemens bootloaders used to update the bootloader (e.g. the 2.5.3 version) would not be suitable. But to answer yout question - with the right ROM (there are two simpadSL.rom and simpadCL.rom) you could reinstall the Siemens bootloader from CF the way you mentioned. Since the bootldr partition is protected you would have to run two commands before the copy command: boot> set override=1 boot> pflash 0 40000 1 boot> copy hda1:/simpadSL.rom bootldr That's it. > Or does this documentation still apply to go back to the old siemens > bootloader? > http://opensimpad.org/wiki/index.php/Docs/SerialInstall No, these instructions are obsolete as soon as we use the hh.org bootldr. A question for Alex and Peter: Why do I get a message that the bootldr partition is being "thrown away" and that it is unprotected when the bootldr initializes? Is this correct? I have no problems on my SL4, but this message does disturb me. Another suggestion from my side. So that we don't have to always write when we mean the hh.org bootldr I would suggest sticking with this: Whenever the hh.org bootldr is meant we use the spelling "bootldr" as oposed to bootloader. What does everybody think? Since the bootldr at hh.org is spellt this way I thought it would be a way of distinguishing which bootloader is meant without having to write "hh.org bootldr" all the time. And since bootldr NG is already a synonym for LAB that wouldn't be appropriate ;-) Chris Martin -- +++ Sparen Sie mit GMX DSL +++ http://www.gmx.net/de/go/dsl AKTION für Wechsler: DSL-Tarife ab 3,99 EUR/Monat + Startguthaben ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/