The OS Customizer tool uses an existing build system, either within the OS running on the SoC processor or through an external computer, to generate the OS firmware image. Four generalized build system configurations can be defined that can be used with the Operating System Customization App. The App automatically determines the configuration and selects the appropriate work flow.
The configuration consists of an SoC device, such as Xilinx® Zynq® ZC706 evaluation kit, attached to your development computer through a network connection. The OS on the SoC device contains a Package Manager that modifies the OS by adding, removing, or updating libraries in the device memory. In this case, the OS Customizer tool acts as an interface to the package manager which:
Determines the necessary packages required by MathWorks® products.
Downloads the missing or out-of-date packages from the internet.
Extracts the new packages updating the OS firmware.
By default, a package manager downloads the missing libraries from known and trusted online repositories containing the most up-to-date version of the library for your OS.
The configuration consists of an external hardware board attached to your development computer through a network connection. The OS image on the hardware board gets created by a build system on the development computer. This work flow is typical of embedded Operating Systems on hardware boards that do not have a package management system, requiring the OS firmware image to be regenerated. In this case, the OS Customizer tool performs three tasks:
Determines the necessary packages required by MathWorks products.
Creates a new OS firmware image using the specified Build System.
Flashes the new OS firmware image onto the hardware board.
The configuration consists of your development computer connected to a build system on a remote computer accessible through the network. The work flow follows the same process as a Development Computer with Build System except that OS Customizer tool generates and downloads the new firmware image on a remote computer containing the build system.
This configuration mirrors the Development Computer with Remote Build System, except the hardware board also must be accessed remotely over the network. Again, the OS Customizer tool acts as an interface to the remote build system.