<?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>Modem crash with 0x4 while using DECT nr+ MAC/DLC APIs</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/128500/modem-crash-with-0x4-while-using-dect-nr-mac-dlc-apis</link><description>Hi everyone, 
 I&amp;#39;m developing a star-topology network using DECT NR+ on nRF9161 DK nodes, running modem firmware mfw-nr+_nrf91x1_2.0.0 (nRF Connect SDK 3.3.0). 
 My issue is a modem crash with error 0x4 on the FT side when it receives a PDU of ~3200 bytes</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 18 Jun 2026 14:49:09 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/128500/modem-crash-with-0x4-while-using-dect-nr-mac-dlc-apis" /><item><title>RE: Modem crash with 0x4 while using DECT nr+ MAC/DLC APIs</title><link>https://devzone.nordicsemi.com/thread/568151?ContentTypeID=1</link><pubDate>Thu, 18 Jun 2026 14:49:09 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:717adc14-ac20-429c-b9c5-b2068dd0df52</guid><dc:creator>0x41</dc:creator><description>&lt;p&gt;Hi,&lt;br /&gt;&lt;br /&gt;Thanks for your answer, but maybe is not the point of what I&amp;#39;m looking for,&amp;nbsp;&lt;em&gt;&amp;nbsp;&lt;span&gt;CONFIG_NRF_MODEM_LIB_SHMEM_CTRL_SIZE&amp;nbsp;&lt;/span&gt;&lt;/em&gt;is&amp;nbsp;not directly user assignable&lt;em&gt;.&lt;br /&gt;&lt;br /&gt;&lt;/em&gt;From .config in build directory it sets to 1832, value found&amp;nbsp;inside&amp;nbsp;&lt;em&gt;&amp;lt;sdk home&amp;gt;/nrfxlib/nrf_modem/Kconfig.&lt;br /&gt;&lt;br /&gt;&lt;/em&gt;In my project I don&amp;#39;t re-define&amp;nbsp;&lt;span&gt;NRF_MODEM_DECT_SHMEM_CTRL_SIZE&lt;/span&gt;&lt;span&gt;.&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;Regards,&lt;br /&gt;Alessandro.&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Modem crash with 0x4 while using DECT nr+ MAC/DLC APIs</title><link>https://devzone.nordicsemi.com/thread/568148?ContentTypeID=1</link><pubDate>Thu, 18 Jun 2026 14:05:51 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2c9eedff-acae-44ee-b052-46e154541cf8</guid><dc:creator>Syed Maysum Abbas Zaidi</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Yes , the error 0x4 is a modem-internal memory management fault, the modem runs out of internal memory during PDU reassembly on the FT side. One thing I would like to mention that the define NRF_MODEM_DECT_PHY_SHMEM_CTRL_SIZE was renamed to NRF_MODEM_DECT_SHMEM_CTRL_SIZE in 3.3.0. If your project still uses the old name, the control region size may get silently ignored so can you please&amp;nbsp;look through all project files and if you find any old name then rename it to NRF_MODEM_DECT_SHMEM_CTRL_SIZE.&lt;/p&gt;
&lt;p&gt;Moreover also ensure&amp;nbsp;CONFIG_NRF_MODEM_LIB_SHMEM_CTRL_SIZE is set to at least 1832.&lt;/p&gt;
&lt;p&gt;Best Regards,&lt;br /&gt;Syed Maysum&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>