That LED sequence is what you should get if OpenWrt is running as expected. That means the device should be accessible via SSH (root@192.168.1.1).
The "medium blinks" should last 2 seconds, and is the window where you can enter failsafe mode. The device is configured (through its devicetree) to blink the amber LED when running in failsafe mode.
Sorry, I overread the solid green, you are of course right! Fast blinking only is failsafe.
Thanks for your reply, EAP Whisperer... You too andy, I aint mad.
So, I can get it into failsafe(eternal rapid yellow blinking) with the button push. Or allow it to settle on green. But thats as far as I can get. Reading the failsafe section hasnt helped me to further this point.
-I dont recall if I actually enabled SSH in luci, still accessable?
grep squash /proc/mounts to check if SquashFS is my root partition, as I read was suggested, only moves my prompt down a line.Progresso!
SSH'd into device-normal mode not failsafe. But I'm still, or back on after resetting the unit many times, snapshot r19043-c2d7896a65. I changed my key and PW and now at sitting at root prompt...
I'm currently searching for the way forward, but if I could get propper direction, I'd make an imaginary round of espresso for everyone in class..
edit- Upgrade by way of SSH, SCP?
I've grabbed latest eap225-v1-squashfs-sysupgrade.bin for my v.1/2 unit from firmware finder as well as generated a custom packages .bin without changing any packages from the default ones assuming they were curated for my device.
Not sure if the CLI instructions apply to upgrading from my Snapshot so waiting to hear back as I continue to read. Thought there was a specific page about how to go from a snap to a release and it didnt go as planned last time, so patience I'll have umm hmm...
-Would also like to have wifi up at first boot.