Hi All
I have recently upgraded MDK from 5.38a to 5.39. Before the upgrade, the pack installer from Project->Manage->Pack Installer is functioning correctly, while after the upgrade of 5.39, it falls to work and the bottom right corner of the screen shows "OFFLINE" while with 5.38a it shows "ONLINE". See the bottom right corner of the image.
Is there anything need to be set up in order to get the status to be online?
Rgds
Calvin
Hi Andreas
I don't think this is the case, as I have tried both custom ticked or unticked, with the correct path of C:\Keil_v5\ARM\cmsis-toolbox\bin
or correct file of C:\Keil_v5\ARM\cmsis-toolbox\bin\cpackget.exe
I suspected that it may be due to our company internet settings that prevent to outgoing of the corresponding sites.
Ok, when the cpackget.exe is there, it can of course also be a network issue. Does the Pack Installer from 5.38a still work? Are you aware of changes that have been applied to your network config recently?
As said, 5.38a is working. In fact, I have 5.38a & 5.39 both installed in my machine.. Using 5.38 pack installer is functioning correctly online. Using 5.39 gets the offline status.
Sorry, then I don't know what could cause this. Can you try MDK 5.39 Pack Installer outside of your company network, maybe on a private PC? If it works there, it is something specific to your company setup.
For a test, you could also try the CMSIS Toolbox command directly on the command line to see what they report.
A private PC with non office network does show online status. So it is highly likely that it relates to company network setup.
I am not familiar with the toolbox command line on how to check this. May be you can hint me on that.
Do you have any idea what url line or the server that cpackget.exe is trying to access to. With a known address, I may be able to just ping it and test the accessibility of the site.
Here in the cpackget page, there is also an example how to initialize a new local pack root folder:
cpackget init --pack-root path/to/new/pack-root https://www.keil.com/pack/index.pidx
The pidx file is also what the Pack Installer tries to access. So you can try this.