Re: [U-Boot] Older u-boot mangles UBI from ubinize 1.5.2

It's all moot now! I accidentally wrecked my u-boot today. I typoed "nand write ${fileaddr} ${BOOTCONFIG_nand_addr} ${0x800}" When I meant "0x800" instead of the undefined "${0x800}", which u-boot translated to 0xacc. I guess I'm going to find out if that JTAG header works.

Re: [U-Boot] Older u-boot mangles UBI from ubinize 1.5.2

Hello Richard, Am 11.08.2016 um 11:51 schrieb Richard Weinberger: Hi! On Thu, Aug 11, 2016 at 4:26 AM, J Mo wrote: I tried re-flashing my UBI and tftpbooting my kernel before u-boot could ever get a chance to mangle it, and now I get much further, though I'm still not able

Re: [U-Boot] Older u-boot mangles UBI from ubinize 1.5.2

Hi! On Thu, Aug 11, 2016 at 4:26 AM, J Mo wrote: > I tried re-flashing my UBI and tftpbooting my kernel before u-boot could > ever get a chance to mangle it, and now I get much further, though I'm still > not able to mount my rootfs for unknown reasons: > > [3.772502]

[U-Boot] Older u-boot mangles UBI from ubinize 1.5.2

Greetings I am attempting to port LEDE/OpenWRT to a new device; the TRENDnet TEW-827DRU, which is a IPQ806X-based (AP148) system. It has a NAND flash for storage with a UBI (kernel + squashfs + ubifs). When my system attempts to attach the UBI, I see the following error from linux: [