Step by step, I feel that i'm near of my objetive.
I hope this "bitacora" helps another one
I've compiled the ecos-redboot sources provided in the TSARM tools CD.
If you need it you can get it also from the embededarm ftp site. Take a look at
the catalog file in ftp root directory.
I've used the arm-9dti-elf, instead of the others five or six that are
mentioned in this message list.
results:
This generates a redboot.bin that enables the eeprom_write command and actually
boots my TS-7250.
It dumps the same error message of "unsuported eeprom type 71", but what my
surprise, i've loaded the ts-preboot and then (unexpecting success)
write_eeprom to the TS7250.
IT WORKS !!!!! [HAPPY]
by the way, i could write to the eeprom the TS-nand-boot, but same redboot
can't read/list/write FIS.
so that:
to write eeprom i use a compiled redboot, the one described in this message.
to read / write FIS, i use one of the official releases.
What's the problem now?
following the "howto":
http://tech.groups.yahoo.com/group/ts-7000/message/5312
i've loaded and writed bootroom & redboot downloaded from the main ftp site.
System boots TS-nand-boot, TS-bootrom and stops at this point.
the console says:
*******************************************************
>> TS-NANDBOOT, Rev 1.01 - built 10:30:52, Dec 20 2005
>> Copyright (C) 2005, Technologic Systems
>> TS-BOOTROM, Rev 1.09 - built 09:54:04, Oct 23 2008
>> Copyright (C) 2006-2008, Technologic Systems
>> TS-7250: Rev >E1 CPU, Rev B PLD, 64MB SDRAM
*******************************************************
and stops. No more words dumped
I've tested severals versions of bootroms and now i'm testing some different
versions of redboot.
who do you think is the cause of the system stops before Redboot loads?
Perhaps have i writed the redboot to a incorrect flash memory address?
does anyone have a fis list dump of the default installed flash, exactly of the
ts-7250 @ 64 MB @ 128 MB Flash.
Mine is:
RedBoot> fis list
Name FLASH addr Mem addr Length Entry point
(reserved) 0x60000000 0x60000000 0x07D20000 0x00000000
RedBoot 0x67D20000 0x67D20000 0x00060000 0x00000000
FIS directory 0x67FE0000 0x67FE0000 0x0001F000 0x00000000
RedBoot config 0x67FFF000 0x67FFF000 0x00001000 0x00000000
RedBoot>
I've writed to 0x67D20000. Is correct?
with a serial redboot load, helped with the magic serialblaster tool, and an
official release of redboot, can i load another redboot.bin and exec it?
It doesn't work in my machine, but i don't know if this is normal behaivour.
In other words, can i run redboot in redboot?
if this is possible, this will speed my test and will help me to discriminate
the cause of boot secuence stops.
thanks everybody.
--- In Curtis Monroe <> wrote:
>
> My guess is that your Redboot is out of date, so it doesn't recognize
> you internal NAND flash memory
>
>
> -Curtis.
>
>
> On Sun, 2010-01-24 at 13:39 +0000, torpedez wrote:
> >
> >
> >
> > Fixed the problem of compiling ecos-redboot.
> > It was the crooscompiler tool.
> > Now i'm using arm-9tdmi-linux-gnu and compiles redboot.
> >
> > Now the problem is that i can't boot from serial.
> >
> > The test and the results that I've recieved:
> >
> > In any case, TS-OPENBOOT works.
> >
> > 1. ecos-redboot compiled with no patch
> > RESULT: (in the TS serial console)
> > CRUS not in serial.
> > I've teste to manually patch the *.S files changing CRUS by 00000000
> > Same result
> >
> > 2. ecos-redboot compiled and patched with redboot.diff provided in the
> > serial blaster source code:
> > RESULT:
> > waiting for ']'
> > found ']'
> > +Can't identify FLASH - device is: f1, supported: 75 79
> > FLASH: driver init failed: Driver does not support device
> > $T050f:80f30200;0d:b89a0400;#88
> >
> > 3. ecos-redboot compiled and patched with redboot.diff provided by the
> > files section of this mailing list:
> > waiting for ']'
> > found ']'
> > +Can't identify FLASH - device is: f1, supported: 75 79
> > FLASH: driver init failed: Driver does not support device
> > $T050f:20eb0200;0d:08900400;#4d
> >
> > Please, could anyone help me?
> > there is a chip on the board, labeled:
> > samsung 810
> > K9F1G08U0B.
> >
> > Is this the eeprom and I shuold look for a different path?
> >
> > I use the ecos-redboot source code provided in the TSARM CD.
> >
> > Please, help me.
> > Thanks in advance.
> >
> > --- In "torpedez" <torpedez@> wrote:
> > >
> > > The second error was the consecuence of a bad redboot.bin.
> > > With others from the embeded arm home page I can boot.
> > >
> > >
> > > The problem now is to put a correct image of the boot in the eeprom.
> > >
> > > I've tryed to compile the ecos redboot but til now i could not.
> > >
> > > Several errors:
> > > compilation time:
> > > memcpy incorrect parameters.
> > > __Atribute__ not suported for this platform
> > > link time:
> > > no memory region specified for loadable section `.ARM.exidx'
> > >
> > >
> > > Eventually i've fixed one by one but not with succsesfull results.
> > > I've got the elf, img but not the bin. And the fist is only 18 kb
> > length.
> > >
> > >
> > > I join the group of people asking for a compiled version of the
> > redboot.bin with eeprom manage support for the TS-7250
> > >
> > > thanks.
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > --- In "torpedez" <torpedez@> wrote:
> > > >
> > > > However, the problem seems to be the time to transfer.
> > > >
> > > > i've edited serial_blaster.c and force not vervose mode.
> > > >
> > > > changing
> > > >
> > > > for(x=0; x<num_bytes; x++)
> > > > {
> > > > res = read(fd_bin, &ch, 1);
> > > > if(res == 1)
> > > > {
> > > > if(bverbose)
> > > > {
> > > >
> > > > into
> > > >
> > > > for(x=0; x<num_bytes; x++)
> > > > {
> > > > res = read(fd_bin, &ch, 1);
> > > > if(res == 1)
> > > > {
> > > > if(0 /*bverbose*/)
> > > > {
> > > >
> > > > in OutputFile function.
> > > >
> > > >
> > > >
> > > >
> > > > Now the problem is:
> > > >
> > > >
> > > >
> > > > waiting for ']'
> > > > found ']'
> > > > +Can't identify FLASH - device is: f1, supported: 75 79
> > > > FLASH: driver init failed: Driver does not support device
> > > > $T050f:acff0200;0d:24a70400;#e1ReadByte ERROR, no input after 10
> > seconds
> > > >
> > > >
> > > > Any sugestion while keeping in fight?
> > > >
> > > > thanks again
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > --- In "torpedez" <torpedez@> wrote:
> > > > >
> > > > > hi evarybody.
> > > > >
> > > > > I'm trying to reload flash of my TS-7250.
> > > > >
> > > > > I switch the JP1 and reboot device while serial_blaster is
> > waiting.
> > > > >
> > > > > the proccess then begins ok, but after a while, the TS7250
> > reboots while serial_blaster keeps sending data.
> > > > >
> > > > > Then the console dump:
> > > > >
> > > > > 0000000000000000
> > > > > 2048 Bytes in 18 seconds.
> > > > > --------------------------------------------------
> > > > >
> > > > > waiting for '>'
> > > > > ERROR!!! Expected '>' but found '<'
> > > > >
> > > > >
> > > > > Why my devive is rebooting?
> > > > >
> > > > > thanks.
> > > > >
> > > >
> > >
> >
> >
> >
> >
> >
> --
> Curtis Monroe
> Wk: 514-747-5076 x230
>
------------------------------------
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:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|