Firmware compatible to Wireless Space?

[fvdw]

happy new year, yes you have been away somewhat longer then 2 weeks :twak you could have left a message

Anyhow in the meantime I got a used wireless space.
I have found a way to get the three LAN ports working with using a custom kernel but...the setup of this device is quit different from the other lacie devices. It has only 4 partitions on the disk (instead of 8 on the others) and it loads the kernel and root file system from nand flash. It also looks on partition one of the disk to load a linux kernel and load it using ext2load.
The user data (shared folders) are on sda4 on this device
some info on the setup when running lacie firmware

Code: Select all

USER_FS=/dev/sda4
WRITE_FS=/dev/sda3
ROOT_FS=/dev/sda1
SWAP_PART=/dev/sda2
BACKUP_ROOTFS=/dev/mtdblock3
#
ROOT=300M
WRITE=100M
SWAP=256M
# Must be the sum of the 2 above
ROOTSWAP=556M
# Must be the sum of the 3 above
ROOTSWAPWRITE=656M
DATA_FS=xfs
DO_SPINDOWN=1

gdisk output for partiton table(it is a disk with gpt table)

Code: Select all

Disk /dev/sda: 1953525168 sectors, 931.5 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 5CCEB263-D07C-4566-AAA1-4A5C27F1C227
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 1953525134
Partitions will be aligned on 8-sector boundaries
Total free space is 0 sectors (0 bytes)

Number  Start (sector)    End (sector)  Size       Code  Name
   1              34          585937   286.1 MiB   0700  primary
   2          585938         1085937   244.1 MiB   0700  primary
   3         1085938         1281250   95.4 MiB    0700  primary
   4         1281251      1953525134   930.9 GiB   0700


Code: Select all

root@LACIE# cat /proc/partitions
major minor  #blocks  name

   8     0  976762584 sda
   8     1     292952 sda1
   8     2     250000 sda2
   8     3      97656 sda3
   8     4  976121942 sda4
  31     0       1024 mtdblock0
  31     1       3072 mtdblock1
  31     2       4096 mtdblock2
  31     3     122880 mtdblock3
root@LACIE#

mount output (lacie firmware)

Code: Select all

root@LACIE# mount
rootfs on / type rootfs (rw)
/dev/root on / type ext3 (ro,data=ordered)
tmpfs on /etc type tmpfs (rw)
none on /proc type proc (rw)
none on /sys type sysfs (rw)
tmpfs on /tmp type tmpfs (rw)
/dev/sda3 on /lacie/var type ext3 (rw,data=ordered)
/dev/sda4 on /lacie/var/userPart type xfs (rw)
usbfs on /proc/bus/usb type usbfs (rw)
/dev/root on /dev/.static/dev type ext3 (ro,data=ordered)
udev on /dev type tmpfs (rw)
root@LACIE#

serial console

Code: Select all

           _           ____ _
          | |    __ _ / ___(_) ___
          | |   / _` | |   | |/ _ \
          | |___ (_| | |___| |  __/
          |_____\__,_|\____|_|\___|
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_
| | | |___|  _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
 \___/    |____/ \___/ \___/ \__|
 ** MARVELL BOARD: ASTON_WS_GN3 REV: 2 LE
Hold rear button - long :  FAIL


U-Boot 1.1.4 (Jul 27 2011 - 17:43:51) Marvell version: 3.4.16  LaCie 1.5.22 256MB

U-Boot code: 06000000 -> 0607FFF0  BSS: -> 060CE600

Soc: MV88F6281 Rev 3 (DDR2)
CPU running @ 800Mhz L2 running @ 400Mhz
SysClock = 200Mhz , TClock = 166Mhz

DRAM CAS Latency = 3 tRP = 3 tRAS = 9 tRCD=3
DRAM CS[0] base 0x00000000   size 256MB
DRAM Total size 256MB  16bit width
Flash:  0 kB
Addresses 98M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (98M - 97M): Done
NAND:
Addresses 98M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (98M - 97M): Done
NAND:128 MB

CPU : Marvell Feroceon (Rev 1)

Streaming disabled
Write allocate disabled

Module 0 is MII

USB 0: host mode
PCI 0: PCI Express Root Complex Interface
PEX interface detected Link X1


Reset IDE:
Marvell Serial ATA Adapter
Integrated Sata device found
[0 0 0]: Enable DMA mode
  Device 0 @ 0 0:
Model: ST1000DM003-9YN162                       Firm: CC4B     Ser#:             W1D0M0YS
            Type: Hard Disk
dev_desc->blksz = 512
            Supports 48-bit addressing
            Capacity: 953869.7 MB = 931.5 GB (1953525168 x 512)

## Valid EFI partition found ##
## Valid EFI partition found ##

** Unable to read "/boot/uImage" from ide 0:1 **

## Checking Image at 00800000 ...
   Bad Magic Number

NAND read: device 0 offset 0x100000, size 0x300000

Reading data from 0x1cf000 --  27% complete.
Bad block at 0x3a0000 in erase block from 0x3a0000 will be skipped
Reading data from 0x41f800 -- 100% complete.
 3145728 bytes read: OK
## Valid EFI partition found ##
## Valid EFI partition found ##

** Unable to read "/boot/uInitrd_m" from ide 0:1 **

## Checking Image at 01200000 ...
   Bad Magic Number

NAND read: device 0 offset 0x400000, size 0x400000

Reading data from 0x77a800 --  87% complete.


Reading data from 0x7ff800 -- 100% complete.
 4194304 bytes read: OK
## Booting image at 00800000 ...
   Image Name:   Linux-2.6.22.18
   Created:      2010-08-20   7:20:22 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2479736 Bytes =  2.4 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK
bootargs from environment variables : initrd=0x1200000 root=/dev/mtdblock3 ro console=ttyS0,115200 cap=gpt,lba64
## Loading Ramdisk Image at 01200000 ...
   Image Name:   8M_ramdisk
   Created:      2010-08-20   8:54:44 UTC
   Image Type:   ARM Linux RAMDisk Image (uncompressed)
   Data Size:    3387392 Bytes =  3.2 MB
   Load Address: 01200000
   Entry Point:  01200000
   Verifying Checksum ... OK

Starting kernel ...

Uncompressing Linux............................................................................................................................................................ done, booting the kernel.



To use this device with fvdw-sl firmware some basic changes will be needed besides a custom kernel. But all possible to do.
I will first look around in the u-boot version on this device to see if we can customize the u-boot commands used to boot the device on the other devices there was a backdoor that enables use of custom boot commands.

--edit
:punk yep backdoor is availble, so it will be relative easy to let it boot the firmware, now need to make a decent kernel

[coelhonet]

Shame on me...

So, first I had a bad HD and couldn't proceed on testing, now I got a spare, but I can see you got one in your hands as well.

Not a apologized action I did, I should let you know.

Anyway, I'm back for beta testing if needed and if you have time for a new project like this, since as you said it's not same as other devices.

Thanks!

[fvdw]

I stopped the project in the beginning of the year due to lack of interest :dry
But I got a working kernel that used one if the ethernet ports, if I remember well I was struggling to get the internal bridge working to use also the other ethernet ports.

I will look one of these days if I can pick it up again.

[coelhonet]

Sure thing! Not your fault.

If you have time for, that's ok, if not, I completely understand.

Thanks!

[fvdw]

just for info I restarted this project.
Coming week more news, first need to restudy what i did so far

[coelhonet]

Awesome! My device is just ready for testing! Let me know. Thanks!

[fvdw]

Ok in principle the kernel runs, the problem is setting up the network interface. This device uses a ethernet switch to use all the ports on the back (just like a router). As result the normal eth0 and eth1 interface can not be setup as usual. I have a 3.9.5 kernel on which I got the switch working and can set LAN1-LAN3 as interface. To use them with the firmware we need to make some adaption of the scripts that setup the networkinterface, as it should use for WS LAN1-LAN3 iso eth0 or eth0
However have a problem to get the switch wortking on the 3.14.2 kernel. They made some changes in the kernel surcing affecting the communication between etho, 1 port and the switch. As result the kernel cannot indentify the switch. As result of that we can only use for the moment on that kernel a fixed setuip of eth0 and with no possibillity to auto negotiate speed/duplex and no dhcp.
I prefer to use the 3.14.2 kernel as is standard for the other kirkwoods, also 3.9.5 kernel has some bugs. I will try to figure out were the problem is but it will take some time

[coelhonet]

Ok, understood! I'd believe it's better to use same kernel you are using for other devices and also you know that older version has some bugs that got fixed. Take your time, I know you have a device with you, what clearly helps, but I can test overseas. Thanks a lot!

[fvdw]

it is done, I have a working standalone and normal kernel that supports the wireless space
This weekend I will sent you some files for testing

[coelhonet]

Awesome! Thanks a lot!