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" <> 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.
> > >
> >
>
------------------------------------
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/
|