Will there be an example of the Nordic UART Service in the central role for the PCA10059 (nRF52840-dongle)? If so is there any timeline on release?
Will there be an example of the Nordic UART Service in the central role for the PCA10059 (nRF52840-dongle)? If so is there any timeline on release?
You can use the one for the PCA10056. Just remap the UART pins.
You can use the one for the PCA10056. Just remap the UART pins.
Except the idea is to use the BLE radio and the USB CDC interface, not the UART. On the PCA10059 the UART does not connect to the USB bus.
Ah, that's a different story. You can combine the CDC example with the uart example for that.
Which I am trying to do and have created an ugly mess. To make this all that much more fun the debugger seems to be refusing to stop at main.
My compiler is IAR EWARM. My hardware is (now changed to be) the PCA10056 board so I'm using the built-in Jlink.
When I start debugging the code immediately runs and creates the CDC device (as shown in the Win7 Device Manager window) but I can't open the device.
It is this weeks long effort of getting a BLE NUS Central with USB working that I was hoping Nordic would create as an example.
It seems like that you have not flashed the softdevice. Try flashing softedevice first then debug your app. Also check the linker mapping. Firmware using softdevice starts at a different location where non SD firmware starts at zero.
Flashing S140 soft device from IAR succeeded but verifying soft device from nRFgo Studio failed so I re-flashed from nRFgo Studio. Now the code doesn't run at all. Gets stuck in app_usbd.c in APP_ERROR_HANDLER()
#if APP_USBD_CONFIG_POWER_EVENTS_PROCESS
ret = nrf_drv_power_init(NULL);
if ((ret != NRF_SUCCESS) && (ret != NRF_ERROR_MODULE_ALREADY_INITIALIZED))
{
/* This should never happen */
APP_ERROR_HANDLER(ret);
}
#endif
Thanks for the hint. Now I'll track down this problem.