• State Verified Answer
  • Replies 6 replies
  • Subscribers 87 subscribers
  • Views 2097 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 337779
Options

Toolchain manager cannot download nRF Connect SDK v2.8.0

puz_md

Hi,

I am currently using nRF Connect SDK v2.5.3 and want to update to a newer version, because I want to create a board definition and I want to do it in HWMv2.

Even though the toolchain manager worked flawlessly before (I have older SDK's on my PC), when downloading the SDK v2.8.0, I get the following error:

Seems like the certificates for the servers are invalid? Can you fix it?

I'm working within my company's network which probably uses some protection framework, if this might be related to the problem.
I could bring my notebook home and try from my private internet connection if you think this helps. Although I think downloading a SDK from within a company network should be possible...

Update: It seems like the toolchain repository can be downloaded without any problem, but the SDK fails.

Best regards,
Michael

PS: I've noticed that there are some new devzone tickets with developers having trouble creating board definitions on the nRF Connect SDK v2.8.0. Is this release still a bit unstable? Would you suggest using 2.7.0 for migration and HWMv2 board definitions at the moment? Or better switch over to 2.8.0 as planned?

Parents
  • 0

    Hi Michael,

    It seems the issue stems from a conflict between GitHub and your company's proxy at a lower network level. Unfortunately, there’s not much improvement that can be made with the Toolchain Manager itself in this scenario.

    For reference, you can check this discussion: Request Error: unable to get local issuer certificate · community · Discussion #36894 · GitHub

    Best regards,
    Charlie

  • +1 in reply to Charlie

    Hi Charlie,

    like I mentioned before, there seems to be some security software running which manipulates Github's SSL certificates, using a root of trust that is my own company. If certificate checks are not implemented within the Toolchain Manager, the invoked command line tools that connect to GIT could be updated to accept local certificates / roots of trust.

    But I can understand if support for "man in the middle" safety solutions is not wanted in the official releases because of risks to security and code authenticity.

    My private PC also installed SDK v2.8.0 without any problems this morning. The error message posted above with failing RPC must have been some random issue or just bad luck that it appeared at the same time.

    Conclusion: In my case, using an internet connection which is not connected to the company's intranet (Guest Wifi, private internet connection at home) solved the problem.

    Thanks for your feedback so far!

    Best regards,
    Michael

    PS: Your link points forwards to a "drivers/clock_control: stm32: Fixes around LSE clock #36894" discussion which does not help... (it is forwarded to https://github.com/zephyrproject-rtos/zephyr/pull/36894).

Reply
  • +1 in reply to Charlie

    Hi Charlie,

    like I mentioned before, there seems to be some security software running which manipulates Github's SSL certificates, using a root of trust that is my own company. If certificate checks are not implemented within the Toolchain Manager, the invoked command line tools that connect to GIT could be updated to accept local certificates / roots of trust.

    But I can understand if support for "man in the middle" safety solutions is not wanted in the official releases because of risks to security and code authenticity.

    My private PC also installed SDK v2.8.0 without any problems this morning. The error message posted above with failing RPC must have been some random issue or just bad luck that it appeared at the same time.

    Conclusion: In my case, using an internet connection which is not connected to the company's intranet (Guest Wifi, private internet connection at home) solved the problem.

    Thanks for your feedback so far!

    Best regards,
    Michael

    PS: Your link points forwards to a "drivers/clock_control: stm32: Fixes around LSE clock #36894" discussion which does not help... (it is forwarded to https://github.com/zephyrproject-rtos/zephyr/pull/36894).

Children
No Data
Related
Terms of service