Quantcast
Channel: Linux Device Hacking
Viewing all articles
Browse latest Browse all 3247

NSA325 - stock u-boot problem booting with Linux Kernel 4.13.5 (3 replies)

$
0
0
Hello Bohdi,

I'm having some issues upgrading the kernel from 4.8.3 to 4.13.5 with an NSA325.
System has been upgraded from jessie to stretch vía apt

I've followed your tutorial and did the 4b point because I don't want to mess with my uboot.

i've done:
cd /boot
tar -xjf linux-4.13.5-kirkwood-tld-1-bodhi.tar.bz2
tar -xf  linux-dtb-4.13.5-kirkwood-tld-1.tar

cd /boot
apt-get remove flash-kernel
dpkg -i linux-image-4.13.5-kirkwood-tld-1_1.0_armel.deb

cp -a zImage-4.13.5-kirkwood-tld-1  zImage.fdt
cat dts/kirkwood-nsa325.dtb >> zImage.fdt
mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-4.13.5-kirkwood-tld-1 -d zImage.fdt  uImage
mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-4.13.5-kirkwood-tld-1 -d initrd.img-4.13.5-kirkwood-tld-1 uInitrd

My uBoot output:
         __  __                      _ _
        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  __/ | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_
| | | |___|  _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
 \___/    |____/ \___/ \___/ \__|
 ** MARVELL BOARD: DB-88F6282A-BP LE

U-Boot 1.1.4 (Jul 18 2013 - 10:47:29) Marvell version: 3.5.9

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 006CFB00

Soc: 88F6282 A1CPU running @ 1600Mhz L2 running @ 533Mhz
SysClock = 533Mhz , TClock = 200Mhz

DRAM (DDR3) CAS Latency = 7 tRP = 8 tRAS = 24 tRCD=8
DRAM CS[0] base 0x00000000   size 512MB
DRAM Total size 512MB  16bit width
Addresses 10M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (10M - 7M): Done
NAND:128 MB
Flash:  0 kB

CPU : Marvell Feroceon (Rev 1)
Kernel address is 0x4640000.

Streaming disabled
Write allocate disabled


USB 0: host mode
        [BlueDBG] reseting SoC Pex[0]  0 ...
PEX 0: PCI Express Root Complex Interface
PEX interface detected Link X1
        [BlueDBG] reseting SoC Pex[1]  0 ...
        [BlueDBG] reseting SoC Pex[1]  1 ...
        [BlueDBG] reseting SoC Pex[1]  2 ...
        [BlueDBG] reseting SoC Pex[1]  3 ...
        [BlueDBG] reseting SoC Pex[1]  4 ...
        [BlueDBG] reseting SoC Pex[1]  5 ...
        [BlueDBG] reseting SoC Pex[1]  6 ...
        [BlueDBG] reseting SoC Pex[1]  7 ...
        [BlueDBG] reseting SoC Pex[1]  8 ...
        [BlueDBG] reseting SoC Pex[1]  9 ...
        [BlueDBG] reseting SoC Pex[1]  10 ...
PEX 1: interface detected no Link.
Net:   egiga0 [PRIME]
Hit any key to stop autoboot:  0
(Re)start USB...
USB:   scanning bus for devices... 3 USB Device(s) found
Waiting for storage device(s) to settle before scanning...
1 Storage Device(s) found
....
8386386 bytes read
## Booting image at 02000000 ...
   Image Name:   Linux-4.13.5-kirkwood-tld-1
   Created:      2017-10-12  16:12:18 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3862548 Bytes =  3.7 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK
## Loading Ramdisk Image at 01100000 ...
   Image Name:   initramfs-4.13.5-kirkwood-tld-1
   Created:      2017-10-12  16:12:32 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    8386322 Bytes =  8 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK

Starting kernel ...

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

am I skipping something? could be that the image is broken?

Files in /boot
drwxrwxrwx 4 root root 1.0K Oct 12 16:12 .
drwxr-xr-x 6 root root 4.0K Oct 12 15:13 ..
-rw-r--r-- 1 root root 152K Oct  7 08:53 config-4.13.5-kirkwood-tld-1
-rw-r--r-- 1 root root 143K Oct 21  2016 config-4.8.3-kirkwood-tld-1
drwxr-xr-x 2 root root 5.0K Sep 20 08:13 dts
-rw-r--r-- 1 root root 8.0M Oct 12 14:24 initrd.img-4.13.5-kirkwood-tld-1
-rw-r--r-- 1 root root 8.2M Oct  9 22:49 initrd.img-4.8.3-kirkwood-tld-1
-rw-r--r-- 1 root root 141K Dec  8  2016 linux-4.8.3-kirkwood-tld-1.patch
drwx------ 2 root root 1.0K Dec  8  2016 lost+found
-rw------- 1 root root 2.5M Oct  7 11:26 System.map-4.13.5-kirkwood-tld-1
-rw------- 1 root root 2.3M Oct 21  2016 System.map-4.8.3-kirkwood-tld-1
-rw-r--r-- 1 root root 3.7M Oct 12 16:12 uImage
-rw-r--r-- 1 root root 8.0M Oct 12 16:12 uInitrd
-rw------- 1 root root 3.7M Oct  7 11:26 vmlinuz-4.13.5-kirkwood-tld-1
-rw------- 1 root root 3.1M Oct 21  2016 vmlinuz-4.8.3-kirkwood-tld-1
-rwxr-xr-x 1 root root 3.7M Oct  7 06:56 zImage-4.13.5-kirkwood-tld-1
-rwxr-xr-x 1 root root 3.1M Dec  8  2016 zImage-4.8.3-kirkwood-tld-1
-rwxr-xr-x 1 root root 3.7M Oct 12 16:11 zImage.fdt

# file uImage
uImage: u-boot legacy uImage, Linux-4.13.5-kirkwood-tld-1, Linux/ARM, OS Kernel Image (Not compressed), 3862548 bytes, Thu Oct 12 16:12:18 2017, Load Address: 0x00008000, Entry Point: 0x00008000, Header CRC: 0x3E922991, Data CRC: 0x0313BB48

# file uInitrd
uInitrd: u-boot legacy uImage, initramfs-4.13.5-kirkwood-tld-1, Linux/ARM, RAMDisk Image (gzip), 8386322 bytes, Thu Oct 12 16:12:32 2017, Load Address: 0x00000000, Entry Point: 0x00000000, Header CRC: 0x8F561567, Data CRC: 0x55FE9383

I've rolled back to 4.8.3 restoring uImage and Uinitrd files and it works

Regards


------------
Mod edit: change subject decription.

Viewing all articles
Browse latest Browse all 3247

Trending Articles