|
Re: Debian on Action Tech SG200 and MI424WR-rev-I May 14, 2021 07:59AM |
Registered: 3 years ago Posts: 112 |
|
Re: Debian on Action Tech SG200 and MI424WR-rev-I May 14, 2021 04:39PM |
Admin Registered: 13 years ago Posts: 18,997 |
8086k,
The file was uploaded by bkallus. I've not rebuilt stock u-boot yet, so I used this u-boot image.
> Still getting invalid image. I found when I use -p
> parameter, invalid image will appear. Maybe the
> version is too old? Can you upload the latest
> binary you have?
-p is correct. This is NAND image so the -p option must be used.
Look at the image information to make sure that it is in fact a u-boot image.
Run it:
I've reattached the image here, in case your previous download was bad.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 05/14/2021 06:43PM by bodhi.
The file was uploaded by bkallus. I've not rebuilt stock u-boot yet, so I used this u-boot image.
> Still getting invalid image. I found when I use -p
> parameter, invalid image will appear. Maybe the
> version is too old? Can you upload the latest
> binary you have?
-p is correct. This is NAND image so the -p option must be used.
Look at the image information to make sure that it is in fact a u-boot image.
mkimage -l uboot-revI-128MbFlash.bin Image Type: MVEBU Boot from nand Image Image version:1 Data Size: 541728 Bytes = 529.03 KiB = 0.52 MiB Load Address: 00600000 Entry Point: 00680000
Run it:
kwboot -t -B 115200 /dev/ttyUSB0 -b uboot-revI-128MbFlash.bin -p
I've reattached the image here, in case your previous download was bad.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 05/14/2021 06:43PM by bodhi.
|
Re: Debian on Action Tech SG200 and MI424WR-rev-I May 14, 2021 06:40PM |
Registered: 3 years ago Posts: 112 |
|
Re: Debian on Action Tech SG200 and MI424WR-rev-I May 15, 2021 03:55AM |
Registered: 3 years ago Posts: 112 |
bodhi,
Please post the log of your mi424wr rev i debian boot log. I can't make RTL8192CE work by changing the PCI-E port.
I notice there are three PCI-E ports in the bootlog if I enable both ports in DTS. This is very strange. I can't find any device except 88f6560 with lspci.
8086k
Edited 1 time(s). Last edit at 05/15/2021 06:07AM by 8086k.
Please post the log of your mi424wr rev i debian boot log. I can't make RTL8192CE work by changing the PCI-E port.
I notice there are three PCI-E ports in the bootlog if I enable both ports in DTS. This is very strange. I can't find any device except 88f6560 with lspci.
8086k
Edited 1 time(s). Last edit at 05/15/2021 06:07AM by 8086k.
|
Re: Debian on Action Tech SG200 and MI424WR-rev-I May 15, 2021 04:44PM |
Admin Registered: 13 years ago Posts: 18,997 |
To recap the progress. Everything works, except Ethernet. Looks like I'm hitting an old mvneta bug, still investigating this issue from time to time.
I've attched the tarball for the DTB and DTS source here. The Aruba is not complete yet.
kwboot booting was done here:
https://forum.doozan.com/read.php?2,78499,116214#msg-116214
Current boot log
PCIe
root@mi424:~# lspci -v
LEDs
root@mi424:~# ll /sys/class/leds/
Network
root@mi424:~# ifconfig
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 3 time(s). Last edit at 05/15/2021 06:54PM by bodhi.
I've attched the tarball for the DTB and DTS source here. The Aruba is not complete yet.
kwboot booting was done here:
https://forum.doozan.com/read.php?2,78499,116214#msg-116214
Current boot log
[ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 5.12.2-kirkwood-tld-1 (root@tldDebian) (gcc (Debian 8.3.0-6) 8.3.0, GNU ld (GNU Binutils for Debian) 2.31.1) #1.0 PREEMPT Tue May 11 21:21:51 PDT 2021 [ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f [ 0.000000] CPU: VIVT data cache, VIVT instruction cache [ 0.000000] OF: fdt: Machine model: Actiontec MI424WR-I [ 0.000000] printk: bootconsole [earlycon0] enabled [ 0.000000] Memory policy: Data cache writeback [ 0.000000] Zone ranges: [ 0.000000] Normal [mem 0x0000000000000000-0x0000000007ffffff] [ 0.000000] Movable zone start for each node [ 0.000000] Early memory node ranges [ 0.000000] node 0: [mem 0x0000000000000000-0x0000000007ffffff] [ 0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x0000000007ffffff] [ 0.000000] On node 0 totalpages: 32768 [ 0.000000] Normal zone: 256 pages used for memmap [ 0.000000] Normal zone: 0 pages reserved [ 0.000000] Normal zone: 32768 pages, LIFO batch:7 [ 0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768 [ 0.000000] pcpu-alloc: [0] 0 [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 32512 [ 0.000000] Kernel command line: console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=orion_nand:2M(U-Boot),32M(JFFS2),80M(Firmware) earlyprintk=serial [ 0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes, linear) [ 0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes, linear) [ 0.000000] mem auto-init: stack:off, heap alloc:on, heap free:off [ 0.000000] Memory: 101848K/131072K available (10240K kernel code, 1550K rwdata, 4228K rodata, 1024K init, 306K bss, 29224K reserved, 0K cma-reserved) [ 0.000000] random: get_random_u32 called from ____cache_alloc+0x408/0x7b4 with crng_init=0 [ 0.000000] rcu: Preemptible hierarchical RCU implementation. [ 0.000000] Trampoline variant of Tasks RCU enabled. [ 0.000000] Tracing variant of Tasks RCU enabled. [ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies. [ 0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16 [ 0.000000] clocksource: orion_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 9556302233 ns [ 0.000001] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 10737418237ns [ 0.008518] Switching to timer-based delay loop, resolution 5ns [ 0.015828] Console: colour dummy device 80x30 [ 0.021023] Calibrating delay loop (skipped), value calculated using timer frequency.. 400.00 BogoMIPS (lpj=2000000) [ 0.032223] pid_max: default: 32768 minimum: 301 [ 0.037811] LSM: Security Framework initializing [ 0.043236] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes, linear) [ 0.051239] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes, linear) [ 0.060704] CPU: Testing write buffer coherency: ok [ 0.067521] Setting up static identity map for 0x100000 - 0x100058 [ 0.074623] mvebu-soc-id: MVEBU SoC ID=0x6560, Rev=0x2 [ 0.080632] rcu: Hierarchical SRCU implementation. [ 0.087071] devtmpfs: initialized [ 0.095500] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns [ 0.106067] futex hash table entries: 256 (order: -1, 3072 bytes, linear) [ 0.150742] prandom32: self test passed (less than 6 bits correlated) [ 0.157862] prandom: seed boundary self test passed [ 0.167604] prandom: 100 self tests passed [ 0.172395] pinctrl core: initialized pinctrl subsystem [ 0.179396] NET: Registered protocol family 16 [ 0.185211] DMA: preallocated 256 KiB pool for atomic coherent allocations [ 0.193480] audit: initializing netlink subsys (disabled) [ 0.200461] thermal_sys: Registered thermal governor 'step_wise' [ 0.200722] audit: type=2000 audit(0.190:1): state=initialized audit_enabled=0 res=1 [ 0.215898] cpuidle: using governor ladder [ 0.220740] cpuidle: using governor menu [ 0.225755] [Firmware Bug]: Feroceon L2: bootloader left the L2 cache on! [ 0.233262] Feroceon L2: Cache support initialised. [ 0.244675] No ATAGs? [ 2.568524] random: fast init done [ 5.100735] "cryptomgr_test" (39) uses obsolete ecb(arc4) skcipher [ 5.318821] raid6: int32x8 gen() 113 MB/s [ 5.488589] raid6: int32x8 xor() 69 MB/s [ 5.658740] raid6: int32x4 gen() 113 MB/s [ 5.828560] raid6: int32x4 xor() 73 MB/s [ 5.998686] raid6: int32x2 gen() 148 MB/s [ 6.168627] raid6: int32x2 xor() 88 MB/s [ 6.338564] raid6: int32x1 gen() 108 MB/s [ 6.508617] raid6: int32x1 xor() 60 MB/s [ 6.513569] raid6: using algorithm int32x2 gen() 148 MB/s [ 6.519657] raid6: .... xor() 88 MB/s, rmw enabled [ 6.525124] raid6: using intx1 recovery algorithm [ 6.530779] vgaarb: loaded [ 6.534722] SCSI subsystem initialized [ 6.539416] libata version 3.00 loaded. [ 6.539704] usbcore: registered new interface driver usbfs [ 6.545923] usbcore: registered new interface driver hub [ 6.552005] usbcore: registered new device driver usb [ 6.557937] pps_core: LinuxPPS API ver. 1 registered [ 6.563600] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it> [ 6.573427] PTP clock support registered [ 6.579895] clocksource: Switched to clocksource orion_clocksource [ 6.680591] VFS: Disk quotas dquot_6.6.0 [ 6.685296] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) [ 6.731936] NET: Registered protocol family 2 [ 6.738073] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 4096 bytes, linear) [ 6.759975] TCP established hash table entries: 1024 (order: 0, 4096 bytes, linear) [ 6.768324] TCP bind hash table entries: 1024 (order: 0, 4096 bytes, linear) [ 6.789952] TCP: Hash tables configured (established 1024 bind 1024) [ 6.797233] MPTCP token hash table entries: 512 (order: 0, 6144 bytes, linear) [ 6.819983] UDP hash table entries: 256 (order: 0, 4096 bytes, linear) [ 6.827213] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes, linear) [ 6.850155] NET: Registered protocol family 1 [ 6.860467] RPC: Registered named UNIX socket transport module. [ 6.867067] RPC: Registered udp transport module. [ 6.889911] RPC: Registered tcp transport module. [ 6.895298] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 6.909916] PCI: CLS 0 bytes, default 32 [ 6.914817] Trying to unpack rootfs image as initramfs... [ 8.642635] Freeing initrd memory: 9736K [ 8.647464] NetWinder Floating Point Emulator V0.97 (double precision) [ 9.152284] Initialise system trusted keyrings [ 9.157459] Key type blacklist registered [ 9.162464] workingset: timestamp_bits=30 max_order=15 bucket_order=0 [ 9.169671] zbud: loaded [ 9.174412] NFS: Registering the id_resolver key type [ 9.180240] Key type id_resolver registered [ 9.185107] Key type id_legacy registered [ 9.189828] nfs4filelayout_init: NFSv4 File Layout Driver Registering... [ 9.197232] nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering... [ 9.205314] Installing knfsd (copyright (C) 1996 okir@monad.swb.de). [ 9.212637] jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc. [ 9.220874] fuse: init (API version 7.33) [ 9.225962] orangefs_debugfs_init: called with debug mask: :none: :0: [ 9.233316] orangefs_init: module version upstream loaded [ 9.239394] SGI XFS with ACLs, security attributes, realtime, scrub, quota, no debug enabled [ 9.352807] xor: measuring software checksum speed [ 9.367194] arm4regs : 1116 MB/sec [ 9.387032] 8regs : 669 MB/sec [ 9.402256] 32regs : 974 MB/sec [ 9.407295] xor: using function: arm4regs (1116 MB/sec) [ 9.413237] async_tx: api initialized (async) [ 9.418281] Key type asymmetric registered [ 9.423102] Asymmetric key parser 'x509' registered [ 9.428711] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 246) [ 9.436936] io scheduler bfq registered [ 9.639844] kirkwood-pinctrl f1018000.pinctrl: registered pinctrl driver [ 9.648419] mvebu-pcie mbus:pcie@82000000: host bridge /mbus/pcie@82000000 ranges: [ 9.656727] mvebu-pcie mbus:pcie@82000000: Parsing ranges property... [ 9.656768] mvebu-pcie mbus:pcie@82000000: MEM 0x00f1040000..0x00f1041fff -> 0x0000040000 [ 9.666092] mvebu-pcie mbus:pcie@82000000: MEM 0x00f1044000..0x00f1045fff -> 0x0000044000 [ 9.675412] mvebu-pcie mbus:pcie@82000000: MEM 0x00f1080000..0x00f1081fff -> 0x0000080000 [ 9.684731] mvebu-pcie mbus:pcie@82000000: MEM 0xffffffffffffffff..0x00fffffffe -> 0x0100000000 [ 9.694568] mvebu-pcie mbus:pcie@82000000: IO 0xffffffffffffffff..0x00fffffffe -> 0x0100000000 [ 9.704404] mvebu-pcie mbus:pcie@82000000: MEM 0xffffffffffffffff..0x00fffffffe -> 0x0200000000 [ 9.714231] mvebu-pcie mbus:pcie@82000000: IO 0xffffffffffffffff..0x00fffffffe -> 0x0200000000 [ 9.724320] mvebu-pcie mbus:pcie@82000000: PCI host bridge to bus 0000:00 [ 9.731813] pci_bus 0000:00: root bus resource [bus 00-ff] [ 9.737985] pci_bus 0000:00: root bus resource [mem 0xf1040000-0xf1041fff] (bus address [0x00040000-0x00041fff]) [ 9.748840] pci_bus 0000:00: root bus resource [mem 0xf1044000-0xf1045fff] (bus address [0x00044000-0x00045fff]) [ 9.759696] pci_bus 0000:00: root bus resource [mem 0xf1080000-0xf1081fff] (bus address [0x00080000-0x00081fff]) [ 9.770548] pci_bus 0000:00: root bus resource [mem 0xf3000000-0xf3ffffff] [ 9.778089] pci_bus 0000:00: root bus resource [io 0x1000-0xeffff] [ 9.785050] pci_bus 0000:00: scanning bus [ 9.785166] pci 0000:00:01.0: [11ab:6560] type 01 class 0x060400 [ 9.791893] pci 0000:00:01.0: reg 0x38: [mem 0x00000000-0x000007ff pref] [ 9.800507] pci_bus 0000:00: fixups for bus [ 9.800527] PCI: bus0: Fast back to back transfers disabled [ 9.806779] pci 0000:00:01.0: scanning [bus 00-00] behind bridge, pass 0 [ 9.806795] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring [ 9.815494] pci 0000:00:01.0: scanning [bus 00-00] behind bridge, pass 1 [ 9.815667] pci_bus 0000:01: scanning bus [ 9.815721] pci 0000:01:00.0: [168c:002e] type 00 class 0x028000 [ 9.822450] pci 0000:01:00.0: reg 0x10: [mem 0x40000000-0x4000ffff 64bit] [ 9.830060] pci 0000:01:00.0: supports D1 [ 9.834755] pci 0000:01:00.0: PME# supported from D0 D1 D3hot [ 9.841202] pci 0000:01:00.0: PME# disabled [ 9.870914] pci_bus 0000:01: fixups for bus [ 9.870934] PCI: bus1: Fast back to back transfers disabled [ 9.877183] pci_bus 0000:01: bus scan returning with max=01 [ 9.877198] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01 [ 9.884519] pci_bus 0000:00: bus scan returning with max=01 [ 9.884706] pci 0000:00:01.0: BAR 14: assigned [mem 0xf3000000-0xf30fffff] [ 9.892288] pci 0000:00:01.0: BAR 6: assigned [mem 0xf3100000-0xf31007ff pref] [ 9.900210] pci 0000:01:00.0: BAR 0: assigned [mem 0xf3000000-0xf300ffff 64bit] [ 9.908203] pci 0000:00:01.0: PCI bridge to [bus 01] [ 9.913870] pci 0000:00:01.0: bridge window [mem 0xf3000000-0xf30fffff] [ 9.921432] pcieport 0000:00:01.0: assign IRQ: got 0 [ 9.921457] pcieport 0000:00:01.0: enabling device (0140 -> 0142) [ 9.928239] pcieport 0000:00:01.0: enabling bus mastering [ 9.928693] mv_xor f1060800.xor: Marvell shared XOR driver [ 9.991035] mv_xor f1060800.xor: Marvell XOR (Registers Mode): ( xor cpy intr ) [ 10.001801] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled [ 10.010228] printk: console [ttyS0] disabled [ 10.015264] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 22, base_baud = 12500000) is a 16550A [ 10.025016] printk: console [ttyS0] enabled [ 10.034874] printk: bootconsole [earlycon0] disabled [ 10.054942] loop: module loaded [ 10.059734] nand: device found, Manufacturer ID: 0x92, Chip ID: 0xf1 [ 10.066885] nand: Eon NAND 128MiB 3,3V 8-bit [ 10.071903] nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64 [ 10.080315] Scanning device for bad blocks [ 10.115722] 3 cmdlinepart partitions found on MTD device orion_nand [ 10.122752] Creating 3 MTD partitions on "orion_nand": [ 10.128627] 0x000000000000-0x000000200000 : "U-Boot" [ 10.135838] 0x000000200000-0x000002200000 : "JFFS2" [ 10.143057] 0x000002200000-0x000007200000 : "Firmware" [ 10.151180] wireguard: WireGuard 1.0.0 loaded. See www.wireguard.com for information. [ 10.159760] wireguard: Copyright (C) 2015-2019 Jason A. Donenfeld <Jason@zx2c4.com>. All Rights Reserved. [ 10.171493] libphy: Fixed MDIO Bus: probed [ 10.177768] libphy: orion_mdio_bus: probed [ 10.199561] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 10.206961] ehci-pci: EHCI PCI platform driver [ 10.212261] ehci-orion: EHCI orion driver [ 10.217183] orion-ehci f1050000.ehci: EHCI Host Controller [ 10.223540] orion-ehci f1050000.ehci: new USB bus registered, assigned bus number 1 [ 10.232235] orion-ehci f1050000.ehci: irq 24, io mem 0xf1050000 [ 10.259918] orion-ehci f1050000.ehci: USB 2.0 started, EHCI 1.00 [ 10.266971] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.12 [ 10.276019] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 10.284005] usb usb1: Product: EHCI Host Controller [ 10.289614] usb usb1: Manufacturer: Linux 5.12.2-kirkwood-tld-1 ehci_hcd [ 10.297072] usb usb1: SerialNumber: f1050000.ehci [ 10.303215] hub 1-0:1.0: USB hub found [ 10.307739] hub 1-0:1.0: 1 port detected [ 10.313204] usbcore: registered new interface driver usb-storage [ 10.320414] mousedev: PS/2 mouse device common for all mice [ 10.327000] i2c /dev entries driver [ 10.331882] device-mapper: uevent: version 1.0.3 [ 10.337512] device-mapper: ioctl: 4.44.0-ioctl (2021-02-01) initialised: dm-devel@redhat.com [ 10.347154] device-mapper: multipath round-robin: version 1.2.0 loaded [ 10.354496] device-mapper: multipath queue-length: version 0.2.0 loaded [ 10.361879] device-mapper: multipath service-time: version 0.3.0 loaded [ 10.369303] device-mapper: dm-log-userspace: version 1.3.0 loaded [ 10.376158] device-mapper: raid: Loading target version 1.15.1 [ 10.382948] freq_table: Duplicate freq-table entries: 0 [ 10.388946] kirkwood-cpufreq kirkwood-cpufreq: Failed to register cpufreq driver [ 10.398513] hid: raw HID events driver (C) Jiri Kosina [ 10.404753] drop_monitor: Initializing network drop monitor service [ 10.412289] NET: Registered protocol family 10 [ 10.418526] Segment Routing with IPv6 [ 10.423110] RPL Segment Routing with IPv6 [ 10.427934] NET: Registered protocol family 17 [ 10.433426] Key type dns_resolver registered [ 10.438960] registered taskstats version 1 [ 10.443866] Loading compiled-in X.509 certificates [ 10.449754] zswap: loaded using pool lzo/zbud [ 10.455253] Key type ._fscrypt registered [ 10.460071] Key type .fscrypt registered [ 10.464722] Key type fscrypt-provisioning registered [ 10.472434] Key type big_key registered [ 10.507895] Key type encrypted registered [ 10.520198] Freeing unused kernel memory: 1024K [ 10.540675] Checked W+X mappings: passed, no W+X pages found [ 10.547090] Run /init as init process [ 10.551515] with arguments: [ 10.551527] /init [ 10.551536] with environment: [ 10.551543] HOME=/ [ 10.551551] TERM=linux [ 10.680041] usb 1-1: new high-speed USB device number 2 using orion-ehci [ 10.901889] usb 1-1: New USB device found, idVendor=05e3, idProduct=0608, bcdDevice=77.63 [ 10.918277] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0 [ 10.944264] usb 1-1: Product: USB2.0 Hub [ 10.955282] hub 1-1:1.0: USB hub found [ 10.974819] hub 1-1:1.0: 4 ports detected [ 11.309990] usb 1-1.1: new high-speed USB device number 3 using orion-ehci [ 11.432827] input: gpio_keys as /devices/platform/gpio_keys/input/input0 [ 11.483255] usb 1-1.1: New USB device found, idVendor=0781, idProduct=5583, bcdDevice= 1.00 [ 11.499986] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 11.508056] usb 1-1.1: Product: Ultra Fit [ 11.525948] usb 1-1.1: Manufacturer: SanDisk [ 11.535964] usb 1-1.1: SerialNumber: 4C530000100504222533 [ 11.549632] usb-storage 1-1.1:1.0: USB Mass Storage device detected [ 11.569495] scsi host0: usb-storage 1-1.1:1.0 [ 11.707878] mvneta f1074000.ethernet eth0: Using hardware mac address 6a:f8:0f:82:d2:57 [ 11.788770] mvneta f1070000.ethernet eth1: Using hardware mac address 92:fe:13:e2:ef:dc [ 11.937203] usbcore: registered new interface driver uas [ 12.651474] scsi 0:0:0:0: Direct-Access SanDisk Ultra Fit 1.00 PQ: 0 ANSI: 6 [ 12.666063] sd 0:0:0:0: [sda] 30031872 512-byte logical blocks: (15.4 GB/14.3 GiB) [ 12.680669] sd 0:0:0:0: [sda] Write Protect is off [ 12.686228] sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00 [ 12.687023] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [ 12.704044] sda: sda1 [ 12.723162] sd 0:0:0:0: [sda] Attached SCSI removable disk [ 22.063368] process '/usr/bin/fstype' started with executable stack [ 22.312085] EXT4-fs (sda1): mounting ext3 file system using the ext4 subsystem [ 22.460413] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null). Quota mode: none. [ 26.204569] thermal thermal_zone0: Temperature sensor reading not valid [ 26.302851] thermal thermal_zone0: failed to read out thermal zone (-5) [ 26.414919] systemd-udevd[372]: Using default interface naming scheme 'v240'. [ 26.515613] systemd-udevd[387]: Using default interface naming scheme 'v240'. [ 26.596622] systemd-udevd[372]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable. [ 26.641746] systemd-udevd[387]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable. [ 26.698080] cfg80211: Loading compiled-in X.509 certificates for regulatory database [ 26.756615] systemd-udevd[384]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable. [ 26.792375] sd 0:0:0:0: Attached scsi generic sg0 type 0 [ 27.777562] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [ 27.804909] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 [ 27.822815] cfg80211: failed to load regulatory.db [ 27.837408] random: crng init done [ 28.314335] ath9k 0000:01:00.0: assign IRQ: got 31 [ 28.314380] pci 0000:00:01.0: enabling bus mastering [ 28.386548] systemd-udevd[386]: Process '/usr/bin/pmount -t ext3 --noatime --umask 000 sda1 rootfs' failed with exit code 4. [ 28.494874] ath: EEPROM regdomain sanitized [ 28.494893] ath: EEPROM regdomain: 0x64 [ 28.494904] ath: EEPROM indicates we should expect a direct regpair map [ 28.494919] ath: Country alpha2 being used: 00 [ 28.494926] ath: Regpair used: 0x64 [ 28.503883] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' [ 28.507805] ieee80211 phy0: Atheros AR9287 Rev:2 mem=0x889a0000, irq=31 [ 28.539574] systemd-udevd[386]: Using default interface naming scheme 'v240'. [ 28.574892] systemd-udevd[386]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable. [ 28.587251] ath9k 0000:01:00.0 wlp1s0: renamed from wlan0 [ 28.765083] systemd-udevd[365]: Using default interface naming scheme 'v240'. [ 30.864429] EXT4-fs (sda1): re-mounted. Opts: user_xattr,acl,errors=remount-ro. Quota mode: none. [ 33.449923] Adding 524284k swap on /swapfile1. Priority:-2 extents:24 across:8314136k FS [ 35.083170] mvneta f1074000.ethernet eth0: cannot request irq 25 [ 35.227145] mvneta f1070000.ethernet eth1: cannot request irq 26 [ 36.874853] wlp1s0: authenticate with 00:26:xx:xx:xx:xx [ 36.897631] wlp1s0: send auth to 00:26:xx:xx:xx:xx (try 1/3) [ 36.913429] wlp1s0: authenticated [ 36.919980] wlp1s0: associate with 00:26:xx:xx:xx:xx (try 1/3) [ 36.932687] wlp1s0: RX AssocResp from 00:26:xx:xx:xx:xx (capab=0x31 status=0 aid=2) [ 36.941773] wlp1s0: associated [ 37.151031] wlp1s0: Limiting TX power to 27 (27 - 0) dBm as advertised by 00:26:xx:xx:xx:xx [ 40.666373] NET: Registered protocol family 15 [ 3672.740068] wlp1s0: authenticate with 00:26:xx:xx:xx:xx [ 3672.763370] wlp1s0: send auth to 00:26:xx:xx:xx:xx (try 1/3) [ 3672.844770] wlp1s0: authenticated [ 3672.854053] wlp1s0: associate with 00:26:xx:xx:xx:xx (try 1/3) [ 3672.870526] wlp1s0: RX AssocResp from 00:26:xx:xx:xx:xx (capab=0x31 status=0 aid=2) [ 3672.879766] wlp1s0: associated [ 3672.973917] wlp1s0: Limiting TX power to 27 (27 - 0) dBm as advertised by 00:26:xx:xx:xx:xx
PCIe
root@mi424:~# lspci -v
00:01.0 PCI bridge: Marvell Technology Group Ltd. Device 6560 (rev 02) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 Memory behind bridge: f3000000-f30fffff Prefetchable memory behind bridge: 00000000-000fffff [virtual] Expansion ROM at f3100000 [disabled] [size=2K] Capabilities: [40] Express Root Port (Slot+), MSI 00 01:00.0 Network controller: Qualcomm Atheros AR9287 Wireless Network Adapter (PCI-Express) (rev 01) Subsystem: Qualcomm Atheros AR9287 Wireless Network Adapter (PCI-Express) Flags: bus master, fast devsel, latency 0, IRQ 31 Memory at f3000000 (64-bit, non-prefetchable) [size=64K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit- Capabilities: [60] Express Legacy Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Virtual Channel Capabilities: [160] Device Serial Number 00-15-xx-ff-xx-xx-xx-xx Capabilities: [170] Power Budgeting <?> Kernel driver in use: ath9k Kernel modules: ath9k
LEDs
root@mi424:~# ll /sys/class/leds/
total 0 drwxr-xr-x 2 root root 0 May 15 15:09 . drwxr-xr-x 49 root root 0 May 15 15:09 .. lrwxrwxrwx 1 root root 0 May 15 15:09 ath9k-phy0 -> ../../devices/platform/mbus/mbus:pcie@82000000/pci0000:00/0000:00:01.0/0000:01:00.0/leds/ath9k-phy0 lrwxrwxrwx 1 root root 0 May 15 15:09 coax:lan -> ../../devices/platform/gpio-leds/leds/coax:lan lrwxrwxrwx 1 root root 0 May 15 15:09 coax:wan -> ../../devices/platform/gpio-leds/leds/coax:wan lrwxrwxrwx 1 root root 0 May 15 15:09 internet:green -> ../../devices/platform/gpio-leds/leds/internet:green lrwxrwxrwx 1 root root 0 May 15 15:09 internet:red -> ../../devices/platform/gpio-leds/leds/internet:red lrwxrwxrwx 1 root root 0 May 15 15:09 wps:green -> ../../devices/platform/gpio-leds/leds/wps:green lrwxrwxrwx 1 root root 0 May 15 15:09 wps:red -> ../../devices/platform/gpio-leds/leds/wps:red
Network
root@mi424:~# ifconfig
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
loop txqueuelen 1000 (Local Loopback)
RX packets 3 bytes 169 (169.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 3 bytes 169 (169.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlp1s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.0.240 netmask 255.255.255.0 broadcast 192.168.0.255
ether 00:03:7f:bf:46:90 txqueuelen 1000 (Ethernet)
RX packets 5337 bytes 916963 (895.4 KiB)
RX errors 0 dropped 67 overruns 0 frame 0
TX packets 492 bytes 64049 (62.5 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 3 time(s). Last edit at 05/15/2021 06:54PM by bodhi.
|
Re: Debian on Action Tech SG200 and MI424WR-rev-I May 15, 2021 08:53PM |
Registered: 3 years ago Posts: 112 |
|
Re: Debian on Action Tech SG200 and MI424WR-rev-I May 15, 2021 09:07PM |
Admin Registered: 13 years ago Posts: 18,997 |
8086k,
Use kwboot from your Ubuntu box. That should work.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Use kwboot from your Ubuntu box. That should work.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on Action Tech SG200 and MI424WR-rev-I May 15, 2021 09:59PM |
Registered: 3 years ago Posts: 112 |
|
Re: Debian on Action Tech SG200 and MI424WR-rev-I May 16, 2021 12:32AM |
Registered: 3 years ago Posts: 112 |
bodhi,
I know the problem. I have installed u-boot-tools, but it doesn't contain kwboot command. Can you get the amd64 version of u-boot-tools.deb contains kwboot command?
edit: I have downloaded the newer version of kwboot. Invalid image disappeared. But bootrom printed xmodem protocol error. What's that thing?
8086k
Edited 1 time(s). Last edit at 05/16/2021 01:10AM by 8086k.
I know the problem. I have installed u-boot-tools, but it doesn't contain kwboot command. Can you get the amd64 version of u-boot-tools.deb contains kwboot command?
edit: I have downloaded the newer version of kwboot. Invalid image disappeared. But bootrom printed xmodem protocol error. What's that thing?
8086k
Edited 1 time(s). Last edit at 05/16/2021 01:10AM by 8086k.
|
Re: Debian on Action Tech SG200 and MI424WR-rev-I May 16, 2021 01:12AM |
Admin Registered: 13 years ago Posts: 18,997 |
8086k,
When you see the "xmodem: Protocol error", do the following:
- Make sure the serial wires are far from the power cord (to avoid interference).
- When you see the protocol error, recall the kwboot command and immediately execute that. Repeat this quickly, as many time as needed.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
When you see the "xmodem: Protocol error", do the following:
- Make sure the serial wires are far from the power cord (to avoid interference).
- When you see the protocol error, recall the kwboot command and immediately execute that. Repeat this quickly, as many time as needed.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on Action Tech SG200 and MI424WR-rev-I May 16, 2021 01:25AM |
Registered: 3 years ago Posts: 112 |
bodhi,
I think my kwboot amd64 binary is bad. Can you post your kwboot amd64 binary? Thank you very much.
8086k
Edited 1 time(s). Last edit at 05/16/2021 01:28AM by 8086k.
user@ubuntu:~$ sudo ./kwboot -t -B 115200 /dev/ttyUSB0 -b mtdblock1.bin -p Sending boot message. Please reboot the target...| Sending boot image... 0 % [++++++.+.+.+BootROM: Invalid header checksum Booting from NAND flash l BootROM 1.34 Booting from NAND flash l BootROM 1.34 Booting from NAND flash BootROM 1.34 Booting from NAND flash BootROM 1.34 Booting from NAND flash BootROM 1.34 Booting from NAND flash BootROM 1.34 Booting from NAND flash BootROM 1.34 Booting from NAND flash BootROM 1.34 Booting from NAND flash BootROM 1.34 Booting from NAND flash BootROM 1.34 Booting from NAND flash BootROM 1.34 Booting from NAND flash BootROM 1.34 Booting from NAND flash BootROM 1.34 Booting from NAND flash BootROM 1.34 Booting from NAND flash BootROM 1.34 Booting from NAND flash BootROM 1.34 Booting from NAND flash BootROM: T+xmodem: Protocol errorNow, as you see. Bootrom said header checksum is invalid.
I think my kwboot amd64 binary is bad. Can you post your kwboot amd64 binary? Thank you very much.
8086k
Edited 1 time(s). Last edit at 05/16/2021 01:28AM by 8086k.
|
Re: Debian on Action Tech SG200 and MI424WR-rev-I May 16, 2021 04:16PM |
Admin Registered: 13 years ago Posts: 18,997 |
This seems wrong
mtdblock1.bin does not seem to contain u-boot.
Check the header:
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
user@ubuntu:~$ sudo ./kwboot -t -B 115200 /dev/ttyUSB0 -b mtdblock1.bin -p
mtdblock1.bin does not seem to contain u-boot.
Check the header:
mkimage -l mtdblock1.bin
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on Action Tech SG200 and MI424WR-rev-I May 16, 2021 06:00PM |
Registered: 3 years ago Posts: 112 |
|
Re: Debian on Action Tech SG200 and MI424WR-rev-I May 16, 2021 06:36PM |
Admin Registered: 13 years ago Posts: 18,997 |
8086k,
> Mtdblock1 is the uboot. I have checked it.
As usual, please post whatever you did, for confirmation.
> I have
> also tried mi424wr's uboot, it always print 'bad
> message'. So I think my kwboot binary is not good.
kwboot binary that comes with the distro is always good. If you want to see it is running OK then do this:
- Connect serial console.
- Run kwboot on you Ubunt VM this way: become root, and execute the kwboot in terminal mode
And then power up the ZTE. You should be able to control serial console this way.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> Mtdblock1 is the uboot. I have checked it.
As usual, please post whatever you did, for confirmation.
mkimage -L mtdblock1.bin
> I have
> also tried mi424wr's uboot, it always print 'bad
> message'. So I think my kwboot binary is not good.
kwboot binary that comes with the distro is always good. If you want to see it is running OK then do this:
- Connect serial console.
- Run kwboot on you Ubunt VM this way: become root, and execute the kwboot in terminal mode
apt-get install u-boot-tools su - kwboot -t -B 115200 /dev/ttyUSB0
And then power up the ZTE. You should be able to control serial console this way.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on Action Tech SG200 and MI424WR-rev-I May 17, 2021 02:45PM |
Registered: 3 years ago Posts: 13 |
@8086k
If you really want to be sure about having the newest kwboot binary, you can compile it from source pretty easily.
Just clone the u-boot git repository and run this:
That said, I'm sure the one in the Ubuntu repositories is fine.
I had the exact same problem that you're having when I was trying to kwboot my MI424WR-I. I even bought a new UART adapter. In the end, I couldn't get it to work. I'm curious about why it works for bodhi. On average, how many tries is it taking you?
Edited 1 time(s). Last edit at 05/17/2021 02:48PM by bkallus.
If you really want to be sure about having the newest kwboot binary, you can compile it from source pretty easily.
Just clone the u-boot git repository and run this:
make defconfig make tools-allThe kwboot binary will be in the tools directory.
That said, I'm sure the one in the Ubuntu repositories is fine.
I had the exact same problem that you're having when I was trying to kwboot my MI424WR-I. I even bought a new UART adapter. In the end, I couldn't get it to work. I'm curious about why it works for bodhi. On average, how many tries is it taking you?
Edited 1 time(s). Last edit at 05/17/2021 02:48PM by bkallus.
|
Re: Debian on Action Tech SG200 and MI424WR-rev-I May 17, 2021 04:04PM |
Admin Registered: 13 years ago Posts: 18,997 |
bkallus,
> I had the exact same problem that you're having
> when I was trying to kwboot my MI424WR-I. I even
> bought a new UART adapter. In the end, I couldn't
> get it to work. I'm curious about why it works for
> bodhi. On average, how many tries is it taking
> you?
I'm running kwboot from another ARM box (Zyxel NSA310S). It works immediately.
Perhaps you guys should try kwboot from another ARM box such as rPi.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> I had the exact same problem that you're having
> when I was trying to kwboot my MI424WR-I. I even
> bought a new UART adapter. In the end, I couldn't
> get it to work. I'm curious about why it works for
> bodhi. On average, how many tries is it taking
> you?
I'm running kwboot from another ARM box (Zyxel NSA310S). It works immediately.
Perhaps you guys should try kwboot from another ARM box such as rPi.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on Action Tech SG200 and MI424WR-rev-I May 18, 2021 07:43AM |
Registered: 3 years ago Posts: 112 |
bkallus,
Thanks, I installed ubuntu 20.04 and now kwboot can send the whole image. But F660 is still not booting from uart. When the transfer is done, my F660 resets and starts to boot from NAND flash. I have also tried mi424wr's uboot image, it stops responding when the transfer is done(this isn't strange).
bodhi,
The uboot of F660 is interesting, it's header is strange but it works on the NAND flash. I can't figure out any more information, I hope you can look at it sometime.
edit: Now the kwboot is working. I don't know why when I edited the uboot image at will, it booted succesfully from kwboot. That's unbelievable but it's truth.
8086k
Edited 1 time(s). Last edit at 05/18/2021 10:22AM by 8086k.
Thanks, I installed ubuntu 20.04 and now kwboot can send the whole image. But F660 is still not booting from uart. When the transfer is done, my F660 resets and starts to boot from NAND flash. I have also tried mi424wr's uboot image, it stops responding when the transfer is done(this isn't strange).
bodhi,
The uboot of F660 is interesting, it's header is strange but it works on the NAND flash. I can't figure out any more information, I hope you can look at it sometime.
edit: Now the kwboot is working. I don't know why when I edited the uboot image at will, it booted succesfully from kwboot. That's unbelievable but it's truth.
8086k
Edited 1 time(s). Last edit at 05/18/2021 10:22AM by 8086k.
|
Re: Debian on Action Tech SG200 and MI424WR-rev-I May 18, 2021 04:28PM |
Admin Registered: 13 years ago Posts: 18,997 |
8086k,
> edit: Now the kwboot is working. I don't know why
> when I edited the uboot image at will, it booted
> succesfully from kwboot. That's unbelievable but
> it's truth.
As usual, to help future users who look to do the same thing.
Please post the log of what you did. And also post whatever the u-boot image you use to kwboot this F660 box.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> edit: Now the kwboot is working. I don't know why
> when I edited the uboot image at will, it booted
> succesfully from kwboot. That's unbelievable but
> it's truth.
As usual, to help future users who look to do the same thing.
Please post the log of what you did. And also post whatever the u-boot image you use to kwboot this F660 box.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on Action Tech SG200 and MI424WR-rev-I May 19, 2021 07:34AM |
Registered: 3 years ago Posts: 112 |
How to boot ZTE F420/F460/F620/F660 with 88f6560 into u-boot through UART
This is the u-boot file that I used. I will do more research on it later, maybe I will improve it.
Use this file like following:
1,Install the latest version of Ubuntu(I'm using Ubuntu 20.04)
2,Use 'sudo apt install u-boot-tools' to install kwboot
3,Connect your F420/F460/F620/F660 to your Ubuntu PC using UART
4,Use 'sudo su' to switch to root mode
5,Use this command to boot your F420/F460/F620/F660
This will appear in the terminal if UART boot is successful.
8086k
Edited 3 time(s). Last edit at 05/21/2021 03:26AM by 8086k.
This is the u-boot file that I used. I will do more research on it later, maybe I will improve it.
Use this file like following:
1,Install the latest version of Ubuntu(I'm using Ubuntu 20.04)
2,Use 'sudo apt install u-boot-tools' to install kwboot
3,Connect your F420/F460/F620/F660 to your Ubuntu PC using UART
4,Use 'sudo su' to switch to root mode
5,Use this command to boot your F420/F460/F620/F660
kwboot -t -B 115200 /dev/ttyUSB0 -b uboot-download.bin -p(Replace ttyUSB0 with your UART device)
This will appear in the terminal if UART boot is successful.
root@ubuntu:/home/user# kwboot -t -B 115200 /dev/ttyUSB0 -b uboot-download.bin -p Sending boot message. Please reboot the target...\ Sending boot image... 0 % [......................................................................] 1 % [......................................................................] 3 % [......................................................................] 5 % [......................................................................] 6 % [......................................................................] 8 % [......................................................................] 10 % [......................................................................] 11 % [......................................................................] 13 % [......................................................................] 15 % [......................................................................] 17 % [......................................................................] 18 % [......................................................................] 20 % [......................................................................] 22 % [......................................................................] 23 % [......................................................................] 25 % [......................................................................] 27 % [......................................................................] 29 % [......................................................................] 30 % [......................................................................] 32 % [......................................................................] 34 % [......................................................................] 35 % [......................................................................] 37 % [......................................................................] 39 % [......................................................................] 41 % [......................................................................] 42 % [......................................................................] 44 % [......................................................................] 46 % [......................................................................] 47 % [......................................................................] 49 % [......................................................................] 51 % [......................................................................] 53 % [......................................................................] 54 % [......................................................................] 56 % [......................................................................] 58 % [......................................................................] 59 % [......................................................................] 61 % [......................................................................] 63 % [......................................................................] 64 % [......................................................................] 66 % [......................................................................] 68 % [......................................................................] 70 % [......................................................................] 71 % [......................................................................] 73 % [......................................................................] 75 % [......................................................................] 76 % [......................................................................] 78 % [......................................................................] 80 % [......................................................................] 82 % [......................................................................] 83 % [......................................................................] 85 % [......................................................................] 87 % [......................................................................] 88 % [......................................................................] 90 % [......................................................................] 92 % [......................................................................] 94 % [......................................................................] 95 % [......................................................................] 97 % [......................................................................] 99 % [....................................] [Type Ctrl-\ + c to quit] U-Boot 2009.08 ( 9月 06 2012 - 16:23:20) Hit enter to stop autoboot: 0 =>
8086k
Edited 3 time(s). Last edit at 05/21/2021 03:26AM by 8086k.
|
Re: Debian on Action Tech SG200 and MI424WR-rev-I May 19, 2021 04:40PM |
Admin Registered: 13 years ago Posts: 18,997 |
|
Re: Debian on Action Tech SG200 and MI424WR-rev-I May 20, 2021 08:41AM |
Registered: 3 years ago Posts: 112 |
bodhi,
Can you understand assembly code of arm? I want to autoboot openwrt. Rebuild u-boot is impossible and counterfeiting kernel checksum is impossible too.
Exactly, I have the good backup of original firmware. I get 'No Version Available on Flash' only during using my openwrt and don't interrupt autoboot.
8086k
Can you understand assembly code of arm? I want to autoboot openwrt. Rebuild u-boot is impossible and counterfeiting kernel checksum is impossible too.
Exactly, I have the good backup of original firmware. I get 'No Version Available on Flash' only during using my openwrt and don't interrupt autoboot.
8086k
|
Re: Debian on Action Tech SG200 and MI424WR-rev-I May 20, 2021 04:40PM |
Admin Registered: 13 years ago Posts: 18,997 |
8086k,
Set the envs as described in this post:
https://forum.doozan.com/read.php?2,78499,120544#msg-120544
Save the envs with savenv.
And then reboot.
When you see the u-boot banner
Interrupt the countdown and
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Set the envs as described in this post:
https://forum.doozan.com/read.php?2,78499,120544#msg-120544
Save the envs with savenv.
And then reboot.
When you see the u-boot banner
BootROM 1.34 Booting from NAND flash BootROM: Image checksum verification PASSED U-Boot 2009.08 ( 5月 13 2013 - 18:06:09) Hit enter to stop autoboot: 0
Interrupt the countdown and
printenvPlease post the entire serial boot log up until this point (everything, including the setenv commands before reboot).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on Action Tech SG200 and MI424WR-rev-I May 21, 2021 06:06AM |
Registered: 3 years ago Posts: 112 |
bodhi,
Have you tried kirkwood ethernet driver yet? I hope it will work. If not, you can choose to use the old armada driver on the new kernel or look at the patch of the driver source code.
I will soon post it. But I can't understand why you want it. U-boot envs can be set successfully and written to nand. I'm now using an env to boot openwrt more quickly. It doesn't affect uboot to boot stock firmware.
I have done some research on F660's pci-e device. Now I think the config in dts is correct but my rtl8192ce driver is not configured properly or isn't correct. I would like to upgrade the kernel version.
What is Fast back to back transfers? For PCI-E bus 1, it is disabled on stock firmware of f660, enabled on linux 3.14 kernel. According to the stock log, RTL8192CE is using PCI-E bus 1.
8086k
Edited 1 time(s). Last edit at 05/21/2021 10:01AM by 8086k.
Have you tried kirkwood ethernet driver yet? I hope it will work. If not, you can choose to use the old armada driver on the new kernel or look at the patch of the driver source code.
I will soon post it. But I can't understand why you want it. U-boot envs can be set successfully and written to nand. I'm now using an env to boot openwrt more quickly. It doesn't affect uboot to boot stock firmware.
I have done some research on F660's pci-e device. Now I think the config in dts is correct but my rtl8192ce driver is not configured properly or isn't correct. I would like to upgrade the kernel version.
What is Fast back to back transfers? For PCI-E bus 1, it is disabled on stock firmware of f660, enabled on linux 3.14 kernel. According to the stock log, RTL8192CE is using PCI-E bus 1.
8086k
Edited 1 time(s). Last edit at 05/21/2021 10:01AM by 8086k.
|
Re: Debian on Action Tech SG200 and MI424WR-rev-I May 21, 2021 05:10PM |
Admin Registered: 13 years ago Posts: 18,997 |
8086k,
> Have you tried kirkwood ethernet driver yet? I
> hope it will work.
I tried once and it did not work. The stock driver is really old and hard to tell, but it looks like the previous incarnation of mvneta (written by Marvell engineers). I did not spend much time on trying Kirkwood driver, though.
>If not, you can choose to use
> the old armada driver on the new kernel
This is not possible. They are too different structurally.
>
> I will soon post it. But I can't understand why
> you want it. U-boot envs can be set successfully
> and written to nand. I'm now using an env to boot
> openwrt more quickly. It doesn't affect uboot to
> boot stock firmware.
OK. I don't need the bootlog. I only want to see exactly how the envs were saved or not saved with the original stock u-boot. The MI424WR-rev-I uses a different version of stock u-boot and it does not have limitation of saving bootcmd.
>
> I have done some research on F660's pci-e device.
> Now I think the config in dts is correct but my
> rtl8192ce driver is not configured properly or
> isn't correct. I would like to upgrade the kernel
> version.
Unfortunatly, I cannot help with kernel 3.14 rtl8192ce driver. For the F660 PCIe, rtl8192ce should work immediately with new kernel (i.e linux-5.11.4-kirkwood-tld-1).
The only issue is Ethernet. Currently, the IRQ seems to be wrong systematically. Kirkwood IRQs and Armada IRQs are different, and I'm still not sure yet which path to take (either hacking it, or try to reconcile it the right way).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> Have you tried kirkwood ethernet driver yet? I
> hope it will work.
I tried once and it did not work. The stock driver is really old and hard to tell, but it looks like the previous incarnation of mvneta (written by Marvell engineers). I did not spend much time on trying Kirkwood driver, though.
>If not, you can choose to use
> the old armada driver on the new kernel
This is not possible. They are too different structurally.
>
> I will soon post it. But I can't understand why
> you want it. U-boot envs can be set successfully
> and written to nand. I'm now using an env to boot
> openwrt more quickly. It doesn't affect uboot to
> boot stock firmware.
OK. I don't need the bootlog. I only want to see exactly how the envs were saved or not saved with the original stock u-boot. The MI424WR-rev-I uses a different version of stock u-boot and it does not have limitation of saving bootcmd.
>
> I have done some research on F660's pci-e device.
> Now I think the config in dts is correct but my
> rtl8192ce driver is not configured properly or
> isn't correct. I would like to upgrade the kernel
> version.
Unfortunatly, I cannot help with kernel 3.14 rtl8192ce driver. For the F660 PCIe, rtl8192ce should work immediately with new kernel (i.e linux-5.11.4-kirkwood-tld-1).
The only issue is Ethernet. Currently, the IRQ seems to be wrong systematically. Kirkwood IRQs and Armada IRQs are different, and I'm still not sure yet which path to take (either hacking it, or try to reconcile it the right way).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on Action Tech SG200 and MI424WR-rev-I May 22, 2021 02:14AM |
Registered: 3 years ago Posts: 112 |
bodhi,
My F660 box's uboot is more complex. Bootcmd doesn't contain the command that copies the kernel to RAM. It is done before bootcmd. Then uboot will do a checksum on the kernel to decide whether to run bootcmd. If the checksum doesn't pass, uboot will just print 'No Version Available on Flash'. If the checksum passes, uboot will continue to run bootcmd. I'm still not sure if the uboot will set bootcmd to a fixed value before running it.
8086k
My F660 box's uboot is more complex. Bootcmd doesn't contain the command that copies the kernel to RAM. It is done before bootcmd. Then uboot will do a checksum on the kernel to decide whether to run bootcmd. If the checksum doesn't pass, uboot will just print 'No Version Available on Flash'. If the checksum passes, uboot will continue to run bootcmd. I'm still not sure if the uboot will set bootcmd to a fixed value before running it.
8086k
|
Re: Debian on Action Tech SG200 and MI424WR-rev-I May 22, 2021 04:01AM |
Admin Registered: 13 years ago Posts: 18,997 |
8086k,
> My F660 box's uboot is more complex. Bootcmd
> doesn't contain the command that copies the kernel
> to RAM. It is done before bootcmd.
That's a dirty hack they did :) nothing complex about it. Usually we don't hard code this in u-boot.
>I'm still not sure if the uboot will set
> bootcmd to a fixed value before running it.
You'll have answer to this question if you did what I asked before.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 05/22/2021 04:01AM by bodhi.
> My F660 box's uboot is more complex. Bootcmd
> doesn't contain the command that copies the kernel
> to RAM. It is done before bootcmd.
That's a dirty hack they did :) nothing complex about it. Usually we don't hard code this in u-boot.
>I'm still not sure if the uboot will set
> bootcmd to a fixed value before running it.
You'll have answer to this question if you did what I asked before.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 05/22/2021 04:01AM by bodhi.
|
Re: Debian on Action Tech SG200 and MI424WR-rev-I May 22, 2021 05:44AM |
Registered: 3 years ago Posts: 112 |
bodhi,
I can make it autoboot by changing a command string. But it will stop uboot from initializing the ethernet device. Finally, the ethernet won't work. How can I crack it by not changing the assembly code?
I'm analyzing uboot code with IDA pro(assembly code is so annoying), The checksum is in assembly code. I have found the function which print 'No Version Available On Flash'. I'm trying to modify it. Can you offer some help about signing the uboot image? I have tested and found that bootrom will check the checksum. Kwboot will do the checksum, but it can't save the image.
8086k
Edited 2 time(s). Last edit at 05/22/2021 07:34AM by 8086k.
I can make it autoboot by changing a command string. But it will stop uboot from initializing the ethernet device. Finally, the ethernet won't work. How can I crack it by not changing the assembly code?
I'm analyzing uboot code with IDA pro(assembly code is so annoying), The checksum is in assembly code. I have found the function which print 'No Version Available On Flash'. I'm trying to modify it. Can you offer some help about signing the uboot image? I have tested and found that bootrom will check the checksum. Kwboot will do the checksum, but it can't save the image.
8086k
Edited 2 time(s). Last edit at 05/22/2021 07:34AM by 8086k.
|
Re: Debian on Action Tech SG200 and MI424WR-rev-I May 22, 2021 05:09PM |
Admin Registered: 13 years ago Posts: 18,997 |
8086k,
I have no idea, I am not familiar with ARM assembler code either.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
I have no idea, I am not familiar with ARM assembler code either.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on Action Tech SG200 and MI424WR-rev-I May 23, 2021 09:27AM |
Registered: 3 years ago Posts: 112 |
|
Re: Debian on Action Tech SG200 and MI424WR-rev-I May 23, 2021 04:36PM |
Admin Registered: 13 years ago Posts: 18,997 |
8086k,
>I'm
> now in linux5.4 and rtl8192ce is still not
> working.
Try booting Debian on USB using Debian-5.2.9-kirkwood-tld-1-rootfs-bodhi.tar.bz2. I'm quite positive that rtl8192ce would work with my latest DTS (for the MI424WR-rev-I).
Use this Debian rootfs to test, it is easier to troubleshoot problems with Debian.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 05/23/2021 04:40PM by bodhi.
>I'm
> now in linux5.4 and rtl8192ce is still not
> working.
Try booting Debian on USB using Debian-5.2.9-kirkwood-tld-1-rootfs-bodhi.tar.bz2. I'm quite positive that rtl8192ce would work with my latest DTS (for the MI424WR-rev-I).
Use this Debian rootfs to test, it is easier to troubleshoot problems with Debian.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 05/23/2021 04:40PM by bodhi.
