nRF52 ble_app_uart example problems with PCA10059

[catfish]

I modified the ble_app_uart example to run on the PCA10059 by altering the flash_start, size, ram_start and size linker settings. I also selected two GPIO for the uart pins. The problem I am having is that after the code is flashed to the dongle using the nRF connect programmer the dongle begins advertising and can be connected to. If the dongle is power cycled - remove from USB port and then reconnected - the advertising LED doesn't blink and I can't see the device advertising. If I press the reset button the bootloader activates and waits for a DFU. After the initial code writing the code won't function. Are there any other specific changes that need to be made to run this example on the PCA10059 dongle?

Thanks

[catfish]

I think I found the problem, I didn't have anything connected to the uart pins so they were triggering data without the pins idleing at the proper state. I connected a USB/serial converter to the pins I selected for RX and TX and the dongle is working properly.

[tesc]

Hi,

Thank you for the update. This means all issues are solved?

Regards,
Terje

[catfish]

Yes, the only other point I want to add is that the example code also sends a message to the uart printf("\r\nUART started\r\n" and if a receiver isn't connected the code blocks here. I assume this is due to interrupt driven transmission? If so, is there a way to have the HW uart code not block in the event a serial connection is used only for debug and may or may not be connected?

Thanks

[catfish]

actually, I'm having intermittent success with the example code functioning without an external serial interface connected. The code blinks while awaiting a BLE connection but when I power the dongle via USB interface if I don't have my external serial interface connected to the RX/TX pins I selected the example code isn't always advertising. If the external serial interface is connected the example code ALWAYS advertises when powered

[catfish]

definitely fixed, the issue is that either the RX line needs a pullup when a serial interface isn't connected or the uart needs to be re-init'd when a comms error is detected. Both methods work well. Issue resolved

[tesc]

Hi,

Sorry for the delay. Thank you for sharing. I am happy to hear that the issue is resolved.

Regards,
Terje