yes this isn't new to me but I thogut it should be possible with the stuff here. but it seems that the stock U-Boot doesn't like boot the kernel.by pengu - Debian
UART booting seems to work: ./kwboot -t -B 115200 /dev/ttyUSB1 -b /data/uboot.2013.10-tld-1-test.nsa325.uart.kwb Sending boot message. Please reboot the target...| Sending boot image... 0 % [......................................................................] 3 % [......................................................................] 5 % [...................................by pengu - Debian
I'm using newer U-Boot un my two Dockstar devices, they are running fineby pengu - Debian
got a DNS-325, tried to boot debian but no luck: ** MARVELL BOARD: DB-88F6281A-BP LE U-Boot 1.1.4 (May 16 2011 - 10:40:38) Marvell version: 3.4.14.DNS-325.03 U-Boot code: 00600000 -> 0067FFF0 BSS: -> 006CEE80 Soc: MV88F6281 Rev 3 (DDR2) CPU running @ 1200Mhz L2 running @ 400Mhz SysClock = 400Mhz , TClock = 200Mhz DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6 DRAM CSby pengu - Debian
> > Did you look at the sys log for clues when this > happened? The only thing I've seen is that the (usb 2 rootfs) stick is gone and so it isn't possible anymore to read from the filesystem. I've connected only usb 2 sticks to the usb3 port and they were still there. it seems that only the usb2.0 back ports were effected > The xhci driver does have quirksby pengu - Debian
@bobafetthotmail thanks .. this seems solved now for my NSA325v2 as you can see, but perhaps it helps to recognize the USB mass storage on NSA320s. but there is another problem, wich rises now: Is there something wrong with the USB 3.0 port? when connecting different usb sticks when running debian, the rootfs will go away after a while, only reboot helps ;-(by pengu - Debian
sz3bbylA: > [ 0.161017] : > /ocp@f1000000/ethernet-controller@72000/ethernet0- > port@0: local-mac-address is not set when the mac adress is set via U-Boot and "ifconfig" shows the same, then you can ignore this message. otherwhise set it here: /etc/network/interfacesby pengu - Debian
sz3bbylA Wrote: ------------------------------------------------------- > Yesterday i saw on my nsa320 this message on boot > > : > /ocp@f1000000/ethernet-controller@72000/ethernet0- > port@0: local-mac-address is not set > ethaddr= please set so this log message should go away. if not, please chack the "ifconfig" output > and > EXT2-fs (sdb1)by pengu - Debian
shootdown isn't working [ ok ] Unmounting temporary filesystems...done. [ ok ] Deactivating swap...done. [ ok ] Unmounting local filesystems...done. [ 747.031241] EXT4-fs (sda3): re-mounted. Opts: (null) Will now halt. logger: Will halt - now [ 749.222476] sd 2:0:0:0: Synchronizing SCSI cache [ 749.229184] reboot: Power down [ 752.418423] ------------[ cut here ]----------by pengu - Debian
no problems when starting debian from the uart NSA310s U-Boot To try this with stock U-Boot I have to flash the kernel stuff into nand or boot from HDDby pengu - Debian
it's quite different: I'm starting kwboot first, then powering on the device and it loads. this seems to interrupt the thing mentioned earler The NSA320s doesn't go off again as without kwboot and I don't have to manually power it on again.by pengu - Debian
bodhi Wrote: ------------------------------------------------------- > pengu, > > Thanks for confirming UART booting works! > > I saw you've responded on the other thread about > the "no link" problem with the 320S. yes ;-) > So to make sure I understood what you've tested: > - Boot with NAND stock u-boot, and Zyxel OS. > - Rebooby pengu - Debian
bodhi Wrote: ------------------------------------------------------- ... >I've started to work on u-boot and think > it will be a little slower to bring up because > nobody has brought this SoC up in mainline u-boot. The Medion Life P89634 MD 90221 has the same board / SoCby pengu - Debian
now let's boot via TFTP Marvell>> setenv bootargs 'console=ttyS0,115200 root=LABEL=rootfs rootfstype=ext4' Marvell>> tftp 0x800000 nsa320s/uImage Using egiga0 device TFTP from server 192.168.1.112; our IP address is 192.168.1.200 Filename 'nsa320s/uImage'. Load address: 0x800000 Loading: ############################################################by pengu - Debian
./kwboot -t -B 115200 /dev/ttyUSB0 -b u-boot-1.1.4-bodhi.nsa310s.uart.bin Sending boot message. Please reboot the target...\ Sending boot image... 0 % [......................................................................] 1 % [......................................................................] 3 % [......................................................................] 5 %by pengu - Debian
bodhi Wrote: ------------------------------------------------------- > @pengu, > > Does the 320s have the same PHY problem? it's different I think power on .. 10 baseT-HD --> green LED U-Boot: "no link" pinging not possible 10 baseT-HD -> green LED ZyXEL OS: 1000 baseT-FD -> amber LED power off: 10 baseTby pengu - Debian
bodhi Wrote: ------------------------------------------------------- > It did complete loading the image when you see > > > but it doesn't start > Sometime if your network is noisy, it could effect > the loading time. It should help if the terminal > session (where you run kwboot) is on a box that is > connected to the same switch/router that the >by pengu - Debian
I tried kwboot on NSA320s again first powered on the device, than it goes off (watchdog?) right after powering on egain, kwboot is loading the image but this does not complete several times ./kwboot -t -B 115200 /dev/ttyUSB0 -b /data/uboot.2013.10-tld-1-test.nsa325.uart.kwb Sending boot message. Please reboot the target...- Sending boot image... 0 % [..................................by pengu - Debian
exactly after the blue LED goes off for the first time I start kwboot .. after a while, the LED goes off and on again and than the image is loading .. but not completely as I think ./kwboot -t -B 115200 /dev/ttyUSB0 -b /data/uboot.2013.10-tld-1-test.nsa325.uart.kwbSending boot message. Please reboot the target...| Sending boot image... 0 % [.........................................by pengu - Debian
the power LED .. first I thought that there is something wrong .. only the power LED lights up ... one of the green LEDs lights up a little bit .. and no serial output after a fiew seconds the power LED goes off and on again .. then U-Boot is up .. you meen this? sometimes this happens twice not only once let's try ;-)by pengu - Debian
I think after 5 .. sometimes after 10 seconds no matter which usb port or hub /extension cable / usb to ttl cable I use sometimes the power on isn't recognized and kwboot still waits for power onby pengu - Debian
thanks bodhi with without -p .. same result ;-( bodhi Wrote: ------------------------------------------------------- > pengu, > > > +xmodem: Protocol error > > > Usually this is the synxtax error in the command. > Try with -p option, and without -p option. See > which one it will take.by pengu - Debian
got a nsa325v2, enabled telnet, changed the U-Boot env to boot debian (same as on NSA310/310s/320s), connected the stick to an usb 2.0 port (on the back) and rebooted the status of the LEDs indicates that ZyXEL OS was booting up looks like bootcmd_usb isn't executed. http://pastebin.com/34W98cgu <- fw_printenv output connectet serial console and same thing as described hby pengu - Debian
bodhi Wrote: ------------------------------------------------------- > pengu. > Did you do anything differently on the NSA310S? Noby pengu - Debian
yes, there were only one reset now after the nand write but it boots sometimes the first and sometimes the second kernel and os as described I could overwrite the older one (kernel, rootfs) so it doesn't matter. an other option is to write the uImage to nand and boot it from there but this could be the same as above sometimes debian is up and running, sometimes Zyxel OS working usbby pengu - Debian
bodhi Wrote: ------------------------------------------------------- > pengu, > > 1. Have you tried the port closest to the Ethernet > port? When you see this, it is stock u-boot > limitation with a very short time out when it > scans for USB drives (in the new u-boot, I > alleviated this by adding the env > usb_ready_retry). >Yes, I have and also changed tby pengu - Debian
Debian is running successful on my NSA310s, so I decided to do this on the NSA320s too but ther were some trouble: None of my usb sticks were recognized at U-Boot stage including the SanDisk Cruizer Blade. __ __ _ _ | \/ | __ _ _ ____ _____| | |by pengu - Debian
I'll try this soon, because I get into troubles on the stock os while transfering files from this on my linux box every 1,8 gb the transfer gets stuck (samba, ftp) no problems on windows 7 or 8.1 damacc could you confirm this? if yes, is this the same on debian? another question: does the display is working on debian?by pengu - Debian
the NSA310s isn't capable of kwboot only the NSA310 and NSA320by pengu - Debian
done, now the device is shown as still up (1000 baseT-FD) this doesn't change when U-Boot is up and running. pinging is now possible. when powering up, the green LED flashes shortly and goes of booting into debian makes the amber LED flashing when the driver is loadingby pengu - Debian