Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FS#3937 - MR32 BCM53xx boot error #8934

Open
openwrt-bot opened this issue Jul 19, 2021 · 4 comments
Open

FS#3937 - MR32 BCM53xx boot error #8934

openwrt-bot opened this issue Jul 19, 2021 · 4 comments
Labels
flyspray release/21.02

Comments

@openwrt-bot
Copy link

openwrt-bot commented Jul 19, 2021

tbilan:

I have an MR32 I'm trying to flash. Following the instructions on https://openwrt.org/toh/meraki/mr32 I uploaded the initramfs successfully to part.safe. When rebooting the console has the following errors then boots back into the Meraki firmware:

[ 4.690000] Mapping 10362880 bytes for /dev/mtdblock/part.safe
[ 4.730000] find_itb_subimage: error finding kernel@1: FDT_ERR_NOTFOUND
[ 4.740000] find_itb_subimage: error finding ramdisk@1: FDT_ERR_NOTFOUND
[ 4.750000] find_itb_subimage: error finding fdt@2: FDT_ERR_NOTFOUND
[ 4.750000] kexec_raw: kexec_load: Cannot assign requested address
[ 6.490000] Mapping 10235904 bytes for /dev/mtdblock/part.old
[ 6.530000] Meraki-build is 23-191963

I built the initramfs from the current git master (7/18/2021). I also had someone on #openwrt-dev build it and I tried theirs and received the same errors.

@openwrt-bot
Copy link
Author

openwrt-bot commented Jul 19, 2021

chunkeey:

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

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

5ec60cb#commitcomment-53657902

This also breaks the bcm53xx Meraki MR32, which relies on kernel@1, ramdisk@1, fdt@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:

dmascord@eafa154

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@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?

@openwrt-bot
Copy link
Author

openwrt-bot commented Jul 20, 2021

tbilan:

I was able to unbrick. I booted into busybox and did a cp from part.old to part.safe and a reboot brought me back to the prompt and I reflashed initramfs from there.

The proposed changes worked so I suggest merging them in.

Another thing to note is that sysupgrade doesn't see it as a valid image so I had to --force to get it to work.

The MR32 performs poorly though (about 7Mbps). The ac chip (BCM43520) doesn't have a kernel driver so it's limited to the bg chip. This makes the device undesirable at this time. It does technically work though and it's better than nothing.

@openwrt-bot
Copy link
Author

openwrt-bot commented Sep 24, 2021

chunkeey:

A new (supposedly) fixed snapshot image is available from:

https://downloads.openwrt.org/snapshots/targets/bcm53xx/generic/

(sha256sum 0912b917026e913110573f9ba27b47ca102c214a93dffd74cfbf914ee26df02b)

@openwrt-bot
Copy link
Author

openwrt-bot commented Oct 1, 2021

chunkeey:

... Any reports? I would like to make a patch for 21.02 but I would like to know if the snapshot image is now working as intended?

Cheers
Christian

@aparcar aparcar added the release/21.02 label Feb 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
flyspray release/21.02
Projects
None yet
Development

No branches or pull requests

2 participants