Why can't I get the ICCID number from 9160's modem on the ncs1.9.0 sdk?

[duxinglang]

After upgrading the SDK from 1.2.0 to 1.9.0, I found a problem: the ICCID numbers that could be read are now unreadable! I still use the AT instruction "AT% XICCID" to read, and it returns an error prompt. Why? The IMEI number and IMSI number can still be read.

my modem fw is V1.3.1,and this is my function:

#define CMD_GET_IMEI	"AT+CGSN"
#define CMD_GET_IMSI	"AT+CIMI"
#define CMD_GET_ICCID	"AT%XICCID"

void func(void)
{
    ...
    
	if(nrf_modem_at_cmd(tmpbuf, sizeof(tmpbuf), CMD_GET_IMEI) == 0)
	{
	#ifdef NB_DEBUG
		LOGD("imei:%s", tmpbuf);
	#endif
		strncpy(g_imei, tmpbuf, IMEI_MAX_LEN);
	}

	if(nrf_modem_at_cmd(tmpbuf, sizeof(tmpbuf), CMD_GET_IMSI) == 0)
	{
	#ifdef NB_DEBUG
		LOGD("imsi:%s", tmpbuf);
	#endif
		strncpy(g_imsi, tmpbuf, IMSI_MAX_LEN);
	}

	if(nrf_modem_at_cmd(tmpbuf, sizeof(tmpbuf), CMD_GET_ICCID) == 0)
	{
	#ifdef NB_DEBUG
		LOGD("iccid:%s", &tmpbuf[9]);
	#endif
		strncpy(g_iccid, &tmpbuf[9], ICCID_MAX_LEN);
	}
	
	...
	
}

[helsing]

Hi,

Which modem firmware version are you using?

And which nRF9160 SiP revision are you using? Does it say 'B0' (revision 1) or 'B1' (revision 2) on the SiP?

Would you be able to share any logs from when this happens?

[helsing]

Hi again,

my modem fw is V1.3.1

Sorry, I now see that you already stated the MFW version.

Would you be able to share a code snippet that reproduces this issue?

Any logs are still of interest.

[duxinglang]

Hi, thank you. I have found a new way to read ICCID numbers, as shown below:

"AT+CRSM=176,12258,0,0,10"

It seems that the instruction: AT% XICCID has no effect on the modem fw in 1.3.1.

[helsing]

nrf_modem_at_cmd(buf, buf_len, fmt, ...) is expecting a text string that can be formatted.

#define CMD_GET_ICCID    "AT%XICCID"

must be changed to

#define CMD_GET_ICCID    "AT%%XICCID"

Please note the double '%'.

We tried MFW 1.3.1 locally, and AT%XICCID seems to work(after having activated with AT+CFUN=1. Before activiating, the modem responds with 'ERROR', however, this is also true for AT+CIMI, like you probably know.

duxinglang said:

"AT+CRSM=176,12258,0,0,10"

This will flip the bytes compared to AT%XICCID, e.g. +CRSM: <>,<>,"214365..." vs. %XICCID: 123456... So if you choose to use CRSM you would have to flip them back in the application.

[duxinglang]

Thank you for your reply. I added an additional% symbol to the instruction as you said. Now I can get the iccid number. It seems that I will change all the instructions that used to contain the '%' symbol into a double '%'.