IMPORTANT UPDATE 5/13/2022
Our good friends at GitHub have implemented a temporary change to how redirects are handled for the Infineon account. This addresses an error in how ModusToolbox™ was handling access to manifest files. The tools will now operate correctly without the CyRemoteManifestOverride workaround.
Future releases of ModusToolbox™ shall, of course, handle the redirects correctly. We shall also be releasing updated versions of the currently shipping tools (e.g ModusToolbox 2.4.1), so you will not be forced to update to a new tools package when the temporary fix expires (in November).
A change in the way GitHub handles URL redirects, deployed on May 2nd, has resulted in ModusToolbox being unable to access manifest files for BSPs, middleware or applications. The problem presents itself in Project Creator and Library Manager, which fail to display any content and report the following error message:
No internet connection found or improper proxy settings and offline content is not available. Use "Settings > Proxy Settings..." to specify the proxy server or check the user guide to see how to get offline content.
To work around the problem we request you set the following environment variable and restart your ModusToolbox tools.
CyRemoteManifestOverride = https://github.com/cypresssemiconductorco/mtb-super-manifest/raw/v2.X/mtb-super-manifest-fv2.xml
Note that, on Windows computers, you should set the variable in the System Properties, not the Eclipse IDE. Select "Edit the system environment variables" from the Windows menu to open this dialog.
Press "Environment Variables..." to open this dialog and either "New..." or "Edit..." to set up the variable.
This workaround will ensure you seamlessly access the same content as before and the tools will continue to present any new content we post.
We are working on a solution in the tools but, since that may require a software release, we strongly recommend using the workaround in order to continue working. We shall keep this message up to date with new information as learn more.
Once the envirnmental variable is changed new apps can be created.
After adding the environment variable, I had to restart my Windows 10 PC before the workaround kicked in.
Simply restarting the ModusToolbox tools did not work for me.
@markgsaunders this workaround does not work for Linux and MacOS. I am using MacOS BigSur with ModusToolbox.
For MacOS add to ~/.zprofile
Then, source the new profile and launch manually
Dimis-MacBook-Pro ~ % /Applications/ModusToolbox/tools_2.4/project-creator/project-creator
This works for MacOS. For Linux, edit ~/.bash_profile and launch in terminal.
Thanks for the extra info. I think the gotcha is that the tools must be able to pick up the env var from the context that they are launched in. There are probably more ways than I can think of to accidentally start them without the variable set. Your suggestions set the variable in the shell initialization, which does the trick nicely.
This does not solve the issue for Library Manager.
I now have a ModusToolbox project where I need to add the I2C Master / DPS3xx library and the Modus Library Manager is failing to get the manifest. I am using the ModusToolbox Eclipse IDE.
My current workaround is a painful one and not stable:
Dimis-MacBook-Pro firmware-cypress-psoc6-internal % cd PSoC6_App
dimitomov@Dimis-MacBook-Pro PSoC6_App % /Applications/ModusToolbox/tools_2.4/library-manager/library-manager
After adding the DPS3xx library, pressing "update" and then closing the library manager, the library does not actually exist in the project.
Please provide a working solution for Eclipse IDE