<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>nRF91 AT%XICCID Command Caching &amp;amp; Parsing</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/122683/nrf91-at-xiccid-command-caching-parsing</link><description>The custom AT command &amp;quot;AT%XICCID&amp;quot; was added in modem firmware v1.1.3 for the nRF9160 and was available from the first release for the nRF91x1. 
 This command provides a processed (digits correctly ordered) and cached copy of the SIM&amp;#39;s ICCID making it</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 09 Jul 2025 09:44:06 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/122683/nrf91-at-xiccid-command-caching-parsing" /><item><title>RE: nRF91 AT%XICCID Command Caching &amp; Parsing</title><link>https://devzone.nordicsemi.com/thread/541907?ContentTypeID=1</link><pubDate>Wed, 09 Jul 2025 09:44:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:987f5c7b-f5eb-4407-946e-89048581dcfa</guid><dc:creator>dejans</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
[quote user=""]In my testing when I switched between a virtual&amp;nbsp;UICC (AT%CSUS=2) to the physical SIM slot 1 (AT%CSUS=0),&amp;nbsp;the reported ICCID (using %XICCID) was not updated until I powered the physical SIM again by entering a CFUN=1 or similar state. Perhaps the cached XICCID value should be invalidated, or updated, when a %CSUS operation switches between UICCs.[/quote]
&lt;p&gt;AT does not have SIM slot related control. It just assumes that data comes from correct SIM/cache. &lt;br /&gt;This is what documentation states about &lt;a href="https://docs.nordicsemi.com/bundle/ref_at_commands_nrf91x1/page/REF/at_commands/access_uicc/csus.html"&gt;%CSUS&lt;/a&gt;:&lt;br /&gt;&lt;br /&gt;&lt;em&gt;All &lt;a title="A card used in UE containing data for subscriber identification." href="https://docs.nordicsemi.com/bundle/ref_at_commands_nrf91x1/page/dita_common/glossary/glossary.html#usim"&gt;&lt;dfn&gt;Universal Subscriber Identity Module (USIM)&lt;/dfn&gt;&lt;/a&gt; and UICC activity is directed to the selected slot the next time the modem or UICC is activated. The slot covers also Soft SIM solutions, such as virtual iUICC, in addition to physical UICC slot.&lt;/em&gt;&lt;br /&gt;&lt;br /&gt;&lt;span&gt;After CSUS change, XICCID returns the initial SIM card&amp;#39;s data until new SIM is activated. Cache value is expected to be updated when card is activated. We will have further internal discussion related to possible XICCID value invalidation or update.&lt;br /&gt;&lt;br /&gt;Due to vacations, delayed replies should be expected. I expect to get back to you at the end of July or at the beginning of August. Thank you for your patience and understanding.&lt;br /&gt;&lt;br /&gt;Best regards,&lt;br /&gt;Dejan&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF91 AT%XICCID Command Caching &amp; Parsing</title><link>https://devzone.nordicsemi.com/thread/541685?ContentTypeID=1</link><pubDate>Mon, 07 Jul 2025 18:14:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6f75374b-050f-48d4-8e41-033ab6cb8eb8</guid><dc:creator>dejans</dc:creator><description>&lt;p&gt;Hi,&lt;br /&gt;&lt;br /&gt;Thank you for your feedback, reporting of possible issue and additional information. We will take your observations internally into further consideration and look into this possible issue.&lt;br /&gt;I hope to get back to you by the end of this week, but please note that replies might get delayed due to start of vacation period.&lt;br /&gt;&lt;br /&gt;Best regards,&lt;br /&gt;Dejan&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF91 AT%XICCID Command Caching &amp; Parsing</title><link>https://devzone.nordicsemi.com/thread/541669?ContentTypeID=1</link><pubDate>Mon, 07 Jul 2025 15:51:18 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a74e419d-689a-47a6-bd17-e5513b26ffad</guid><dc:creator>GNotman</dc:creator><description>&lt;p&gt;Hi Dejan,&lt;/p&gt;
&lt;p&gt;This was ticket was more to provide some feedback and report a possible issue with the modem firmware, as such I&amp;#39;m not specifically looking for a solution. Please let me know if there is a preferred avenue for provide similar feedback.&lt;/p&gt;
&lt;p&gt;With regards to which versions these observations apply to:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The &amp;#39;at_parser&amp;#39; library, this behaviour was seen in SDK v2.8.0 but it appears to be the same in the latest.&lt;/li&gt;
&lt;li&gt;The format of the %XICCID output is as defined in the AT Command manual.&lt;/li&gt;
&lt;li&gt;The behaviour of %XICCID after using %CSUS was observed in MFW v2.0.2.&lt;/li&gt;
&lt;/ul&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF91 AT%XICCID Command Caching &amp; Parsing</title><link>https://devzone.nordicsemi.com/thread/541491?ContentTypeID=1</link><pubDate>Fri, 04 Jul 2025 14:23:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2827a840-bc5b-42ce-b77d-79af4613569d</guid><dc:creator>dejans</dc:creator><description>&lt;p&gt;Hi,&lt;br /&gt;&lt;br /&gt;Which NCS and modem firmware versions do you use?&lt;br /&gt;&lt;br /&gt;Best regards,&lt;br /&gt;Dejan&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>