Quantcast
Channel: Linux Device Hacking
Viewing all 3178 articles
Browse latest View live
↧

cannot ssh after systemd installation (1 reply)

February 24, 2021, 10:12 pm
$
0
0
I am currently using

Kernel linux-5.10.7-kirkwood-tld-1
Debian-5.2.9-kirkwood-tld-1-rootfs-bodhi.tar.bz2 (25 Aug 2019)

Every time I try to install systemd using

sudo apt-get install systemd,

after reboot, I would get connection refused when trying to ssh to it.

I had to reformat the stick and put the rootfs and kernel back but kept running into the same problem every time. Is there any suggestion where the cause of the problem might be?

Thanks.
↧
Search

DS210j - flash chip failure and image rebuilding (1 reply)

February 25, 2021, 2:05 pm
$
0
0
DS210j, board ADM22L1 v1.3,

Went dead suddenly, currently only blue led blinks. No sings of life from debug console.
Found that flash chip is damaged - stayed quite hot when touched and i wasn't able to read/erase/write it in external programmer due to overcurrent error.

Appeared that i need new chip (25P32) programmed with rebuilt image. Altough i've managed to extract rd and zimage from syno PAT update, i couldn't find bootloader in none of update files. Is it possible to download or compile stock bootloader image intended for this particular board/CPU? (88F6-BIA2)


Another problem was about finding memory layout. Googled for ds210j bootlogs, found something:

0x003c0000-0x00400000 : "RedBoot"
0x00000000-0x00200000 : "zImage"
0x00200000-0x00380000 : "rd.gz"
0x00380000-0x00390000 : "vendor"
0x00390000-0x003b0000 : "RedBoot Config"
0x003b0000-0x003c0000 : "FIS directory"

which is weird because of redboot placed not at 0x00 flash addr.


When looked at bootlogs of other similiar devices, like ds110j:

0x00000000-0x00080000 : "RedBoot"
0x00080000-0x00280000 : "zImage"
0x00280000-0x003c0000 : "rd.gz"
0x003c0000-0x003d0000 : "vendor"
0x003d0000-0x003f0000 : "RedBoot Config"
0x003f0000-0x00400000 : "FIS directory"

This layout seemed more reasonable to me.


Does anyone can confirm first memory layout, or give a hint how to extract such information?
↧
↧

Pogo E02 tries to boot from a non-rootfs drive. (9 replies)

February 26, 2021, 11:40 pm
$
0
0
Hi there,

I am using a 4GB USB stick to boot my pogoplug E02 with the latest kernel (5.10.7) which seems to be ok. But when I tried to attach a 320GB hard drive with a single partition with no rootfs label, it seems the system tried to boot from the hard drive and was never successful. How should I fix it?

[Note that the hard drive partition is ext4 and was hooked up to another debian on my dockstar as a data drive. I never had problem booting on it, but now I am using the E02 as a nextcloud server, I try to move it here.]

Here is the log when the hard drive was not attached: 

U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:13:18 -0700)
Pogo E02
gcc (Debian 6.3.0-18) 6.3.0 20170516
GNU ld (GNU Binutils for Debian) 2.28
Hit any key to stop autoboot:  0 
Initializing devices...
starting USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
       scanning usb for storage devices... 
Use USB retry period from the environment: 15 second(s)
1 Storage Device(s) found
Unknown command 'ide' - try 'help'
Unknown command 'mmc' - try 'help'
Loading envs from usb 0...
33 bytes read in 599 ms (0 Bytes/s)
... envs loaded
importing envs ...
running scan_disk ...
Scan device usb
device usb 0:1
1 bytes read in 539 ms (0 Bytes/s)
Found bootable drive on usb 0
5316528 bytes read in 851 ms (6 MiB/s)
9662424 bytes read in 1023 ms (9 MiB/s)
10106 bytes read in 3568 ms (2 KiB/s)
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-5.10.7-kirkwood-tld-1
   Created:      2021-02-21   9:31:25 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    5316464 Bytes = 5.1 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-5.10.7
   Created:      2021-02-26   3:00:20 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    9662360 Bytes = 9.2 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 01c00000
   Booting using the fdt blob at 0x1c00000


Starting kernel ...


And here is when the hard drive was attached and ran into a problem. 

U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:13:18 -0700)
Pogo E02
gcc (Debian 6.3.0-18) 6.3.0 20170516
GNU ld (GNU Binutils for Debian) 2.28
Hit any key to stop autoboot:  0 
Initializing devices...
starting USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 4 USB Device(s) found
       scanning usb for storage devices... 
Use USB retry period from the environment: 15 second(s)

Use USB retry period from the environment: 15 second(s)
2 Storage Device(s) found
Unknown command 'ide' - try 'help'
Unknown command 'mmc' - try 'help'
Loading envs from usb 0...
** File not found /boot/uEnv.txt **
Loading envs from usb 1...
33 bytes read in 599 ms (0 Bytes/s)
... envs loaded
importing envs ...
running scan_disk ...
Scan device usb
device usb 0:1
** File not found /boot/uImage **
device usb 1:1
1 bytes read in 538 ms (0 Bytes/s)
Found bootable drive on usb 1
** File not found /boot/uImage **
** File not found /boot/uInitrd **
** File not found /boot/dts/kirkwood-pogo_e02.dtb **
Wrong Image Format for bootm command
ERROR: can't get kernel image!
PogoE02>
↧

Newbie! Need Help with Pogoplug E02 (1 reply)

February 27, 2021, 1:57 pm
$
0
0
Hello! First post and new to embedded devices.

Found an old Pogoplug E02 while doing some spring cleaning. I am trying to follow Jeff's Tutorial and running into some issues since the newest version of Debian it lists in the tutorial is Wheezy.

I am able to SSH into the device. I got to the command:
./kirkwood.debian-wheezy.sh
and ran into an error about invalid mirror and updated the following line from:
DEB_MIRROR="http://cdn.debian.net/debian"
to 
DEB_MIRROR="http://archive.debian.org/debian/"
.

After updating the installer was going fine until I got this error:
^Mzlib1g_1%3a1.2.7.dfs   0% |                               |     0  --:--:-- ET
FATAL: kernel too old
I am guessing the best bet would be to install the newest stable version of Debian Stretch, but need help. I searched through the site and could not find anything to point me in the right direction following similar steps from Jeff's Tutorial.

Can anyone help point me in the right directions? Thanks!
↧

Oxnas vs Kirkwood (1 reply)

March 1, 2021, 1:48 pm
$
0
0
So I'm curious bodhi, with the latest kernel upgrade for Oxnas, it's now very close to Kirkwood. Given the very limited manufacturer support available for Oxnas, what functions / drivers / other low level stuff does it not offer that the Kirkwood kernel offers or is there no difference now?

I have to confess that my Oxnas devices have been a little neglected as I have been devoting most of my hacking time to Kirkwood. Maybe some additional capabilities might reignite my Oxnas crush.

As a side note, the clock is ticking on all these armv5 and armv6 devices that are not 64 bit capable. Noticed a loss of support of many software over the years as the community doesn't have the resources to devote to older architectures. Sad to think about.
↧
↧

Verifying Checksum ... Bad Data CRC (1 reply)

March 1, 2021, 3:10 pm
$
0
0
I have a Pogoplug Mobile that I've updated with the latest uboot. It boots debian off the SD card just fine, but I also set these environment variables so it would boot the original Cloud Engines OS if there's no SD card inserted:

Quote

bootcmd_exec=if run load_uimage; then if run load_initrd; then if run load_dtb; then bootm $load_uimage_addr $load_initrd_addr $load_dtb_addr; else bootm $load_uimage_addr $load_initrd_addr; fi; else if run load_dtb; then bootm $load_uimage_addr - $load_dtb_addr; else bootm $load_uimage_addr; fi; fi; else run bootcmd_pogo; fi
bootcmd_pogo=if ubi part root 2048 && ubifsmount ubi:rootfs && ubifsload 0x800000 uboot.mtd0.dockstar.original.kwb ; then go 0x800200; fi

I've done this on lots of others, and it works fine. But this one wouldn't boot, so I hooked up a console and saw this:

Quote

Write allocate disabled

USB 0: host mode
PEX 0: interface detected no Link.
Net: egiga0 [PRIME], egiga1
Hit any key to stop autoboot: 0

Loading from NAND 128MB 3,3V 8-bit, offset 0x200000
Image Name: Linux-2.6.31.8
Created: 2011-08-23 20:00:55 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2080956 Bytes = 2 MB
Load Address: 00008000
Entry Point: 00008000
## Booting image at 00800000 ...
Image Name: Linux-2.6.31.8
Created: 2011-08-23 20:00:55 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2080956 Bytes = 2 MB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... Bad Data CRC
CE>>

As I said, debian boots fine, so not really a big deal. Just trying to understand what would cause this. Maybe a bad eraseblock? I did check dmesg and there was 1 bad block at something like block 273. Could that have caused the /boot/uboot.mtd0.dockstar.original.kwb file to be corrupted?
↧

Badly borked uBoot (Netgear Stora MS2110) (1 reply)

March 2, 2021, 11:29 pm
$
0
0
Greetings. I'll be quite blunt...I got myself into a bit of a fustercluck with my Netgear Stora.

First off, I tried updating uBoot from stock to the latest 2017.07 release, with the intention of attempting to install OMV (or at least something newer than the ancient stock kernel so I can get stable SMB2 support). Unfortunately, since my initial plan was to install OMV, I didn't follow the instructions provided on this forum. Instead, I followed the instructions located at http://chrislamothe.blogspot.com/2014/08/openmediavault-06-kralizec-on-netgear.html (but replaced the tftp filename with the latest version). However, after flashing the new uBoot, I decided instead of going right into installing OMV, I'd first try to get (what was at the time I downloaded it) the latest Bodhi kernel (Debian-5.2.9-kirkwood-tld-1-rootfs).

This is when things went off the rails.

uBoot itself seems to have flashed fine, and I have serial access to it. However, it will not boot from the 5.2.9 kernel USB. It'll make it as far as "Uncompressing Linux... done, booting the kernel.", and then just hang there forever.

I also tried booting it from an older "stora-debian-rootfs_20140114" ext2 flash drive that I've successfully used in the past for recovery purposes (after accidentally nuking the stock /lib directory, oops...), but same thing, it hangs at "booting the kernel". Same when I change the environment variables to boot from the stock kernel in NAND, it hangs. Basically...I'm currently stuck in uBoot, with no way to go any further.

I imagine what's happened is that one or more environment variables got screwed up...and then I made things even worse in my attempts to fix them piecemeal by reading multiple different forum posts. So, I imagine flashing the default environment variables might fix it. However...how do I do this from within uBoot? Is that even possible? The forum post that tells how to flash them only tells how to do it from within a booted Linux, and not from within uBoot itself.

If it helps, here is the uBoot startup log, along with the output of printenv: 

U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:38:05 -0700)
Netgear Stora MS2110

SoC:   Kirkwood 88F6281_A0
DRAM:  128 MiB
WARNING: Caches not enabled
NAND:  256 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
PHY reset timed out
88E1116 Initialized on egiga0
Hit any key to stop autoboot:  3  2  0 
Netgear Stora> printenv
arcNumber=2743
baudrate=115200
boot_sata1=mw 0x800000 0 1; setenv bootargs console=ttyS0,115200 root=/dev/sda1 rootdelay=10 $mtdparts; ide reset; ext2load ide 0:1 0x800000 /uImage; ext2load ide 0:1 0x01100000 /uInitrd; bootm 0x00800000 0x01100000
bootargs=console=ttyS0,115200 root=/dev/sda1
bootcmd=setenv bootargs $(console) root=LABEL=rootfs rootdelay=8; run bootcmd_usb; bootm 0x200000 0x800000
bootcmd_exec=run load_uimage; if run load_initrd; then if run load_dtb; then bootm $load_uimage_addr $load_initrd_addr $load_dtb_addr; else bootm $load_uimage_addr $load_initrd_addr; fi; else if run load_dtb; then bootm $load_uimage_addr - $load_dtb_addr; else bootm$load_uimage_addr; fi; fi
bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi
bootcmd_usb=usb reset; ext2load usb 0 0x200000 /boot/uImage; ext2load usb 0 0x800000 /boot/uInitrd
bootdelay=3
bootdev=usb
console=console=ttyS0,115200
device=0:1
devices=usb ide
disks=0 1 2 3
dtb_file=/boot/dts/kirkwood-netgear_stora_ms2000
ethact=egiga0
ethaddr=52:3b:20:9c:11:51
fileaddr=800000
filesize=4bbd60
if_netconsole=ping $serverip
ipaddr=192.168.1.169
led_error=orange blinking
led_exit=green off
led_init=green blinking
load_dtb=echo loading DTB $dtb_file ...; load $bootdev $device $load_dtb_addr $dtb_file
load_dtb_addr=0x1c00000
load_initrd=echo loading uInitrd ...; load $bootdev $device $load_initrd_addr /boot/uInitrd
load_initrd_addr=0x1100000
load_uimage=echo loading uImage ...; load $bootdev $device $load_uimage_addr /boot/uImage
load_uimage_addr=0x800000
machid=ffffffff
mainlineLinux=yes
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1m(uboot),4m@1m(kernel),251m@5m(rootfs) rw
partition=nand0,2
preboot_nc=run if_netconsole start_netconsole
scan_disk=echo running scan_disk ...; scan_done=0; setenv scan_usb "usb start";  setenv scan_ide "ide reset";  setenv scan_mmc "mmc rescan"; for dev in $devices; do if test $scan_done -eq 0; then echo Scan device $dev; run scan_$dev; for disknum in $disks; do if test $scan_done -eq 0; then echo device $dev $disknum:1; if load $dev $disknum:1 $load_uimage_addr /boot/uImage 1; then scan_done=1; echo Found bootable drive on $dev $disknum; setenv device $disknum:1; setenv bootdev $dev; fi; fi; done; fi; done
serverip=192.168.1.69
set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts $custom_params
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=serial
stdin=serial
stdout=serial
uenv_addr=0x810000
uenv_import=echo importing envs ...; env import -t $uenv_addr $filesize
uenv_init_devices=setenv init_usb "usb start";  setenv init_ide "ide reset";  setenv init_mmc "mmc rescan"; for devtype in $devices; do run init_$devtype; done;
uenv_load=run uenv_init_devices; setenv uenv_loaded 0; for devtype in $devices;  do for disknum in 0; do run uenv_read_disk; done; done;
uenv_read=echo loading envs from $devtype $disknum ...; if load $devtype $disknum:1 $uenv_addr /boot/uEnv.txt; then setenv uenv_loaded 1; fi
uenv_read_disk=if test $devtype -eq mmc; then if $devtype part; then run uenv_read;  fi; else if $devtype part $disknum; then run uenv_read; fi;  fi
usb_boot=run usb_load_uimage; run usb_load_uinitrd; bootm 0x800000 0x1100000
usb_bootcmd=usb start; run usb_init; run usb_set_bootargs; run usb_boot
usb_load_uimage=ext2load usb 0:1 0x800000 /boot/uImage
usb_load_unitrd=ext2load usb 0:1 0x1100000 /boot/uInitrd
usb_ready_retry=15
usb_root=LABEL=rootfs
usb_rootdelay=10
usb_rootfstype=ext2
usb_set_bootargs=setenv bootargs $console root=$(usb_root) rootfstype=$(usb_rootfstype) rootdelay=$(usb_rootdelay)

Environment size: 3798/131068 bytes

Note: Along with the various assorted "desperate attempt to fix this" changes, many of which I can not recall off the top of my head, I also manually changed bootdelay to 3 simply because I didn't like waiting 10 seconds for it to try booting from USB. :p


And here is the boot log of it attempting to boot from the 5.2.9 kernel USB: 

Netgear Stora> boot
resetting USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
       scanning usb for storage devices... 
Use USB retry period from the environment: 15 second(s)
1 Storage Device(s) found
4963680 bytes read in 852 ms (5.6 MiB/s)
9713936 bytes read in 820 ms (11.3 MiB/s)
## Booting kernel from Legacy Image at 00200000 ...
   Image Name:   Linux-5.2.9-kirkwood-tld-1
   Created:      2019-08-25   2:22:31 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4963616 Bytes = 4.7 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 00800000 ...
   Image Name:   initramfs-5.2.9-kirkwood-tld-1
   Created:      2019-08-25   2:22:50 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    9713872 Bytes = 9.3 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
   Loading Ramdisk to 036bc000, end 03fff8d0 ... OK
Using machid 0xffffffff from environment

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

And then it hangs, forever and all eternity.

How can I fix this?

Thank you...
↧

Swapping to Network File (NFS and iSCSI) (no replies)

March 6, 2021, 4:54 pm
$
0
0
This is a tutorial about swapping to network shared file. For now, the outline, and then I'll fill in the details (very slowly, whenever I have time).

While I'm writing this, if anybody'd like to experiment with iSCSI target/initiator, feel free to do that. The Kirkwood and MVEBU kernel I release in this forum have this capability. I could use some helps to co-author the iSCSI part of the tutorial.

I. Swap over NFS

1. Create swap file in NFS shared folder
2. Set up loop device in NFS client rootfs
3. Commands needed in NFS client rootfs
4. NFS rootfs
5. RAM disk

II. Swap over iSCSI

1. Create iSCSI target
1.1 Windows iSCSI
1.2 Linux iSCSI
2. Create swap file in iSCSI target folder
3. Create iSCSI initiator in the client rootfs
3. RAM disk
↧
Search

Netgear Stora MS2110 smbd keeps crashing (6 replies)

March 8, 2021, 10:10 am
$
0
0
Greetings. I have an old Netgear Stora MS2110 that I've been (mostly experimentally) been trying to get SMB2 support reliably working on, but so far with no luck.

My first attempt involved installing samba36 on the stock firmware, but it had an issue where the memory usage kept increasing as the number of files copied across grew, gradually slowing down as swap got hammered progressively harder, until eventually OOM killer would stop the service. So, I gave up on that.

My next attempt involved flashing the newest uBoot, then installing Debian Stretch and OMV4 as detailed in this thread. Unfortunately the web server for OMV seems to be too much for the Stora to properly handle, and smbd often became the very first victim of OOM killer as the web server sucked up the system resources. I tried disabling the web server, but then I kept running into an issue where the tmpfs at /run would fill up and stop smbd from working. The previously-linked thread includes a fix for this problem, but it didn't seem to work for me. It seems systemd (which OMV requires) isn't suited for the tiny memory on the Stora. So, I moved on again.

My current attempt involves the Debian 5.2.9 rootfs with samba installed via apt. This time, the smbd service doesn't appear as if it is being terminated by OOM killer. Rather, it just...stops working. It seems to still be running, but no longer accepts any data from clients (Windows reports "a device attached to the system is not functioning"). I'm assuming, though, that this is still an OOM issue. Restarting the service gets it working again, but only temporarily. No tmpfs full issues this time, it's just...boom, stops working.

I know the fact that the Stora has only 128MB of memory is a major bottleneck for reliable operation beyond bone stock functionality. Like I said, even on the severely cut-down stock firmware with a smaller memory footprint, I couldn't get samba36 to work without hitting OOM issues. But, I'm wondering if anyone here has any ideas as to how I might be able to reliably get SMB2 support working on this thing long-term. It's been retired as my primary NAS, but if I can find a way to give it a second life as a backup NAS or such, I'd greatly appreciate it.

Thank you.
↧
↧

mergerfs on NSA325v2 (no replies)

March 13, 2021, 12:07 pm
$
0
0
Hi,

I'm using my Zyxel NSA325v2 for more than half a year now and I'm very happy with it apart from some noise issues. Now I'm trying to get mergerfs to work to pool both drives without needing a RAID. However, I keep getting a "Transport endpoint is not connected" error when trying to write to the merged folder/filesystem. I have seen on the forum that someone got it working but that was more than one year ago. Does anyone use mergerfs on this box and can share how he did it?

Thanks in advance!
↧

Bug you for cellphone advice? Some things changed (no replies)

March 18, 2021, 2:49 am
$
0
0
To me a phone is the last place to have personal information, and I have no root for my Android phone. It looks like Mint Mobile may have good news finally but I'll know more tomorrow.

A Windows 10 netbook with SIM would take care of big hindrances here. This is because Windows apps can be finniky about using the dev's download app.

But a plain Jane cryogenamod on Motorola or something, I only need it for calls and hotspot/tethering, but not rooted to someone else.

I sure thank ya! Price range anything to maybe 2-$30, but for 2 cents I'd go for a flip phone.
↧

Setting GPIOs in serial console (Kirkwood SoCs) (2 replies)

March 19, 2021, 1:50 pm
$
0
0
In u-boot console.

First, dump the memory content of these 2 memory banks: GPIO0 address 0xF1010100 and GPIO1 address 0xF1010140

There are 32 GPIOs in each bank. 
md.l 0xF1010100 1
md.l 0xF1010140 1

In the below example, we will set USB Power GPIO on the Zyxel NSA320: GPIO 21. Note that each box has a different GPIO assigned to it, event though they are all in the same Kirkwodd SoCs family

So we use the hex output of the first command (because GPIO 21 is in the 1st bank, GPIO0). We'll call it xxx. 
md.l 0xF1010100 1

And then modify xxx to turn on the bit 21 (right to left, 0 to 31).

You want to set that bit 21 to 1. Do this temporarily on a notepad, The result is yyy (in hex).

And then write the result yyy back to the memory address 0xF1010100 

mw.l 0xF1010100 yyy

======

Another example shows the layout of the bit pattern. The arrow below points to GPIO 29 being set. 

GPIO0:

xxx = 0000 0000 0100 0010 0000 0000 0000 0000
yyy = 0010 0000 0100 0010 0000 0000 0000 0000
        ^
↧

Setting GPIOs in serial console (Kirkwood SoCs) (2 replies)

March 19, 2021, 1:50 pm
$
0
0
In u-boot console.

First, dump the memory content of these 2 memory banks: GPIO0 address 0xF1010100 and GPIO1 address 0xF1010140

There are 32 GPIOs in each bank. 
md.l 0xF1010100 1
md.l 0xF1010140 1

In the below example, we will set USB Power GPIO on the Zyxel NSA320: GPIO 21. Note that each box has a different GPIO assigned to it, event though they are all in the same Kirkwodd SoCs family

So we use the hex output of the first command (because GPIO 21 is in the 1st bank, GPIO0). We'll call it xxx. 
md.l 0xF1010100 1

And then modify xxx to turn on the bit 21 (right to left, 0 to 31).

You want to set that bit 21 to 1. Do this temporarily on a notepad, The result is yyy (in hex).

And then write the result yyy back to the memory address 0xF1010100 

mw.l 0xF1010100 yyy

======

Another example shows the layout of the bit pattern. The arrow below points to GPIO 29 being set. 

GPIO0:

xxx = 0000 0000 0100 0010 0000 0000 0000 0000
yyy = 0010 0000 0100 0010 0000 0000 0000 0000
        ^
↧
↧

So Bizarre - Netgear Stora with non-kirkwood CPU? (5 replies)

March 20, 2021, 12:29 am
$
0
0
I will try to post the boot logs in a moment. Right now, I am getting environment overflow errors. That happened immediately after flashing Bodhi's Uboot. That, however, isn't the strange part. Boot Logs claim this Stora MS2110 has a Marvell Feroceon CPU @ 100 MHz!

Has anyone come across such a thing?

FWIW, when issuing a printenv from the serial console at boot, I get at least 6 screens full of the same non-ascii character. About 6 screens in, the ctl-c I pressed kicks-in...

My guess is the new uboot expects the env code at an earlier point the the old uboot, and the new is picking up "dead" code at the beginning, and by the time the real environment data comes up, the buffer is full?

Terminal output, from beginning of boot, almost to the end, is below: 
         __  __                      _ _
        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  __/ | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_ 
| | | |___|  _ \ / _ \ / _ \| __| 
| |_| |___| |_) | (_) | (_) | |_ 
 \___/    |____/ \___/ \___/ \__| 
 ** MARVELL BOARD: RD-88F6281A LE 

U-Boot 1.1.4 (Sep  4 2009 - 09:36:11) Marvell version: 3.4.14

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 006CEE60

Soc: 88F6281 A0 (DDR2)
CPU running @ 1000Mhz L2 running @ 333Mhz
SysClock = 333Mhz , TClock = 200Mhz 

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000   size  64MB 
DRAM CS[1] base 0x04000000   size  64MB 
DRAM Total size 128MB  16bit width
Flash:  0 kB
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:256 MB
CRC in Flash: ffffffff, Calculated CRC: 619d86db
+++++++++++++++++++++++++++Checksum Error!++++++++++++++++++++++++++++++
+++++++++++++++++++++++++++Checksum Error!++++++++++++++++++++++++++++++
+++++++++++++++++++++++++++Checksum Error!++++++++++++++++++++++++++++++
+++++++++++++++++++++++++++Checksum Error!++++++++++++++++++++++++++++++
+++++++++++++++++++++++++++Checksum Error!++++++++++++++++++++++++++++++
## Error: environment overflow, "stdin" deleted
## Error: environment overflow, "stdout" deleted
## Error: environment overflow, "stderr" deleted

CPU : Marvell Feroceon (Rev 1)
## Error: environment overflow, "console" deleted
## Error: environment overflow, "mainlineLinux" deleted
## Error: environment overflow, "CASset" deleted
## Error: environment overflow, "enaMonExt" deleted
## Error: environment overflow, "enaCpuStream" deleted
## Error: environment overflow, "enaWrAllo" deleted
## Error: environment overflow, "pexMode" deleted
## Error: environment overflow, "disL2Cache" deleted
## Error: environment overflow, "setL2CacheWT" deleted
## Error: environment overflow, "disL2Prefetch" deleted
## Error: environment overflow, "enaICPref" deleted
## Error: environment overflow, "enaDCPref" deleted
## Error: environment overflow, "sata_dma_mode" deleted
## Error: environment overflow, "MALLOC_len" deleted
## Error: environment overflow, "ethprime" deleted
## Error: environment overflow, "netbsd_en" deleted
## Error: environment overflow, "vxworks_en" deleted
## Error: environment overflow, "bootargs_root" deleted
## Error: environment overflow, "bootargs_end" deleted
## Error: environment overflow, "image_name" deleted
## Error: environment overflow, "bootcmd" deleted
## Error: environment overflow, "standalone" deleted
## Error: environment overflow, "bootdelay" deleted
## Error: environment overflow, "disaMvPnp" deleted
## Error: environment overflow, "disaMvPnp" deleted
## Error: environment overflow, "ethaddr" deleted
## Error: environment overflow, "ethmtu" deleted
## Error: environment overflow, "eth1addr" deleted
## Error: environment overflow, "eth1mtu" deleted
## Error: environment overflow, "mvPhoneConfig" deleted
## Error: environment overflow, "mvNetConfig" deleted
## Error: environment overflow, "usb0Mode" deleted
## Error: environment overflow, "yuk_ethaddr" deleted
## Error: environment overflow, "nandEcc" deleted
## Error: environment overflow, "hddPowerCtrl" deleted
## Error: environment overflow, "netretry" deleted
## Error: environment overflow, "rcvrip" deleted
## Error: environment overflow, "loadaddr" deleted
## Error: environment overflow, "autoload" deleted
## Error: environment overflow, "enaAutoRecovery" deleted

Streaming disabled 
Write allocate disabled

Module 0 is RGMII
Module 1 is TDM

USB 0: device mode
PEX 0: interface detected no Link.
Net:   ## Error: environment overflow, "ethact" deleted
egiga0, egiga1## Error: environment overflow, "ethact" deleted

USB:   scanning bus for devices... 1 USB Device(s) found
       scanning bus for storage devices... 0 Storage Device(s) found
Aquiring an IP address using DHCP...
## Error: environment overflow, "ethact" deleted
egiga0 no link
## Error: environment overflow, "ethact" deleted
egiga1 no link
## Error: environment overflow, "ethact" deleted
*** ERROR: `ethaddr' not set
## Error: environment overflow, "ethact" deleted
egiga1 no link
## Error: environment overflow, "ethact" deleted
egiga0 no link
## Error: environment overflow, "ethact" deleted
## Error: environment overflow, "ethact" deleted
egiga1 no link
## Error: environment overflow, "ethact" deleted
egiga0 no link
## Error: environment overflow, "ethact" deleted
*** ERROR: `eth1addr' not set
## Error: environment overflow, "ethact" deleted
egiga0 no link
## Error: environment overflow, "ethact" deleted
egiga1 no link
## Error: environment overflow, "ethact" deleted
## Error: environment overflow, "ethact" deleted
egiga0 no link
## Error: environment overflow, "ethact" deleted
egiga1 no link
## Error: environment overflow, "ethact" deleted
*** ERROR: `ethaddr' not set
## Error: environment overflow, "ethact" deleted
egiga1 no link
## Error: environment overflow, "ethact" deleted
egiga0 no link
## Error: environment overflow, "ethact" deleted
Failed to retreive an IP address assuming default (<NULL>)!
Starting the Recovery process to retreive the file...
## Error: environment overflow, "ethact" deleted
egiga1 no link
## Error: environment overflow, "ethact" deleted
egiga0 no link
## Error: environment overflow, "ethact" deleted
*** ERROR: `eth1addr' not set
## Error: environment overflow, "ethact" deleted
egiga0 no link
## Error: environment overflow, "ethact" deleted
egiga1 no link
## Error: environment overflow, "ethact" deleted
Failed
Power Button is pressed!
MPP Sel: 00000530, Data IN Enable: 00020058, Data In Polarity: 00000040, Data In: 00000011
Power Button is released!
MAC: 00:01:97:6E:97:B1, IP: 10.110.151.177
## Error: environment overflow, "ethaddr" deleted
## Error: environment overflow, "ipaddr" deleted
## Error: environment overflow, "serverip" deleted
## Error: environment overflow, "netmask" deleted
## Error: environment overflow, "image_name" deleted
## Error: environment overflow, "console" deleted
## Error: environment overflow, "bootargs_root" deleted
## Error: environment overflow, "rootpath" deleted
## Error: environment overflow, "ethact" deleted
egiga0 no link
## Error: environment overflow, "ethact" deleted
egiga1 no link
## Error: environment overflow, "ethact" deleted
↧

Lacie wireless space u-boot and jtag backup-restore with openocd (1 reply)

March 21, 2021, 2:13 pm
$
0
0
Hi,
I am new to this forum but have some history with certain devices and other forums.
I started this topic because I received a Lacie wireless space device and woild like to set it up with new u-boot and openwrt.
I would need some help with it.
First, I compiled a version of u-boot from 2013.07. The config for this device was not kept in the mainline u-boot distribution.I wander if it is possible to reinclude it. I would do this with a little help.
Also, i can access the device with serial and can enter the u-boot console on stock version. Need some guide on backup using u-boot.
Maybe redboot would be also possible to be installed?
Also, I have jtag access with openocd. I have a tumpa device which is supported in openocd. There are configbfiles for feroceon but the samsung 128 mb flash i don't know if it is supported. I don't know if any board config can be used or i need to make another.
So could someone help me in some steps to hack this device? What inwould like:
-ability to backup / restore flash with jtag. This woild be a first step
- u-boot, recent version, flash repartition
- maybe dual boot in failsafe if long-pressing the power button
- ability to setup autostart if care of power failure
- openwrt in flash only and sata hdd to be used only as storage.
I will post here some device data.

Kind regards
↧
Search

[Synology][DS411slim] Another brick in the wall ? (1 reply)

March 21, 2021, 2:45 pm
$
0
0
Hello,
I have a DS411slim with a blicking blue light.
The first symptoms were that the NAS would become unresponsive. At first it happened after a few weeks of normale activity. A reboot would then fix it after unpluging the Synology. It then happened more and more, till the DS411slim won't boot anymore, stuck in blicking blue light of death.
Gladly, by using a Raspberry Pi, I was able to regain access my data without loosing anything.

I went through usual tests : removed each disk, one at a time, removed all disks, tried a hard reset, and visually check the motherboard.
I haven't see any damaged component on the mother board, but those are so fin that it is not easy to say.
I've check the power supply, it seems to deliver 12v, even during boot. But my multimeter is not really accurate.

No clue...

Googling around, I found here many relevant information and decided to go a bit further.
I then get a rs232 module and consoled to the DS411slim, getting inspiration from https://forum.doozan.com/read.php?3,100059 for exemple.

My first attempt showed encouraging things :

| \/ | __ _ _ ____ _____| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| | | | (_| | | \ V / __/ | |
|_| |_|\__,_|_| \_/ \___|_|_|
_ _ ____ _
| | | | | __ ) ___ ___ | |_
| | | |___| _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
\___/ |____/ \___/ \___/ \__| ** LOADER **
** MARVELL BOARD: Synology Disk Station LE
U-Boot 1.1.4 (Aug 9 2010 - 19:58:12) Marvell version: 3.5.3
...
CPU : Marvell Feroceon (Rev 1)
So far so good...

It then went to :
Uncompressing Linux... done, booting the kernel.
And .. stayed stucked :-(

OK, fine, it looks a lot at things I have seen when Googling, so I found an appropriate .pat file, extracted the zlimage file and tftp it to the Synology.
Trying a bootm, the console goes a bit further, begin booting the kernel and... stalled.

I tried another time, and the startup procedure went a bit further and stalled again.
The third try stalled too, but at another point.
Surprising... :-/

I tried again the normal startup, with the same constatation : the boot sequence would start but stalled at some point, never the same.
After numerous tries, the console showed the login demand. Wow !

Unfortunatly, I have forgotten my login and password. So I decided to add 2 new disks and try a fresh install.
Rebooting went fine and the Synology Assistant found my NAS.
I gave it the information it needs to install and it started fine, but ... stalled... :-(

And again...
And again...

So basically, my DS411slim is stalling in the boot sequence or after.
  • When it is in the boot sequence, it leads to the famous blinking blue light.
  • When it stall after booting, the NAS just becomes unresponsive.

What do you think ?
Any hint ?

Regards
↧

Lightweight is the key...... (1 reply)

March 23, 2021, 5:13 am
↧
↧

Updated uboot from 2014- Cannot scan pogoplug v4 on network (2 replies)

March 23, 2021, 9:37 pm
$
0
0
Hi,
Having issues with updating from the 2013 roots to the latest version. I attempted to update uboot to the 2017 version, but I believe I messed something up. Can someone with a little better knowledge let me know if I need to crack it open?
I can boot the old rootfs from 2013 and the led goes green, but is not present on my network. I don't see a mac address, would this be an issue? 

root@Debplug-2:/tmp# fw_printenv
bootcmd_exec=run load_uimage; if run load_initrd; then if run load_dtb; then bootm $load_uimage_addr $load_initrd_addr $load_dtb_addr; else bootm $load_uimage_addr $load_initrd_addr; fi; else if run load_dtb; then bootm $load_uimage_addr - $load_dtb_addr; else bootm $load_uimage_addr; fi; fi
bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec
bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi
bootdelay=10
bootdev=usb
device=0:1
devices=usb ide mmc
disks=0 1 2 3
ethact=egiga0
if_netconsole=ping $serverip
led_error=orange blinking
led_exit=green off
led_init=green blinking
load_dtb_addr=0x1c00000
load_initrd_addr=0x1100000
load_uimage_addr=0x800000
load_dtb=echo loading DTB $dtb_file ...; load $bootdev $device $load_dtb_addr $dtb_file
load_initrd=echo loading uInitrd ...; load $bootdev $device $load_initrd_addr /boot/uInitrd
load_uimage=echo loading uImage ...; load $bootdev $device $load_uimage_addr /boot/uImage
mainlineLinux=yes
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
partition=nand0,2
scan_disk=echo running scan_disk ...; scan_done=0; setenv scan_usb "usb start";  setenv scan_ide "ide reset";  setenv scan_mmc "mmc rescan"; for dev in $devices; do if test $scan_done -eq 0; then echo Scan device $dev; run scan_$dev; for disknum in $disks; do if test $scan_done -eq 0; then echo device $dev $disknum:1; if load $dev $disknum:1 $load_uimage_addr /boot/uImage 1; then scan_done=1; echo Found bootable drive on $dev $disknum; setenv device $disknum:1; setenv bootdev $dev; fi; fi; done; fi; done
set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts $custom_params
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=serial
stdin=serial
stdout=serial
uenv_addr=0x810000
uenv_import=echo importing envs ...; env import -t $uenv_addr $filesize
uenv_init_devices=setenv init_usb "usb start";  setenv init_ide "ide reset";  setenv init_mmc "mmc rescan"; for devtype in $devices; do run init_$devtype; done;
uenv_load=run uenv_init_devices; setenv uenv_loaded 0; for devtype in $devices;  do for disknum in 0; do run uenv_read_disk; done; done;
uenv_read_disk=if test $devtype -eq mmc; then if $devtype part; then run uenv_read;  fi; else if $devtype part $disknum; then run uenv_read; fi;  fi
uenv_read=echo loading envs from $devtype $disknum ...; if load $devtype $disknum:1 $uenv_addr /boot/uEnv.txt; then setenv uenv_loaded 1; fi
usb_ready_retry=15
arcNumber=3960
machid=f78
dtb_file=/boot/dts/kirkwood-pogoplug_v4.dtb
serverip=192.168.1.252
ipaddr=192.168.1.129
preboot_nc=setenv nc_ready 0; for pingstat in 1 2 3 4 5; do; sleep 1; if run if_netconsole; then setenv nc_ready 1; fi; done; if test $nc_ready -eq 1; then run start_netconsole; fi
preboot=run preboot_nc

root@Debplug-2:/tmp# reboot
↧

Seems to be a bug in mke2fs on latest rootfs (9 replies)

March 24, 2021, 2:49 pm
$
0
0
So, 2x 1TB HDDs, both formatted by my Goflex Net. Both had errors trying to mount on my Ubuntu laptop. Tried the first 12 or so backup superblocks in the filesystem with e2fsck, but those all had identical issues. The problem seems to be that the filesystem size was 1 block bigger than the partition size.

Fortunately, I only had about 300 GB of data on the one drive, and nothing on the other. In addition, the mount and fsck commands are tolerant of the above issue on the Goflex Net, so it can mount drives formatted on both my Laptop and the GoFlex. The solution, then, was to reformat the already blank drive in Ubuntu, and then put it back into the GoFlex Net.

I will copy 'n' paste the the exact error in a moment, after I finish copying over my 300 GB. Might take a little while for that.
↧

Custom recovery image for axentra devices? (no replies)

March 25, 2021, 1:43 pm
$
0
0
Found the following online. Check page 12:
USB Flash recovery from Uboot

The info is for a "sheevaplug dev kit". However, I suspect it can be adapted to things like the GoFlex, Stora, and other such things.

This of course, assumes that the Dev Kit is similar enough to the finished product. IE, that the commercial version didn't change anything major in the recovery process - I suspect this is a very risky assumption to make. It would help to be able to get the original recovery file to examine.
↧
Viewing all 3178 articles
Browse latest View live
Search