Why isn't the app location blank?

RE: Why isn't the app location blank?

jstoezel — Thu, 16 Mar 2017 21:20:48 GMT

Ok I got this sorted out. Once compiled the hex in the example folder can actually run on top of the s132 softdevice. It requires a reset of the board once it is programmed. I had provided a link to the tutorial I was following in the documentation, though it doesn't look like it actually points to the example I was referring to. Somehow the tutorial is not directly linkable.

Regardless, I got it to work, thanks for your help.

RE: Why isn't the app location blank?

Hung Bui — Thu, 16 Mar 2017 14:38:04 GMT

It could be a bug with our documentation. Could you point to the exact place in infocenter.nordicsemi.com/index.jsp that telling you to flash the pre-compiled hex ?

Which board are you testing with ? I just tested here with the ble_app_hids_mouse_pca10040_s132.hex on PCA10040 board, the LED1 was blinking and the board advertise in BLE as a "Nordic_Mouse"

RE: Why isn't the app location blank?

jstoezel — Wed, 15 Mar 2017 13:36:47 GMT

Thanks for the reply. I feel confused by your reply as this page: infocenter.nordicsemi.com/index.jsp seems to imply I first needed to flash a softdevice before tryinig to run the precompiled example

I used the command line to fully erase then program the ble_app_hids_mouse_pca10040_s132.hex example. How can I insure this works properly? By this I mean there is no LED blinking, the board doesn't seem to respond to button click and most of all I cannot seem to detect any sort Bluetooth device when the board is running.

Regards, JS

RE: Why isn't the app location blank?

Hung Bui — Wed, 15 Mar 2017 12:11:49 GMT

Hi,

If you are testing with the pre-compiled hex, you shouldn't flash the softdevice prior to that. The reason is the pre-compiled hex (in the "hex" folder) already include a softdevice.

You can try to compile the application code your self and you can find the hex file generated in _build folder, it usually named "nrf52832_xxaa.hex"