|
Oh exactly, but I was trying to figure out how to restore a board to its factory state (factory preboot, tsbootrom, and redboot images). I think I'm almost there :-)
serial_blaster works great and perhaps later I'll look at using the open version of the 2K boot eeprom code; for now though I need the factory images.
Thanks for all the help.
Cheers
On 2/3/07, Curtis Monroe <> wrote:
On February 2, 2007 05:32 pm, Gary Wicker wrote:
> Thanks Curtis, but I think I there is a deeper underlying problem in my
> case. There are actually three boot images involved, not two: preboot,
> bootrom, and redboot. The factory 2K EEPROM code loads an additional 16K
> image from flash, these images are located at:
>
SerialBlaster does not need the second half of the boot loader. It load
redboot with ECC directly, and its still only 2KB.
Because it is so small it does not perform some initialization. But it
initializes enough to get Redboot loaded. The remaining initialization can be
moved to Redboot. I didn't make these changes to Redboot because I don't have
the peripheral boards to test with (a lot of the missing initialization is
for external daughter boards).
>
ftp.embeddedarm.com/images/tsbootrom
>
> I assume this is the image that then loads from the redboot partition in
> flash. Now I just need to figure out where to install that tsbootrom image
> in the flash and I should be able to restore one of these boards to factory
> condition using serial_blaster. When I was doing my flash experiments I
> must have wiped out this image.
>
> Of course my programming board is on its way from technologic just in case
> :-) Should be here Monday...
>
> Cheers
>
> Gary
-Curtis.
>
>
> On 2/2/07, Curtis Monroe <> wrote:
> >
> > The other option is to add the hardware initialization to the
> > SerialBlaster.
> > Its probably just some PLL settings. The SerialBlaster project includes
> > commented disassemblies of TS eeprom boot code.
> >
> > You may need to remove something to fit this initialization in. Like maybe
> > remove the SDRAM testing code.
> >
> > Or you could add this hardware initialization to a custom RedBoot (which
> > is
> > probably where it should be anyway).
> >
> > I've restored my TS-7250 with the serialblaster. But I never used USB with
> > it.
> >
> > -Curtis.
> >
> >
> > On February 2, 2007 02:55 pm, gkwicker wrote:
> > > Thanks Curtis, I've tried this but now I get the following whenever I
> > > try to boot the board:
> > >
> > > >> TS-NANDBOOT, Rev 1.00 - built 10:14:31, Mar 7 2005
> > > >> Copyright (C) 2004, Technologic Systems
> > > $T0a0f:08003000;0d:00510180;#13
> > >
> > > >> TS-NANDBOOT, Rev 1.00 - built 10:14:31, Mar 7 2005
> > > >> Copyright (C) 2004, Technologic Systems
> > > $T0a0f:08003000;0d:00510180;#13
> > >
> > > (...repeats indefinitely...)
> > >
> > > Here are the steps I took:
> > >
> > > 1) Used serial_blaster to boot the board with the serial_blaster
> > > redboot image.
> > >
> > > 2) Downloaded the following images from ftp.embeddedarm.com:
> > >
> > > preboot/ts7250-default
> > > redboot/ts7250-32-kernel
> > >
> > > My board is a TS-7250 with 32MB RAM and 32MB flash, so I'm guessing
> > > these are the right images.
> > >
> > > 3) After serial_blaster completes, connect teraterm and:
> > >
> > > RedBoot> load -v -r -b %{FREEMEMLO} -m xmodem
> > >
> > > 4) Send ts7250-32-kernel image using xmodem to the board.
> > >
> > > 5) Write the redboot image to flash and prepare to receive the EEPROM
> > > image:
> > >
> > > RedBoot> fis create RedBoot -b %{FREEMEMLO} -l 0x40000
> > >
> > > [...answer 'y' at prompt...]
> > >
> > > RedBoot> load -v -r -b %{FREEMEMLO} -l 2048
> > >
> > > 6) Send ts7250-default preboot image using xmodem to the board.
> > >
> > > 7) Write the preboot image to EEPROM:
> > >
> > > eeprom_write -b %{FREEMEMLO} -o 0 -l 2048
> > >
> > > I then remove the JP1 jumper and reboot. After that, it just
> > > continuously reboots, printing the message I listed at the top of
> > > this post.
> > >
> > > I tried some other preboot and redboot images from the embeddedarm
> > > ftp site, but I get the same result with all of them. I also tried
> > > these images:
> > >
> > > preboot/ts7250-nand2k-default
> > > redboot/ts7250-32-kernel-ts10
> > >
> > > Any ideas? Has anyone successfully restored a TS-7250 to its factory
> > > default loads of preboot/redboot using serial_blaster? If so, which
> > > images and procedure did you follow? Thanks in advance for your
> > > help...
> > >
> > > Cheers
> > >
> > >
> > > --- In Curtis Monroe <> wrote:
> > > >
> > > > The SerialBlaster eeprom resident bootloader does not have enough
> > > space to
> > > > initialize all hardware settings. So USB and some other hardware
> > > may not
> > > > work.
> > > >
> > > > You should use the serialblaster to re-install the old TS eeprom
> > > boot loader.
> > > > Then it should all work.
> > > >
> > > >
> > > >
> > > > -Curtis.
> > > >
> > > >
> > > > On February 1, 2007 07:31 pm, gkwicker wrote:
> > > > > Has anyone seen this? I recovered my TS-7250 using the
> > > serial_blaster
> > > > > utility, but now USB doesn't work in the linux kernel anymore.
> > > > > Everything else seems to work, can boot NFS root filesystem etc...
> > > > >
> > > > > Cheers
> > > > >
> > > > >
> > > >
> > >
> > >
> > >
> >
> >
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
>
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ts-7000/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/ts-7000/join
(Yahoo! ID required)
<*> To change settings via email:
mailto:
<*> To unsubscribe from this group, send an email to:
m("yahoogroups.com","ts-7000-unsubscribe");">
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
__._,_.___
![]()
__,_._,___
|