ts-7000
[Top] [All Lists]

Re: [ts-7000] Re: ts7200 won't boot into redboot... I erased flash and k

To:
Subject: Re: [ts-7000] Re: ts7200 won't boot into redboot... I erased flash and killed it....
From: Curtis Monroe <>
Date: Sun, 4 Jun 2006 02:02:19 -0400

On June 3, 2006 07:29 pm, yur_grampa wrote:

> Thank you for the info Curtis.

> I get the message:

> waiting for '>'

> ERROR!!! Expected '>' but found '<'

>

> Unless I change the boot.s file from:

> .org 2048 @ ensures the file is 2k in size. (no more, no less)

>

> to

> .org 2040 @

>

> and recompile....

>

> Then I get:

> 000000000000000000000000000000000000000000000000boot.bin: Success

>

> ***Exiting***

> ***********************

>

> I really do not know how Success shows up(must be sent from the TS7000 )

> because entering:

> linux:/usr/local/opt/sb # find /usr/local/opt/sb -type f -print |xargs

> grep -n "Success"

> linux:/usr/local/opt/sb #

>

> yields nothing.... from serialblaster.c or any of the other support

> files...

>

> I can only guess that the ts7000 responded with a Success due to file

> transfer.... unfortunately nothing else happens -- it never gets to the:

> waiting for '>'

> found '>'

I think the problem is here:

else

{

perror(file_name);

exit(-1);

}

"perror" prints the file name followed by the latest error code, which happens to be "Success" or no error.

This is happening because its getting to the end of your file before the required 2048 bytes have been read.

You need the ".org 2048" !!!

>

> so it does not go to the next function of serial blaster code which as

> you know is

> 1.open the bootloader

> 2.wait for length acknowlegement

> 3.send redboot.bin

> 4. execute redboot...

>

> obviously something is not going correctly so I am left with taking

> the messages received and try to make sense of them-which in this case

> will take me some time, but with help I hope it is possible...

>

> This kind of troubleshooting can frustrate me but I find the

> application very worthy of looking into at great depth, for my own sake..

> I feel lucky that such an interesting application is even offered as

> open source...

> If I get it to work, I will feel more at ease in being dangerous with

> commands I do not know much about... and will want to get another

> model ts7xxx to mess around with....

>

>

>

>

>

>

>

> --- In Curtis Monroe <> wrote:

> >

> > You don't need to "pad" to boot file!!!

> > The ".org 2048" does that for you.

> >

> > You just can't go over 2048 Bytes. (or you get the error I put in to

> warn you)

> >

> > Boot.S should easily fit in the 2048 Byte limit. Boot.S is only

> really tight

> > when you are making an EEPROM image. The EEPROM image contains the

> NAND ECC

> > routines. The TS7200 does not have a NAND chip, so you don't need

> that code.

> > And it doesn't even have an EEPROM, it boot directly from NOR Flash.

> >

> > If you are not getting a message that says:

> >

> > waiting for '>'

> > found '>'

> >

> > Then you failed to load the 2048 Byte boot code before the watchdog

> reset. The

> > boot code is never executed till you get this message.

> >

> > Are you getting this message?

> >

> > -Curtis.

> >

> >

> >

> >

> >

> >

> > On June 2, 2006 08:42 pm, yur_grampa wrote:

> > > Bucky2090 in previous post mentioned pg 61 from the Cirris

> > > EP9301_User_Guide:

> > > cpu outputs a ">" to signify 2048(decimal) characters from UART1 have

> > > been read.

> > > That really helped. I did not know how that happened. So I

> > > took the screen output of the boot.bin file that serial blaster sends

> > > to the ts7200 and noted that it was around 2640 characters. Looking

> > > into boot.s

> > > (that eventually compiles to boot.bin) I noted that near the end a ck

> > > for size is done:

> > > .org 2048@ ensures the file is 2k in size. (no more, no less)

> > > I then realized that the compiled size of boot.bin must be too large

> > > even though I did nothing to it but change the value of 32 to 16 on

> > > one line of code!

> > > So now a new adventure begins, to try and determine how to get a

> > > workable boot.bin that is 2048 and not 1 character more or less...

> > > Wow! What trickster thought up this one!

> > >

> > >

> > >

> > >

> > >

> > >

> > >

> > >

> > >

> > >

> > >

> > > Yahoo! Groups Links

> > >

> > >

> > >

> > >

> > >

> > >

> > >

> > >

> >

>

>

>

>

>

>

>

>

> ------------------------ Yahoo! Groups Sponsor --------------------~-->

> You can search right from your browser? It's easy and it's free. See how.

> http://us.click.yahoo.com/_7bhrC/NGxNAA/yQLSAA/CFFolB/TM

> --------------------------------------------------------------------~->

>

>

> Yahoo! Groups Links

>

> <*> To visit your group on the web, go to:

> http://groups.yahoo.com/group/ts-7000/

>

> <*> To unsubscribe from this group, send an email to:

>

>

> <*> Your use of Yahoo! Groups is subject to:

> http://docs.yahoo.com/info/terms/

>

>

>

>



SPONSORED LINKS
Linux os Hardware Arms
Computer internet Computer security Computer hardware security


YAHOO! GROUPS LINKS

  •  Visit your group "ts-7000" on the web.
     
  •  To unsubscribe from this group, send an email to:
     =Unsubscribe
     
  •  Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.



<Prev in Thread] Current Thread [Next in Thread>
Admin

Disclaimer: Neither Andrew Taylor nor the University of NSW School of Computer and Engineering take any responsibility for the contents of this archive. It is purely a compilation of material sent by many people to the birding-aus mailing list. It has not been checked for accuracy nor its content verified in any way. If you wish to get material removed from the archive or have other queries about the archive e-mail Andrew Taylor at this address: andrewt@cse.unsw.EDU.AU