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.
On 08/11/2016 04:28 AM, J Mo wrote:
Hm, I just found another example. I don't know why this didn't turn up
in my searches yesterday since it's a perfect match with the EXACT
error. This too was on a QSDK AP148:
https://patchwork.ozlabs.org/patch/509468/
I think I'll g
I got that good old feeling... like I just jumped onto a bag of flaming
poo. Ha ha
On 08/11/2016 03:40 AM, Daniel Golle wrote:
Understandable. However, we also need to experiment and figure out the
mess left behind by $vendor which often doesn't leave a lot of
reasonable options for 3rd-p
On 08/11/2016 05:31 AM, Daniel Golle wrote:
That's what I told you in the previous mail, removing the rootfs=
parameter from the dts should do the trick, because you just cannot
mount a ubi device (which is a character device in Linux) with a
block-based filesystem (like squashfs). This cannot
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:
[
5 matches
Mail list logo
