I apologize for the new thread but this needs it’s own thread. While other threads mention firmware flashing issues, they have non-related topic names (bluetooth), or they seem specific to RS+. A new topic can put these in one place, so maybe we can experiment with work-arounds until a formal Emlid fix is ready.
Two threads mention reflashing errors…
and…
but would it be possible to have one topic so we can help each other with a similar problem?
I have an additional clue/idea which may help provide a workaround of trying a different computer and/or fully charging a unit may help:
Bryce in the second link above could not get his firmware flashed, with an error that the flasher could not find eMMC module.
I took the same receiver, and after charging it up well, managed to reflash the receiver on a computer of mine, but during the reflashing procedure my computer showed repeated warning messages that the device on the USB port was requiring more power than available (see image) and repeatedly made these error/warning messages.
I kept ignoring these error messages, and my computer managed to flash the RS2, but is it possible that the larger than normal power drain (1000-1500 mA instead of the usual 500 mA limit on some USB ports) is causing firmware programming to fail?
If anyone is having trouble reflashing RS2 (or even RS+) firmware, and getting an error of not being able to find eMMC, try fully charging with a high power charger (5-10 amp) for a while, and try a different, maybe newer, computer, and report back if it’s working. It may have worked for me.
(I think the RS+ limited charging current to 500 mA, which caused some slow charging complaints, but think the RS2 was specifically designed to allow high power charging. The docs suggest 5, 7.5 or up to 10 watt chargers. Could that be causing some USB ports to fail during firmware reflashing?)
- tj.