Promwad-ThinClient - can't boot 6.11 kernel

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
Hit any key to stop autoboot:  0 
Marvell>>

This is a thin client armv5tel, in my country they are sold in large quantities at flea markets for pennies.

Some guy has already created a topic about my device - his thread helped me - it has links to source code of stock uboot (2011.06) and stock downstream kernel (2.6.39.2).

For this device I used the stock downstream kernel + openwrt 23.05.5 rootfs (screenshot in attachments) - and it works fine (network, userspace software, etc), but stock downstream kernel a very old, that's why a lot of software doesn't work correctly (for example - firefall (nf) says that the netlink kernel interface is incompatible, etc).

When, I try the stock downstream kernel + debian 12 rootfs - but the device does not start (because systemd needs 3+ kernel as far as I remember) = with stock kernel I can run only debain 7 or older.



That is, a newer kernel is needed.

There is a 6.11 kernel from bodhi for this SoC on this forum, I try it, but got error:

Marvell>> tftpboot 0x1000000 uImage
Using egiga0 device
TFTP from server 192.168.10.1; our IP address is 192.168.10.10
Filename 'uImage'.
Load address: 0x1000000
Loading: #################################################################
	 #################################################################
	 #################################################################
	 #################################################################
	 #################################################################
	 #################################################################
	 ##########
done
Bytes transferred = 5871096 (5995f8 hex)
Marvell>> bootm 0x1000000
## Booting kernel from Legacy Image at 01000000 ...
   Image Name:   Linux-6.11.6-kirkwood-tld-1
   Created:      2024-11-28   8:45:30 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    5871032 Bytes = 5.6 MiB
   Load Address: 00800000
   Entry Point:  00800000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...


Error: invalid dtb and unrecognized/unsupported machine ID
  r1=0x00000d54, r2=0x00000100
  r2[]=05 00 00 00 01 00 41 54 00 00 00 00 00 00 00 00
Available machine support:

ID (hex)	NAME
ffffffff	Generic DT based system
ffffffff	Marvell Kirkwood (Flattened Device Tree)

Please check your kernel config and/or bootloader.

*for the test, I started kernel from tftp, but in general I store OS at 1G nand




So, I understand that the reason for the error of starting a new kernel - my old uboot without FDT. And there is no newer uboot for my board
uImage I was created like this: mkimage -A arm -O linux -T kernel -C none -a 0x1000000 -e 0x1000000 -n Linux-6.11.6-kirkwood-tld-1 -d zImage-6.11.6-kirkwood-tld-1 uImage.


I tried to extract dtb/dts from my running system/kernel with various utilities (binwalk, extract-dtb, etc) + I tried extract dts/dtb from working system (from /sys, /proc, etc) - but I couldn't find dts/dtb anywhere (maybe my kernel uses an older mechanism than dts/dtb?)


printenv:

baudrate=115200
bootcmd=tc_sleep; tc_rootfs_update; setenv bootargs ${x_bootargs} ${x_bootargs_root}; run x_bootcmd_kernel; bootm 0x1000000;
bootdelay=1
eth1addr=02:50:43:55:26:c6
ethact=egiga0
ethaddr=02:50:43:fd:60:de
ipaddr=192.168.10.10
serverip=192.168.10.1
stderr=serial
stdin=serial
stdout=serial
tc_is_env_updated=yes
x_bootargs=console=tty1 console=ttyS0,115200n8 loglevel=9 mtdparts=orion_nand:1M(U-Boot),4M(uImage),-(ubipart)
x_bootargs_root=ubi.mtd=2 root=ubi0:rootfs rootfstype=ubifs
x_bootcmd_kernel=nand read.e 0x1000000 0x100000 0x400000

Environment size: 585/262140 bytes

(kernel 4M partition is enough for the stock, but for 6.11 in the future I will expand it without any problems)


uboot help:
in attachments

---
Please give me some ideas about questions:
1) How can I run the new 6.11 kernel from bodhi? Сan the downstream kernel sources or stock uboot sources help me in this? (with extract dts/dtb and etc) (I don't care that SiS video card won't work with new kernel)
2) Will it be difficult for me to build a new uboot for my board if I have stock uboot sources? If not difficult, what information about the board from stock uboot sources will I need to transfer to the new uboot sources? (I would be grateful for links to guides for this)
(the second question is most likely beyond my power, I asked purely out of interest)



Edited 6 time(s). Last edit at 11/29/2024 10:22AM by cmp18.

cmp18,

Here for how to boot this box with stock u-boot:

https://forum.doozan.com/read.php?2,102054,105374#msg-105374

The DTB is needed to be appended to uImage, though. Let me take sometime to read that old thread again.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 11/29/2024 01:44PM by bodhi.

Quote

I tried to extract dtb/dts from my running system/kernel with various utilities (binwalk, extract-dtb, etc) + I tried extract dts/dtb from working system (from /sys, /proc, etc) - but I couldn't find dts/dtb anywhere (maybe my kernel uses an older mechanism than dts/dtb?)

Old kernels don't have FDT. So you have to use an existing DTB for another box to boot it first. And then I can create a new DTS/DTB for you.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

cmp18,

Power up, interrupt serial console and

bdinfo
mii info

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 11/29/2024 02:51PM by bodhi.

Hi, try DTB from this topic
https://forum.doozan.com/read.php?2,133204,133272,quote=1

for two or more usb sticks hub with external power requerd

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.

MM,

> Hi, try DTB from this topic
> https://forum.doozan.com/read.php?2,133204,133272,quote=1
>
> for two or more usb sticks hub with external power
> requerd

Thanks! I forgot all about it. Probably because @gt suddenly stop posting. So that DTB might work only partially.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Here is the DTB, with its DTS also attached.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

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   = 0x3F972000
irq_sp      = 0x3FE31F68
sp start    = 0x3FE31F58
FB base     = 0x00000000

mii info

PHY 0x00: OUI = 0x5043, Model = 0x0B, Rev = 0x03,  10baseT, HDX
PHY 0x01: OUI = 0x5043, Model = 0x0B, Rev = 0x03, 1000baseT, FDX

also, I tried to run the kernel by adding your dtb (cat file.dtb >> zImage ; mkimage ...), but kernel silent via serial com (rs-232) port:

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
Hit any key to stop autoboot:  0 

NAND read: device 0 offset 0x100000, size 0xa00000
 10485760 bytes read: OK
## Booting kernel from Legacy Image at 01000000 ...
   Image Name:   Linux-6.11.6-kirkwood-tld-1
   Created:      2024-12-02   8:59:00 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    5882531 Bytes = 5.6 MiB
   Load Address: 01000000
   Entry Point:  01000000
   Verifying Checksum ... OK
   XIP Kernel Image ... OK
OK

Starting kernel ...

current envs:

Marvell>> printenv 
baudrate=115200
bootcmd=tc_sleep; tc_rootfs_update; setenv bootargs ${x_bootargs} ${x_bootargs_root}; run x_bootcmd_kernel; bootm 0x1000000;
bootdelay=3
eth1addr=02:50:43:16:b8:61
ethact=egiga0
ethaddr=02:50:43:52:f3:44
ipaddr=192.168.10.10
serverip=192.168.10.1
stderr=serial
stdin=serial
stdout=serial
tc_is_env_updated=yes
x_bootargs=console=ttyS0,115200n8 loglevel=9 mtdparts=orion_nand:1M(U-Boot),10M(uImage),-(ubipart) earlyprintk=serial
x_bootargs_root=ubi.mtd=2 root=ubi0:rootfs rootfstype=ubifs
x_bootcmd_kernel=nand read 0x1000000 0x100000 0xA00000

Environment size: 590/262140 bytes

Edited 1 time(s). Last edit at 12/02/2024 04:06AM by cmp18.

cmp18,

Set envs to boot from usb, see manual by bodhi:

https://forum.doozan.com/read.php?2,102054,105374#msg-105374

cmp18,

create rootfs on USB stick, see

https://forum.doozan.com/read.php?2,12096

update 01 Nov 2023

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 working only with kernel 6.6.3-kirkwood-tld-1 and older. With newer kernels - the trouble that I wrote about above: the device boot once out of ten times (and works fine). in the other nine times - there is a kernel freeze without outputs after "Starting kernel ...".
However, 6.6.3 kernel are enough for me, so, thank you very much again.

if it's interesting, I added the log of the rare successful boot of the 6.11 kernel, and stable successful boot of the 6.6.3 kernel to the attachment.

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 strings: Mfr=0, Product=1, SerialNumber=2
[ 3354.891343] usb 1-1.4: Product: USB Storage
[ 3354.896269] usb 1-1.4: SerialNumber: 000000009225
[ 3354.919405] usb 1-1.4: rejected 1 configuration due to insufficient available bus power
[ 3354.928212] usb 1-1.4: no configuration chosen from 1 choice

do I need to increase the power in dts/dtb?
or dts/dtb for usb incorrect? there is a usb PIN48 error in the kernel messages:

root@depo-sky-a60:~# dmesg -lerr
[    0.236969] [Firmware Bug]: Feroceon L2: bootloader left the L2 cache on!
[    6.997981] kirkwood-pinctrl f1010000.pin-controller: pin PIN48 already requested by f1010000.pin-controller; cannot claim for regulators
[    7.011269] kirkwood-pinctrl f1010000.pin-controller: pin-48 (regulators) status -22
[    7.019844] kirkwood-pinctrl f1010000.pin-controller: could not request pin 48 (PIN48) from group mpp48  on device f1010000.pin-controller
[    7.033123] simple-pm-bus regulators: Error applying setting, reverse things back

This is not critical for me, but it would be nice to fix it if possible



Edited 4 time(s). Last edit at 12/03/2024 12:13PM by cmp18.

cmp18,

> 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 working only
> with kernel 6.6.3-kirkwood-tld-1 and older. With
> newer kernels - the trouble that I wrote about
> above: the device boot once out of ten times (and
> works fine). in the other nine times - there is a
> kernel freeze without outputs after "Starting
> kernel ...".
> However, 6.6.3 kernel are enough for me, so, thank
> you very much again.
>
> if it's interesting, I added the log of the
> rare successful boot of the 6.11 kernel, and
> stable successful boot of the 6.6.3 kernel to the
> attachment.

Looking at both boot log, I think you did not follow the instruction to boot with stock u-boot here in the Wiki thread

Quote

Kirkwood plugs

Basic steps to install Debian and new u-boot on Kirkwood boxes
Boot Kirkwood rootfs with stock u-boot

Basically you need to boot with both uImage and uInitrd from the rootfs. And load each to the correct address.

So please try that with kernel 6.11.6 and post the entire serial console here (from the u-boot banner until the Debian login prompt). Don't post excerpts (there are other important info that I need to see).

Even if it is successful, still post the whole log.

[ 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 strings: Mfr=0, Product=1, SerialNumber=2
[ 3354.891343] usb 1-1.4: Product: USB Storage
[ 3354.896269] usb 1-1.4: SerialNumber: 000000009225
[ 3354.919405] usb 1-1.4: rejected 1 configuration due to insufficient available bus power
[ 3354.928212] usb 1-1.4: no configuration chosen from 1 choice

Yes there is some conflict, the regulator is not running. So I need to look at the log and see the error in context, and goes from there.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)