Timer_older_than return false in light switch example with UART communication

RE: Timer_older_than return false in light switch example with UART communication

Bjørn Kvaale — Tue, 22 May 2018 12:52:35 GMT

But I thought you specifically told me that you integrated the UART example with the mesh sdk? You will need a connection interval if you want to add normal BLE communication & mesh communication in the same device. Just take a look at the regular UART example (any ble_peripheral example for that matter) & one of the first things you will see is the connection interval.

RE: Timer_older_than return false in light switch example with UART communication

Arij — Mon, 21 May 2018 13:39:47 GMT

i searched in all UART files but i didn't find these parameters, maybe there is a different way to do it, or do i have to modify light switch client example?

In ble mesh we are talking about advertising and scanning, i don't think there is connection interval, am i right?

RE: Timer_older_than return false in light switch example with UART communication

Bjørn Kvaale — Fri, 18 May 2018 12:44:36 GMT

You can find it in the uart main file. Just search for MIN_CONN_INTERVAL MSEC_TO_UNITS & you should be able to find it.

RE: Timer_older_than return false in light switch example with UART communication

Arij — Thu, 17 May 2018 12:55:24 GMT

Sorry for asking too much, where can i find these lines in the light switch demo,

Is it in ble_gap.h ?

RE: Timer_older_than return false in light switch example with UART communication

Bjørn Kvaale — Wed, 16 May 2018 14:07:57 GMT

define MIN_CONN_INTERVAL MSEC_TO_UNITS(100, UNIT_1_25_MS)
define MAX_CONN_INTERVAL MSEC_TO_UNITS(500, UNIT_1_25_MS)

Set the min connection interval to 100 milliseconds (as according to comments here).

#define APP_ADV_INTERVAL 288

I would start by only increasing the min conn interval & testing to see if that helps. If that doesn't help, try increasing the advertising interval too.

RE: Timer_older_than return false in light switch example with UART communication

Arij — Tue, 15 May 2018 12:45:31 GMT

I don't know how to do it, can you please help me on that?

RE: Timer_older_than return false in light switch example with UART communication

Bjørn Kvaale — Tue, 15 May 2018 12:34:34 GMT

Did you try to update the connection & advertisement intervals by increasing their values? I would increase those values a bit every time until you do not get the error anymore.

RE: Timer_older_than return false in light switch example with UART communication

Arij — Mon, 14 May 2018 14:27:11 GMT

Thank you for your reply. I double checked in map file and i think it refers to TIMER_OLDER_THAN() function,

here what i found in this file

I included uart modules to the light switch client example and did some changes in the flash_placement.xml so i didn't follow the coexistence with other nordic SDK's , i used the UART example from SDK v14.2.

I agree with you about the two functions taking too much time to complete, what should i do in this case?

RE: Timer_older_than return false in light switch example with UART communication

Bjørn Kvaale — Mon, 14 May 2018 13:25:42 GMT

Could you double check in your map file (found inside the build folder of your example code) that the 0x0002EF8A refers to the TIMER_OLDER_THAN() or bearer_handler_action_end() function just to double check this is where the error is occuring? Just take a look at the .map file & try to find the 0x0002EF8A location in memory & let us know what the comment is for that memory location. It might be that this exact location is not in memory, but then you can take a look at the next values that are in between this memory location.

Did you refer to the coexistence with other nordic SDK's to merge the mesh sdk with uart? Which UART example code version are you using? SDK 14.2?

My guess is that uart_putstring() & uart_getstring() are taking too much time to complete, which then leads to the MESH ASSERT message you mention. This line in the link above might be helpful too: "By design, the SoftDevice activity is prioritized over mesh activity. Therefore, you should keep the connection and advertisement intervals used by the SoftDevice as large as possible (i.e. infrequent) when using Bluetooth low energy connections."