bodhi Wrote: ------------------------------------------------------- > Interesting. But it's a good learning exeperience > with JTAG. It would be nice if you can post your > JTAG unbricking log and parts, setup …. :) when > you find the time to do it. Yes, I will do if I find some time. For most steps howto's are already available. For the time being: I've takby shv - uBoot
shv Wrote: ------------------------------------------------------- > bodhi Wrote: > > ------------------------------------------------------ > > @shv, > > > > uboot.2014.07-tld-1.goflexnet.bodhi.tar is the latest U-Boot and I'm running it on my GoFlex Net. > > Did you keep the log? I can take a look to see if you've missed anything. > > Iby shv - uBoot
I never used netconsole with SATA booting because I have a serial interface connected always. You can try to add the following line to your u-boot.env: preboot = run preboot_ncby shv - uBoot
Using vim to edit the u-boot.env is not OK. I never used mkenvimage. The boot environments are written by uboot to the ext4 partition. Can you please provide a boot log and boot env setting which you get with the serial console? But I think you don't have a serial adapter cable. Due to the LED it seams that the kernel is loaded but a Reset occurs afterwards. -shvby shv - uBoot
@morph027: you can find the necessary files (uboot.img, uboot.env, uboot-spl.bin) for SATA booting in the following message: http://forum.doozan.com/read.php?3,16017,17297#msg-17297. If you want we can discuss this topic in the uboot thread. -shvby shv - Debian
bodhi Wrote: ------------------------------------------------------- Quote** File not found /boot/dts/ox820-pogoplug-pro.dtb ** This is no problem just an output of the if condition. In this case bootm 0x60500000 0x60e000 is executed but the 2nd address is wrong. It must be bootm 0x60500000 0x60e00000 instead. I will try what occurs if I change this... With this little change the 2.6.31.14by shv - uBoot
@bodhi, I created a kernel with ramdisk. But it doesn't start somehow. It stops after veryfying the checksum of uImage. Reset IDE: Bus 0: OK Device 0: Model: ST9500325AS Firm: 0002BSM1 Ser#: 5VEKYXGQ Type: Hard Disk Supports 48-bit addressing Capacity: 476940.0 MB = 465.7 GB (976773168 x 512) 2346684 bytes read in 520 ms (4.3 MiB/s) 2567509 byby shv - uBoot
Looks that you have a device which does not support UART booting. In this case the only way is a JTAG interface to recover your device. I also have a Goflex Net device with boot ROM v 1.11 which does not support UART booting.by shv - uBoot
It seams that using root=LABEL=rootfs in bootargs doesn't work for the old 2.6.31.x kernels where just uImage is available. Does this behavior belongs to the missing uInitrd? Is there any way to solve this somehow with changes in bootenv? Otherwise booting from USB with IDE drive present doesn't work. The follwoing skript can be used to deactivate SATA booting without any damage of pby shv - uBoot
@bodhi, thank you for the explanation. I wasn't aware of this. A possible solution: usb_boot= ext2load usb $usb_device 0x60500000 /boot/uImage; if ext2load usb $usb_device 0x60e00000 /boot/uInitrd; then if ext2load usb $usb_device 0x62c00000 /boot/dts/ox820-pogoplug-pro.dtb; then bootm 0x60500000 0x60e00000 0x62c00000; else bootm 0x60500000 0x60e00000; fi;by shv - uBoot
@bodhi, tanks for your answer. 1. To seperate sets of boot envs: I want to prevent switching between seperate boot env sets. 2. label rootfs: good proposal - will try to use this 3. Not completed - I don't understand why: I tried booting ftd kernel and this works well - bootm 0x60500000 0x60e00000 0x62c00000 is included. Isn't it complete? I am not sure with bootargs becaby shv - uBoot
@bodhi, I am trying to make the boot environment more flexible with the following goals: 1. boot chain: (ide), usb, flash -> ide booting not available yet 2. booting of different kernels a) uImage, b) uImage and uInitrd, c) uImage, uInitrd, dtb Can you please have a look at my boot env for possible improvements? autoload=no baudrate=115200 boot=bootm 60500000 boot_stock=run loaby shv - uBoot
bodhi Wrote: ------------------------------------------------------- > @shv, > > That's a nice 19% performance improvement!!! > > Which kernel are you running? can you change other > u-boot envs? This u-boot uses the same env > location as the stock env, so it should not change > any of the envs. However, steps 8 and 9 flashes a > default set of envs, dby shv - uBoot
I have successfully flashed the uboot. It seams to be not possible to keep the old uboot environment. It might be overwriten or located at a different address. fw_printenv is working with the new uboot and its environment. blparam does not work anymore. I tried to change the ethaddr with fw_setenv without success. ~# fw_setenv ethaddr Can't overwrite "ethaddr" In the boot consoby shv - uBoot
@bodhi, CPU Benchmark 2.6.31.6@700MHz with USB Stick sysbench --test=cpu --cpu-max-prime=2000 --num-threads=2 run sysbench 0.4.12: multi-threaded system evaluation benchmark Running the test with following options: Number of threads: 2 Doing CPU performance benchmark Threads started! Done. Maximum prime number checked in CPU test: 2000 Test execution summary: totaby shv - uBoot
@bodhi: what performace tests should I do before I flash the new u-boot-spl.bin? You can find some performance data for 700/850MHz in the followin topic: http://pogoplug.square7.de/forum/viewtopic.php?f=4&t=13#p14 -shvby shv - uBoot
@bodhi, I used WarheadsSE stage1 loader with 850MHz for a long time. Now I am using my own 2013.10 u-boot-spl.bin file with 850MHz which is prepared for SATA booting on HD drive. No I did'nt run the new NAND u-boot with 800Mhz stage1 yet. In NAND I currently have WarheadsSEs kernel. Will try the 850MHz u-boot-spl Flash image later. -shvby shv - uBoot
Bodhi, yes, 850MHz works stable. I am using this frequency since more than 1,5 years 24/7. -shvby shv - uBoot
Hello Bodhi, after I am already using the uboot on my SATA disk. Now I want to try to flash it. Can you please provide a uboot-spl.img for 850MHz? Can you please write how to backup flash areas to be able to use them for recovery if neccessary some time? -shvby shv - uBoot
bodhi Wrote: ------------------------------------------------------- > @shv, > > uboot.2014.07-tld-1.goflexnet.bodhi.tar is the > latest U-Boot and I'm running it on my GoFlex Net. > Did you keep the log? I can take a look to see if > you've missed anything. > > I hope you did not flash the archive itself? I don't have a log. But I am sure thatby shv - uBoot
I flashed the older uboot.2014.07-tld-1.goflexnet.bodhi.tar yesterday to my GoflexNet device. All steps were OK. Now the device does not boot anymore after reset. No light is blinking and nothing occur on serial connection. I am waiting for delivery of JTAG interface now because my device is not able to boot from USB with kwboot.by shv - uBoot
Booting from internal FLASH with removed magic dust was possible. But the partition structure of the device was also destroyed.by shv - uBoot
You could check network and drive throughput separetly: 1. Network throughput: with netio on NAS and PC/Mac -> TCP/UDP 2. Drive throughput: with dd write:dd if=/dev/zero of=/media/usb0/test.tmp bs=500K count=1024 read: dd if=/media/usb0/test.tmp of=/dev/null bs=500K count=1024 copy: dd if=/media/usb0/test.tmp of=/media/usb1/test.tmp bs=500K count=1024 With these data you can seeby shv - Debian
If I want to remove the magic dust I must use the following command? perl <<EOF | dd of="$disk" bs=512 print "\x00" x 0x200; EOF If I have some time I will try to boot from FLASH with a "clean" SATA drive attached.by shv - uBoot
@bodhi, I was never able to boot from flash if a SATA device was connected. The device detected the SATA drive and tried to boot from it and never started booting from flash. I am not sure if I had to wait longer but it seamed to last forever even with new SATA drives. Maybe the drive must be prepared somehow to stop the SATA boot processing and jump to flash booting but I don't know how.by shv - uBoot
zzbao Wrote: ------------------------------------------------------- > Does this version of uboot support > connecting a sata drive used for data only? No! But if you put the right stage1 bootloader and the right uboot to your SATA drive it might boot with them. You can't use the files which are provided here for Flash install. Moreover you must put the stage1 bootloader to yourby shv - uBoot
@bodhi, I found the reason for the problem with network not available due to "Configuring network interfaces...SIOCSIFHWADDR: No such device". It could occur that a wrong or different MAC address is registered in /etc/udev/rules.d/70-persistent-net.rules. To solve the problem it is just necessary to remove the line(s) form the file. -shvby shv - Debian
As far I read the GBit is connected to USB2.0 which limits the speed to 30MB/s. -shvby shv - Allwinner A10
My rootfs is compatible to the ALARM kernel and stock uboot in flash. You can see in you log is that a kirkwood kernel is loaded. You should use the rootfs form bodhi instead of mine Because you have already his new uboot. You can find it here in this forum.by shv - uBoot
Which uboot and which kernel are currently on the device? With the old uboot the netconsole doesn't work. With the old kernel you must use blparam instead of fw_setenv! If you have the old ALARM uboot and kernel image in the flash you could use my Wheezy rootfs: http://pogoplug.cwsurf.de/forum/viewtopic.php?f=5&t=114 -shvby shv - Debian