The documentation here:
https://developer.motorola.com/build/tools/flashing-firmware
The documentation here:
https://developer.motorola.com/build/tools/flashing-firmware
This tool is a little less sophisticated than Nuttx. If you want to change any configurations you just edit the .config file by hand. As before, copy the .config back over your defconfig to preserve the changes for future builds.
Is that the answer to my own question?
The Reference Moto Mod Bootloader uses the Vendor ID (VID) and Product ID (PID) to ensure the correct NuttX firmware is running on the device and to provide over-the-air firmware updates. When you receive the Reference Moto Mod it will be in Example mode with a MDK VID and a PID derived from the Personality Card which is installed. When developing your custom firmware for prototyping, you should switch to the Developer VID of 0x42 to ensure no firmware over-the-air update attempts to reflash you Reference Moto Mod. To easily update the bootloader with Developer VID 0x42, use the Set Mode function in the MDK Utility.
The MDK Utility intentionally restricts firmware flashing to Developer VID 0x42. As a result, your prototype projects should use 0x42 for easy flashing.
The switch allows you to be able to update whatever firmware you developed. This is not only a good idea but necessary.
Clem
Well, you could always flash the bootloader with the openocd tools. But then you'd have to compile the developer bootloader and flash it yourself...hopefully this is a little easier.