Re: Bootloader after piggyback / what is jtag

Ralf Miunske <ralf <at> miunske.de> writes:

> 
> > But I can't complete the procedure you suggest. How I'm 
> > supposed to start the serial download??
> You just need to get you the appropiate (win/un*x) "serload" version, and 
> simply run it using:
> 
> serload /path/to/an/opensimpad/image.img ttyS0
> (Un*x, simpad connected to com1)
> 
> or
> serload.exe /path/to/an/opensimpad/image.img COM1
> (Same using for example W*nd*ws eXPerimental :)
> 
> Did'nt you already practice this a lot to upload the bootldr-image? ]

Yes, in fact it doesn't work anymore once you have restored the simpad via 
piggyback. Any try to serload another alternate bootloader or windows image 
will result in an overlap error. You can't serload any opensimpad image since 
there isn't any option to erase (the 'Y' option in the newest bootloader). And 
you can't serload any newer bootloader because it simply will not work (once it 
restart you will always have the 2.4 bootloader, no matter what you have sent).


> Serload cannot define what will happen to the image after uploading. It is 
> stored inside the image itself, what to do with the contained data.

The problem is that I can't even start the upload procedure (with windows ce 
images, I've been able to upload a windowsce 3.0 16mb image rather than the 
32mb, but it's an horrible OS Version!!)

> 
> If you ever want to restore windows, don't ask how that works, it's the 
> same  Erm, of course, then you should'nt point serload to an opensimpad 
> image :)
> 
> > What does it means "press the right of both available keys..." ?
> I never know which of the two keys to hold on the simpad while resetting it 
to 
> reach the serial boot-console. Usually I need two runs 
> This only works with an updated arnold bootloader.

I see, in fact with the bootloader restored after piggyback procedure, it 
doesn't work.

I know it's probably my fault, since it can't be so difficult to restore it, 
but I've tried almost everything. The situation is this:

- Bootloader 2.4
- It's not possible to install any newer bootloader (after it restarts the 2.4 
is always there, even if the upload procedure seems succesfully)
- It's not possible to upload any Windows CE image nor any alternate bootloader 
(I always get the overlap error and it refuses to upload anything)
- It's not possible to upload any opensimpad image (the 2.4 bootloader menu 
miss the 'Y' option to actually erase the mem before upload. So the upload 
procedure is succesfully, but after the upload I have a lot of errors and at 
the end the opensimpad startup procedure always fail with some errors).

Desperate!

Massimo






-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM. 
Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php