No errors from the scope like a flashing red light on the switch. Scope bootup is delayed with the card in so the device definitely knows there's a card in the slot. However, after a few minutes the scope reverts to it's regular bootup routine and never initiates the firmware update.
That sounds like you have the wrong file loaded first on the card.
The LS firmware normally operates like a PC with a BIOS and C: drive.
There is a master file called C:\Firmware.bin that is the boot file that normally starts it up.
If there is a card in the SD slot when booting, the BIOS treats it like an old style bootable floppy and will try to boot from it first. If it cant start from the card, the switch LED blinks, but otherwise it just starts and runs the bootstrap firmware
on the card.
The fact yours starts properly ( after a while ), would indicate you have got the file names mixed up somewhere
when creating the SD card.
Not sure for the latest firmwares, but early on,
there was a "Firmware.bin" file in the "Program Files\Meade\AutostarSuite\Updater\" directory
This is the special Bootfile that starts and then loads firmware to the mount.
Then you have the individual file directories for each of the LX firmware versions
I have one called "Program Files\Meade\AutostarSuite\Updater\ETX_LS16A\"
In this directory there is also a Firmware.bin file and a series of subdirectories for the data
This Firmware.bin file is the true one that starts the scope ( and gets copied onto the LS C: drive during the load )
To get around having 2 Firmware.bin files, what Meade did was copy the master Firmware.bin onto the SD card
as FIRMWARE.bin ( and it had to be the first file copied on after the format )
The SD cards drive was named as "EFINDERETX"
They then renamed the version specific Firmware.bin to FlashFirmware.bin and copied it to the card second.
On booting, the Firmware.bin on the card simply copies and renames the FlashFirmware.bin file
to the mounts C: drive as Firmware.bin.
As a simple check, if you have a hex editor, just open each of the firmware.bin/flashFirmware.bin files
and search for NAND.
It should only be in the master file.
Andrew Johansen Melbourne Australia