<?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>Migrating from SDK14.2.0 to SDK15.0.0, nrfx uart</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/57121/migrating-from-sdk14-2-0-to-sdk15-0-0-nrfx-uart</link><description>Hi, 
 
 I am migrating from SDK14.2 to SDK15.0 and I can compile now, but when runnning the nrfx_uart_init the hardware handshake signal RTS is high from the beginning. 
 Also if I dont use hardware handshake the event handler is not trigged by incoming</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 31 Jan 2020 13:33:00 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/57121/migrating-from-sdk14-2-0-to-sdk15-0-0-nrfx-uart" /><item><title>RE: Migrating from SDK14.2.0 to SDK15.0.0, nrfx uart</title><link>https://devzone.nordicsemi.com/thread/232100?ContentTypeID=1</link><pubDate>Fri, 31 Jan 2020 13:33:00 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:29da0410-5579-4916-b026-7aabc4d4239e</guid><dc:creator>Edvin</dc:creator><description>&lt;p&gt;Have you copied your project file from the old SDK to SDK15? I would suggest that you rather start of with one of the project files from SDK15, and port your main.c file to that, and add the files that you have written yourself.&lt;/p&gt;
&lt;p&gt;The files that it complains it can&amp;#39;t find doesn&amp;#39;t exist in those locations anymore, and they have been renamed.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Please start with a project file from SDK15.0.0. It will save you a lot of time.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Migrating from SDK14.2.0 to SDK15.0.0, nrfx uart</title><link>https://devzone.nordicsemi.com/thread/232075?ContentTypeID=1</link><pubDate>Fri, 31 Jan 2020 12:04:23 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9ed63893-7d11-4cee-ba70-0d9e306eb1a2</guid><dc:creator>Bjarke</dc:creator><description>&lt;p&gt;I can compile.&lt;/p&gt;
&lt;p&gt;The UART is not responding. The event is not fired, and the RTS is constant high.&lt;/p&gt;
&lt;p&gt;Bluetooth is running.&lt;/p&gt;
&lt;p&gt;I get a NRFX_SUCCESS from the app_fifi_uart_init ( should be NRF_SUCCESS, if the glue.h is applied correctly)&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;In the Uart loopback example I dont see the the glue.h file is applied anywhere.&lt;/p&gt;
&lt;p&gt;See my other&amp;nbsp;reply&amp;nbsp;below&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Migrating from SDK14.2.0 to SDK15.0.0, nrfx uart</title><link>https://devzone.nordicsemi.com/thread/232073?ContentTypeID=1</link><pubDate>Fri, 31 Jan 2020 11:59:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cbe66ece-f14b-4cf5-b628-57862b8bb3bf</guid><dc:creator>Edvin</dc:creator><description>[quote user="Bjarkegoth"]It seems that the nrfx_glue changes the NRFX_xxx to NRF_xxx.[/quote]
&lt;p&gt;&amp;nbsp;Yes. In addition there is a file called apply_old_config.h, which you should take a look at.&lt;/p&gt;
&lt;p&gt;Basically, if you have defines in sdk_config.h that has both NRFX_EXAMPLE_DEFINE and EXAMPLE_DEFINE, then the EXAMPLE_DEFINE will overrule the NRFX_EXAMPLE_DEFINE.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Note that this&amp;nbsp;&lt;strong&gt;does not&lt;/strong&gt; mean that you are using the legacy drivers.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I am not sure exactly what difficulties you are experiencing. I agree that it is confusing with NRFX and NRF defines, and it is not ideal. But what is the issue you are encountering? Are you able to compile? Does the app &amp;quot;crash&amp;quot; during runtime? Or is the UART not responding?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Migrating from SDK14.2.0 to SDK15.0.0, nrfx uart</title><link>https://devzone.nordicsemi.com/thread/232072?ContentTypeID=1</link><pubDate>Fri, 31 Jan 2020 11:59:00 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ce9acb91-4993-409f-b64b-ff4e596ff9c6</guid><dc:creator>Bjarke</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;I have started over the migrating process. I had lost track of what configuration enabled that worked and what didn&amp;#39;t.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;error :Makefile:273: Cannot find source file:&amp;nbsp; ../../../SDK15.0.0/components/drivers_nrf/common/nrf_drv_common.c&lt;/p&gt;
&lt;p&gt;Where is the corresponding nrfx_common.c?&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;error: &amp;quot;components/drivers_nrf/hal/nrf_saadc.c&amp;quot; not found:&lt;/p&gt;
&lt;p&gt;is it moved to &amp;quot;modules/nrfx/hal/nrf_saadc.c&amp;quot;?&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;error: &amp;quot;components/libraries/twi&amp;quot; not founc:&lt;/p&gt;
&lt;p&gt;is it moved to &amp;quot;components/libraries/twi_mngr&amp;quot;?&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Error:&amp;quot;components/device&amp;quot; folder not found:&lt;/p&gt;
&lt;p&gt;is this moved to &amp;quot;modules/nrfx/mdk&amp;quot;?&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Error :&amp;quot;components/toolchain/gcc/gcc_startup_nrf52.S&amp;quot; not found:&lt;/p&gt;
&lt;p&gt;is this move to &amp;quot;/modules/nrfx/mdk/gcc_startup_nrf52.S&amp;quot;?&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Error :&amp;quot;components/toolchain/gcc/system_nrf52.c&amp;quot; not found:&lt;/p&gt;
&lt;p&gt;is this move to &amp;quot;/modules/nrfx/mdk/system_nrf52.c&amp;quot;?&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;NRF_SDH_BLE_GAP_DATA_LENGTH is a new macro requirement in nrf_ble_gatt.c?&lt;/p&gt;
&lt;p&gt;Am I right in that the app_uart_fifo.c is only for legacy/integration and not purely nrfx_uart compatible?&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Thanks,&lt;/p&gt;
&lt;p&gt;Bjarke&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Migrating from SDK14.2.0 to SDK15.0.0, nrfx uart</title><link>https://devzone.nordicsemi.com/thread/231947?ContentTypeID=1</link><pubDate>Thu, 30 Jan 2020 15:08:35 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:31b765c1-9d12-44a2-b22d-e4c8414b1887</guid><dc:creator>Bjarke</dc:creator><description>&lt;p&gt;I think the legacy code is messing up the nrfx drivers.&lt;/p&gt;
&lt;p&gt;The UART loopback test example is now working, but it is only sdk_config and inlude files that are different. Back and compare.yawn&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Migrating from SDK14.2.0 to SDK15.0.0, nrfx uart</title><link>https://devzone.nordicsemi.com/thread/231912?ContentTypeID=1</link><pubDate>Thu, 30 Jan 2020 13:51:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9a5a1f1e-a1cc-47fc-baeb-71008aa31e6a</guid><dc:creator>Bjarke</dc:creator><description>&lt;p&gt;By steeping through the code.&lt;/p&gt;
&lt;p&gt;It seems that the nrfx_glue changes the NRFX_xxx to NRF_xxx.&lt;/p&gt;
&lt;p&gt;It&amp;#39;s a mess&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Migrating from SDK14.2.0 to SDK15.0.0, nrfx uart</title><link>https://devzone.nordicsemi.com/thread/231909?ContentTypeID=1</link><pubDate>Thu, 30 Jan 2020 13:44:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:200bb1a4-b3c0-4775-9491-33be53be1350</guid><dc:creator>Edvin</dc:creator><description>&lt;p&gt;NRFX_SUCCESS == NRF_SUCCESS. How did you determine that it returned NRFX_SUCCESS, and not NRF_SUCCESS?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Migrating from SDK14.2.0 to SDK15.0.0, nrfx uart</title><link>https://devzone.nordicsemi.com/thread/231842?ContentTypeID=1</link><pubDate>Thu, 30 Jan 2020 10:41:36 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3698d1f7-ccbd-4825-a7ae-20cde15d8f77</guid><dc:creator>Bjarke</dc:creator><description>&lt;p&gt;I have read out the err_code from the&amp;nbsp;APP_UART_FIFO_INIT, should be NRF_SUCCESS, but it is&amp;nbsp; NRFX_SUCCESS. why?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Migrating from SDK14.2.0 to SDK15.0.0, nrfx uart</title><link>https://devzone.nordicsemi.com/thread/231670?ContentTypeID=1</link><pubDate>Wed, 29 Jan 2020 13:45:29 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6960292f-b205-47a3-904a-70b43ead8a1e</guid><dc:creator>Bjarke</dc:creator><description>&lt;p&gt;I have not copied any library driver from the old SDK, I have 1 c file that holds the UART communication in my program.&lt;/p&gt;
&lt;p&gt;I can see that the examples uses the nrfx driver, but the legacy integration drivers are also included....&lt;/p&gt;
&lt;p&gt;I have also included those, otherwise the app_uart would not work.&lt;/p&gt;
&lt;p&gt;I will try one of the uart examples, and test if it will work at all.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;BR&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Migrating from SDK14.2.0 to SDK15.0.0, nrfx uart</title><link>https://devzone.nordicsemi.com/thread/231653?ContentTypeID=1</link><pubDate>Wed, 29 Jan 2020 12:52:57 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:86a50333-466b-4cdc-831c-4961b9cfa56b</guid><dc:creator>Edvin</dc:creator><description>&lt;p&gt;Have you copied a lot of library files or drivers from your old SDK? I suggest that you start with a project from the new SDK that you are porting to, and replace the main.c file, and add the files that you have written yourself. This way everything should be set up. Or are you just trying to backport the drivers from the later SDK to your current SDK?&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;If you started off with a new SDK, then I just want to make you aware of the file &amp;quot;apply_old_config.h&amp;quot;. I am not convinced that this is the cause of your issues, but it is worth knowing that it exists.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;BR,&lt;/p&gt;
&lt;p&gt;Edvin&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Migrating from SDK14.2.0 to SDK15.0.0, nrfx uart</title><link>https://devzone.nordicsemi.com/thread/231626?ContentTypeID=1</link><pubDate>Wed, 29 Jan 2020 12:04:57 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:24fd0072-9b46-4173-8764-c28f371c42de</guid><dc:creator>Bjarke</dc:creator><description>&lt;p&gt;I am able to compile with app_uart, but the handshake signals are the same...RTS is still high from the beginning....&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Migrating from SDK14.2.0 to SDK15.0.0, nrfx uart</title><link>https://devzone.nordicsemi.com/thread/231614?ContentTypeID=1</link><pubDate>Wed, 29 Jan 2020 11:40:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c7574bd0-4240-4b08-b0a5-081f8f48838d</guid><dc:creator>Bjarke</dc:creator><description>&lt;p&gt;Added APP_UART ENABLE +&amp;nbsp;APP_UART_DRIVER_INSTANCE 0 to config.&lt;/p&gt;
&lt;p&gt;but&amp;nbsp;&lt;/p&gt;
&lt;p&gt;../../../SDK15.0.0/modules/nrfx/drivers/include/nrfx_uart.h:80:35: error: &amp;#39;NRFX_UART0_INST_IDX&amp;#39; undeclared here (not in a function)&lt;/p&gt;
&lt;p&gt;remains&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Migrating from SDK14.2.0 to SDK15.0.0, nrfx uart</title><link>https://devzone.nordicsemi.com/thread/231602?ContentTypeID=1</link><pubDate>Wed, 29 Jan 2020 10:50:55 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:70d390cc-e787-4183-b955-37b0a679975a</guid><dc:creator>Bjarke</dc:creator><description>&lt;p&gt;What am I missing here?&lt;/p&gt;
&lt;p&gt;../../../SDK15.0.0/integration/nrfx/legacy/nrf_drv_uart.h:382:1: error: unknown type name &amp;#39;ret_code_t&amp;#39;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;I have added&amp;nbsp;sdk_error.h to nrfx.h. But the &amp;quot;app_uart_put/get/init&amp;quot; is still not found in the linker even though app_uart_fifo.c is added&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Migrating from SDK14.2.0 to SDK15.0.0, nrfx uart</title><link>https://devzone.nordicsemi.com/thread/231592?ContentTypeID=1</link><pubDate>Wed, 29 Jan 2020 10:12:19 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:91e5a890-efda-45d8-886a-8c84309f0f08</guid><dc:creator>Edvin</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;I am not sure I understand what you mean. app_uart_put() is included in app_uart_fifo.c. Doesn&amp;#39;t your compiler find it? Is APP_UART_ENABLED defined to 1 in sdk_config.h?&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Edvin&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>