Using RedBoot

[Gregorio Ortiz]

Hello, I'm using a TTL to RS232 converter and I'm accesing to the Router Station very well.

I'm trying to change Openwrt firmware, this is the the log:

fis list:

Name FLASH addr Mem addr Length Entry point
RedBoot 0xBF000000 0xBF000000 0x00030000 0x00000000
kernel 0xBF030000 0x80060000 0x000C0000 0x80060000
rootfs 0xBF0F0000 0x8006CC00 0x00F00000 0x8006CC00
FIS directory 0xBFFF0000 0xBFFF0000 0x0000F000 0x00000000
RedBoot config 0xBFFFF000 0xBFFFF000 0x00001000 0x00000000

this is my partitions...

bottom the boot up process


RedBoot(tm) bootstrap and debug environment [ROMRAM]
Ubiquiti Networks certified release, version 0.9.8.04 - built 15:47:39, Dec 15 2008

Copyright (C) 2000, 2001, 2002, 2003, 2004 Red Hat, Inc.

Board: Ubiquiti AR71xx-based board
RAM: 0x80000000-0x84000000, [0x8003abc0-0x83fe1000] available
FLASH: 0xbf000000 - 0xc0000000, 256 blocks of 0x00010000 bytes each.
== Executing boot script in 1.000 seconds - enter ^C to abort
RedBoot> fis load -d -e kernel
Trying LZMA decompression...
Image loaded from 0x80060000-0x80288085
Image is not ELF, skipping ELF parsing...
RedBoot> exec
Now booting linux kernel:
Base address 0x80050000 Entry 0x80060000
Cmdline : console=ttyS0,115200 init=/init
Linux version 2.6.26.8 (goyo@goyo-laptop) (gcc version 4.1.2) #2 Mon Jan 26 12:00:41 CET 2009
console [early0] enabled
CPU revision is: 00019374 (MIPS 24K)
Determined physical RAM map:
memory: 04000000 @ 00000000 (usable)
Initrd not found or empty - disabling initrd
Zone PFN ranges:
Normal 0 -> 16384
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
0: 0 -> 16384
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 16256
Kernel command line: rootfstype=squashfs,yaffs,jffs2 noinitrd console=ttyS0,115200 init=/etc/preinit
Primary instruction cache 64kB, VIPT, 4-way, linesize 32 bytes.
Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes
Writing ErrCtl register=0004a002
Readback ErrCtl register=0004a002
PID hash table entries: 256 (order: 8, 1024 bytes)
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 62200k/65536k available (1764k kernel code, 3264k reserved, 318k data, 128k init, 0k highmem)
SLUB: Genslabs=6, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Mount-cache hash table entries: 512
net_namespace: 484 bytes
NET: Registered protocol family 16
MIPS: machine is Generic AR71xx board
registering PCI controller with io_map_base unset
PCI: mapping irq 32 to pin1@0000:00:11.0
PCI: mapping irq 33 to pin1@0000:00:12.0
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
TCP reno registered
NET: Registered protocol family 1
squashfs: version 3.0 (2006/03/15) Phillip Lougher
Registering mini_fo version $Id$
JFFS2 version 2.2. (NAND) (SUMMARY) �© 2001-2006 Red Hat, Inc.
yaffs Jan 23 2009 13:03:43 Installing.
msgmni has been set to 121
io scheduler noop registered
io scheduler deadline registered (default)
Serial: 8250/16550 driver $Revision: 1.90 $ 1 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0x18020000 (irq = 11) is a 16550A
console handover: boot [early0] -> real [ttyS0]
ag71xx_mdio: probed
eth0: Atheros AG71xx at 0xb9000000, irq 4
eth0: invalid speed specified
ag71xx: probe of ag71xx.0 failed with error -22
eth0: Atheros AG71xx at 0xba000000, irq 5
Atheros AR71xx SPI Controller driver version 0.2.2
m25p80 spi0.0: unrecognized JEDEC id c22018
Atheros AR71xx hardware watchdog driver version 0.1.0
TCP vegas registered
NET: Registered protocol family 17
802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
All bugs added by David S. Miller <davem@redhat.com>
VFS: Cannot open root device "<NULL>" or unknown-block(0,0)
Please append a correct "root=" boot option; here are the available partitions:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)


I can not find redboot documentation over RouterStation, I suppose the commands I using are wrong, but How is the process for flashing a OpenWrt firmware from zero?

Regards

[JulioCP]

Can you post the steps that you are following to flash the RouterStation?

A generic flashing of OpenWrt inside RedBoot would include steps like this:
fis init
fis load -r -b %{FREEMEMLO} openwrt-atheros-vmlinux.lzma
fis create -r 0x80041000 -e 0x80041000 kernel
fis load -r -b %{FREEMEMLO} openwrt-atheros-root.squashfs
fis create -l 0x00300000 rootfs

:!: (Some of the values used can differ from the one that you need to use. e.g.: the number 0x00300000 must be calculated to check YOUR avalaible free space.)

Saludos, Julio

[Gregorio Ortiz]

There are my steps:

The kernel boots up, thus, I only flash the rootfs partition..

fis load -r -b %{FREEMEMLO} ar71xx/openwrt-ar71xx-root.squashfs

fis free
0xBF0F0000 .. 0xBFFF0000

The difference is: 0x00F00000

fis create -l 0x00F00000 rootfs

reset

and the result is the same:

VFS: Cannot open root device "<NULL>" or unknown-block(0,0)
Please append a correct "root=" boot option; here are the available partitions:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
+


I've tested with:

openwrt-ar71xx-root.jffs2-128k
openwrt-ar71xx-root.squashfs

With the same results.... unable to mount rootfs...

Any idea?

[Uu]

I see two problems in the kernel messages:

MIPS: machine is Generic AR71xx board


m25p80 spi0.0: unrecognized JEDEC id c22018

The machine was not automaticaly detected. You can fix that by adding "board=UBNT-RS" (if you are using latest revision of openwrt.org trunk) - see target/linux/ar71xx/files/arch/mips/ar71xx/prom.c for other board= values.

But machine detection is not the main problem. Your flash driver does not know about flash part. Man, which openwrt branch are you using? RouterStation is supported in trunk (https://svn.openwrt.org/openwrt/trunk).

The Macronix flash support was added in openwrt:

r13676 | juhosg | 2008-12-17 15:56:14 +0200 (Wed, 17 Dec 2008) | 1 line

[ar71xx] add support for Macronix mx25lxxx flash chips,

[Gregorio Ortiz]

My version is
OpenWrt Kamikaze (r13658), and I think this can be the problem... I'll test newer version of the trunk, and I'll post the results in the forum...

thank you very much.

[Gregorio Ortiz]

Ouggh!!

I've downloaded the latest version of trunk, and the error is basically the same..

It not appears m25p80 spi0.0: unrecognized JEDEC id c22018

but it appears MIPS: machine is Generic AR71xx board

Where can i add "board=UBNT-RS" ??

reagards

[Uu]

You can add "board=UBNT-RS" in RedBoot, run "fconfig" and when it asks for startup script, enter these two lines:

fis load -d -e kernel
exec -c "board=UBNT-RS"


Please attach boot messages if you still have trouble.

[Gregorio Ortiz]

Perfectly!! thank you very much Uu for your help!!

Now boots up kernel+rootfs and the OpenWrt is now in scene....

I hope the Ubiquity people writes a setup manual of this process in a few days....

Thank you very much again!.

[GovWireless]

I have eseentially the same problem and this did not work for me. I have tried mulitple code versions, I have the board=UBNT-RS and mine hangs at the CMDline: prompt. I have loaded all the images I can image. I need UBNT to post or email me the images sent with the original boards.

[UBNT-Mike.Taylor]

GovWireless,

I know we got your boards un-bricked using the shipping image of UBNT firmware (available elsewhere on the site). I am wondering, however, why you didn't get the same result building the latest OpenWRT code as others did. If you feel like trying this again - share the details so we can get to the bottom of it.

- Mike

[sarvani]

Dear Friend,

We just procured 2no.s UBIQUITI ROUTER STATION boards. How to make a TTL to RS232 converter ?

How to use these boards with basic openWRT OS?

Please help me.


Thanks

Amarendra
India
email:ceo.sarvanitelecom@gmail.com

[sarvani]

Dear Friend,

We just procured 2no.s UBIQUITI ROUTER STATION boards. How to make a TTL to RS232 converter ?

How to use these boards with basic openWRT OS?

Please help me.


Thanks

Amarendra
India
email:ceo.sarvanitelecom@gmail.com

[sarvani]

Dear Friend,

We just procured 2no.s UBIQUITI ROUTER STATION boards. How to make a TTL to RS232 converter ?

How to use these boards with basic openWRT OS?

Please help me.


Thanks

Amarendra
India
email:ceo.sarvanitelecom@gmail.com

[freezer2k]

google for MAX232

[penypinch]

Is there a step by step for flashing the RS to dd-wrt?
Thanks

[coolboss]

And I'm using a TTL to RS232 too

[penypinch]

The below worked for me. It is a post on the dd-wrt forum
Hope it helps you.....
...........

This should get it done for you. It sounds more complicated then it actually is.
You can actually assign your windows machine the correct static IP,
something like 192.168.1.30.
You can then put the RS in upgrade mode by holding down the little button as your turn it on.
You would then tftp the firmware.


Here is a copy and paste of something more in detail.

Quote:
Assign your tftp host with a static IP address of 192.168.1.100 with 24bit
subnet mask (255.255.255.0).
Using the command line interface (CLI) to tftp the image will work fine.
Get a command shell ready to go with the
tftp command(on windows c:\>tftp -i 192.168.1.20 RS.dd-wrt.bin put)in this example,
the DD-WRT image is located in the root of C drive.
It's advisable to use a switch or hub since you will need to switch the
tftp host interface to the LAN1 port after pushing the DD-WRT image thru
the WAN interface of the Ubiquity Routerstation (ubntRS).
Connect tftp host to switch/hub.
Get a second command shell ready & start continuous ping of the
WAN interface of the ubntRS (c:\>ping 192.168.1.20 -t)..
.connect the "data" side of PoE to your switch/hub..
.have the PoE side ready to plug into ubntRS..
.Hold the reset button on the ubntRS & connect to PoE and
continue holding reset button for 10seconds & then release.
A couple of seconds later you will see ICMP echo (ping) from
the ubntRS in the command window on 192.168.1.20 &
this is when you should now issue the tftp command as listed above.
It will take a few seconds for the tftp image to push to the ubntRS
but it will let u know if successful.
Once the DD-WRT image is transfered ubntRS will lose ICMP echo (reply)
as seen in your continuous ping command shell.
Without power cycle of ubntRS, you can move your tftp host to the LAN1 interface of the
ubntRS.
It will take about 5minutes for the image to reboot on the ubntRS..
.while thats happening, you can start another ping on
the LAN1 interface with "c:\>ping 192.168.1.1 -t" and once you get replies
you should be able to use your browser to access the DD-WRT firmware web interface.
Here's a couple of notes:
if you have any "cached" DD-WRT credentials from this ubntRS or
any other DD-WRT device that you have worked with on this computer,
you might get the jacked up "black & white" DD-WRT login page..
.simply access the interface with the full URL & you should
get in "http://192.168.1.1/index.asp"..
.remember, this DD-WRT image requires activation...happy flashing....cheers...;-}

[penypinch]

The below worked for me. It is a post on the dd-wrt forum
Hope it helps you.....
...........

This should get it done for you. It sounds more complicated then it actually is.
You can actually assign your windows machine the correct static IP,
something like 192.168.1.30.
You can then put the RS in upgrade mode by holding down the little button as your turn it on.
You would then tftp the firmware.


Here is a copy and paste of something more in detail.

Quote:
Assign your tftp host with a static IP address of 192.168.1.100 with 24bit
subnet mask (255.255.255.0).
Using the command line interface (CLI) to tftp the image will work fine.
Get a command shell ready to go with the
tftp command(on windows c:\>tftp -i 192.168.1.20 RS.dd-wrt.bin put)in this example,
the DD-WRT image is located in the root of C drive.
It's advisable to use a switch or hub since you will need to switch the
tftp host interface to the LAN1 port after pushing the DD-WRT image thru
the WAN interface of the Ubiquity Routerstation (ubntRS).
Connect tftp host to switch/hub.
Get a second command shell ready & start continuous ping of the
WAN interface of the ubntRS (c:\>ping 192.168.1.20 -t)..
.connect the "data" side of PoE to your switch/hub..
.have the PoE side ready to plug into ubntRS..
.Hold the reset button on the ubntRS & connect to PoE and
continue holding reset button for 10seconds & then release.
A couple of seconds later you will see ICMP echo (ping) from
the ubntRS in the command window on 192.168.1.20 &
this is when you should now issue the tftp command as listed above.
It will take a few seconds for the tftp image to push to the ubntRS
but it will let u know if successful.
Once the DD-WRT image is transfered ubntRS will lose ICMP echo (reply)
as seen in your continuous ping command shell.
Without power cycle of ubntRS, you can move your tftp host to the LAN1 interface of the
ubntRS.
It will take about 5minutes for the image to reboot on the ubntRS..
.while thats happening, you can start another ping on
the LAN1 interface with "c:\>ping 192.168.1.1 -t" and once you get replies
you should be able to use your browser to access the DD-WRT firmware web interface.
Here's a couple of notes:
if you have any "cached" DD-WRT credentials from this ubntRS or
any other DD-WRT device that you have worked with on this computer,
you might get the jacked up "black & white" DD-WRT login page..
.simply access the interface with the full URL & you should
get in "http://192.168.1.1/index.asp"..
.remember, this DD-WRT image requires activation...happy flashing....cheers...;-}