Welcome! Log In Create A New Profile

Advanced

NSA 325 V2 Debian Is Possible!

Posted by Buttzy10169 
Re: NSA 325 V2 Debian Is Possible!
January 03, 2014 03:52PM
I actualy did not think to check for a jtag connection on mine. best to see if you can get uart booting to work first there is a thread on this forum about uart booting and how far I got is above in this thread perhaps you will have better luck?
Re: NSA 325 V2 Debian Is Possible!
January 06, 2014 08:02AM
Another option is chain loading for testing purposes. You'll want to have it boot at least once to disable the watchdog while you sort out testing anyways.
marcin
Re: NSA 325 V2 Debian Is Possible!
February 18, 2014 05:58PM
USB 0: host mode
        [BlueDBG] reseting SoC Pex[0]  0 ...
PEX 0: PCI Express Root Complex Interface
PEX interface detected Link X1
        [BlueDBG] reseting SoC Pex[1]  0 ...
        [BlueDBG] reseting SoC Pex[1]  1 ...
        [BlueDBG] reseting SoC Pex[1]  2 ...
        [BlueDBG] reseting SoC Pex[1]  3 ...
        [BlueDBG] reseting SoC Pex[1]  4 ...
        [BlueDBG] reseting SoC Pex[1]  5 ...
        [BlueDBG] reseting SoC Pex[1]  6 ...
        [BlueDBG] reseting SoC Pex[1]  7 ...
        [BlueDBG] reseting SoC Pex[1]  8 ...
        [BlueDBG] reseting SoC Pex[1]  9 ...
        [BlueDBG] reseting SoC Pex[1]  10 ...
PEX 1: interface detected no Link.
Net:   egiga0 [PRIME]
Hit any key to stop autoboot:  0 
(Re)start USB...
USB:   scanning bus for devices... 3 USB Device(s) found
Waiting for storage device(s) to settle before scanning...
T

and cursor is blinking ,... nothing happens ...

after some time there is another fragment of output:

T Device NOT ready
   Request Sense returned 00 00 00
1 Storage Device(s) found
** Bad partition 1 **
** Bad partition 1 **
## Booting image at 02000000 ...
Bad Magic Number
Marvell>>


unable to boot to original firmware. ...whats wrong ?

I have pendrive with two partitions:
sda1 - fat32 with unpacked from: usb-debian-uboot.tar.gz
sda2 - ext2 with unpacked kirkwood as described in http://forum.doozan.com/read.php?2,12096
marcint43
Re: NSA 325 V2 Debian Is Possible!
February 18, 2014 06:02PM
I have serial console.

PRODUCT_NAME=NSA-325v2

(...)
run_diag=yes
console=console=ttyS0,115200 mtdparts=nand_mtd:0xc0000@0(uboot)ro,0x7f00000@0x100000(root)
ethprime=egiga0
bootargs_root=root=/dev/nfs rw
bootargs_end=:::DB88FXX81:eth0:none
image_name=uImage
standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneConfig); bootm 0x2000000;

(...)
bootargs_stock=console=ttyS0,115200 mtdparts=nand_mtd:0x100000(uboot),0x80000(uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(rootfs1),0xA00000(kernel_2),0x2F
C0000(rootfs2) root=/dev/nfs rw init=/init
bootargs_linux=console=ttyS0,115200 mtdparts=nand_mtd:0x100000(uboot),0x80000(uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(rootfs1),0xA00000(kernel_2),0x2F
C0000(rootfs2) root=LABEL=rootfs loglevel=8
bootcmd_linux=setenv bootargs $(bootargs_linux); mw.l f1010100 0020c000; usb reset; ext2load usb 0:1 $(loadaddr) /uImage; ext2load usb 0:1 0x01100000 /uInitrd; bootm $(loadaddr) 0x01100000
bootcmd_stock=setenv bootargs $(bootargs_stock); nand read.e $(loadaddr) $(kernel_addr) 0xA00000; bootm $(loadadr)
to_stock=setenv mainlineLinux no; setenv bootcmd \'run bootcmd_stock\'; saveenv; reset
to_linux=setenv mainlineLinux yes; setenv bootcmd \'run bootcmd_linux\'; saveenv; reset
bootcmd='run bootcmd_linux'

stdin=serial
stdout=serial
stderr=serial
mainlineLinux=yes

kernel_addr=0x4640000
pcieTune=no
pcieTune1=no
bootargs=console=ttyS0,115200 mtdparts=nand_mtd:0x100000(uboot),0x80000(uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(rootfs1),0xA00000(kernel_2),0x2FC0000(
rootfs2) root=LABEL=rootfs loglevel=8

Environment size: 2499/131068 bytes
Marvell>> 

Re: NSA 325 V2 Debian Is Possible!
February 18, 2014 06:08PM
You setup your usb device wrong. you have a fat32 partition and uboot is trying to load files from it but for 1 the files arent there and 2 its looking at the wrong partition you need to follow the instructions properly.

first partition is boot partition it should contain the files from the boot directory and be ext2.

then the second partition should be the root and labeled rootfs.



Edited 1 time(s). Last edit at 02/18/2014 06:10PM by Buttzy10169.
marcint43
Re: NSA 325 V2 Debian Is Possible!
February 18, 2014 06:10PM
of course: sda2 has label=rootfs

When I try to go back to previous state I have:

Marvell>> run bootcmd_stock

NAND read: device 0 offset 0x4640000, size 0xa00000

Reading data from 0x503f800 -- 100% complete.
 10485760 bytes read: OK
## Booting image at 02000000 ...
   Image Name:   Linux-2.6.31.8
   Created:      2013-08-22   9:04:41 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    5754856 Bytes =  5.5 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux..................................................................................................................................................................................
............................................................................................ done, booting the kernel.


console is frozen...nothing happens, no keyboard available...
Re: NSA 325 V2 Debian Is Possible!
February 18, 2014 06:14PM
Again your not following the instructions your trying to load stock firmware thats just not there. you shouldnt be typeing anything in there just reset and let it boot.

But it wont boot because your partions are wrong.
marcint43
Re: NSA 325 V2 Debian Is Possible!
February 18, 2014 06:36PM
Ok, lets again,

Partitions on my pendrive:

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *          32      391167      195568   83  Linux
/dev/sda2          391168     4587519     2098176   83  Linux

?

first - sda1 = ext2 -> bootable -> content:
boot  lost+found

sda2 -> ext4, content:
bin  dev  etc  home  initrd.img  lib  lost+found  media  mnt  opt  proc  root  run  sbin  selinux  srv  sys  tmp  usr  var  vmlinuz

linuxbox# cat sda2/etc/fstab
# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
/dev/sda2      /               ext4    noatime,errors=remount-ro 0 1
tmpfs          /tmp            tmpfs   defaults          0       0


still:
        [BlueDBG] reseting SoC Pex[1]  7 ...
        [BlueDBG] reseting SoC Pex[1]  8 ...
        [BlueDBG] reseting SoC Pex[1]  9 ...
        [BlueDBG] reseting SoC Pex[1]  10 ...
PEX 1: interface detected no Link.
Net:   egiga0 [PRIME]
Hit any key to stop autoboot:  0 
(Re)start USB...
USB:   scanning bus for devices... 3 USB Device(s) found
Waiting for storage device(s) to settle before scanning...
T Device NOT ready
   Request Sense returned 00 00 00
1 Storage Device(s) found
** Bad partition 1 **
** Bad partition 1 **
## Booting image at 02000000 ...
Bad Magic Number
Marvell>> 
marcint43
Re: NSA 325 V2 Debian Is Possible!
February 18, 2014 06:50PM
I moved files from boot directory - directly to partition...

# ls -l sda1/
-rw-r--r-- 1 root root  121807 lut  4 11:45 config-3.13.1-kirkwood-tld-2
-rw-r--r-- 1 root root 6568002 lut  5 20:30 initrd.img-3.13.1-kirkwood-tld-2
drwx------ 2 root root   12288 lut 19 02:17 lost+found
-rw-r--r-- 1 root root 1698808 lut  4 15:20 System.map-3.13.1-kirkwood-tld-2
-rw-r--r-- 1 root root 2399792 lut  5 20:30 uImage
-rw-r--r-- 1 root root 6568066 lut  5 20:31 uInitrd
-rw-r--r-- 1 root root 2399728 lut  4 15:20 vmlinuz-3.13.1-kirkwood-tld-2

..no results, the same error :(

Please help me, and thanks in advance.
Re: NSA 325 V2 Debian Is Possible!
February 18, 2014 06:51PM
I had the same issue when I tried to use a HDD. I think the drive wasnt spinning up fast enough to be initialized before boot kicks off. That was the case with my nsa325 v1. I ended up using a small profile flash drive. I played with uboot sleep setting but it didnt help.

~sol
Re: NSA 325 V2 Debian Is Possible!
February 18, 2014 06:52PM
SomeoneOnline could be right there

T Device NOT ready

Sounds like its an issue with the drive your using what kind of usb drive is it?

I had issues before with the usb board in a usb drive having kind of a hidden partition or something on it and it wouldnt it wouldnt read the drive.



Edited 1 time(s). Last edit at 02/18/2014 06:56PM by Buttzy10169.
marcint43
Re: NSA 325 V2 Debian Is Possible!
February 18, 2014 06:56PM
In my timezone is 2:52 AM ...so maybe I not think good after whole day, but I think that this is not issue with spinning, because when I have console active again and type "boot" reply is given immediately ... without any seconds waiting:


Marvell>> run bootcmd_linux
(Re)start USB...
USB:   scanning bus for devices... 1 USB Device(s) found
Waiting for storage device(s) to settle before scanning...
0 Storage Device(s) found
** Bad partition 1 **
** Bad partition 1 **
## Booting image at 02000000 ...
Bad Magic Number
Marvell>> boot
(Re)start USB...
USB:   scanning bus for devices... 1 USB Device(s) found
Waiting for storage device(s) to settle before scanning...
0 Storage Device(s) found
** Bad partition 1 **
** Bad partition 1 **
## Booting image at 02000000 ...
Bad Magic Number
Marvell>> 
Re: NSA 325 V2 Debian Is Possible!
February 18, 2014 06:59PM
Thats because it only detects the usb's once no matter how many times you ask it to check / power on i think.

so if it wasnt there when it first checked it doesnt check again you need to restart.
marcint43
Re: NSA 325 V2 Debian Is Possible!
February 18, 2014 07:03PM
> Sounds like its an issue with the drive your using what kind of usb drive is it?

I am using pendrive, exaclty the same looks like:
http://www.ebay.com/itm/Patriot-Memory-8GB-Supersonic-Boost-XT-USB-3-0-Flash-Drive-PEF8GSBUSB-/400655951474
but 16GB capacity, and PATRIOT text instead of XPORTER.
marcint43
Re: NSA 325 V2 Debian Is Possible!
February 18, 2014 07:06PM
restarted few times, via turning power from the wall outlet
nothing changes
Re: NSA 325 V2 Debian Is Possible!
February 18, 2014 07:07PM
Which USB port is it plugged into?
marcint43
Re: NSA 325 V2 Debian Is Possible!
February 18, 2014 07:09PM
the rear one of course
1st or 2nd
Re: NSA 325 V2 Debian Is Possible!
February 18, 2014 07:13PM
Right now the only clue to the problem is:

USB:   scanning bus for devices... 3 USB Device(s) found
Waiting for storage device(s) to settle before scanning...
T Device NOT ready
   Request Sense returned 00 00 00
1 Storage Device(s) found

which to me says that your usb drive isnt being detected.
marcint43
Re: NSA 325 V2 Debian Is Possible!
February 18, 2014 07:15PM
every first time console is frozen at:

Waiting for storage device(s) to settle before scanning...
T

and after some time there is rest printed (not ready....blahblah)
Re: NSA 325 V2 Debian Is Possible!
February 18, 2014 07:21PM
Again its trying to detect your usb drive there so maybe try a different usb drive?

or maybe its the permissions on the usb drive thats stopping the files from being read?
marcint43
Re: NSA 325 V2 Debian Is Possible!
February 18, 2014 07:23PM
I am just doing that ... preparing another pendrive (very old one, Kingstone, 512MB)..give me 2minutes
Re: NSA 325 V2 Debian Is Possible!
February 18, 2014 07:30PM
Make sure you only have 1 usb drive pluged in when your testing it.
marcint43
Re: NSA 325 V2 Debian Is Possible!
February 18, 2014 07:40PM
of course, only one pendrive one time.


linuxbox# ls -l sda1
razem 19381
-rw-r--r-- 1 root root  121807 lut  4 11:45 config-3.13.1-kirkwood-tld-2
-rw-r--r-- 1 root root 6568002 lut  5 20:30 initrd.img-3.13.1-kirkwood-tld-2
-rw-r--r-- 1 root root 1698808 lut  4 15:20 System.map-3.13.1-kirkwood-tld-2
-rw-r--r-- 1 root root 2399792 lut  5 20:30 uImage
-rw-r--r-- 1 root root 6568066 lut  5 20:31 uInitrd
-rw-r--r-- 1 root root 2399728 lut  4 15:20 vmlinuz-3.13.1-kirkwood-tld-2
linuxbox# ls -l sda2
razem 38
drwxr-xr-x  2 root root  3072 gru 14 07:33 bin
drwxr-xr-x  5 root root  1024 lut 24  2012 dev
drwxr-xr-x 51 root root  4096 sty  1  1970 etc
drwxr-xr-x  2 root root  1024 sty 22  2012 home
lrwxrwxrwx  1 root root    37 lut  5 20:31 initrd.img -> boot/initrd.img-3.13.1-kirkwood-tld-2
drwxr-xr-x 11 root root  1024 cze 14  2013 lib
drwx------  2 root root 12288 lut 24  2012 lost+found
drwxr-xr-x  2 root root  1024 lut 24  2012 media
drwxr-xr-x  2 root root  1024 sty 22  2012 mnt
drwxr-xr-x  2 root root  1024 lut 24  2012 opt
drwxr-xr-x  2 root root  1024 sty 22  2012 proc
drwx------  4 root root  1024 lut  5 21:49 root
drwxr-xr-x  2 root root  1024 lut  8  2013 run
drwxr-xr-x  2 root root  4096 gru 14 07:33 sbin
drwxr-xr-x  2 root root  1024 lip 21  2010 selinux
drwxr-xr-x  2 root root  1024 lut 24  2012 srv
drwxr-xr-x  2 root root  1024 sty  1  2011 sys
drwxrwxrwt  2 root root  1024 sty  1  1970 tmp
drwxr-xr-x 10 root root  1024 lut 24  2012 usr
drwxr-xr-x 11 root root  1024 sty  1  1970 var
lrwxrwxrwx  1 root root    34 lut  5 20:31 vmlinuz -> boot/vmlinuz-3.13.1-kirkwood-tld-2


linuxbox# cat  sda2/etc/fstab
# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
/dev/sda2      /               ext4    noatime,errors=remount-ro 0 1
tmpfs          /tmp            tmpfs   defaults          0       0
linuxbox#


PS> My daugther will kill me :P I erased her all fairy tales ;-)




IT WORKS !
marcint43
Re: NSA 325 V2 Debian Is Possible!
February 18, 2014 07:42PM
PEX 1: interface detected no Link.
Net:   egiga0 [PRIME]
Hit any key to stop autoboot:  0 
(Re)start USB...
USB:   scanning bus for devices... 3 USB Device(s) found
Waiting for storage device(s) to settle before scanning...
1 Storage Device(s) found
.........................
.........................
.........................
.........................
.........................
.........................
.........................
.........................
.........................
..

2399792 bytes read
.
.........................
.........................
.........................
.........................
.........................
.........................
.........................
.........................
.........................
.........................
.........................
.........................
.........................
.........................
.........................
...
......................
.........................
.........................
.........................
.........................
.........................
.........................
.........................
.........................
.........................

6568066 bytes read
## Booting image at 02000000 ...
   Image Name:   Linux-3.13.1-kirkwood-tld-2
   Created:      2014-02-05  19:30:49 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2399728 Bytes =  2.3 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK
## Loading Ramdisk Image at 01100000 ...
   Image Name:   initramfs-3.13.1-kirkwood-tld-2
   Created:      2014-02-05  19:31:01 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    6568002 Bytes =  6.3 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... 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 3.13.1-kirkwood-tld-2 (root@tldDebian) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 PREEMPT Tue Feb 4 03:19:07 PST 2014
[    0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977
[    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] Machine: ZyXEL NSA325 2-Bay Power Media Server
[    0.000000] Memory policy: Data cache writeback
[    0.000000] On node 0 totalpages: 131072
[    0.000000] free_area_init_node: node 0, pgdat c06aa824, node_mem_map c0719000
[    0.000000]   Normal zone: 1024 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 131072 pages, LIFO batch:31
[    0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[    0.000000] pcpu-alloc: [0] 0 
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 130048
[    0.000000] Kernel command line: console=ttyS0,115200 mtdparts=nand_mtd:0x100000(uboot),0x80000(uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(rootfs1),0x
A00000(kernel_2),0x2FC0000(rootfs2) root=LABEL=rootfs loglevel=8
[    0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.000000] Memory: 506064K/524288K available (4659K kernel code, 346K rwdata, 1588K rodata, 211K init, 425K bss, 18224K reserved)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
[    0.000000]     vmalloc : 0xe0800000 - 0xff000000   ( 488 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xe0000000   ( 512 MB)
[    0.000000]     modules : 0xbf000000 - 0xc0000000   (  16 MB)
[    0.000000]       .text : 0xc0008000 - 0xc06220ac   (6249 kB)
[    0.000000]       .init : 0xc0623000 - 0xc0657e4c   ( 212 kB)
[    0.000000]       .data : 0xc0658000 - 0xc06ae824   ( 347 kB)
[    0.000000]        .bss : 0xc06ae824 - 0xc0718d6c   ( 426 kB)
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000] NR_IRQS:114
[    0.000000] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 21474836475ns
[    0.000000] Console: colour dummy device 80x30
[   18.343093] Calibrating delay loop... 1594.16 BogoMIPS (lpj=7970816)
[   18.382908] pid_max: default: 32768 minimum: 301
[   18.382995] Security Framework initialized
[   18.383054] Mount-cache hash table entries: 512

...


[....] Starting NFS common utilities: statd idmapd. ok 
[....] Starting rpcbind daemon...[....] Already running.. ok 
[....] Starting NTP server: ntpd. ok 
[....] Not starting NFS kernel daemon: no exports. ... (warning).
[....] Starting OpenBSD Secure Shell server: sshd. ok 
1699 (klogd)
. ok 

Debian GNU/Linux 7 debian ttyS0

debian login:

:-))))))))))))))))))))))))))))))))


THANKS A LOT !
marcint43
Re: NSA 325 V2 Debian Is Possible!
February 18, 2014 07:45PM
Home sweet home :) Debian :))))

root@debian:~# cat /proc/cpuinfo 
processor       : 0
model name      : Feroceon 88FR131 rev 1 (v5l)
Features        : swp half thumb fastmult edsp 
CPU implementer : 0x56
CPU architecture: 5TE
CPU variant     : 0x2
CPU part        : 0x131
CPU revision    : 1

Hardware        : ZyXEL NSA325 2-Bay Power Media Server
Revision        : 0000
Serial          : 0000000000000000
root@debian:~#



PS. how to install mdadm ?
marcint43
Re: NSA 325 V2 Debian Is Possible!
February 18, 2014 07:50PM
Thanks all for help, but SPECIALLY THANKS TO "Buttzy10169" - MANY THANKS FOR YOUR SUPPORT :))))))
I spent hours on that before I decided to write message on that forum, MANY THANKS FOR YOU :)

Now it's almost 4 AM...and I will wake up at 6:30am...so I will go to sleep ... for a while ;-)

Thanks again :)
NobuoT
Re: NSA 325 V2 Debian Is Possible!
February 21, 2014 05:37AM
I got debian running on NSA325v2 from SATA with bodhi's kernel, Buttzy's instructions and some trial and error. Great and thanks for all your work! Especially also to WarheadSE and the ARCH team working on these parts.

Now there are still some minor things about the kernel and the hardware in general that are bugging me and I hope someone can shed a bit of light for me on one or another:

1. The buzzer:
Doesn't look like it is addressed at all in the kernel patch. Are there any plans to add support for it? I had a look at this in the zyxel kernel sources and they seem to drive the buzzer by toggling the buzzer pin (GPIO 44) in a busy loop inside a kernel timer? o_0
Isn't there a more elegant way of doing this?

2. NSA325_GPIO_HDD2_POWER in arch/arm/mach-kirkwood/nsa325-setup.c:
Where does that come from? Didn't find any equivalent in the zyxel sources...?
And while we're at it: Any idea what this HTP pin on GPIO43 is? (it's also in the zyxel sources)

3. WOL:
Again: Didn't find anything related in the patch. Any plans?

4. The MCU:
AFAIK it has 3 main tasks:
a) A watchdog timer that pulls the SoC reset line if GPIO14 is not pulled high
b) "smart" fan speed control via PWM
c) SPI-like interface to report temperature and fan speed to SoC

Is this really all? If they went to the length to attach a whole MCU to their design instead of some cheap i2c sensors and controllers, why didn't they make it do something actually useful? Like a method for software fan speed control by SoC?
Or attach the buzzer to a PWM capable pin?
And I don't know if they did, but it surely would have been a smart idea to hook the reset switch also to a MCU input to implement a kind of intelligent reset system in combination with their funny watchdog...


And a bit OT:
Did anyone already take a look at zyxel's uBoot sources to compile a new version with more features (FDT support anyone)?
Re: NSA 325 V2 Debian Is Possible!
February 21, 2014 07:56AM
Buzzer:
Well, you could write a wrapper around that, but that's really the only way to drive it since it is attached to GPIO, not PWM. You might be able to semi-synthezie PWM.

HDD2_POWER:
That's take from the the init bits on what GPIO are being set high at boot (and me manually pinning out each GPIO to confirm) from ZyXEL stock. It was a PITA to find, and in the unified 2013.10-kirkwood we're going to make it turn it on by default.

MCU:
I hate ZyXEL's "creative" EE's. Simple as that. Seriously? Use the WOL feature of the PHY to communicate with the SoC via RGMII to control the 2nd LED into a tri-state and twip the bit thereon to get the MCU to listen and stop resetting the board?? OH MY GOD.

HTP on 43 .. hrm, I have to go back and look.
marcint43
Re: NSA 325 V2 Debian Is Possible!
February 27, 2014 04:57PM
how to revert back changes if I would like to back to original firmware ?

Marvell>> setenv bootcmd \'run bootcmd_stock\'
Marvell>> printenv bootcmd
bootcmd='run bootcmd_stock'
Marvell>> saveenv
Saving Environment to NAND...
Erasing Nand...Writing to Nand... done
Marvell>> reset


device boots, and stops at:

[BlueDBG] reseting SoC Pex[1]  4 ...
        [BlueDBG] reseting SoC Pex[1]  5 ...
        [BlueDBG] reseting SoC Pex[1]  6 ...
        [BlueDBG] reseting SoC Pex[1]  7 ...
        [BlueDBG] reseting SoC Pex[1]  8 ...
        [BlueDBG] reseting SoC Pex[1]  9 ...
        [BlueDBG] reseting SoC Pex[1]  10 ...
PEX 1: interface detected no Link.
Net:   egiga0 [PRIME]
Hit any key to stop autoboot:  0 

NAND read: device 0 offset 0x4640000, size 0xa00000

Reading data from 0x503f800 -- 100% complete.
 10485760 bytes read: OK
## Booting image at 02000000 ...
   Image Name:   Linux-2.6.31.8
   Created:      2013-08-22   9:04:41 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    5754856 Bytes =  5.5 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux..................................................................................................................................................................................


nothing changes next ...

default values before any change were:
bootargs=console=ttyS0,115200 mtdparts=nand_mtd:0x100000(uboot),0x80000(uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(rootfs1),0xA00000(kernel_2),0x2FC0000(rootfs2) root=/dev/nfs rw init=/init
bootcmd=nand read.e 0x2000000 $(kernel_addr) 0xA00000; bootm 0x2000000
bootdelay=2

now I have:

bootargs=console=ttyS0,115200 mtdparts=nand_mtd:0x100000(uboot),0x80000(uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(rootfs1),0xA00000(kernel_2),0x2FC0000t
bootdelay=2
arcNumber=4495
bootargs_stock=console=ttyS0,115200 mtdparts=nand_mtd:0x100000(uboot),0x80000(uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(rootfs1),0xA00000(kernel_2),0x2F
C0000(rootfs2) root=/dev/nfs rw init=/init
bootargs_linux=console=ttyS0,115200 mtdparts=nand_mtd:0x100000(uboot),0x80000(uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(rootfs1),0xA00000(kernel_2),0x2F
C0000(rootfs2) root=LABEL=rootfs loglevel=8
bootcmd_linux=setenv bootargs $(bootargs_linux); mw.l f1010100 0020c000; usb reset; ext2load usb 0:1 $(loadaddr) /uImage; ext2load usb 0:1 0x01100000 /uInitrd; bootm $(loadaddr) 0x01100000
bootcmd_stock=setenv bootargs $(bootargs_stock); nand read.e $(loadaddr) $(kernel_addr) 0xA00000; bootm $(loadadr)
to_stock=setenv mainlineLinux no; setenv bootcmd \'run bootcmd_stock\'; saveenv; reset
to_linux=setenv mainlineLinux yes; setenv bootcmd \'run bootcmd_linux\'; saveenv; reset
bootcmd='run bootcmd_stock'
mainlineLinux=yes
(...)


Marvell>> setenv bootcmd 'nand read.e 0x2000000 $(kernel_addr) 0xA00000; bootm 0x2000000'
Marvell>> boot
NAND read: device 0 offset 0x4640000, size 0xa00000


..also freezes on Uncompressing linux ..................
Re: NSA 325 V2 Debian Is Possible!
February 27, 2014 05:02PM
Guys,

Could you post your dmesg output for NSA325? (running kernel 3.xx.xx whether Debian or Arch).

Thanks!

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



Edited 1 time(s). Last edit at 02/27/2014 05:03PM 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: