xTimecomposer will not connect to xmos.com

[ArtemisRodent]

Hi everyone,

First off, I have checked the solutions posted by others regarding this issue. ;-)

I am using xTimecomposer Studio Community 13.2.2 on windows. When trying to refresh the packages in the xSoftIP explorer panel, I get the message: "Connection to https://www.xmos.com failed".

I get the same message for the HowTo and Community panels.

What I have checked:

1. I checked that my OS is not using a proxy
2. I checked that "Enable connection to https://www.xmos.com" is checked in the settings
3. I tried both with certificate checking disabled and enabled, same result
4. I changed the Active Provider in the Network Connections settings panel to Direct from Native, same result
5. I toggled offline/online mode in the xSoftIP panel
6. I launched the web browser from Show View->Other->General and ensured that it could navigate to https://www.xmos.com
7. I removed the cached data in .xmos
8. I verified that my firewall wasn't blocking the connection and even disabled it entirely.
9. Restarted the computer and swore at it for good measure (you never know)

I should add that this worked previously, so I am not sure what happened.

I ran the composer in debug mode, and when I hit refresh in the xSoftIP panel, the debug output shows several Category entries and an error message.

The category entry directly before the error message and the error message are below:

Code: Select all

<category component="app_sdram_mfg_tests" domain="Memory" subdomain="Volatile" />

ERROR: ComponentBrowserView(handleRefreshError): null

There are obviously more category tags before that, but no other error messages.

What can I do? Thanks in advance.

[ArtemisRodent]

I should add that I also uninstalled and reinstalled 13.2.2, and the problem remained. I then installed 13.2.1 again as that was the version it initially worked with, but the problem is present there as well.

In case it was a problem with the files in the workspace folder, I removed them all and tried again, same result.

[ArtemisRodent]

It's working now, I guess it was either a server issue or some rat in the pipes between my computer and xmos.com.

If you guys fixed something, thanks. ;-)