Show all posts by user
Discussions that don't fit anywhere else
Re: Shuttle KS10 - 3 years ago
bodhi Wrote: ------------------------------------------------------- > Also you don't need to change the memory size in > the DTS. It will be detected by u-boot. I was looking further at that patch. It adds a 'ARM_ATAG_DTB_COMPAT_CMDLINE_MANGLE' to Kconfig / .config. And in arch/arm/boot/compressed/atags_to_fdt.c, there is a code block disabled by this config: #ifnby Mijzelf - Debian
Re: NSA325 - OpenWRT - rebuild RAID1 - 3 years ago
Why are you asking that here? The OpenWrt forum seems more appropriate. Anyway, in contrast to Debian OpenWrt is a very minimal OS targeting routers. So any functionality which is not found on a basic router, is not installed. I think you have to install kmod-md-raid0, kmod-md-raid1 and blockd. And then you should be able to assemble the array mdadm --assemble /dev/md0 /dev/sda2 /dev/sby Mijzelf - Debian
Re: Shuttle KS10 - 3 years ago
OK, this kwboot works: ./kwboot -b spidump -t /dev/ttyUSB0 kwboot version 2022.01-00673-g70fe7827f2-dirty Patching image boot signature to UART Aligning image header to Xmodem block size Sending boot message. Please reboot the target.../ Waiting 2s and flushing tty Sending boot image header (59648 bytes)... 0 % [.....................................................................by Mijzelf - Debian
Re: Shuttle KS10 - 3 years ago
Quote Nice! it makes sense (with its own battery). Well, there is no visible battery on the board, but I suppose the RTC is that low powered that it can keep the time on a capacitor. Quote This u-boot is too old. Correction: This u-boot is old. It still gets its job done, I just have to wait a little longer. (And yes, a new u-boot with fdt support and everything would be nice, but at tby Mijzelf - Debian
Re: Shuttle KS10 - 3 years ago
bodhi Wrote: > > While the RN102 uses loadaddr 0x2000000, The > Mirabox uses loadaddr 0x6400000. Perhaps try > 0x6400000 to see it will make any difference. You mean this? Unfortunately it didn't make any difference Using egiga0 device TFTP from server 172.20.172.252; our IP address is 172.20.172.169 Filename 'openwrt-mvebu-cortexa9-globalscale_mirabox-initramby Mijzelf - Debian
Re: Shuttle KS10 - 3 years ago
Quote Shuttle>> bootm ## Booting kernel from Legacy Image at 02000000 ... Image Name: ARM OpenWrt Linux-5.10.90 Created: 2022-01-13 8:33:29 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 5087137 Bytes = 4.9 MB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Startingby Mijzelf - Debian
Re: Unbrick Synology DS918+ - 3 years ago
My 2 cents. I think the checksum is to prevent the flasher from flashing a damaged file. And you can ask binwalk what is inside the 16MB backup file.by Mijzelf - uBoot
NAS326 wake on RTC? - 3 years ago
Does anybody know if wake on RTC works on a NAS326?by Mijzelf - Debian
Re: Shuttle KS10 - 3 years ago
The dts job seems to be done. After all the 'reboot' gpio 55 was the power-off gpio. Somehow it causes a reboot when activated from shell, but it powers down the box when shutting down. Maybe the combination with the blue system led which is on when up, but somewhere switches off during shutdown. Now I can startup and shutdown the box using the same button. For some reason the 'by Mijzelf - Debian
Re: Shuttle KS10 - 3 years ago
QuoteIt has a Power button? Yes, it has a power button. Quotethe correct Power Off GPIO (if it is indeed using GPIO). What are the other options? QuoteUnfortunately the stock boot log does not show the SPI flash chip name. u-boot has some information Shuttle>> sf probe 0 1024 KiB EN25Q80 at 0:0 is now current deviceby Mijzelf - Debian
Re: Shuttle KS10 - 3 years ago
Quotebodhi Not really, we don't know where it crashed. It could have crashed before this. Or just a little bit after, and the kernel could not output the partial log before it crashed. The bottom line is to debug this OpenWrt kernel, you probably need to recompile it with DEBUG UART and earlyprintk configs. Once it works, then go back to the standard OpenWrt kernel. It took some time toby Mijzelf - Debian
Re: Shuttle KS10 - 3 years 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 - 3 years 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 - 3 years 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 - 3 years 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 bridgeby Mijzelf - Debian
Re: Shuttle KS10 - 3 years 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. /tmby Mijzelf - Debian
Re: Shuttle KS10 - 3 years 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 - 3 years 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 Sataby Mijzelf - Debian
Re: Shuttle KS10 - 3 years 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 pby Mijzelf - Debian
Re: Shuttle KS10 - 3 years 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 fby Mijzelf - Debian
Re: Shuttle KS10 - 3 years 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 cby Mijzelf - Debian
Re: Shuttle KS10 - 3 years 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 - 3 years 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-bootby Mijzelf - Debian