Clone u-boot and environment settings (3 replies)

August 18, 2019, 4:32 pm

≫ Next: Pogo V4 Flashed with wrong uboot (1 reply)

≪ Previous: Pogoplug v4 not starting (1 reply)

I have several Pogoplug E02 devices. I recently updated u-boot on one of them to the 2017-07 U-Boot using the instructions posted by Bodhi. I managed to bork up some of the environment settings, so I had to crack open the Pogo and use a serial console to get it working again. I want to upgrade my other devices, but I don't want to have to set the environment settings for each one.

I have a nanddump of mtd0 from the 1st device that I've successfully upgraded. If I restore that nanddump to another unit, will it also update the environment settings? If not, is there a straightforward way to copy the environment settings from one Pogo to another without having to do it manually?

↧

Pogo V4 Flashed with wrong uboot (1 reply)

August 20, 2019, 1:17 am

≫ Next: POGO-V4-A3-01 + 2017.07 U-Boot Kirkwood + Debian 4.12.1 rootfs + Kernel 5.2.9 (1 reply)

≪ Previous: Clone u-boot and environment settings (3 replies)

Is there any easy way to undo this ? I had an NSA320 that I flashed and my brain was stuck on NSA320, so they are flashed with that uboot now. Thanks for any assistance, or laughs you can send my way.

It was late when I wrote this, now it's later, I mean to say that I bricked 2 Pogo V4's using the NSA320 uboot.

↧

POGO-V4-A3-01 + 2017.07 U-Boot Kirkwood + Debian 4.12.1 rootfs + Kernel 5.2.9 (1 reply)

August 20, 2019, 8:55 pm

≫ Next: NSA320 Broken uboot (15 replies)

≪ Previous: Pogo V4 Flashed with wrong uboot (1 reply)

I've been trying for some days to set up POGO-V4-A3-01 + 2017.07 U-Boot Kirkwood + Debian 4.12.1 rootfs + Kernel 5.2.9 without success.

The steps I followed:

Executing automatic shell script which installs uboot.2014.07-tld-1.pogo_v4.bodhi and uboot.2014.07-tld-1.environment.img.
Extracting the corresponding rootfs to a 1GB Sandisk SD-card formated as ext3 with 128MB linux-swap partition at the end. The formating was done with the linux tool gparted.
Test result: Success
Tried to upgrade with linux-5.2.9-kirkwood-tld-1-bodhi.tar.bz2 (18 Aug 2019) without success.
Issue post #2 suggested that it was necessary to update to uboot.2017.07-tld-1.pogo_v4.bodhi.
Flashed 2017.07 U-Boot Kirkwood on POGO-V4-A3-01. Result: success.
Extracted Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2 (24 Jul 2017) onto the same 1GB Sandisk SD-card and also onto an old Data Traveller 2GB USB2.0-stick with only one ext3 partition.
Extracted the environment variables as instructed from the archive uboot.2016.05-tld-1.environment.img (the default envs image to be flashed) and flashed them successfully.
Rebooted with test result: Failed.
Booting Debian 4.12.1 rootfs was not possible.
The last step to update the kernel to linux-5.2.9-kirkwood-tld-1-bodhi.tar.bz2 (18 Aug 2019) was not possible to perform.

Booting Debian 4.12.1 rootfs produces the following regardless of if there is only one SD-card, one USB-stick (top socket) or both SD-card and USB-stick:

U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:34:01 -0700)
Pogoplug V4
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... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found

Reset IDE: ide_preinit failed

MMC rescan: current device # 0 initialized OK
Loading envs from usb 0...
** Bad device usb 0 **
Loading envs from usb 1...
** Bad device usb 1 **
Loading envs from usb 2...
** Bad device usb 2 **
Loading envs from usb 3...
** Bad device usb 3 **
Loading envs from ide 0...
** Bad device ide 0 **
Loading envs from ide 1...
** Bad device ide 1 **
Loading envs from ide 2...
** Bad device ide 2 **
Loading envs from ide 3...
** Bad device ide 3 **
Loading envs from mmc 0...
** No partition table - mmc 0 **
Loading envs from mmc 1...
MMC Device 1 not found
MMC Device 1 not found
** Bad device mmc 1 **
Loading envs from mmc 2...
MMC Device 2 not found
MMC Device 2 not found
** Bad device mmc 2 **
Loading envs from mmc 3...
MMC Device 3 not found
MMC Device 3 not found
** Bad device mmc 3 **
running scan_disk ...
Scan device usb
device usb 0:1
** Bad device usb 0 **
device usb 1:1
** Bad device usb 1 **
device usb 2:1
** Bad device usb 2 **
device usb 3:1
** Bad device usb 3 **
Scan device ide

Reset IDE: ide_preinit failed
device ide 0:1
** Bad device ide 0 **
device ide 1:1
** Bad device ide 1 **
device ide 2:1
** Bad device ide 2 **
device ide 3:1
** Bad device ide 3 **
Scan device mmc

MMC rescan: current device # 0 initialized OK
device mmc 0:1
** No partition table - mmc 0 **
device mmc 1:1
MMC Device 1 not found
MMC Device 1 not found
** Bad device mmc 1 **
device mmc 2:1
MMC Device 2 not found
MMC Device 2 not found
** Bad device mmc 2 **
device mmc 3:1
MMC Device 3 not found
MMC Device 3 not found
** Bad device mmc 3 **
loading uImage ...
** Bad device usb 0 **
loading uInitrd ...
** Bad device usb 0 **
loading DTB /boot/dts/kirkwood-pogoplug_v4.dtb ...
** Bad device usb 0 **
Wrong Image Format for bootm command
ERROR: can't get kernel image!

I found another (older) thread suggesting to add these environment variables (which didn't change anything):

Pogov4> setenv usb_rootfstype 'ext3'
Pogov4> setenv mmc_bootcmd 'mmc rescan; run mmc_set_bootargs; run mmc_boot'
Pogov4> setenv mmc_boot 'mw 0x800000 0 1; ext2load mmc 0:1 0x00800000 /boot/uImage; if ext2load mmc 0:1 0x01100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi'
Pogov4> setenv mmc_root '/dev/mmcblk0p1'
Pogov4> setenv mmc_set_bootargs 'setenv bootargs console=$console root=$mmc_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params'
Pogov4> saveenv

I am suspecting that possible causes for this could be:

that there is something wrong with the environment variables in uboot.2016.05-tld-1.environment.img (the default envs image to be flashed), or
uboot 2017.07 cannot find the partition table on neither device
the ext3 partition that worked with uboot.2014.07-tld-1.pogo_v4.bodhi no longer works.
I have missed to do some essential steps that could have been forgotten to be mentioned in the installation instruction, as you guys probably already are familiar with the procedure of setting up POGO-V4-A3-01, but newcomers are not aware of.

The funny thing is that an uboot 2014.07 works, but a uboot 2017.07 doesn't, even though all steps have been carefully done:

Download uboot.2017.07-tld-1.pogo_v4.bodhi.tar

Download uboot tools script:

  #!/bin/bash
 # (the pogoplug ships with busybox, so we have to use ash instead of bash.) 
 # see https://github.com/pepaslabs/pogoplug_mobile_uboot_installer 
 # file name: download_uboot_tools.sh 
 # parse command line args: 
 
 assume_yes=0 
 if [ "${1:-}" == "-y" ] 
 then 
 assume_yes=1 
 fi 
 
 ### functions 
 
 echo_step() 
 { 
 echo 
 echo "* $@" 
 } 
 
 echo2() 
 { 
 echo "$@" >&2 
 } 
 
 prompt_to_proceed() 
 { 
 local message="$1" 
 
 echo -n "${message} [Y/n]: " 
 
 if [ "${assume_yes}" -eq 1 ] 
 then 
 echo "(Assuming yes...)" 
 return 0 
 fi 
 
 read yn 
 case $yn in 
 y|Y|yes|Yes|YES|'') echo "Proceeding..." ;; 
 *) echo2 "Exiting..." ; exit 1 ;; 
 esac 
 # thanks to http://stackoverflow.com/a/226724 
 } 
 
 # entering "strict" mode 
 set -e 
 set -u 
 set -o pipefail 
 
 # verbose 
 #set -x 
 
 ### cache / downloads section 
 
 echo_run() 
 { 
 echo "+ $@" 
 eval "$@" 
 } 
 
 md5_step() 
 { 
 local file="$1" 
 local sum="$2" 
 
 echo_step "Verifying ${file}" 
 echo "${sum} ${file}" | md5sum -c - 
 } 
 
 wget_step() 
 { 
 local file="$1" 
 local baseurl="$2" 
 local sum="$3" 
 
 if [ ! -e ${file} ] 
 then 
 echo_step "Downloading ${file}" 
 echo_run wget "${baseurl}/${file}" 
 fi 
 
 if pwd | grep -q '/bin' 
 then 
 chmod +x "${file}" 
 fi 
 
 md5_step "${file}" "${sum}" 
 } 
 
 mkdir -p /tmp/bin /tmp/dev /tmp/cache /tmp/mnt 
 export PATH=/tmp/bin:${PATH} 
 
 # download flash utils 
 cd /tmp/bin 
 #baseurl="http://download.qnology.com/pogoplug/v4&quot; 
 # Note: download.qnology.com seems to be down. Falling back to mirrored files: 
 baseurl="http://ssl.pepas.com/pogo/mirrored/download.qnology.com/pogoplug/v4&quot; 
 wget_step nanddump ${baseurl} 770bbbbe4292747aa8f2163bb1e677bb 
 wget_step nandwrite ${baseurl} 47974246185ee52deae7cc6cfea5e8fc 
 wget_step flash_erase ${baseurl} 8b5f9961376281e30a1bd519353484b0 
 wget_step fw_printenv ${baseurl} 7d28314b0d2737094e57632a6fe43bbe 
 wget_step fw_setenv ${baseurl} 7d28314b0d2737094e57632a6fe43bbe 
 
 echo_step "Downloaded all files. Exiting."

Pogo-V4-A3-01$ chmod +x /tmp/download_uboot_tools.sh
Pogo-V4-A3-01$ ./tmp/download_uboot_tools.sh
Pogo-V4-A3-01$ export PATH=/tmp/bin:${PATH}
desktop$ echo e2c2b4927dcd8189f0c97dd81b72ad7e uboot.2017.07-tld-1.pogo_v4.bodhi.tar > uboot.2017.07-tld-1.pogo_v4.bodhi.tar.md5
desktop$ echo 18f856d2106aabe6029331358fb06f053ea9257ad896e2d382f4f096f93c46e9 uboot.2017.07-tld-1.pogo_v4.bodhi.tar > uboot.2017.07-tld-1.pogo_v4.bodhi.tar.sha256
desktop$ md5sum -c uboot.2017.07-tld-1.pogo_v4.bodhi.tar.md5
uboot.2017.07-tld-1.pogo_v4.bodhi.tar: OK
desktop$ sha256sum -c uboot.2017.07-tld-1.pogo_v4.bodhi.tar.sha256
uboot.2017.07-tld-1.pogo_v4.bodhi.tar: OK
desktop$ scp uboot.2017.07-tld-1.pogo_v4.bodhi.* root@<pogo_ip_address>:/tmp
Pogo-V4-A3-01$ md5sum -c uboot.2017.07-tld-1.pogo_v4.bodhi.tar.md5
uboot.2017.07-tld-1.pogo_v4.bodhi.tar: OK
Pogo-V4-A3-01$ sha256sum -c uboot.2017.07-tld-1.pogo_v4.bodhi.tar.sha256
uboot.2017.07-tld-1.pogo_v4.bodhi.tar: OK
Pogo-V4-A3-01$ cat /etc/fw_env.config
# MTD device name Device offset Env. size Flash sector size Number of sectors
/dev/mtd0 0xc0000 0x20000 0x20000
Pogo-V4-A3-01$ cat /proc/mtd
dev: size erasesize name
mtd0: 00200000 00020000 "u-boot"
mtd1: 00300000 00020000 "uImage"
mtd2: 00300000 00020000 "uImage2"
mtd3: 00800000 00020000 "failsafe"
mtd4: 07000000 00020000 "root"
Pogo-V4-A3-01$ fw_printenv ethaddr
ethaddr=00:aa:bb:cc:dd:ee
Pogo-V4-A3-01$ nanddump --noecc --omitoob -l 0x80000 -f mtd0 /dev/mtd0
Pogo-V4-A3-01$ fw_printenv > current_envs.txt
desktop$ scp root@<pogo_ip_address>:/tmp/mtd0 .
desktop$ scp root@<pogo_ip_address>:/tmp/current_envs.txt .
Pogo-V4-A3-01$ dmesg | grep -i 'bad'
[ 2.084074] Scanning device for bad blocks
[ 2.105538] Bad eraseblock 210 at 0x000001a40000
(Comment: It's ok since it is outside block 1-8.)
Pogo-V4-A3-01$ cd /tmp
Pogo-V4-A3-01$ tar -xf uboot.2017.07-tld-1.pogo_v4.bodhi.tar
Pogo-V4-A3-01$ flash_erase /dev/mtd0 0 4
Erase Total 4 Units
Performing Flash Erase of length 131072 at offset 0x60000 done
Pogo-V4-A3-01$ nandwrite /dev/mtd0 uboot.2017.07-tld-1.pogo_v4.mtd0.kwb
Writing data to block 0 at offset 0x0
Writing data to block 1 at offset 0x20000
Writing data to block 2 at offset 0x40000
Writing data to block 3 at offset 0x60000
Download the default u-boot envs:
uboot.2016.05-tld-1.environment.bodhi.tar
desktop$ echo 3823eef10011b864859d31a76470e0e3 uboot.2016.05-tld-1.environment.bodhi.tar > uboot.2016.05-tld-1.environment.bodhi.tar.md5
desktop$ echo c8db95a4225e8d78bdaaaa372bd5a87e4b98f3448dd9c62fc96c72b2df1a997c uboot.2016.05-tld-1.environment.bodhi.tar > uboot.2016.05-tld-1.environment.bodhi.tar.sha256
desktop$ md5sum -c uboot.2016.05-tld-1.environment.bodhi.tar.md5
uboot.2016.05-tld-1.environment.bodhi.tar: OK
desktop$ sha256sum -c uboot.2016.05-tld-1.environment.bodhi.tar.sha256
uboot.2016.05-tld-1.environment.bodhi.tar: OK
desktop$ scp uboot.2016.05-tld-1.environment.bodhi.tar* root@<pogo_ip_address>:/tmp
Pogo-V4-A3-01$ md5sum -c uboot.2016.05-tld-1.environment.bodhi.tar.md5
uboot.2016.05-tld-1.environment.bodhi.tar: OK
Pogo-V4-A3-01$ sha256sum -c uboot.2016.05-tld-1.environment.bodhi.tar.sha256
uboot.2016.05-tld-1.environment.bodhi.tar: OK
Pogo-V4-A3-01$ cd /tmp
Pogo-V4-A3-01$ tar -xf uboot.2016.05-tld-1.environment.bodhi.tar
Pogo-V4-A3-01$ fw_printenv > current_envs.txt
Pogo-V4-A3-01$ flash_erase /dev/mtd0 0xc0000 1
Erase Total 1 Units
Performing Flash Erase of length 131072 at offset 0xc0000 done
Pogo-V4-A3-01$ nandwrite -s 786432 /dev/mtd0 uboot.2016.05-tld-1.environment.img
Writing data to block 6 at offset 0xc0000
Pogo-V4-A3-01$ fw_setenv arcNumber 3960
Pogo-V4-A3-01$ fw_setenv machid f78
Pogo-V4-A3-01$ fw_setenv mtdparts 'mtdparts=orion_nand:2M(u-boot),3M(uImage),3M(uImage2),8M(failsafe),112M(root)'
Pogo-V4-A3-01$ fw_setenv ethaddr '00:aa:bb:cc:dd:ee' (Comment: Make sure you use your own address printed under the box!)

uEnv.txt envs correction:
Pogo-V4-A3-01$ fw_setenv uenv_init_devices 'echo Initializing 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'
Pogo-V4-A3-01$ fw_setenv uenv_read 'echo Loading envs from $device_type $disk_number...; if load $device_type $disk_number:1 $uenv_addr /boot/uEnv.txt; then setenv uenv_loaded 1; echo ... envs loaded; fi'
Pogo-V4-A3-01$ fw_setenv uenv_load 'run uenv_init_devices; setenv uenv_loaded 0; for devtype in $devices; do for disknum in $disks; do if test $uenv_loaded -eq 0; then setenv device_type $devtype; setenv disk_number $disknum; run uenv_read; fi; done; done;'
Pogo-V4-A3-01$ fw_setenv uenv_read_disk

And for boxes that boot with SATA as rootfs. Please make this adjustment if your boot drive is SATA. This will help the "ide reset" to work properly. There seems to be a bug in u-boot that if you do "ide reset" too quickly in succession, the SATA drive might have problem spinning up).
Pogo-V4-A3-01$ fw_setenv bootcmd_uenv 'run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi; sleep 3'
Pogo-V4-A3-01$ fw_setenv dtb_file '/boot/dts/kirkwood-pogoplug_v4.dtb'

Adjust 192.168.0.xxx and 192.168.0.yyy below to the real numbers in your network configuration. 192.168.0.xxx is this plug IP address , and 192.168.0.yyy is the IP address of the netconsole server where it will monitor the output from the this plug (adjust them to the real values in your own local network settings).
Pogo-V4-A3-01$ fw_setenv 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'
Pogo-V4-A3-01$ fw_setenv preboot 'run preboot_nc'
Pogo-V4-A3-01$ fw_setenv ipaddr '192.168.0.xxx'
Pogo-V4-A3-01$ fw_setenv serverip '192.168.0.yyy'
Pogo-V4-A3-01$ reboot
Extract Debian 4.12.1 rootfs to the ext3-formated 1GB SD-card (made with gparted) and the ext3-formated USB2.0-stick (made with gparted) with
tar -xvf Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2

Pogov4> printenv

  
 arcNumber=3960 
 bootargs=console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=orion_nand:2M(u-boot),3M(uImage),3M(uImage2),8M(failsafe),112M(root) 
 bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec 
 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; sleep 3 
 bootdelay=10 
 bootdev=usb 
 device=0:1 
 device_type=mmc 
 devices=usb ide mmc 
 disk_number=3 
 disks=0 1 2 3 
 dtb_file=/boot/dts/kirkwood-pogoplug_v4.dtb 
 ethact=egiga0 
 ethaddr=00:aa:bb:cc:dd:ee[/b] (Comment: Make sure you use your own address printed under the box!) 
 if_netconsole=ping $serverip 
 init_ide=ide reset 
 init_mmc=mmc rescan 
 init_usb=usb start 
 ipaddr=192.168.10.xxx 
 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=f78 
 mainlineLinux=yes 
 mmc_boot=mw 0x800000 0 1; ext2load mmc 0:1 0x00800000 /boot/uImage; if ext2load mmc 0:1 0x01100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi 
 mmc_bootcmd=mmc rescan; run mmc_set_bootargs; run mmc_boot 
 mmc_root=/dev/mmcblk0p1 
 mmc_set_bootargs=setenv bootargs console=$console root=$mmc_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params 
 mtdids=nand0=orion_nand 
 mtdparts=mtdparts=orion_nand:2M(u-boot),3M(uImage),3M(uImage2),8M(failsafe),112M(root) 
 nc_ready=1 
 ncip=192.168.10.yyy 
 partition=nand0,2 
 preboot=run preboot_nc 
 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 
 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 
 scan_ide=ide reset 
 scan_mmc=mmc rescan 
 scan_usb=usb start 
 serverip=192.168.10.yyy 
 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=nc 
 stdin=nc 
 stdout=nc 
 uenv_addr=0x810000 
 uenv_import=echo importing envs ...; env import -t $uenv_addr $filesize 
 uenv_init_devices=echo Initializing 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 $disks; do if test $uenv_loaded -eq 0; then setenv device_type $devtype; setenv disk_number $disknum; run uenv_read; fi; done; done; 
 uenv_loaded=0 
 uenv_read=echo Loading envs from $device_type $disk_number...; if load $device_type $disk_number:1 $uenv_addr /boot/uEnv.txt; then setenv uenv_loaded 1; echo ... envs loaded; fi 
 usb_ready_retry=15 
 usb_rootfstype=ext3 
 
 Environment size: 3824/131068 bytes

It is quite difficult to understand what could be wrong, following the installation guide. What could the issue be?

Pogov4> mmc info
mmc info
Device: MVEBU_MMC
Manufacturer ID: 3
OEM: 5344
Name: SD01G 
Tran Speed: 25000000
Rd Block Len: 512
SD version 1.10
High Capacity: No
Capacity: 968.8 MiB
Bus Width: 4-bit
Erase Group Size: 512 Bytes
Pogov4> mmc list
mmc list
MVEBU_MMC: 0 (SD)
Pogov4> mmc dev
mmc dev
switch to partitions #0, OK
mmc0 is current device
Pogov4> mmc part
mmc part
## Unknown partition table type 0
Pogov4> usb stop
usb stop
stopping USB..
Pogov4> usb start
usb start
starting USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Pogov4> usb storage
usb storage
No storage devices, perhaps not 'usb start'ed..?
Pogov4> usb info
usb info
1: Hub,  USB Revision 2.0
 - u-boot EHCI Host Controller 
 - Class: Hub
 - PacketSize: 64  Configurations: 1
 - Vendor: 0x0000  Product 0x0000 Version 1.0
   Configuration: 1
   - Interfaces: 1 Self Powered 0mA
     Interface: 0
     - Alternate Setting 0, Endpoints: 1
     - Class Hub
     - Endpoint 1 In Interrupt MaxPacket 8 Interval 255ms

↧

NSA320 Broken uboot (15 replies)

August 24, 2019, 3:52 pm

≫ Next: Overclock NSA325v2 with u-boot? (no replies)

≪ Previous: POGO-V4-A3-01 + 2017.07 U-Boot Kirkwood + Debian 4.12.1 rootfs + Kernel 5.2.9 (1 reply)

Hi all, my name is Leo, I'm a software engineer from Argentina.
First of all thank you for all the information provided here.

I'm here as another fellow who screwed up, all by him self, his NSA320 uboot.

First of all, my setup:

NSA320 without HDDs (don't wanna screw up my data, I do have an spare HDD to test tho) (had 4.70 firmware)
Manjaro on my laptop
RPI3B+ HypriotOS

I've followed the provided steps, and did not spot any errors whatsoever during the procedure. The output of the commands did match the provided outputs in the guide.

But, I think I've screwed up during the first steps, I realize that now that I'm reading the guide again after a good night sleep.

Quote

1. uBoot envs config should be defined as followed in your /etc/fw_env.config

cat /etc/fw_env.config

# MTD device name Device offset Env. size Flash sector size Number of sectors
/dev/mtd0 0xc0000 0x20000 0x20000

If I'm not mistaken, I think I life /dev/mtd1 as it was and just added /dev/mtd0, and seeing the partition table below that's probably my mistake.

After reboot, my NSA320 in a boot loop. When turning on, all LEDs are turned on for 1 second, then they stop, fan spins and then it starts again, LEDs turn on for a seconds and so on.
If I try to hold the power button, nothing happens. Only way to power it off is unplugging power.

I have hacked myself a serial cable from the NSA320 to an RPI3B+, and I've tried to use kwboot as stated (https://forum.doozan.com/read.php?3,51739,51919#msg-51919).
Although, I have never used a serial cable connection before so I'm not sure what to expect or how to debug the connection.

Quote
sudo ./kwboot -t -B 115200 /dev/ttyAMA0 -b ./uboot.2017.07.tld-1.nsa320.bodhi.tar -p -d
Segmentation Fault

I don't think my serial connection is working.

Quote
dmesg | grep ttyAMA0
[1.0837481] 3f201000.serial: ttyAMA0 at MMIO 0x3f201000 (irq = 81, base_baud = 0) is a PL011 rev2

Do you guys have any documentation on how to connect the NSA320 through an RPI with serial cable? I couldn't find much info to be honest, but I'm not an expert on the subject so I'm probably using the wrong keywords.

If I'm not mistaken, now what I should do is run kwboot through serial to flash the u-boot image directly.

Thank you!!

↧

Overclock NSA325v2 with u-boot? (no replies)

August 28, 2019, 4:44 am

≫ Next: Pogoplug E02, default SSH PWD unknown (1 reply)

≪ Previous: NSA320 Broken uboot (15 replies)

Hello,

It came to my mind that it should be possible to overclock the cpu simply by setting the correct parameters in u-boot.

As NSA325v2 cpu (88F6282) supports 1.6 GHZ, 1.8 GHz, and 2.0 GHz, but is run on 1.6GHz, so ... would there be any ways to enable any other higher frequencies in u-boot?

I cloned the latest uboot, (git clone https://github.com/mibodhi/u-boot-kirkwood) but there's no frequency table in 'u-boot-kirkwood/arch/arm/mach-kirkwood/cpu.c', but instead it looks like it would be reading it from the existing u-boot environment(?) Or is included in some other (include) file?

i.e. 'u-boot-kirkwood/arch/arm/mach-mvebu/cpu.c' has a frequency table, which, in my understanding, could be altered in order to gain higher cpu frequencies...?

So, would it be possible to gain higher cpu frequencies in NSA325v2 simply by hard-coding alternate values to 'u-boot-kirkwood/arch/arm/mach-kirkwood/cpu.c'?

Any ideas?

--jama

↧

Pogoplug E02, default SSH PWD unknown (1 reply)

August 31, 2019, 4:08 am

≫ Next: Pogoplug v4 doesn't connect to network (1 reply)

≪ Previous: Overclock NSA325v2 with u-boot? (no replies)

Hi,

I've been looking at a lot of threads in an attempt to get Linux working on my now redundant Pogoplug E02.

My ultimate aim was to get own cloud running to share photos and avoid Google photos for all my scanned 'analog' photos. I read a lot and it looked achievable!

I tried to get an SSH connection from my Ubuntu box. The connection was refused. Of course I tried using sudo SSH...

I tried the curl method to see if I can get an SSH connection. I did, but the password was rejected.

So, I wonder is there a way to reset the SSH password. I have followed another sites guidance to reset to factory default, but this was generic and I have little confidence that it worked.

I've also tried connecting my CP2102 evb to the serial console on the E02. Some success. I get a console output and after boot there is no console prompt! I think (99%) that the serial connection is working since I can interrupt the boot process at "press any key"... When I type on cutecom it tells me commands like ls are not loaded. The only doubt I have is that since I'm using individual 0.1" pitch wires I can't fit the Find wire in that connector. There is a VERY small impedance between the desired Gnd pin and the pin 1 of the connector to the left of the serial connector. This assumes you are viewing the PCB with the serial connector at the top of the board. Like I say I'm pretty confident that it works. I just don't want to waste anyone's time.

Because this seeming last resort didn't work I try following instructions to create an Ubuntu boot USB stick. I followed the instructions to the letter.
I put the stick into the E02 and held my breath. It booted up the regular firmware. I sighed, a long sigh! I imagine there is more of that ahead.

I'd appreciate any help to get me to a console prompt over the serial connection or any other route towards my end goal...

Familiar with Linux and a veteran Raspi owner. There are a few here. A complete novice with getting anything desirable to happen on my E02!

↧

Pogoplug v4 doesn't connect to network (1 reply)

September 12, 2019, 2:04 pm

≫ Next: Pogoplug E02 couldn't get the rootfs and showed "Gave up waiting for root device" (no replies)

≪ Previous: Pogoplug E02, default SSH PWD unknown (1 reply)

Hi Friends,

First, thanks for all the work you have done here: pretty amazing!

I have recently followed the instructions here https://forum.doozan.com/read.php?3,12381 to add the most current u-boot to a pogoplug v4 and then followed the instructions here https://forum.doozan.com/read.php?2,12096 to put Debian onto a flashdrive and now, while the pogoplug appears to boot, it does not seem to be connecting to my network.

Regrettably, I did not save the log for the setup and I do not have a serial connection to the pogoplug at this time.

Taking that into account, the device appears to have booted all the way to Debian since the light on the front of the device starts blinking green when I power-on the pogoplug and continues blinking until the light on the flashdrive blinks (presumably this means the pogoplug has found the flashdrive) then the pogoplug's light turns a combination of red and green until it finally goes solid green. When I look for the device on my router it does not show up. The ethernet port's lights blink during the booting process.

I wonder if there might be something I could do to fix this without have the serial connection?

with many thanks,
leon

↧

Pogoplug E02 couldn't get the rootfs and showed "Gave up waiting for root device" (no replies)

September 12, 2019, 10:35 pm

≫ Next: zyxel310 + uBoot no USB (4 replies)

≪ Previous: Pogoplug v4 doesn't connect to network (1 reply)

PogoE02>

U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:13:18 -0700)
Pogo E02

SoC:   Kirkwood 88F6281_A0
DRAM:  256 MiB
WARNING: Caches not enabled
NAND:  128 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
No link on egiga0
ping failed; host 192.168.2.118 is not alive
No link on egiga0
ping failed; host 192.168.2.118 is not alive
No link on egiga0
ping failed; host 192.168.2.118 is not alive
No link on egiga0
ping failed; host 192.168.2.118 is not alive
No link on egiga0
ping failed; host 192.168.2.118 is not alive
Hit any key to stop autoboot:  0
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'

Partition Map for USB device 0  --   Partition Type: DOS

Part    Start Sector    Num Sectors     UUID            Type
  1     63              7293825         79534b65-01     83 Boot
  2     7293888         532224          79534b65-02     82

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0
loading envs from usb 0 ...
** File not found /boot/uEnv.txt **
Unknown command 'ide' - try 'help'
Unknown command 'mmc' - try 'help'
running scan_disk ...
Scan device usb
device usb 0:1
1 bytes read in 754 ms (0 Bytes/s)
Found bootable drive on usb 0
loading uImage ...
2461416 bytes read in 904 ms (2.6 MiB/s)
loading uInitrd ...
6362802 bytes read in 1062 ms (5.7 MiB/s)
loading DTB /boot/dts/kirkwood-pogo_e02.dtb ...
** File not found /boot/dts/kirkwood-pogo_e02.dtb **
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-3.14.0-kirkwood-tld-1
   Created:      2014-04-06  20:44:27 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2461352 Bytes = 2.3 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-3.14.0-kirkwood-tld-1
   Created:      2014-04-06  20:44:41 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    6362738 Bytes = 6.1 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
   Loading Ramdisk to 0f4fe000, end 0fb0f672 ... OK
Using machid 0xdd6 from environment

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Initializing cgroup subsys cpuacct
[    0.000000] Linux version 3.14.0-kirkwood-tld-1 (root@tldDebian) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 PREEMPT Tue Apr 1 22:54:58 PDT 2014
[    0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977
[    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] Machine: Pogoplug E02
[    0.000000] Memory policy: Data cache writeback
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 65024
[    0.000000] Kernel command line: console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
[    0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes)
[    0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
[    0.000000] Memory: 246192K/262144K available (4779K kernel code, 352K rwdata, 1644K rodata, 213K init, 424K bss, 15952K reserved)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
[    0.000000]     vmalloc : 0xd0800000 - 0xff000000   ( 744 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xd0000000   ( 256 MB)
[    0.000000]     modules : 0xbf000000 - 0xc0000000   (  16 MB)
[    0.000000]       .text : 0xc0008000 - 0xc064df14   (6424 kB)
[    0.000000]       .init : 0xc064e000 - 0xc0683444   ( 214 kB)
[    0.000000]       .data : 0xc0684000 - 0xc06dc3c4   ( 353 kB)
[    0.000000]        .bss : 0xc06dc3c4 - 0xc074665c   ( 425 kB)
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000] NR_IRQS:114
[    0.000012] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 21474836475ns
[   13.878440] Console: colour dummy device 80x30
[   13.878470] Calibrating delay loop... 1191.11 BogoMIPS (lpj=5955584)
[   13.968215] pid_max: default: 32768 minimum: 301
[   13.968324] Security Framework initialized
[   13.968388] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[   13.968408] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[   13.968995] Initializing cgroup subsys devices
[   13.969019] Initializing cgroup subsys freezer
[   13.969032] Initializing cgroup subsys net_cls
[   13.969043] Initializing cgroup subsys blkio
[   13.969120] CPU: Testing write buffer coherency: ok
[   13.969510] Setting up static identity map for 0x485fa0 - 0x485fdc
[   13.971624] devtmpfs: initialized
[   13.974200] prandom: seed boundary self test passed
[   13.978297] prandom: 100 self tests passed
[   13.978314] pinctrl core: initialized pinctrl subsystem
[   13.978692] regulator-dummy: no parameters
[   13.979029] NET: Registered protocol family 16
[   13.979437] DMA: preallocated 256 KiB pool for atomic coherent allocations
[   13.980218] cpuidle: using governor ladder
[   13.980235] cpuidle: using governor menu
[   13.980329] Kirkwood: MV88F6281-A0, TCLK=200000000.
[   13.980350] Feroceon L2: Enabling L2
[   13.980388] Feroceon L2: Cache support initialised.
[   13.985589] bio: create slab <bio-0> at 0
[   13.986035] vgaarb: loaded
[   13.986333] usbcore: registered new interface driver usbfs
[   13.986400] usbcore: registered new interface driver hub
[   13.986524] usbcore: registered new device driver usb
[   13.987233] Switched to clocksource orion_clocksource
[   14.011955] NET: Registered protocol family 2
[   14.012608] TCP established hash table entries: 2048 (order: 1, 8192 bytes)
[   14.012644] TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
[   14.012676] TCP: Hash tables configured (established 2048 bind 2048)
[   14.012744] TCP: reno registered
[   14.012758] UDP hash table entries: 256 (order: 0, 4096 bytes)
[   14.012780] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[   14.012973] NET: Registered protocol family 1
[   14.013296] RPC: Registered named UNIX socket transport module.
[   14.013308] RPC: Registered udp transport module.
[   14.013315] RPC: Registered tcp transport module.
[   14.013322] RPC: Registered tcp NFSv4.1 backchannel transport module.
[   14.013577] Unpacking initramfs...
[   14.542882] Freeing initrd memory: 6212K (cf4fe000 - cfb0f000)
[   14.542980] NetWinder Floating Point Emulator V0.97 (double precision)
[   14.543536] futex hash table entries: 256 (order: -1, 3072 bytes)
[   14.543691] audit: initializing netlink subsys (disabled)
[   14.543747] audit: type=2000 audit(0.650:1): initialized
[   14.544421] bounce pool size: 64 pages
[   14.544492] zbud: loaded
[   14.544676] VFS: Disk quotas dquot_6.5.2
[   14.544731] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[   14.545031] NFS: Registering the id_resolver key type
[   14.545089] Key type id_resolver registered
[   14.545099] Key type id_legacy registered
[   14.545116] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[   14.545126] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[   14.545282] jffs2: version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
[   14.545566] msgmni has been set to 492
[   14.545689] Key type big_key registered
[   14.547559] alg: No test for stdrng (krng)
[   14.547652] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[   14.547664] io scheduler noop registered
[   14.547672] io scheduler deadline registered
[   14.547702] io scheduler cfq registered (default)
[   14.547961] mv_xor mv_xor.0: Marvell shared XOR driver
[   14.587296] mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
[   14.627289] mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
[   14.627408] mv_xor mv_xor.1: Marvell shared XOR driver
[   14.667297] mv_xor mv_xor.1: Marvell XOR: ( xor cpy )
[   14.707295] mv_xor mv_xor.1: Marvell XOR: ( xor cpy )
[   14.707590] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[   14.728248] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33, base_baud = 12500000) is a 16550A
[   15.273954] console [ttyS0] enabled
[   15.278437] nand: device found, Manufacturer ID: 0xad, Chip ID: 0xf1
[   15.284821] nand: Hynix NAND 128MiB 3,3V 8-bit
[   15.289313] nand: 128MiB, SLC, page size: 2048, OOB size: 64
[   15.295003] Scanning device for bad blocks
[   15.406443] 4 cmdlinepart partitions found on MTD device orion_nand
[   15.412751] Creating 4 MTD partitions on "orion_nand":
[   15.417934] 0x000000000000-0x000000100000 : "u-boot"
[   15.423199] 0x000000100000-0x000000500000 : "uImage"
[   15.428479] 0x000000500000-0x000002500000 : "rootfs"
[   15.433756] 0x000002500000-0x000008000000 : "data"
[   15.439536] libphy: Fixed MDIO Bus: probed
[   15.455575] libphy: orion_mdio_bus: probed
[   15.459838] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[   16.538100] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address 00:25:31:00:37:6b
[   16.547040] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[   16.553626] ehci-pci: EHCI PCI platform driver
[   16.558163] ehci-orion: EHCI orion driver
[   16.562256] orion-ehci orion-ehci.0: EHCI Host Controller
[   16.567726] orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1
[   16.575444] orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000
[   16.597267] orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00
[   16.603393] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[   16.610233] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[   16.617508] usb usb1: Product: EHCI Host Controller
[   16.622411] usb usb1: Manufacturer: Linux 3.14.0-kirkwood-tld-1 ehci_hcd
[   16.629157] usb usb1: SerialNumber: orion-ehci.0
[   16.634359] hub 1-0:1.0: USB hub found
[   16.638182] hub 1-0:1.0: 1 port detected
[   16.642671] mousedev: PS/2 mouse device common for all mice
[   16.957289] usb 1-1: new high-speed USB device number 2 using orion-ehci
[   17.108705] usb 1-1: New USB device found, idVendor=05e3, idProduct=0608
[   17.115451] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[   17.122644] usb 1-1: Product: USB2.0 Hub
[   17.127356] hub 1-1:1.0: USB hub found
[   17.131453] hub 1-1:1.0: 4 ports detected
[   17.417581] usb 1-1.3: new high-speed USB device number 3 using orion-ehci
[   17.530829] usb 1-1.3: New USB device found, idVendor=0930, idProduct=6544
[   17.537764] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   17.545123] usb 1-1.3: Product: DataTraveler 2.0
[   17.549781] usb 1-1.3: Manufacturer: Kingston
[   17.554160] usb 1-1.3: SerialNumber: 001CC0EC329EC020669A06EE
[   17.657259] rtc-mv rtc-mv: internal RTC not ticking
[   17.662281] i2c /dev entries driver
[   17.666398] hidraw: raw HID events driver (C) Jiri Kosina
[   17.672119] drop_monitor: Initializing network drop monitor service
[   17.678634] TCP: cubic registered
[   17.681969] NET: Registered protocol family 17
[   17.686553] Key type dns_resolver registered
[   17.691340] registered taskstats version 1
[   17.695940] regulator-dummy: incomplete constraints, leaving on
[   17.702248] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[   17.710190] Freeing unused kernel memory: 212K (c064e000 - c0683000)
Loading, please wait...
[   17.787942] udevd[54]: starting version 175
[   17.955983] SCSI subsystem initialized
[   17.985751] usb-storage 1-1.3:1.0: USB Mass Storage device detected
[   18.030006] scsi0 : usb-storage 1-1.3:1.0
[   18.042877] usbcore: registered new interface driver usb-storage
[   19.028190] scsi 0:0:0:0: Direct-Access     Kingston DataTraveler 2.0 1.00 PQ: 0 ANSI: 2
[   19.065019] sd 0:0:0:0: [sda] 7827392 512-byte logical blocks: (4.00 GB/3.73 GiB)
[   19.073870] sd 0:0:0:0: [sda] Write Protect is off
[   19.079234] sd 0:0:0:0: [sda] No Caching mode page found
[   19.084574] sd 0:0:0:0: [sda] Assuming drive cache: write through
[   19.094483] sd 0:0:0:0: [sda] No Caching mode page found
[   19.099888] sd 0:0:0:0: [sda] Assuming drive cache: write through
[   19.107731]  sda: sda1 sda2
[   19.113608] sd 0:0:0:0: [sda] No Caching mode page found
[   19.118990] sd 0:0:0:0: [sda] Assuming drive cache: write through
[   19.125115] sd 0:0:0:0: [sda] Attached SCSI removable disk
[   19.141197] sd 0:0:0:0: Attached scsi generic sg0 type 0
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Waiting for root file system ... done.
Gave up waiting for root device.  Common problems:
 - Boot args (cat /proc/cmdline)
   - Check rootdelay= (did the system wait long enough?)
   - Check root= (did the system wait for the right device?)
 - Missing modules (cat /proc/modules; ls /dev)
ALERT!  /dev/disk/by-label/rootfs does not exist.  Dropping to a shell!
modprobe: module i8042 not found in modules.dep
[   38.406883] uhci_hcd: USB Universal Host Controller Interface driver
[   38.422800] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[   38.439274] usbcore: registered new interface driver usbhid
[   38.444880] usbhid: USB HID core driver


BusyBox v1.20.2 (Debian 1:1.20.0-7) built-in shell (ash)
Enter 'help' for a list of built-in commands.

/bin/sh: can't access tty; job control turned off
(initramfs) ls /boot
ls: /boot: No such file or directory
(initramfs) printenv

↧

zyxel310 + uBoot no USB (4 replies)

September 23, 2019, 5:28 am

≫ Next: Restore to mtd partitions (no replies)

≪ Previous: Pogoplug E02 couldn't get the rootfs and showed "Gave up waiting for root device" (no replies)

Hi,

I tried to install debian on zyxel310 nas server, because I had problems with original fw (nfs freeze and some other). Nex time I tried openwrt, but there is some problem with speed over net (samba/nfs/sshfs - all are slow)

But when I tried debian - http://davidegironi.blogspot.com/2018/12/debian-and-openmediavault-on-zyxtel.html I have problem with step 2

uboot does not see usb:

NSA310> printenv 
baudrate=115200
bootcmd=ubi part ubi; ubi read 0x800000 kernel; bootm 0x800000
bootdelay=3
console=console=ttyS0,115200
ethact=egiga0
ethaddr=50:67:F0:69:BF:1E
ipaddr=192.168.1.108
mtddevname=uboot
mtddevnum=0
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:0x0c0000(uboot),0x80000(uboot_env),0x7ec0000(ubi)
partition=nand0,0
serverip=192.168.1.2
stderr=serial
stdin=serial
stdout=serial

Environment size: 394/131068 bytes
NSA310> 

NSA310> usb reset
resetting USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008c80
EHCI timed out on TD - token=0x80008c80
EHCI timed out on TD - token=0x80008c80
 ERROR: NOT USB_CONFIG_DESC 80
EHCI timed out on TD - token=0x80008d80
2 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
NSA310>

but when I installed openwrt, usb in uboot worked, in openwrt usb working too.
Uboot I installed with kwboot

I tried 4 different devices, but nothing :-/

can someone help me please?

thank You a lot

↧

Restore to mtd partitions (no replies)

September 26, 2019, 2:34 pm

≫ Next: PogoPlug v4 Soft Brick Recovery / Restoring MTDs (1 reply)

≪ Previous: zyxel310 + uBoot no USB (4 replies)

Hi
I have some files and I want to write in mtd partitions.

My files name are:
- BOOT.bin
- devicetree.dtb
- rootfs.jffs2
- uImage

How can I do it?
These images has a .sh file to install.
here is the code:

if [ -e BOOT.bin ]; then
        flash_erase /dev/mtd0 0x0 0x80 >/dev/null 2>&1
        nandwrite -p -s 0x0 /dev/mtd0 ./BOOT.bin >/dev/null 2>&1
        rm -rf BOOT.bin
    fi

    if [ -e devicetree.dtb ]; then
        flash_erase /dev/mtd0 0x1020000 0x1 >/dev/null 2>&1
        nandwrite -p -s 0x1020000 /dev/mtd0 ./devicetree.dtb >/dev/null 2>&1
        rm devicetree.dtb
    fi

    if [ -e uImage ]; then 
      flash_erase /dev/mtd0 0x1100000 0x40 >/dev/null 2>&1
      nandwrite -p -s 0x1100000 /dev/mtd0 ./uImage >/dev/null 2>&1
      rm uImage
    fi

    if [ -e rootfs.jffs2 ]; then
      if [ -f /dev/mtd3 ];then
          flash_erase /dev/mtd2 0x0 0x1E0 >/dev/null 2>&1
      else
          flash_erase /dev/mtd2 0x0 0x280 >/dev/null 2>&1
      fi
      nandwrite -p -s 0x0 /dev/mtd2 ./rootfs.jffs2 >/dev/null 2>&1
      rm rootfs.jffs2
    fi

When I want to run "flash_erase /dev/mtd0 0x0 0x80"
I get this error:

libmtd: error!: "/dev/mtd0" is not a character device
flash_erase: error!: mtd_get_dev_info failed

How can I do it?
thanks

↧

PogoPlug v4 Soft Brick Recovery / Restoring MTDs (1 reply)

October 11, 2019, 7:39 pm

≫ Next: Help with Lenovo NAS Iomega IX4-300d and PX4-400d (no replies)

≪ Previous: Restore to mtd partitions (no replies)

I PM'd bodhi for advice about restoring the MTDs on my PogoPlug v4. He requested that I make a new thread here, I'd imagine in the interest of helping anyone else that's gotten themselves in the same situation I have.

To recap --

I (naturally) messed up my PogoPlug by not reading carefully enough when flashing and by also not keeping a better record or any kind of backup of what I had / hadn't done to it over the course of messing with it. The short version is that I used one of the earliest versions of bodhi's guide to convert it to Debian years ago, briefly used it for something that now eludes my memory, lost it in the back of a closet for a while, recently rediscovered it and would like to use it as a network ad blocker via PiHole.

When I went to update everything to the latest versions of bodhi's uBoot and Debian image, I obviously did something wrong, though I'm not sure what. I suspect that I've managed to mess up the envvars, but again I'm not 100% sure.

Typically when I get myself into situations like this, I'll wipe everything back to the way it was when I started (back to known-good) and simply try again. In this instance, 1) I'm not sure that's the best solution, and 2) not sure how to go about doing it if it is. I did try to grab bodhi's MTDs archive from here, but it looks like the link is dead. Reading through the thread, it seemed like the better option to simply send bodhi a message rather than continue to possibly make things worse by messing with it on my own. I guess the pertinent details of my specific issue are:

[*] My PogoPlug v4 will no longer boot correctly, or identify itself to the network
[*] I do still have serial console access though, and can in fact interrupt the boot process and get to the "PogoPlug v4>" prompt
[*] When all is said and done, I'd ideally like to have your latest uBoot and Debian Buster image be the only things on the Plug and running smoothly

So if I've not already taken up too much of your time, and if it's not asking too much, what do I do?

Bodhi asked that I post the output of the `printvars` command, which I have done below:

U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:34:01 -0700)
Pogoplug V4

SoC:   Kirkwood 88F6192_A1
DRAM:  128 MiB
WARNING: Caches not enabled
NAND:  128 MiB
MMC:   MVEBU_MMC: 0
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
Hit any key to stop autoboot: 10

Pogov4> 

Pogov4> printenv

arcNumber=3960
bootargs=console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=orion_nand:2M(u-boot),3M(uImage),3M(uImage2),8M(failsafe),112M(root) init=/bin/systemd
bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec
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
bootdelay=10
bootdev=usb
device=0:1
device_type=mmc
devices=usb ide mmc
disk_number=3
disks=0 1 2 3
dtb_file=/boot/dts/kirkwood-pogoplug_v4.dtb
ethact=egiga0
ethaddr=00:25:31:03:2b:1b
if_netconsole=ping $serverip
init_ide=ide reset
init_mmc=mmc rescan
init_usb=usb start
ipaddr=192.168.0.231
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=f78
mainlineLinux=yes
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:2M(u-boot),3M(uImage),3M(uImage2),8M(failsafe),112M(root)
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
scan_ide=ide reset
scan_mmc=mmc rescan
scan_usb=usb start
serverip=192.168.0.220
set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=orion_nand:2M(u-boot),3M(uImage),3M(uImage2),8M(failsafe),112M(root) init=/bin/systemd
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=echo Initializing 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 $disks; do if test $uenv_loaded -eq 0; then setenv device_type $devtype; setenv disk_number $disknum; run uenv_read; fi; done; done;
uenv_loaded=0
uenv_read=echo Loading envs from $device_type $disk_number...; if load $device_type  $disk_number:1 $uenv_addr /boot/uEnv.txt; then setenv uenv_loaded 1; echo ... envs loaded; fi
usb_ready_retry=15

Environment size: 3275/131068 bytes

Pogov4>

Bodhi explained that the steps to fix whatever I've done should be easy enough, he described them as:

- Recreate the Buster image to make sure I have a good rootfs.
- Power up, interrupt serial console and load a default set of envs, adjust a few envs for Pogo V4 and my network.
- Boot

Three steps certainly does seem simple enough, hopefully Bodhi will be along shortly with a few more details.

↧

Help with Lenovo NAS Iomega IX4-300d and PX4-400d (no replies)

October 12, 2019, 10:43 pm

≫ Next: Seagate GoFlex Net - A lot of bad block in "DMESG" (2 replies)

≪ Previous: PogoPlug v4 Soft Brick Recovery / Restoring MTDs (1 reply)

Hi. I have 2 Lenovo NAS, model IX4-300d and PX4-400d.
They are both new but came without disk and I have not been able to set them.
Does anyone here have at least one of these models that could help me set the unit?

Thanks in advance.

↧

Seagate GoFlex Net - A lot of bad block in "DMESG" (2 replies)

October 15, 2019, 8:03 pm

≫ Next: RN204 U-Boot boot issue (1 reply)

≪ Previous: Help with Lenovo NAS Iomega IX4-300d and PX4-400d (no replies)

Hello All,
Before I start to beg for help, let me introduce myself :
I am 42 years old and a linux newcomer.

I followed this forum years ago when I boought the Goflex Net (GFN) but at that time I decided to use a custom linux called "Squeezeplug". It ran on USB thumbdrive (2 died, exhausted by the R/W cycle). it was a beat tricky to ssh and start the logitechmediaserver. then I moved to a RPI3 that has a best fit for use. The GFNwent to the drawer.

Now I would like to use the GFN to set a drive to host a shared folder ( samba ), to sync the file from the different device around the house (4PC + 2 tablet). Optionally run some module like "transmission". I would like that the GFN boots and runs without the need of the USB thumbdrive because they wear to o fast and are not reliable to run 24/7.
Thati swhy I wanted to refresh the GFN with latest UBOOT, ROOTFS and Rescue Sytem.

I tried to follow the tutorial : 2017.07 U-Boot Kirkwood - GoFlexNet, but at step 4 :
"Be sure there is no bad block in the first 1M of your NAND (check dmesg). This is very important, if there is bad block in the first 1M (8 blocks), don't flash u-boot, because you will almost certainly brick your box. Please post your question here (there is a work around for it). "

DMESG give this log output :( see attachment for detail)
Scanning device for bad blocks
Bad eraseblock 1 at 0x000000020000
Bad eraseblock 3 at 0x000000060000
Bad eraseblock 4 at 0x000000080000
Bad eraseblock 5 at 0x0000000a0000
Bad eraseblock 7 at 0x0000000e0000
Bad eraseblock 8 at 0x000000100000
Bad eraseblock 10 at 0x000000140000
Bad eraseblock 11 at 0x000000160000
Bad eraseblock 12 at 0x000000180000
Bad eraseblock 13 at 0x0000001a0000
Bad eraseblock 15 at 0x0000001e0000
Bad eraseblock 16 at 0x000000200000
Bad eraseblock 17 at 0x000000220000
Bad eraseblock 18 at 0x000000240000
Bad eraseblock 19 at 0x000000260000
Bad eraseblock 20 at 0x000000280000
Bad eraseblock 22 at 0x0000002c0000

thats stopped me .
I tried to implement the rescue system v.2 from Jeff : https://forum.doozan.com/read.php?4,3896
Unfortunately, I got this message :
--2019-10-15 16:06:56-- (try: 2) http://projects.doozan.com/uboot/valid-uboot.md5
Connecting to projects.doozan.com|45.77.104.33|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1133 (1.1K)
Saving to: `/tmp/valid-uboot.md5'

100%[===========================================================================>] 1,133 --.-K/s in 0s

2019-10-15 16:06:56 (34.2 MB/s) - `/tmp/valid-uboot.md5' saved [1133/1133]

##
## uBoot is not up-to-date
## Please install the newest uBoot and then re-run this installer.
##

What do I do ? proceed with uboot anyway ? I fear to brick the GFN
I have logs from mount , fw_printenvs and uboot version available
Thanks for your support.

↧

RN204 U-Boot boot issue (1 reply)

October 29, 2019, 7:59 pm

≫ Next: Pogoplug E02 no Ethernet after uboot update (1 reply)

≪ Previous: Seagate GoFlex Net - A lot of bad block in "DMESG" (2 replies)

Preface, I am a newbie and am looking for some help with U-Boot. I have a little knowledge of programming. I know the ‘environment variables’ are just global constants that the program ‘U-Boot’ uses to process conditions. I have been reading on http://www.denx.de/ and a few other websites. One site https://www.linuxjournal.com/content/handy-u-boot-trick shows block diagram ‘x-loader – u-boot.bin – interruption – u-boot shell --or-- no interruption – execute bootcmd.
I have a Netgear NAS that does not boot correctly. I know the hardware is fine.
Here is the issue - with usb-serial attachment I am able to connect. If I interrupt the boot process and from the U-Boot command line and I type in ‘boot’, the unit comes up normally and I can access it. If I don’t interrupt the boot it goes into another state and I cannot access.
My question is what is U-Boot doing? What is it setting NAS up for? I have looked at some environment prints from a Buffalo NAS (which usually boots from the 1st harddrive) and compared it to my environment variables to see the differences. Not sure how U-Boot is handling things. I know U-Boot is basically bootstrap software to load up operating systems. If you need full environment printout I can supply.

U-Boot 2013.10-alpine_db-1.49 (Dec 21 2017 - 13:28:18)

Here is excerpts from my environment:

bootcmd=run odmbootseq;
odmbootseq=run odmbootargs; run odmbootusb; run odmbootfirmware; failure;
odmbootargs=setenv bootargs pci=pcie_bus_perf console=ttyS0,115200 $reasonargs $bootargsextra ; printenv bootargs
reasonargs=reason=normal
bootargsextra=bdtype=rn204
odmbootusb=usb start;fatload usb 0 $loadaddr NTGR_USBBOOT_INFO.txt;if test $? -eq 0; then run odmbootbackusb;fi;
loadaddr=0x08000000
loadaddr_dt=0x07000000
loadaddr_fs=0x8800000
loadaddr_payload=0x08000004
loadaddr_rootfs_chk=0x07000000
nand_pt_addr_al_boot=0x0
nand_pt_addr_fs=0x01000000
nand_pt_addr_kernel=0x00400000
nand_pt_addr_kernel_1=0x00400000
nand_pt_addr_kernel_2=0x00a00000
nand_pt_desc_kernel_1=Test kernel A
nand_pt_desc_kernel_2=Test kernel B
nand_pt_size_al_boot=0x00100000
nand_pt_size_fs=0x3f000000
nand_pt_size_kernel=0x00c00000
odmbootbackusb=usb start;lcd_print "Loading..."; fatload usb 0 $loadaddr uImage-recovery;if test $? -eq 0; then fatload usb 0 $loadaddr_fs initrd-recovery.gz;if test $? -eq 0; then flash_contents_obj_read DT 0 $loadaddr_dt;run odmboot;else;lcd_print "Failed!";failure;fi;else;lcd_print "Failed!";failure;fi;
odmboot=lcd_print "Booting..."; gpio set 33;bootm $loadaddr $loadaddr_fs $loadaddr_dt;
test=echo this is a test!

This is from 'ALPINE_DB> fdt print'.
( Per Netgear for 'usb recovery' put usb drive in and press and hold the backup button and power on, and it 'should' load from the usb. Not sure if the backup button is 'gpio33'.)

if_gpio33 {
	id = "if_gpio";
	arg = <0x00000021>;
};
button@3 {
	label = "Backup Button";
	linux,code = <0x00000085>;
	gpios = <0x00000009 0x00000000 0x00000001>;
};

If I do not interrupt boot process this is some of what comes on console:

Hit any key to stop autoboot:  0 
bootargs=pci=pcie_bus_perf console=ttyS0,115200 reason=normal bdtype=rn204
## Error: "odmbootusb" not defined

NAND read: device 0 offset 0x7000000, size 0x400000
 4194304 bytes read: OK

NAND read: device 0 offset 0x7400000, size 0xb00000
 11534336 bytes read: OK
## Booting kernel from Legacy Image at 08000000 ...
   Image Name:   Linux-3.10.20-al-2.5.2
   Created:      2014-11-17  23:30:27 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2978744 Bytes = 2.8 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 08800000 ...
   Image Name:   
   Created:      2015-01-12   8:29:10 UTC
   Image Type:   ARM Linux RAMDisk Image (lzma compressed)
   Data Size:    10039368 Bytes = 9.6 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
** Using primary FDT on legacy kernel
## Flattened Device Tree blob at 01b25008
   Booting using the fdt blob at 0x1b25008
   Loading Kernel Image ... OK
   Loading Ramdisk to 01190000, end 01b23048 ... OK
   Using Device Tree in place at 01b25008, end 01b2c1b4
ft_board_setup_clock: unable to set /soc/arch-timer.clock-frequency!

Starting kernel ...

If I interrupt the boot process and type in boot at command line, this is what I get:

ALPINE_DB> run odmbootseq
bootargs=pci=pcie_bus_perf console=ttyS0,115200 reason=normal bdtype=rn204
(Re)start USB...
USB0:   Register 8000450 NbrPorts 8
Starting the controller
USB XHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
** Bad device usb 0 **

NAND read: device 0 offset 0x200000, size 0x600000
 6291456 bytes read: OK

NAND read: device 0 offset 0x800000, size 0x400000
 4194304 bytes read: OK
gpio: pin 33 (gpio 33) value is 1
## Booting kernel from Legacy Image at 08000000 ...
   Image Name:   Linux-4.4.184.alpine.1
   Created:      2019-09-05   2:32:26 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3437376 Bytes = 3.3 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 08800000 ...
   Image Name:   initramfs
   Created:      2019-09-18   3:20:11 UTC
   Image Type:   ARM Linux RAMDisk Image (lzma compressed)
   Data Size:    3423536 Bytes = 3.3 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 07000000
   Booting using the fdt blob at 0x7000000
   Loading Kernel Image ... OK
   reserving fdt memory region: addr=0 size=100000
   Loading Ramdisk to 017df000, end 01b22d30 ... OK
   Using Device Tree in place at 07000000, end 07008bd3

Starting kernel ...

Also, I noticed in the environment these line:

bootext4=lcd_print "Booting...";scsi init; ext4load scsi ${ext4dev}:${ext4part} $loadaddr ${ext4dir}${dt_filename};if test $? -ne 0; then run fail; exit; fi;if test ${dt_is_from_toc} != 1; then; else flash_contents_obj_read_mem $loadaddr_dt $loadaddr;if test $? -ne 0; then run fail; exit; fi;fi;ext4load scsi ${ext4dev}:${ext4part} $loadaddr ${ext4dir}uImage;if test $? -ne 0; then run fail; exit; fi;fdt addr $loadaddr_dt;bootm $loadaddr - $fdtaddr;run fail; exit
bootnand=lcd_print "Booting...";nand set_partition_offset $nand_pt_addr_kernel;nand read $loadaddr $nand_pt_addr_kernel 4;setenvmem filesize $loadaddr;incenv filesize 4;nand read $loadaddr $nand_pt_addr_kernel $filesize;nand set_partition_offset $nand_pt_addr_al_boot;bootm $loadaddr_payload - $fdtaddr;lcd_print Failed!;failue;
bootnandmulti=run kernel_select;if test $kernel_selected -ne 0; then run bootnand; fi
boottftp=lcd_print "Booting...";tftpboot $loadaddr ${tftpdir}${dt_filename};if test $? -ne 0; then run fail; exit; fi;if test ${dt_is_from_toc} != 1; then; else flash_contents_obj_read_mem $loadaddr_dt $loadaddr;if test $? -ne 0; then run fail; exit; fi;fi;tftpboot $loadaddr ${tftpdir}uImage;if test $? -ne 0; then run fail; exit; fi;fdt addr $loadaddr_dt;bootm $loadaddr - $fdtaddr;run fail; exit
bootupd=is_nand_boot; if test $? -eq 0; then run bootupdspi; else; run bootupdnand; fi
bootupdnand=lcd_print "Updating al-boot" "to NAND"; tftpboot $loadaddr_dt ${tftpdir}${dt_filename};if test $? -ne 0; then run fail; exit; fi;if test ${dt_is_from_toc} != 1; then; else flash_contents_obj_read_mem $loadaddr $loadaddr_dt;if test $? -ne 0; then run fail; exit; fi;fi;tftpboot $loadaddr ${tftpdir}boot.img; if test $? -ne 0; then run fail; exit; fi;nand set_partition_offset $nand_pt_addr_al_boot;nand erase.spread $nand_pt_addr_al_boot $filesize; nand write $loadaddr $nand_pt_addr_al_boot $filesize; nand erase.spread ${dt_location} 10000; nand write ${loadaddr_dt} ${dt_location} 10000; lcd_print "Done"
bootupdnandy=lcd_print "Updating al-boot" "to NAND"; echo >> Use YModem to upload the device tree binary...;loady $loadaddr_dt;if test $? -ne 0; then run fail; exit; fi;if test ${dt_is_from_toc} != 1; then; else flash_contents_obj_read_mem $loadaddr $loadaddr_dt;if test $? -ne 0; then run fail; exit; fi;fi;echo >> Use YModem to upload the boot image binary...;loady $loadaddr;if test $? -ne 0; then run fail; exit; fi;nand set_partition_offset $nand_pt_addr_al_boot;nand erase.spread $nand_pt_addr_al_boot $filesize; nand write $loadaddr $nand_pt_addr_al_boot $filesize; nand erase.spread ${dt_location} 10000; nand write ${loadaddr_dt} ${dt_location} 10000;lcd_print "Done"
bootupdspi=lcd_print "Updating al-boot" "to SPI"; tftpboot $loadaddr_dt ${tftpdir}${dt_filename};if test $? -ne 0; then run fail; exit; fi;if test ${dt_is_from_toc} != 1; then; else flash_contents_obj_read_mem $loadaddr $loadaddr_dt;if test $? -ne 0; then run fail; exit; fi;fi;setenv filesize_dt $filesize;tftpboot ${loadaddr} ${tftpdir}boot.img; if test $? -ne 0; then run fail; exit; fi;sf probe; sf erase 0 +${filesize}; sf write ${loadaddr} 0 ${filesize}; sf erase ${dt_location} +${filesize_dt}; sf write ${loadaddr_dt} ${dt_location} ${filesize_dt}; echo bootupd done;echo Notice: Changes in default environment variables will only take effect once the;echo environment variables are deleted from flash using the 'delenv' script;lcd_print "Done"
bootupdspiy=lcd_print "Updating al-boot" "to SPI"; echo >> Use YModem to upload the device tree binary...;loady $loadaddr_dt;if test $? -ne 0; then run fail; exit; fi;if test ${dt_is_from_toc} != 1; then; else flash_contents_obj_read_mem $loadaddr $loadaddr_dt;if test $? -ne 0; then run fail; exit; fi;fi;setenv filesize_dt $filesize;echo >> Use YModem to upload the boot image binary...;loady ${loadaddr};if test $? -ne 0; then run fail; exit; fi;sf probe; sf erase 0 +${filesize}; sf write ${loadaddr} 0 ${filesize}; sf erase ${dt_location} +${filesize_dt}; sf write ${loadaddr_dt} ${dt_location} ${filesize_dt};echo bootupd done;echo Notice: Changes in default environment variables will only take effect once the;echo environment variables are deleted from flash using the 'delenv' script;lcd_print "Done"
bootupdy=is_nand_boot; if test $? -eq 0; then run bootupdspiy;else; run bootupdnandy; fi
rootargshd=setenv rootargs root=${hdroot} rw
rootargsnand=setenv rootargs root=ubi0:root rootfstype=ubifs ubi.mtd=3
rootargsnfs=setenv rootargs root=/dev/nfs rw nfsroot=${serverip}:${nfsrootdir},tcp,nolock rw ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${board_name}:eth1:none
rootfsupd=lcd_print "Updating rootfs...";tftpboot $loadaddr_rootfs_chk ${tftpdir}rootfs.ubi.md5;if test $? -ne 0; then run fail; exit; fi;tftpboot $loadaddr ${tftpdir}rootfs.ubi;if test $? -ne 0; then run fail; exit; fi;md5sum -v $loadaddr $filesize *$loadaddr_rootfs_chk;if test $? -ne 0; then run fail; exit; fi;nand set_partition_offset $nand_pt_addr_fs;nand erase.spread $nand_pt_addr_fs $nand_pt_size_fs;nand write $loadaddr $nand_pt_addr_fs $filesize;nand set_partition_offset $nand_pt_addr_al_boot;echo rootfsupd done;lcd_print "Done"

2nd question - how do the root and bootup and a few other statements come into play? What calls these variables?
3rd question – ‘odmbootseq=run odmbootargs; run odmbootusb; run odmbootfirmware; failure;’ what does ‘failure’ do in u-boot? I cannot find that in command listings, or anywhere on the web.

Thanks in advance.
Mike

=========
moderator edit: please use code tags to post logs and commands

↧

Pogoplug E02 no Ethernet after uboot update (1 reply)

November 3, 2019, 10:43 pm

≫ Next: Zyxel NSA 325 / Power on after power failure (3 replies)

≪ Previous: RN204 U-Boot boot issue (1 reply)

I recently used the serial port and tftp to update the uboot on a Pogoplug E02 to the 2017.07 U-Boot Kirkwood version. It seemed to go well but the result was no Ethernet port activity after rebooting. I get a brief flash of the port status and speed LEDs after a reset but they're otherwise dark. My router does not notice the Pogoplug and all pings from the Pogoplug fail.

I checked the printenv results and they match the pre-update values: ethact=egig0, ethaddr matches the MAC printed on the Pogoplug sticker, and ipaddr is within the address range of the router. Pluging in a USB stick with Debian boots all the way to the user login (using the serial port) but doesn't seem to make the Ethernet port do anything either.

The Ethernet port did work prior to the uboot update. Any ideas as to what I should be looking for?

↧

Zyxel NSA 325 / Power on after power failure (3 replies)

November 10, 2019, 4:43 am

≫ Next: Zyxel NSA 325 / Restore stock firmware (1 reply)

≪ Previous: Pogoplug E02 no Ethernet after uboot update (1 reply)

Hello,

does anyone please know how to configure automatic power on/off after power failure behavior of Zyxel NSA 325?

I cannot find any information about how to set this. My only idea now is to temporarily boot into stock and try to set it there to try if it persists. But I am not sure if booting stock is possible after u-boot upgrade.

Thanks for any ideas or hints,

Tomas

↧

Zyxel NSA 325 / Restore stock firmware (1 reply)

November 10, 2019, 3:30 pm

≫ Next: trying to upgrade PogoPlug E02 (4 replies)

≪ Previous: Zyxel NSA 325 / Power on after power failure (3 replies)

Hello,

I am currently using OpenWrt on my NSA325 but I would like to run the stock firmware ( V4.81(AALS.1)C0 which is available from official page https://www.zyxel.com/support/SupportLandingSR.shtml?c=gb&l=en&kbid=M-01820&md=NSA325%20v2 ) to try to set Power On After Power Failure ( https://forum.doozan.com/read.php?3,92579 ). But I have no clue how to corectly reflash it.

Does someone know how to do it?

Thanks,

Tomas

↧

trying to upgrade PogoPlug E02 (4 replies)

November 18, 2019, 8:51 pm

≫ Next: nsa325 v2 "formatting" (1 reply)

≪ Previous: Zyxel NSA 325 / Restore stock firmware (1 reply)

I was following the UBoot instructions from an older pogoplug I had set up here back in 2014-15, I think the pendrive eventually went bad. I was still able to boot into the stock pogo OS and was following these instructions . I noticed I didn't have an /boot folder towards the end, setup netconsole and rebooted. Below is the output from booting.
Where did I go wrong?

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...
** File not found /boot/uEnv.txt **
Loading envs from usb 1...
** Bad device usb 1 **
Loading envs from usb 2...
** Bad device usb 2 **
Loading envs from usb 3...
** Bad device usb 3 **
Loading envs from ide 0...
** Bad device ide 0 **
Loading envs from ide 1...
** Bad device ide 1 **
Loading envs from ide 2...
** Bad device ide 2 **
Loading envs from ide 3...
** Bad device ide 3 **
Loading envs from mmc 0...
** Bad device mmc 0 **
Loading envs from mmc 1...
** Bad device mmc 1 **
Loading envs from mmc 2...
** Bad device mmc 2 **
Loading envs from mmc 3...
** Bad device mmc 3 **
running scan_disk ...
Scan device usb
device usb 0:1
1 bytes read in 569 ms (0 Bytes/s)
Found bootable drive on usb 0
loading uImage ...
1612096 bytes read in 985 ms (1.6 MiB/s)
loading uInitrd ...
7096647 bytes read in 1974 ms (3.4 MiB/s)
loading DTB /boot/dts/kirkwood-pogo_e02.dtb ...
** File not found /boot/dts/kirkwood-pogo_e02.dtb **
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   kernel 3.2.0-4-kirkwood
   Created:      2014-11-07  19:11:20 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1612032 Bytes = 1.5 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   ramdisk 3.2.0-4-kirkwood
   Created:      2014-11-07  19:11:22 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    7096583 Bytes = 6.8 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... Bad Data CRC
Ramdisk image is corrupt or invalid
PogoE02>

↧

nsa325 v2 "formatting" (1 reply)

November 23, 2019, 4:09 pm

≫ Next: U-Boot for Zyxel NSA-325v2 (1 reply)

≪ Previous: trying to upgrade PogoPlug E02 (4 replies)

Hi
it's been a while i enjoyed playing with my kirkwood so i've forgotten everything;
my issue is rather simple: some packages like apache2 are missing dependencies and this broke even ftp connections
since i've been trying hard to fix it, even by adding newer repos, i guess the easiest solution is to format and reinstall debian, just i don't remember how to do it
and above all if i have do it via serial cable or i can just unpack the linux-5.3.2-kirkwood-tld-1-bodhi.tar.bz2 in the /boot directory of the hard disk where debian is running
sorry for the silly request

↧

U-Boot for Zyxel NSA-325v2 (1 reply)

November 24, 2019, 2:48 pm

≫ Next: Zyxel NSA320 Bricked (3 replies)

≪ Previous: nsa325 v2 "formatting" (1 reply)

Hi,

I don't find any U-Boot for the Zyxel NSA-325v2 - is it exactly the same as the v1 ? I just got a stock Zyxel NSA325-v2 on my desk which I want to convert to something useful:-)

Cheers,

4920441

↧