Colin Tuckley wrote:
> OK, sent to the list to try and keep things where people can see them. Also
> copied to Nick since someone said he wasn't seeing list email atm, Nick can
> you confirm you are reading the list?
> 
Yup. Seems ok now.

> I just tried using my new bootldr.small to do a load of bootldr.fast via
> minicom so that I could see the error messages - this is what I got:
> 
> boot> load bootldr
> partition bootldr is a bootldr partition:
>  requiring a bootldr or parrot image.
>  After receiving file, will automatically uncompress .gz images
> loading flash region bootldr
> using xmodem
> ready for xmodem download..
> ded to C0000400
> 
The missing leading chars for "LOAded to ..." is entirely normal.

> programming flash...
> unlocking boot sector of flash
> amdFlashProtectRange: unimplemented!!
That is correct.

> erasing ...
> Erasing sector 00000000
> Erasing sector 00010000
> eraseFlashSector timeout
>   flashp=50010000
>   flashAddress=00010000
>   flashContents=00000000
>   oldFlashContents=00000000
>   timeout=00000000
> erase error!
Now that looks wrong.

> ACK0
>     boot>
> 
> Does anyone have any ideas what might be wrong? or where to start
> investigating in the code?
> 
This ACK0 this is odd. I wonder if it suggests some kind of linker 
alignment problem where the control variable is not initialised to zero 
by default.

See if you can print out the value of the control variable before it can 
possibly be changed to see what it is.

> If people want to look at the code then it's on balloonboard.org in the svn
> repository.
Ta. I'll check it out and build it under 2.95 - my favourite test.
> 
> Colin
>