MM, You're right, I didn't like the rc version (bugs), so I posted the stable,and in a new theme: https://forum.doozan.com/read.php?4,138721,138721by cmp18 - Debian
DO NOT FLASH OTHER DEVICES! This UBI only for specific NAND flash (Samsung NAND 1GiB 3,3V 8-bit, Manufacturer ID: 0xec, Chip ID: 0xd3) 1) Debian (rootfs via debootstrap, systemd logs in ram) Link (images and howto) 2) OpenWRT with official OpenWRT kernel (kmod packages are working) (official openwrt kernel config for kirkwood without HIGHMEM, therefore only 768Mb RAM visible) Linkby cmp18 - Rescue System
Great, thanks, happy new year!by cmp18 - Debian
MM, there probably aren't many such devices outside of Russia, so I'll give you a link to openwrt and a manual here: https://storage.vysm.ru/s/N2MqXLx7bdEnZb5 (outdated and deleted, see later posts)by cmp18 - Debian
I tested the new dtb - it looks like no changes bootlog in attachmentby cmp18 - Debian
just in case, bootlog of the stock embedded firmware in attachment (before that I posted the log of the stock firmware based on deb6) envs: baudrate=115200 bootargs=ubi.mtd=3 ramdisk_size=41000 root=/dev/ram0 video=xgifb:mode:1024x768x32 mtdparts=orion_nand:4M(U-Boot),4M(uImage),24M(uInitrd),-(ubipart) boot:file:// conf:file:// bootcmd=run gcload; stoptc; bootm 0x800000 0xc000000 bootdelaby cmp18 - Debian
MM Wrote: ------------------------------------------------------- > gt used ext. powered USB hub to obtane log, > > log with no errors from pin controller, but > gt's last post before he disappeared from > the topic: > >Bodhi, is it ok to ask to tinker with dtb a > little > > more? Usb devices are not powering up in > linux... > > gt didnby cmp18 - Debian
bodhi, USB flash drive was not connected during the last test. here is a new test with a connected USB flash drive: Marvell>> md.l 0xF1010000 8 f1010000: 01111111 00003311 33331100 33003333 .....3....3333.3 f1010010: 40000033 00004444 00000000 00000000 3..@DD.......... Marvell>> md.l 0xF1010100 1 f1010100: 00000080 .... Marvell>> md.l 0xF1010140 1 f1010140:by cmp18 - Debian
commands: Marvell>> md.l 0xF1010000 8 f1010000: 01111111 00003311 33331100 33003333 .....3....3333.3 f1010010: 40000033 00004444 00000000 00000000 3..@DD.......... Marvell>> md.l 0xF1010100 1 f1010100: 00000080 .... Marvell>> md.l 0xF1010140 1 f1010140: 00018000 .... Marvell>> usb reset (Re)start USB... USB: Register 10011 NbrPorts 1 USB EHCI 1.0by cmp18 - Debian
bodhi, hmm, I just tested the kernel 6.11.6 with the new dtb, but nothing has changed - the same usb errors that I and MM wrote about aboveby cmp18 - Debian
bodhi, thanks a lot for the help and for the device tree files. I will test and publish the results. I have good news too - 6.11 has been working stably on other new devices all this time. These devices were shipped with OSes: windows ce, or linux embedded, or linux based on debian 6. The boot log for stock fw deb6 based in attachment (got it by setting console=ttyS0,115200n8 - stockby cmp18 - Debian
bodhi, I have a similar problem and errors with usb, but there is no such problem on the stock 2.6.39.2 kernel (usb works fine). maybe the answer is in these lines: MMs errors: [ 7.683201][ T21] kirkwood-pinctrl f1010000.pin-controller: pin PIN45 already requested by f1010000.pin-controller; cannot claim for regulators [ 7.696469][ T21] kirkwood-pinctrl f1010000.pin-controllby cmp18 - Debian
MM, it's cool that kernel 6.11 has loaded normally at you device. But I did a lot of tests with kernel 6.11 with my device: 1) booting from nand with kernel+initrd 2) booting from usb repeating everything according to bodhi's instruction 1in1 (kernel, unitrd, right addresses... I used dtb from bodhi's post on this topic). But the result is the same - 6.11 can boot normal andby cmp18 - Debian
PS About the usb - I was happy early (I just looked that the name of the device is being determined), but I can't connect the USB stick for expand storage, the output: [ 3354.709259] usb 1-1.4: new high-speed USB device number 5 using orion-ehci [ 3354.874047] usb 1-1.4: New USB device found, idVendor=05e3, idProduct=0712, bcdDevice=92.28 [ 3354.883227] usb 1-1.4: New USB device stringby cmp18 - Debian
MM, I don't need a USB stick with rootfs, I use the built-in NAND 1GB flash with ubifs for OS and etc. In any case, the kernel should at least output something to the console (even without rootfs), and not freeze without outputs bodhi, thank you so much! your dts/dtb are working fine for my device (network and usb are working, iperf ~700 Mbits/sec), but the device is workingby cmp18 - Debian
hi again, bdinfo arch_number = 0x00000D54 boot_params = 0x00000100 DRAM bank = 0x00000000 -> start = 0x00000000 -> size = 0x20000000 DRAM bank = 0x00000001 -> start = 0x20000000 -> size = 0x20000000 ethaddr = 02:50:43:d9:43:39 ip_addr = 192.168.10.10 baudrate = 115200 bps TLB addr = 0x3FFF0000 relocaddr = 0x3FF72000 reloc off = 0xby cmp18 - Debian
bodhi, thanks for the answers and help, after the weekend when I will be near the device, I will execute bdinfo and mii info commands and publish the output. Also, I will try an existing DTBs for other boxes and publish results. MM, thanks, I will try kirkwood-promwad-wtplug.dtb from that topic (from last message) and publish results.by cmp18 - Debian
Hi, i have a device Promwad-ThinClient (or AK Systems Thin client AK1100) (or DEPO Sky A60). Uboot output: U-Boot 2011.06 (Jan 03 2013 - 16:19:06) Promwad-ThinClient SoC: Kirkwood 88F6282_?? RevID 0x01 DRAM: 1 GiB NAND: 1024 MiB In: serial Out: serial Err: serial Net: egiga0, egiga1 88E1121 Initialized on egiga0, devadr 1 88E1121 Initialized on egiga1, devadr 0 Hitby cmp18 - Debian