kalehrl, > The log is basically the same as the above one > just with U-Boot-2016 in the header: Please repeat what I suggested above: https://forum.doozan.com/read.php?3,26562,46214#msg-46214 and post the entire serial console log here.by bodhi - uBoot
Try this: setenv bootargs_linux 'console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=orion_nand:0x100000(uboot),0x80000(uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(rootfs1),0xA00000(kernel_2),0x2FC0000(rootfs2) earlyprintk=serial' setenv bootcmd_linux 'setenv bootargs $(bootargs_linux); mw.l f1010100 0020c000; usb reset; eby bodhi - Debian
daviddyer Wrote: ------------------------------------------------------- > Set it and forget it, then enjoy it and no "why". > Merry Christmas! :)) Right on.by bodhi - uBoot
lolinger, > BTW: I noticed that no bootargs are specified. I > guess the kernel needs further information about > the rootfs. Yes indeed! Try this additional env: setenv bootargs_linux 'console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=orion_nand:0x100000(uboot),0x80000(uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(by bodhi - Debian
kalehrl, Don't run kwboot. The instruction above is for u-boot-2016.06-tld-1. Just let it boot normally, and interrupt serial console.....by bodhi - uBoot
lolinger, > Thank you. I entered and saved your command. > However, now it is booting from NAND, not USB: That's because your envs were never set up to boot both USB and stock properly. This bootcmd forces the boot process to always boot stock. bootcmd=nand read.e 0x2000000 $(kernel_addr) 0xA00000; bootm 0x2000000 To verify the bootcmd_linux works: power up, interruptby bodhi - Debian
Log into Debian and get output of: dmesg cat /proc/mtd fw_printenv Please post these output here inside code tags. If I cannot see the solution after examining the above output, then there must be something in your own system that has prevented it. Nobody else has this problem with the new DTB. Since I don't have access to my Dockstar, I will need a different user to confirmby bodhi - uBoot
kalehrl, > This is with the older, installed u-boot: > U-Boot 2016.05-tld-1 (Jun 12 2016 - 14:06:08 > -0700) > HP Thin Client T5325 When you installed this u-boot 2016.05-tld-1 version, you have missed a step, and did not install the default envs image Quote5. Flash u-boot default envs to mtd0. cd /tmp/sdb1/boot flash_unlock /dev/mtd0 flashcp -v uboot.2016.05-tld-1.by bodhi - uBoot
The correct command is setenv bootcmd_linux 'setenv bootargs $(bootargs_linux); mw.l f1010100 0020c000; usb reset; ext2load usb 0:1 $(loadaddr) /boot/uImage; ext2load usb 0:1 0x01100000 /boot/uInitrd; bootm $(loadaddr) 0x01100000' However, there might be some problem with your u-boot envs. So let's see what you have. Power up, interrupt serial console and printenv Poby bodhi - Debian
Connect serial console and let it boot. Log into Debian and cat /proc/mtd fw_printenv Post the entire serial console log (from u-boot banner up until this point).by bodhi - uBoot
lolinger Wrote: ------------------------------------------------------- > Hi bodhi, > > I am trying to find the correct settings for > NSA325-v2 stock bootloader. I've formatted a > USB-Stick with a single ext3 partition, the kernel > is in the folder /boot. I managed to boot from a > ext2 partition that contains only the kernel > image, rootfs is on the secby bodhi - Debian
edinger, > When I tried to set ethaddr directly in uboot > (netcat) I got a strange output Think about it. netcosnole relies on the MAC address to establish network connection. So you should not able change it while connecting with netconsole. Changing the ethaddr in Debian should be OK. After you reboot, u-boot will read the ethaddr env and then establish network connection.by bodhi - uBoot
kalehrl, Your envs probably messed up. And with this uboot, you should not have to enter any new envs to boot with USB. So, Interrupt serial console at countdown U-Boot 2016.05-tld-1 (Jun 12 2016 - 14:06:08 -0700) HP Thin Client T5325 SoC: Kirkwood 88F6281_A1 SPI: ready DRAM: 512 MiB WARNING: Caches not enabled SF: Detected MX25L8005 with page size 256 Bytes, erase size 64by bodhi - uBoot
bernd Wrote: ------------------------------------------------------- > Thank you, Bodhi and Raffe, for your analysis. > > Changing the uInitrd load address from 0x1100000 > to 0x2100000 helped me to boot kernels > 4.10.9 > which didn't work before. > > Bernd Cool!by bodhi - Debian
kalehrl, This problem is quite simple to solve. I'll be back to post some corrected instruction.by bodhi - uBoot
kalehrl Wrote: ------------------------------------------------------- > Hi bodhi > It's me again. :D > I'm trying to update uboot but it doesn't work. > When I run flash_unlock /dev/mtd0 I get: > > flash_unlock: error!: could not unlock device: > /dev/mtd0 > > error 95 (Operation not supported) > > Any ideas what may be cby bodhi - uBoot
edinger Wrote: ------------------------------------------------------- > Hi bodhi, > > sorry, that I missed this step. > I worked through your description and did step by > step again: unpacking, installing, unpacking dts, > building uImage, uInitrd. Now it uses the currents > dts, but still the error occurs. > > root@nas:~# fw_setenv ethaddr 00:10:75:1A:DD:by bodhi - uBoot
joerg_999 Wrote: ------------------------------------------------------- > bodhi, that worked, your new bootcmd_exec did it. > - could maybe implemented fix in the next > uenvs... > - thank you very much again. > joerg_999 Cool! Yes, that will be in the next released default envs image.by bodhi - Rescue System
Added to the Wiki thread. QuoteUnder/Over the hood Modding Reset button for Pogoplug V3 (OXNAS)by bodhi - Debian
edinger, > I installed your rootfs > Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2 > on another usb stick and with that I was able to > set ethaddr. Could it be that my Debian wheezy > installation is somehow too old? No. As I said, your DTB is too old: root@nas:~# ls -l /boot/dts/kirkwood-dockstar* -rw-r--r-- 1 root root 10180 Feb 6 2015 /boot/dts/kirkwood-doby bodhi - uBoot
Boot into Debian and fw_setenv bootcmd_exec 'if run load_uimage; then; if run load_initrd; then if run load_dtb; then bootm $load_uimage_addr $load_initrd_addr $load_dtb_addr; else bootm $load_uimage_addr $load_initrd_addr; fi; else if run load_dtb; then bootm $load_uimage_addr - $load_dtb_addr; else bootm $load_uimage_addr; fi; fi; fi' Reboot. Interrupt serial console and removeby bodhi - Rescue System
edinger, > Ok, I will proceed with this and keep you > informed. > Here > the description differs. There is no 4a or 4b, > just4 and I skipped it. > > 4. Create uImage with embedded DTB for booting > with older u-boots (2012 or earlier). Skip this > step if you have installed the latest U-Boot for > Kirkwood (or are installing this u-boot at the > saby bodhi - uBoot
Yes. Your u-boot envs need some further setup. Let me write a new env to do that shortly.by bodhi - Rescue System
edinger Wrote: ------------------------------------------------------- > I unpacked the dts files, build uImage with the > following commands (as described in Step 4) again > and rebooted. > Same problem. > Should I build it without dts file? It was unclear > how, because when I skip step 4 I have no uImage > file. This indicated that you have not installed the kerby bodhi - uBoot
Quoteif i am on LEDE i cant do a reboot (soft reboot) - cold reboot unplug - plug again works perfect. What you do get when you do a reboot from LEDE? please post the entire serial console log for this case.by bodhi - Rescue System
jgkempen Wrote: ------------------------------------------------------- > Thanks for your help. I got it working again Cool!by bodhi - Debian
edinger, You're running the latest kernel 4.14.1, but you did not install the latest DTB in step 2 during kernel installation: Quote2. Extract the kernel and the DTB files in the archive: cd /boot tar -xjf linux-4.14.1-kirkwood-tld-1-bodhi.tar.bz2 tar -xf linux-dtb-4.14.1-kirkwood-tld-1.tarby bodhi - uBoot
edinger Wrote: ------------------------------------------------------- > reboot worked, but i get same error when setting > ethaddr after booting into debian. > I also tried with /boot/uEnv.txt. No effect. > Then with update to newest kernel: > > root@nas:~# uname -a > Linux nas 4.14.1-kirkwood-tld-1 #1 PREEMPT Wed Nov > 22 23:38:14 PST 2017 armv5tel GNU/Linuxby bodhi - uBoot
jgkempen Wrote: ------------------------------------------------------- > I am pretty sure the problems are unrelated to my > samba installation, but for the drive I was using > for samba had its partitions resized using gparted > on Lubuntu on an X86 machine. That drive was > formatted in NTFS as I needed to maintain the > ability to plug it into a windows machine ifby bodhi - Debian