[问答]

将X-CUBE-CELLULAR移植到新的调制解调器和主机MCU上卡死该如何解决呢

问答对人有帮助，内容完整，我也想知道答案 0 我正在将 X-CUBE-CELLULAR 移植到新的调制解调器和主机 MCU。将命令“AT”发送到调制解调器时，我卡在了 AT 命令通道的初始调制解调器初始化中。调制解调器是 Nimbelink TC4NAG，主机 MCU 是 Nucleo 144 F429。流量控制在调制解调器上被禁用，并且没有使用流量控制。波特率为 115200。我以 BG96 调制解调器为例。我已经移植了蜂窝应用程序，我可以确认 UART 通信通道在调制解调器和 MCU 之间正常工作。我的问题是当 MCU 发出命令“AT”时，调制解调器响应的“OK”未被处理（就像调制解调器在等待整个“OK”响应之前关闭 UART RX 中断。我已经转在跟踪输出上，我可以看到 MCU 通过 UART 接收到的消息。在下面截取的代码的第 89 行，您将看到我第二次发送“AT”命令时，UART 在响应缓冲区中具有来自先前 AT 命令的响应的字符“O”。是否有超时设置可以调整以修复此行为？ ===== X-Cube-Cellular version : X-CUBE-CELLULAR-6.0.0 ===== -----> New State: BOOT_STATE <----- TC4NAG UART config: BaudRate=115200 / HW flow ctrl=0 CS:CELLULAR_reset_socket_context ********* modem state : CA_MODEM_POWER_OFF IPC:IPC channel 0x20003a80 registered IPC:state 0x1 IPC:active channel handle: 0x20003a80 IPC:inactive channel handle: 0 IPC:HAL_UART_Receive_IT error UTILS:ppposif_client_config ComLib: sim state: rt_state:3 index_slot:0 sim_status:8 =====>CST_notif_callback (Data Cache event=0) =====>CST_notif_callback (Data Cache event=3) <<< Echoclt 1: wait data is ready to get date and time from network!>>> ATCore: AUTOM TASK: BOOT_STATE - NO_EVENT ============ CST_cellular_service_task : autom_event = no event AUTOM TASK: BOOT_STATE - BOOT_EVENT ******* CST_boot_event_mngt **** -----> New State: MODEM_INIT_STATE <----- AUTOM TASK: MODEM_INIT_STATE - MODEM_INIT_EVENT ******* CST_init_state_mngt **** SysCtrl_NL_TC4NAG :Modem Status ON when Power OFF SysCtrl_NL_TC4NAG :Waiting 30000 millisec for modem running... SysCtrl_NL_TC4NAG :...done SysCtrl_NL_TC4NAG :Modem Status ON after Power ON sequence IPC:IPC channel 0x20003a80 registered IPC:state 0x1 IPC:active channel handle: 0x20003a80 IPC:inactive channel handle: 0x20000d1c IPC:IPC select 0x20000d1c IPC:Change IPC channels IPC:state 0x1 IPC:active channel handle: 0x20000d1c IPC:inactive channel handle: 0x20003a80 Datapack: msgtype=4 size=0 (biggest =0) ATCModem:No data to unpack for SID 101 ATCModem: build the cmd (type=5, length=0) ATCModem:==== CMD TIMEOUT = 0 ==== ATCModem:atcm_modem_build_cmd returned status = 0 ATCustom:atcc_getCmd returned status = 0 ATParser:ATParser_get_ATcmd returned action = 0x2 ATCore: Waiting Sema (to=0) * IPC:IPC abort 0x20000d1c BG96:test connection [try number 1] ATCModem: build the cmd (type=4, length=0) ATCModem:==== CMD TIMEOUT = 1000 ==== ATCModem:atcm_modem_build_cmd returned status = 0 ATCustom:atcc_getCmd returned status = 0 ATParser:* SEND (size=3) * AT ATParser:ATParser_get_ATcmd returned action = 0x2 ATCore: Waiting Sema (to=1000) * ATCore:Msg received callback IPC:DBG IPC_RXFIFO_readMsgHeader: index_read = 0 IPC:header_byte1[0x80] header_byte2[0x6] IPC:complete=1 size=6 AT BG96:input message: size=6 ATCustom:start idx=0 end idx=2 size=3 rank=1 ATCustom:atcc_extractElement returned endmsg = 1 BG96:receive an un-expected line... is it a text line ? ATCustom:atcc_analyzeCmd returned action = 0x10 ATParser:analyzeCmd retval = 16 (DATA mode=0) msg_end = 1 ATParser:ATParser_parse_rsp returned action = 0x10 ATCore:RAW ACTION (analyze_action_result) = 0x10 ATCore:CLEANED ACTION=16 (data mode=0) ATCore: Sema Timeout (=1000) !!! * ATCore: Sema Freed * ATCore:TIMEOUT EVENT(1000 ms) IPC:IPC abort 0x20000d1c BG96:test connection [try number 2] ATCModem: build the cmd (type=4, length=0) ATCModem:==== CMD TIMEOUT = 1000 ==== ATCModem:atcm_modem_build_cmd returned status = 0 ATCustom:atcc_getCmd returned status = 0 ATParser:* SEND (size=3) * AT ATParser:ATParser_get_ATcmd returned action = 0x2 ATCore: Waiting Sema (to=1000) * ATCore:Msg received callback IPC:DBG IPC_RXFIFO_readMsgHeader: index_read = 8 IPC:header_byte1[0x80] header_byte2[0x6] IPC:complete=1 size=6 OAT BG96:input message: size=6 ATCustom:start idx=0 end idx=2 size=3 rank=1 ATCustom:atcc_extractElement returned endmsg = 1 BG96:receive an un-expected line... is it a text line ? ATCustom:atcc_analyzeCmd returned action = 0x10 ATParser:analyzeCmd retval = 16 (DATA mode=0) msg_end = 1 ATParser:ATParser_parse_rsp returned action = 0x10 ATCore:RAW ACTION (analyze_action_result) = 0x10 ATCore:CLEANED ACTION=16 (data mode=0) ATCore: Sema Timeout (=1000) !!! * ATCore: Sema Freed *** ATCore:TIMEOUT EVENT(1000 ms) 这是 MCU 仅在 UART RX 线上看到的内容的捕获。调制解调器打开了回声模式。它按预期响应，但调制解调器没有看到“确定”响应来处理它。 AT OK AT OK AT OK AT OK AT OK AT OK AT OK AT OK AT OK AT OK AT OK AT OK AT OK AT OK 0
2022-12-13 08:46:37　　评论淘帖0 邀请回答您可以邀请以下用户，快速回答问题 × wang21cj 该类别下有 44 个回答。邀请回答新星之火12138 该类别下有 41 个回答。邀请回答 chm5 该类别下有 39 个回答。邀请回答 hgimtk 该类别下有 33 个回答。邀请回答 HengDu 该类别下有 30 个回答。邀请回答 jghgfdssas 该类别下有 28 个回答。邀请回答 hwp0415229 该类别下有 28 个回答。邀请回答可口可甜该类别下有 26 个回答。邀请回答 kingnet6688 该类别下有 26 个回答。邀请回答颜刚YanG 该类别下有 26 个回答。邀请回答 zyh34997 该类别下有 25 个回答。邀请回答柱子图宁该类别下有 25 个回答。邀请回答 jenny042 该类别下有 25 个回答。邀请回答 kingnet9999 该类别下有 25 个回答。邀请回答 andyfly7 该类别下有 25 个回答。邀请回答麻酱该类别下有 25 个回答。邀请回答 iyfhnvbn 该类别下有 24 个回答。邀请回答哈哈神神该类别下有 24 个回答。邀请回答成长的小师弟该类别下有 24 个回答。邀请回答 gXDhn 该类别下有 24 个回答。邀请回答举报宜家相关推荐 • 使用X-CUBE-CELLULAR设置波段出错怎么解决呢 195 • 求AN5249移植指南 185 • 如何更改BG96调制解调器配置？ 306 • X-CUBE-CELLULAR是否需要2个uart才能工作呢 210 • 在X-CUBE-CLOUD页面上我可以下载X-CUBE-AZURE吗？ 237 • 线缆调制解调器的原理是什么？ 2435 • Virtex 2 Pro与Fargo Maestro 20 GSM调制解调器连接问题的解决办法？ 939 • 如何在STMOD+连接器上将X-CUBE-CELLULAR Framework与STEVAL-STWINKT1和Quectel BG96一起使用？ 203 • 如何检查调制解调器是否挂起？ 327 • Qualcomm 212 LTE IoT调制解调器有哪些特性及应用？ 2134 1个回答

答案对人有帮助，有参考价值 0 我在 Sysctrl power on 函数中切换了 Power up 和 Open channel 的顺序。恢复到原来的顺序，即 1) 通电 2) 打开 Uart 通道似乎已经解决了这个问题。

2022-12-13 14:19:41 评论举报杨静