lacie 5 big network v.1 please support for fvdw

Re: lacie 5 big network v.1 please support for fvdw

Postby totorweb » Wed Oct 23, 2013 4:00 pm

hi,

looking at http://lacie-nas.org/doku.php?id=start it seems that the 5big Network is not supported by clunc, maybe this is the major cause of the boot problem ?
totorweb
 
Posts: 46
Joined: Fri Oct 18, 2013 11:28 am

Re: lacie 5 big network v.1 please support for fvdw

Postby fvdw » Wed Oct 23, 2013 5:13 pm

the 5big is supporting clunc, otherwise we could use the u-boot console

@tatae

You did not do the test with first performing
Code: Select all
marvel>> ide reset

then set env variables for netconsole support, upload with tftpboot the kernel and perform the bootm command

@mijzelf
thanks for helping to try to find the reason of this issue. But if the normal kernel boots form the standard address why shouldn't the standalone kernel not boot from that same address ?
Code: Select all
loading the normal kernel 20

Loading from IDE device 4, partition 6: Name: hde6
  Type: U-Boot
   Image Name:   Linux-2.6.39.4
   Created:      2013-09-23  18:39:53 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1871800 Bytes =  1.8 MB
   Load Address: 00008000
   Entry Point:  00008000
## Booting image at 00400000 ...
   Image Name:   Linux-2.6.39.4
   Created:      2013-09-23  18:39:53 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1871800 Bytes =  1.8 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel ...


Anyhow when loading the normal kernel u-boot uses indeed address 00400000
So why not use that instead of 1000000

ps The difference between the standalone and normal is the initram file system, the initramfs is the same as used for nwsp2, 5big2, 2big2, isp1..so I am 100% sure that it is ok. Also you would expect in that case that the kernel would not fail to load but stop as soon as init is performed.
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: lacie 5 big network v.1 please support for fvdw

Postby totorweb » Wed Oct 23, 2013 6:00 pm

I've just did the test doing a ide reset at first, same problem.

starting u-boot net console click on window and press enter


Marvell>> ide reset
ide reset

Reset IDE:
Marvell Serial ATA Adapter
Found adapter at bus 1, device 7 ... Scanning channels
Device 0: OK
Model: ST31500341AS Firm: CC4H Ser#:
9VS21T6A
Type: Hard Disk
Supports 48-bit addressing
Capacity: 1430799.3 MB = 1397.2 GB (-1364690128 x 512)
Device 1: OK
Model: ST31500341AS Firm: CC1H Ser#:
9VS2YA2Q
Type: Hard Disk
Supports 48-bit addressing
Capacity: 1430799.3 MB = 1397.2 GB (-1364690128 x 512)
Device 2: OK
Model: ST31500341AS Firm: CC4H Ser#:
9VS220RH
Type: Hard Disk
Supports 48-bit addressing
Capacity: 1430799.3 MB = 1397.2 GB (-1364690128 x 512)
Device 3: OK
Model: ST31500341AS Firm: CC4H Ser#:
9VS1V7YP
Type: Hard Disk
Supports 48-bit addressing
Capacity: 1430799.3 MB = 1397.2 GB (-1364690128 x 512)
Device 4: OK
Model: ST31500341AS Firm: CC4H Ser#:
9VS1XN8B
Type: Hard Disk
Supports 48-bit addressing
Capacity: 1430799.3 MB = 1397.2 GB (-1364690128 x 512)

Marvell>> setenv ipaddr ${ipaddr}
setenv ipaddr ${ipaddr}
Marvell>> setenv serverip ${serverip}
setenv serverip ${serverip}
Marvell>> setenv bootargs console=ttyS0,115200 netconsole=6666@${ipaddr}/,6666@$
{serverip}/
setenv bootargs console=ttyS0,115200 netconsole=6666@${ipaddr}/,6666@${serverip}
/
Marvell>> tftpboot 0x800000 UIMAGE-26394-NWSP2CL-5BIG1-21-standalone
tftpboot 0x800000 UIMAGE-26394-NWSP2CL-5BIG1-21-standalone
Using egiga0 device
TFTP from server 192.168.0.12; our IP address is 192.168.0.252
Filename 'UIMAGE-26394-NWSP2CL-5BIG1-21-standalone'.
Load address: 0x800000
Loading: #################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#########################
done
Bytes transferred = 3120840 (2f9ec8 hex)
Marvell>> bootm
bootm
## Booting image at 00800000 ...
Image Name: Linux-2.6.39.4
Created: 2013-10-20 7:51:30 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3120776 Bytes = 3 MB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK

totorweb
 
Posts: 46
Joined: Fri Oct 18, 2013 11:28 am

Re: lacie 5 big network v.1 please support for fvdw

Postby fvdw » Wed Oct 23, 2013 6:21 pm

I must go for a party

So ide reset is not the problem

you can try to use the load address of the normal kernel 0x400000
so use
tftpboot 0x400000... (instead of tftpboot 0x800000...)
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: lacie 5 big network v.1 please support for fvdw

Postby Mijzelf » Wed Oct 23, 2013 6:55 pm

Anyhow when loading the normal kernel u-boot uses indeed address 00400000
So why not use that instead of 1000000
It's about sizes. If the kernel on 0x0800000 overwrites a part of u-boot, then u-boot must be at 0x07e0000, or something like that. Between 0x0400000 and 0x07e0000 is slightly less than 4MiB, so chances are that u-boot is overwritten from the other side. But there is plenty of memory beyond 0x0800000, so I just jumped in the ocean.

Of course it won't hurt to try 0x0400000.

I thought of another possible problem.
Code: Select all
        if (verify) {
                puts ("   Verifying Checksum ... ");
                if (crc32 (0, (char *)data, len) != ntohl(hdr->ih_dcrc)) {
                        printf ("Bad Data CRC\n");
                        return 1;
                }
                puts ("OK\n");
        }

        len_ptr = (ulong *)data;

<snip>

        /*
         * We have reached the point of no return: we are going to
         * overwrite all exception vector code, so we cannot easily
         * recover from any failures any more...
         */

        iflag = disable_interrupts();

        switch (hdr->ih_comp) {
        case IH_COMP_NONE:
                if(ntohl(hdr->ih_load) == addr) {
                        printf ("   XIP %s ... ", name);
                } else {
#if defined(CONFIG_HW_WATCHDOG) || defined(CONFIG_WATCHDOG)
                        size_t l = len;
                        void *to = (void *)ntohl(hdr->ih_load);
                        void *from = (void *)data;

                        printf ("   Loading %s ... ", name);

                        while (l > 0) {
                                size_t tail = (l > CHUNKSZ) ? CHUNKSZ : l;
                                WATCHDOG_RESET();
                                memmove (to, from, tail);
                                to += tail;
                                from += tail;
                                l -= tail;
                        }
#else   /* !(CONFIG_HW_WATCHDOG || CONFIG_WATCHDOG) */
                        memmove ((void *) ntohl(hdr->ih_load), (uchar *)data, len);
#endif  /* CONFIG_HW_WATCHDOG || CONFIG_WATCHDOG */
                }

<snip>
        puts ("OK\n");
 
<snip>
           do_bootm_linux  (cmdtp, flag, argc, argv,
                             addr, len_ptr, verify);
On the original IBM PC the hardware clocktick was used to refresh the memory, among other things. So if you disabled the clock interrupt, after some time (a second?) the system just 'faded away'.

Maybe a similar problem is here. In that case the kernel is too big, and the system just stops before the kernel can re-enable the interrupts. In that case it could be solved by putting the initd in a second uImage. That can be moved to it's destination while the interrupts are not disabled yet.
Mijzelf
 
Posts: 255
Joined: Wed Nov 21, 2012 9:12 am

Re: lacie 5 big network v.1 please support for fvdw

Postby totorweb » Wed Oct 23, 2013 7:09 pm

same problem with 0x400000

Code: Select all
Marvell>> bootm 0x400000
bootm 0x400000
## Booting image at 00400000 ...
   Image Name:   Linux-2.6.39.4
   Created:      2013-10-20   7:51:30 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3120776 Bytes =  3 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
totorweb
 
Posts: 46
Joined: Fri Oct 18, 2013 11:28 am

Re: lacie 5 big network v.1 please support for fvdw

Postby taetae » Wed Oct 23, 2013 9:12 pm

fvdw wrote:the 5big is supporting clunc, otherwise we could use the u-boot console

@tatae

You did not do the test with first performing
Code: Select all
marvel>> ide reset

then set env variables for netconsole support, upload with tftpboot the kernel and perform the bootm command




Code: Select all
provided by fvdw
waiting for u-boot..
starting u-boot net console click on window and press enter


Marvell>> ide reset
ide reset

Reset IDE:
Marvell Serial ATA Adapter
Found adapter at bus 1, device 7 ... Scanning channels
  Device 0: OK
Model: WDC WD20EZRX-00D8PB0                     Firm: 80.00A80 Ser#:      WD-WMC
4M0410979
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 1907729.0 MB = 1863.0 GB (-387938128 x 512)
  Device 1: OK
Model: WDC WD20EZRX-00D8PB0                     Firm: 80.00A80 Ser#:      WD-WMC
4M0218180
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 1907729.0 MB = 1863.0 GB (-387938128 x 512)
  Device 2: OK
Model: WDC WD20EZRX-00D8PB0                     Firm: 80.00A80 Ser#:      WD-WMC
4M0424246
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 1907729.0 MB = 1863.0 GB (-387938128 x 512)
Error - Failed initializing(SRST) drive on channel 3
Failed initializing storage deivce connected to SATA channel 3
  Device 4: OK
Model: WDC WD5000AADS-00S9B0                    Firm: 01.00A01 Ser#:      WD-WCA
V90478832
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 476940.0 MB = 465.7 GB (976773168 x 512)

Marvell>> setenv ipaddr ${ipaddr}
setenv ipaddr ${ipaddr}
Marvell>> setenv serverip ${serverip}
setenv serverip ${serverip}
Marvell>> setenv bootargs console=ttyS0,115200 netconsole=6666@${ipaddr}/,6666@$
{serverip}/
setenv bootargs console=ttyS0,115200 netconsole=6666@${ipaddr}/,6666@${serverip}
/
Marvell>> tftpboot 0x800000 UIMAGE-26394-NWSP2CL-5BIG1-21-standalone
tftpboot 0x800000 UIMAGE-26394-NWSP2CL-5BIG1-21-standalone
Using egiga0 device
TFTP from server 192.168.1.12; our IP address is 192.168.1.252
Filename 'UIMAGE-26394-NWSP2CL-5BIG1-21-standalone'.
Load address: 0x800000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #########################
done
Bytes transferred = 3120840 (2f9ec8 hex)
Marvell>> bootm
bootm
## Booting image at 00800000 ...
   Image Name:   Linux-2.6.39.4
   Created:      2013-10-20   7:51:30 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3120776 Bytes =  3 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
Last edited by taetae on Wed Oct 23, 2013 9:24 pm, edited 1 time in total.
taetae
Donator VIP
Donator VIP
 
Posts: 438
Joined: Mon Aug 26, 2013 9:02 am

Re: lacie 5 big network v.1 please support for fvdw

Postby fvdw » Wed Oct 23, 2013 9:22 pm

On the original IBM PC the hardware clocktick was used to refresh the memory, among other things. So if you disabled the clock interrupt, after some time (a second?) the system just 'faded away'.

Maybe a similar problem is here. In that case the kernel is too big, and the system just stops before the kernel can re-enable the interrupts. In that case it could be solved by putting the initd in a second uImage. That can be moved to it's destination while the interrupts are not disabled yet.


I did not disable the clock interrupt (at least not by purpose) as said the only difference between kernel 21 standalone and kernel 20 is the initramfs (which is the same as used in all the other working standalone kernels), if is caused by a too big kernel then I must make one smaller then 2 MB (the normal kernel is 1.8 MB). Funny is that an isp1 with 64 MB and same kernel has no problems with a standalone kernel form 23 MB, but of course it has probably another u-boot version. Also a 2big1 has no issues
what is different on the 5big1 compared to a isp1, 2big1that could cause this problem. There is a difference compared with these other orion based mainboards and that is that it using a pci interface for the HDD disks.
But then it is puzzling me that without the initramfs the kernel has no problem.
I think I must find a way to make a standalone kernel of max 1.9 MB

Tatae posted the u-boot environment a while ago, ther is some interesting info
Code: Select all
image_name=uImage
standalone=fsload 0x400000 $(image_name);setenv bootargs $(bootargs) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end); bootm 0x400000;
disaMvPnp=no
eth1addr=00:00:00:00:51:82
overEthAddr=no
pciMode=host
usb0Mode=host
bootdelay=40
bootcmd=if lump 5; then ; else run disk_disk; fi
kernel_addr=0x400000
boot_disk10=disk ${kernel_addr} 4:6
boot_disk9=if disk ${kernel_addr} 3:6; then; else run boot_disk10; fi
boot_disk8=if disk ${kernel_addr} 2:6; then; else run boot_disk9; fi
boot_disk7=if disk ${kernel_addr} 1:6; then; else run boot_disk8; fi
boot_disk6=if disk ${kernel_addr} 0:6; then; else run boot_disk7; fi
boot_disk5=if disk ${kernel_addr} 4:A; then; else run boot_disk6; fi
boot_disk4=if disk ${kernel_addr} 3:A; then; else run boot_disk5; fi
boot_disk3=if disk ${kernel_addr} 2:A; then; else run boot_disk4; fi
boot_disk2=if disk ${kernel_addr} 1:A; then; else run boot_disk3; fi
boot_disk1=if disk ${kernel_addr} 0:A; then; else run boot_disk2; fi
disk_disk=ide reset; run boot_disk1; bootm ${kernel_addr};
ethact=egiga0
bootargs=console=ttyS0,115200 root=/dev/sda7 ro boardType=mv88F5281 productType=5Big reset=0

So
(1) boot command used is disk_disk
(2) the address to load the kernel should be 0x400000
(3) disk_disk sequence is first perform ide reset run boot-disk1 (and the others if needed, then using bootm 0x400000

we should exactly copy that,
we almost did, first ide reset then upload the kernel with tftpboot 0x400000 UIMAGE
BUT we only use "bootm" to boot it.
Maybe it requires bootm 0x400000

So tatae or totorweb please another trial using this extra addedto the bootm command (don't forget to set net console parameters also !)
so setenv for netconsole support
perform ide reset
perform tftpboot 0x400000 UIMAGE-NWSP2CL-5BIG1-21-standalone
perform bootm 0x400000

ps there is another interesting command in this u-boot available
Code: Select all
standalone=fsload 0x400000 $(image_name);setenv bootargs $(bootargs) root=/dev/mtdblock0 rw

It seems to have a standalone kernel from Lacie in flash I have no idea what it will do and if it can be contacted with telnet.
Also it could be that it initialize all disk automatic and formats them, meaning destroying all data on it. So for the moment my advise is not tot use before we know what it does. (Safest way will be a test without any disk inside) I have a version of a lacie initramfs that includes the 5big1 but that one will ininitialize and format all disks. For sure this initramfs has no telnet server
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: lacie 5 big network v.1 please support for fvdw

Postby taetae » Wed Oct 23, 2013 9:37 pm

Code: Select all
provided by fvdw
waiting for u-boot..
starting u-boot net console click on window and press enter


Marvell>> ide reset
ide reset

Reset IDE:
Marvell Serial ATA Adapter
Found adapter at bus 1, device 7 ... Scanning channels
  Device 0: OK
Model: WDC WD20EZRX-00D8PB0                     Firm: 80.00A80 Ser#:      WD-WMC
4M0410979
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 1907729.0 MB = 1863.0 GB (-387938128 x 512)
  Device 1: OK
Model: WDC WD20EZRX-00D8PB0                     Firm: 80.00A80 Ser#:      WD-WMC
4M0218180
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 1907729.0 MB = 1863.0 GB (-387938128 x 512)
  Device 2: OK
Model: WDC WD20EZRX-00D8PB0                     Firm: 80.00A80 Ser#:      WD-WMC
4M0424246
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 1907729.0 MB = 1863.0 GB (-387938128 x 512)
  Device 3: OK
Model: WDC WD20EZRX-00D8PB0                     Firm: 80.00A80 Ser#:      WD-WMC
4M0219436
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 1907729.0 MB = 1863.0 GB (-387938128 x 512)
  Device 4: OK
Model: WDC WD5000AADS-00S9B0                    Firm: 01.00A01 Ser#:      WD-WCA
V90478832
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 476940.0 MB = 465.7 GB (976773168 x 512)

Marvell>> setenv ipaddr ${ipaddr}
setenv ipaddr ${ipaddr}
Marvell>> setenv serverip ${serverip}
setenv serverip ${serverip}
Marvell>>  setenv bootargs console=ttyS0,115200 netconsole=6666@${ipaddr}/,6666@
${serverip}/
 setenv bootargs console=ttyS0,115200 netconsole=6666@${ipaddr}/,6666@${serverip
}/
Marvell>> tftpboot 0x400000 UIMAGE-5BIG1-21-standalone
tftpboot 0x400000 UIMAGE-5BIG1-21-standalone

Using egiga0 device
TFTP from server 192.168.1.12; our IP address is 192.168.1.252
Filename 'UIMAGE-5BIG1-21-standalone'.
Load address: 0x400000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #########################
done
Bytes transferred = 3120840 (2f9ec8 hex)
Marvell>> bootm 0x400000
bootm 0x400000
## Booting image at 00400000 ...
   Image Name:   Linux-2.6.39.4
   Created:      2013-10-20   7:51:30 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3120776 Bytes =  3 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
taetae
Donator VIP
Donator VIP
 
Posts: 438
Joined: Mon Aug 26, 2013 9:02 am

Re: lacie 5 big network v.1 please support for fvdw

Postby fvdw » Wed Oct 23, 2013 10:09 pm

:dry that means I need to compile a smaller standalone kernel I guess

job for tomorrow evening....we will get this to work
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

PreviousNext

Return to Lacie 5Big Network vs1

Who is online

Users browsing this forum: No registered users and 7 guests