Project Creator: “Failed to access remote server”. How to resolve this error?
Issue: Unable to access the site that hosts the manifest files when creating a new application on ModusToolbox™ software. The Project Creator fails with the error “Failed to access remote server”. How to offload the file request to the manifest files to resolve this error?
Figure 1: Failed to access remote server error
How to manifest files in ModusToolbox™ ?
When you create a new application in ModusToolbox™ software, information is fetched from files called “manifests” to display Board Support Packages (BSP) and code example templates. For more details, see the “Manifest files” section in the ModusToolbox™ software user guide.
The manifest files are hosted on the Infineon GitHub repository. GitHub is used to serve files kept in GitHub repositories.
In a few countries or in situations when access to this domain is restricted, there are three options to work around this problem:
- Method 1: Offloading the manifests to a different remote server location
- Method 2: Offloading the manifests to a location on the disk
- Method 3: Using ModusToolbox™ software offline package
Method 1 or 2 is recommended if you have access to the internet but only face problems accessing the GitHub domain through raw http access. It allows you to get the latest libraries, code examples, BSPs, etc., each time you create a new application.
Method 3 involves downloading a static offline package. Note that this package is a few hundred MBs in size and is updated quarterly. To get the new libraries and code examples, you need to download them from time to time. It is only recommended when working offline.
Use the following methods in priority order.
1. Method 1: Offloading the manifests to a different remote server location
This is a one-time process; all new applications created will use these offloaded manifests.
Do the following to offload manifest files to a different server (in this case from GitHub to itools.infineon.cn):
- Run the in-built bash shell if you are a Linux/macOS user. Windows users can skip to the next step.
- Set the System Variable:
- Windows: Set the system environment variable to override the manifests permanently. Set the variable name to CyRemoteManifestOverride and the value to the corresponding manifest file location. Use the forward slashes as path separators.
Figure 2: System Variable
- Linux/macOS: Execute the following command in the bash shell:
- For ModusToolbox™ software 2.1:
>> export CyRemoteManifestOverride = ITools - Manifests: MTB super manifest.xml
- For ModusToolbox™ software 3.x and earlier versions:
>> export CyRemoteManifestOverride = ITools - Manifests: MTB super manifest fv2.xml
- Create a new application:
- Windows: Launch Eclipse IDE for ModusToolbox™ software or Project Creator standalone tool to create a new application. Both methods invoke the Project Creator window.
- Linux/macOS: Invoke Eclipse IDE for ModusToolbox™ software or Project Creator standalone tool from the bash shell in the same bash session. The variable set in the previous step will only have an effect in the same bash session.
To invoke Eclipse IDE for ModusToolbox™ software run the command:
- For ModusToolbox™ software 2.x:
>> ~/ModusToolbox/ide_2.4/eclipse/ModusToolbox.exe
- For ModusToolbox™ software 3.x:
>> ~/ModusToolbox/ide_3.0/eclipse/modustoolbox-eclipse.exe
To invoke the Project Creator tool run the command with the appropriate tools version:
>> ~/ModusToolbox/tools_2.4/project-creator/project-creator.exe
Note: Change the path accordingly if you have installed ModusToolbox™ software in a custom location.
You will notice that the manifest files are now being fetched from a different server location.
Figure 3: Manifest data from the server location
2. Method 2: Offloading the manifests to a location on the disk
This is a one-time process; all new applications created will use these offloaded manifests.
Do the following to offload manifest files:
- Download the zip archive of the manifest files from here.
- Extract the files to the ~/.modustoolbox directory. In case you do not see this directory, create a directory named “.modustoolbox” and extract inside it.
Figure 4 ModusToolbox™ software directory
- Run the in-built bash shell if you are a Linux/macOS user. Windows users can skip to the next step.
- Set the System Variable:
- Windows: Set the system environment variable to override the manifests permanently. Set the variable name to CyRemoteManifestOverride and the value to the corresponding location of the manifest file on the disk. Use the forward slashes as path separators.
- For ModusToolbox™ software 2.1, the variable value is:
<path_to_file>/.modustoolbox/mtb-super-manifest.xml
- For ModusToolbox™ software 3.x and earlier versions, the variable value is:
<path_to_file>/.modustoolbox/mtb-super-manifest-fv2.xml
- Linux/macOS: Execute the following command in the bash shell:
- For ModusToolbox™ software 2.1:
>> export CyRemoteManifestOverride=file:///$HOME/.modustoolbox/mtb-super-manifest.xml
- For ModusToolbox™ software 3.x and earlier versions:
>> export CyRemoteManifestOverride=file:///$HOME/.modustoolbox/mtb-super-manifest-fv2.xml
- Create a new application:
- Windows: Launch Eclipse IDE for ModusToolbox™ software or Project Creator standalone tool to create a new application. Both methods invoke the Project Creator window.
- Linux/macOS: Invoke Eclipse IDE for ModusToolbox™ software or Project Creator standalone tool from the bash shell in the same session. The variable set in the previous step will only have an effect in the same bash session.
To invoke Eclipse IDE for ModusToolbox™ software run the command:
- For ModusToolbox™ software 2.x:
>> ~/ModusToolbox/ide_2.4/eclipse/ModusToolbox.exe
- For ModusToolbox™ software 3.x:
>> ~/ModusToolbox/ide_3.0/eclipse/modustoolbox-eclipse.exe
To invoke the Project Creator tool run the command with the appropriate tools version:
>> ~/ModusToolbox/tools_2.4/project-creator/project-creator.exe
Note: Change the path accordingly if you have installed ModusToolbox™ software in a custom location.
You will notice that the manifest files are now being fetched from the location on the disk.
Figure 5: Manifest files to the local disk
3. Method 3: Using ModusToolbox Offline Package
ModusToolbox™ software 2.x and 3.0 provide an offline content package that you can download and use to create new applications. Use this method as a last-resort option. Asset releases occur frequently while offline content releases are not. So, the offline content may not always reflect the latest updates.
On ModusToolbox™ software 3.1 and newer, this package is deprecated in favor of the new local content storage feature.
For more information, see the ModusToolbox™ software offline libraries.
Author: DheerajK_81 Version: *C
Translation - Japanese: ModusToolboxのマニフェストファイルのオフロード - KBA230953 - Community Translated (JA)