As the toolbelt does not have any access to USB, you would still need to do make cload or use cfloader to flash the bin file:
Code: Select all
cfloader flash cf2.bin stm32-fw -w radio://0/40/2M/E7E7E7E703
Code: Select all
cfloader flash cf2.bin stm32-fw -w radio://0/40/2M/E7E7E7E703
That is a reasonable assumption and it is sort of correct Decks that have some sort of firmware running in the deck it self are updated during this phase, but the Flow and Multi ranger do not (currently only the Lighthouse deck and soon the AI-deck).Oh I see. I thought there might be a difference, since at the end of the flash it showed detecting deck to update firmware. I thought having the deck detached, the firmware is not updating the corresponding deck driver.
The multi ranger is not used for state estimation, so that should not change the behavior. The distance sensors on the multi ranger and flow deck are running on the same same bus though, and the boot sequence is a bit special, there might be something here if the firmware is not OK possibly?More specifically, I believe the issue is state estimation instability caused by all range measurements not able to update (static measurement value during bootup).