Hi bodhi, Did you back from your trip? And any update about the HW IO patch?by wacke - uBoot
Hi bodhi, Any update about the HW IO patch?by wacke - uBoot
bodhi Wrote: ------------------------------------------------------- > Hi wacke, > > I'm getting a used Armada 370 board for testing > purpose. So I will get back to this task > eventually. Hi bodhi, Any update about the HW IO patch?by wacke - uBoot
bodhi Wrote: ------------------------------------------------------- > Perhaps version 2.6? Hi bodhi, When you get the version 2.6 ready, just send it to me, i'll test it. (my device is completely idle)by wacke - uBoot
Hi bodhi, The boot log of kernel 2.4 with "marvell,armada-xp-cpu-config",still crashed... Marvell>> run bootcmd4 Reset IDE: Marvell Serial ATA Adapter Integrated Sata device found Device 1 @ 0 1: Model: JMicron Firm: 100415 Ser#: 00000000002E9 Type: Hard Disk Supports 48-bit addressing Cby wacke - uBoot
Hi bodhi, The boot log of kernel 2.5, crashed: Marvell>> run bootcmd4 Reset IDE: Marvell Serial ATA Adapter Integrated Sata device found Device 1 @ 0 1: Model: JMicron Firm: 100415 Ser#: 00000000002E9 Type: Hard Disk Supports 48-bit addressing Capacity: 3836.0 MB = 3.7 GB (7856128 x 512) Loadinby wacke - uBoot
bodhi Wrote: ------------------------------------------------------- > Hi wacke, > > I've re-uploaded the tarball in the post above. > > https://forum.doozan.com/read.php?3,43214,73239#msg-73239 Hi bodhi, I've updated the full image,but it still crashed: Marvell>> run bootcmd4 Reset IDE: Marvell Serial ATA Adapter Integrated Sata device foundby wacke - uBoot
bodhi Wrote: ------------------------------------------------------- > Hi wacke, > > I've updated the post above (kernel version > tld-2.4 was uploaded). > > https://forum.doozan.com/read.php?3,43214,73239#msg-73239 Hi bodhi, The tld-2.4 version also crashed,did you have the kernel modules of version tld-2.4(currentlly I used the kernel modules of version tld-2by wacke - uBoot
bodhi Wrote: ------------------------------------------------------- > It should be in the kernel module > > mv88e6xxx.ko Hi bodhi, I found the problem, the kernel modules didn't load,but the kernel crashed... [ 77.933551] Internal error: Oops - undefined instruction: 0 [#3] PREEMPT SMP ARM [ 77.943703] Modules linked in: bridge ath9k(+) ath10k_pci(+) ath9k_commonby wacke - uBoot
bodhi Wrote: ------------------------------------------------------- > Hi wacke, > > :) sorry, it is too noisy! I was mistakenly put a > debug print in that function. > > But it looks like it is working. > Hi ,bodhi I'll try to test the throughput to see if it's working or not,but the 88e6171r switch dirver didn't compile into the kernel?by wacke - uBoot
Hi, bodhi The kernel version 4.19.1-mvebu-tld-2.3 boot log: Marvell>> run bootcmd4 Reset IDE: Marvell Serial ATA Adapter Integrated Sata device found Device 1 @ 0 1: Model: JMicron Firm: 100415 Ser#: 00000000002E9 Type: Hard Disk Supports 48-bit addressing Capacity: 3836.0 MB = 3.7 GB (7856128 x 5by wacke - uBoot
bodhi Wrote: ------------------------------------------------------- > I suspected some problem like this. We might have > force the code to pretend it knows that it is > armada370. But that will make this test kernel > only works for the Armada 370. Hi bodhi, Then separate the armada 370 kernel from other device?by wacke - uBoot
Hi bodhi, Change below coherencyfab: coherency-fabric@20200 { compatible = "marvell,coherency-fabric"; reg = <0x20200 0xb0>, <0x21010 0x1c>; }; To this? coherencyfab: coherency-fabric@20200 { compatible = "marvell,armada370"; reg = <0x20200 0xb0>, <0x21010 0x1c>; };by wacke - uBoot
Hi bodhi, My devide DTS file: /* * Device Tree file for Marvell Armada 370 Reference Design board * (RD-88F6710-A1) * * Copied from arch/arm/boot/dts/armada-370-db.dts * * Copyright (C) 2013 Florian Fainelli <florian@openwrt.org> * * This file is dual-licensed: you can use it either under the terms * of the GPL or the X11 license, at your option. Note that this dualby wacke - uBoot
Hi bodhi, I've update the 4.19.1-mvebu-tld-2.2 version,but the HW coherency didn't work... Marvell>> run bootcmd4 Reset IDE: Marvell Serial ATA Adapter Integrated Sata device found Device 1 @ 0 1: Model: JMicron Firm: 100415 Ser#: 00000000002E9 Type: Hard Disk Supports 48-bit addressingby wacke - uBoot
bodhi Wrote: ------------------------------------------------------- > Hi wacke, > > Yes, it was disable at where I thought it was. > Will upload another version tomorrow. OK. Waiting for your another version.by wacke - uBoot
bodhi Wrote: ------------------------------------------------------- > Ok I've uploaded the zImage. You can just copy it > to your rootfs and try it. If you are booting with > uImage then append the DTB to this and make > uImage. Hi bodhi, I've updated the test kernel, boot log: Marvell>> run bootcmd4 Reset IDE: Marvell Serial ATA Adapter Integrated Sby wacke - uBoot
Hi bodhi, Maybe the thermal driver should also modified? See armada_thermal.c in kernel 4.19: static const struct armada_thermal_data armada370_data = { .init = armada370_init, .is_valid_bit = BIT(9), .temp_shift = 10, .temp_mask = 0x1ff, .coef_b = 3153000000ULL, .coef_m = 10000000ULL, .coef_div = 13825, .syscon_status_off = 0x0, .syscon_control1_off = 0x4, }; static cby wacke - uBoot
1000001101000 Wrote: ------------------------------------------------------- > I wonder if either of these would work: > reg = <0x18300 0x4 > 0x18300 0x8>; > > reg = <0x18300 0x4 > 0x18304 0x8>; @1000001101000 Actually I've tested both of those, for my device it did not work at all...by wacke - uBoot
@1000001101000 After modify the DTS, the hermal sensor still not working properly: root@debian:~# cat /sys/class/thermal/thermal_zone*/temp 228065 The temp was always 228065 which was not correct....by wacke - uBoot
Hi bodhi, I've tried to modify the armada-370.dtsi: thermal: thermal@18300 { compatible = "marvell,armada370-thermal"; reg = <0x18308 0x4 0x18300 0x8>; status = "okay"; }; And the boot log after modified: Marvell>> run bootcmd4 Reset IDE: Marvell Serial ATA Adapter Integrated Sata device found Device 1 @ 0 1: Modeby wacke - uBoot
Hi bodhi, I've update the kernel to your linux-4.19.1-mvebu-tld-1 , and the boot log: BootROM 1.08 Booting from NAND flash High speed PHY - Version: 2.1.2 (COM-PHY-V20) Update PEX Device ID 0x67100 High speed PHY - Ended Successfully DDR3 Training Sequence - Ver 4.5.0 DDR3 Training Sequence - Ended Successfully Status = MV_OK BootROM: Imageby wacke - uBoot
bodhi Wrote: ------------------------------------------------------- > Sorry, no idea how to overcome this. Other than > disable it in kernel config so it is not invoked. Bodhi, So how to disable the cpu idle in the kernel config?by wacke - uBoot
Hi bodhi, The boot log: Marvell>> setenv bootcmd4 'ide reset; ext2load ide 1:1 0x00800000 /boot/uImage; ext2load ide 1:1 0x2100000 /boot/uInitrd; setenv bootargs rootdelay=10 root=/dev/sda1 console=ttyS0,115200 earlyprintk=serial; bootm 0x800000 0x2100000' Marvell>> saveenv Saving Environment to NAND... Erasing Nand... Writing to Nand... done Marvell>> run booby wacke - uBoot
Hi,bodhi The rest log is stuck at "booting the kernel" Marvell>> run bootcmd4 Reset IDE: Marvell Serial ATA Adapter Integrated Sata device found Device 1 @ 0 1: Model: JMicron Firm: 100415 Ser#: 00000000002E9 Type: Hard Disk Supports 48-bit addressing Capacity: 3836.0 MB = 3.7 GB (785612by wacke - uBoot
Hi bodhi, uboot env: BootROM 1.08 Booting from NAND flash High speed PHY - Version: 2.1.2 (COM-PHY-V20) Update PEX Device ID 0x67100 High speed PHY - Ended Successfully DDR3 Training Sequence - Ver 4.5.0 DDR3 Training Sequence - Ended Successfully Status = MV_OK BootROM: Image checksum verification PASSED __ __ _ _ | \by wacke - uBoot
Hi,bodhi I've embedded the DTB to the uImage: cd /boot mv uImage uImage.orig cp -a zImage-4.18.5-mvebu-tld-1 zImage.fdt cat dts/armada-370-rtnasv3.dtb >> zImage.fdt mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-4.18.5-mvebu-tld-1 -d zImage.fdt uImage mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-4.18.5-mby wacke - uBoot
Hi bodhi, I've update the kernel to 4.18.5-mvebu-ld-1,and my device was stuck at: Loading file "/boot/uImage" from ide device 1:1 (hdb1) 4465829 bytes read ## Booting kernel from Legacy Image at 00800000 ... Image Name: Linux-4.18.5-mvebu-tld-1 Created: 1970-01-01 0:14:03 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 4465765by wacke - uBoot
bodhi Wrote: ------------------------------------------------------- > I already had kernel 4.18.5-mvebu-ld-1 out in the > release thread for a couple months now. OK,I'll test it later.by wacke - uBoot
bodhi Wrote: ------------------------------------------------------- > Hi wacke, > > Any thought about this Armada 370 temp sensor > topic? > > https://forum.doozan.com/read.php?2,71644,72579#msg-72579 Hi, bodhi My device is runing openwrt with kernel 4.14.xx, I'll try to build a 4.18+ kernel to see if my device will boot or not. Or if you have the 4.18+ kerneby wacke - uBoot