Factory Functions
Danger
This is historical documentation, and tooling and console operations are no longer available.
Microvisor system calls include the following functions for managing operations on the assembly line:
Return Values and Errors
All of the functions described below return a 32-bit integer that is one of the values from the standard Microvisor enumeration MvStatus. All possible error values for a given system call are provided with each function’s description.
Success is always signaled by a return value of zero (MV_STATUS_OKAY).
mvTestingComplete()
Informs Microvisor that the testing of product hardware has completed
Declaration
extern enum MvStatus mvTestingComplete(uint32_t status);
Parameters
Parameter |
Description |
|---|---|
|
A value indicating the outcome of applied tests |
Possible Errors
Error Value |
Description |
|---|---|
|
This call has been made outside of application test mode |
Description
Include this call in your factory-oriented application test code after all your tests have completed, whether successfully or not. If the tests were successful, pass in the value 0. All other values indicate test failure.
Calling this function will stop the test code immediately. Specifically passing 0 will cause Microvisor to install your application firmware from the device under test’s (DUT) external SPI Flash into the MCU, overwriting the hardware test code. The DUT may now be passed to the next assembly line station.
Passing any other value than 0 causes Microvisor to display Programming Failed in the provision console. The assembly line operator may now remove the device for analysis and repair, or disposal. If the DUT is reset, the hardware test code will be run again.