Help me with Bootloader reinstallation on SIMPAD SL4, PLEASE !

Thanks for the information. I'll try it
About the ARNOLDBOOT pdf. I don't konw if the memory organisation is the same as in the simpad. But the .img file layout (7.3 Genboot Header) should by right.

yeah i'm not sure either about the memory stuff, but it was interesting ... that difference in the persistent registry.

let me know if the erasing helped!

Just erasing with x e0 and x e1 and reflashing wince with serload didn't work .
Tomorrow I try to erase the the hole flash and start with jtaging at the begining.

What I not understand is:
Flash0 virtual mapping to 0x0500 0000 to 0x0600 0000
Flash1 (no virtual mapping) 0x0800 0000 to 0x0900 0000

Now Downloading a WinCE image (first download to the RAM), then burning to flash from 0x0508 0000 to 0x06A7 E017
(first 0x8000 is the bootloader) but there is a gap between 0x0600 0000 and 0x0700 0000.
What happens there or did they remap the flash over again? Question over Question

download on a linux pc

ah, yes i guess you should jtag the whole 32mb with 00 00 00 00 or FF FF FF FF then
this cl4 crap can cause so many problems

virtual addresses have nothing to do with physical addresses in that sense. i've seen a mapping that mapped physical rom start (0x0) to 0xA0000000 this was funny because the cpu was xscale and there the physical ram start addr is .. guess what 0xA0000000 (different for strongarm in the simpad - 0xC0000000) but the cpu will know how to interprete it, whether virtual or physical. so, if you understand what i mean, that's no real gap at 0x06000000. oh, and often there's more than one virtual address mapped to the same physical address.


edit: ah i see now what confused you. seems like the flash is mapped like this: first 16mb chip from physical 0x0 to 0x01000000 is mapped as 0x05000000-0x06000000 virtually and second 16mb chip which is from 0x08000000 to 0x09000000 physical address is mapped from 0x06000000 to 0x07000000 virtually. the image is about 25MB so it has to go to second part too to fit. does that help?

Edited by cmonex 2006-12-10 8:55 PM

any progress?

No, I had to work for school
But today my 3rd Simpad arrived (CL Swisscom Version, no PCMCIA ) for 20$ incl. dockingstation

Tomorrow I'll try to get live back to my Simpad SL

yay, i had the swisscom too they are good bc they are cheap

btw, here's another dumped bootloader part from 0x0 to 0x80000, just in case: http://izemize.fw.hu/mysimpadbl2_253.zip
(actually it is 2.5.3 just as the first one is - but some certain parts are different)

Flashing your 2nd dump file has the same effect (what's the difference, no FABDATA what else ... ) CE will not boot.
Booting stop with

But I've found an old NE2000 PCMCIA card, now I can download the CE image quite fast


Edited by joni 2006-12-13 5:16 PM

ok can you tell me which CE image you're flashing. what is the file size? 27255299 bytes? if so, it might still be corrupt, i'd suggest a redownload from the simpad roms site

btw, did you jtag both flash chips with 00 00 00 00?

the bootloader i uploaded is from a different sl4 it had had linux on it so no fabdata. and one of the bootloader headers looks different. i thought maybe it could be better than mine. - well nope

if nothing else works, you *might* jtag the entire OS (i think someone did this) but that will take a lot of time

I downloaded the CE3.0 (just for testing if this one works), normal I take CE4.1
I tried to erase the 2nd flash chip (0x08000000) over jtag, but the jtag tool just give me an error message , but I had read somewhere that just the 1st flash chip can be accessed by the jtag interface

I tried the handhelds bootldr, but it did't work
No I jtaging again your boot dump file, then loading the hole (except the first 0x80000) flash with 0xFF over serload and then reload wince41

oh, yes i remember reading that it cannot be accessed by jtag boh, yes i remember reading that it cannot be accessed by jtag but after that fladda mentioned he did erase it by writing 00 00 to it via jtag.. unless i misunderstood.
anyway you erased it by using X E1, so it should be empty now...

i would have suggested trying another PC as your COM port might not be perfect (btw what about FIFO?), but ne2000 didn't work either ...

this is really a mystery to me... let me know if the retry worked.

Edited by cmonex 2006-12-13 6:51 PM

I tried 3 different pc's (incl. Linux serload), in windows fifo enabled and disabled. NE2000 seems to work for downloading.
I created a ARNOLDBOOT file which load the hole flash (excl. first 0x80000 bytes, bootloader) with 0x00 over serload or NE2000, but no improvement after downloading the wince image file

Can you please post the serial output when you bootup wince4.1, thanks

Edited by joni 2006-12-14 11:37 AM

hmm.. exactly how did you destroy the original working bootloader (when fiddling with linux)? can you detail it?

serial output when i boot into ce 4.1 (without flashing anything):

with 2.4:

PBL V2.4 20.07.2001
Booting...
================================================
Siemens Switzerland Bootloader V2.4 20.07.2001
Running @206Mhz Processor ID 0x6901b118
Press ESC for monitor
Occupied Memory: [0x00004000-0x00008000],[0x01f00014-0x01f74b9c]
Flash Id 0x00000018 at virt adr 0x05000000 Size 0x01000000
No 32Bit Flash detected 0x00000000
FlashImage Checksum 0x05040014-0x05061ab0=0x342f5fd8 Bootloader Image OK
Fabdata Flash @0x05061ab4 Ram @0x01f21ab4 FABDATA: S842-KJNVU
MSC2=0x211954e0 :: MQ200 - Revision ID=2 ...
Initialise PCMCIA Interface... done.
Codec UCB1200 ID:0x1005 Ver.5 Dev.0 Suppl.1 IO 0x00000000
No PCMCIA Card Attached
No serial download request
Boothdr at 0x05080000 -> 0x31415926
Loading executable with header 0x0000
[*********************/] 0kB/sec
Done

t

and with 2.5.3:

PBL V2.4 20.07.2001
Booting...
================================================
Siemens Switzerland Bootloader V2.5.3 10.06.2003
Running @206Mhz Processor ID 0x6901b118
Press ESC for monitor
Occupied Memory: [0x00004000-0x00008000],[0x00008014-0x0007500c]
Flash Id 0x00000018 at virt adr 0x05000000 Size 0x01000000
No 32Bit Flash detected 0x00000000
FlashImage Checksum 0x05040014-0x05059f11=0x8912ac03 Bootloader Image OK
Fabdata Flash @0x05059f18 Ram @0x00021f18 FABDATA: S842-KJNVU
MQ200 - Revision ID=2 ...
Initialise PCMCIA Interface... done.
Codec UCB1200 ID:0x1005 Ver.5 Dev.0 Suppl.1 IO 0x00000000
No PCMCIA Card Attached
NO PCMCIA CARD! -- Use serial IO
Sysinit done
No serial download request
Boothdr at 0x05080000 -> 0x31415926
Loading executable with header 0x0000
[*********************|] 0kB/sec
Done


(i get a little "t" with 2.4 alternative bl - with some accent ... maybe it was there with 2.5.3 too, i should check)

Edited by cmonex 2006-12-14 8:24 PM

I installed the hh.org bootloader for the simpad and installed a 2.6.12 kernel and some basic tools (busybox... ,created with openembedded). Some console application worked, I flashed the the simpad more than 10 times with linux but after a reset the hh.org bootloader didn't start up any more

You asked for the 1.4 Image file. I found some one sourceforge , but I never tested them.