[LEDE-DEV] WRT1900ACS - Kernel 4.4.12 boot failure

[Dheeran Senthilvel]

Hi,
	Yes even after I run resetenv followed by a reset command, the fw_printenv produces the same output every time. 

> On 07-Jun-2016, at 3:54 PM, Claudio Leite <leitec at gmail.com> wrote:
> 
> Hi,
> 
> * Dheeran Senthilvel (dheeranmech at gmail.com) wrote:
>> Hi,
>>       Thanks for the reply. But I already documented it in my previous
>> mails in May 2016.
>> This is temporary, once again when reboot is done the same error occurs.
> 
> I see, sorry for the noise.
> 
>> 
>>       I haven't been able to solve this issue. Also if altnandboot is
>> performed and used having lede in nandboot there seems to be no problem.
>> But once lede boots the error is imminent upon reboot.
> 
> I'm not sure I understand this part. Is the same image, with no custom
> settings, stored in both partitions?
Sorry for that! What I mean to say is if I boot ‘altnandboot’ (recovery official firmware) having lede in the primary_image partition, the problem doesn’t occur. Once I invoke nandboot and allow lede to boot and issue a reboot command, the error occurs. I gave this statement to clarify that the problem lede and not the 'hardware' or 'u-boot’.
> 
> What does fw_printenv look like after a "resetenv; reset" and boot into
> a recent LEDE? At that point, the linksys-recovery stuff will already
> have run.
But I really don’t understand the problem. This OpenWrt WiKi page - https://wiki.openwrt.org/doc/techref/bootloader/uboot.config , shows that this kind of error show only when the partition map is incorrect (That is what i understood) and as the following command shows that flash mapping recognised by lede is incorrect

root at WRT1900ACS:/# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00200000 00020000 "u-boot"
mtd1: 00040000 00020000 "u_env"
mtd2: 00040000 00020000 "s_env"
mtd3: 00100000 00020000 "devinfo"
mtd4: 02800000 00020000 "kernel1"
mtd5: 02200000 00020000 "ubi"
mtd6: 02800000 00020000 "kernel2"
mtd7: 02200000 00020000 "rootfs2"
mtd8: 02600000 00020000 "syscfg"
mtd9: 00680000 00020000 “unused_area"

whereas boot to altnandboot gives something like this

armada-nand f10d0000.nand: Initialize HAL based NFC in 8bit mode with DMA Disabled using BCH 4bit ECC
NAND device: Manufacturer ID: 0x01, Chip ID: 0xf1 (AMD/Spansion NAND 128MiB 3,3V 8-bit), 128MiB, page size: 2048, OOB size: 64
Bad block table found at page 65472, version 0x01
Bad block table found at page 65408, version 0x01
10 cmdlinepart partitions found on MTD device armada-nand
Creating 10 MTD partitions on "armada-nand":
0x000000000000-0x000000200000 : "uboot"
0x000000200000-0x000000240000 : "u_env"
0x000000240000-0x000000280000 : "s_env"
0x000000900000-0x000000a00000 : "devinfo"
0x000000a00000-0x000003200000 : "kernel"
0x000001000000-0x000003200000 : "rootfs"
0x000003200000-0x000005a00000 : "alt_kernel"
0x000003800000-0x000005a00000 : "alt_rootfs"
0x000000a00000-0x000005a00000 : "ubifs"
0x000005a00000-0x000008000000 : "syscfg"


> 
> -Claudio
> 
>> On 07-Jun-2016 3:27 pm, "Claudio Leite" <leitec at gmail.com> wrote:
>> 
>>> * Dheeran Senthilvel (dheeranmech at gmail.com) wrote:
>>>> Hi,
>>>>      Compiled build r504 followed by clean build. Still not clear what
>>> is causing the boot error mentioned previously in mailing list - May 2016.
>>> [snip]
>>>> 
>>>> auto_recovery_check changes bootcmd: run nandboot
>>>> Hit any key to stop autoboot:  0
>>>> ## Error: "nandboot" not defined
>>> 
>>> Have you tried the 'resetenv' command from u-boot?
>>> 
>>> resetenv- resetenv      - earse environment sector to reset all
>>> variables to default.
>>> 
>>> I haven't tried this on a WRT1900AC, but on the EA4500 (which has a
>>> somewhat similar u-boot) it correctly resets everything to default
>>> values. Given that your u-boot settings are gone one way or another (as
>>> your fw_printenv later shows) this might be worth a try.
>>> 
>>> -Claudio
>>>