Debug UART with SDK 7.1

RE: Debug UART with SDK 7.1

Jerod — Fri, 22 May 2015 18:29:48 GMT

Thanks for the tip! I was just running into this when upgrading from SDK 6.

The big question is "why"? What has broken?

Here's the default HRS example's output with device_manager output turned on:

[DM]: >> dm_init. [DM]: Initializing Application Instance 0x00000000. [DM]: Initializing Connection Instance 0x00000000. [DM]: Initializing Peer Instance 0x00000000. [DM]: Initializing Peer Instance 0x00000001. [DM]: Initializing Peer Instance 0x00000002. [DM]: Initializing Peer Insta0[DM]ae[DM]aa[DM]nt[DM]:n[DM]:[e[DM][e[DM]: DevFF[DM]:c4[DM]]F[DM]: Dedx[DM]:[e[DM]:e[DM]: Dev00[DM]: F[DM]x0[DM]: DeeF[DM]:[a[DM]:e[DM]: Dev [DM]:BF[DM]xF[DM]: DeA0[DM]:[l[DM]:c[DM]: Dev0 [:[D_[DMa[D<[ADV]: Starting fast advertisement[DM]: Request to allocation connection instance [DM]:[00]: Connection Instance Allocated. [DM]: Searching for device 0x8F 0xEC 0x53 0x9B 0x38 0x6C. [DM]:[DI 0x00]: Device type 0xFF. [DM]: Device Addr 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF. [DM]:[DI 0x01]: Device type 0xFF. [DM]: Device Addr 0xFF 0xFF 0xFF 0xFF 0F[DM]e[DM]: Decx [DMDe[DM]: Dedx[DM]:c[DM][DM:y[DM]: DeA [DM] t

RE: Debug UART with SDK 7.1

Seth — Wed, 11 Mar 2015 15:43:12 GMT

I'm currently having the same problem, but Keil packs is requiring that I include app_trace_init and log because I'm using the BLE device manager library, which requires them. Any solutions/way around this to get retarget and printf working again?

RE: Debug UART with SDK 7.1

jt — Fri, 19 Dec 2014 01:23:05 GMT

I'm porting my existing application to SDK 7.1. I just got the new NRF51 dev kit (was using PCA10001), so I'll be doing a more major port in the coming week to that + new SDK.

Wojciech - thanks, didn't know that, will give that a shot

RE: Debug UART with SDK 7.1

jt — Thu, 11 Dec 2014 02:25:51 GMT

Thank you!!

RE: Debug UART with SDK 7.1

Wojciech Jasko — Mon, 08 Dec 2014 10:49:09 GMT

Hello, You have to check which kind of app_uart you have linked to your project. App_trace requires app_uart_fifo.c.

RE: Debug UART with SDK 7.1

cpignol — Sat, 06 Dec 2014 01:51:41 GMT

Found a solution for the UART problem.

Stop using app_trace_init and app_trace_log (deselect app_trace in pack routine selection) import from ble_app_hrs_printf the routine retarget.c

#include <stdio.h>
#include <stdint.h>
#include "simple_uart.h"
#include "nordic_common.h"
#include "nrf51.h"
#include "nrf51_bitfields.h"
#include "boards.h"**

struct __FILE { int handle; /* Add whatever you need here */ };
FILE __stdout;
FILE __stdin;

void retarget_init(void)
{
    simple_uart_config(RTS_PIN_NUMBER, TX_PIN_NUMBER, CTS_PIN_NUMBER, RX_PIN_NUMBER, HWFC);
}

int fputc(int ch, FILE * p_file) 
{
    simple_uart_put((uint8_t)ch);
    return 0;
}

/**
 *@}

 **/

Then use retarget_init(); to initialize the UART and printf to output message. With this setup the baudrate is 38400 no parity no flow control.

This works with PCA10001 (COM3) and PCA10028 (COM6).

Claude

RE: Debug UART with SDK 7.1

Stian Røed Hafskjold — Thu, 04 Dec 2014 09:51:24 GMT

What do you mean with "switched over"? Are you trying to port your existing application over to SDK 7.1, or did you just start with a fresh example from SDK 7.1?

RE: Debug UART with SDK 7.1

cpignol — Thu, 04 Dec 2014 07:12:16 GMT

Hi,

I am also using SDK7.1 with the new nRF6824 (nRF51 Development kit), When I try to use app_trace_init and app_trace_log via Segger USB COM I get the first character of each app_trace_log call. app_trace_log("Test\r\n") will print T. I am using PuTTY 115200bps 8 bits no parity no HWFC. Thanks