I have starting working with UART. I see that there are two options for configuring it: UART_0_ASYNC and UART_0_INTERRUPT_DRIVEN. I want to use ASYNC option for my UART, but when I enable this option, the device is unable to be provisioned anymore. It means if I just enable this configuration in the chat example, it breaks the application for provision.
I also tried to initialize the UART only when the device is provisioned, but it has no effect.
Hi Ashish!
Have you tried doing it using a prj.conf configuration?
I also tried to initialize the UART only when the device is provisioned, but it has no effect.
Could you expand a bit on this? Are you provisioning the device and then re-flashing it?
Best regards,
Elfving
Hi Elfving
Yes, I tried with the prj.conf also by adding following
CONFIG_SERIAL=y
CONFIG_UART_ASYNC_API=y
CONFIG_UART_0_INTERRUPT_DRIVEN=n
CONFIG_UART_0_ASYNC=y
Simple explanation is just by adding the above code in prj.conf or enabling the UART from nrf configure tool, the application is disabled for Mesh provisioning.
The issue is somewhere with UART_0_ASYNC because if you configure prj.conf with following, it is okay:
CONFIG_UART_ASYNC_API=y
CONFIG_SERIAL=y
CONFIG_UART_0_INTERRUPT_DRIVEN=y
I use chat example in nrf Connect SDK v1.7.1.
I am not provisioning and then reflashing but everytime I erase all to check the sanity.
Hello Ashish,
That is a bit odd, and I am not able to reproduce it.
UART_ASYNC shouldn't make much of a difference in the context of provisioning either. I would assume that it is mainly something else that it causes.
Is this a clean and un-modified chat example? Is this an issue on any other Mesh samples? Have you noticed anything else not working on the node besides issues provisioning?
Ashishsult said:I am not provisioning and then reflashing but everytime I erase all to check the sanity.
Could you expand a bit on this? I am still not sure about what you are doing to initialize UART after it is provisioned.
Best regards,
Elfving
chat-working_fine.zipchat-not_working.zip
Hi Elfving, I have now attached the application files here.
My main aim is to get data from UART and sent it using BLE mesh. However, I have narrow down the issue already that there is something to so with UART ASYN configuration. So, please check.
Hey!
Do you have any issues when enabling UART ASYNC on an otherwise unmodified example?
Best regards,
Elfving
Hi Elfving, I checked now couple of other mesh examples. It seems that only in this Chat example the async creates issue.
I see.
And that is with a completely unmodified example as well?
Might be that when you open the chat example you open it along with a series of other modifications as well, that are the actual cause of the problem. To make sure the example you use isn't modified as well as keeping the projects you have in this version of the SDK, you could try and install another version of NCS and see if the issue occurs in that version of the chat example as well.
Best regards,
Elfving
I see.
And that is with a completely unmodified example as well?
Might be that when you open the chat example you open it along with a series of other modifications as well, that are the actual cause of the problem. To make sure the example you use isn't modified as well as keeping the projects you have in this version of the SDK, you could try and install another version of NCS and see if the issue occurs in that version of the chat example as well.
Best regards,
Elfving
Hi Elving, yes, I tried with unmodified example in two SDK versions 1.71. and 1.6.1. And both of them shows issue during provisioning.
Are these the configurations you added when you attempted to provision?
Ashishsult said:CONFIG_SERIAL=y
CONFIG_UART_ASYNC_API=y
CONFIG_UART_0_INTERRUPT_DRIVEN=n
CONFIG_UART_0_ASYNC=y
And did you provision using the nRF Mesh app? Where any other nodes provisioned as well?
Best regards,
Elfving
Yes, I add these lines in the prj.conf file, run CMake and then build. I connect, erase device and flash it to the device using Segger.
Next, I use Mobile nRF Mesh App v3.1.6 to provision the device (which fails).
Other nodes in my use case doesn't have the UART so are successfully provisioned.
What other nodes are on the network? And how many?
Best regards,
Elfving
I wanted to have three nodes: 1. With UART as client, 2. Without UART as Relay and 3. Without UART as Server.
But I don't understand how this issue of provisioning a device linked with it.
Because even if there is nothing provisioned already, we have the same issue.
May be you can try to provision the device (nrf52832) with the changes in prj.conf as mentioned before and see if you are able to do so. I already posted the code as well before.
