Welcome! Log In Create A New Profile

Advanced

2017.07 U-Boot Kirkwood - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile, Sheevaplug, NSA325, NSA320, NSA310S, NSA320S, NSA310, HP T5325, Dreamplug

Posted by bodhi 
I'd like to upgrade to the newest u-boot image for my e02, but i'm a bit stuck. When I built my e02, i followed the instructions here: http://archlinuxarm.org/platforms/armv5/pogoplug-v2-pinkgray this evidently gave me a u-boot that doesn't have wget:

version:
U-Boot 2014.04.R3-1 (May 26 2014 - 19:45:55) Arch Linux ARM
Pogo E02
gcc (GCC) 4.8.2 20131219 (prerelease)
GNU ld (GNU Binutils) 2.24

PogoE02> printenv
baudrate=115200
bootcmd=usb start; setenv letter 9;for type in usb; do for disk in 0 1 2 3; do if ${type} part ${disk};then setexpr letter $letter + 1;run load;fi;done;done;
bootdelay=3
bootm=echo Booting from ${disk} ...; run setargs; bootm ${loadaddr};
bootz=echo Booting from ${disk} ...; run setargs; bootz ${loadaddr} - ${fdt_addr};
console=ttyS0
ethact=egiga0
ethaddr=XXXX REDACTED XXXX
fdt_addr=0x800000
fdt_file=/boot/dtbs/kirkwood-pogo_e02.dtb
if_netconsole=ping $serverip
importbootenv=echo Importing environment (uEnv.txt)...; env import -t $loadaddr $filesize
load=echo Attempting to boot from ${type} ${disk}:1...;if run loadbootenv; then run importbootenv;fi;echo Checking if uenvcmd is set ...;if test -n $uenvcmd; then echo Running uenvcmd ...;run uenvcmd;fi;echo Running default loadzimage ...;if run loadzimage; then run loadfdt;run bootz;fi;echo Running default loaduimage ...;if run loaduimage; then run bootm;fi;
loadaddr=0x810000
loadbootenv=load ${type} ${disk}:1 ${loadaddr} /boot/uEnv.txt
loadfdt=load ${type} ${disk}:1 ${fdt_addr} ${fdt_file}
loaduimage=load ${type} ${disk}:1 ${loadaddr} ${uimage}
loadzimage=load ${type} ${disk}:1 ${loadaddr} ${zimage}
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),-(rootfs)
preboot=run if_netconsole start_netconsole
setargs=setenv bootargs console=${console},${baudrate} ${optargs} root=/dev/sd${letter}1 rw rootwait ${mtdparts}
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
uimage=/boot/uImage
zimage=/boot/zImage

Environment size: 1664/131068 bytes

I'm not really sure what the first step is going to be, I checked the link to get the tools, but they assume I have wget. Also I've tried and command not found:

busybox wget

These are the commands available:
?       - alias for 'help'
base    - print or set address offset
bdinfo  - print Board Info structure
boot    - boot default, i.e., run 'bootcmd'
bootd   - boot default, i.e., run 'bootcmd'
bootm   - boot application image from memory
bootp   - boot image via network using BOOTP/TFTP protocol
bootz   - boot Linux zImage image from memory
chpart  - change active partition
cmp     - memory compare
coninfo - print console devices and information
cp      - memory copy
crc32   - checksum calculation
dhcp    - boot image via network using DHCP/TFTP protocol
echo    - echo args to console
editenv - edit environment variable
env     - environment handling commands
exit    - exit script
ext2load- load binary file from a Ext2 filesystem
ext2ls  - list files in a directory (default /)
ext4load- load binary file from a Ext4 filesystem
ext4ls  - list files in a directory (default /)
false   - do nothing, unsuccessfully
fatinfo - print information about filesystem
fatload - load binary file from a dos filesystem
fatls   - list files in a directory (default /)
fdt     - flattened device tree utility commands
go      - start application at address 'addr'
help    - print command description/usage
iminfo  - print header information for application image
imxtract- extract a part of a multi-image
itest   - return true/false on integer compare
load    - load binary file from a filesystem
loadb   - load binary file over serial line (kermit mode)
loads   - load S-Record file over serial line
loadx   - load binary file over serial line (xmodem mode)
loady   - load binary file over serial line (ymodem mode)
loop    - infinite loop on address range
ls      - list files in a directory (default /)
md      - memory display
mii     - MII utility commands
mm      - memory modify (auto-incrementing address)
mtdparts- define flash/nand partitions
mw      - memory write (fill)
nand    - NAND sub-system
nboot   - boot from NAND device
nfs     - boot image via network using NFS protocol
nm      - memory modify (constant address)
ping    - send ICMP ECHO_REQUEST to network host
printenv- print environment variables
reset   - Perform RESET of the CPU
run     - run commands in an environment variable
saveenv - save environment variables to persistent storage
setenv  - set environment variables
setexpr - set environment variable as the result of eval expression
showvar - print local hushshell variables
sleep   - delay execution for some time
source  - run script from memory
test    - minimal test like /bin/sh
tftpboot- boot image via network using TFTP protocol
true    - do nothing, successfully
ubi     - ubi commands
ubifsload- load file from an UBIFS filesystem
ubifsls - list files in a directory
ubifsmount- mount UBIFS volume
ubifsumount- unmount UBIFS volume
usb     - USB sub-system
usbboot - boot from USB device
version - print monitor, compiler and linker version

One last note, I'm plugged in via a serial connection



Edited 2 time(s). Last edit at 06/15/2015 06:28PM by ubermacin.
Download the files you need (utilities and flash files) on a desktop machine running Windows or Linux. Put the files on a flash drive formatted to Fat32. On the plug, use busybox to create a directory in /tmp (i.e. mkdir /tmp/flashloc) and mount the flash drive to that location - usb start, mount /dev/sda1 /tmp/flashloc. Cd to /tmp/flashloc. Chmod a+x all the utility files. Then run all the suggested utilities preceding the commands with /tmp/flashloc/ example /tmp/flashloc/nandwrite ............

LeggoMyEggo's Google Plus Profile
Thank you Leggo! I really appreciate it, I can't believe I didn't think to try that. I'll report back

EDIT: Uggg, no busy box. I did try tftp and it does respond despite not being listed:

PogoE02> tftp -?
No link on egiga0



Edited 1 time(s). Last edit at 06/15/2015 10:23PM by ubermacin.
ubermacin,

u-boot does not have wget. And you can't install u-boot at u-boot prompt in a normal way as in Debian or Arch (different instructions is needed). The best way to install u-boot is to boot into Arch or Debian and start from there.

-bodhi
===========================
Forum Wiki
bodhi's corner
Hallo,

I haven't uses my DockStar for quiet a while but now I like to use it again.
So I decided to do a complete update (and start in this sence from scratch).

First of all thanks to all the contributors and especially to bodhi, to keep all the necessary things updated.

I updated to u-boot to 2014.07 according to this thread. I also used the uboot.2014.07-tld-2.environment.img to update and adopted the u-boot environment according to my system / environment.
I downloaded Debian-3.18.5-kirkwood-tld-1-rootfs-bodhi.tar.bz2 (also from bodhi) and followed the installation instructions and I also updated to the latest kernel 4.0.0. In principle everything works fine and I can boot to Debian Jessie.

Now my problem:
I also wanted to update the rescue system (to v 2.8.2). But there is no /dev/mtd1 or /dem/mtd2 anymore. From Debian
"cat /proc/mtd" shows:
mtd0: 10000000 00020000 "orion_nand"
"cat /proc/cmdline" shows:
console=ttyS0,115200 root=/dev/sda1 rootdelay=10 rootfstype=ext3 orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
Obvious mtd0 is to large. I have no idea why and where this happens. How can I recreate /dev/mtdx? I understood from some google-reading that this is passed as argument to the kernel?
Could you give me some advice? Any more information needed (serial connection to the box is also working)

Thanks
Pit
Pit,


>. From Debian
> "cat /proc/mtd" shows:
> mtd0: 10000000 00020000 "orion_nand"
> "cat /proc/cmdline" shows:
> console=ttyS0,115200 root=/dev/sda1 rootdelay=10
> rootfstype=ext3
> orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(dat
> a)

This was because your u-boot env for mtdparts was not defined correctly.

When you do cat /proc/cmdline, It should show:
mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)

It's a common error when you set the env for mtdparts. There are 2 mtdparts string.

fw_setenv mtdparts 'mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)'

So when you list it again, it should be
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)

-bodhi
===========================
Forum Wiki
bodhi's corner
Hallo,

it was in deed wrong. Thanks for the hint.

bodhi Wrote:
-------------------------------------------------------
>
> So when you list it again, it should be
>
> mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage)
> ,32M(rootfs),-(data)
>


But now I get the following error message

Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
mount: Invalid argument
Begin: Running /scripts/local-bottom ... done.
done.
Begin: Running /scripts/init-bottom ... mount: No such file or directory
done.
mount: No such file or directory
mount: No such file or directory
Target filesystem doesn't have requested /sbin/init.
No init found. Try passing init= bootarg.
(initramfs)

Is something else missing in the environment?`

DockStar> printenv
arcNumber=2998
baudrate=115200
bootcmd=run bootcmd_uenv; run bootcmd_usb; reset
bootcmd_mmc=run mmc_init; run set_bootargs_mmc; run mmc_boot
bootcmd_pogo=run bootcmd_rescue
bootcmd_rescue=run set_bootargs_rescue; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000
bootcmd_sata=run sata_init; run set_bootargs_sata; run sata_boot;
bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi
bootcmd_usb=run usb_init; run set_bootargs_usb; run usb_boot;
bootdelay=10
console=ttyS0,115200
device=0:1
devices=usb
ethact=egiga0
ethaddr=00:10:75:xxxxx
if_netconsole=ping $serverip
ipaddr=192.168.1.xx
led_error=orange blinking
led_exit=green off
led_init=green blinking
load_dtb=ext2load usb 0:1 0x1c00000 /boot/dts/kirkwood-dockstar.dtb
load_initrd=ext2load usb 0:1 0x1100000 /boot/uInitrd
load_uimage=ext2load usb 0:1 0x800000 /boot/uImage
mainlineLinux=yes
mmc_boot=mw 0x800000 0 1; run mmc_load_uimage; if run mmc_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
mmc_init=mmc rescan
mmc_load_uimage=ext2load mmc $device 0x800000 /boot/uImage
mmc_load_uinitrd=ext2load mmc $device 0x1100000 /boot/uInitrd
mmc_root=/dev/mmcblk0p1
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
partition=nand0,2
preboot_nc=run if_netconsole start_netconsole
rescue_bootcmd=if test $rescue_installed -eq 1; then run rescue_set_bootargs; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000; else run pogo_bootcmd; fi
rescue_installed=1
rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params
rootdelay=10
rootfstype=ext3
sata_boot=mw 0x800000 0 1; run sata_load_uimage; if run sata_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
sata_init=ide reset
sata_load_uimage=ext2load ide $device 0x800000 /boot/uImage
sata_load_uinitrd=ext2load ide $device 0x1100000 /boot/uInitrd
sata_root=/dev/sda1
serverip=192.168.1.40
set_bootargs_mmc=setenv bootargs console=$console root=$mmc_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
set_bootargs_rescue=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts
set_bootargs_sata=setenv bootargs console=$console root=$sata_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
set_bootargs_usb=setenv bootargs console=$console root=$usb_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
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_import=echo importing envs ...; env import -t 0x810000
uenv_init_devices=setenv init_usb "usb start"; 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 0x810000 /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 load_dtb; run load_uimage; if run load_initrd; then bootm 0x800000 0x1100000 0x1c00000; else bootm 0x800000 - 0x1c00000; fi
usb_device=0:1
usb_init=usb start
usb_load_uimage=ext2load usb $device 0x800000 /boot/uImage
usb_load_uinitrd=ext2load usb $device 0x1100000 /boot/uInitrd
usb_root=/dev/sda1
usb_rootfstype=ext3


Thanks for the support

Pit
Pit,

Something is missing in the bootargs, it's is hard to tell without seeing the kernel command line. Please post the entire serial boot log including the mount error above.

-bodhi
===========================
Forum Wiki
bodhi's corner
Bodhi,

thanks for your effort.
Here is the serial boot log:

U-Boot 2014.07-tld-2 (Sep 20 2014 - 01:10:10)
Seagate FreeAgent DockStar

SoC: Kirkwood 88F6281_A0
DRAM: 128 MiB
WARNING: Caches not enabled
NAND: 256 MiB
In: serial
Out: serial
Err: serial
Net: egiga0
88E1116 Initialized on egiga0
Hit any key to stop autoboot: 10

U-Boot 2014.07-tld-2 (Sep 20 2014 - 01:10:10)
Seagate FreeAgent DockStar

SoC: Kirkwood 88F6281_A0
DRAM: 128 MiB
WARNING: Caches not enabled
NAND: 256 MiB
In: serial
Out: serial
Err: serial
Net: egiga0
88E1116 Initialized on egiga0
Hit any key to stop autoboot: 0
(Re)start USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found

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

Part Start Sector Num Sectors UUID Type
1 2048 7346176 005b0e82-01 83
2 7348224 466944 005b0e82-02 82
loading envs from usb 0 ...
** File not found /boot/uEnv.txt **
(Re)start USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found
10180 bytes read in 1231 ms (7.8 KiB/s)
3048360 bytes read in 399 ms (7.3 MiB/s)
5400458 bytes read in 534 ms (9.6 MiB/s)
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Linux-4.0.0-kirkwood-tld-2
Created: 2015-06-16 7:47:24 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3048296 Bytes = 2.9 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
Image Name: initramfs-4.0.0-kirkwood-tld-2
Created: 2015-06-16 7:48:24 UTC
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 5400394 Bytes = 5.2 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 01c00000
Booting using the fdt blob at 0x1c00000
Loading Kernel Image ... OK
Loading Ramdisk to 075f7000, end 07b1d74a ... OK
Loading Device Tree to 075f1000, end 075f67c3 ... OK

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 4.0.0-kirkwood-tld-2 (root@tldDebian) (gcc version 4.9.1 (Debian 4.9.1-19) ) #1 PREEMPT Thu Apr 30 10:09:56 PDT 2015
[ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f
[ 0.000000] CPU: VIVT data cache, VIVT instruction cache
[ 0.000000] Machine model: Seagate FreeAgent Dockstar
[ 0.000000] Memory policy: Data cache writeback
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32512
[ 0.000000] Kernel command line: console=ttyS0,115200 root=/dev/sda1 rootdelay=10 rootfstype=ext3 mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
[ 0.000000] PID hash table entries: 512 (order: -1, 2048 bytes)
[ 0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[ 0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[ 0.000000] Memory: 115664K/131072K available (5799K kernel code, 386K rwdata, 2108K rodata, 284K init, 302K bss, 15408K reserved, 0K cma-reserved)
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
[ 0.000000] vmalloc : 0xc8800000 - 0xff000000 ( 872 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xc8000000 ( 128 MB)
[ 0.000000] modules : 0xbf000000 - 0xc0000000 ( 16 MB)
[ 0.000000] .text : 0xc0008000 - 0xc07c0e48 (7908 kB)
[ 0.000000] .init : 0xc07c1000 - 0xc0808000 ( 284 kB)
[ 0.000000] .data : 0xc0808000 - 0xc08689bc ( 387 kB)
[ 0.000000] .bss : 0xc08689bc - 0xc08b42fc ( 303 kB)
[ 0.000000] Preemptible hierarchical RCU implementation.
[ 0.000000] NR_IRQS:16 nr_irqs:16 16
[ 0.000016] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 21474836475ns
[ 0.000435] Console: colour dummy device 80x30
[ 0.000467] Calibrating delay loop... 1191.11 BogoMIPS (lpj=5955584)
[ 0.090116] pid_max: default: 32768 minimum: 301
[ 0.090239] Security Framework initialized
[ 0.090374] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.090397] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.091156] Initializing cgroup subsys blkio
[ 0.091188] Initializing cgroup subsys devices
[ 0.091211] Initializing cgroup subsys freezer
[ 0.091245] Initializing cgroup subsys net_cls
[ 0.091346] CPU: Testing write buffer coherency: ok
[ 0.091786] Setting up static identity map for 0x583128 - 0x583180
[ 0.092081] mvebu-soc-id: MVEBU SoC ID=0x6281, Rev=0x2
[ 0.096071] devtmpfs: initialized
[ 0.097932] prandom: seed boundary self test passed
[ 0.101742] prandom: 100 self tests passed
[ 0.101774] pinctrl core: initialized pinctrl subsystem
[ 0.106341] NET: Registered protocol family 16
[ 0.106819] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.130120] cpuidle: using governor ladder
[ 0.160119] cpuidle: using governor menu
[ 0.160544] Feroceon L2: Enabling L2
[ 0.160591] Feroceon L2: Cache support initialised.
[ 0.160972] [Firmware Info]: /ocp@f1000000/ethernet-controller@72000/ethernet0-port@0: local-mac-address is not set
[ 0.165324] No ATAGs?
[ 0.201618] vgaarb: loaded
[ 0.201998] usbcore: registered new interface driver usbfs
[ 0.202080] usbcore: registered new interface driver hub
[ 0.202145] usbcore: registered new device driver usb
[ 0.203244] Switched to clocksource orion_clocksource
[ 0.240053] NET: Registered protocol family 2
[ 0.240807] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.240834] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.240854] TCP: Hash tables configured (established 1024 bind 1024)
[ 0.240923] TCP: reno registered
[ 0.240937] UDP hash table entries: 256 (order: 0, 4096 bytes)
[ 0.240962] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[ 0.241151] NET: Registered protocol family 1
[ 0.241540] RPC: Registered named UNIX socket transport module.
[ 0.241553] RPC: Registered udp transport module.
[ 0.241560] RPC: Registered tcp transport module.
[ 0.241567] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.241868] Unpacking initramfs...
[ 0.726395] Freeing initrd memory: 5276K (c75f7000 - c7b1e000)
[ 0.726529] NetWinder Floating Point Emulator V0.97 (double precision)
[ 0.727851] futex hash table entries: 256 (order: -1, 3072 bytes)
[ 0.727881] Initialise system trusted keyring
[ 0.727988] audit: initializing netlink subsys (disabled)
[ 0.728043] audit: type=2000 audit(0.720:1): initialized
[ 0.728847] zpool: loaded
[ 0.728863] zbud: loaded
[ 0.729162] VFS: Disk quotas dquot_6.5.2
[ 0.729226] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 0.729846] NFS: Registering the id_resolver key type
[ 0.729906] Key type id_resolver registered
[ 0.729916] Key type id_legacy registered
[ 0.729942] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[ 0.729957] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[ 0.730177] jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
[ 0.730645] Key type big_key registered
[ 0.733621] alg: No test for stdrng (krng)
[ 0.733665] Key type asymmetric registered
[ 0.733683] Asymmetric key parser 'x509' registered
[ 0.733772] bounce: pool size: 64 pages
[ 0.733866] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[ 0.733887] io scheduler noop registered
[ 0.733901] io scheduler deadline registered
[ 0.733956] io scheduler cfq registered (default)
[ 0.735280] kirkwood-pinctrl f1010000.pin-controller: registered pinctrl driver
[ 0.735945] irq: Cannot allocate irq_descs @ IRQ32, assuming pre-allocated
[ 0.736370] irq: Cannot allocate irq_descs @ IRQ64, assuming pre-allocated
[ 0.736907] mv_xor f1060800.xor: Marvell shared XOR driver
[ 0.773325] mv_xor f1060800.xor: Marvell XOR: ( xor cpy )
[ 0.813310] mv_xor f1060800.xor: Marvell XOR: ( xor cpy )
[ 0.813502] mv_xor f1060900.xor: Marvell shared XOR driver
[ 0.853308] mv_xor f1060900.xor: Marvell XOR: ( xor cpy )
[ 0.893308] mv_xor f1060900.xor: Marvell XOR: ( xor cpy )
[ 0.893739] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[ 0.895123] console [ttyS0] disabled
[ 0.895187] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 26, base_baud = 12500000) is a 16550A
[ 1.491455] console [ttyS0] enabled
[ 1.496248] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
[ 1.502629] nand: Micron MT29F2G08AAD
[ 1.506347] nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[ 1.513985] Scanning device for bad blocks
[ 1.674966] 4 cmdlinepart partitions found on MTD device orion_nand
[ 1.681258] Creating 4 MTD partitions on "orion_nand":
[ 1.686445] 0x000000000000-0x000000100000 : "u-boot"
[ 1.691865] 0x000000100000-0x000000500000 : "uImage"
[ 1.697270] 0x000000500000-0x000002500000 : "rootfs"
[ 1.702692] 0x000002500000-0x000010000000 : "data"
[ 1.709140] libphy: Fixed MDIO Bus: probed
[ 1.713598] libphy: orion_mdio_bus: probed
[ 1.724847] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[ 2.804084] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address 00:10:75:1a:bf:85
[ 2.813103] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 2.819725] ehci-pci: EHCI PCI platform driver
[ 2.824279] ehci-orion: EHCI orion driver
[ 2.828487] orion-ehci f1050000.ehci: EHCI Host Controller
[ 2.834055] orion-ehci f1050000.ehci: new USB bus registered, assigned bus number 1
[ 2.841907] orion-ehci f1050000.ehci: irq 29, io mem 0xf1050000
[ 2.863281] orion-ehci f1050000.ehci: USB 2.0 started, EHCI 1.00
[ 2.869560] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 2.876409] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 2.883681] usb usb1: Product: EHCI Host Controller
[ 2.888581] usb usb1: Manufacturer: Linux 4.0.0-kirkwood-tld-2 ehci_hcd
[ 2.895243] usb usb1: SerialNumber: f1050000.ehci
[ 2.900710] hub 1-0:1.0: USB hub found
[ 2.904561] hub 1-0:1.0: 1 port detected
[ 2.909390] mousedev: PS/2 mouse device common for all mice
[ 3.223307] usb 1-1: new high-speed USB device number 2 using orion-ehci
[ 3.374913] usb 1-1: New USB device found, idVendor=05e3, idProduct=0608
[ 3.381665] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[ 3.388872] usb 1-1: Product: USB2.0 Hub
[ 3.393757] hub 1-1:1.0: USB hub found
[ 3.397912] hub 1-1:1.0: 4 ports detected
[ 3.683665] usb 1-1.4: new high-speed USB device number 3 using orion-ehci
[ 3.885537] usb 1-1.4: New USB device found, idVendor=054c, idProduct=02a5
[ 3.892456] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3.899837] usb 1-1.4: Product: Storage Media
[ 3.904234] usb 1-1.4: Manufacturer: Sony
[ 3.908261] usb 1-1.4: SerialNumber: 9B20011000000000
[ 3.923275] rtc-mv f1010300.rtc: internal RTC not ticking
[ 3.928926] i2c /dev entries driver
[ 3.933736] hidraw: raw HID events driver (C) Jiri Kosina
[ 3.939543] drop_monitor: Initializing network drop monitor service
[ 3.946129] TCP: cubic registered
[ 3.949469] NET: Registered protocol family 17
[ 3.954102] Key type dns_resolver registered
[ 3.959263] Loading compiled-in X.509 certificates
[ 3.964137] registered taskstats version 1
[ 3.969238] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[ 3.977919] Freeing unused kernel memory: 284K (c07c1000 - c0808000)
Loading, please wait...
[ 4.033813] udev[57]: starting version 164
[ 4.442758] SCSI subsystem initialized
[ 4.451263] usb-storage 1-1.4:1.0: USB Mass Storage device detected
[ 4.457915] usb-storage 1-1.4:1.0: Quirks match for vid 054c pid 02a5: 80000
[ 4.465206] scsi host0: usb-storage 1-1.4:1.0
[ 4.471171] usbcore: registered new interface driver usb-storage
[ 4.480111] usbcore: registered new interface driver uas
[ 5.652025] scsi 0:0:0:0: Direct-Access Sony Storage Media 0100 PQ: 0 ANSI: 0 CCS
[ 5.674977] sd 0:0:0:0: [sda] 7815168 512-byte logical blocks: (4.00 GB/3.72 GiB)
[ 5.683473] sd 0:0:0:0: [sda] Write Protect is off
[ 5.688947] sd 0:0:0:0: [sda] No Caching mode page found
[ 5.694353] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 5.706687] sda: sda1 sda2
[ 5.713198] sd 0:0:0:0: [sda] Attached SCSI removable disk
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
mount: Invalid argument
Begin: Running /scripts/local-bottom ... done.
done.
Begin: Running /scripts/init-bottom ... mount: No such file or directory
done.
mount: No such file or directory
mount: No such file or directory
Target filesystem doesn't have requested /sbin/init.
No init found. Try passing init= bootarg.
(initramfs)
Appolgies from my side.
I have used an other USB Stick with the same content but formated with ext2. After converting to ext3 everything works fine.

Thanks again
Pit
Pit,

Cool.
> Appolgies from my side.
No need to!

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: 2014.07 NSA320 Error: unrecognized/unsupported machine ID (r1 = 0x00000f74
June 28, 2015 11:22AM
Hello,
i have a NSA320 and a while ago i succesfully (kind of ) installed the 2011.12 uboot and 3.17 Linux.
Only the USB didnt work and i wrote for help about it here: http://forum.doozan.com/read.php?2,19251,19251#msg-19251

I did not succeed in solving the Problems, dont remember what i tried exactly.
Then i put it away for some months, and want to give it a new start now.

I have netconsole (on my macbook terminal , nc -klu 6666 worked best for me) and serial line hooked up via minicom or coolterm.

First , i had an error
 ** ext2fs_devread() read outside partition sector
i fixed this by tar'ing the HD's content, making a new part scheme with a 3GB ext2 primary partition named "rootfs" again, and untaring the aformentioned contents there. The rest of the HD and the second drive slot may stay empty for now.
I also made an USB Flash Stick with the same filesystem and contents.
When i boot now, i get this in the netconsole:
U-Boot 2011.12 (May 03 2012 - 17:04:23)
ZyXEL NSA320 2-Bay Power Media Server
arm-none-linux-gnueabi-gcc (Sourcery G++ Lite 2009q3-67) 4.4.1
GNU ld (Sourcery G++ Lite 2009q3-67) 2.19.51.20090709
Hit any key to stop autoboot:  0

Reset IDE: Bus 0: OK Bus 1: not available
  Device 0: Model: WDC WD20EARS-00MVWB0 Firm: 51.0AB51 Ser#:  WD-WCAZA7723695
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 1907729.0 MB = 1863.0 GB (-387938128 x 512)
Loading file "/boot/uImage" from ide device 0:1 (hda1)
2822232 bytes read
Loading file "/boot/uInitrd" from ide device 0:1 (hda1)
6114335 bytes read
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-3.17.0-kirkwood-tld-1
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2822168 Bytes = 2.7 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-3.17.0-kirkwood-tld-1
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    6114271 Bytes = 5.8 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...
and then the serial console logs(i removed some whitespace):
Uncompressing Linux... done, booting the kernel.
Error: unrecognized/unsupported machine ID (r1 = 0x00000f74).
Available machine support:
ID (hex).NAME
ffffffff.Generic DT based system
ffffffff.Marvell Kirkwood (Flattened Device Tree)
Please check your kernel config and/or bootloader.

This is the environment:
NSA320> printenv
printenv
arcNumber=3956
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 /boot/uImage; ext2load ide 0:1 0x01100000 /boot/uInitrd; bootm 0x00800000 0x01100000
boot_sata2=mw 0x800000 0 1; setenv bootargs console=ttyS0,115200 root=/dev/sdb1 rootdelay=10 $mtdparts; ide reset; ext2load ide 1:1 0x800000 /boot/uImage; ext2load ide 1:1 0x01100000 /boot/uInitrd; bootm 0x00800000 0x01100000
bootcmd=run boot_sata1; run boot_sata2; run bootcmd_usb; usb stop; run bootcmd_rescue; reset
bootcmd_usb=run usb_init; run usb_load_uimage; run set_bootargs_usb; run usb_boot;
bootdelay=10
console=ttyS0,115200
ethact=egiga0
ethaddr=b0:b2:dc:ee:d4:f2
if_netconsole=ping $serverip
ipaddr=10.9.1.208
mainlineLinux=yes
mtddevname=key_store
mtddevnum=2
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),512K(uboot_env),512K(key_store),512K(info),10M(etc),10M(kernel_1),48896K(rootfs1),10M(kernel_2),-(rootfs2)
ncip=10.9.1.200
netmask=255.255.255.0
partition=nand0,2
preboot=run if_netconsole start_netconsole
serverip=10.9.1.200
set_bootargs_usb=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=nc
stdin=nc
stdout=nc
usb_boot=if ext2load usb $usb_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000;else bootm 0x800000;fi;
usb_device=0:1
usb_init=usb start
usb_load_uimage=mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage
usb_root=LABEL=USBROOT
usb_rootdelay=10
usb_rootfstype=ext2

Environment size: 1759/131068 bytes

How do i solve this error?
did i miss an important file?
The tar /untar commands didnt throw errors...
I would also like to install a 4.xx kernel. and maybe also latest uboot, if required.
I understand from your posting, that all the commandline stuff runs on the actual system,
but i am stuck with the minimal (maybe busybox?) shell at the "nsa320>" prompt.
How and where do i enter the correct info?
Yours sincerely

Dirk

2 Pieces NSA320 , u-boot 2016.05, debian 4.12.1, Several Mac and Linux boxes connected.
More into soldering than programming. Location:Hildesheim, Germany



Edited 1 time(s). Last edit at 06/28/2015 11:39AM by shivahoj.
Re: 2014.07 NSA320 Error: unrecognized/unsupported machine ID (r1 = 0x00000f74
June 28, 2015 01:04PM
Dirk,

You're running u-boot 2011.12 which does not support FDT kernel booting the normal way. So to run kernel or rootfs 3.17.0-kirkwood-tld-1, you need to append the NSA320 DTB file to the uImage.

In the instruction for kernel 3.17, this step stated:

Quote

4b. Boot with DTB file embedded in the kernel image (no U-Boot envs change needed)

Generate the uImage and uInitrd:
cd /boot
cp -a zImage-3.17.0-kirkwood-tld-1 zImage.fdt
cat dts/kirkwood-goflexnet.dtb >> zImage.fdt
mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-3.17.0-kirkwood-tld-1 -d /boot/zImage.fdt /boot/uImage
mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-3.17.0-kirkwood-tld-1 -d /boot/initrd.img-3.17.0-kirkwood-tld-1 /boot/uInitrd

You should mount this USB rootfs on a different Linux box and regenerate uImage.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: 2014.07 NSA320 Error: unrecognized/unsupported machine ID (r1 = 0x00000f74
June 28, 2015 02:18PM
Thanks a lot, that did help!
wonderful!
And i even remembered my root password...

One strange thing: i tried your "4b" solution on the USB flash stick first, but it couldnt find the root filesystem(as i think of it now, not THAT strange). T hen i copied the entire /boot folder to the harddisk, and there it worked.

Now i can go and try to upgrade to the latest kernel.
Do i need to upgrade to a newer uboot as well?

Anyway, a BIG thanks to the swift response.

Dirk
Re: 2014.07 NSA320 Error: unrecognized/unsupported machine ID (r1 = 0x00000f74
June 28, 2015 04:16PM
Dirk,

> One strange thing: i tried your "4b" solution on
> the USB flash stick first, but it couldnt find the
> root filesystem(as i think of it now, not THAT
> strange). T hen i copied the entire /boot folder
> to the harddisk, and there it worked.

Because the instruction was written for installing kernel on a live system. If you mount the USB on a different machine, /boot in the above needed to be adjusted to be under the mount point, for example if the mountpoint is /media/sdb1, then:
/media/sdb1/boot
I've updated the instruction slightly to take that into account in later kernel release (i.e. 3.18, 4.0), but did not update previous one.

> Do i need to upgrade to a newer uboot as well?

It is recommended, because sooner or later you will need modern features that the newer u-boot provides (see the description). But you can always postpone until you actually need to do that.

-bodhi
===========================
Forum Wiki
bodhi's corner
NSA320 uboot and debian success, some last thoughts...
July 10, 2015 03:40PM
OK, i successfully tried to update to latest u-boot, and kernel.
Now, everything works just fine, even the USB Ports...
I changed the /etc.rc.local to include the following right at the top:
echo heartbeat  >/sys/class/leds/nsa320:orange:sys/trigger
echo usb-host   > /sys/class/leds/nsa320:green:usb/trigger
echo ide-disk1  > /sys/class/leds/nsa320:green:hdd1/trigger
echo ide-disk2  > /sys/class/leds/nsa320:green:hdd2/trigger
Is there a reason why this isnt enabled by default?
I would like to blink the HDD LEDs in red, when i run smartctl via cron script at night, and it exits nonzero.
Has anybody already set up a script? Shouldn't be too hard, maybe i'll do it myself, and post it here.
Also i would like to hook up a small (low power) beeper instead of the red copy LED, which then could to give me an audible feedback, like this:
echo timer  > /sys/class/leds/nsa320:red:copy/trigger
When i just installed munin-node(to report system internals to some other linux box), i found that the folder /sys/class/hwmon is empty, and sensors-detect (run as root) from the package lm-sensors doesnt find any sensors.
Do i need to install something else(other than lm-sensors)?
BTW, Davygravy wrote in an older posting(here), that this worked for him.

2 Pieces NSA320 , u-boot 2016.05, debian 4.12.1, Several Mac and Linux boxes connected.
More into soldering than programming. Location:Hildesheim, Germany



Edited 1 time(s). Last edit at 07/10/2015 03:44PM by shivahoj.
Re: NSA320 uboot and debian success, some last thoughts...
July 10, 2015 06:02PM
@shivahoj,

> Is there a reason why this isnt enabled by
> default?

No particular reason at all. They just have not been taken care of, due to no user's request! I guess others always set them in rc.local and did not bother request me to put the default LED states in the kernel. Agree, they should have been defaulted to somthing.

> When i just installed munin-node(to report system
> internals to some other linux box), i found that
> the folder /sys/class/hwmon is empty, and
> sensors-detect (run as root) from the package
> lm-sensors doesnt find any sensors.
> Do i need to install something else(other than
> lm-sensors)?

The NSA3xx hwmon module was missing in this version due to kernel code change that I was not aware of. I've incorporated this module back in Kernel 4.0.0-kirkwood-tld-1.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: NSA320 uboot and debian success, some last thoughts...
July 10, 2015 11:19PM
Then there someting else is wrong, because i have installed
root@zyxie:/sys/devices/platform/gpio_keys/input# uname -a
Linux zyxie 4.1.0-kirkwood-tld-1 #2 PREEMPT Sun Jun 28 01:12:41 PDT 2015 armv5tel GNU/Linux
, it should work then. Maybe something else is wrong?
Re: NSA320 uboot and debian success, some last thoughts...
July 11, 2015 01:34AM
Was the module running?
lsmod
if nsa3xx-hwmon is not in the list then
modprobe nsa3xx-hwmon

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: NSA320 uboot and debian success, some last thoughts...
July 11, 2015 01:25PM
Hi,

in the newer devicetree enabled linux kernels from linux-3.18.5 onwards, the hwmon nsa3xx module for the NSA320
is not working, because the gpio pins 14, 16, 17 which are the relevant gpios for the

pmx_mcu_data,
pmx_mcu_clk,
pmx_mcu_act

signals of the mcu are not exposed outside via compatible descriptions to the nsa3xx driver, see kirkwood-nsa320.dts,..

I have looked into that already, but did not find any suitable documentation of devicetree
bindings for this special case,where an hwmon capable mcu is connected to gpio's,
and not - as it is the normal way - is connected via i2c bus,...

so without that, the nsa3xx hwmon kernel module will simply never!! work again,
meaning the compatible descriptions in the devicetree implementation for nsa320
are simply not defined by the dts devs of the linux kernel,

see: http://lists.infradead.org/pipermail/linux-arm-kernel/2014-April/245202.html

as this has been asked several times in this forum a quote from this link clarifies the situation:

This DTS just describes the features that
 work with the current kernel drivers. New drivers still
 need writing to support the temperature sensor, the
 power on behaviour control and the buzzer

so it will not be working until somebody finds a solution how to expose the gpios to the
nsa3xx hwmon module in kirkwood-nsa320.dts in the same way as it was functioning in
nsa320-setup.c from peter schildmann for nsa3xx-hwmon before linux kernels 3.16,..

see also here: http://forum.doozan.com/read.php?2,16532,22608#msg-22608

and here: http://forum.doozan.com/read.php?2,12096,22263#msg-22263


best wishes pbg4



Edited 2 time(s). Last edit at 07/11/2015 01:37PM by pbg4.
Re: NSA320 uboot and debian success, some last thoughts...
July 11, 2015 01:38PM
@pbg4,

Thanks for the information, again :) I remember you've reported this problem before but somehow it never got on my Todo list. I will look into this. Perhaps we can incorporate the old setup into the new kernel.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: NSA320 uboot and debian success, some last thoughts...
July 11, 2015 10:02PM
@pbg4,

On second thought, I recall now that you've said you might give it a try in fixing this hwmon (I think that's why it was under my radar :)
http://forum.doozan.com/read.php?2,12096,22263#msg-22263

Will you have free time to look into this? or do you need more help?

PS.

Looking at this : http://forum.doozan.com/read.php?2,16532,22608#msg-22608 . Perhaps if the hwmon driver patch is too drastic, we could instead add a patch in kirkwood GPIO to only do this for NSA320 (i.e. CONFIG_SENSORS_NSA3XX)? I know it's not as nice, but it'll work around it without a script.

-bodhi
===========================
Forum Wiki
bodhi's corner



Edited 2 time(s). Last edit at 07/11/2015 10:36PM by bodhi.
Re: NSA320 uboot and debian success, some last thoughts...
July 12, 2015 03:22AM
Hi bodhi,

perhaps it is best to give an example what should be done in kirkwood-nsa320.dts,

in devicetree nomenclature it should be as simple as that code snippet below,
that would be all that is to be done basically, to get nsa3xx-hwmon going,
(beware, the code snippet is just an example of how it should be done, it will not work!!)

however: ----> there is no compatible description for gpio-hwmon,...

in order to get this upstream, we will perhaps have to contact one
of the linux devs, e.g. shesselba who cares for the armada stuff, and kirkwood pincntrl, etc. I have written an email
to him, let's see if he reacts and if he can help us,

all the definitions which are available are in linux-4.1/Documentation/devicetree/bindings but you
will not find anything usefull for a hwmon capable mcu which is connected to gpio's and not i2c, there are descriptions for thermal sensors, but they don't fit either,..

but maybe there are more opinions on that issue here in the forum,

best wishes pbg4

        nsa3xx-hwmon {
                compatible = "gpio-hwmon;
                pinctrl-0 = <&pmx_mcu_data &pmx_mcu_clk &pmx_mcu_act>;
                pinctrl-names = "default";

                mcu-data {
                        gpios = <&gpio1 14 GPIO_ACTIVE_HIGH>;
                };

                mcu-clk {
                        gpios = <&gpio0 16 GPIO_ACTIVE_HIGH>;
                };

                mcu-act {
                        gpios = <&gpio0 17 GPIO_ACTIVE_HIGH>;
                };
        };



Edited 3 time(s). Last edit at 07/12/2015 05:49AM by pbg4.
Re: NSA320 uboot and debian success, some last thoughts...
July 12, 2015 12:37PM
@ pbg4,

Adding a DTS device is not difficult, as you've just illustrated. The time consuming part is to test and fix any error. I don't have the NSA320 box so I would rely on you :)

-bodhi
===========================
Forum Wiki
bodhi's corner
Hello,
I have a E02 pink pogo and like many others I tried with Archlinux tutorial on http://archlinuxarm.org/platforms/armv5/pogoplug-v2-pinkgray.
Now I have only access to alarm on flash stick and only two mtd partitions visible (mtd0 and mtd1). Can I proceed with doozan uboot installation from Arch and what else needs to be done to be able to boot to original pogo software without attached flash memory? What about environment variables?
I have already install wget with pacman.

edit: also no bad blocks

edit: Is it enough http://archlinuxarm.org/forum/viewtopic.php?f=58&t=7558&start=10#p41522 ?



Edited 2 time(s). Last edit at 07/12/2015 01:24PM by miksi.
@miksi,

> Can I proceed with doozan uboot installation from
> Arch

No, Jeff's u-boot is too old. You'll need to install my latest u-boot build in the first post of this thread.

> and what else needs to be done

See this post at Arch site for how to migrate from Arch u-boot (or search this forum for user TEN posts):
http://archlinuxarm.org/forum/viewtopic.php?f=30&p=46069#p46069

PS.

Regarding original Pogo OS: You will need to get the orginal NAND images from others here and restore them. It seems Arch installation has some how corrupted the orginal OS (unintentionnally of course), according to TEN.

-bodhi
===========================
Forum Wiki
bodhi's corner



Edited 3 time(s). Last edit at 07/12/2015 02:32PM by bodhi.
Re: NSA320 uboot and debian success, some last thoughts...
July 12, 2015 02:59PM
Hello,
i would gladly offer my NSA320 to test any upcoming software development.
I have two of them(one in Zyxels original firmware version, one with latest Uboot and Kernel). I still want to try to download and save first one's MTD contents, check the possibility of re-installation, and then also flash it to latest Uboot and Kernel.
Maybe i could speed up this process(maybe 'til tomorrow evening) and then send one of the boxes over to you, or give you ssh access to the box.
Or you could send me instructions, on how to test new software versions.
If you are interested, drop me a line, i will send you my contact details via PM.

Dirk

2 Pieces NSA320 , u-boot 2016.05, debian 4.12.1, Several Mac and Linux boxes connected.
More into soldering than programming. Location:Hildesheim, Germany
Re: NSA320 uboot and debian success, some last thoughts...
July 12, 2015 04:23PM
Hi Dirk,

Thanks for the offer. But let's hold off, I think it's best for pbg4 to give it a try first, I have high confidence in pbg4 to produce a good patch.

-bodhi
===========================
Forum Wiki
bodhi's corner
bodhi Wrote:
-------------------------------------------------------
> @miksi,
>
> > Can I proceed with doozan uboot installation
> from
> > Arch
>
> No, Jeff's u-boot is too old. You'll need to
> install my latest u-boot build in the first post
> of this thread.
>
> > and what else needs to be done
>
> See this post at Arch site for how to migrate from
> Arch u-boot (or search this forum for user TEN
> posts):
> http://archlinuxarm.org/forum/viewtopic.php?f=30&p
> =46069#p46069
>
> PS.
>
> Regarding original Pogo OS: You will need to get
> the orginal NAND images from others here and
> restore them. It seems Arch installation has some
> how corrupted the orginal OS (unintentionnally of
> course), according to TEN.

First, Thanks for support.
Also, I want to clear things up. My expectations from pogo is to connecting audio DAC to it and stream music from wherever is possible.
But I wouldn't give up on pogo's original software, so I prefer not to touch mtd1 if possible.

This is what I did next:
fw_setenv mtdparts 'mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)'

rebooted and now I can see mtd0-mtd3:
[root@alarm /]# fw_printenv mtdparts
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)

I'm trying to follow flashing instruction on http://forum.doozan.com/read.php?3,12381.

[root@alarm /]# cat /etc/fw_env.config
# Configuration file for fw_(printenv/saveenv) utility.
# Up to two entries are valid, in this case the redundant
# environment sector is assumed present.
# Notice, that the "Number of sectors" is ignored on NOR.

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

[root@alarm /]# cat /proc/mtd
dev: size erasesize name
mtd0: 00100000 00020000 "u-boot"
mtd1: 00400000 00020000 "uImage"
mtd2: 02000000 00020000 "rootfs"
mtd3: 05b00000 00020000 "data" # red digit is where it differs from your post

But you also stated that This assumes that your plug has been installed with Jeff's official installation script.
I didn't do that. Can I proceed with running Jeff's official install script with option --no boot check?
Can I presume that Jeff's script installs uboot and different environment variables in NAND?

Thanks again.
miksi,

> But you also stated that This assumes that your
> plug has been installed with Jeff's official
> installation script
.
> I didn't do that. Can I proceed with running
> Jeff's official install script with option --no
> boot check?
> Can I presume that Jeff's script installs uboot
> and different environment variables in NAND?
>

There is no need to do this intermediate step (this instruction was written before Arch u-boot was released).

Since you have latest Arch U-boot for Pogo E0, you can install my u-boot image and then flash the default u-boot envs following the installation instruction.

Jeff/davygravy u-boot, Arch u-boot, and my u-boot images all use the same location for u-boot envs. But the envs are defined differently.

So basically you need to perform every step in the installation instruction.

-bodhi
===========================
Forum Wiki
bodhi's corner



Edited 1 time(s). Last edit at 07/13/2015 04:27PM by bodhi.
Author:

Your Email:


Subject:


Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: