<?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>nRF52840 crashes after porting to SES from Makefile project (gcc).</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/53535/nrf52840-crashes-after-porting-to-ses-from-makefile-project-gcc</link><description>I have recently ported our working project to SES. The project uses S140 with nordik SDK 15.20 on nRF52840 custom board. the project also makes use of freeRTOS. It&amp;#39;s important to note that using the makefile project everything works smoothly. including</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 06 Nov 2019 12:04:49 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/53535/nrf52840-crashes-after-porting-to-ses-from-makefile-project-gcc" /><item><title>RE: nRF52840 crashes after porting to SES from Makefile project (gcc).</title><link>https://devzone.nordicsemi.com/thread/218805?ContentTypeID=1</link><pubDate>Wed, 06 Nov 2019 12:04:49 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4775ab1c-856a-4051-9f63-ded54530afc7</guid><dc:creator>Amanda Hsieh</dc:creator><description>&lt;p&gt;Hi Eyal,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;It seems to be the hardfault is caused by the application changes and is not related to our libraries or solutions.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;I would suggest you&amp;nbsp;&lt;span&gt;find the instruction address that caused the hardfault as described in this &lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/27014/how-can-i-distinguish-the-reason-for-hardfault"&gt;post&lt;/a&gt;. You&amp;nbsp;&lt;/span&gt;need to look into the RAM memory pointed by [SP + 0x18] to get the instruction address that caused the hardfault. That would give you better understanding on the context of the hardfault.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;-Amanda H.&amp;nbsp;&lt;/p&gt;
&lt;div&gt;
&lt;div&gt;
&lt;div&gt;
&lt;div&gt;&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52840 crashes after porting to SES from Makefile project (gcc).</title><link>https://devzone.nordicsemi.com/thread/218077?ContentTypeID=1</link><pubDate>Sun, 03 Nov 2019 10:11:42 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:774f6b2c-5895-4393-b9ff-ee3f02f64dc6</guid><dc:creator>Eyal</dc:creator><description>&lt;p&gt;no, after debugging i can see it&amp;#39;s not the issue.&lt;br /&gt;However i can also see tha LR is not 0 it might be zero in the final handler, but if you stop to debug it you can see in the bootloader (SD) when the exception occurs the LR is 0xfffffff1.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52840 crashes after porting to SES from Makefile project (gcc).</title><link>https://devzone.nordicsemi.com/thread/217298?ContentTypeID=1</link><pubDate>Tue, 29 Oct 2019 11:38:26 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a05aac82-9306-43f3-819e-fffab1664071</guid><dc:creator>Eyal</dc:creator><description>&lt;p&gt;i need to debug it better. basically after i did this i&amp;#39;m still getting hardfaults however when i check it using JLinkExe i do see a proper LR value, i need to see the value of the LR while in the exception handler and then i&amp;#39;ll know if i&amp;#39;ve moved on to the next issue.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52840 crashes after porting to SES from Makefile project (gcc).</title><link>https://devzone.nordicsemi.com/thread/217285?ContentTypeID=1</link><pubDate>Tue, 29 Oct 2019 10:37:35 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4d85a66c-99bc-4a9c-9322-abf2ccc18864</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;The issue with SES and FreeRTOS in SDK15.2 is something that strikes my memory.&lt;/p&gt;
&lt;p&gt;Can you please remove the red #if 0 and #endif combo as shown in the figure below in&amp;nbsp;&amp;nbsp;&lt;/p&gt;
&lt;div&gt;nRF5_SDK_15.2.0_9412b96\external\freertos\portable\CMSIS\nrf52\port_cmsis_systick.c&lt;/div&gt;
&lt;p&gt;&lt;img alt=" " src="https://devzone.nordicsemi.com/resized-image/__size/465x80/__key/communityserver-discussions-components-files/4/pastedimage1572345392790v1.png" /&gt;&lt;/p&gt;
&lt;p&gt;I think this caused problems before. Please test it and update us on the results.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52840 crashes after porting to SES from Makefile project (gcc).</title><link>https://devzone.nordicsemi.com/thread/217059?ContentTypeID=1</link><pubDate>Mon, 28 Oct 2019 12:15:04 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:00886acb-ec4a-40cc-8f98-77b620ea99be</guid><dc:creator>Eyal</dc:creator><description>&lt;p&gt;segger studio is 4.22&lt;/p&gt;
&lt;p&gt;arm gcc we are using 6-1017-q2 but also tried with 7 and 8. all works ok.&lt;br /&gt;i&amp;#39;m not saying hard faults don&amp;#39;t happen on arm gcc version i&amp;#39;m saying THAT hard fault doesn&amp;#39;t seem to happen.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52840 crashes after porting to SES from Makefile project (gcc).</title><link>https://devzone.nordicsemi.com/thread/217057?ContentTypeID=1</link><pubDate>Mon, 28 Oct 2019 12:10:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d6e988c7-1b0e-4b98-a11c-586b9d524365</guid><dc:creator>Amanda Hsieh</dc:creator><description>&lt;p&gt;Hi Eyal,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
[quote user="Eyal Gal"]Again, this code works ok if i use arm gcc, the issue mainly occurs in segger studio.[/quote]
&lt;p&gt;&amp;nbsp;Do you mean only the image compiled by the segger studio has this issue?&lt;/p&gt;
&lt;p&gt;If so, what is the version of the Segger studio you are using? What is the version of the arm gcc?&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;-Amanda H.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52840 crashes after porting to SES from Makefile project (gcc).</title><link>https://devzone.nordicsemi.com/thread/216958?ContentTypeID=1</link><pubDate>Sun, 27 Oct 2019 09:56:24 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ad71ba4b-993f-48e1-a6b1-8319ea881dfb</guid><dc:creator>Eyal</dc:creator><description>&lt;p&gt;nop, it&amp;#39;s not it apparently, followed the article and debugged like they suggested and it seems like the memory regions are defined ok.&lt;br /&gt;Again, this code works ok if i use arm gcc, the issue mainly occurs in segger studio.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52840 crashes after porting to SES from Makefile project (gcc).</title><link>https://devzone.nordicsemi.com/thread/216627?ContentTypeID=1</link><pubDate>Thu, 24 Oct 2019 12:46:04 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:29e4d143-cc09-46ea-9718-8cb8d2cabe4c</guid><dc:creator>Amanda Hsieh</dc:creator><description>&lt;p&gt;Hi Eyal,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;I got the suggestion from my colleague that&lt;/p&gt;
&lt;div&gt;The LR showing address 0x0 seems to have occurred from a bad POP instruction,&amp;nbsp;so it is mostly a stack corruption. Please check the memory (IROM/IRAM) settings correctly with this &lt;a href="https://devzone.nordicsemi.com/nordic/short-range-guides/b/getting-started/posts/adjustment-of-ram-and-flash-memory"&gt;tutorial&lt;/a&gt;.&amp;nbsp;&lt;/div&gt;
&lt;div&gt;&lt;/div&gt;
&lt;div&gt;-Amanda H.&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52840 crashes after porting to SES from Makefile project (gcc).</title><link>https://devzone.nordicsemi.com/thread/216520?ContentTypeID=1</link><pubDate>Thu, 24 Oct 2019 08:35:04 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6b474801-6523-493f-9f3e-5b268309f4e6</guid><dc:creator>Eyal</dc:creator><description>&lt;p&gt;Thanks Amanda, indeed it&amp;#39;s similar and explains the origin of the 0x978 address handler, as i thought it seems to be MBR softdevice and we have the same softdevice (S140 6.1).&lt;br /&gt;However in the case you show they used NRF_Delay while i&amp;#39;m using vTaskDelay.&lt;br /&gt;Further investiagation of the code showed me the clash happen when the code ran a timer that started nordic&amp;#39;s RTC (delayed for 2 seconds by a freeRTOS timer, my CTO claims that otherwise freertos will freeze at times).&lt;br /&gt;We use RTC 2 after RTC is initialized the hardfault occurs, i&amp;#39;m not sure but i&amp;#39;m betting on low priority interrupt somehow gets called from a high priority one, but not sure where and how to fix it.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52840 crashes after porting to SES from Makefile project (gcc).</title><link>https://devzone.nordicsemi.com/thread/216497?ContentTypeID=1</link><pubDate>Thu, 24 Oct 2019 06:55:10 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e74e2ece-ce09-430a-91fb-bcc67e2552d5</guid><dc:creator>Amanda Hsieh</dc:creator><description>&lt;p&gt;Hi Eyal,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;It looks similar to this &lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/50769/bug-unable-to-fix-as-going-to-unknown-function-0x00000978"&gt;case&lt;/a&gt;. Could you try to modify the delay?&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;-Amanda H.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52840 crashes after porting to SES from Makefile project (gcc).</title><link>https://devzone.nordicsemi.com/thread/216217?ContentTypeID=1</link><pubDate>Tue, 22 Oct 2019 15:15:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:659c8d29-9b7f-4348-892e-1d1b9b3cba93</guid><dc:creator>Eyal</dc:creator><description>&lt;p&gt;Update:&lt;br /&gt;I run besides the log task (freeRTOS task) a task i created, in that task i call vTaskDelay(). apprently for some reason calling VtaskDelay inside my task causes a hardfault. now, any hints ?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>