[LEDE-DEV] [PATCH] ipq806x: Add nand boot support for ipq40xx AP-DK04.1-C1
Ram Chandra Jangir
rjangir at codeaurora.org
Mon May 8 09:54:00 PDT 2017
Hi Christian,
>Hello,
On Saturday, May 06, 2017 11:24 PM Christian Lamparter wrote:
>On Friday, May 5, 2017 9:19:36 PM CEST Ram Chandra Jangir wrote:
> This change add nand boot support for IPQ40xx based
> AP-DK04.1-C1 board using ubi image, also add sysupgrage support for
> AP-DK04.1-C1 and generates a sysupgrade.tar image.
>
> Testing:
> *Tested on IPQ40xx AP-DK04.1-C1 and IPQ806x AP148 Board:
> a. NAND boot
> b. ubi sysupgrade
>
> Signed-off-by: Ram Chandra Jangir <rjangir at codeaurora.org>
>Thanks for posting this.
>Chris Blake is currently in the process of adding the Cisco Meraki MR33.
><https://github.com/riptidewave93/LEDE-MR33>
>The MR33 uses the IPQ4029 and has just a Spansion S34ML01G200TFV00 128MiB
NAND Flash for storage.
>He reported that with this patch attached. The driver is loading, but it
can't access the nand:
>[ 0.860703] nand: second ID read did not match 7f,7f against 01,71
>[ 0.861633] nand: No NAND device found
>The id is supposed to be 01 (manuf = Spanion), f1 (128MiB).
>both readings are bad.
>I think this is caused by two problems:
>1. 7f, 7f should be 0xff, 0xff. 0x71 should be 0xf1.
>2. It seems that the NAND chip was not ready on the first read.
>I strongly suspect (due to the MSB error for BIT 7), that at least one I/O
line is missing due to a bad pinctrl/mux setup.
>Could you please add the pinctrl nand definitions to the dts so he can test
again?
>Regards,
>Christian
IPQ4019 (ex. AP-DK04.1-C1) boards will have nand boot mode with a dedicated
jumper settings. Based on nand boot jumper settings change, HW will
automatically take care of initializing the nand_pins mux at boot time.
That is why we don't need to do initialization of pinmux in ipq4019 kernel
boot/dts. Currently I don't have Cisco Meraki MR33 board with me to give a
try.
I will give a try for nor-nand boot on ipq4019 with pinmux initialization
and will update you, if it helps you.
Thanks,
Ram
More information about the Lede-dev
mailing list