Hotfixes And Updating Msc-Ldk - Avnet SMARC MSC SM2S-IMX8MINI User Manual

Figure 7-29. Bug report. Target partition selector.

7.4 Hotfixes and updating MSC-LDK

Typically twice a year a full MSC-LDK release is issued. A release may contain an updated Yocto or other updated layers as well as new supported
boards. For each release an own branch is used (e.g. v1.0.0) which is tagged with the date encoded (e.g. LC984_20150421_V0_4_0, 21st April 2015),
too. The release is checked out using the version syntax (e.g.: git checkout v1.3.0) as described above. Sometimes an intermediate hot-fix is necessary
which doesn't modify the resulting image but fixes changed repository locations of third party software or similar minor changes. Hot-fixes are tagged
with a newer date stamp (e.g. LC984_20160113_V0_4_0). A hot-fix can be checked out explicitly using these tags. When MSC-LDK is checked out the
first time all hot-fixes are applied automatically.
To update an older checkout and to pull all the newer hot-fixes, run "scripts/update.py" from the MSC-LDK root directory. This will update MSC-LDK and
all layers. Depending on the kind of hot-fixes applied in the meantime, running setup.py again might be necessary. When a hot-fix has been checked
out explicitly, running update will not make sense and it will fail with an error.
After the first call of setup.py, no manual "git checkout" is required, as its layers will already be in synchronization with MSC-LDK. Either use update.py
or clone MSC-LDK again. The subdirectories "download" and "sstate-cached" can be moved to other MSC-LDK installations or shared by symbolic links.
MSC SM2S-IMX8MINI 85 / 87
User Manual