Gravelrash Wrote: ------------------------------------------------------- > :))) if the vendor bought his parts from the local > recycler then possibly :))) > :)) then mine is possibly going to be. I need to find my multimeter somewhere in the "lab" :))) to see if the power supply is bad, let's hope so. 5V 2A is easy to find, I think. > if i remember corrby bodhi - Debian
The Buffallo LS-XL is in mainline u-boot. But it is a different SoC! so probably not close.by bodhi - uBoot
Look at this thread: http://forum.doozan.com/read.php?3,12381 Starting from here: Quote6. Erase mtd0 flash_erase /dev/mtd0 0 4 Expected output: Erase Total 4 Units Performing Flash Erase of length 131072 at offset 0x60000 done 7. Write image to NAND Among the nandwrite commands below, be extra careful and execute only one nandwrite command corresponding to your platform thaby bodhi - uBoot
protocold Wrote: ------------------------------------------------------- > Hi All, > > I have managed to get serial working on my buffalo > LS-WVL and here attached is the stock u-boot log. > Is there a replacement u-boot that I can try with > this device? Try UART booting with the NSA325 u-boot: QuoteLast Updated 19 June 2016 I've uploaded 2016.05-tld-1 Uby bodhi - uBoot
Thanks Joey & Ray for testing. Looks like in the new version I'll have to remove all my assumptions about the 88E1310 and do exactly what stock u-boot does. This is weird, because it's supposed to be the same as the 88E1318.by bodhi - Debian
Interesting note: Arch Linux ARM was affected the same way this site was by the DDoS. Both IP addresses must be somewhere in the DDoS IP address range!by bodhi - Off-Topic
Chuck, > I'm afraid you are talking over my level. The > uImage and env are from the result of the compile. > Where do you copy it to on the USB stick? I'm > thought I had to compile the uImage on the > Pogoplug. You don't need to compile anything. The rootfs 4.4 that you have created is a complete, basic Debian Linux system. The rootfs already contain theby bodhi - uBoot
JoeyPogoPlugE02 Wrote: ------------------------------------------------------- > I'd imagine they're a lot harder to return if > there's leftover solder where the pins go. All I > can ask is, are you sure the power supply is > working? 5v 3A, I don't see many of those in my > little world.Also when the TTY is hooked to the > pins, the lights mostly goby bodhi - Debian
> I wonder what the motive is behind it - there's > nothing here that steps on anyone's toes. It is not this site particularly at all. The forum is hosted by commercial provider servers in Atlanta. Their servers have been under DDoS attack most of Saturday. Perhaps someone is practicing for their real DDoS attack somewhere else later.by bodhi - Off-Topic
Damn these eBay vendors :) just had "another one bite the dust"! May be I bought the one that Gravelrash returned? :)). Got the box, this time I did not even open it yet (I want to observe the LEDs ligh behavior), just plugged in the power supply, turned on, and .... nothing, no power came into the board, completely dead. Please either PM me or post the link to eBay that you bought tby bodhi - Debian
> Will send a PR to LEDE soon with this fix and if > they don't accept it I'm going to find and > slaughter all their kittens. > :))by bodhi - uBoot
There was a massive DDoS attack on the server provider host in Atlanta.by bodhi - Off-Topic
I'd like to point out this fact for general consumption: FIT image and uImage are just the same kernel files inside being packaged a different way. The main advantage with FIT is you can sign your image, so it is more secure. But when it comes down to maintainability for us is no more or less works. - So there are drawback when you're hacking such as: less convenient when you'reby bodhi - uBoot
Quotebodhi Wrote: > You can now proceed to install u-boot if you feel > like doing. But if the rootfs is RO then you need > to copy u-boot image and uboot env image to the > USB drive first, offline. Chuck, install new u-boot for real. No need for any temporary measure.by bodhi - uBoot
Joey, > @ bodhi here's Test 1 MON > > U-Boot 2016.05-tld-2.6 (Sep 02 2016 - 01:00:09 > -0700) > Cisco ON100_K9 > > SoC: Kirkwood 88F6282_A1 > DRAM: 512 MiB > WARNING: Caches not enabled > NAND: 512 MiB > MMC: kwsdio: 0 > *** Warning - bad CRC, using default environment > > In: serial > Out: serial > Err: serialby bodhi - Debian
jlovell, This is the problem: QuoteNSA-jaynas01-console-boot-early-root-md-with-broken-eth.txt (18.4 KB) [ 0.000000] Linux version 4.4.0-kirkwood-tld-1 (root@tldDebian) (gcc version 4.9.2 (Debian 4.9.2-10) ) #1 PREEMPT Mon Jan 25 20:35:24 PST 2016 [ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f [ 0.000000] CPU: VIVT data cache, VIVT instructionby bodhi - Debian
> That's plain wrong, they still support many > devices with bootloaders that can only boot > uImage, and their toolchain still has the code and > tools to make uImages. :) that did not seem to register when I told habibie this.by bodhi - uBoot
mike, > loading envs from mmc 0 ... > 98 bytes read in 1089 ms (0 Bytes/s) > > no IDE devices available > importing envs ... > ## Info: input data size = 284 = 0x11C > ** Bad device usb 0 ** > ** Bad device usb 0 ** > Wrong Image Format for bootm command > ERROR: can't get kernel image! > resetting ... Looks like you have installed u-boot inby bodhi - uBoot
Please try this 2.6 version. I've mistyped some numbers in the code last time. Test 1: with ethernet cable connected to MON port Boot with kwboot, interrupt serial console version setenv ipaddr <IP address of the ON100> setenv ethaddr <the MAC address of the MON port> ping <your router IP> Test 2: with ethernet cable connected to LAN port Boot with kwboot,by bodhi - Debian
Was rootfs still mounted as RO? if it was, shutdown and bring this USB drive to your Ubuntu and check for error (if it was assigned sdb1) umount /media/sdb1 e2fsck /dev/sdb1 Also, pls attach serial console log while Linux is booting (entire serial console log is better). dmesg only shows the kernel messages, not everything. IOW, hacking Linux, there are things you can only see in serial cby bodhi - uBoot
rayknight Wrote: ------------------------------------------------------- > I've been sick for the last week, so just now > getting caught up with forum posts. I'll try the > latest version on my ON100 tomorrow night. > > Ray Glad you feel better! we need you to resume the party here :)by bodhi - Debian
> Remove the reset command from the end of your > dt_bootcmd_usb and it should proceed to run the > bootcmd_stock. > > Ray Right! there should be only one reset at the end of bootcmd.by bodhi - uBoot
Try this: Stop the booting process in serial console or netconsole: setenv bootcmd 'run bootcmd_uenv; if run dt_bootcmd_usb; then echo "booting Debian..."; else echo "booting stock..."; run bootcmd_stock; fi; reset' boot If this works, boot with USB or HDD into Debian, and set it for real: fw_setenv bootcmd 'run bootcmd_uenv; if run dt_bootcmd_uby bodhi - uBoot
JoeyPogoPlugE02 Wrote: ------------------------------------------------------- > I can somewhat understand a BIOS for allocating > video memory (such as the ThinClient I'm typing > on), where 128MB or 256MB can be absolutely spoken > for from the RAM allocation for video use, but as > for little Android boxes, I'm not sure about > anything when there doesnby bodhi - Off-Topic
Mr Dini Wrote: ------------------------------------------------------- > Thanks a lot! I'm in finish! :) The machine booted > up successfuly and it is working fast and stable. > > Awesome! Cool!by bodhi - Debian
Mike231 Wrote: ------------------------------------------------------- > Hello, > First of all, I would like to thank you for your > great contribution to pogoplug support. > I need your help. > My pogoplug is unfortunately bricked. > I can connect to my pogoplug mobile only via > serial port: ./kwboot -t -B 115200 > /dev/ttyUSB0 -b > uboot.2016.05-tld-1.pogo_by bodhi - uBoot
Chuck99 Wrote: ------------------------------------------------------- > Did kwboot as usual. Stop at PPV4> prompt. Did > copy paste this: setenv set_bootargs_usb 'setenv > bootargs console=$console root=$usb_root > rootdelay=$rootdelay rootfstype=ext3 $mtdparts' > boot > > no errors. also did a saveenv. Since uboot was > running in RAM I suppose tby bodhi - uBoot
red9r Wrote: ------------------------------------------------------- > Hmmm... It seems that they removed the header > shown in the picture of the linked thread. I guess > I'll have to break out the old soldering iron. Cool. So I forgot that damacc did post the serial pinouts!by bodhi - Debian
bodhi Wrote: ------------------------------------------------------- > > Also tried to change memory address for loading > > and starting, same results. > > > > Have you tried the standard memory address? > > > load_initrd_addr=0x1100000 > load_uimage_addr=0x800000 > > > This is way too low > > > NSA310> bootz 0x8000by bodhi - uBoot
I would not trust this uImage. QuoteBut it does not end here. I tried also with other uImages+appended-dtb generated by LEDE build system. NSA310> fatload usb 0 0x8000 lede-kirkwood-dockstar-uimage reading lede-kirkwood-dockstar-uimage 1871076 bytes read in 89 ms (20 MiB/s) NSA310> bootm 0x8000 Wrong Image Format for bootm command Error occured, error code = 112 ERROR: can'by bodhi - uBoot