<?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>UART not responding</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/99660/uart-not-responding</link><description>Hello, Have tried to port the Adafruit DFU bootloader project ( https://github.com/adafruit/Adafruit_nRF52_Bootloader) to an NRF52811_XXAA on uart for a custom board. All builds well, but uart seem to be dead. I.e. no serial events are detected or handled</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 16 May 2023 14:42:04 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/99660/uart-not-responding" /><item><title>RE: UART not responding</title><link>https://devzone.nordicsemi.com/thread/425939?ContentTypeID=1</link><pubDate>Tue, 16 May 2023 14:42:04 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8953f15c-929c-42be-af2f-4779c0384d3d</guid><dc:creator>AndersG</dc:creator><description>&lt;p&gt;Thanks!&lt;/p&gt;
&lt;p&gt;That did the trick...&lt;/p&gt;
&lt;p&gt;Br, Anders&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: UART not responding</title><link>https://devzone.nordicsemi.com/thread/425932?ContentTypeID=1</link><pubDate>Tue, 16 May 2023 14:17:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4bc26fa6-5799-46e2-a40e-f8526a68ab93</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi Anders,&lt;/p&gt;
&lt;div&gt;
&lt;div&gt;&lt;span&gt;7 is NRF_ERROR_INVALID_PARAM, and the typical reason for getting this returned from&amp;nbsp;sd_softdevice_enable() is an issue with the clock configuration. What is the content of the struct pointed to in the first parameter supplied to&amp;nbsp;sd_softdevice_enable()? The proper set of configurations for using LFRC with calibration is as indicated in &lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/67478/nrf52840-examples-with-lfrc-and-calibration/276416"&gt;this post&lt;/a&gt;.&lt;/span&gt;&lt;/div&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: UART not responding</title><link>https://devzone.nordicsemi.com/thread/425905?ContentTypeID=1</link><pubDate>Tue, 16 May 2023 14:11:24 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:eff8601a-26c3-4626-a698-a39a468d190b</guid><dc:creator>AndersG</dc:creator><description>&lt;p&gt;Thanks Einar!&lt;br /&gt;I continued by trying the the secure&amp;nbsp;pca10056e_uart DFU on the custom board, worked fine with nrfutil, also installed SES 7.20, using gcc, to get a better overview of the code base. (used gcc make before...)&lt;/p&gt;
&lt;p&gt;Then tried some samples with S112(7.2.0) but, can&amp;#39;t get any these samples to work. sd_softdevice_enable returns a parameter error (7).&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Any thoughts of the origin of this error?&lt;/p&gt;
&lt;p&gt;The custom board has an external 32MHz HF-xtal, no LF-xtal connected...&amp;nbsp;&lt;br /&gt;Tested the RTC-sample(rtc_pca10056), and compared setting the CLOCK_CONFIG_LF_SRC to 0 or 2,&lt;br /&gt;the the HF, and I assume the HF clock is bit too fast (1.4%), 123.3 ms with an expected(?) 125.0 ms 4096/32768)&lt;br /&gt;This is far too much and must be trimmed with the loading caps, but I assume the S112 cannot tell that it is &lt;br /&gt;too much off?&lt;/p&gt;
&lt;p&gt;Br, Anders&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: UART not responding</title><link>https://devzone.nordicsemi.com/thread/425346?ContentTypeID=1</link><pubDate>Fri, 12 May 2023 12:53:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8ffe42a4-c595-45e6-943a-9de8c7ed18a8</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi Anders,&lt;/p&gt;
&lt;p&gt;I am not familiar with the&amp;nbsp;Adafruit DFU bootloader (though I see it is based on our bootloader), but generally you should need very few changes to port a project to nRF52811. One potential pitfall could be that if this is partially based on SDK 11, it means that it is based on an SDK released&amp;nbsp;before the nRF52811 was released, to the MDK files will not exist for the nRF52811 (support for that was introduces in nRF5 SDK 15.3.0). And as the example project is for a bigger device, you should make sure that the peripheral instances being used actually exist on the nRF52811 (if you have changed the project to build for nRF52811 you would get build errors if not, though).&lt;/p&gt;
[quote user=""]Then also found the uart DFU-samples, all of them encrypted, what&amp;#39;s the simplest way disable the encryption?[/quote]
&lt;p&gt;Are you referign to the nRF5 SDK&amp;nbsp;bootloader we provide now? If so, that does not use encryption, but the secure bootloader use signature verification, and unsigned or incorrectly signed images are rejected. It is possible to configure it as an open bootloader without requiering a signature though, which you can see an example of in the &lt;a href="https://infocenter.nordicsemi.com/topic/sdk_nrf5_v17.1.0/ble_sdk_app_open_bootloader.html"&gt;Open Bootloader with DFU&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Einar&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>