MSC SM2S-IMX8MINI 60 / 87
User Manual
Make sure to keep the Private Key "id_rsa" well secured. It is generally possible to share one keypair within one and the same project, to allow several
people access to the MSC sources. But then the validated user is responsible to keep track of the Private Key any time, and MUST inform MSC Support
if the key has been compromised and access must be withdrawn.
The SSH key must not have a passphrase. It will be used in background communication and therefore there is no possibility to enter the passphrase.
Trying to fetch repositories from the MSC Public GIT Server would fail with no hint that the passphrase is missing.
7.2.2.4 Configuring HTTP proxy
Some source files will be downloaded from HTTP and FTP servers. If a proxy must be used, these environment variables have to be set:
export http_proxy=http://my-proxy:3128
export https_proxy=http://my-proxy:3128
export ftp_proxy=http://my-proxy:3128
Note: Replace "my-proxy" with the appropriate address of your network's proxy, Port number "3128" may also vary depending on your network. Please
consult your admin for proper settings.
On some networks, tunneling Git SSH access over HTTPS may be additionally necessary. Please contact Avnet Integrated /MSC Technical Support
for a related App Note.
7.2.3 Setup the MSC-LDK build environment
The MSC-LDK must be installed on a partition with at least 128 GB free space. As a lot of source files will be accessed, it is recommended to use an
EXT4 partition with the mount options "noatime,nodiratime".
To Next Page
Loading...
Need help?
General
