OpenWrt Forum Archive

Topic: Support for Marvell 88F5xx81 based routers

The content of this topic has been archived between 18 Jan 2014 and 6 May 2018. Unfortunately there are posts – most likely complete pages – missing.

heji wrote:

I have upgraded 128m ram successfully .
    __  __                      _ _
        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  __/ | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
_   _     ____              _
| | | |   | __ )  ___   ___ | |_
| | | |___|  _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
\___/    |____/ \___/ \___/ \__|  ** LOADER **
** MARVELL BOARD: RD-88F5181L-VOIP-GE LE

U-Boot 1.1.1 (Dec 12 2006 - 16:12:22) Marvell version: 1.7.3

DRAM CS[0] base 0x00000000   size 128MB
DRAM Total size 128MB

Do you mind sharing how? DRAM Model etc...

That's a huge leap of faith by the way, gutsy move!

Kudos!

Except for the webupgrade-builder Kaloz has integrated all wrt350n support into trunk (r13604 and upwards).

I'm now testing the latest WIFI-AP patches and so far it is running smoothly. Ofcourse I don't want to jump to conclusions so it's a matter of time to know for sure if it's stable now. Will post back later.

(Last edited by dirkNL on 15 Dec 2008, 02:13)

You guys are awesome.

heji wrote:

I have upgraded 128m ram successfully .
    __  __                      _ _
        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  __/ | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
_   _     ____              _
| | | |   | __ )  ___   ___ | |_
| | | |___|  _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
\___/    |____/ \___/ \___/ \__|  ** LOADER **
** MARVELL BOARD: RD-88F5181L-VOIP-GE LE

U-Boot 1.1.1 (Dec 12 2006 - 16:12:22) Marvell version: 1.7.3

DRAM CS[0] base 0x00000000   size 128MB
DRAM Total size 128MB
Flash: mvFlashInit base 0xff800000 devW 1 busW 1
Flash: flashStructGet manu 0xec id 0xe0
Flash: flashStructGet flash is supported.
FLASH: initFlashSecs TOP Sector Type
Flash: flashSecsInit main sector loop 0 - 127
[8192kB@ff800000] Flash:  8 MB
Addresses 20M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (20M - 16M): Done
*** Warning - bad CRC, using default environment


Soc: MV88F5181 Rev 9
CPU: ARM926 (Rev 0) running @ 500Mhz
SysClock = 166Mhz , TClock = 166Mhz

can you tell me how to modify the uboot to support  128M ram , plz ?


HY5DU121622CTP-D43 should be ok, but i dont't know how to modify the uboot.

(Last edited by kmper on 20 Dec 2008, 11:32)

http://forum.dsmg600.info/viewtopic.php?id=2388&p=1

DNS-323 Custom Firmware » 128MB RAM Upgrade Details


i upgrade the memory ,but i don't understand how to patch uboot . Can anyone help on this?

(Last edited by kmper on 21 Dec 2008, 11:48)

it seems works .follow the guide  http://forum.dsmg600.info/viewtopic.php?id=2388&p=1


1,  dd if=/dev/mtdblock4 of=uboot.bin
2,  patch the uboot.bin

   f1001500: 00000000 01ff0001 10000000 00000000   
==>f1001500: 00000000 07ff0001 10000000 00000000

   f1001410: 00000000 00000000 00000000 00000062
==>f1001410: 00000020 00000000 00000000 00000062

so modify two places.  (1)   SDRAM_BANK0_SIZE : the location is offset 0x315f,  01 00 ff 01  ==>  01 00 ff 07
                                 (2)  SDRAM_ADDR_CTRL_REG:the location is offset 0x19fd0, 10 60 A0 E3 ==> 30 60 A0 E3

3,   dd if=uboot.bin of=/dev/mtdblock4 bs=1 skip=12639 seek=12639 count=1 conv=notrunc
      dd if=uboot.bin of=/dev/mtdblock4 bs=1 skip=106448 seek=106448 count=1 conv=notrunc


sorry for my poor english.

(Last edited by kmper on 22 Dec 2008, 08:20)

dirkNL wrote:

Except for the webupgrade-builder Kaloz has integrated all wrt350n support into trunk (r13604 and upwards).

I'm now testing the latest WIFI-AP patches and so far it is running smoothly. Ofcourse I don't want to jump to conclusions so it's a matter of time to know for sure if it's stable now. Will post back later.

Is there any status update if wlan is stable now?

dirkNL wrote:

Except for the webupgrade-builder Kaloz has integrated all wrt350n support into trunk (r13604 and upwards).

Hi,

   I try to install openwrt in my wrt350n but without success sad. Compilation is OK and i see the two files:
          *  openwrt-orion.squashfs.img
          *  openwrt-wrt350nv2-uImage
   I try to use linksys web interface but files are rejected, probably because headers. I read quickly
trunk/target/linux/orion/image/Makefile; Kaloz seems to have provided the headers's add. So, can you indicate
me how to do it ?

   An other way is tftp. I also tried to use it but probably router doesn't use it by default ? Do you know
if there is a special way to enable it ?

   Really, you have realized a great work. I hope i could use it.

Just signed up here on the hunt for WNR854T support.. looks promising from what I've read so far, but I'm still unclear about the wifi situation with this router.
Is it working at all? (even if not stable) or has support for the wireless card not been added yet?

Also I read some things about port number 4 (i think) not working on the switch.. is that still the case?

Thanks!

To answer a couple of questions

-Wifi is stable, it no longer kernel panics every 5 minutes. However, I'm not very sure the wifi link itself is a stable signal. I've tested it with a laptop in line of sight but sometimes the signal would just die in seconds. Other times I could run it for 1 hour straight without any hasle.

-Webupgrade package isn't integrated in the buildroot, ask Kaloz about that why it isn't

-The broken port is just a matter of time, it will be fixed but that's a bit low on the priority list. FYI port 4 is down with the wrt350n, some other port is not working for the WNR854T, just a little difference on how those are connected to the switch chip.

dirkNL, thanks for the info.

I'll be keeping an eye on this thread as I need to use all the ports on my router so can't update just yet.. hopefully soon though as the stock netgear firmware is appauling!

Hi,

after reading now over 2 weeks in several post an froums , i decided to register here.
3 weeks ago I tried to flash a wrt350nv2-bin per webupdate to my router with original firmware 200.19 and at reboot it fails.
Now it seems that I have bricked my wrt350nv21, no telnet, no ping to 192.168.1.1. Resetbutton during power on results in flashing yellow/green powerLED, Also the Lan-LEDs are working.
In Wiki-page ther are described two connectors (serial and Jtag). I then tried via serial cable, Gnd,RX,TX to get connected, but it fails.
Is it necessary to have the 3.3V also connected to the serial-cable ?
Do anyone knows a possibility to get the router work without JTag ? If no, can I simply solder a jtag-connector to the PCB, or do I have to add some resistors beside the jtag, better which values of the resistors? IS a Wigglerclone ok for this, or do I need better adapter?

Sorry, for the stupid questions, but I´m a bloody newbie in this thematik, my other 4 routers i always managed to get to work via tftp, or smilar tools.


Thx for advice

Best regards

cm

where in the world are you ?

i got a serial connection from what looks the the factory as it have to right connector to my board smile

I´m in Germany and as mentioned a noob.

So do I need 3,3V or is gnd, rx, tx enough? What serial cable do you use (usb-r232, or TTL chipset) ?
Or can I use external Power supply for 3,3 v ?

Thx

cm

http://up-it.dk/dl/arxp8t/

i use a converter i got from the manifactor plant budt i think you can use a FTDI TTL-232R-3V3 cable.

Thx for advice!

Yesterday I managed to modify old Handy-T68 USB-Prolific2303-cable and got telnet to work.
The uboot 1.1 seems to be ok, and I can stop boot.
Now I have the fear to kill uboot with the wrong command.
What should I do now, erase flash? How can I get tftp work? Do I need debrick utility?
Is there enough space to modifiy the env to boot image form e.g. USB-stick?

Thx

best regards

cm

CTRL C at bootup (i think)

try booting mtd0.img via nfs on page8 of this thread from dirkNL
got my wrt350n working with this and reflashed it via webinterface

(Last edited by pregi on 19 Jan 2009, 15:42)

cmoegele wrote:

Resetbutton during power on results in flashing yellow/green powerLED, Also the Lan-LEDs are working.

If i recall correctly the yellow green flashing means its in recovery mode. You should be able to tftp the device when its in this mode.

A quick check in the wrt350n manual confirms.

The firmware upgrade failed, and/or the Power LED is flashing.
The upgrade could have failed for a number of reasons. Follow these steps to upgrade the firmware and/or
make the Power LED stop flashing:
• If the firmware upgrade failed, use the TFTP program (it was downloaded along with the firmware). Open
   the pdf that was downloaded along with the firmware and TFTP program, and follow the pdf’s
   instructions.
• Set a static IP address on the PC; refer to “Problem #2, I need to set a static IP address.�  Use the following
   IP address settings for the computer you are using:
   IP Address: 192.168.1.50
   Subnet Mask: 255.255.255.0
   Gateway: 192.168.1.1
• Perform the upgrade using the TFTP program or the Administration tab of the Router’s web-based utility.

Hi... im new to this project but i read this topic from begining.

i apriciate your work on my favourite router!

i tried flashing my compiled image but no success. now my 350n won´t boot.
i cant ping the router or do anything else with it. the only thing i can do ist hold down the reset button, while plugin the power-cord to get the power LED flashing green orange.

i tried following:
tftp
tftp> connect 192.168.1.1
tftp> put WRT350N-2.00.17_200712132250.img
Transfer timed out.
tftp>

any ideas whats wrong?

bw

(Last edited by Polly on 20 Jan 2009, 00:13)

Thx!

I  will try tomorrow with method from dirknl. With tftp I was not able to ping or flash anything I also tried IP from bootenv, but no sucess.
Perhaps my tftp utility from linksys is pretty old, but on the download section for wrt350nV2 there was nothing at all. Even other and newer tftp-tools did´nt work.

         __  __                      _ _
        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  __/ | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
_   _     ____              _
| | | |   | __ )  ___   ___ | |_
| | | |___|  _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
\___/    |____/ \___/ \___/ \__|  ** LOADER **
** MARVELL BOARD: RD-88F5181L-VOIP-GE LE

U-Boot 1.1.1 (Dec 12 2006 - 16:12:22) Marvell version: 1.7.3

DRAM CS[0] base 0x00000000   size  32MB
DRAM Total size  32MB
Flash: mvFlashInit base 0xff800000 devW 1 busW 1
Flash: flashStructGet manu 0xec id 0xe0
Flash: flashStructGet flash is supported.
FLASH: initFlashSecs TOP Sector Type
Flash: flashSecsInit main sector loop 0 - 127
[8192kB@ff800000] Flash:  8 MB
Addresses 20M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (20M - 16M): Done
*** Warning - bad CRC, using default environment


Soc: MV88F5181 Rev 9
CPU: ARM926 (Rev 0) running @ 500Mhz
SysClock = 166Mhz , TClock = 166Mhz


USB 0: host mode
PCI 0: PCI Express Root Complex Interface
PCI 1: Conventional PCI, speed = 33000000
Net:   mvEgigaLoad: egiga0 load ok
egiga0 [PRIME]

***************DRIVER INFO*****************

DRIVER BUILD DATA: Jan  9 2007 at 18:25:44
DRIVER VERSION 1.06

*******************************************
dbSign is:65:52:63:4f:6d:4d
mac address in flash is:00:1e:e5:93:e9:10

have eRcOmM

Hit ENTER to stop autoboot:  3  2  1  0
Marvell>> <INTERRUPT>
Marvell>> 
Marvell>> printenv

bootcmd=scload; bootm 0x400000
baudrate=115200
loads_echo=0
ipaddr=172.21.5.10
serverip=172.21.5.30
rootpath=/mnt/ARM_FS/
stdin=serial
stdout=serial
stderr=serial
cpuName=926
CASset=min
enaMonExt=no
enaFlashBuf=yes
enaCpuStream=no
MALLOC_len=4
ethprime=egiga0
bootargs_root=root=/dev/nfs rw
bootargs_end=:::DB88FXX81:eth0:none
image_name=uImage
bootdelay=3
disaMvPnp=no
ethaddr=00:00:00:00:51:81
overEthAddr=no
usb0Mode=host
ethact=egiga0

Environment size: 439/8188 bytes

Marvell>> reset

I see some people just flashing an image without even knowing what it might contain, if you would have _read_ this thread just like I said you should do, you would know there isn't _any_ flashable image online!!!

As long as the people at OpenWRT don't fully support this router, I'm not going to publish any binfile...

But, for the ones eager to try out what or how far we've come so far, you can build your own webupgrade image. Just checkout the OpenWRT trunk and apply my latest patch. This patch only contains the webupgrade tool for the wrt350nv2.

Note: you need "zip" on your system for this tool to work.

Now after you've ran a 'make' you see a webupgrade package in the bin dir.

PLEASE also see this post for some warnings and limitations

(Last edited by dirkNL on 23 Jan 2009, 16:16)

Just checking in on this thread to see if there is any news..
Anyone have any idea if work on getting the missing switch port working is still going on?

I have a different wireless card i can use in the router but i need all the wired port so stuck with the rubbish netgear firmware atm.
The router rebooting itself when adding port forwarding rules is pretty ridiculous.. what the hell were netgear thinking!

dirkNL: yesterday I tried compiling from scratch with your patch included using the same openwrt revision when patch was made and also with the latest revision(and also with extra packages). All the same the webimage generation failed.(right after .img deflation) Is there anyone else who has succeeded or failed in creating the web upgrade package with "new" revisions? I can provide error output later on when I'm home. Btw: Can I use the .img file to directly TFTP upload it to wrt350nV2? (Yes, I'm a rookie to openwrt)

Secondly, Thank you all to people who have put effort to bring openwrt to wrt350n V2. I would gladly see this effort brought home!