Firmware compatible to Wireless Space?

[coelhonet]

Ok, got it!

I requested a USB to Serial (PL2303). Hopefully this will help me on setting up a local console.

Should get it until Wed next week.

When I get it, I'll test and post results here.

Thanks!

[coelhonet]

Hello!

So, I got a Prolific USB to Serial adapter. Installed on my Windows set 115200,8,N,1 on it and opened TeraTerm to connecti via serial console.

I plugged TX/RXon supposed to be RX/TX on J2 (I'd say pins 7 and 8 respectively) and also 3.3V and GND (pins 1 and 2 respectively).

I got nothing on my screen when booting up Lacie Wireless Space. Any idea on what could be wrong here?

Thanks!

[fvdw]

baud rate should be 115200, 8 data bits, 1 stop bit, parity none, flow control xon/xoff (probably none for flow control will do)
Of course you need to use the right com port as well, (see device managere windows to find the right com port)
Also the adapter should have TTL level voltage (3,3 V) but from your post I make up it is a 3,3 V one. If this adapter is not TTL level then the voltage level it supplies might be 5 V instead of 3.3 V.
Then it wont work and may damage the board.

When it connect properly you should at least see u-boot loading and that reporting it loads and boots the kernel, after that the kernel out should follow. If you don't see the u-boot output then a not properly setup communication is the problem.
Look here to check out your setup: http://lacie.nas-central.org/wiki/Seria ... space_2%29

ps I use Putty for serial connection.

maybe you could try to switch rx and tx connection (pin 7 and 8 on the board)

ps the serial connection will not give output if you open connection when the lacie is power up. You need to have an open connection and then power up the lacie

[coelhonet]

Hi!

Thanks for your guidance! Good news! I can get console output!
So, I used a digital multimeter to find out where 3.3V and GND where on J2 at PCB. On Network Space 2 TX is near to power switch button and on opposite side you hava VC 3.3V. That's not the case on Wireless Space.
I can take a picture and point where they are, but on a text format, here is layout on Wireless Space:

--------------(Power Switch)------|
O | VC 3.3V
O | GND
O |
O |
O |
O |
O | TX
O | RX
|

Maybe it's just my USB adapter that has TX and RX twisted, but that's the way it worked.

Attached you have normal boot from LaCie Wireless Space firmware and another one with FVDW firmware. Now that I have console access we can try to moving on debugging.

Thanks once again!

[fvdw]

:thumbup that looks not bad at all for a first shot and the output is very helpful to find the issue
The fvdw-sl standalone kernel loads but has a problem with initializing the ethernet driver. This is the the reason why we cannot connect wit the telnet client. The busybox errors are wei5rd, but that is of later worry, first we need to get the ethernet driver working.
Seems it needs a different driver then other kirkood, in the lacie kernel boot output you see this INIT Marvell Ethernet Driver: mv_netdev
Need to see if that one is present in the linux kernel source

I arrived home late tonight so not a job for this evening, tomorrow evening I will make some adaptations to the kernel setup file for this device, I am pretty confident that we can compile a suitable kernel for this device only issue is the ethernet driver.

--- edit
A quick look to lacie kernels output of other kirkwood device it seems Lacie uses also on nwsp2 this mv_netdev driver in their kernels. In the vanilla kernel the mv643xx_eth driver is supplied and that works also on the other kirkwood devices like nwsp2 , 2big2 and 5big2, as proven by the our kenrels running with that driver on these boards. I think a simple modification of the load address may solve it

[coelhonet]

NP, when you have time I can push new version to my box.

If there's something I can do at my side, let me know.

Also, not sure if it'll make any difference later which ethernet port I should use to connect to the box.

Thanks once again!

[fvdw]

attached a new standalone kernel, please try

To load it via fvdw-sl console unzip the archive and put the kernel in the tftp folder of the fvdw-sl console

[coelhonet]

Hey!

Thanks for quick reply.

Not working yet.

Attached you have stdout.

Thanks!

[fvdw]

mmm..same error, I changed the address were the ethernet driver was loaded but that doesn't seems to be the problem. :scratch
In the setup file it initialize two ethernet platform drivers because it has mutiple interfaces. From the error output it goes wrong with registering these platform drivers, it mentions that we try to initialize something that already is initialized. This is weird because settings for both are different.
Anyhow in the next trail kernel I will disable one and see what that brings
in the afternoon it will be posted, I will put the compiler at work

[fvdw]

a new trial standalone kernel for testing