Having trouble with an NSA310S, freezing after loading kernel May 05, 2020 06:54AM |
Registered: 3 years ago Posts: 9 |
Starting kernel ... Uncompressing Linux... done, booting the kernel.
usb start setenv bootargs console=ttyS0,115200 root=/dev/sda1 usb-storage.delay_use=0 rootdelay=1 rw ext2load usb 0:1 0x1c00000 /boot/dts/kirkwood-nsa310s.dtb ext2load usb 0:1 0x1100000 /boot/uInitrd ext2load usb 0:1 0x800000 /boot/uImage bootm 0x800000 0x1100000 0x1c00000
U-Boot 1.1.4 (May 28 2013 - 16:07:08) Marvell version: 3.6.0. I investigated updating the version of U-Boot based on https://forum.doozan.com/read.php?3,12381 where I noticed the step to check for bad blocks:
/ # dmesg | grep -i bad Scanning device for bad blocks Bad eraseblock 452 at 0x000003880000 Bad eraseblock 504 at 0x000003f00000
/ # cat /etc/fw_env.config # Configuration file for fw_(printenv/saveenv) utility. # Up to two entries are valid, in this case the redundand # environment sector is assumed present. # Notice, that the "Number of sectors" is ignored on NOR. # MTD device name Device offset Env. size Flash sector size Number of sectors # NAND example /dev/mtd1 0x0000 0x20000 0x20000 4
/ # cat /proc/mtd dev: size erasesize name mtd0: 00100000 00020000 "uboot" mtd1: 00080000 00020000 "uboot_env" mtd2: 00080000 00020000 "key_store" mtd3: 00080000 00020000 "info" mtd4: 00a00000 00020000 "etc" mtd5: 00a00000 00020000 "kernel_1" mtd6: 02fc0000 00020000 "rootfs1" mtd7: 00a00000 00020000 "kernel_2" mtd8: 02fc0000 00020000 "rootfs2"
Marvell>> printenv bootargs=console=ttyS0,115200 mtdparts=nand_mtd:0x100000(uboot),0x80000(uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(rootfs1),0xA00000(kernel_2),0x2FC0000(rootfs2) root= /dev/nfs rw init=/init bootcmd=nand read.e 0x2000000 $(kernel_addr) 0xA00000; bootm 0x2000000 bootdelay=2 baudrate=115200 loads_echo=0 ipaddr=10.4.52.165 serverip=10.4.52.7 rootpath=/srv/ubuntu netmask=255.255.255.0 nandEcc=1bit MODEL_ID=AD03 PRODUCT_NAME=STG-315 FEATURE_BIT=00 CONTRY_TYPE=FF VENDOR_NAME=MitraStar Technology Corp. run_diag=yes ethaddr=28:28:5D:1F:2D:42 stdin=serial stdout=serial stderr=serial console=console=ttyS0,115200 mtdparts=nand_mtd:0xc0000@0(uboot)ro,0x7f00000@0x100000(root) mainlineLinux=no enaMonExt=no enaCpuStream=no enaWrAllo=no pexMode=RC disL2Cache=no setL2CacheWT=yes disL2Prefetch=yes enaICPref=yes enaDCPref=yes sata_dma_mode=yes ethprime=egiga0 netbsd_en=no vxworks_en=no bootargs_root=root=/dev/nfs rw bootargs_end=:::DB88FXX81:eth0:none image_name=uImage standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneConfig); bootm 0x2000000; disaMvPnp=no ethmtu=1500 mvPhoneConfig=mv_phone_config=dev[0]:fxs,dev[1]:fxo mvNetConfig=mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500 usb0Mode=host yuk_ethaddr=00:00:00:EE:51:81 netretry=no rcvrip=169.254.100.100 loadaddr=0x02000000 autoload=no image_multi=yes enaAutoRecovery=yes kernel_addr=0x4640000 pcieTune=no ethact=egiga0
Re: Having trouble with an NSA310S, freezing after loading kernel May 05, 2020 04:10PM |
Registered: 5 years ago Posts: 125 |
Re: Having trouble with an NSA310S, freezing after loading kernel May 05, 2020 04:13PM |
Registered: 3 years ago Posts: 9 |
Re: Having trouble with an NSA310S, freezing after loading kernel May 05, 2020 04:16PM |
Registered: 5 years ago Posts: 125 |
Re: Having trouble with an NSA310S, freezing after loading kernel May 05, 2020 04:38PM |
Admin Registered: 13 years ago Posts: 18,495 |
Re: Having trouble with an NSA310S, freezing after loading kernel May 05, 2020 04:42PM |
Registered: 3 years ago Posts: 9 |
Re: Having trouble with an NSA310S, freezing after loading kernel May 05, 2020 04:50PM |
Admin Registered: 13 years ago Posts: 18,495 |
Re: Having trouble with an NSA310S, freezing after loading kernel May 06, 2020 05:01AM |
Registered: 3 years ago Posts: 9 |
Re: Having trouble with an NSA310S, freezing after loading kernel May 06, 2020 05:24AM |
Admin Registered: 13 years ago Posts: 18,495 |
Quote
A. Flashing Instruction:
Installation is the same for each u-Boot image, the instruction below is written to include all boxes. So choose the platform name that you are installing for, and copy/paste the appropriate commands.
If you are running kernel that do not provide mtd-utils and uboot-tools (fw_setenv, fw_printenv, flash_erase, nandwrite), you can download the NAND and U-Boot tools binaries here in this thread.
Re: Having trouble with an NSA310S, freezing after loading kernel May 06, 2020 05:28AM |
Registered: 3 years ago Posts: 9 |
Quote
A. Flashing Instruction:
>
>
> Installation is the same for each u-Boot image,
> the instruction below is written to include all
> boxes. So choose the platform name that you are
> installing for, and copy/paste the appropriate
> commands.
>
> If you are running kernel that do not provide
> mtd-utils and uboot-tools (fw_setenv, fw_printenv,
> flash_erase, nandwrite), you can download the NAND
> and U-Boot tools binaries here in this
> thread.
Re: Having trouble with an NSA310S, freezing after loading kernel May 06, 2020 05:34AM |
Registered: 3 years ago Posts: 9 |
/ # /e-data/52be4d76-9754-4d4e-bcee-7228b6f8015d/tmp/tools/flash_erase /dev/mtd0 0 4 Erasing 128 Kibyte @ 60000 -- 100 % complete
nandwrite /dev/mtd0 /e-data/52be4d76-9754-4d4e-bcee-7228b6f8015d/tmp/uboot.2 017.07-tld-1.nsa310s.mtd0.kwb Writing data to block 0 Writing data to block 20000 Writing data to block 40000 Writing data to block 60000
Re: Having trouble with an NSA310S, freezing after loading kernel May 06, 2020 06:18AM |
Registered: 3 years ago Posts: 9 |
Re: Having trouble with an NSA310S, freezing after loading kernel May 06, 2020 03:56PM |
Admin Registered: 13 years ago Posts: 18,495 |
Quote
Slightly different output from the thread, but it seems to have been successful. Also, the NSA310S seems to store its environment variables in a separate partition, so no messing around with offsets needed. Here goes...
Re: Having trouble with an NSA310S, freezing after loading kernel May 06, 2020 05:06PM |
Registered: 3 years ago Posts: 9 |
>Quote
Slightly different output from the thread,
> but it seems to have been successful. Also, the
> NSA310S seems to store its environment variables
> in a separate partition, so no messing around with
> offsets needed. Here goes...
Re: Having trouble with an NSA310S, freezing after loading kernel May 06, 2020 10:37PM |
Admin Registered: 13 years ago Posts: 18,495 |
> >Quote
Slightly different output from the
> thread,
> > but it seems to have been successful. Also, the
> > NSA310S seems to store its environment
> variables
> > in a separate partition, so no messing around
> with
> > offsets needed. Here goes...
Re: Having trouble with an NSA310S, freezing after loading kernel May 07, 2020 03:19AM |
Registered: 3 years ago Posts: 9 |
Quote
r1. There must be only one partition among all partitions from all drives that contains the kernel files. The 2 kernel files are /boot/uImage and /boot/uInitrd.
r2. The partition that contains the 2 kernel files must be partition 1 in a disk drive
r3. The partition that contains the rootfs must be labeled rootfs
r4. The rootfs partition is recommended to be type Ext3 (this is not a hard requirement, ext4 should boot OK, but Ext3 will ensure no problem).
[ 18.944010] Creating 9 MTD partitions on "orion_nand": [ 18.965905] 0x000000000000-0x000000100000 : "uboot" [ 18.980137] 0x000000100000-0x000000180000 : "uboot_env" [ 18.997455] 0x000000180000-0x000000200000 : "key_store" [ 19.017520] 0x000000200000-0x000000280000 : "info" [ 19.041946] 0x000000280000-0x000000c80000 : "etc" [ 19.056260] 0x000000c80000-0x000001680000 : "kernel_1" [ 19.075145] 0x000001680000-0x000004640000 : "rootfs1" [ 19.102567] 0x000004640000-0x000005040000 : "kernel_2" [ 19.118613] 0x000005040000-0x000008000000 : "rootfs2
Re: Having trouble with an NSA310S, freezing after loading kernel May 07, 2020 04:41AM |
Admin Registered: 13 years ago Posts: 18,495 |
Quote
r1. There must be only one partition
> among all partitions from all drives that contains
> the kernel files. The 2 kernel files are
> /boot/uImage and /boot/uInitrd.
> r2. The partition that contains the 2 kernel files
> must be partition 1 in a disk drive
> r3. The partition that contains the rootfs must be
> labeled rootfs
> r4. The rootfs partition is recommended to be type
> Ext3 (this is not a hard requirement, ext4 should
> boot OK, but Ext3 will ensure no problem).
[ 18.965905] 0x000000000000-0x000000100000 : "uboot"