[FS#3937] MR32 BCM53xx boot error

[OpenWrt Bugs]

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#3937 - MR32 BCM53xx boot error
User who did this - Christian Lamparter (chunkeey)

----------

> 
  [ 4.730000] find_itb_subimage: error finding kernel at 1: FDT_ERR_NOTFOUND
  [ 4.740000] find_itb_subimage: error finding ramdisk at 1: FDT_ERR_NOTFOUND
  [ 4.750000] find_itb_subimage: error finding fdt at 2: FDT_ERR_NOTFOUND

There's a comment on a merged series "scripts: mkits.sh: replace @ with - in nodes " that could explain these errors:

https://github.com/openwrt/openwrt/commit/5ec60cbe9d94b925393bea2a54bdaf062a28fece#commitcomment-53657902

> This also breaks the bcm53xx Meraki MR32, which relies on kernel at 1, ramdisk at 1, fdt at 2 being present in the dtb. I think we need to introduce a new option, which indicates the delimiter used DEVICE_DTS_REF_DELIMITER=@ for example, and default to -

"

the commenter also proposed a patch:

https://github.com/dmascord/openwrt/commit/eafa1545d68fcec88c002e124c30404dd40bf962

An option to verify that it's indeed what causes the device to refuse to boot would be to revert the patch+"build: use config-1 instead of config at 1 as default" (or try the proposed patch, which seems to do both).

Also, do you need help "unbricking" the device? Or can you get into a shell?
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=3937#comment9943

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.