BLE_ERRORINTSTAT happens during long-term test

⚠️
Hi there.. thanks for coming to the forums. Exciting news! we’re now in the process of moving to our new forum platform that will offer better functionality and is contained within the main Dialog website. All posts and accounts have been migrated. We’re now accepting traffic on the new forum only - please POST any new threads at https://www.dialog-semiconductor.com/support . We’ll be fixing bugs / optimising the searching and tagging over the coming days.
4 posts / 0 new
Last post
firebird
Offline
Last seen: 1 year 10 hours ago
Joined: 2019-07-12 09:48
BLE_ERRORINTSTAT happens during long-term test

Hi, teams.

 

As titles says, I got BLE_ERRORINTSTAT_BIT during long-term test.

It happens within 24 hours normally, but varys from in a few hours to more than 12 hours.

How can I debug this problem?

Device: 
firebird
Offline
Last seen: 1 year 10 hours ago
Joined: 2019-07-12 09:48
Additional comment on testing

Additional comment on testing environment:

It was very crowded condition. 50 ~ 100 bluetooth (BLE or classic) devices existed, and testing device was working and scanning as provisioned MESH node.

KevinL
Offline
Last seen: 1 year 4 months ago
Staff
Joined: 2017-11-06 13:52
Hi Firebird,

Hi Firebird,

What role does the board play in BLE Mesh?

Did you try to put the testing board into an environment without too many bluetooth devices to observe the testing result?

 

firebird
Offline
Last seen: 1 year 10 hours ago
Joined: 2019-07-12 09:48
Device was working as MESH

Device was working as MESH node, and provisioned state.

It seems that only a single node in MESH network has the same error, and not related to the model which device includes in.

In summary, it was only observed in DA1468x MESH node.

I tried to reproduce this symptom in non-mesh condition, for example, BLE central, but so far it is not reproduced.