Modify

Opened 10 years ago

Closed 3 years ago

#684 closed enhancement (no_response)

last steps to support wrv54g / ixp425

Reported by: common Owned by: kaloz
Priority: low Milestone: Features Paradise
Component: kernel Version:
Keywords: wrv54g xscale ixp425 Cc:

Description

the relevant steps left to flash a wrv54g with openwrt on serial console
( i did not create images for flashing via webinterface )
i'm sorry the long urls will break the layout.

1) add wrv-bin from openixp to create the image
http://openixp.devel.phj.hu/cgi-bin/trac.cgi/browser/target/utils/src/wrv-bin.c

2) add the zLoader from openixp
http://openixp.devel.phj.hu/cgi-bin/trac.cgi/browser/target/linux/image/wrv54g/kernel-loader/files/loader.S
and logic to compile it
http://openixp.devel.phj.hu/cgi-bin/trac.cgi/browser/target/linux/image/wrv54g/kernel-loader/Makefile

3)
add the mtd patch for the openrg partition table:
http://openixp.devel.phj.hu/cgi-bin/trac.cgi/browser/target/linux/linux-2.6/wrv54g/patches/wrv54g/040-gtwx5715-mtd-parts.patch

4)
fix this bug:

mount
/dev/root on / type jffs2 (rw)
none on /dev type devfs (rw)
none on /proc type proc (rw)
none on /tmp type tmpfs (rw,nosuid,nodev)
none on /dev/pts type devpts (rw)
none on /sys type sysfs (rw)

so the image still exists after you reboot.

5)
add the intel ixp patches to support the ixp ethernet devices
http://openixp.devel.phj.hu/cgi-bin/trac.cgi/browser/target/linux/linux-2.6/wrv54g/ixp4xx.mk
http://openixp.devel.phj.hu/cgi-bin/trac.cgi/browser/target/linux/linux-2.6/wrv54g/patches/wrv54g/030-ixp400-Kconfig.patch
http://openixp.devel.phj.hu/cgi-bin/trac.cgi/browser/target/linux/linux-2.6/wrv54g/patches/wrv54g/031-ixp400-Makefile.patch
http://openixp.devel.phj.hu/cgi-bin/trac.cgi/browser/target/linux/linux-2.6/wrv54g/patches/wrv54g/032-ixp400-linux26.patch
http://openixp.devel.phj.hu/cgi-bin/trac.cgi/browser/target/linux/linux-2.6/wrv54g/patches/wrv54g/035-ixp400_eth-Kconfig.patch
http://openixp.devel.phj.hu/cgi-bin/trac.cgi/browser/target/linux/linux-2.6/wrv54g/patches/wrv54g/036-ixp400_eth-Makefile.patch
http://openixp.devel.phj.hu/cgi-bin/trac.cgi/browser/target/linux/linux-2.6/wrv54g/patches/wrv54g/037-ixp400_eth-linux26.patch
http://openixp.devel.phj.hu/cgi-bin/trac.cgi/browser/target/linux/linux-2.6/wrv54g/patches/wrv54g/038-ixp400_eth-vlan.patch

6)
support the kendin vlan switch via kernel config and add a script to set default vlans
http://openixp.devel.phj.hu/cgi-bin/trac.cgi/browser/target/linux/linux-2.6/wrv54g/patches/wrv54g/015-spi-bus.patch
http://openixp.devel.phj.hu/cgi-bin/trac.cgi/browser/package/base-files/default/etc/kendin

7) add support for prism54 based minipci cards

8) add a line that creates the bin image:

../staging_dir_armeb/bin/wrv-bin /share/hda4/openixp/build_armeb/linux-2.6-wrv54g/zLoader ../build_armeb/linux/arch/arm/boot/zImage openwrt-xscale-2.6-jffs2-128k.img openwrt-wrv54g-2.6-jffs2.bin

while in the bin directory worked for me (here you see the zLoader file from above again)

9) flash via tftp from openrg bootloader console:
load -u tftp://192.168.2.3/image.bin -s 2

10) prepare to get drunk if i ever meet you in the country of good beer

Attachments (0)

Change History (39)

comment:1 Changed 10 years ago by nbd

  • Milestone changed from 0.9/rc6 to Kamikaze

comment:2 Changed 10 years ago by Carlo Pires

What is the status of this in kamikaze? It's possible to play with wrv54g and kamikaze already ?

comment:3 follow-up: Changed 9 years ago by svk

UP! Does kamikadze support wrv54g?

comment:4 in reply to: ↑ 3 Changed 9 years ago by jo

Would interesting..!

comment:5 follow-up: Changed 9 years ago by mangoo

It looks that http://openixp.devel.phj.hu died... All pages seem to give give error 404.

Does someone work on wrv54g?

comment:6 Changed 8 years ago by ppc52776

Does current openwrt(r10380) works on wrv54g now ?

comment:7 Changed 8 years ago by disavowed

I've been trying this the last couple of days... while it does now support the ixp4xx chip, it lacks the ability to create the zLoader and create the correct image. I've tried uploading without this and the router fails to boot :-(

I'm trying to get the zLoader stuff to work with kamikaze, but it aint goin well :-(

comment:8 follow-up: Changed 8 years ago by disavowed

Just a quick update.. i've manged to create a profile for openwrt and get it to build both the wrv tools and the zLoader. Annoyingly the zLoader is created incorrect, and it seems that GCC messes up one of the instructions in the assembly code. I haven't tried using 4.0.2 (what OpenIXP uses yet, its on my list). Using a prebuild zLoader from OpenIXP and the kernel from OpenWRT i managed to get it to boot, though it seems to freeze when mounting the root fs.

I've altered a lot of the patches from the IXP tree to get them to work with WRT, though still no avail, using either JFFS2 or squashfs as the rootfs it fails. I've also hacked together a profile for the wrv54g, to make building easier.

If the dev's are still interested I can post what i've got/done so far (*hopes*)

comment:9 Changed 8 years ago by anonymous

Hi, could you post how and what you did?

I have one such device, maybe I'll do some testing?

comment:10 in reply to: ↑ 8 Changed 8 years ago by anonymous

Replying to disavowed:

If the dev's are still interested I can post what i've got/done so far (*hopes*)

Yes, they are! Please let us get this working. (I'm here to test something if you want...)

comment:11 Changed 8 years ago by disavowed

Hi guys, just a quick post (will do a big one soon). I have got Kamikaze working on it, after porting most of the patches from the IXP tree. Im still having to use a precompiled zLoader as newer versions of GCC have a slightly different output from the assembly code.

A bootable image is created :D and the router loads fine, with it repartitioning the flash the first time (as in IXP), and then doing a normal boot after that. I had to edit the pre-init script for that, to check if it was running on the GTWX9715 platform (nasty hack im sure).

My current issue is that the ethernet support is non-existant, despite the in-kernel IAL stack. Im in the process of trying to get the GPL driver from Intel to work with it (either the 2.4 or 3.0 ver), but its having problems on compilation. Im hoping to get this sorted soon as everything else works.

I will try and do some more work on it and upload the patches etc, but atm im doing my final exams so time is pretty tight.

comment:12 follow-ups: Changed 8 years ago by disavowed

Quick update, I now have the WAN port working perfectly using the in-kernel stack, and the LAN ports are working, but there's a catch. To use the LAN ports the Kendin switch driver is needed, based on the SPI stack. After a good few attempts to port it to the new SPI stack, I ended up replacing the new stack with the old (yes I know this is very bad!). If anyone out there is good with C, and fancies a challenge, HELP!

With this done, the switch can be enabled on the command line, there is however a problem. In the ethernet config the driver only listens to a specific phy, so the switch<>router connection is only activated if a cable is connected to a certain port. Im looking at how to fix this both in the driver, and by telling linux to ignore the cable state. Any suggestions welcome.

I will try to get the patch collection sorted out and posted asap

comment:13 in reply to: ↑ 12 Changed 8 years ago by jal2@…

Replying to disavowed:

With this done, the switch can be enabled on the command line, there is however a problem.
In the ethernet config the driver only listens to a specific phy, so the switch<>router
connection is only activated if a cable is connected to a certain port.
Im looking at how to fix this both in the driver, and by telling linux to ignore
the cable state. Any suggestions welcome.

Couldn't you tell the driver to take the link state from the port (no. 5) where the IXP425 is connected to? It's supposed to be up all the time.

comment:14 in reply to: ↑ 12 Changed 8 years ago by anonymous

Replying to disavowed:

Quick update, I now have the WAN port working perfectly using the in-kernel stack, and the LAN ports are working, but there's a catch. To use the LAN ports the Kendin switch driver is needed, based on the SPI stack. After a good few attempts to port it to the new SPI stack, I ended up replacing the new stack with the old (yes I know this is very bad!). If anyone out there is good with C, and fancies a challenge, HELP!

With this done, the switch can be enabled on the command line, there is however a problem. In the ethernet config the driver only listens to a specific phy, so the switch<>router connection is only activated if a cable is connected to a certain port. Im looking at how to fix this both in the driver, and by telling linux to ignore the cable state. Any suggestions welcome.

I will try to get the patch collection sorted out and posted asap

Do you have an update for us? Did your patches make it into Kamikaze 8.08?

comment:15 in reply to: ↑ 5 Changed 8 years ago by anonymous

Replying to mangoo:

It looks that http://openixp.devel.phj.hu died... All pages seem to give give error 404.

Does someone work on wrv54g?

try:
svn co svn://openixp.devel.phj.hu/openixp openixp

Still works. It is just trac that's not maintainedfor some reason.

comment:16 Changed 8 years ago by disavowed

Apologies for my very late reply, i've now restarted work on this device and have subscribed to the openwrt-devel mailing list. I've submitted some patches to make the device boot, though i'm still working on it.

Hopefully we can sign this device off soon enough :-)

comment:17 follow-up: Changed 8 years ago by jvasco@…

It's best to skip trying to use the existing bootloader and put redboot instead. The switch can be made with jungo-image.py found in the scripts directory on the trunk. This requires firmware 2.03 (copy found at http://www.seattlewireless.net/LinksysWrv54g). See http://wiki.openwrt.org/OpenWrtDocs/Hardware/Actiontec/MI424-WR for more details.

comment:18 in reply to: ↑ 17 Changed 8 years ago by johnrw

Replying to jvasco@verizon.net:

It's best to skip trying to use the existing bootloader and put redboot instead. The switch can be made with jungo-image.py found in the scripts directory on the trunk. This requires firmware 2.03 (copy found at http://www.seattlewireless.net/LinksysWrv54g). See http://wiki.openwrt.org/OpenWrtDocs/Hardware/Actiontec/MI424-WR for more details.

SeattleWireless.net seems to be under attack... ddos 150MB/sec so they have been temporarily null routed. (Sure, I used the whois and called.)
Use http://google.com/search?q=cache%3Awww.seattlewireless.net%2FLinksysWrv54g temoprarily.

Doesn't that Actiontec have the same switch...
well... Here Brainslayer says something curious about the WRV54G's Kendin switch hookup... requiring special driver handling. https://www.dd-wrt.com/phpBB2/viewtopic.php?p=57801 So... maybe that's why Ajit (mankash on irc) can't get the switch to work, but has a working RedBoot otherwise. But Brainslayer was also complaining that he had received a donation that was bricked and didn't seem to think any effort was justified on this model. He also notes that avila gateworks GW2345 has hardware similar.

comment:19 Changed 7 years ago by anonymous

Hi
Is this thread dead??
Or is there still some progress on the WRV54G ??

regards
grif

comment:20 Changed 7 years ago by disavowed

I submitted a set of patches to the mailing list a while back that got the device booting with the standard bootloader, and things seemed to work ok (didnt test switching vlan's on the switch). The patches seem to have been forgotten about though.

I still use my wrv54g (with an atheros card) and it works pretty well. Last time i tried though I couldn't get it to resize the flash properly. I just got an email on the dev list about some redboot firmware for it, so I might give it a go at some point (dont want to brick it though)

comment:21 Changed 7 years ago by eloy2125

Sorry but anyone have the files for upgrade my wrv54g, this files not exist in the web :(

comment:22 Changed 7 years ago by kalikid021

I would love to find out if someone has gotten OpenWRT working on this hardware, I would be very thankful for any information. Thanks!

comment:23 Changed 7 years ago by qlippoth@…

Me too... *sigh*.

comment:24 follow-up: Changed 7 years ago by matein4

I've gotten this device to work using the same approach as used for Actiontec's MI424-WR. I've created a redboot for it here: http://mysite.verizon.net/jvasco/openwrt/rb-wrv54g-ROM.bin

The only problem that I ran into was with the Prism WiFi card. It sort of worked but it was unreliable and unusable after a short duration. The last time I tried was before Kamikaze was released so things may have changed in the meantime.

comment:25 Changed 7 years ago by anonymous

hi,matein4

i try atheros5416, is ok. work on the last trunk.

user ath9, work on the AP mode. speed 6MB/S

comment:26 in reply to: ↑ 24 Changed 7 years ago by sniperpr@…

Replying to matein4:

I've gotten this device to work using the same approach as used for Actiontec's MI424-WR. I've created a redboot for it here: http://mysite.verizon.net/jvasco/openwrt/rb-wrv54g-ROM.bin

The only problem that I ran into was with the Prism WiFi card. It sort of worked but it was unreliable and unusable after a short duration. The last time I tried was before Kamikaze was released so things may have changed in the meantime.

hi,matein4

i try atheros5416, is ok. work on the last trunk.

user ath9, work on the AP mode. speed 6MB/S

comment:27 Changed 7 years ago by anonymous

Can someone post a working image? openwrt buildroot has deps I don't want to install on my server.

comment:28 Changed 7 years ago by tek

I am also waiting for an image or instruction on how to compile a kernel on debian/ARM.
I have a couple of unit and Cisco seems not interested on updating their firmware.

comment:29 Changed 6 years ago by thepeople

  • Milestone changed from Kamikaze to Kamikaze Features Paradize
  • Priority changed from high to low

comment:30 Changed 6 years ago by anonymous

anyone?

comment:31 Changed 6 years ago by tol-ric@…

It would be nice to have a hardrive since it has two mini PCi slot. Here is what I have in mind.
AX8930 Mini PCI ultra 160 SCSI module (Adaptec) or
MIO-3140 (Silicon Image) or
PartNo: MP6421 (VIA VT6421A Chipset)

comment:32 Changed 6 years ago by tol-ric@…

Wi-Fi is not important.

comment:33 Changed 6 years ago by anonymous

i would use openixp if wifi is not important, for lan only its working very well. why not an alix1d?

comment:34 follow-up: Changed 6 years ago by matein4

I'm using OpenWrt (rev 21231) and everything seems to be working pretty well. The only thing missing is the LED control. The original WiFi card (prism) is doing fine now.

It requires that a custom image be built. Make sure to use make kernel_menuconfig to select Gemtek WX5715. Also add the appropriate WiFi interface.

comment:35 Changed 6 years ago by anonymous

matein4, is prism54 working well or do you mean p54pci whith hostapd?

comment:36 Changed 6 years ago by anonymous

Mind releasing a flash-able image so technically challenged can use it?

comment:37 in reply to: ↑ 34 Changed 6 years ago by anonymous

Replying to matein4:

I'm using OpenWrt (rev 21231) and everything seems to be working pretty well. The only thing missing is the LED control. The original WiFi card (prism) is doing fine now.

It requires that a custom image be built. Make sure to use make kernel_menuconfig to select Gemtek WX5715. Also add the appropriate WiFi interface.

can you please post the image ?

THanks

comment:38 Changed 6 years ago by g.woloszyn@…

Hello,

I'm also interested in matein4 rom.

Thank you

comment:39 Changed 3 years ago by tripolar

  • Resolution set to no_response
  • Status changed from new to closed

no activity since 3 years. closing the bug. if still needed please reopen a new one.

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.