How to add uart debug support to BLE DFU

RE: How to add uart debug support to BLE DFU

bjorn-spockeli — Wed, 13 Jan 2016 07:46:07 GMT

No problem :) Could you mark my answer as correct so that other DevZone users can see that problem has been solved.

RE: How to add uart debug support to BLE DFU

Andreas — Wed, 13 Jan 2016 06:42:26 GMT

Thank you Bjørn, now it is much more clear.

RE: How to add uart debug support to BLE DFU

bjorn-spockeli — Tue, 12 Jan 2016 16:39:32 GMT

See answer to the post I linked to in my answer.

RE: How to add uart debug support to BLE DFU

bjorn-spockeli — Tue, 12 Jan 2016 16:10:26 GMT

You have to either change your code to

for (uint8_t i = 0; i < len; i++)
{
    while (app_uart_put(s[i]) != NRF_SUCCESS);
}

or use app_uart_fifo.c instead of app_uart.c. Please see this post

RE: How to add uart debug support to BLE DFU

Andreas — Tue, 12 Jan 2016 16:07:29 GMT

OK, I think I solved the problem. I switched from app_uart.c to app_uart_fifo.c. Can anyone explain me, why app_uart_fifo.c does work and app_uart.c does not? Now the complete string is transmitted.

Regards, BTProgrammer

RE: How to add uart debug support to BLE DFU

Andreas — Tue, 12 Jan 2016 15:21:08 GMT

Ok, I have done a little step forward. If I send only one byte via the interface, it is working. So after uartOpen() I do

c='t';app_uart_put(c);

And I get the "t" on my serial terminal. Why does the

void putstring(char * s){
uint32_t err_code;

uint8_t len = strlen((char *) s);
for (uint8_t i = 0; i < len; i++)
{
    err_code = app_uart_put(s[i]);
    APP_ERROR_CHECK(err_code);
}}

not work? Is there a problem with the scheduler?