Figure 20. Disabling image verification in bootloader
After that change, select the Build option from the quickstart panel (as shown in
) to start the compilation and linking of
the bootloader.
Figure 21. Build option in quickstart panel
5.4 Programming the firmware and artifacts
This section shows how to update the firmware. There are multiple ways to update the firmware, which also depends on whether
the default NXP credentials are used. If the default NXP credentials are used, there are limitations on what can be updated without
code changes.
By default, the image verification is on, which means that if the bootloader or local_demo are programmed without a valid signature
in the Flash Image Configuration Area (FICA), the image verification fails and the code execution halts.
If the image verification is not disabled (it is enabled by default), then the only application that can be updated is the local_demo
via the Mass Storage Device (MSD) update. To update the firmware without debugging, follow the steps in
.
There are other ways to program firmware into the device with a section dedicated to the manufacturing package called “Ivaldi”,
which is described in
. These tools are available to manufacturers and developers for automated
programing and taking a product from the assembly to the distribution autonomously.
The following section assumes that the image verification is disabled and all supporting artifacts are available to the developer
and that the J-Link debug probe and MCUXpresso IDE are used.
NXP Semiconductors
Building and programming with MCUXpresso
SLN-LOCAL2-IOT Developer’s Guide, Rev. 0, 19 April 2021
User's Guide
27 / 87
