MCC deploy error due to firmware mismatch
Moku Cloud Compile (MCC) is a powerful feature of Liquid Instruments Moku products allowing users to run custom logic inside the Moku device and implement personalized functionalities.
Each project created in MCC must target a specific device, which is a combination of both hardware (e.g. Moku:Pro, Moku:Lab, or Moku:Go) and firmware (e.g. version 587). Liquid Instruments regularly releases firmware and software updates. When Moku is updated to a new firmware, a new bitstream should be created that corresponds to the updated firmware version.
The Moku device's firmware version is shown when uploading a custom bitstream using the Moku App, highlighted here in the red dashed box.
MCC error due to firmware mismatch
Uploading a bitstream with mismatched firmware via the web interface or Moku app can lead to error messages of "Device not responding" and "Connection lost," resulting in your Moku device hanging during deployment. In such cases, you will need to power cycle your Moku device.
Solutions
To generate a new bitstream, you will revisit your MCC project and update your device settings by selecting the firmware version that matches your Moku device.
Then re-compile the bitstream with your updated Target Device. The firmware version is automatically included in the bitstream name for reference. For example, in the name “XXXXXX_mokugo_580_9ab5dbb.tar.gz”, “580” indicates the firmware version of the Target Device.
Find detailed instructions and examples of Moku Cloud Compile here.