From linux-kirkwood to kinux-kirkwood-dt on Tonidoplug-V2?

This forum is for Marvell Kirkwood devices such as the GoFlex Home/Net, PogoPlug v1/v2, SheevaPlug, and ZyXEL devices.

From linux-kirkwood to kinux-kirkwood-dt on Tonidoplug-V2?

Postby landzend » Mon Apr 16, 2018 1:43 am

Hi,

I have noticed that the kernel "linux-kirkwood" package hasn't been updated since last November.

On my Tonidoplug V2 should I just swap over to the "linux-kirkwood-dt" package? And If I do this, should I also update any other required packages or other preliminary work as well? (I do regular "pacman -Syu", so all other packages should already be up to date.)

Thanks in advance,

Brian
landzend
 
Posts: 4
Joined: Fri May 11, 2012 1:18 am

Re: From linux-kirkwood to kinux-kirkwood-dt on Tonidoplug-V

Postby summers » Mon Apr 16, 2018 9:52 am

You'll probably need an updated uboot, that can handle the device tree.

moonman was the main man doing the roll out for kirkwood devices - so he'll know the status ...
summers
 
Posts: 537
Joined: Sat Sep 06, 2014 12:56 pm

Re: From linux-kirkwood to kinux-kirkwood-dt on Tonidoplug-V

Postby landzend » Mon Apr 16, 2018 1:07 pm

Thanks for that.

I had a look around and was able to work out how to do a "tftpboot" with my current kernel and also the latest kernel from the linux-kirkwood-dt package.

Using my current kernel worked (so I proved I could do it):
Code: Select all
Marvell>> tftpboot 00800000 uImage
Using egiga0 device
TFTP from server 192.168.1.10; our IP address is 192.168.1.11
Filename 'uImage'.
Load address: 0x800000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         ######################################################
done
Bytes transferred = 4600064 (463100 hex)
Marvell>> bootm
## Booting image at 00800000 ...
   Image Name:   Linux-4.4.97-1-ARCH
   Created:      2017-11-11   4:51:55 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4600000 Bytes =  4.4 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Initializing cgroup subsys cpuacct
[    0.000000] Linux version 4.4.97-1-ARCH (builduser@leming) (gcc version 7.2.0 (GCC) ) #1 PREEMPT Sat Nov 11 04:51:38 UTC 2017
[    0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f
[    0.000000] CPU: VIVT data cache, VIVT instruction cache

etc...


I extracted the kernel from the latest linux-kirkwood-dt package and got:
Code: Select all
Marvell>> tftpboot 00800000 zImage
Using egiga0 device
TFTP from server 192.168.1.10; our IP address is 192.168.1.11
Filename 'zImage'.
Load address: 0x800000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         ##############################
done
Bytes transferred = 5141928 (4e75a8 hex)
Marvell>> bootm
## Booting image at 00800000 ...
Bad Magic Number
Saving Environment to NAND...
Erasing Nand...Writing to Nand... done
Marvell>>


I think this proved that my old version isn't up to it (I believe).

Looking at the U-Boots available via pacman:

Code: Select all
[root@crusty dev]# pacman -Ss uboot
alarm/uboot-dockstar 2016.09-1
    U-Boot for the Seagate FreeAgent DockStar
alarm/uboot-goflexhome 2016.09-1
    U-Boot for the Seagate GoFlex Home
alarm/uboot-goflexnet 2016.09-1
    U-Boot for the Seagate GoFlex Net
alarm/uboot-guruplug 2016.09-1
    U-Boot for the Guruplug (plus)
alarm/uboot-nsa310 2016.09-1
    U-Boot for the Zyxel NSA310
alarm/uboot-nsa320 2016.09-1
    U-Boot for the Zyxel NSA320
alarm/uboot-nsa325 2016.09-1
    U-Boot for the Zyxel NSA325
alarm/uboot-olinuxino 2016.07-1
    U-Boot for i.MX233-OLinuXino
alarm/uboot-oxnas 2013.10-2
    U-Boot for PLX/Oxford Semiconductor NAS7820
alarm/uboot-pogo_e02 2016.09-1
    U-Boot for the Pogoplug V2 (E02)
alarm/uboot-pogoplugv4 2016.09-1
    U-Boot for the Pogoplug V4 & Pogoplug Mobile
alarm/uboot-sheevaplug 2016.09-1
    U-Boot for the Sheevaplug (esata)
alarm/uboot-tools 2018.03-1
    U-Boot Tools


there isn't one for my Tonidoplug2. :(

Any pointers as to how I go about getting the latest U-Boot for my Tnidoplug2?

Thanks in advance,

Brian
landzend
 
Posts: 4
Joined: Fri May 11, 2012 1:18 am

Re: From linux-kirkwood to kinux-kirkwood-dt on Tonidoplug-V

Postby summers » Mon Apr 16, 2018 1:59 pm

Yes its a question for moonman. There is a thread pinned at the top of this area discussing roll out of new uboot to devices.

Good that you can access uboot - that makes life easier. Means you can type the commands to load the device tree, which will be needed for modern kernel.

Oh yes, do you use "bootm" or "bootz" for booting a zImage? Let me see if i can check remotely. Yes I use:

Code: Select all
bootz ${kernel_addr_r} - ${fdt_addr_r};


And possible problem - I can't see a device tree for you here: https://github.com/torvalds/linux/tree/master/arch/arm/boot/dts
summers
 
Posts: 537
Joined: Sat Sep 06, 2014 12:56 pm

Re: From linux-kirkwood to kinux-kirkwood-dt on Tonidoplug-V

Postby summers » Mon Apr 16, 2018 9:00 pm

Now at home, so can check on my nsa325 ...

Just checked which device tree come in kirkwood, uboot. I don't have anything tonidoplug but I do have:
Code: Select all
/boot/dtbs/kirkwood-topkick.dtb

Which
https://archlinuxarm.org/platforms/armv5/tonidoplug-2
Says it is a copy of, so may well be worth trying ...
summers
 
Posts: 537
Joined: Sat Sep 06, 2014 12:56 pm

Re: From linux-kirkwood to kinux-kirkwood-dt on Tonidoplug-V

Postby moonman » Fri Apr 20, 2018 3:01 pm

I would try appening dtb to the zImage and create a uImage out of it to be booted with the current bootloader.

Code: Select all
# Append DTB to zImage
cat zImage <filename>.dtb > zImage_w_dtb
# Create uImage
mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n "ArchLinuxArm kernel" -d zImage_w_dtb uImage


And copy the resultimg uImage where your current one is. Obviously you should take care of keeping your existing one as a backup so you can boot the device back in case this doesn't work.

Try this, if it works, we can create a pacman hook that does this automatically after every kernel update.
Pogoplug V4 | GoFlex Home | Raspberry Pi B 512 | CuBox-i4 Pro | ClearFog | BeagleBone Black | Odroid U2 | Odroid C1 | Odroid XU4
-----------------------------------------------------------------------------------------------------------------------
[armv5] Updated U-Boot | |[armv5] How to install my.pogoplug.com service | [armv5] NAND Rescue System
moonman
Developer
 
Posts: 3121
Joined: Sat Jan 15, 2011 3:36 am
Location: Calgary, Canada


Return to Marvell Kirkwood

Who is online

Users browsing this forum: No registered users and 3 guests