Robin Wrote: > Those are 256MB DDR3 1600Mhz capable chips, but as > the attached stock bootlog shows, those are run at > 1066Mhz in the DS214 even though the MV78230 SoC > is 1600Mhz capable. > The MV78230 SoC has 4 speed ratings (1066 Mhz, 1200 Mhz, 1333 Mhz, and 1600 Mhz). The rating used in the DS214 is 1066 Mhz, while that used in the DS214+, DS414 and RS814 is 1333 Mhzby rayknight - uBoot
Do you know how to build Linux kernel from source? Are you familiar with Device Tree Compiler? What I was suggesting was to either obtain the actual device tree source (.dts) file or as a last resort using the Device Tree Compiler tool to de-compile the DTB file to create a DTS file. Once you have a DTS it will likely need updating as what you have is for kernel 3.10.53 and you'll need toby rayknight - Debian
bodhi Wrote: ------------------------------------------------------- > For boxes with Armada 385 SoC, hwmon0 is usually > reserved for the HDD. Usually we use hddtemp to > get the temperature so we ignore this, but beware > that in the latest Debian release, hddtemp is no > longer available. So smartctl should be used to > get the temperature of the disk drives. > &by rayknight - Debian
Based on the following from your boot log: Jan 1 00:00:30 sigmatek-arm user.info kernel: Machine: Freescale i.MX6 Quad/DualLite (Device Tree), model: Sigmatek TT1933-S Board The device you have is likely this one SigmTek TT1933-S. I would suggest searching their website for newer firmware or contacting them to see if they have an updated SDK for the device. Failing that you could extracby rayknight - Debian
A quick look at the various boot logs shows all images where the kernel is less than 6 MB boot successfully. The boot where kernel > 6 MB do not boot. Does the load address need to be adjusted? Rayby rayknight - Debian
If you want to boot and use and OS from the NAND flash on this device you should be looking at OpenWrt. The NSA320 doesn't currently have support, but adding support should not be difficult. Rayby rayknight - Off-Topic
Not sure if you are aware, but the Network Space 2 like most LaCie NAS devices has issues as documented at Install from a LaCie stock U-Boot. It also implements its own form of U-Boot Net Console called CLUNC. If you follow the instructions at the first link you should be able to get U-Boot replaced and Debian installed. Its been a few years, but that is how I got Debian working on my Networkby rayknight - Debian
There is mainline U-Boot support for this device, so you should be able to easily build a modern U-Boot for it. See https://github.com/u-boot/u-boot/blob/master/configs/netspace_v2_defconfig in the U-Boot source for the default config file for building U-Boot for the device. Rayby rayknight - Debian
For someone who hasn't read the entire thread, what exactly is the difference in test setup (i.e. not the result difference, but configuration difference) between test 1 and test 2? Rayby rayknight - uBoot
Please re-create your boot device and post a log of the creation process as for some reason U-Boot is not finding a readable partition. Are you creating on a Linux distribution? If so when completed please run the command: fdisk -l /dev/sd? Replacing the ? with the device indicator (i.e. either a, b, c ...) depending on how the USB drive was identified by Linux. Also helpful would be tby rayknight - uBoot
It has been a while since I made the WikiDevi entry for this device. However, if I recall correctly the 1MB Serial Flash contains the configuration for the USB4640 IC which is a USB 2.0 Flash Media Controller with Hi-Speed USB Hub. If you look at the DTS for this device you see the following: &hsic0 { status = "okay"; usb1@1 { compatible = "usb424,2640"by rayknight - Debian
gov Wrote: ------------------------------------------------------- > hello Bodhi ser.. > > I have flashed new boot image and I don't know how > to go forward after this step. > SNIP > Pogoplug:/tmp$ ./fw_printenv ethaddr > > >by rayknight - Rescue System
pczerepaniak Wrote: ------------------------------------------------------- > Hi, i try to get wake on lan working on RN102 with > debian. > > I am setting on wake on lan with: > > ethtool -s eht0/end1 wol g > Likely not the issue, but you do have a typo in the above line. It should be: ethtool -s eth0 wol gby rayknight - Debian
See the Backup/Restore rootfs using tar commandby rayknight - Rescue System
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
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
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
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
High res photos of board for one of my devices are available at WikiDevi. Markings indicate V1.01by rayknight - Rescue System
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
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
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
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
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
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
Sounds like he has the ZyXEL NAS540 which is a four-bay dual core Freescale FS1024 based NAS.by rayknight - uBoot
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
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
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
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