WS-AP3825i factory initramfs crashes "ft_fixup_l2cache: FDT_ERR_NOTFOUND"

Installing and Using OpenWrt
1

Initial install on brand new Extreme Networks WS-AP3825i fails to boot. Followed the instructions on the table of hardware page.
The image loads but crashes.

U-Boot 2010.12.6 (Mar 09 2016 - 19:56:30) (primary)
openwrt-24.10.0-mpc85xx-p1020-extreme-networks_ws-ap3825i-initramfs-kernel.bin
---------------------------------------
TFTP from server 192.168.0.11; our IP address is 192.168.0.105
Filename 'initramfs.bin'.
Load address: 0x2000000
Loading: ###################...
done
Bytes transferred = 8105992 (7bb008 hex)
## Booting kernel from FIT Image at 02000000 ...
   Using 'config-1' configuration
   Trying 'kernel-1' kernel subimage
     Description:  POWERPC OpenWrt Linux-6.6.73
     Type:         Kernel Image
     Compression:  uncompressed
     Data Start:   0x020000ec
     Data Size:    8091484 Bytes = 7.7 MiB
     Architecture: PowerPC
     OS:           Linux
     Load Address: 0x01500000
     Entry Point:  0x01500000
     Hash algo:    crc32
     Hash value:   2fccfc4e
     Hash algo:    sha1
     Hash value:   7529816b730b9a9627d08113b8ca3fd86cdaf0bf
   Verifying Hash Integrity ... crc32+ sha1+ OK
## Flattened Device Tree from FIT Image at 02000000
   Using 'config-1' configuration
   Trying 'fdt-1' FDT blob subimage
     Description:  POWERPC OpenWrt extreme-networks_ws-ap3825i device tree blob
     Type:         Flat Device Tree
     Compression:  uncompressed
     Data Start:   0x027b7998
     Data Size:    12574 Bytes = 12.3 KiB
     Architecture: PowerPC
     Hash algo:    crc32
     Hash value:   95b2a45c
     Hash algo:    sha1
     Hash value:   0fc127433f710e00617e9ce2ba65c36fd7ded240
   Verifying Hash Integrity ... crc32+ sha1+ OK
   Booting using the fdt blob at 0x27b7998
   Loading Kernel Image ... OK
OK
   Loading Device Tree to 03ff9000, end 03fff11d ... OK
ft_fixup_l2cache: FDT_ERR_NOTFOUND
2

Does it crash w/ 23.05.5 as well?

3

Thanks, that worked fine. I had tried a few earlier releases which did boot, but didn't have enough ram available to download the image for sysupgrade.

4

Did it sysupgrade to 24.10.0?

5

sysupgrade to 23.05.5 worked fine.
Just tried sysupgrade to 24.10.0. No joy, I'll give it another try later.

6

sysupgrade to 24.10.0 worked!
Thanks for the help.

7

Same issue here, but a sysupgrade also didn't work.

8

I just flashed 3 from 23.05.5 to 24.10.0 and all worked. They take anywhere from 10-15min to complete.

@Mawoka were you trying to do the same or were you trying to flash a new device?

10

For how long did you wait at this step? Mine just hung there.

11

10-15 minutes

12

Oh, wow. Then I may have just been too impatient. I'll try again

13

Yes. Waiting did the trick, thanks!

14

I thought the first one failed because I no longer saw any output on the serial port. Seemed like more than ten minutes before it completed.

15

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.