I've attached the configuration of my uEnv.txt file, as well as screenshots showing where I have everything located.by Wrecktify - uBoot
bodhi Wrote: ------------------------------------------------------- > :)) > > Acoording to my post (above that post), uEnv.txt > should work with tld-4 version. > http://forum.doozan.com/read.php?3,16017,20193#msg > -20193 I can't make out why this isn't working......I have uEnv.txt located at /boot/uEnv.txt, and I've created it as root, and copied vby Wrecktify - uBoot
bodhi Wrote: ------------------------------------------------------- > Here you go: starting from this post, see if any > good info. > > http://forum.doozan.com/read.php?3,16017,20204#msg > -20204 Thank you Bodhi, I wasn't even paying attention to the revision of U-Boot I was running (I thought I was on 1 and not 4), so that may put me in a better spot than I thougby Wrecktify - uBoot
bodhi Wrote: ------------------------------------------------------- > > There is a really easy way to recover (uEnv.txt). > But you are running an older unreleased version of > my uboot, so I forgot if I have added this > capability to this version (the 2015.10 version > has this). > > See the instruction for my uboot 2015.10 about > uEnv.txt. And try thatby Wrecktify - uBoot
bodhi Wrote: ------------------------------------------------------- > > Let's try one last time on Linux Mint. Use picocom > to run serial console, don't use any thing else. > > > This take more works than serial console: > > - open the box > - buy matching SATA cable > - Buy HDD if not having one > - connect to an eSATA enclosure withby Wrecktify - uBoot
bodhi Wrote: ------------------------------------------------------ > > Not the same as before. Last boot, the drive was > not even recognized by u-boot. This boot, the > kernel has loaded and attempted to run. > > Probably the reason it could not run was because > the u-boot env for bootargs was wrong. So we are > back to the orginal starting point. And to solby Wrecktify - uBoot
bodhi Wrote: ------------------------------------------------------- > Wrecktify, > > Ok this problem should be easy! plug in your USB > rootfs to the port in the back (next to the > ethernet port), boot up and post serial log. Freshly formatted Linux Mint 18.1 (had to reinstall completely, I was using 14 and it was WAY outdated), freshly formatted flash drive (ext3), fby Wrecktify - uBoot
bodhi Wrote: ------------------------------------------------------- > > Try loop back your TX and RX on the converter. > Type something and it should echo back. This at > least solves 1/2 of the problem. > > There are too many posts so it is hard for me to > keep track of what you have done :) is the serial > console log in the 1st post good to use as a > rby Wrecktify - uBoot
daviddyer Wrote: ------------------------------------------------------- > Do you have net console enabled? You are lucky if > you have. That Uboot version has a working NC > while the latest version doesn't. Try net console > see if you can stop uboot, then set the location > for dtb file, saveenv, try to boot the 3.17 kernel > debian. > > If net console isby Wrecktify - uBoot
Also to add, this is an OXNAS box, not Kirkwood. Rootfs I'd assume would be different between the 2. I just loaded my converter via Linux Mint and used screen to monitor the output and while I can see everything fine, still no transmit, so I can't interrupt the boot process. Grrr this is so frustrating... The rootfs I have on the flash drive is brand new, it's never been ruby Wrecktify - uBoot
daviddyer Wrote: ------------------------------------------------------- > Just download a bootable Linux iso, burn it to usb > or CDROM disc, boot linux system with your windows > machine, now you can make the rootfs > for your plugs. > > It doesn't have to be in Kirkwood / OX820 > environment to make rootfs for Kirkwood / OX820. Right, so to give you someby Wrecktify - uBoot
daviddyer Wrote: ------------------------------------------------------- > I think you can try from the most simple one > first: > > 1 Use a new flash drive or usb hard drive. > 2 Make a new rootfs on the new usb drive > 3 Try to boot with the new drive. > > > USB flash drive is not reliable. After a few years > (maybe one or two, or longer), it will diby Wrecktify - uBoot
bodhi Wrote: ------------------------------------------------------- > It should accept input if the connection is > correct. Check the Pogo serial header wire RX and > your serial connverter TX. So, I've played and played with this thing, such as swapping wiring out and trying a different PC and different terminal emulation software, and I cannot get transmit to work going tby Wrecktify - uBoot
I'll double check my wiring, but I am at least getting data back from the PP, so I'd assume GND and RX on the converter match up to GND and RX on the PP, may just be a loose wire for RX on the PP to TX on the converter. If I can sort that out, I'll get you the envs so we can figure out what's going on. That's been my suspicion, that something got mucked up with them.by Wrecktify - uBoot
Hey folks, New to the forums here, so forgive my ignorance with what I'm doing with my PogoPlug. Long story short, I've got a box that has the 2013.10-tld-4 U-Boot installed (seems I upgraded it properly at the time), but I believe due to a number of factors that went wrong with everything thereafter (U-Boot envs, amongst others), I can't get the thing to boot. Initially,by Wrecktify - uBoot