Coexistence examples: SDK UART coexistence example

RE: Coexistence examples: SDK UART coexistence example

Min — Tue, 20 Aug 2019 14:00:48 GMT

Hi Edvin,

This part is all working well with RTT or SES Debug Terminal. My goal is to have the the printf call be sent to regular UART terminal. If you un-comment the code in main.c for printf, you will understand what I was talking about.printf should be sent to uart but instead, the statement shows up in RTT or SES Debug Terminal.

I solved this problem by enable the Module RETARGET.

Thanks.

RE: Coexistence examples: SDK UART coexistence example

Edvin — Tue, 20 Aug 2019 06:43:51 GMT

Hello,

I wasn't able to compile your project. I had to add some include paths in order to compile, so I guess the folder structure is a bit different on your project, or you moved some files. It shouldn't really matter.

But when I had all the .c and .h files included, I couldn't really replicate your issue:

It looks normal here. Can you try to unzip your project in a set of unmodified SDK for Mesh and normal SDK and see if it still behaves the same? It shouldn't print the characters three times.

To be sure, you can try the attached .hex file (remember to flash the softdevice as well).

devzone.nordicsemi.com/.../light_5F00_switch_5F00_server_5F00_nrf52840_5F00_xxAA_5F00_s140_5F00_6.1.1.hex

If you test this, you can monitor the RTT Viewer by using JLink RTT Viewer.

If the characters are still quadruple it means that there is something wrong with your uart terminal.

Best regards,

Edvin

RE: Coexistence examples: SDK UART coexistence example

Min — Mon, 19 Aug 2019 16:29:35 GMT

Hi Edvin,

I believe I found where the problem is. I have to enable the module RETARGET to make it work!

Thanks for the help!

RE: Coexistence examples: SDK UART coexistence example

Edvin — Mon, 19 Aug 2019 06:28:26 GMT

Hello,

I believe I have to see your implementation to understand why this happens. Is it possible to zip the project folder and send it? That is, the folder which includes the Segger Embedded Studio (SES) project file, as well as the src folder which includes the main.c file.

RE: Coexistence examples: SDK UART coexistence example

Min — Fri, 16 Aug 2019 19:09:19 GMT

Hi Edvin,

Thanks for the response and I agree with you. I will wait for the future Nordic Mesh release on this one...

I was able to add uart to the server code in light_switch example under Mesh 3.2.0 + SDK 15.3.0 release.

It received data from UART fine, however, all the printf calls go directly to SES Debug Terminal instead of an UART terminal as you can see as follows:

<t: 0>, main.c, 439, ----- BLE Mesh Light Switch Server Demo -----
<t: 13022>, main.c, 357, Initializing and adding models
<t: 13025>, main.c, 252, App OnOff Model Handle: 2
<t: 17898>, mesh_app_utils.c, 65, Device UUID (raw): C3D12D8D4134B54C8DDF96A0D164F5B8
<t: 17901>, mesh_app_utils.c, 70, Device UUID : 8D2DD1C3-3441-4CB5-8DDF-96A0D164F5B8
data received from uart: ttttt

data received from uart: eeeee

data received from uart: sssss

data received from uart: ttttt

.....

I am totally lost as why this happens. Will you be able to shed some light on this?

How do we direct printf calls to uart instead of SES debug terminal in Mesh server code?

Thanks!

RE: Coexistence examples: SDK UART coexistence example

Edvin — Fri, 16 Aug 2019 12:06:54 GMT

Hello,

You can take a look at this site:

https://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.meshsdk.v3.2.0%2Fmd_doc_getting_started_gatt_proxy.html&cp=5_2_1_5_1

But it may be easier to add the NUS service to any of the other examples than adding the provisioning service to the coexistence example.

[quote user="mlou"]It is beyond my ability to answer for now since I just started working with nRF for about couple weeks. But I am sure you may figure it out from the call stack above.[/quote]

Unfortunately I can't tell what's going on from the callstack. If you .zip the project folder, that would make it easier to see.

Best regards,

Edvin

RE: Coexistence examples: SDK UART coexistence example

Min — Wed, 14 Aug 2019 16:18:18 GMT

Hi Edvin,

I understand that having both PB-ADV and PB-GATT is a luxury...Will it be possible for future Mesh SDK supports dynamic provisioning? Either based on initial configuration or signal sensing, to support one instead of both to save valuable resources?

Just a layman's thought...

Thanks.

RE: Coexistence examples: SDK UART coexistence example

Min — Wed, 14 Aug 2019 14:37:35 GMT

Hi Edvin,

What you said above is true. Below is the call stack trace for your reference:

As for your question: "How are you including the PG-GATT service? Do you add a new advertising set, or just add the service?"

It is beyond my ability to answer for now since I just started working with nRF for about couple weeks. But I am sure you may figure it out from the call stack above. My guess is that the code is trying to add the service to an existing advertising set, since we do have an advertising set to support the standard PB-ADV already in the coexistence example.

If "Not enough memory to configure a new advertising handle", will it make more difficult to create a new advertising set?

I tried increase NRF_SDH_BLE_VS_UUID_COUNT = 4, it gave me the same error.

Was this an educated guess? Please feel free to correct me...

I appreciate your help!

RE: Coexistence examples: SDK UART coexistence example

Edvin — Wed, 14 Aug 2019 06:36:32 GMT

Try to increase NRF_SDH_BLE_VS_UUID_COUNT in sdk_config.h

What SDK version are you using, and what is the function that returned err_code = 4 that was passed onto APP_ERROR_CHECK(err_code) before line 147 in mesh_adv.c. Was it sd_ble_gap_adv_set_configure()?

If so, it says on line 1802 in ble_gap.h (the description of sd_ble_gap_adv_set_configure() ):

* @retval ::NRF_ERROR_NO_MEM Not enough memory to configure a new advertising handle. Update an existing advertising handle instead.

How are you including the PG-GATT service? Do you add a new advertising set, or just add the service?

RE: Coexistence examples: SDK UART coexistence example

Min — Tue, 13 Aug 2019 16:34:37 GMT

Hello Edvin,

Thanks for the response. I was able to build, however, I got this error below:

<info> app: Debug logging for UART over RTT started.
<error> app: ERROR 4 [NRF_ERROR_NO_MEM] at ......\nRF5SDK.15.3.0\nrf5SDKforMeshv320src/examples/common/src/mesh_adv.c:147
PC at: 0x0005C62D
<error> app: End of error report

What does it mean?

1. I am out of memory?

2. I have not allocated memory?

3. How do I work around it?

Thanks.

RE: Coexistence examples: SDK UART coexistence example

Edvin — Mon, 12 Aug 2019 12:51:53 GMT

Hello,

It is correct. The SDK coexistance uart example doesn't support PB-GATT out of the box, but it is possible to add it. Just look at how it is done in the light switch client or server examples.

Best regards,

Edvin