.emproject

[wischmi2]

I am trying to do the segger development for the 9160 lte ble gateway.  When I do the setup info for segger I keep getting a popup saying it can't find the .emproject file.  I don't see an emproject file in any of the samples?

[AndreasF]

Hi.

Which version of Segger are you using? Have you done the nRF Connect Getting Started Assistant?

Best regards,

Andreas

[wischmi2]

Hi Andreas,

Yes, I completed the getting started assistant.  I was able to connect to my board and get the "gps" signal and I can flip the switch and see it change status in the RFcloud.  I am using 64-bin Segger v4.14.

[wesaymorning]

Am seeing the same issue as wischmi2. My setup is MAC OSX 10.14.2, Segger 4.14.

[wischmi2]

Yes, I’m still getting the pop up similar to what wesaymorning posted.

[wesaymorning]

Found my issue. The following commands had failed during the setup. Once this was resolved I was able to load the project file.

pip3 install --user -r zephyr/scripts/requirements.txt
pip3 install --user -r nrf/scripts/requirements.txt

[hmolesworth]

Nice .. what's the Windows magic? :-)

[AndreasF]

Hi.

Did you try the same as wesaymorning did?

pip3 install -r zephyr/scripts/requirements.txt
pip3 install -r nrf/scripts/requirements.txt

Best regards,

Andreas

[wischmi2]

Hi Andreas,

Yes, I attempted this but it didn't make a difference.

wesaymorning - what happens now that you got it fixed, does it create a build directory when you click ok?

Brian

[wesaymorning]

Brian,

Also check that the commands listed in Tools -> Options -> nRF Connect are valid. I also found that the path I had listed for cmake on my setup was invalid. Once this was fixed, the application was able to create a valid project file. 

[AndreasF]

Hi again.

wischmi2 I've replied in the other ticket you are active in, can you please check that. Also I think you only should have to check the options in Tools -> Options -> nRF Connect if you are running MAC.

Best regards,

Andreas

[hmolesworth]

Yes, it fixed the project issue but I didn't yet get past the build issues:

C:\Projects\ncs>\Python37\Scripts\pip3 install --user -r Zephyr\scripts\requirements.txt
C:\Projects\ncs>\Python37\Scripts\pip3 install --user -r nrf\scripts\requirements.txt

This is the build issue, which I haven't checked yet. I installed the licence and pulled in the CMSIS packages.

1> Combining ‘zephyr/include/generated/offsets.h’
1> Traceback (most recent call last):
1>   File "C:/Projects/ncs/Zephyr/scripts/gen_offset_header.py", line 72, in <module>
1>     input_file = open(args.input, 'rb')
1> FileNotFoundError: [Errno 2] No such file or directory: 'C:/Projects/ncs/nrf/samples/nrf9160/at_client/build/zephyr/CMakeFiles/offsets.dir/arch/arm/core/offsets/offsets.c.obj'
Build failed

The directory is present but currently empty. Not sure whether it is a build sequence issue but disabling parallel builds does not correct this issue.

There were lots of path warnings when running pip3 assuming user "MoiIci":

 Running setup.py install for whelk ... done
 Running setup.py install for docopt ... done
 Running setup.py install for git-spindle ... done
 Running setup.py install for hub ... done
 Running setup.py install for arrow ... done
 The script gitlint.exe is installed in 'C:\Users\MoiIci\AppData\Roaming\Python\Python37\Scripts' which is not on PATH.
 Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location.
 Running setup.py install for pyelftools ... done
 Running setup.py install for future ... done

Adding to the path didn't seem to help:

C:\Users\MoiIci\AppData\Roaming\Python\Python37\Scripts

[wischmi2]

Hi wesaymorning,

Wow, I went and looked in the Tools->Options directory that you mentioned and all of those "Executables" are just blank.  There is nothing setup for any of them.  I don't understand how that could be?  Which part of the Getting Started guide would have done that?