QuoteRemember, this box is the same SoC OX820 as the Pogo Pro V3. I was so focused to KD20 last weeks so that my searching was narrow-minded to Shuttle KD20 only and I didn't saw the things left and right the path :( You point me towards this again now! Your help is very appreciated, thank you very much!by Bastler - uBoot
Weekend is coming and it's time to go ahead, at least I would like to :) Booting via sata seems to be stable now, but the next steps, writing uImage into mtd0, I don't see any land for now. QuoteYou can flash u-boot to mtd0. And then fix the env at serial console prompt. Sounds easy but isn't (for me) :) Have to read so much more in the forum about the correct howto. If I loby Bastler - uBoot
here are the results. fw_printenv looks from beginning not such good, but may be, is at this point nevertheless ok? cat /proc/mtd dev: size erasesize name mtd0: 00e00000 00020000 "boot" mtd1: 07200000 00020000 "ubi" root@debian:~# cat /etc/fw_env.config # MTD device name Device offset Env. size Flash sector size Number of sectors # pogoplug pro /dev/mtby Bastler - uBoot
bodhi Would you say that this is what you could tell a 'clean boot' from sata now? There is no USB Drive plugged in, just the sata drive. (& Network cable and the serial cable) These are the (standard) envs used for this today: What's to do more before I can insert init=/bin/systemd and use LABEL now? And once more: A big thank you for your patience with me! OXNAby Bastler - uBoot
Had some problems with uInitrd but solved it and gave it a new try. Have to clean up some world-writable but this is secondary problem for now because I can repeat all the needed steps up to here again. I hope I'm soon at the point to try making the kd20 box booting without sata now? OXNAS> OXNAS> tftp 0x60000000 uImage Wait GMAC to reset Wait for PHY reset PHY is IC+ IP100by Bastler - uBoot
Ok, was (is) different as I thought. Had to look to QuoteUpdated 02 Aug 2017: Now I can boot into debian via tftpboot, but I have still to search about the HowTo write into the kd20 to make booting permanent. But for now I can say I'm happy I could reach this step, as it is, now. mkimage -A arm -O linux -C none -T kernel -a 0x60008000 -e 0x60008000 -n 'Linux-4-4-54-oxnas-tld-1by Bastler - uBoot
Yes, you are right, I didn't made this steps. Overlooked that while following instructions above. Will try that next days.by Bastler - uBoot
Ok, I tried to follow your instructions. In fact I use a sata disc I extracted the files from Debian-4.4.54-oxnas-tld-1-rootfs-bodhi.tar.bz2 to sda2 (rootfs). I append zImage + ox820-kd20.dtb to the new file uImage. Placed both files to my tftp folder. Started kd20 to menu. tftp uImage to 60500000 and tftp uInitrd to 61000000. bootm 60500000 61000000 got bad magic number. setby Bastler - uBoot
Ok bodhi, seems the last information was the winner for now. Quotebootm 0x60500000 0x61000000 System runs now to login :) And here I stumbled again :( I tried several logins and passwords I found, and know, but I can't find the right combination of login and pwd for this. OXNAS> tftp 61000000 uInitrd_w Wait GMAC to reset Wait for PHY reset PHY is IC+ IP1001LF Wait for linby Bastler - uBoot
No luck up to now. To answer your question: Quote1. So what is on the USB drive? is the rootfs on the 2nd partition? With the current bootargs that you have, rootfs mut be on sda2 I had nothing in sda2 so I extracted wheezy_rootfst.tar.gz to it. I had no usb-drive connected up to now. I added console to folder dev which let the 'run' a little bit longer, but it stopped as before.by Bastler - uBoot
bodhi, no success. I set the two envs, checked them via printenv and tried to erase. Result -> HW-reset as before. Little bit frustrating for now :) Meanwhile I played around and I tried to load the uImage to 60500000 and get this: tftp 0x60500000 uImage Wait GMAC to reset Wait for PHY reset PHY is IC+ IP1001LF Wait for link to come up...........Link up Wait for auto-negotiatby Bastler - uBoot
bodhi, seems I have none of these commands :( Version: U-Boot 1.1.2 (Jan 24 2015 - 13:54:11) OXNAS> help ? - alias for 'help' base - print or set address offset bdinfo - print Board Info structure beep - make beep sound bootm - boot application image from memory bootp - boot image via network using BootP/TFTP protocol clrenv - clear environment cmpby Bastler - uBoot
Didn't thought that printenv would be the right one for this. Ok, there is no such information as described. mtdparts is not supported. After doing the tftp 64000000 uboot.backup, printenv will throw out just a little more information as seen in second block here: //--------------- first start -------------------- OXNAS> printenv bootcmd=run beep select0 load loadr sysled bootby Bastler - uBoot
Check at this point, your envs should indicate whether you have mtd partitions and can access NAND. Sorry for asking, but how do I have to check this?by Bastler - uBoot
No it's not working, I run into next problems now. Costs me a lot of hours to made it possible to connect my notebook with the kd20 using tftpd-hpa. The moment I could ping both, I thought I could try to tftp uboot.backup. OXNAS> tftp 64000000 uboot.backup Wait GMAC to reset Wait for PHY reset PHY is IC+ IP1001LF Wait for link to come up...........Link up Wait for auto-negotiatiby Bastler - uBoot
thank you bodhi! But without all the infos here inside forum and your will to help I would not stay at this point now. And it's not the end of the story. I have to learn how to make the stock files permanent so the kd20 will run as before. I will try to follow Peacemaker post: Quotehttps://forum.doozan.com/read.php?2,17649,19426 Okay, then 1. boot form sata to Uboot 2. load your uby Bastler - uBoot
Update: I found this thread and followed instructions. I attached existing uImage and used the two other files from : Quotehttps://www.dropbox.com/s/82t5pfnybvacr3b/KD20_sata_boot.tar.gz?dl=0 Quotehttps://forum.doozan.com/read.php?2,17649,19426 This output comes while disk_create script is running: 0+1 Datensätze ein 0+1 Datensätze aus 444 bytes copied, 0,33572 s, 1,3 kB/s Writinby Bastler - uBoot
QuoteI think that 2nd HDD should be disconnected to make sure the bootROM reads the 1st one only. There is one sata_hdd only (sdd) which I placed into the right slot of the kd20. sdd1 is the unformated partition of size 10M. sdd2 is the second partition which is formated to ext3 but with no contents. As far as I can see disk_create script is writing something to sdd. But are these valueby Bastler - uBoot
Hope I hit the point now: I created a folder which contains stage1-, u-boot- and uImages- folder and the disk_create script and the three links. Folders got the files inside. @stage1.wrapped => stage1/stage1.wrapped-nand @u-boot.wrapped => u-boot/u-boot.wrapped @uImage => uImages/uImage Used an empty hdd (sdd), created the two partitions and formated the second. Festplatte /devby Bastler - uBoot
Getting some headache with my tries :( I need a little hint to come ahead. What I get always, now is: Stage-1 Bootloader 2012-06.13-13:06:32 Attempting to set PLLA to 750MHz ... plla_ctrl0 : 0x0000000A plla_ctrl1 : 0x000F0000 plla_ctrl2 : 0x001D01A0 plla_ctrl3 : 0x00000017 PLLA Set Setup memory, testing, Image 0 Failed to correct error Failed to correct error Hdr lenby Bastler - uBoot
Thank you bodhi for your quick reply. I assume that these files inside ox20-sata-uboot will work for my kd20 too? As far as I understand I will just have to use u-boot.img and u-boot-spl.bin out of the ox820-sata-uboot tar. While reading through many of the threads I'm more and more confused about the -HowTo- now... Starts with correct preparing the hdd to use the disk_create scriptby Bastler - uBoot
@crosser while playing around I bricked my kd20 a year ago. And sure, I made no backup that time :( Reading your post I thought this could be a way to unbrick my KD20 using sata_boot now. I followed your explanation above but run into problems. I can't manage to compile krefs u-boot source to get the 750MHz files, no way :( So my question, could you please offer all your (hopefullby Bastler - uBoot