Re: Zyxel NSA310 u-boot-2014.07-tld-4 for testing

August 21, 2015, 3:54 pm

≫ Next: Re: Zyxel NSA310 u-boot-2014.07-tld-4 for testing

≪ Previous: Re: Zyxel NSA310 u-boot-2014.07-tld-4 for testing

$

0

0

bobafetthotmail Wrote:
-------------------------------------------------------
> nsa310 here, zyxel one.
>
> It does seem to have indeed that realtek chip.

Cool! thanks for the confirmation.

> kwbooted and your uboot has no ethernet access.

No wonder!

> rebooting into normal uboot, see below

> then I get multiple errors of marvell driver like
> below, suspectging the dts is wrong, it maybe says
> there is a marvell eth when there is none. I am
> using dts booting with dts in uimage (or zimage),
> kernel 3.17. dts nsa310, not nsa310a.

Yes, either the DTS or kernel ethernet config is suspected. I'm surprised nobody has reported this. iirc, some users have tried and/or use my built kernel for NSA310.

> there seems to be some significant confusion
> somehwere, I can assure you that this is NOT a
> nsa325, yet lshw tells me this
>
> description: Computer
> product: ZyXEL NSA325
> width: 32 bits
> *-core
> description: Motherboard
> physical id: 0
> capabilities: zyxel_nsa325
> marvell_kirkwood-88f6282 marvell_kirkwood

Check your appended DTB if it is the right one, and/or try to boot with 3.16 to see if the same info show up. And 3.6 kernel needs u-boot envs:

arcNumber - set to 4022
machid - removed this env

BTW, does your dmesg show that it is the NSA310, not NSA325?

---

Re: Zyxel NSA310 u-boot-2014.07-tld-4 for testing

August 21, 2015, 4:52 pm

≫ Next: Re: pogoplug E02 prompt "ERROR: can't get kernel image!", please help!

≪ Previous: Re: Zyxel NSA310 u-boot-2014.07-tld-4 for testing

$

0

0

Quote
http://forum.doozan.com/read.php?3,12381,21223#msg-21223

marlemion said:

EDIT7: So the RTL8111d chip is an PCI-e chip. PCI-e is initialized, however, the linking problems remain. Does anybody know how to get further?

And:
http://www.realtek.com.tw/products/productsView.aspx?Langid=1&PFid=5&Level=5&Conn=4&ProdID=193

This is going to be troublesome.

Re: pogoplug E02 prompt "ERROR: can't get kernel image!", please help!

August 21, 2015, 6:21 pm

≫ Next: Re: pogoplug E02 prompt "ERROR: can't get kernel image!", please help!

≪ Previous: Re: Zyxel NSA310 u-boot-2014.07-tld-4 for testing

$

0

0

Many thanks. Please check below

root@debian:~# fw_printenv
ethact=egiga0
bootdelay=3
baudrate=115200
arcNumber=2097
mainlineLinux=yes
console=ttyS0,115200
led_init=green blinking
led_exit=green off
led_error=orange blinking
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
mtdids=nand0=orion_nand
partition=nand0,2
stdin=serial
stdout=serial
stderr=serial
rescue_installed=0
rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params
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
pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi
force_rescue=0
force_rescue_bootcmd=if test $force_rescue -eq 1 || ext2load usb 0:1 0x1700000 /rescueme 1 || fatload usb 0:1 0x1700000 /rescueme.txt 1; then run rescue_bootcmd; fi
ubifs_mtd=3
ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params
ubifs_bootcmd=run ubifs_set_bootargs; if ubi part data && ubifsmount rootfs && ubifsload 0x800000 /boot/uImage && ubifsload 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; fi
usb_scan=usb_scan_done=0;for scan in $usb_scan_list; do run usb_scan_$scan; if test $usb_scan_done -eq 0 && ext2load usb $usb 0x800000 /boot/uImage 1; then usb_scan_done=1; echo "Found bootable drive on usb $usb"; setenv usb_device $usb; setenv usb_root /dev/$dev; fi; done
usb_scan_list=1 2 3 4
usb_scan_1=usb=0:1 dev=sda1
usb_scan_2=usb=1:1 dev=sdb1
usb_scan_3=usb=2:1 dev=sdc1
usb_scan_4=usb=3:1 dev=sdd1
usb_init=run usb_scan
usb_device=0:1
usb_root=/dev/sda1
usb_rootfstype=ext2
usb_rootdelay=10
usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params
usb_bootcmd=run usb_init; run usb_set_bootargs; run usb_boot
usb_boot=mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage; if ext2load usb $usb_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; reset
root@debian:~#

Re: pogoplug E02 prompt "ERROR: can't get kernel image!", please help!

August 21, 2015, 6:40 pm

≫ Next: Re: pogoplug E02 prompt "ERROR: can't get kernel image!", please help!

≪ Previous: Re: pogoplug E02 prompt "ERROR: can't get kernel image!", please help!

$

0

0

doomgiant,

So now when you boot without the USB drive, what does serial console output looks like?

Re: pogoplug E02 prompt "ERROR: can't get kernel image!", please help!

August 21, 2015, 6:41 pm

≫ Next: Re: PogoPlug 4: cant access external usb drive on network

≪ Previous: Re: pogoplug E02 prompt "ERROR: can't get kernel image!", please help!

$

0

0

Sorry for the missing log.

without the usb drive, it display as below and can't get the ip address

U-Boot 2011.12 (Feb 20 2012 - 21:21:59)
Pogoplug E02

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

** Invalid boot device **
Creating 1 MTD partitions on "nand0":
0x000002500000-0x000008000000 : "mtd=3"
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    129024 bytes
UBI: smallest flash I/O unit:    2048
UBI: sub-page size:              512
UBI: VID header offset:          512 (aligned 512)
UBI: data offset:                2048
UBI: attached mtd1 to ubi0
UBI: MTD device name:            "mtd=3"
UBI: MTD device size:            91 MiB
UBI: number of good PEBs:        728
UBI: number of bad PEBs:         0
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     0
UBI: available PEBs:             717
UBI: total number of reserved PEBs: 11
UBI: number of PEBs reserved for bad PEB handling: 7
UBI: max/mean erase counter: 1/1
UBIFS error (pid 0): ubifs_get_sb: cannot open "ubi:rootfs", error -19
Error reading superblock on volume 'ubi:rootfs'!
** Block device usb 0 not supported
** Block device usb 1 not supported
** Block device usb 2 not supported
** Block device usb 3 not supported
** Block device usb 0 not supported
** Block device usb 0 not supported
Wrong Image Format for bootm command
ERROR: can't get kernel image!
stopping USB..
### JFFS2 loading 'uboot-original-mtd0.kwb' to 0x800000
Scanning JFFS2 FS: ....... done.
### JFFS2 load complete: 437248 bytes loaded to 0x800000
## Starting application at 0x00800200 ...

Re: PogoPlug 4: cant access external usb drive on network

August 21, 2015, 8:08 pm

≫ Next: Re: PogoPlug 4: cant access external usb drive on network

≪ Previous: Re: pogoplug E02 prompt "ERROR: can't get kernel image!", please help!

$

0

0

theeleaper Wrote:
-------------------------------------------------------
> Hi
> I have debian installed with your help. That is
> working great. Now i have a problem with external
> usb HD. It shows up in network. On windows machine
> but can not access
> Thank you

post your smb.conf

run the following command and post it here

cat /etc/samba/smb.conf

Re: PogoPlug 4: cant access external usb drive on network

August 21, 2015, 10:00 pm

≫ Next: Re: Zyxel NSA310 u-boot-2014.07-tld-4 for testing

≪ Previous: Re: PogoPlug 4: cant access external usb drive on network

$

0

0

Hi.

Thank you for responding. here is info
TIA

[global]
 workgroup = WORKGROUP
 server string = POGOPLUG
 netbios name = POGOPLUG
 load printers = no
 printing = bsd
 printcap name = /dev/null
 disable spoolss = yes
 log file = /var/log/samba/%m.log
 max log size = 50
 socket options = IPTOS_LOWDELAY TCP_NODELAY SO_KEEPALIVE
 write cache size = 2097152
 use sendfile = yes

 #unprotected/public share without login
 security = share
 guest account = root

[root$]
  path = /
  read only = no
  public = yes
  writable = yes
  #force user = root
  guest ok = yes

[usb]
  path = /media/usb/share
  read only = no
  public = yes
  writable = yes
  #force user = root
  guest ok = yes

Re: Zyxel NSA310 u-boot-2014.07-tld-4 for testing

August 22, 2015, 3:50 am

≫ Next: Re: Zyxel NSA310 u-boot-2014.07-tld-4 for testing

≪ Previous: Re: PogoPlug 4: cant access external usb drive on network

$

0

0

Attached here is the first cut to enable RTL8169 chip ( not sure how far we'll get with this image :).

I turned on RTL8169 debug so we can see if the card is intialized at all.

Please test with UART only (not flashing to NAND)

kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2014.07-tld-4-test-1.nsa310.mtd0.kwb -p

---

Re: Zyxel NSA310 u-boot-2014.07-tld-4 for testing

August 22, 2015, 5:08 am

≫ Next: Re: HOW2: Repair Pogo E02 with Raspberry PI (JTAG) and OpenOCD

≪ Previous: Re: Zyxel NSA310 u-boot-2014.07-tld-4 for testing

$

0

0

the "ZyXEL" NSA310 has arrived so let's see
it has the _same_ ethernet chip as the "TDC" one.

http://abload.de/img/nsa310_lan_chipapkr9.jpg <- lan chip

http://abload.de/img/nsa310_pcb_2auqoo.jpg <- pcb


@bobafetthotmail

I never had problems with the NSA310 (ZxXEL and TDC) (Kernel 3.18.3, 4.0.0, 4.10)
that one on which I tested the new U-Boot yesterday has some memory issues

[    1.947877] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[    1.953538] pci 0000:00:01.0: enabling device (0140 -> 0143)
[    1.959242] pci 0000:00:01.0: enabling bus mastering
[    1.959260] r8169 0000:01:00.0: enabling device (0140 -> 0143)
[    1.965155] r8169 0000:01:00.0: enabling Mem-Wr-Inval
[    1.965310] r8169 0000:01:00.0: enabling bus mastering
[    1.965975] r8169 0000:01:00.0 eth0: RTL8168d/8111d at 0xd090e000, 00:00:00:00:00:30, XID 083000c0 IRQ 83
[    1.975622] r8169 0000:01:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]

...
...

   14.253938] NET: Registered protocol family 10
[   14.444661] r8169 0000:01:00.0 eth0: link down
[   14.449151] r8169 0000:01:00.0 eth0: link down
[   14.453708] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   16.308575] r8169 0000:01:00.0 eth0: link up
[   16.312903] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[....] Configuring network interfaces...Internet Systems Consortium DHCP Client 4.3.1
Copyright 2004-2014 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/eth0/5c:f4:ab:e3:e6:1e
Sending on   LPF/eth0/5c:f4:ab:e3:e6:1e
Sending on   Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPOFFER from 192.168.1.1
DHCPACK from 192.168.1.1

there were no memory issues so I can go furher:
http://pastebin.com/m0dyJqYS

no linking problems but poor performance (read)
I never noticed this before but a friend of me has the same issue
with some tuning I get 25 MB/s read and 38 MB/s write

Re: HOW2: Repair Pogo E02 with Raspberry PI (JTAG) and OpenOCD

August 22, 2015, 9:26 am

≫ Next: Re: Linux Kernel 4.1 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs

≪ Previous: Re: Zyxel NSA310 u-boot-2014.07-tld-4 for testing

$

0

0

I think this is very much the same as the pogo cfg file. I did use the init_docstar proc when the software command didn't get a proper halt. Read through the cfg file to see other procs available. The Openocd manual has some good stuff on the config file if you are curious. It explains some of the variables used in the config file.

pi@raspberrypi ~ $ cat /usr/share/openocd/scripts/board/dockstar.cfg 
# Marvell SheevaPlug

# I'm using a wiggler compatible cable
source [find interface/sysfsgpio-raspberrypi.cfg]
source [find target/feroceon.cfg]
adapter_khz 200
adapter_nsrst_delay 500

$_TARGETNAME configure \
	-work-area-phys 0x100000 \
	-work-area-size 65536 \
	-work-area-backup 0

# Disabled for the dockstar	
#arm7_9 dcc_downloads enable

# this assumes the hardware default peripherals location before u-Boot moves it
set _FLASHNAME $_CHIPNAME.flash
nand device $_FLASHNAME orion 0 0xd8000000

proc dockstar_init { } {

	# We need to assert DBGRQ while holding nSRST down.
	# However DBGACK will be set only when nSRST is released.
	# Furthermore, the JTAG interface doesn't respond at all when
	# the CPU is in the WFI (wait for interrupts) state, so it is
	# possible that initial tap examination failed.  So let's
	# re-examine the target again here when nSRST is asserted which
	# should then succeed.
	jtag_reset 0 1
	feroceon.cpu arp_examine
	halt 0
	jtag_reset 0 0
	wait_halt

	arm mcr 15 0 0 1 0 0x00052078

	mww 0xD0001400 0x43000C30
	mww 0xD0001404 0x39543000 
	mww 0xD0001408 0x22125451 
	mww 0xD000140C 0x00000833 
	mww 0xD0001410 0x000000CC
	mww 0xD0001414 0x00000000 
	mww 0xD0001418 0x00000000
	mww 0xD000141C 0x00000C52 
	mww 0xD0001420 0x00000042 
	mww 0xD0001424 0x0000F17F 
	mww 0xD0001428 0x00085520 
	mww 0xD000147c 0x00008552 

	# 1st bank is 128 MB
	mww 0xD0001504 0x07FFFFF1 
	# 2nd bank of DRAM is not used
	mww 0xD0001508 0x00000000 
	mww 0xD000150C 0x00000000
	# Commented the 3 following	lines
	#mww 0xD0001504 0x0FFFFFF1 
	#mww 0xD0001508 0x10000000 
	#mww 0xD000150C 0x0FFFFFF5 
	mww 0xD0001514 0x00000000
	mww 0xD000151C 0x00000000
	mww 0xD0001494 0x003C0000 
	mww 0xD0001498 0x00000000
	mww 0xD000149C 0x0000F80F 
	mww 0xD0001480 0x00000001 
	mww 0xD0020204 0x00000000
	mww 0xD0020204 0x00000000
	mww 0xD0020204 0x00000000
	mww 0xD0020204 0x00000000
	mww 0xD0020204 0x00000000
	mww 0xD0020204 0x00000000
	mww 0xD0020204 0x00000000
	mww 0xD0020204 0x00000000
	mww 0xD0020204 0x00000000
	mww 0xD0020204 0x00000000
	mww 0xD0020204 0x00000000
	mww 0xD0020204 0x00000000
	mww 0xD0020204 0x00000000
	mww 0xD0020204 0x00000000
	mww 0xD0020204 0x00000000
	mww 0xD0020204 0x00000000
	mww 0xD0020204 0x00000000
	mww 0xD0020204 0x00000000
	mww 0xD0020204 0x00000000
	mww 0xD0020204 0x00000000
	mww 0xD0020204 0x00000000
	mww 0xD0020204 0x00000000
	mww 0xD0020204 0x00000000
	mww 0xD0020204 0x00000000
	mww 0xD0020204 0x00000000
	mww 0xD0020204 0x00000000
	mww 0xD0020204 0x00000000
	mww 0xD0020204 0x00000000
	mww 0xD0020204 0x00000000
	mww 0xD0020204 0x00000000
	mww 0xD0020204 0x00000000
	mww 0xD0020204 0x00000000
	mww 0xD0020204 0x00000000
	mww 0xD0020204 0x00000000
	mww 0xD0020204 0x00000000
	mww 0xD0020204 0x00000000
	mww 0xD0020204 0x00000000

	mww 0xD0010000 0x01111111 
	mww 0xD0010004 0x11113322 
	mww 0xD0010008 0x00001111

	mww 0xD0010418 0x003E07CF
	mww 0xD001041C 0x000F0F0F
	mww 0xD0010470 0x01C7D943

}

proc sheevaplug_reflash_uboot { } {

	# reflash the u-Boot binary and reboot into it
	sheevaplug_init
	nand probe 0
	nand erase 0 0x0 0xa0000
	nand write 0 uboot.bin 0 oob_softecc_kw
	resume

}

proc sheevaplug_reflash_uboot_env { } {

	# reflash the u-Boot environment variables area
	sheevaplug_init
	nand probe 0
	nand erase 0 0xa0000 0x40000
	nand write 0 uboot-env.bin 0xa0000 oob_softecc_kw
	resume

}

proc sheevaplug_load_uboot { } {

	# load u-Boot into RAM and execute it
	sheevaplug_init
	#load_image uboot.elf
	#verify_image uboot.elf
	load_image u-boot
	verify_image u-boot
	resume 0x00600000

}

proc dockstar_reset_cpu { } {

#	System and User mode registers
#		  r0: 00000000       r1: 00000000       r2: 00000000       r3: 00000000
#		  r4: 00000000       r5: 00000000       r6: 00000000       r7: 00000000
#		  r8: 00000000       r9: 00000000      r10: 00000000      r11: 00000000
#		 r12: 00000000   sp_usr: 7dddee86   lr_usr: dffebe46       pc: ffff0a42
#		cpsr: 400000f3

	reg r1 0
	reg r2 0
	reg r3 0
	reg r4 0
	reg r5 0
	reg r6 0
	reg r7 0
	reg r8 0
	reg r9 0
	reg r10 0
	reg r11 0
	reg r12 0
	reg sp_usr 0
	reg lr_usr 0
	reg pc 0
	# Set the CPU in Supervisor mode
	reg cpsr 0x13

#	FIQ mode shadow registers
#	  r8_fiq: fbcfff64   r9_fiq: d7dfafd6  r10_fiq: 1fff6d2e  r11_fiq: 1db65df4
#	 r12_fiq: ff5a6de4   sp_fiq: 745fe7d5   lr_fiq: 89f7ae3e spsr_fiq: 00000000

	reg r8_fiq 0
	reg r9_fiq 0
	reg r10_fiq 0
	reg r11_fiq 0
	reg r12_fiq 0
	reg sp_fiq 0
	reg lr_fiq 0
	reg spsr_fiq 0

#	Supervisor mode shadow registers
#	  sp_svc: fffeff84   lr_svc: ffff0a43 spsr_svc: 00000000

	reg sp_svc 0
	reg lr_svc 0
	reg spsr_svc 0

#	Abort mode shadow registers
#	  sp_abt: 51fe66f7   lr_abt: d7abaef7 spsr_abt: 00000000

	reg sp_abt 0
	reg lr_abt 0
	reg spsr_abt 0

#	IRQ mode shadow registers
#	  sp_irq: 7fdb4ed5   lr_irq: 6d41122e spsr_irq: 00000000

	reg sp_irq 0
	reg lr_irq 0
	reg spsr_irq 0
	
#	Undefined instruction mode shadow registers
#	  sp_und: 75ffef7e   lr_und: d75b6cd1 spsr_und: 00000000

	reg sp_und 0
	reg lr_und 0
	reg spsr_und 0
	
}
pi@raspberrypi ~ $ /share/openocd/scripts/board/dockstar.cfg 
-bash: /share/openocd/scripts/board/dockstar.cfg: No such file or directory
pi@raspberrypi ~ $ pi@raspberrypi ~ $ cat /usr/share/openocd/scripts/board/dockstar.cfg 
-bash: pi@raspberrypi: command not found
pi@raspberrypi ~ $ 

Re: Linux Kernel 4.1 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs

August 22, 2015, 9:37 am

≫ Next: Re: Linux Kernel 4.1 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs

≪ Previous: Re: HOW2: Repair Pogo E02 with Raspberry PI (JTAG) and OpenOCD

$

0

0

PBG4 wrote that the NSA320 has been tested and validated. Will this be available for uploading? Thanks.

Paul

Re: Linux Kernel 4.1 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs

August 22, 2015, 1:29 pm

≫ Next: Re: PogoPlug 4: cant access external usb drive on network

≪ Previous: Re: Linux Kernel 4.1 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs

$

0

0

z3bram3n Wrote:
-------------------------------------------------------
> PBG4 wrote that the NSA320 has been tested and
> validated. Will this be available for uploading?
> Thanks.
>
> Paul

Hi Paul,

See my post above:
http://forum.doozan.com/read.php?2,12096,23388#msg-23388

I'm building a test kernel, and will check out on other Kirkwood boxes. Will let you know.

Re: PogoPlug 4: cant access external usb drive on network

August 22, 2015, 1:59 pm

≫ Next: Re: Linux Kernel 4.1 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs

≪ Previous: Re: Linux Kernel 4.1 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs

$

0

0

theeleaper,

So the problem is with Samba? if it is, see this post for a working Samba config:
http://forum.doozan.com/read.php?8,23223,23293#msg-23293

I would suggest that when you need help with any problem, be very wordy :) give a lot details, as much as you can. And post a log of what you trying to do.

Re: Linux Kernel 4.1 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs

August 22, 2015, 2:48 pm

≫ Next: Re: Linux Kernel 4.1 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs

≪ Previous: Re: PogoPlug 4: cant access external usb drive on network

$

0

0

bodhi Wrote:
-------------------------------------------------------
> hawryszka Wrote:
> --------------------------------------------------
> -----
> > Hello Guys
> > I have problems with nsa 325 v2.
> > I did everything, step by step on the solution
> but
> > stil have problems , i dont have any more
> patient
> > for that ..
> > I try to start linux from USB storage formated
> to
> > ext2 but i have that information in console :
> >

> > Part    Start Sector    Num Sectors     UUID    
>  
> >      Type
> >   1     63              15728577       
> > 100615b5-01     83 Boot
> > 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
> > 2931288 bytes read in 607 ms (4.6 MiB/s)
> > 6535284 bytes read in 909 ms (6.9 MiB/s)
> > ## Booting kernel from Legacy Image at 00800000
> > ...
> >    Image Name:   Linux-4.0.0-kirkwood-tld-1
> >    Created:      2015-08-21  19:28:15 UTC
> >    Image Type:   ARM Linux Kernel Image
> > (uncompressed)
> >    Data Size:    2931224 Bytes = 2.8 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-1
> >    Created:      2015-08-21  19:31:12 UTC
> >    Image Type:   ARM Linux RAMDisk Image (gzip
> > compressed)
> >    Data Size:    6535220 Bytes = 6.2 MiB
> >    Load Address: 00000000
> >    Entry Point:  00000000
> >    Verifying Checksum ... OK
> >    Loading Kernel Image ... OK
> > Using machid 0x118f from environment
> > 
> > Starting kernel ...
> > 
> > Uncompressing Linux... done, booting the
> kernel.
> > 
> > Error: unrecognized/unsupported machine ID (r1
> =
> > 0x0000118f).
> > 
> > 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.
> >

> >
> > I trying change kernel from 3.18 to new one but
> > without succesful
> >
> > Maybe some of You Guys can help me ?
> >
> > Best Regards!
>
>
> First step: boot with 3.16 rootfs (simpler to
> setup):
> http://forum.doozan.com/read.php?4,23425,23427#msg
> -23427
>
> And then come back, we'll cover device tree for
> it.

I can't believe ! After long time it's works !
Believe me or not but i searching information about solution aprox 1 month before write my post here, i try to start every i think available kernels and rootfs but no 3.16
Thanks bodhi !
Should or could i update/upgrade it to 4.0/4.1 rootfs version ?
From which instruction should i take it ?

Best Regards !

Re: Linux Kernel 4.1 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs

August 22, 2015, 3:53 pm

≫ Next: Re: Zyxel NSA310 u-boot-2014.07-tld-4 for testing

≪ Previous: Re: Linux Kernel 4.1 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs

$

0

0

hawryszka,

Glad it works for you!

> Should or could i update/upgrade it to 4.0/4.1
> rootfs version ?
> From which instruction should i take it ?

The reason you've had trouble trying out many different kernel versions was the issue of device tree (FDT) kernel vs. older non-FDT kernels. My kernel build 3.16.x or earlier were non-FDT. You should upgrade to get all the latest fixes for the NSA325. But as always, pls back up your rootfs first!

Some u-boot installation on the net are tailored to detect FDT kernel and boot that. But a simple and typical u-boot installation don't. So to upgrade to the latest kernel, see the same kernel thread and install the latest kernel (Linux-4.1.0-kirkwood-tld-2).

Pay special attention to section 4 (4. Create uImage and uInitrd and setup for booting), and the DTB-related steps.

- Use method 4b (appended DTB), this does not require changing u-boot envs. You are running the latest u-boot, so you could choose method 4a, but save it for later when you have become familiar with booting using 4a (separate DTB).

- Look for the correct DTB file in /boot/dts. For the NSA325v1/2, it is kirkwood-nsa325.dtb.

---

Re: Zyxel NSA310 u-boot-2014.07-tld-4 for testing

August 22, 2015, 4:29 pm

≫ Next: Re: pogoplug E02 prompt "ERROR: can't get kernel image!", please help!

≪ Previous: Re: Linux Kernel 4.1 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs

$

0

0

@pengu,

Please try UART booting the test u-boot image attached above:
uboot.2014.07-tld-4-test-1.nsa310.mtd0.kwb

Re: pogoplug E02 prompt "ERROR: can't get kernel image!", please help!

August 22, 2015, 7:31 pm

≫ Next: Re: Zyxel NSA310 u-boot-2014.07-tld-4 for testing

≪ Previous: Re: Zyxel NSA310 u-boot-2014.07-tld-4 for testing

$

0

0

doomgiant,

Everthing looks normal. Except that the stock kernel could not start. I believe this is likely the problem that restamp and I solved a few months ago, and I uploaded a new Pogo E02 u-boot image but forgot to release it:
http://forum.doozan.com/read.php?3,12381,20906#msg-20906

Basically, somehow the stock OS in NAND was modified during the installation or later, but with a different compression method, so the old u-boot was not capable of booting it any more. In your set up with Jeff script, the original u-boot was chained load and it loaded the stock kernel, but the stock OS in NAND could not be read properly, so it hang.

Let's not continue this stock OS booting issue, until I put the newer Pogo E02 u-boot up in the u-boot release thread, and then you can decide whether to pursue this. The Pogo E02 does not have serial recovery (i.e. UART booting) so there is a little bit more risk in flashing.

Re: Zyxel NSA310 u-boot-2014.07-tld-4 for testing

August 23, 2015, 12:41 am

≫ Next: Re: pogoplug E02 prompt "ERROR: can't get kernel image!", please help!

≪ Previous: Re: pogoplug E02 prompt "ERROR: can't get kernel image!", please help!

$

0

0

I'll do so but there is another interesting thing:

as seen in a previous post, on ZyXEL OS the "r8168" driver is used.
there, you geht 40 MB/s read and 45 MB/s write.
this driver is still used on debian wheezy (kernel 3.2.0)

on newer kernels wie have the "r8169 with this driver you only get
22 MB/s read and 35 MB/s write
with some network tuning, the following is possible:
26 MB/s read 38 MB/s write

should this change with the new U-Boot? let's see

the first chang I see is the following:

after setting ipaddr and serverip I cannot ping like on stock u-boot but with another error message:

NSA310> ping 192.168.1.112
No ethernet found.
ping failed; host 192.168.1.112 is not alive
NSA310>

read/write are the same as before ..
fhirst, this looks different but this was load related

Re: pogoplug E02 prompt "ERROR: can't get kernel image!", please help!

August 23, 2015, 2:50 am

≫ Next: Re: Zyxel NSA310 u-boot-2014.07-tld-4 for testing

≪ Previous: Re: Zyxel NSA310 u-boot-2014.07-tld-4 for testing

$

0

0

bodhi,

Many thanks for your detail explanation, it has been a great progress to make it work with Debian.

Thanks again!

And does it mean this boot issue can be fixed on 2014.07 U-Boot?

Re: Zyxel NSA310 u-boot-2014.07-tld-4 for testing

August 23, 2015, 1:04 pm

≫ Next: Re: Zyxel NSA310 u-boot-2014.07-tld-4 for testing

≪ Previous: Re: pogoplug E02 prompt "ERROR: can't get kernel image!", please help!

$

0

0

pengu,

>

> NSA310> ping 192.168.1.112
> No ethernet found.
> ping failed; host 192.168.1.112 is not alive
> NSA310> 
>

Is this the output from the test u-boot UART booting?