<?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>Hard Fault when an array is send over uart every &amp;#39;n&amp;#39; second</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/111668/hard-fault-when-an-array-is-send-over-uart-every-n-second</link><description>Hello, 
 I am trying to send an array which has 2048 bytes via UART. But, when I add a some delay to repeat the the UART transfer, the code gets stuck on the HardFault. I am using nRF52DK for it. 
 This is the code: 
 
 I would greatly appreciate any</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 30 May 2024 11:10:53 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/111668/hard-fault-when-an-array-is-send-over-uart-every-n-second" /><item><title>RE: Hard Fault when an array is send over uart every 'n' second</title><link>https://devzone.nordicsemi.com/thread/486638?ContentTypeID=1</link><pubDate>Thu, 30 May 2024 11:10:53 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:16cb50fa-3d06-4d48-88e2-cbf40bbba822</guid><dc:creator>Surya09</dc:creator><description>&lt;p&gt;Thanks, I understood it. Now, it works.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Hard Fault when an array is send over uart every 'n' second</title><link>https://devzone.nordicsemi.com/thread/486625?ContentTypeID=1</link><pubDate>Thu, 30 May 2024 10:24:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8d789201-89c3-44ad-a1d0-8b9bdff15a5d</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;You are not registering a UART callback in your APP_UART_FIFO_INIT(), which will cause the program to execute a NULL function pointer if a UART event is triggered (e.g., on APP_UART_TX_EMPTY). I expected this to be handled in the driver by either raising an error or not invoking the callback when it is set to NULL, but that does not seem to be the case, unfortunately.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Vidar&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>