N4100+ Corrupt Firmware - Help!

[wxhunter]

So I screwed the N4100+ firmware up somehow, I think when I was trying to create my own certificates. So here is an attempt at recovery.

I have searched the internet exhaustively and found some hopeful information.

I have successfully interrupted the boot process and can get the Redboot prompt.

arping -f 192.168.1.100 && telnet 192.168.1.100 9000
WARNING: interface is ignored: Operation not permitted
ARPING 192.168.1.100 from 192.168.1.104 eth0
Unicast reply from 192.168.1.100 [00:14:FD:10:33:8E] 6.473ms
Sent 9 probes (9 broadcast(s))
Received 1 response(s)
Trying 192.168.1.100...
Connected to 192.168.1.100.
Escape character is '^]'.
== Executing boot script in 2.650 seconds - enter ^C to abort
^C
RedBoot>

Now my problem is to restore the firmware to the right flash memory locations. Any suggestions would be helpful.

So far I have been able to deinstall the firmware and have uploaded ramdisk.arm and zImage to the proper memory locations as described below, but still no joy.

ip -h 192.168.1.2
load -r ramdisk.arm -b 0x00800000
load -r zImage -b 0x00200000
exec -c "console=ttyS0,115200 root=/dev/ram0 initrd=0xa0800000,42M"

After all that I tried changing the RedBoot config and now I cannot get to the RedBoot prompt.
Does anyone know if and where I can get this thing fixed?

[Tanuki]

Yeeps ... I don't know now.

Without the RedBoot prompt ...

URL is the RedBoot documentation:

ecos.sourceware.org/docs-latest/redboot/redboot-guide.html

[since this is my first post I can't post a URL in standard form ]

I had a similiar problem and after reading the RedBoot docs, I discovered the solution was fairly simple. To load and run the OS on flash:

RedBoot>fis load ramdisk
RedBoot>fis load kernel
RedBoot>exec

The system then booted and all was good

To make this automatic I used the fconfig command. All I added was the items in BOLD and just hit return to leave the balance unchanged.

RedBoot>fconfig
Run script at boot: true
Enter script, terminate with empty line
>> fis load ramdisk
>> fis load kernel
>> exec
>>
Boot script timeout (1000ms resolution): 5
Use BOOTP for network configuration: false
Gateway IP address:
Local IP address:
Local IP address mask:
Default server IP address:
Console baud rate: 115200
DNS server IP address:
GDB connection port: 9000
HW Status: 0
Force console for special debug messages: false
MAC address: 0xB0:0xB9:0x02:0xF0:0xC8:0xB9
MAC address 2: 0xE8:0xB9:0x02:0xF0:0x28:0xDD
Network debug at boot time: false
Reset default: Normal
Serial number: 12345678901234567890123456789012
... Unlock from 0xf0fc0000-0xf0fc1000: .
... Erase from 0xf0fc0000-0xf0fc1000: .
... Program from 0x0ffd2000-0x0ffd3000 at 0xf0fc0000: .
... Lock from 0xf0fc0000-0xf0fc1000: .


Without the RedBoot prompt I think you are ready for JTAG lessons or a return to the dealer for JTAG.

Sorry I couldn't help you sooner.

Tanuki