ble_app_uart sdk 15 dosnt work

RE: ble_app_uart sdk 15 dosnt work

bjorn-spockeli — Mon, 25 Jun 2018 11:24:58 GMT

Hi Robert,

my colleague Martin has posted the solution for this issue in this answer.

Bjørn

RE: ble_app_uart sdk 15 dosnt work

Josep Robert — Fri, 22 Jun 2018 17:38:04 GMT

nRF SDK version 15.0

nRF52 Development Kit board (PCA10040)

nRF52 DK v1.1.0 2016.19

Example code:

C:\Nordic_semi\nRF5_SDK_15.0.0\examples\ble_peripheral\ble_app_uart\pca10040\s132\ses\ble_app_uart_pca10040_s132.emProject

retarget.c file

Original line 100:

int __putchar(int ch, FILE * p_file)

Modifien line 100:

int __putchar(int ch, __printf_tag_ptr * p_file)

Both lines, original and modified, give me the same error: Conflicting types for '__putchar'.

I'd like to begin with this example and, once working, modified for a low power, closing and opening the UART.

Thanks.

RE: ble_app_uart sdk 15 dosnt work

Joakim Jakobsen — Thu, 21 Jun 2018 13:33:08 GMT

[quote user="navarrocantero"]Otherwise in the uart example, the file retarget.c throws a error in line 100 [/quote]

Take a look at this thread, regarding the same issue.

https://devzone.nordicsemi.com/f/nordic-q-a/34784/conflicting-types-for-_putchar

Cheers.

RE: ble_app_uart sdk 15 dosnt work

Joakim Jakobsen — Wed, 20 Jun 2018 08:01:59 GMT

Ok, so when there is an error in your application, you won't see the device in your iOS app.
This is because it probably won't be advertising.

Are you sure this is an unmodified example? The uart example should run just fine out-of-the-box.
You could try the pre-compiled hex file (containing both the softdevice and the application) and see if that works.
The hex file can be found in your SDK_Folder/examples/ble_peripheral/ble_app_uart/hex

As for the "int __putchar (int ch, FILE * p_file)", as far as I know there should be two '_'.
What kind of error are you getting here?
As suggested below, you should you try debugging to find out what is causing this error.

Best regards,
Joakim.

RE: ble_app_uart sdk 15 dosnt work

navarrocantero — Tue, 19 Jun 2018 11:47:38 GMT

Can you see the device in nRF Connect advertising with a wrong name, or can't you see the device at all?

Exactly, I cant see anything in my Ios apps

Are you using nRF Connect on a smartphone or nRF Connect for desktop?

Im ussing the nrf Toolbox and nrf Connect apps in Ios 11.

This is with ble_peripheral/ble_app_blinky

And with ble_peripheral/ble_app_uart i cant see any ssid in the app.

Otherwise in the uart example, the file retarget.c throws a error in line 100

int __putchar(int ch, FILE * p_file) and I renamed it  to

int _putchar(int ch, FILE * p_file) ( the diference is a one '_' minus)




Regards Joakim!

RE: ble_app_uart sdk 15 dosnt work

Raghav Iyer — Tue, 19 Jun 2018 11:32:12 GMT

Hi,

I am assuming you are using Segger embedded studio and a dk. try the following

enable RTT logging and make sure logger serial backend is disabled in sdk_config.h

run the app in debug mode and see if you notice any error logs

try commenting the uart_init function or, if you need it, try connecting a device to the rx and tx pins and then try.

RE: ble_app_uart sdk 15 dosnt work

Joakim Jakobsen — Tue, 19 Jun 2018 11:24:41 GMT

Hi!

So you can see the advertising name, "Nordic_Blinky", when using the ble_app_blinky example.

But you can't see the advertising name when using the uart examples? Can you see the device in nRF Connect advertising with a wrong name, or can't you see the device at all?

[quote user=""]Its normal that I cant see the ssid in the nrfconnect app?[/quote]

No, you should be able to see the device in nRF Connect when using the UART examples.

Are you using nRF Connect on a smartphone or nRF Connect for desktop?

Best regards,
Joakim.