Show all posts by user

Re: Shuttle KS10 - 1 year ago

Quote I can't find the poweroff gpio. I though if I flip all available gpio's as output, one would switch off the box. But it doesn't. Maybe gpio 55 has something to do with it. When I set that to 1, sometimes (as in 3 times reproducible, and then 3 times not) the box reboots.

by Mijzelf - Debian

Re: Shuttle KS10 - 1 year ago

The gpio in- and outputs are identified and added to dts. The leds show up in /sys/class/leds, and I can toggle them with echo. The 2 buttons give 'something' when I run 'cat /dev/input/event0' and press the power or reset button. I have identified the i2c device, it's a pcf8563 RTC. Added to dtb, and it works. ---------------- I can't find the poweroff gpio.

by Mijzelf - Debian

Re: Shuttle KS10 - 1 year ago

Something fishy is going on. When I add the string mtdparts to the command line, the box boots. But when I add a mtdparts=<something> I get a kernel panic. (full bootlog attached) Begin: Mounting root file system ... /init: .: [ 10.833926][ T1] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000200 [ 10.843657][ T1] CPU: 0 PID: 1 Comm: init Not tainted 5.10.

by Mijzelf - Debian

Re: Shuttle KS10 - 1 year ago

Got a preliminary dtb. Copied the dts from mirabox, edited the name, memory size and mtd partitions. Added the sata part of rn102 (which is marked eSATA interface, apparently the esata is on the SoC), and removed the 2nd ethernet interface. It boots from disk, and the nic works. root@debian:~# lspci 00:01.0 PCI bridge: Marvell Technology Group Ltd. Device 6707 (rev 01) 00:02.0 PCI bridge

by Mijzelf - Debian

Re: Shuttle KS10 - 1 year ago

Booted the bodhi Mirabox uImage with the rootfs on flash, and I can confirm the network port works then. Further there was some scaring log: Will now check all file systems. Checking all file systems. LABEL=rootfs2 is mounted Done checking file systems. Log is being saved in /var/log/fsck/checkfs if that location is writable. Cleaning up temporary files...Cleaning /tmp...done. /tm

by Mijzelf - Debian

Re: Shuttle KS10 - 1 year ago

Quote> That is clear, but why doesn't it boot my box? The > mirabox dts should be ok. If you had booted with the kernel uImage on USB rootfs (if USB is available in stock u-boot), or boot the kernel uImage with tftp, and mount USB rootfs, then it would work with the Mirabox DTS. But not SATA, it does not exist in the Mirabox. Here I was talking about the OpenWrt Mirabox uImage,

by Mijzelf - Debian

Re: Shuttle KS10 - 1 year ago

Bootlog of Mirabox uImage (using LABEL=rootfs caused a kernel panic on the rn104, maybe because there is no initramfs, so I specified the partition) Shuttle>> setenv bootargs console=ttyS0,115200 root=/dev/sda1 rootdelay=10 mtdparts=pxa3xx_nand-0:4M(u-boot),4M(linux),-(filesystem) earlyprintk=serial Shuttle>> ide reset Reset IDE: Marvell Serial ATA Adapter Integrated Sata

by Mijzelf - Debian

Re: Shuttle KS10 - 1 year ago

This u-boot supports booting from disk. I create 2 partitions, one 1GiB ext2 and one ext4. Created a mirabox uImage on the first partition, and put your mvebu Debian rootfs on the 2nd. The boot ended in a kernel panic. It took me some time to realize that a mirabox doesn't have sata. So I took the netgear rn102 uImage instead. That one boots, but there is something wrong with the network p

by Mijzelf - Debian

Re: Shuttle KS10 - 1 year ago

Quotebohdi Can you post a link to some OpenWrt Armada 38x targets? https://openwrt.org/docs/techref/targets/mvebu#devices_with_this_target The OpenWrt sources do not contain a dts file for the mirabox, so the file from Linux is used, which contains soc { ranges = <MBUS_ID(0xf0, 0x01) 0 0xd0000000 0x100000 I build an OpenWrt mirabox initramfs kernel from f

by Mijzelf - Debian

Re: Shuttle KS10 - 1 year ago

Quotebodhi So if the OpenWrt baseline MVEBU kernel enables CONFIG_DEBUG_UART_xxx then, It does, this is the default config for all mvebu targets: ~/openwrt $ grep 'EARLY_PRINTK\|DEBUG_UART' target/linux/mvebu/config-5.10 CONFIG_DEBUG_UART_8250=y CONFIG_DEBUG_UART_8250_SHIFT=2 CONFIG_DEBUG_UART_PHYS=0xd0012000 CONFIG_DEBUG_UART_VIRT=0xfec12000 CONFIG_EARLY_PRINTK=y and I c

by Mijzelf - Debian

Re: Shuttle KS10 - 1 year ago

bodhi Wrote: ------------------------------------------------------- > I would look at the DTS for these 2 boxes Well, that is a problem. There are none. AFAIK the stock firmware doesn't use fdt, and GPL sources are not available. The KD22 thread on the OpenWrt forum concluded in: 'the Mirabox uImage (+dts) works'. bodhi Wrote: ----------------------------------------

by Mijzelf - Debian

Debian on Omninas Shuttle KS10 - 1 year ago

@bohdi I'm trying to fill some gaps. When trying to boot an OpenWrt Mirabox uImage on my Shuttle Omninas KS10 (Armada 370), it stopped at 'Starting Kernel...'. The reason to try that image, is that it is confirmed to work on the Shuttle KD22, which seems to be a dual disk version of the KS10. I was pointed to this thread, and indeed I could boot the box using your 'old u-boot

by Mijzelf - Debian