新文件 2 （匹配64次）
行 6: [14298.202604] cnss: FW sram dump start /var/crash/2017-08-05-20-58-28-q6-sram.bin …
行 7: [14298.202653] cnss: FW sram dump create file /var/crash/2017-08-05-20-58-28-q6-sram.bin failed
行 8: [14298.202661] cnss: FW sram dump end, status -13
行 12: [14298.202702] cnss: Timeout waiting for FW ready indication
行 13: [14298.202712] cnss: Posting event: RECOVERY(9), state: 0x2190
行 14: [14298.202719] cnss: PM stay awake, state: 0x2190, count: 1
行 15: [14298.202725] cnss_pm_stay_awake: NAP-TODO
行 16: [14298.202741] cnss: PM relax, state: 0x2190, count: 0
行 17: [14298.202747] cnss_pm_relax: NAP-TODO
行 18: [14298.202752] cnss: cnss_driver_event_work
行 19: [14298.202756] cnss: PM stay awake, state: 0x2190, count: 1
行 20: [14298.202758] cnss_pm_stay_awake: NAP-TODO
行 21: [14298.202762] cnss: Processing driver event: RECOVERY(9), state: 0x2190
行 22: [14298.202765] cnss: Driver recovery is triggered with reason: TIMEOUT(3)
行 23: [14298.202768] cnss: Recovery is already in progress!
行 24: [14298.202773] cnss: PM relax, state: 0x2190, count: 0
行 25: [14298.202781] cnss_pm_relax: NAP-TODO
行 1509: [14869.401063] cnss: Posting event: UNREGISTER_DRIVER(8)-sync, state: 0x2190
行 1510: [14869.401073] cnss: PM stay awake, state: 0x2190, count: 1
行 1511: [14869.401080] cnss_pm_stay_awake: NAP-TODO
行 1512: [14869.401154] cnss: cnss_driver_event_work
行 1513: [14869.401166] cnss: Processing driver event: UNREGISTER_DRIVER-sync(8), state: 0x2190
行 1514: [14869.401175] cnss: Skip driver remove
行 1515: [14869.401204] cnss: wlan en pin is not supported
行 1516: [14869.401230] cnss: Completed event: UNREGISTER_DRIVER(8), state: 0x2190, ret: 0/0
行 1517: [14869.401238] cnss: PM relax, state: 0x2190, count: 0
行 1518: [14869.401244] cnss_pm_relax: NAP-TODO
行 1557: [14886.684205] cnss: Posting event: REGISTER_DRIVER(7)-sync, state: 0x2190
行 1558: [14886.684227] cnss: PM stay awake, state: 0x2190, count: 1
行 1559: [14886.684233] cnss_pm_stay_awake: NAP-TODO
行 1560: [14886.684303] cnss: cnss_driver_event_work
行 1561: [14886.684316] cnss: Processing driver event: REGISTER_DRIVER-sync(7), state: 0x2190
行 1562: [14886.684324] cnss: Setting MHI state: DEINIT(1)
行 1564: [14886.685620] cnss: wlan en pin is not supported
行 1565: [14886.686004] cnss: lnkctl 0x10120040
行 1566: [14886.686025] cnss: QMI timeout is 10000 ms
行 1567: [14886.686032] cnss: Setting MHI state: INIT(0)
行 1572: [14886.765528] cnss: Setting MHI state: POWER_ON(5)
行 1646: [14919.429191] cnss: Failed to set MHI state: POWER_ON(5)
行 1647: [14919.429202] cnss: Failed to start MHI, err = -5
行 1648: [14919.429260] cnss: Completed event: REGISTER_DRIVER(7), state: 0x2190, ret: 0/0
行 1649: [14919.429272] cnss: PM relax, state: 0x2190, count: 0
行 1650: [14919.429279] cnss_pm_relax: NAP-TODO
行 1669: [14924.549152] cnss: FW sram dump start /var/crash/2017-08-05-21-08-55-q6-sram.bin …
行 1670: [14924.549205] cnss: FW sram dump create file /var/crash/2017-08-05-21-08-55-q6-sram.bin failed
行 1671: [14924.549222] cnss: FW sram dump end, status -13
行 1675: [14924.549277] cnss: Timeout waiting for FW ready indication
行 1676: [14924.549288] cnss: Posting event: RECOVERY(9), state: 0x2190
行 1677: [14924.549296] cnss: PM stay awake, state: 0x2190, count: 1
行 1678: [14924.549302] cnss_pm_stay_awake: NAP-TODO
行 1679: [14924.549322] cnss: PM relax, state: 0x2190, count: 0
行 1680: [14924.549329] cnss_pm_relax: NAP-TODO
行 1681: [14924.549396] cnss: cnss_driver_event_work
行 1682: [14924.549405] cnss: PM stay awake, state: 0x2190, count: 1
行 1683: [14924.549414] cnss_pm_stay_awake: NAP-TODO
行 1684: [14924.549421] cnss: Processing driver event: RECOVERY(9), state: 0x2190
行 1685: [14924.549430] cnss: Driver recovery is triggered with reason: TIMEOUT(3)
行 1686: [14924.549435] cnss: Recovery is already in progress!
行 1687: [14924.549444] cnss: PM relax, state: 0x2190, count: 0
行 1688: [14924.549449] cnss_pm_relax: NAP-TODO
根据您提供的日志，FC64EAAMD 模块加载驱动时反复出现固件超时（Timeout waiting for FW ready）和 MHI 启动失败（Failed to set MHI state: POWER_ON，err = -5），结合 FW SRAM 转存文件创建失败（status -13），通常指向硬件连接、供电或固件环境配置异常。由于当前社区与公开知识库中暂未查询到该模块此类报错的专项解决方案，建议优先排查供电稳定性、接口连通性和固件文件是否正确放置。若问题仍未解决，请等待技术工程师为您进一步分析。
本回答仅供参考。若问题已解决，可标记为 
解决方案 ；若仍有疑问，请等待官方技术人员回复，最终请以专业解答为准。