<?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>How to debug when program flow goes to 0xFFFFFFFE?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/23917/how-to-debug-when-program-flow-goes-to-0xfffffffe</link><description>Hi, when doing wired uart-BLE combination and increasing the traffic in the uart comms and BLE comms, at some unpredictable stage, the program flow goes to 0xFFFFFFFE. Any thoughts as how to debug this? I do APP_ERROR_CHECK every time and it is fine.</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Sun, 30 Jul 2017 02:31:30 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/23917/how-to-debug-when-program-flow-goes-to-0xfffffffe" /><item><title>RE: How to debug when program flow goes to 0xFFFFFFFE?</title><link>https://devzone.nordicsemi.com/thread/94130?ContentTypeID=1</link><pubDate>Sun, 30 Jul 2017 02:31:30 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:44504277-d9e2-40d7-822b-bf5715aa6c38</guid><dc:creator>RK</dc:creator><description>&lt;p&gt;Good chance you blew the stack. Take a look at the stack pointer and the last stuff on the stack after you end up there, quite likely it&amp;#39;s run into the heap or the program data and a return has dumped you somewhere invalid. Also look at the registers, are you in hardfault or memfault or some other error?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to debug when program flow goes to 0xFFFFFFFE?</title><link>https://devzone.nordicsemi.com/thread/94131?ContentTypeID=1</link><pubDate>Sun, 30 Jul 2017 00:46:36 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0a0c7a18-e05d-4d70-b069-4f5f8a3166a4</guid><dc:creator>Nguyen Hoan Hoang</dc:creator><description>&lt;p&gt;Looks like bad pointer or lockup some where.  Traffic increase means using more buffers and you ran out of buffers. So you likely to lockup and softdevice doesn&amp;#39;t like it and goes to hardfault.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>