Help me with Bootloader reinstallation on SIMPAD SL4, PLEASE !

little correction (to make it more clear) about "you already have the full pbl image flashed for both bootloader spaces" - if you just did a jtag, then of course you only have it flashed in once. but it's executing from the alternative memory space, hard coded for that.

Edited by cmonex 2006-12-07 1:16 AM

Now I can download the 2.4 loader_bl but it ends with


And Simpad doesn't restart automatic . I have to press the reset button, but this I think will kill the bootloader in the RAM and he will not flashed into the flash .



Have you any idea how to fix this or did I run in a false direction.

jonathan

well, two things.

first, this is the output of a successful bootloader download _and_ flashing:

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
?Setting baud rate to 115200
¦?Serial download request
Booting : <NULL>
Serial download entered.
??
Base : 0x1f00000 Size 107300 entry:0x1f00014
¦?[*********************|] 1070086
Load finished with 10kB/sec
Starting Image at 1f00014 PPCR 0x0000000a
================================================
Siemens Switzerland Bootloader V2.5.3 10.06.2003
Running @206Mhz Processor ID 0x6901b118
Press ESC for monitor
Occupied Memory: [0x00004000-0x00008000],[0x01f00014-0x01f6d00c]
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 @0x01f19f18 Copy Fabdata to Ram... Done
[*************************-]
Firmware Update Successfully Finished
Press Button to restart
Firmware Update Successfully Finished
Press Button to restart
Firmware Update Successfully Finished
Press Button to restart
Firmware Update Successfully Finished
Press Button to restart
Firmware Update Successfully Finished
Press Button to restart
Firmware Update Successfully Finished
Press Button to restart


so you have to manually restart at the end of it. but if you didn't get any further than "Starting Image at 8014 PPCR 0x0000000a" then the flashing indeed didn't start.

and why didn't it start? there can be two reasons i can think of... sometimes you just have to retry until it accepts the image BUT in your case i suspect you were trying to flash the 2.5.3 bootloader because the size of it that's reported in your quote is the size of the 2.5.3 bootloader. are you sure you were trying to flash the 2.4 one???

note, i haven't tried flashing 2.5.3 directly after flashing the full bootloader (linux, jtag, shorting pins, etc all flash the full pbl), only 2.4, because i noticed the 2.5.3 is a lot smaller, so i think the correct sequence is 2.4 and then 2.5.3. this worked in the case of Soldalot1. (this is a guess though.)

Edited by cmonex 2006-12-07 12:23 PM

I have tried both (2.4 2.5.3). It had the same effects. But now, i'm starting at the begining (jtaging bl, and go step for step through your instruction.

ok, let me know if it worked.. you do have to retry sometimes, until it works.

I have tested an other alternative. Grab the bootlader from my 2nd Simpad (CL4 with bl 2.5.3) via jtag from address 0x0 to 0x80000. Change the serial nr from C420 to S842 in the binary file. Erase the first flash chip on my Simpad SL over jtag (128 blocks). Load the grabed file on the Simpad SL over jtag.

Booting....


Now I try to flash wince

hey nice idea. i'm surprised though that you flashed a CL4 bootloader. hope it'll work..

if it doesn't work... i can send you the SL4 version of this bootloader, dumped off my SL4.

but the original method should really work too

Grab CL bootloader, doesn't work
I've tested your solution , but the bl serlaod stopps with



I tried it 5 to 10 times (when serload was able to downlaod bl successful), allways the same behavior
I would be obliged if you can send me (devnow -a-t- gmail. -c-o-m-) a SL4 dump file of your 2.5.3 bootloader (0x0 to 0x80000 -> 512Kbyte should by the hole bootloader in flash).

thanks
jonathan

i've uploaded the dump of 2.4 from 0x0 to 0x80000. http://izemize.fw.hu/mysimpadbl24.zip (zip file is 118685 bytes)

this has my simpad's fabdata. you'd better rewrite it to your own if you can

Jtaged your Dump File



Now flashing wince

did it work?

No



Flashing seems to work, but when I press reset, I just see the bootloader starting up.
Now I want to understand how flashing work on the simpad (study Serload, ARNOLDBOOTBLOCK, physical to virtual address translation...)
By the way which Simpad hardware revision have you ? My is HW 1.


Edited by joni 2006-12-10 9:58 AM

Terminal output after CE41 Update

hey. i'm sorry to hear it didn't work

but i'm not so surprised. i read that after using the cl4 bootloader it is harder to get the sl4 bootloader and OS to get to work..

(i assume you flashed an approx. 25MB sl4 image and not a 14MB cl4 image!)

someone (called fladda on forums) ended up in the same situation as you, after trying cl4 bootloader, no OS would boot on his sl4.
he solved this by erasing the second flash chip of the sl4 at 0x08000000. actually it is done by writing 00 00 00 00's to the flash. (or FF FF FF FF, whichever you prefer)

or you can use the extended commands to erase that chip. i didn't try them yet but i read you have to enter this extended mode by typing x and then a hex value between 00 and ff depending on the exact command. for example you need to type x (in hyperterminal after calling monitor) then e1 to erase the second flash chip. if this is easier for you than jtagging the whole 16mb flash...

after that, you may be able to flash and load the sl4 OS fine. let me know if this helped!

wow nice pdf, how did you find it! i looked into it, and it tells a lot of information applicable to the simpad. sure makes a lot of sense compared to my experiences and conclusions and it tells even more!

i can see the persistent registry might be at a different address (and in the second flash) for the cl4 (16mb) than for the sl4 (32mb)... could be your problem?

about physical to virtual address translation, check out some cpu docs (and additionally maybe a strongarm doc as that's what the simpad has, i can give you links), those will tell you more than what's needed for this flashing in a nutshell the cpu has a mmu (memory management unit) which is responsible for this. the actual physical addresses are usually mapped to virtual addresses. most of the time the virtual addresses are used (unless there is no mapping, at some parts of the bootloader for example). the terminal output uses virtual ones for example. jtagging uses physical ones (obviously).
what drove me crazy about the simpad was that the mapping seems to be different when only the bootloaders are running, from the mapping that is active when the OS is running - and you can dump only the latter with some tools (pmemmap). still, the mapping for the bootloader phase can be guessed from terminal outputs or from disassembled bootloader code. anyway, other hpc's i dealt with aren't this complicated

how would i check the simpad HW revision?

edit: i found a line on the bottom of the simpad saying HW 2 / SW 2 - would this be it?
but i don't think this is the problem, the bootloaders i dumped for you are not the original factory ones. they are originated from the same bootloader image that is available on the internet (the one you jtagged as well)

Edited by cmonex 2006-12-10 4:02 PM