<?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>BMD-360 EVK debugging issue</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/89503/bmd-360-evk-debugging-issue</link><description>Hello, 
 I&amp;#39;m starting development with nordic arm processors. Therefore we purchased the BMD-360 EVK. This board features the NRF52811 processor and has the same pins as the PCA10040. I&amp;#39;m currently trying to setup a firmware project and faced some issues</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 30 Jun 2022 13:16:50 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/89503/bmd-360-evk-debugging-issue" /><item><title>RE: BMD-360 EVK debugging issue</title><link>https://devzone.nordicsemi.com/thread/374920?ContentTypeID=1</link><pubDate>Thu, 30 Jun 2022 13:16:50 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c2b62353-1bfd-4071-add9-9b7fa989d232</guid><dc:creator>rsf</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;thank you for the answer. changing the adresses solved the issue.&lt;/p&gt;
&lt;p&gt;best,&lt;br /&gt;martin&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BMD-360 EVK debugging issue</title><link>https://devzone.nordicsemi.com/thread/374908?ContentTypeID=1</link><pubDate>Thu, 30 Jun 2022 12:31:52 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1e4513eb-64a6-497a-b229-9349afcefe11</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Please see &lt;a href="https://infocenter.nordicsemi.com/topic/sdk_nrf5_v17.1.0/nrf52811_user_guide.html"&gt;Developing for nRF52811&lt;/a&gt;&lt;span&gt;, particularly&amp;nbsp;the section&amp;nbsp;&lt;em&gt;Transferring the project to nRF52811 hardware&lt;/em&gt;. This is unfortunately&amp;nbsp;not 100% complete, but contains the most important points.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Looking at the configuration changes you have described I notice the following:&lt;/span&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;span&gt;The changes you have described done to&amp;nbsp;flash_placement.xml does not make sense to me, and should&amp;nbsp;be reverted. If the project does not compile without it, we need to look at the build error and see if we can make sense of it.&lt;/span&gt;&lt;span&gt;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;The linker settings does not reflect the flash and RAM size. That most likely does not matter, but it depends a bit on where the linker places things. So you should adjust that, and ensure that the start address + size of both ROM and RAM is within the physically available memory (192 kB / 24 kb).&lt;/span&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;span&gt;&lt;strong&gt;The main issue though, seems to be this&lt;/strong&gt;: You are using an application that does not depend on the SoftDevice, so it should start at address 0. But your FLASH_START is 0x26000, which would only be correct if you had a SoftDevice with that size first in the flash. This does not seem to be the case (at least you do not use it), and if so, the memory at address 0 is uninitialized&amp;nbsp;and the CPU will not have any code to execute. So, you need to sett FLASH_START in the linker settings to 0.&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>