Hello everyone,
The more I learn, the more I learn how much more I have to learn.
I am pretty new to embedded systems development. I am tasked with developing an nRF52-based Bluetooth device. I have successfully compiled and run many non-Bluetooth programs which send data over the UART. So far, I have had no luck getting my PCA10036 nRF52 development kit seen by other Bluetooth devices (an Apple laptop, an Android phone). My boss says that communicating between devices made by different manufacturers is sometimes challenging.
However, I just acquired a second PCA10036. If I understand the SDK 0.9.1 documentation, I have what I need to try the ble_app_heart_c example. I don't care about the heart rate service specifically, but at least I should be able to verify that Bluetooth is functioning, in a Nordic-to-Nordic connection. I am still not getting it to work.
My problems may be no different than the ones I described in an earlier question, but then again, they might be. I use JLink, on a Linux box. Here is what I have done:
- I flash the S132 SoftDevice .hex file to both boards at memory address 0.
- At memory address 0x1f000, I flash ble_app_hrs_c to one board; then I connect a UART to it.
- At 0x1f000, I flash ble_app_hrs to the other board.
Nothing ever happens. My UART remains silent. The SDK asks you to observe on the "central" device "that the BSP_INDICATE_ADVERTISING state is indicated." On some older boards, there's apparently a blinking LED state associated with advertising? On the PCA10036, I'm seeing no Blinkenlights when I run the heart rate apps.
In the discussion I mentioned above, I was beginning to believe that the S132 driver was not handing off control to my application at 0x1f000 as it should. I don't know why that might happen, or how to determine whether it is happening. But my new result is consistent with the earlier result.
Any suggestions? Thanks.