<?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 download Project ‘usbd_ble_uart_pca10056_s140’ in nrf52 dongle</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/59101/how-to-download-project-usbd_ble_uart_pca10056_s140-in-nrf52-dongle</link><description>I am converting the the Project ‘usbd_ble_uart_pca10056_s140’ to pca10059, to download it in the nrf52840 dongle. I followed the steps in the nRF52840 Dongle Programming Tutorial and changed the processor and linker attributes. But an error is occurring</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 23 Mar 2020 13:08:24 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/59101/how-to-download-project-usbd_ble_uart_pca10056_s140-in-nrf52-dongle" /><item><title>RE: How to download Project ‘usbd_ble_uart_pca10056_s140’ in nrf52 dongle</title><link>https://devzone.nordicsemi.com/thread/241142?ContentTypeID=1</link><pubDate>Mon, 23 Mar 2020 13:08:24 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2b487f38-2f08-4db5-adfe-a93071c98442</guid><dc:creator>Marjeris Romero</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;For SDK v15.3.0 you need to use Softdevice v6.1.1. You can find it under the folder components/softdevice/s140/hex/s140_nrf52_6.1.1_softdevice.hex inside the SDK folder.&lt;/p&gt;
&lt;p&gt;Click &amp;quot;Add HEX file&amp;quot; in the nRF Programmer app to upload a new Softdevice and then &amp;quot;Write&amp;quot;.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Marjeris&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to download Project ‘usbd_ble_uart_pca10056_s140’ in nrf52 dongle</title><link>https://devzone.nordicsemi.com/thread/240891?ContentTypeID=1</link><pubDate>Fri, 20 Mar 2020 13:38:19 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6160bf60-6050-4a55-b59f-f6a6f413067e</guid><dc:creator>MRK-196</dc:creator><description>&lt;p&gt;Hi, I tried your approach, it builds but I am encountering another problem related to the nrf connect app when programing the dongle.&lt;/p&gt;
&lt;p&gt;The problem is related to the SoftDevices. When writing the new hex file I chose 0XAE (s140_nrf52_6.1.0) for the sdk15.3.0.&amp;nbsp; I also chose 0XA9 (s140_nrf52_6.0.0) and all the rest just to try. But still I did not fix the issue.&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " src="https://devzone.nordicsemi.com/resized-image/__size/320x240/__key/communityserver-discussions-components-files/4/8867.1.png" /&gt; &lt;img alt=" " src="https://devzone.nordicsemi.com/resized-image/__size/320x240/__key/communityserver-discussions-components-files/4/1031.3.PNG" /&gt;&lt;/p&gt;
&lt;p&gt;Is there something I am missing to do ?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to download Project ‘usbd_ble_uart_pca10056_s140’ in nrf52 dongle</title><link>https://devzone.nordicsemi.com/thread/240392?ContentTypeID=1</link><pubDate>Wed, 18 Mar 2020 10:12:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9dff53d2-ae47-4c38-98c2-1cc2179e9c4b</guid><dc:creator>Marjeris Romero</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Sorry for the late reply. Since this example uses SoftDevice the only thing you need to do is to update the Preprocessor Definitions by removing &lt;code&gt;BOARD_PCA10056&lt;/code&gt; and inserting &lt;code&gt;BOARD_PCA10059 &lt;/code&gt;and you should be able to build the example. You don&amp;#39;t need to adjust the linker configuration.&lt;/p&gt;
&lt;p&gt;Did you check if you were able to build the example out of the box? It could be that your working directory is in a too deep level (i.e. long path name). This is a problem related to Windows path limitation, and is a known issue when the names get too long. You can try to move the SDK folder to level that is not that deep.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Marjeris&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>