This repository has been archived by the owner on Jul 9, 2024. It is now read-only.
Flash Thingy:91 firmware and cloud credentials via MCUBoot #484
coderbyheart
started this conversation in
Ideas
Replies: 1 comment
-
I've just realized that right new we need the AT host running on the device, because the flashing depends on a set of AT commands (and responses) which are transferred via UART. When the asset_tracker_v2 is running however, it prints other messages on UART (debug logs), which can interfer with the certificate flashing and reading of neccessary modem information. Using the AT host ensures that nothing is printed on UART except AT command responses. /cc @simensrostad |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Flashing the Thingy:91 is not as straightforward as the DK because the CLI currently does not support flashing via MCU Boot and it requires a JTAG cable.
We do not specifically mention the process in our docs which in recent walk throughs by new employees lead to confusion. They would plug in the Thingy:91 directly via USB to their computers and expect to be able to program the credentials and flash it. However it is more complicated:
And the above description does not even mention that the Thingy:91 has to be turned on BEFORE the DK.
Proposal
Update the documentation and CLI to allow flashing credentials and firmware onto the Thingy:91 using MCUBoot. The
asset_tracker_v2
has the AT host enabled by default so there is also no need to flash it. In theory the new process could be:Beta Was this translation helpful? Give feedback.
All reactions