@mrahul said in OM2+ getting stuck in boot stage with custom firmware using b255: Should we see the same behavior if we use the binary downloaded from the Onion FW Repo? No, my previous comment does not apply to firmware in the Onion firmware repo - these firmware images are already compiled and should contain everything needed. So devices with mac addresses that start with 40:A3:6B should boot and operate properly when flashed with any firmware from the Onion firmware repo. Devices with mac address addresses starting with 88:1E:59 will boot and operate correctly when flashed with firmware b255 and higher. I've confirmed this with devices I have on hand Device with 40:A3:6B mac address running firmware b254: Device with 40:A3:6B mac address running firmware b259: Device with 88:1E:59 mac address running firmware b256: @mrahul said in OM2+ getting stuck in boot stage with custom firmware using b255: However, we only use two methods, i.e. through ethernet or syupgrade to upgrade or re-flash a device on bricking. How different are these two processes? For a device that boots into linux successfully, upgrading the firmware thru sysupgrade and thru ethernet with the bootloader will have the same effect. As long as sysupgrade is run with the -n option to overwrite the existing configuration and filesystem. For a device that cannot boot into Linux, we recommend reflashing the firmware with ethernet thru the bootloader. @mrahul said in OM2+ getting stuck in boot stage with custom firmware using b255: Lately, we've started seeing the same behavior again with b255 where it gets stuck in the boot process. Does this mean the firmware sometimes works and sometimes doesn't? This could point to something in the hardware design impacting the boot sequence. Do you use any SPI devices? Do you follow the bootstrapping pins guidelines in your hardware? My recommendation Since you mentioned you're using the through-hole Omega2+, we can try to isolate where the issue is coming from. I recommend doing the following: Remove an Omega2+ device from your custom board Plug it into an Onion Expansion Dock with an Ethernet Expansion Use the bootloader + ethernet to flash firmware b259 from the Onion firmware repo Observe the outcome, given my testing I expect this device should boot properly Plug the device back into your custom board and attempt to boot it again Let me know how it goes!

@IBH I think this is the key firewall rule: config zone option name 'wan' list network 'wan' list network 'wwan' option output 'ACCEPT' option masq '1' option mtu_fix '1' option input 'ACCEPT' option forward 'ACCEPT' It causes masquerading of the sta through the ap.

If I change /etc/config/network like this: ... config interface 'ext_chan1' option type 'bridge' option proto 'dhcp' option ifname 'apcli0' then all works as expected.