[QCC3020] ADK 6.4以上单耳死机

黃子衡

如题, 默认工程只要对耳无电或找不着的时候, 将会进入IDLE, 并且停滞数秒后重启, 而且是一直反覆重启无限多次.
尝试ADK 6.3没有此问题. 提供以下部分log给大师们看看.

在这行以后为重启1122.762 apps1: 112A: appSmHandlePeerSyncStatus 0
个人已发case到高通support官网, 还未有回应.
目前只能想办法修改为进入pairing, 避免IDLE导致死机, 但还不知如何做, 请大师解惑.

1122.754 apps1: 110D: appPeerSigHandleInternalMsgChannelTxRequest, state 1 chan 2 size 15
1122.754 apps1: 110E: appPeerSyncHandlePeerSigMsgChannelTxCfm, failed, status 6
1122.754 apps1: 110F: appConnRulesSetEvent, new event 0000000000000400, events 0011000030480500
1122.754 apps1: 1110: appConnRulesCheck, starting events 0011000030480500
1122.754 apps1: 1111: appConnRulesCheck, running rule 0, status 0, events 0011000030480500
1122.756 apps1: 1112: rulePageScanUpdate, (sm_connectable,peer,handset,peer_sync,peer_handset,peer_handset_tws)=100000, ps=1
1122.756 apps1: 1113: appConnRulesCheck, rule ignored
1122.756 apps1: 1114: appConnRulesCheck, running rule 1, status 0, events 0011000030480500
1122.757 apps1: 1115: ruleBleConnectionUpdate Paired(peer:1, handset:1). BLE(allowed:0,allowed_out_case:0,has:0,is_trying:0)
1122.757 apps1: 1116: ruleBleConnectionUpdate, IGNORE - no change
1122.757 apps1: 1117: appConnRulesCheck, rule ignored
1122.757 apps1: 1118: appConnRulesCheck, running rule 2, status 0, events 0011000030480500
1122.757 apps1: 1119: ruleCheckUpgradable, block as out of case and not permitted
1122.757 apps1: 111A: appConnRulesCheck, rule in progress
1122.759 apps1: 111B: appConnRulesCheck, running rule 40, status 4, events 0011000030480500
1122.759 apps1: 111C: ruleOutOfCaseConnectPeer
1122.759 apps1: 111D: ruleConnectPeer, defer as peer sync not complete
1122.759 apps1: 111E: appConnRulesCheck, rule deferred
1122.759 apps1: 111F: appConnRulesCheck, running rule 41, status 4, events 0011000030480500
1122.759 apps1: 1120: ruleOutOfCaseConnectHandset
1122.759 apps1: 1121: ruleConnectHandset, reason 3
1122.759 apps1: 1122: ruleConnectHandset, ignore as peer sync has failed
1122.759 apps1: 1123: appConnRulesCheck, rule ignored
1122.759 apps1: 1124: appConnRulesSetStatus, rule 41, status 3
1122.759 apps1: 1125: appConnRulesCheck, running rule 61, status 4, events 0011000030480500
1122.759 apps1: 1126: ruleSelectMicrophone, defer as peer sync not complete
1122.759 apps1: 1127: appConnRulesCheck, rule deferred
1122.759 apps1: 1128: appConnRulesCheck, in progress, filtered events 0011000010480500
1122.762 apps1: 1129: appUpgradeAllowUpgrades(0) - success:1 (sts:0)
1122.762 apps1: 112A: appSmHandlePeerSyncStatus 0
Saw '[0x10404:0x10408]: The dongle has no link to the DUT: could not read 1 transactions from device': retrying
Probable reset: suppressing further errors and preparing to read from start of buffer
Couldn't find a log string at address 0xb4edb5a7
Couldn't find a log string at address 0x401ae1e
Couldn't find a log string at address 0xe59721c3
Couldn't find a log string at address 0x5cbc7917
Couldn't find a log string at address 0xeed3aaaf
Couldn't find a log string at address 0x934ace7d
Couldn't find a log string at address 0x79e484e3
Couldn't find a log string at address 0x46631557
Couldn't find a log string at address 0xe5bd680c
Couldn't find a log string at address 0xaac6d1cd

zhaopeng2511

死机问题其实是最好解的，挂平台跑，panic死机后平台会停下来，看callstack死机函数调用顺序。这样一下子就可以定位到死机在哪里，死机前调用了哪些函数都一目了然，剩下的就是分析原因了

黃子衡

zhaopeng2511 发表于 2020-3-5 11:15
死机问题其实是最好解的，挂平台跑，panic死机后平台会停下来，看callstack死机函数调用顺序。这样一下子就 ...

这问题最难的部分是没出现PANIC, 可见得应该是底层导致死机, 并非app的部分.
应当只有高通出patch能解.

y1054642361

请问你用的是ADK6.4.2.26还是ADK6.4.0.43?

zhaopeng2511

黃子衡 发表于 2020-3-5 11:58
这问题最难的部分是没出现PANIC, 可见得应该是底层导致死机, 并非app的部分.
应当只有高通出patch能解.

底层死机一样会panic的，但有时panic后callstack中没有用信息倒是有可能的。如果说平台没有挂掉，软件还在跑着，但却一直开关，那就是上层软件跑进死循环逻辑中出不来了

黃子衡

y1054642361 发表于 2020-3-5 14:53
请问你用的是ADK6.4.2.26还是ADK6.4.0.43?

两种都有试过一样

co9

请问这个问题的根源找到了吗

黃子衡

co9 发表于 2020-3-10 16:18
请问这个问题的根源找到了吗

发出问题但无人回覆.
您是否有遇到呢?

黃子衡

黃子衡 发表于 2020-3-10 16:44
发出问题但无人回覆.
您是否有遇到呢?

某印度籍工程师回覆了, 但照他的说法我build不了啊.
====================
We are not sure whats happening. The chips might be panicking somewhere, and that might trigger reset.

Set PanicAction=2 in subsys0_config3.html and rebuild and deploy dev config filesystem. That will stop EB from resetting if it panics.

Then please take a coredump which could be taken from MDE->Tools->Obtain Coredump with apps SQIF included.
==============================

Build失败, 显然PanicAction=2是有问题的

==============================================================================
ERROR:
line 7, column 15: Unknown name: PanicAction

1 error found
==============================================================================
Failed