--- In Curtis Monroe <> wrote:
>
> My modified RedBoot dissables the automatic boot scripting that
Redboot has. When recovering a board its nice skip RedBoots scripting.
You may want to re-enable it. (see my patch file for the location)
>
Thanks for the tip, I thought it just was just initially disabled by
default.
>
//-----------------------------------------------------------------------------
> // NAND FLASH TS-7250 32MB version (part # NAND256W3A0AN6 )
>
//-----------------------------------------------------------------------------
> // 0x0000-0000 - 0x0000-3FFF : 16 KB "TS-BOOTROM"
> // 0x0000-4000 - 0x01D0-3FFF : 29696 KB "Linux" (29 MB)
> // 0x01D0-4000 - 0x01FF-FFFF : 3056 KB "RedBoot" (3 MB - 16 KB)
>
//---------------------------------------------------------------------------
> // TOTAL 32768 KB = 32 MB
>
Aren't these addresses supposed to start with "6" rather than "0"?
I've got a 32MB TS-7260 and the flash is definitely resident starting
at 0x6000-0000 -- the maps you posted would match my board if they did.
>
>
> > Alternatively, do you know if there is a way to do the reverse of "fis
> > write" and copy from an arbitrary address range in flash to RAM? If
>
> fis load
>
> RedBoot> help fis
> Load image from FLASH Image System [FIS] into RAM
> fis load [-d] [-b <memory_load_address>] [-c] name
>
> you might need to specify the "-b" memory address to load the image
into.
> The "-d" option if for decompresing the image.
>
Unfortunately, since the chunk of flash that I want to copy to RAM
does not correspond to an FIS name ("arbitrary address range"), this
won't work.
> look in: (for the code.)
> ecosroot/packages/redboot/current/src/flash.c
It looks like that's where I'm headed. It appears from the code that
it is possible to disable the "reserved" protection in the code.
Thanks for all the info!
P.S. I really don't understand why TS didn't just define the FIS
directory as follows:
TS-BOOTROM 0x6000-0000 - 0x6000-3fff
LinuxFS 0x6000-4000 - 0x6....
RedBoot 0x6....
zimage ...
RedBoot config ...
If they did it that way, it would be very easy to use RedBoot to
replace the LinuxFS with whatever you wanted. Instead of course they
grouped the TS-BOOTROM and the LinuxFS under "(reserved)" and you
can't touch it with RedBoot. So we have to become RedBoot source
hackers to do anything non-standard with the board.
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/
|