nRF52840 pca10056 compiled ble_app_blinky hex too small and doesn't work

RE: nRF52840 pca10056 compiled ble_app_blinky hex too small and doesn't work

Øyvind — Thu, 06 Jun 2019 12:26:35 GMT

Glad to hear!

Yes, you can mark it as Answered, however, to ask questions (and get an answer) you must reopen the case. Once marked as Verified Answer, we do not get any notifications on new comments (which is a known bug we are working on) 🙂

RE: nRF52840 pca10056 compiled ble_app_blinky hex too small and doesn't work

gjames — Wed, 05 Jun 2019 17:44:31 GMT

Thanks Øyvind, and no worries, this isn't stalling our development. (Also, the email notifications from this forum are great!). Thanks for the follow up!

Can I mark this as Answered, or is that something you do from your end? Either way, I'm happy and our project is going great so far.

RE: nRF52840 pca10056 compiled ble_app_blinky hex too small and doesn't work

Øyvind — Wed, 05 Jun 2019 07:29:59 GMT

My apologies for the late reply.

The drag-and-drop feature is part of the J-Link OB Debugger. I don't know the details about the drag-and-drop feature, but you can read more here.

Kind regards,
Øyvind

RE: nRF52840 pca10056 compiled ble_app_blinky hex too small and doesn't work

gjames — Wed, 29 May 2019 18:16:32 GMT

Great - programming from Keil works.

For when the pca10056 DK appears as a drive in Windows, is there code and documentation with more detail about how that works? It's not obvious what is getting erased with either the Keil or drag-and-drop interface. Does the 'mount as a drive' feature come from one of the bootloaders in the SDK, probably working with your windows driver for the usb device?

Thanks Øyvind

RE: nRF52840 pca10056 compiled ble_app_blinky hex too small and doesn't work

Øyvind — Tue, 28 May 2019 09:21:59 GMT

Hi Greg,

[quote user=""]I'm copying the 485kb hex from examples\ble_peripheral\ble_app_blinky\hex\ble_app_blinky_pca10056_s140.hex[/quote]

This file includes both SoftDevice and the example itself. When you drag this file over to the JLink folder, the device will do a full erase and program this file.

[quote user=""]When I build the uvprojx from examples\ble_peripheral\ble_app_blinky\pca10056\s140\arm5_no_packs, the build succeeds and produces a 63kb .hex in the _build folder[/quote]

Yes, this is correct, as this only builds the software itself and does not include the SoftDevice.

[quote user=""]When I copy this to the JLINK drive, the device resets, but the example does not work. LED 1 does not illuminate and the stats for "Nordic_Blinky" are grayed out in nRFConnect.[/quote]

See my first answer. The device does a full erase, so you lose the SoftDevice on the device. This means that you do not get any BLE connectivity. Are you able to find anything when you search for devices in nRF Connect?

Is there a reason for why you are not programming the device via Keil? When clicking Download (F8) in Keil, see image below, the SoftDevice is not deleted and the example should work as expected.

[quote user=""]Please help me to link in the softdevice or flash this in some way that works.[/quote]

Please use the Keil programming interface to program the device, as this will not delete the SoftDevice.

Let me know how this works for you.

Kind regards,
Øyvind