Can't see Nordic_Prox in Devices

[cycledude]

I have just purchased a nRF52840-DK

I am following the getting started tutorial and when I scan for devices the Nordic_prox device is not appearing in the device list but other devices are.

I loaded the proximity demo .bin file in the JLINK folder on my PC.The proximity demo does not work as it does not see the Nordic_prox device.

I am using a windows 10 pc,and  a samsung s9 phone,with nRF Connect and nRF toolbox installed.

Can you please assist?

Regards

Rick

[Edvin]

Hello Rick,

Where exactly did you find that .bin file? I suggest that you try to upload the .hex file that is located in the folder:

SDK\examples\ble_peripheral\ble_app_proximity\hex\ble_app_proximity_pca10056_s140.hex.

Note that this file is precompiled. If you change anything in this project, it will not affect this .hex file. 

If you change anything in the project, you need to build it, using e.g. Segger Embedded Studio. You can also flash your project using Segger Embedded Studio, and it will also upload the SoftDevice (Bluetooth Low Energy Stack) automatically. If you use another IDE, you must upload the softdevice manually from SDK\components\softdevice\s140\hex\*.hex

The precompiled hex files already has the softdevice merged into it. 

If you flash the correct files, you should see LED1 blink when it starts to advertise. If you can't see it from your phone, does the LED blink?

[cycledude]

I got the file from here https://www.nordicsemi.com/Software-and-tools/Development-Kits/nRF52-DK/Download#infotabs

Unfortunately I am not able to connect to(404 error) https://www.nordicsemi.com/SDK\examples\ble_peripheral\ble_app_proximity\hex\ble_app_proximity_pca10056_s140.hex.

Led 1 is not blinking. Is deleting the existing bin file performed by loading the correct hex file. If not how do I clear it?
I loaded the bin file by placing it in the JLINK folder, is this correct?
Sorry for my lack of knowledge.

Thanks for your assistance.

[Edvin]

Oh. I see. Your first link is not firmware for the nRF mounted on the DK, it is firmware for the Segger chip (the programming chip, which is the large one with the sticker on it). 

Usually, although it is possible, we don't program the DK with drag'n'drop. I suggest that you download nRF Connect for Desktop, and install the "programmer" app. When you open this app, does the DK appear from the drop down menu? It should look like this:

Do you see your DK from the drop down menu? The first number and the COM port will be different from my screenshot, but it should say pca10056 if you are using the nRF5240 DK. 

If you can see it, try to drag'n'drop the hex file from 

SDK\examples\ble_peripheral\ble_app_proximity\hex\ble_app_proximity_pca10056_s140.hex

to the "file memory layout" box, and click write from the menu to the right. After this, does LED1 start blinking?

If the device doesn't appear on the list in the programmer app, let me know.

Best regards,

Edvin

[Edvin]

Oh, I forgot:

 

cycledude said:

Also could you please suggest some resources on you site for beginners?

 If you are new to BLE, I would suggest that you take a look at the following 3 tutorials:

Advertising introduction

Services introduction

Characteristics introduction

BR,

Edvin

[cycledude]

Thanks Edvin!

Could you please send me the link to the zip file with the SDK software for the nRF52840. there are several on your site and I am not sure which one I need.

Thanks

Rick

[Edvin]

I would use the SDK16.0.0, which you can find here. There is a link to the top right saying "Download latest version, nRF5 SDK. This will give you the SDK16.0.0.