Posted: Wed Nov 18, 2009 21:50 Post subject: Senao/EnGenius 5610 RedBoot (fis list)
I am very new on this......
Let see if can help me on this....
I got an EnGenius 5610 and I am in RedBoot via Putty, but went i try several time to load (fis load), but nothing happens, just "Error: invalid number" or "no image".
Here are some logs:
RedBoot> ip_address -l 192.168.1.1 -h 192.168.1.10
IP: 192.168.1.1/255.255.255.0, Gateway: 0.0.0.0
Default server: 192.168.1.10
RedBoot> fis init -f load -r -b %{FREEMEMLO} jffs2.linux.bin
** Error: no default/non-flag arguments supported
** Error: invalid flag 'r'
** Error: invalid flag 'b'
** Error: no default/non-flag arguments supported
** Error: no default/non-flag arguments supported
RedBoot> load -r -b %{FREEMEMLO} jff2.linux.bin
Using default protocol (TFTP)
Can't load 'jff2.linux.bin': file not found
RedBoot> fis init -f
About to initialize [format] FLASH image system - continue (y/n)? y
*** Initialize FLASH Image System
... Erase from 0xbe030000-0xbe7e0000: ...........................................................................................................................
... Erase from 0xbe7e0000-0xbe7f0000: .
... Program from 0x81fe0400-0x81ff0400 at 0xbe7e0000: .
RedBoot> load -r -b %{FREEMEMLO} jff2.linux.bin
Using default protocol (TFTP)
Can't load 'jff2.linux.bin': file not found
RedBoot> load -r -b %{FREEMEMLO}jffs2.linux.bin
** Error: invalid number '0x80000400jffs2.linux.bin' for load address
RedBoot> load -r -b %{FREEMEMLO} jffs2.linuxbin
Using default protocol (TFTP)
Can't load 'jffs2.linuxbin': file not found
RedBoot> load -f -b %{FREEMEMLO} jffs2.eoc-5610.bin
** Error: invalid flag 'f'
RedBoot> load -r -b %{FREEMEMLO} jffs2.eoc-5610.bin
Using default protocol (TFTP)
Can't load 'jffs2.eoc-5610.bin': file not found
RedBoot> ip_address -l 192.168.1.1 -h 192.168.1.10
IP: 192.168.1.1/255.255.255.0, Gateway: 0.0.0.0
Default server: 192.168.1.10
RedBoot> load -r -b %{FREEMEMLO}jffs2.eoc-5610.bin
** Error: invalid number '0x80000400jffs2.eoc-5610.bin' for load address
RedBoot> load -r -b %{FREEMEMLO}jffs2.eoc5610.bin
** Error: invalid number '0x80000400jffs2.eoc5610.bin' for load address
RedBoot> load -r -b %{FREEMEMLO}jffs2.eoc-5610.bin
** Error: invalid number '0x80000400jffs2.eoc-5610.bin' for load address
RedBoot> fis load -l vmlinux.bin.l7
No image 'vmlinux.bin.l7' found
RedBoot> fis list
Name FLASH addr Mem addr Length Entry point
RedBoot 0xBE000000 0xBE000000 0x00030000 0x00000000
FIS directory 0xBE7E0000 0xBE7E0000 0x0000F000 0x00000000
RedBoot config 0xBE7EF000 0xBE7EF000 0x00001000 0x00000000
Posted: Mon Nov 23, 2009 20:08 Post subject: Senao/EnGenius 5610 RedBoot (fis list)
I read what you post... If don't exists, how can I or you can explain me how to find(or if you have it) that image and be so kind and explain me how to upload it, thru RedBoot.
Posted: Wed Dec 02, 2009 21:17 Post subject: Senao/EnGenius 5610 RedBoot (fis list)
I was checking all the files via RedBoot from another 5610 that it's fully functional, and have all the same files(registry), everything it's the same, then what's the problem now!, do all the proccess again!....
Posted: Wed Dec 02, 2009 22:05 Post subject: 5610 flash fails
Hi folks,
I'm encountering this problem with new 5610s that I got in today. There appears to be some difference with the flash numbers ranges. TFTP copies the file over no problem, but the "fis create linux" only takes about two minutes to run instead of the 10-15 it is supposed to. Everything completes as it should, but upon reboot, Redboot comes up and then nothing.
Does anyone know how this can be fixed? I've included my telnet log.
Chris
== Executing boot script in 0.690 seconds - enter ^C to abort
^C
RedBoot> ip_address -l 192.168.1.1 -h 192.168.1.11
IP: 192.168.1.1/255.255.255.0, Gateway: 0.0.0.0
Default server: 192.168.1.11
RedBoot> fis init
About to initialize [format] FLASH image system - continue (y/n)? y
*** Initialize FLASH Image System
... Erase from 0xbe7e0000-0xbe7f0000: .
... Program from 0x81fe0400-0x81ff0400 at 0xbe7e0000: .
RedBoot> load -r -b 0x80041000 linux.bin
Using default protocol (TFTP)
Raw file loaded 0x80041000-0x80580fff, assumed entry at 0x80041000
RedBoot> fis create linux
... Erase from 0xbe030000-0xbe570000: ....................................................................................
... Program from 0x80041000-0x80581000 at 0xbe030000: ....................................................................................
... Erase from 0xbe7e0000-0xbe7f0000: .
... Program from 0x81fe0400-0x81ff0400 at 0xbe7e0000: .
RedBoot> fconfig
Run script at boot: true
Boot script:
.. fis load -l linux
.. exec
Enter script, terminate with empty line
>> fis load -l linux
>> exec
>>
Boot script timeout (1000ms resolution): 2
Use BOOTP for network configuration: false
Gateway IP address:
Local IP address: 192.168.1.1
Local IP address mask: 255.255.255.0
Default server IP address:
Console baud rate: 9600
GDB connection port: 9000
Force console for special debug messages: false
Network debug at boot time: false
Update RedBoot non-volatile configuration - continue (y/n)? y
... Erase from 0xbe7e0000-0xbe7f0000: .
... Program from 0x81fe0400-0x81ff0400 at 0xbe7e0000: .
RedBoot> reset
Joined: 09 Aug 2006 Posts: 121 Location: Germany, Bensheim
Posted: Fri Jan 08, 2010 22:13 Post subject:
Quote:
but the "fis create linux" only takes about two minute to run instead of the 10-15 it is supposed to
The 5610 flashes way faster then the 1650/2610/etc.
On a 5610 a fis create should takes ca 2-4 minutes but not longer (just estimated, but i flashed e few in the past ).
On the slower devices a fis create indeed will take up to 10 minutes. But this can be speed up using "fis create256" instead.
).