Missing files when installing nRF Connect SDK and "west init" can't connect to server

[adb82]

Hi,

I have been trying to install nRF Connect SDK.

I initially tried installing via the Toolchain Manager as recommended. I have previously used Power Profiler and LTE Link Monitor so I believe Connect for Desktop is fine. 
Once installed in Quick Setup the SDK path comes up as "undefined (c:\ncs\v2.2.0). A lot of files seem to be missing, I can't find any samples, and when I tried creating my own application there were "no boards found" in the build configuration.

Having uninstalled and reinstalled everything a couple of times, I decided to try manual installation following Installing manually — nRF Connect SDK 2.2.99 documentation (nordicsemi.com)
At "west init" stage the following is output:

C:\ncs>west -v init -m github.com/.../sdk-nrf --mr v2.2.0
=== Initializing in C:\ncs
--- Cloning manifest repository from github.com/.../sdk-nrf, rev. v2.2.0
Cloning into 'C:\ncs\.west\manifest-tmp'...
fatal: unable to access 'github.com/.../': Failed to connect to github.com port 443 after 21068 ms: Couldn't connect to server
FATAL ERROR: command exited with status 128: git clone --branch v2.2.0 github.com/.../sdk-nrf 'C:\ncs\.west\manifest-tmp'

We believe it is due to the company proxy but can't find any information on how to get around this. 
Is there a way either via Toolchain Manager or manually to install with a proxy?
Or is there another issue?

Thank you for any help!

[Hung Bui]

Hi Alice, 

Coud you please check if you can access "https://github.com/nrfconnect/sdk-nrf/" from the browser ? 

If it's blocked by your company's firewall I'm not so sure what we can do here except turning off the firewall. We currently don't provide the SDK as a .zip package that you can download yet.

You may think of download and install on your home computer and copy it to your work computer ? 

[adb82]

Hi Hung Bui,

I can access sdk-nrf from the browser. 
I tried downloading it and extracting it into ncs/v2.2.0 after the automatic installation, but I wasn't really sure where to go from there. 

Thank you,
Alice

EDIT:

We downloaded the release from the github and added it to the automatic install in C:\ncs, so that "downloads" and "toolchain" are from Toolchain Manager and "v2.2.0" was from Github. It is now working correctly.

Thank you for your help!