Show all posts by user
Discussions that don't fit anywhere else
Re: HowTo: OpenWrt on Kirkwood boxes - 2 years ago
bowent@encorecsl.com Wrote: ------------------------------------------------------- > Greetings, installing rescue system on Pink > Pogoplug E02 and am getting errors right out of > the gate. > Ran command: > fw_printenv mtdparts > > > Got this error: > ## Error: "mtdparts" not defined > > Any help appreciated. mtdparts is defined in U-Boby rayknight - Rescue System
Re: Help! Akitio mycloudmini using stock kernel but missing system setting files - 2 years ago
Popo Wrote: > but, now ! after fix dtb, I can completely power > off machine! > It's good situation... Can you please post the your modified dts file? Thanks, Rayby rayknight - Rescue System
Re: Help! Akitio mycloudmini using stock kernel but missing system setting files - 2 years ago
QuotePopo BTW, my machine is not DC01. My machine is the same OEM product as OpenWRT and Ray's machine. It's just that I don't have the RTC on the motherboard. Are you sure you have no RTC on the motherboard? I posted a link to an image of my board which does have an RTC IC, just not the one referenced in the DTS. On the bottom of the board there is a small battery marked BT1by rayknight - Rescue System
Re: Bricked NSA320S during 2017.07 flash - 2 years ago
AleXSR700 Wrote: > EDIT: > For anybody hooking up UART. You need RX, TX > aaaaand GND. No VCC but you do need GND. Probably > obvious for most but less so for inexperienced > users like me who usually use VCC & GND for their > flashing needs. This can vary depending on what you are using to connect to the UART port. For instance I make extensive use of the μArtby rayknight - uBoot
Re: Help! Akitio mycloudmini using stock kernel but missing system setting files - 2 years ago
High res photos of board for one of my devices are available at WikiDevi. Markings indicate V1.01by rayknight - Rescue System
Re: Help! Akitio mycloudmini using stock kernel but missing system setting files - 2 years ago
Perhaps the original DTB has always been wrong? I have 2 of these devices that I gave up on as I was having issues getting them to boot and now that I go back an look at them they both have STMicroelectronics M41T80 for RTC not the Dallas 1307.by rayknight - Rescue System
Re: Help! Akitio mycloudmini using stock kernel but missing system setting files - 2 years ago
Popo Wrote: ------------------------------------------------------- > > U-Boot SPL 2013.10-g3a0f380-dirty (Jul 26 2014 - > 14:31:34) > Boot device: SATA > Attempting to set PLLA to 850 MHz ... > plla_ctrl0 : 0000020a > plla_ctrl1 : 00330000 > plla_ctrl2 : 0065008b > plla_ctrl3 : 000000f1 > This could be the source of some of your problems.by rayknight - Rescue System
Re: resurrecting iomega storcenter ix2 u-boot and debian - 2 years ago
This is not a kirkwood device, but an earlier Marvell SOC known by the code name Orion. There are a few Orion based devices currently supported by mainline Linux kernel mostly Buffalo and Lacie NAS boxes. I believe the Orion devices like the very early kirkwood devices do not support kwboot. I would advise looking at trying the generic orion5x-rd88f5182-nas.dts as a starting point.by rayknight - uBoot
Re: Accidentaly erased nand flash and uboot wont load - 2 years ago
salahbr, OpenWrt does have nandutils package that I seem to recall contains the nanddump binary. So you might try to see if there is an OpenWrt device similar to you device. Rayby rayknight - uBoot
Re: 2023.04 U-Boot MVEBU -- Thecus N2350 and Synology DS116/RS816 - 2 years ago
Did you figure out pin configuration of serial port? If so could you provide. Also I'd appreciate if you could provide link to GPL code as it will likely be quicker than getting a response from Thecus. I don't know why these vendors don't just host the code on a GitHub repository! Rayby rayknight - uBoot
Re: 2023.04 U-Boot MVEBU -- Thecus N2350 and Synology DS116/RS816 - 2 years ago
Bodhi, I've made an entry for the Thecus N4350 with photos at WikiDevi. Is the board the same as used in the N2350? Do you have GPL source code for N2350? The source code available currently at Thecus website appears to be wrong (i.e. it appears to be for one of there x86 boards not the N2350/N4350). Rayby rayknight - uBoot
Re: NAS540 Kernel seafile.servator Debian - 2 years ago
Sounds like he has the ZyXEL NAS540 which is a four-bay dual core Freescale FS1024 based NAS.by rayknight - uBoot
Re: Sheevaplug board pics - 2 years ago
The more accurate entries for the DreamPlug are the ones I created with the actual version number (i.e. GlobalScale DreamPlug V10R1, GlobalScale DreamPlug V12 and GlobalScale DreamPlug V9R1) as I actually do a tear down of the devices when I make an entry on WikiDevi.by rayknight - uBoot
Re: Sheevaplug board pics - 2 years ago
I'll have to dig around for them, but I have two different AppNeta devices that are re-labeled GlobalScale Sheevaplugs. I created the WikiDevi pages AppNeta PathView microAppliance PS310 and AppNeta PathView microAppliance m20 by actually opening up the devices, so the listed ETH chip2: Marvell 88E1116R is the actual PHY chip on the board. If I come across one of the devices in the next feby rayknight - uBoot
Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325 - 2 years ago
The setenv and printenv commands are u-boot shell commands, not Linux shell commands. Therefore the shell you are using from Linux have no bearing. From Linux you would use the fw_printenv and fw_setenv commands after first setting the appropriate values in /etc/fw_env.config. Rayby rayknight - uBoot
Re: Help flashing to a Sheevaplug NAND - 2 years ago
You've installed the 23.05.0 fourth release candidate. The actual release is now available. You should download https://downloads.openwrt.org/releases/23.05.0/targets/kirkwood/generic/openwrt-23.05.0-kirkwood-generic-globalscale_sheevaplug-squashfs-sysupgrade.bin to the /tmp directory on the device and then run the sysupgrade command to upgrade to the latest release. See https://openwrt.oby rayknight - Debian
Re: DS411 Slim flash is corrupted and it's bricked. Please help install Debian. - 2 years ago
I use this device for most serial connections https://www.crowdsupply.com/signoid/muart. It isn't exactly cheap, and requires you to connect the power pin, but it also has some features that I find useful. Complete galvanic isolation Reverse polarity protection over-current protection voltage auto-sensing working voltage from 1.8-5.4V up to 3Mbaud transfer speedby rayknight - Debian
Re: Upgrading Debian Distribution - 2 years ago
Upgrading to Debian Bookworm with systemd can be a long process with this 128MB device! I personally would avoid systemd on systems with such low memory. Rayby rayknight - Debian
Re: 2023.04 U-Boot MVEBU -- Thecus N2350 and Synology DS116/RS816 - 2 years ago
I don't yet have the N4350, but it is on it's way to me and scheduled to arrive by October 31st. Rayby rayknight - uBoot
Re: 2023.04 U-Boot MVEBU -- Thecus N2350 and Synology DS116/RS816 - 2 years ago
Any chance this release will work with the Thecus N4350? It appears to be a 4 bay version of the N2350 with a 1.8GHz processor instead of the 1GHz in the 2350. Rayby rayknight - uBoot
Re: Debian on Chip PC LXD8941 - 2 years ago
I see the issue with all kernels from 5.13.8 thru 6.4.11. One difference between this device and the t5335z is CPU is clocked at 933 MHz vs 1 GHz for the t5335z. From U-Boot log: Board: RD-88AP510-Avengers SoC: MV88F510 Rev 7 CPU: ??? (0x0c08) (Rev 1) CPU @ 933Mhz, L2 @ 466Mhz DDR3 @ 466Mhz, TClock @ 166Mhz If my notes are correct I had a similar issue with the Globy rayknight - Debian
Re: Debian on Chip PC LXD8941 - 2 years ago
Trying to narrow down stack trace issues with this device I started with the Debian-5.13.8-mvebu-tld-1-rootfs-bodhi.tar.bz2 image. It appears that the stack trace issue was already present with that version: [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 5.13.8-mvebu-tld-1 (root@tldDebian) (gcc (Debian 8. 3.0-6) 8.3.0, GNU ld (GNU Binutils for Debian) 2.31.by rayknight - Debian
Re: Debian on Chip PC LXD8941 - 2 years ago
Sorry all the differences in the diff between my version and yours. I tried many different things to get the eMMC recognized properly, so lost track of the diff to the original. I've gone back and made the appropriate changes to the original. Adding the broken-cd tag was the fix for SD card. Attached dts file now recognizes the SD card removal and insertion. I did not remove the sata (aby rayknight - Debian
Re: Promise Apollo Cloud - Armada 385 - 2 years ago
I created the wikidevi page back in January so my memory is not clear, but I do believe CN4 was the serial port. Rayby rayknight - Debian
Re: Debian on Chip PC LXD8941 - 2 years ago
I'm sure its missing the eject signal, but can't seem to get a proper DTS configuration for it. Note the SD card is actually SDIO1, not SDIO0 as you originally had defined. When I add similar pinctrl and gpio entries for SDIO1 that you have had for SDIO0 the SD card is no longer recognized even when inserted on boot. I tried using both pmx_sdio0_gpio and pmx_sdio1_gpio. Maybe "by rayknight - Debian
Re: Debian on Chip PC LXD8941 - 2 years ago
Just wanted to note that this doesn't create an immediate problem for me as I am intending on booting from the microSD card so will not need to remove it after booting. I'm just interested in trying to correct the DTB for this device. I intend to continue working on the device to attempt to get the audio working as well. Rayby rayknight - Debian
Re: Debian on Chip PC LXD8941 - 2 years ago
Using a different SD card (already re-used the previous PNY card). I've also added some steps I believe might be helpful. Boot with microSD card in slot root@debian:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:0 1 14.9G 0 disk └─sda1 8:1 1 14.9G 0 part / mtdblock0 31:0 0 768K 0 disk mtdblock1 31:1 0by rayknight - Debian
Re: Debian on Chip PC LXD8941 - 2 years ago
After various attempts to enable the onboard eMMC the attached dts file enables access to the eMMC. There is still an issue with only having access to the SD Card if it is inserted on boot and ejection is still not recognized. @bodhi could use some help in how to resolve that issue! Results when building a DTB with the attached DTS as follows: Booting without card in microSD slot. rootby rayknight - Debian
Re: Debian on Chip PC LXD8941 - 2 years ago
Following up on my LXD8941 using linux-6.4.11-mvebu-tld-1-bodhi.tar.bz2 from this forum. Booting without card in microSD slot. root@debian:~# dmesg | grep mmc [ 7.926993] mmc0 bounce up to 128 segments into one, max segment size 65536 bytes [ 7.954373] mmc1 bounce up to 128 segments into one, max segment size 65536 bytes [ 7.975303] mmc0: SDHCI controller on f1090000.sdio-hby rayknight - Debian
Re: Debian on Chip PC LXD8941 - 2 years ago
Recently received an LXD8941 and it appears that the devicetree still needs work. The onboard eMMC is not recognized and the devicetree file has no support for the audio which should be very similar to the HP T5335z. Booting with other DTB files I discovered that the dove-d2plug.dtb enables me to access both the microSD card and the onboard eMMC. I'll try to work on getting an improved deby rayknight - Debian