'make' is not recognized as an internal or external command

[Marius]

I'm following this guide from Nordic to set up GCC and Eclipse to develop with Nordic SDK for the nRF52840. I'm going to develop for the SparkFun Pro nRF52840 mini development board, though that's not yet an issue. Having set up GNU toolchain (it seems to work) and GNU make (it seems to work) I'm editing the Makefile.windows so that it points to the \GNU Tools folder but when I run "make" in the "examples\....blank\armgcc" folder I get the error:

'make' is not recognized as an internal or external command.

This seems to obviously be that it cannot find the install root for the GNU Tools but I have changed the path to the correct one and it will still not work. Here is the makefile.windows:

Here is the make command and the error when ran from this directory:

I'm not sure where to go from here. I'm developing on Windows 10 and because I'm developing on the SparkFun development board I need to do some extra modifications later on so I'm not sure if this method is even the best one for developing for this board? Any help would be appreciated.

[awneil]

Why not just use an IDE?

Segger Embedded Studio is free, all the Nordic SDK examples have an SES Project, and many of the Nordic blogs & tutorials, etc, use SES.

Marius said:

'make' is not recognized as an internal or external command.

That's a standard Windows (and MS-DOS before it) error message.

You either have to give the full path to make.exe, or add it to the System PATH.

[Marius]

Thank you for your answer! I can use the Segger Embedded Studio I guess, but I'm not sure how to make that one work with the SparkFun nRF52840 (or if it even will?). The System PATH has been set already!

[awneil]

Yes, of course it will work.

The board the device is mounted on does not affect the IDE!

I would strongly recommend that you start with an nRF52840-DK - as you will have ready-made projects for all the SDK examples, and a Segger J-Link for programming & debugging.

Once you have gained familiarity with the chip & the tools, you can move on to the Sparkfun board - and still be able to use the J-Link for programming & debugging.

[Marius]

I agree to this, I just thought it was unnecessary to get another development board when I already had one. I was developing with Arduino already for the SparkFun board but needed more functionality, so this is why I'm now switching to Nordic SDK. I guess you are right that it is better to start with something that works "out of the box" and go from there. I will look into that.

[awneil]

Marius said:

it is better to start with something that works "out of the box"

I think so.

Even with >30 years experience, I would always start on the manufacturer's dev kit to gain familiarity with a new product & its tools.

Of course, you can do it all from scratch - but why bother? It doesn't add (much? any?) value.

[Marius]

I agree, I will definitely try and order an official Nordic development board. Thanks