AP went down, netinstall?

I have a 433 that locked up after an update to 5.11.

I power cycled it, can’t get it to come up.

Is there any way to trigger it to boot from netinstall aside from a serial cable?

new devices can trigger netinstall with the reset button, but I think it depends on your RouterBOOT version.

try to hold the button when powering up, release when the user LED shuts off.

I think the RouterBoot may be the problem. It was an old 433 running 4.17 with whatever version came with 4.17. I had copied 5.12 on there earlier so I could upgrade it later on. It started 5.12 after a power cycle, didn’t work very well, 5GHz link had horrible ccq where it was near 100% on 4.17, and in poor judgement I put 5.11 on there as I’ve had good luck with it. Never boot up again.

If the weather permits we’ll change it out this morning and I’ll sort out the problem back at the office.

I think the problem may be caused by older firmware. I should have thought of that before rebooting again. What firmware is required on an old 433 to boot 5.11? Will a netinstall update the Routerboard firmware as well?

I got it swapped out yesterday, reinstalling ROS on the board this morning. It has firmware 2.20. v5.12 boot just fine, v5.11 boots then says “System halted”.

Could this be because I didn’t upgrade the firmware before the install?

Netinstall 4.17 and it is up and going. I’m going to upgrade and try 5.11 again.

Got it running 4.17, updated the firmware, upgraded to 5.11 without a problem this time.

Was the firmware the problem?

Very interesting comment, should we check before updating that firmware is upto date on the current version (say 4.17) and then update?

Perhaps a popup prompt when packages are transferred to “files”