- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Could someone help to explain the details for debugging trace where 20737 is not able to keep connection.
The connection is made but down immediately.
I'm using bluez on Linux to connect to 20737. The disconnection is not managed neither at 20737 nor Linux system side. It just happened autonomously.
16:05:25 - 0201050a097242532d30303a354507ff
16:05:25 - 0000ffffffff
16:05:25 AppTimer(adv, conn) stopped: 0
16:05:25 noAdv
16:05:25 AppTimer(adv, conn) stopped: 0
16:05:25 BLE_high_un_adv:timer(0)
16:05:28 Connection is UP.
16:05:28 profile idle timer stop
16:05:28 connUp
16:05:28 noAdv
16:05:29 SMP Conn Down
16:05:29 SMPTmrStp
16:05:29 connDown
16:05:29 ConnDnStopIdlTmr
16:05:29 - 0201050a097242532d30303a354507ff
16:05:29 - 0000ffffffff
16:05:29 BLE_high_un_adv:timer(0)
16:05:44 AppTimer(adv, conn) stopped: 2
16:05:44 BLE_low_un_adv:timer(0)
16:06:28 - 0201050a097242532d30303a354507ff
16:06:28 - 0000ffffffff
16:06:28 AppTimer(adv, conn) stopped: 0
16:06:28 noAdv
16:06:28 AppTimer(adv, conn) stopped: 0
16:06:28 BLE_high_un_adv:timer(0)
16:06:44 AppTimer(adv, conn) stopped: 2
16:06:44 BLE_low_un_adv:timer(0)
16:06:53 AppTimer(adv, conn) stopped: 0
16:06:53 BLE_high_un_adv:timer(0)
16:07:44 AppTimer(adv, conn) stopped: 2
16:07:44 BLE_low_un_adv:timer(0)
16:07:52 - 0201050a097242532d30303a354507ff
16:07:52 - 0000ffffffff
16:07:52 AppTimer(adv, conn) stopped: 0
16:07:52 noAdv
16:07:52 AppTimer(adv, conn) stopped: 0
16:07:52 BLE_high_un_adv:timer(0)
16:08:44 AppTimer(adv, conn) stopped: 2
16:08:44 BLE_low_un_adv:timer(0)
16:08:52 - 0201050a097242532d30303a354507ff
16:08:52 - 0000ffffffff
16:08:52 AppTimer(adv, conn) stopped: 0
16:08:52 noAdv
16:08:52 AppTimer(adv, conn) stopped: 0
16:08:52 BLE_high_un_adv:timer(0)
16:09:44 AppTimer(adv, conn) stopped: 2
16:09:44 BLE_low_un_adv:timer(0)
16:09:52 - 0201050a097242532d30303a354507ff
16:09:52 - 0000ffffffff
16:09:52 AppTimer(adv, conn) stopped: 0
16:09:52 noAdv
16:09:52 AppTimer(adv, conn) stopped: 0
16:09:52 BLE_high_un_adv:timer(0)
16:10:44 AppTimer(adv, conn) stopped: 2
16:10:44 BLE_low_un_adv:timer(0)
16:10:52 - 0201050a097242532d30303a354507ff
16:10:52 - 0000ffffffff
16:10:52 AppTimer(adv, conn) stopped: 0
16:10:52 noAdv
16:10:52 AppTimer(adv, conn) stopped: 0
16:10:52 BLE_high_un_adv:timer(0)
16:11:44 AppTimer(adv, conn) stopped: 2
16:11:44 BLE_low_un_adv:timer(0)
16:11:49 Connection is UP.
16:11:49 profile idle timer stop
16:11:49 connUp
16:11:49 noAdv
16:11:50 SMP Conn Down
16:11:50 SMPTmrStp
16:11:50 connDown
16:11:50 ConnDnStopIdlTmr
16:11:50 - 0201050a097242532d30303a354507ff
16:11:50 - 0000ffffffff
16:11:50 BLE_high_un_adv:timer(0)
16:12:02 Connection is UP.
16:12:02 profile idle timer stop
16:12:02 connUp
16:12:02 noAdv
16:12:03 SMP Conn Down
16:12:03 SMPTmrStp
16:12:03 connDown
16:12:03 ConnDnStopIdlTmr
16:12:03 - 0201050a097242532d30303a354507ff
16:12:03 - 0000ffffffff
16:12:03 BLE_high_un_adv:timer(0)
Solved! Go to Solution.
- Labels:
-
Debug
-
MasterSlave
-
SDK 2.X
-
Timers
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
An air trace may be more insightful in this instance. Where are you located? I can get the local broadcom representative to contact you if viable.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks boont!
Let's discuss this by email.