RE: Bootloader problems after serload

Hi Peter

The problem below shows the alternative bootloader. If you burn the piggyback bootloader then you burn the alternative bootloader.
Look at the occupied memory addresses to see which one is running. 
Normal bootloader starts at 0x8014 and alternative bootloader starts
at 0x1f00014.
Next is that the burning of the bootloader failes.
I think that here the alternate bootloader is downloaded again instead
of the nomal one. So it overlaps and is not flashed.
Try downloading the normal instead of the alternative.

Walter

-----Original Message-----
From: [email protected] [mailto:[email protected]]On Behalf Of Peter Clarke
Sent: Thursday, July 15, 2004 5:31 PM
To: [email protected]
Subject: [Simpad-general] Bootloader problems after serload


Hello,
I found this thread below in a newsgroup and am having exactly the same problem.  Is there anything else that can be done to try to fix it or do I need to throw the Simpad away.
Thanks for your help.
Regards
Peter Clarke
 
 
 
_______________________________________________________________________________________________________________________
 
Hi Walter,
 
thanks for your tip! I tried to serload the 2.4 bootloader, but I think
I have the same problem:
I cannot get rid of the piggyback bootloader.
 
The alternative loader can't be loaded because of an overlap with the
piggyback loader:
 
Base   : 0x1f00000 Size 138944 entry:0x1f00014
Overlap: 1f00000-1f21ec0   && 1f00014-1f74b9c
Will fail -- try to load alternate loader: loader.alt
 
The serload of loader_bl 2.4 succeeded. But after the reset it seems to
me, that the piggyback loader (address 0x01f00014) gets activated again
instead of the downloaded one:
 
Load finished with 10kB/sec
Starting Image at 8014 PPCR 0x0000000a
 
PBL V2.4 20.07.2001
Booting...
================================================
Siemens Switzerland Bootloader V2.4 20.07.2001
Running  <at> 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  <at> 0x05061ab4 Ram  <at> 0x01f21ab4 FABDATA: S842-KJUBJ
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
[\                    ]
 
When I try to serload the CE image after that, I get this overlap error
message:
 
Base   : 0x1080014 Size 27371523 entry:0x4081000
Overlap: 1080014-2a9a817   && 1f00014-1f74b9c
Will fail -- try to load alternate loader: loader.alt
 
Do you have an idea, why the serloaded bootloader won't be started after
a reset?
 
Regards
Michael
 
> -----Original Message-----
> From: Walter Schweizer
[mailto:simpad-general-admin <at> lists.sourceforge.net]
> Sent: Montag, 23. Februar 2004 15:28
> To: Michael Bihler; simpad-general <at> lists.sourceforge.net
> Subject: RE: [Simpad-general] Need Bootloader Help
> 
> 
> Hi Michael
> 
> try the 2.4 bootloader that can be downloaded with serload, after 
> you have loaded the piggyback bootloader.
> To run WinCE you do not need the 2.5.3 bootloader.
> You can get the 2.4 bootloader from sourceforge.
> 
> Regards
> Walter
> 
> > -----Original Message-----
> > From: Michael Bihler [mailto:mbihler <at> freenet.de]
> > Sent: Friday, February 20, 2004 3:17 PM
> > To: simpad-general <at> lists.sourceforge.net
> > Subject: [Simpad-general] Need Bootloader Help
> > 
> > 
> > I killed my Simpad after flashing WinCE 4.0 via internet.
> > 
> > As a result, there was no active bootloader.
> > (cyclic message "PBL V2.4 20.07.2001, Booting,..." in terminal)
> > 
> > In the forum I read about a tip of Walter Schweizer, to
> > connect the pins
> > 1+2 of the test field, to activate the internal piggyback
> > bootloader. It
> > worked.
> > 
> > Unfortunately this loader can't load a WinCE-Image. I think 
> because of 
> > an overlapping address space:
> > 
> >     Base   : 0x1080014 Size 27371523 entry:0x4081000
> >     Overlap: 1080014-2a9a817   && 1f00014-1f74b9c
> >     Will fail -- try to load alternate loader: loader.alt
> > 
> > Downloading the 2.5.3 bootloader was successful!
> > But it seems, that the old loader (address 0x01f00014) gets 
> activated 
> > again after a reset:
> > 
> >     Load finished with 10kB/sec
> >     Starting Image at 8014 PPCR 0x0000000a
> > 
> >     PBL V2.4 20.07.2001
> >     Booting...
> >     ================================================
> >     Siemens Switzerland Bootloader V2.4 20.07.2001
> >     Running  <at> 206Mhz Processor ID 0x6901b118
> >     Press ESC for monitor
> >     Occupied Memory: [0x00004000-0x00008000],[0x01f00014-0x01f74b9c]
> >     Flash Id 0x00000018 at virt adr 0x05000000 Size 0x01000000
> > 
> > Because I don't want to integrate the JTAG interface yet:
> > 
> > Can anybody give me a hint to manipulate the startup 
> address after a 
> > reset, so that the new bootloader runs instead of the piggyback one?
> > 
> > Please help,...
> > 
> > Michael
> > 
> > E-Mail mailto:mbihler <at> freenet.de
> > 
 
 


-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_idG21&alloc_id040&op=click