Gaogao, Please post your serial boot log, dmesg, and fw_printenv.by bodhi - uBoot
Look in your log, if you have saved it, when you boot with stock kernel. If you don't have the log, then look for the MAC addr on the NSA325 case itself, or on the product carboard box.by bodhi - Debian
Ah! I've just realized that this Mac address you used does not look right! What is the real MAC address that you got on the box? try that one. etherwake 00:50:43:00:02:02by bodhi - Debian
InfoScav Wrote: ------------------------------------------------------- > stuck at a point! > > after changing the default password, i gave the > address of the Korean debian mirror to the the > 'sources.list' file. the shell seemed to then have > gotten stuck in an unending loop. i then closed > then. since then, whenever i open the shell, it > asks meby bodhi - Debian
Eike, I listed what I have done below. It is almost the same as you did. root@Nsa325:~# ethtool eth0 Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supported pause frame use: No Supports auto-negotiation: Yes Advertised link modes: 1by bodhi - Debian
@gaogao and others NSA320 users, Here is the latest U-Boot-2013.10 NSA320 for testing. Please test with UART if you have serial console, but do not flash to NAND yet until we have testers confirmation! Boot with UART: ./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2013.10-tld-1.nsa320.mtd0.kwb -p Note that you will see CRC error in environment. This is because the envs location this U-Bootby bodhi - uBoot
Eike, It does work for me with NSA325v2. Have you tried to use static IP? I wonder if it could be something to do with your router. If it's a static IP the MAC address should be correct all the time. And do you have bridge somewhere in your network?by bodhi - Debian
Sounds like you've misplaced the single quote somewhere. The correct syntax is: setenv usb_init 'run usb_scan; setenv usb_root LABEL=rootfs' The actual parameter to the kernel is mtdparts=41000000.nand:14m(boot),-(data). So the first mtdparts word is a text, the second is the variable (which has $ in front of the name). setenv mtdparts 'mtdparts=41000000.nand:14m(bby bodhi - Debian
shatterstar78 , You should do this: 1. Set the envs to scan USB drives (try this in serial console first, once it booted, set them in Debian using fw_setenv): usb_device=0:1 mtdparts=mtdparts=41000000.nand:14m(boot),-(data) 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; theby bodhi - Debian
shatterstar78, The problem is the rootfs drive was probably not device 0:1 dt_load_initrd=ext2load usb 0:1 $uinitrd_addr /boot/uInitrd dt_load_uimage=ext2load usb 0:1 $uimage_addr /boot/uImage When you have 2 USB drives attached, which ever was detected first is assigned 0:1, the other is 1:1. So you will need some logic in the envs to select the correct drive. The default envs are only thby bodhi - Debian
Thanks Gaogao! Yes, the EFI/GPT option is missing in this NSA320 U-boot build. I will upload another version.by bodhi - uBoot
InfoScav Quote> 2. update the uboot using Jeff's script. After this, it really does not matter whether you are going to go through with the installation of Debian on USB or not (2012 U-boot is already installed). Any new wheezy Kirkwood rootfs with kernel 3.x will work. So it is really a prudent beginner's step to do the complete installation just to see how it works. And then,by bodhi - Debian
PawelW Wrote: ------------------------------------------------------- > WIll this u-boot work in NSA 310? It might or might not. Each U-Boot needs to be built for that machine (different memory, frequency, …). The 310 and 320 are cousins so it might. I did not build U-Boot for the NSA310, becaus I never got feeback on the Kirkwood kernel and rootfs, so I thought there is no one interby bodhi - uBoot
I don't know any USB cable with that header. But you can use this adapter to make it USB A-female: http://www.dx.com/p/usb-a-female-to-mini-usb-5-pin-female-adapter-26780#.U_VL39m9K0dby bodhi - Off-Topic
gaogao & other NSA320 users, In reference to this NSA320 test U-Boot in this post: http://forum.doozan.com/read.php?3,12381,16787#msg-16787 If you have problem connecting UART, please try both ./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2013.10-tld-0.1.nsa320.mtd0.kwb and ./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2013.10-tld-0.1.nsa320.mtd0.kwb -p And watch the power button,by bodhi - uBoot
I'd say don't do it! you are risking to brick it for good. I would just drill a lot of holes on the bottom and raise the Dockstar with rubber feet. If you're obsessed :) how about using a thermometer to measure the temp after you've done that? if it's way under the Sheeva max operating temp then you should not worry?!by bodhi - Off-Topic
OK Warhead. Got to earn a paycheck right:)by bodhi - uBoot
FYI. 1st post was updated: QuoteReferences: U-Boot source code at GitHub (Latest branch 2014.07.b-kirkwood, tag v2014.07-kirkwood)by bodhi - uBoot
@Warhead, We also need to change the env location to 0xC0000, to be consistent with other Kirkwood U-Boot, and more importantly: common Kirkwood rootfs. ./include/configs/nsa325.h #define CONFIG_ENV_ADDR 0xc0000 #define CONFIG_ENV_OFFSET 0xc0000 /* env starts here */by bodhi - uBoot
Hi notmine, There is no need to step through, you can go directly to the latest kernel version 3.16 from those. After that, do apt-get update and apt-get upgrade to get the latest packages in wheezy. But always back up your rootfs first before doing these upgrades!by bodhi - Debian
I have not released it, since nobody has reported test result. Here is the UART booting version (not ready to flash to NAND): http://forum.doozan.com/read.php?3,12381,16787#msg-16787by bodhi - uBoot
You should be able to see what caused the problem booting in serial console. Do you have a log of that you can post here? As a temporary work around, you can backup the initrd in /boot to initrd-xxx.save, install, and if it fails to boot, restore it using a different Linux box, just use the old initrd for booting. And you could try to regenerate it manually with update-initramfs -uby bodhi - Debian
InfoScav, > > as in the tutorial from Jeff, do i need to follow > the 'updating uBoot' tutorial too, after removing > my presently attached pen-drive, or may i start > directly with the installation of debian on the > fresh pen-drive? Jeff's Squeeze script installs both U-boot and Debian. If you can't boot after running the script, post here. Someby bodhi - Debian
Mark, > http://blog.qnology.com/2013/10/pogoplug-e02-v2-se > rial-connection.html You have Pogo V3, which is different. The serial port might or migh not have different pins out (can't recall). I'll find it in my bookmarks and post it for you. Update: it does have same pins out. LED flashing green is always a good sight. If you don't see any flashing LED then it&by bodhi - Rescue System
Cool! it really helps to see the obvious problem so quickly when you have serial console.by bodhi - Debian
WarheadsSE Wrote: ------------------------------------------------------- > I looked at the patch. Most of these changes I > will make without issue. If it is really down to a > typo on the pin number, LOL. > > Some of these are a matter of white space changes, > which make either no sense, or are un-needed/don't > conform to the stylings in u-boot. By all meby bodhi - uBoot
See here about the NSA325 watchdog: http://forum.doozan.com/read.php?3,14697,17166#msg-17166 Once we got GitHub updated, I'll make a build from that version and release in the U-Boot thread. Atm, the testing build for UART booting is availabe if anybody is anxious to run it. Note: it should be executed without the -p option. kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2013.10-tld-1by bodhi - Debian
Attached here is the test patch for NSAxxx U-Boot.by bodhi - uBoot
Mike Wrote: ------------------------------------------------------- > I'm using the same USB drive that I used with > Arch. I can access it no problem on my Pi if I > need to make changes though. Already tried to set > a static IP address just in case it wasn't pulling > DHCP when debian started. Do you have serial console or did you set up netconsole?by bodhi - Debian
I see, we need to remove the mask to make mtd0 writeable then.by bodhi - uBoot