Hardware & Firmware
- Board: nRF9151-DK (DKA), two separate units, both sourced from Farnell/Mouser
- DK Hardware Revision: 1.4.0
- DK PCB version: v0.2.0 (from Board Configurator log)
- Board Controller FW: 1.2.1
- Modem firmware:
mfw_nrf91x1_2.0.4 - TF-M:
v2.1.1-ncs4 AT%HWVERSION:nRF9151 LACA A1A- nRF Connect for Desktop: latest available at time of testing
- Application tested: stock AT Client sample (
nrf/samples/nrf9x/at_client)
Problem Description
Both nRF9151-DK boards are completely unable to detect or communicate with any SIM card. The symptom is identical on both boards. Two different nano-SIM cards were tested. Previous nRF9151-DK boards sourced from a different supplier worked without issue. The modem AT interface itself is healthy — AT+CGMR, AT%HWVERSION, AT+CFUN, and IMEI retrieval (confirmed via nRF Quick Start) all function correctly. Only SIM-related commands fail.
Board Configurator State
- SIM Option: SIM Card selected (not eSIM)
Write configapplied, board power cycledsim-selectpin (pin 14): ON- Board Controller FW: 1.2.1
Full AT Command History — Session 1 (initial diagnostics)
Full AT Command History — Session 2 (following Nordic AI assistant advice)
AT+CFUN?
Key Diagnostic Findings
AT+CIMIreturns plainERRORin bothCFUN=0andCFUN=1— not+CME ERROR: 10(no SIM) or+CME ERROR: 13(SIM failure). This pattern persists across two boards and two different SIM cards.AT%UICC?returnsERROR— the SIM interface software-switching command is not functioning or not applicable on this hardware variant.AT%XFACTORYRESET=0did not resolve the issue — modem NVM configuration is not the cause.AT%CSUS=0explicitly selects the external SIM interface. Even after applying this inCFUN=0and then switching toCFUN=1,AT+CIMIstill returnsERROR.%XSIM: 0,9— after enabling SIM state notifications withAT%XSIM=1and enteringCFUN=1, the modem unsolicited response reports SIM state 0 (not ready) with cause code 9. This confirms the modem is actively attempting to initialize the SIM interface but failing at the hardware communication level.AT+CRSM=176,28589,0,0,10returnsERROR— direct SIM filesystem access is impossible.- nRF Quick Start Verify passes — Manufacturer, Hardware version, and IMEI are all read correctly, confirming the modem itself is functional.
Custom Application Boot Output (for reference)
What Has Been Ruled Out
- Faulty SIM card — two different SIM cards tested on both boards, all fail identically
- Application firmware interference — AT Client sample used in clean state
- Modem NVM configuration —
AT%XFACTORYRESET=0performed, no change - Incorrect SIM interface selection —
AT%CSUS=0explicitly applied, no change - Modem AT interface fault — standard modem queries (
AT+CGMR,AT%HWVERSION, IMEI) all respond correctly - Board Configurator not applied — Write config applied, board power cycled
Questions
- What does
%XSIM: 0,9specifically indicate? What is cause code 9 in the context of%XSIMonmfw_nrf91x1_2.0.4? - What does the
LACAvariant code inAT%HWVERSION: nRF9151 LACA A1Aindicate regarding the SIM interface? Does this variant have a functioning external nano-SIM interface, or does it differ from previously available variants? - Why does
AT%UICC?return plainERRORonmfw_nrf91x1_2.0.4with this hardware variant? IsAT%UICCunsupported onnRF9151 LACA A1A? - Is Board Controller FW 1.2.1 on DK Hardware Revision 1.4.0 (DK v0.2.0) fully compatible with SIM mux switching via the Board Configurator? Could an outdated Board Controller FW cause the
sim-selectsignal to not switch correctly despite Write config being applied? - Is there a known issue with nRF9151-DK boards at Hardware Revision 1.4.0 or DK v0.2.0 related to SIM card detection?
- Both affected boards share the same supplier batch (Farnell). Is there a known batch or revision difference compared to boards from other distributors that would affect SIM functionality?