SDK 14 printf() Issue

RE: SDK 14 printf() Issue

operator — Sat, 07 Oct 2017 00:51:51 GMT

Hi Jørgen, I believe I found my issue but will respond here for the benefit of any future folks who may encounter a similar problem.

To address your questions, I'm using Keil uVision so presumably armcc v5.06.

I did test the retarget.c from SDK 13.1-alpha but the issue persisted.

The issue eventually turned out to be, or so it appears, with a sensor read timeout timer that had been implemented. The sensor is present on production hardware but not on the eval board which caused something to hang somewhere I couldn't locate.

This wasn't difficult to fix but was ferociously hard to diagnose. I enabled RTT but, oddly, this made the issue go away. There were also no significant messages related to the failure even with the log level set to debug. I only managed to figure it out by systematically commenting out chunks of code until things started working and narrowing it down from there.

RE: SDK 14 printf() Issue

Jørgen Holmefjord — Wed, 04 Oct 2017 12:51:48 GMT

Which compiler are you using? Have you tested the retarget.c file from SDK 13 1.alpha to see if the issue is related to this file?

RE: SDK 14 printf() Issue

operator — Thu, 28 Sep 2017 20:15:24 GMT

Hi Jørgen, this is a port of an existing, custom SDK 13.0.0-1alpha project, where printf() is working just fine.

The UART portion is based heavily upon the ble_app_uart example from SDK 14.0.0.

The results are the same on Tera Term, Realterm, and minicom. Any of these terminals correctly displays the initial printf() calls from main() so I'm reasonably certain the issue isn't on the terminal side.

RE: SDK 14 printf() Issue

Jørgen Holmefjord — Thu, 28 Sep 2017 12:06:09 GMT

I'm not able to reproduce this issue. Is this based off some example in the SDK, or is it a custom project? Which terminal software are you using?