Firmware compatible to Wireless Space?

[Jocko]

Hi Redstorm,

I don't understand well what you mean here:

Wireless Space IP fixed to 192.168.0.1

192.168.0.1 should be the IP of the gateway (Router / DHCP server) and so the Ip address of your WS will be 192.168.0.252

[Redstorm]

Hi Redstorm,

I don't understand well what you mean here:

Wireless Space IP fixed to 192.168.0.1

192.168.0.1 should be the IP of the gateway (Router / DHCP server) and so the Ip address of your WS will be 192.168.0.252

Apparently complicated, really simple the "test net " is made of two machines.
192.168.0.1 is the Wireless Space , and this is the address I write in the console in the field I understand is the TARGET ADDRESS.
192.168.0.10 is a Lenovo R61 with XPPro, directly connected to the Wireless Space with a cable.

The basic test is the use of network shares by Lenovo.
No router, no gimmick, if it is not there, cannot :hammerhead break, isn't it?

Maybe that I am incorrectly using fvdw-console? Every recommendetation is welcome.

I understand from the manual that the WS has a built in recovery mode, in which the "WAN" port assumes a172.0.x.1 address as boot time: maybe this the way to get in?

Peter

[Jocko]

:shocked :shocked :shocked

You must have a router : ie your ISP box.

And on the ISP box, you must enable the DHCP server (it must be available by default) and set a gateway 192.168.0.1 or 192.168.1.1. (with an ip mask 255.255.255.0).

So connect your Lenovo R61 (wireless or network cable) to your ISP box and do the same thing with your WS by using a network cable.

Then when you will use the fvdw-sl console and start the WS, this one will have as IP address : 192.168.0.252 (or 192.168.1.252)

[Redstorm]

o.k. but now I am in trouble.
I understand that everything happens during pre boot time slot, and that BOTH WS and PC will get from the Router their address.
last question: i am supposed to connect the cable on the WS on the WAN port, because the WS itself is a Router.
Correct?

Regards
Peter

[Jocko]

Ah I understood what you wanted to do.

WS can be a router/DHCP only if it is working but it's not your case... So you must use it as an host on your LAN and connected on another router.

[fvdw]

you must use the LAN1 port on your wireless space (ws) (so not LAN2 or LAN3)
To load and run the standalone kernel we don't need necessarily a dhcp server but the LAN should allow use of IPs' n the range of 192.168.1.x or 192.168.0.x

If the standalone kernel doesn't seems to run by loading it directly we can try to run it form u-boot terminal console and enable netconsole output to see if we get info were there kernel fails

To do this switch off your ws, then fire up the fvdw-sl console, start the the tftp server and then choose the action u-boot console
A command window will pop up mentioning that it is waiting for u-boot
Now start the ws
The u-boot console should intrupt boot and ask you to click on it., now you get a Marvell>> prompt in the u-boot console window.
Now we are talking to u-boot running on the ws.
Set boot parameters by entering after this prompt these commands
(do not replace ip addr and serverip and so on by actual ip's, type the command exactly as given)

Code: Select all

Marvell>> setenv ipaddr ${ipaddr}; setenv serverip ${serverip}
Marvell>> setenv bootargs console=ttyS0,115200 netconsole=6666@${ipaddr}/,6666@${serverip}/ root=/dev/sda7

(you can paste it in the window, right click on title bar of the window and choose edit)

Then upload the kernel

Code: Select all

Marvell>> tftpboot 0x800000 UIMAGE-395-NWSP2CL-178-standalone

this will give output that it uploads the kernel and mention when it is done

next boot the kernel

Code: Select all

Marvell>> bootm

and see what happens. If it loads and produce output we need that output to see what can be done to solve the problem

[coelhonet]

Hey there! Sorry for being away for long. I started this thread and came back here many times, but for some reason things changed for good and I was not here.

So, I'm ready to test whatever you have. I'll prepare to backup my data, so I can have WS ready for whatever it comes.

Sorry for taking too long to answer this one and thanks a lot for working on this matter.

[fvdw]

I need to dig up the trial kernel I made, that is the first condition we have to fullfill, a running kernel. The WS has its own mainboard and needs a dedicated kernel. PS do jou have access to via the serial console ? if not we can still try to get it running but if the kernel fails to load it will become difficult to find the reason.

[coelhonet]

Hey there!

No serial console access. I can try to make it, but have to dig into how to make it and what cables I need before moving on.

If it's a must, let me know, so I'll make it.

Thanks again!

[fvdw]

lets first try if our standlone kernel for wireless space works. It is a kirkwood based device and the kernel contains support for the wireless space. I included a setup file but chave never test it.

To test download the latest fvdw-sl console (viewtopic.php?f=7&t=1271) and choose action load and start standalone kernel. It will ask which kernel to load, select when asked UIMAGE-395-NWSP2CL-179-standalone and see if you can log in with the telnet client (see instructions of the the fvdw-sl console)