<?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>Integration Error When Adding BLE Functionality to nRF52840 Custom Board Application</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/106392/integration-error-when-adding-ble-functionality-to-nrf52840-custom-board-application</link><description>Hi, I am currently working with the nRF Connect SDK v2.4.0 to develop applications for custom boards based on the nRF52840 microcontroller. The application involves interfacing with various sensors such as temperature, humidity, etc. The code successfully</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 07 Dec 2023 11:53:04 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/106392/integration-error-when-adding-ble-functionality-to-nrf52840-custom-board-application" /><item><title>RE: Integration Error When Adding BLE Functionality to nRF52840 Custom Board Application</title><link>https://devzone.nordicsemi.com/thread/459345?ContentTypeID=1</link><pubDate>Thu, 07 Dec 2023 11:53:04 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7d5081a5-3c53-4cfc-a5cb-eded9ab63ecb</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;It looks like your device tree selects the legacy UART instance and not the UARTE with DMA support, which is&amp;nbsp;needed for using the asynchronous UART driver. To confirm this, please try building your project for the &amp;#39;nrf52840dk_nrf52840&amp;#39; board and check if the same error occurs. If it doesn&amp;#39;t, you can then compare the &amp;#39;zephyr.dts&amp;#39; file generated in the &amp;#39;build/zephyr&amp;#39; directory with the one generated when building for your board.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Integration Error When Adding BLE Functionality to nRF52840 Custom Board Application</title><link>https://devzone.nordicsemi.com/thread/459276?ContentTypeID=1</link><pubDate>Thu, 07 Dec 2023 07:09:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2d1daa87-1d08-415c-b6bd-863455a34437</guid><dc:creator>Anmol Maske</dc:creator><description>&lt;p&gt;Hello Vidar,&lt;/p&gt;
&lt;p&gt;I have previously utilized these CONFIG options, but the issue persists with the same errors. Additionally, I forgot to mention earlier that I am encountering yellow underlined Kconfig options in my prj.conf, accompanied by the following warning:&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;CONFIG_UART_ASYNC_API was assigned the value y, but got the value n. Missing dependencies: SERIAL_SUPPORT_ASYNC

CONFIG_UART_CONSOLE was assigned the value y, but got the value n. Missing dependencies: SERIAL_HAS_DRIVER&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;Also getting CMakeList and KConfig warnings as follows:&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:240px;max-width:320px;" src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/Screenshot-2023_2D00_12_2D00_07-120022.png" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;When I look into the .config file, there is no option which contain the CONFIG_UART_1_ASYNC with y.&lt;/p&gt;
&lt;p&gt;So is the warning wrong and the async option is activated anyways?&lt;br /&gt;How can I make sure the async option is used?&lt;/p&gt;
&lt;p&gt;Best regards!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Integration Error When Adding BLE Functionality to nRF52840 Custom Board Application</title><link>https://devzone.nordicsemi.com/thread/459204?ContentTypeID=1</link><pubDate>Wed, 06 Dec 2023 14:11:29 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3174c674-4b85-4e5a-a1e0-1167550334da</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;&lt;span style="font-family:inherit;"&gt;Sorry, I overlooked the other errors. Those indicate that you are missing relevant kconfig settings to enable the async UART driver. Please ensure you have the following symbols enabled in your project:&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;CONFIG_UART_ASYNC_API=y&lt;br /&gt;CONFIG_NRFX_UARTE0=y&lt;br /&gt;CONFIG_SERIAL=y&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Integration Error When Adding BLE Functionality to nRF52840 Custom Board Application</title><link>https://devzone.nordicsemi.com/thread/459178?ContentTypeID=1</link><pubDate>Wed, 06 Dec 2023 12:46:17 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f7b08af7-d82c-4bb9-952d-80722895425d</guid><dc:creator>Anmol Maske</dc:creator><description>&lt;p&gt;Hello Vidar,&lt;/p&gt;
&lt;p&gt;Thank you for your prompt response. Unfortunately, I have previously attempted the suggested solution, but the issue persists. The error message I&amp;#39;m encountering is as follows:&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;FAILED: CMakeFiles/app.dir/src/peripherals/ws360_uart.c.obj 
C:\ncs\toolchains\31f4403e35\opt\zephyr-sdk\arm-zephyr-eabi\bin\arm-zephyr-eabi-gcc.exe -DKERNEL -DNRF52840_XXAA -DUSE_PARTITION_MANAGER=0 -D_ANSI_SOURCE -D_FORTIFY_SOURCE=1 -D__LINUX_ERRNO_EXTENSIONS__ -D__PROGRAM_START -D__ZEPHYR__=1 -I../src/peripherals -I../. -IC:/ncs/v2.4.0/nrf/drivers/mpsl/clock_control -IC:/ncs/v2.4.0/zephyr/include -Izephyr/include/generated -IC:/ncs/v2.4.0/zephyr/soc/arm/nordic_nrf/nrf52 -IC:/ncs/v2.4.0/zephyr/lib/libc/newlib/include -IC:/ncs/v2.4.0/zephyr/soc/arm/nordic_nrf/common/. -IC:/ncs/v2.4.0/zephyr/subsys/bluetooth -IC:/ncs/v2.4.0/zephyr/subsys/settings/include -IC:/ncs/v2.4.0/nrf/include -IC:/ncs/v2.4.0/nrf/lib/multithreading_lock/. -IC:/ncs/v2.4.0/nrf/subsys/bluetooth/controller/. -IC:/ncs/v2.4.0/zephyr/drivers/flash -IC:/ncs/v2.4.0/nrf/tests/include -IC:/ncs/v2.4.0/modules/hal/cmsis/CMSIS/Core/Include -IC:/ncs/v2.4.0/modules/hal/nordic/nrfx -IC:/ncs/v2.4.0/modules/hal/nordic/nrfx/drivers/include -IC:/ncs/v2.4.0/modules/hal/nordic/nrfx/mdk -IC:/ncs/v2.4.0/zephyr/modules/hal_nordic/nrfx/. -IC:/ncs/v2.4.0/modules/debug/segger/SEGGER -IC:/ncs/v2.4.0/modules/debug/segger/Config -IC:/ncs/v2.4.0/zephyr/modules/segger/. -IC:/ncs/v2.4.0/modules/crypto/tinycrypt/lib/include -IC:/ncs/v2.4.0/nrfxlib/mpsl/include -IC:/ncs/v2.4.0/nrfxlib/mpsl/include/protocol -IC:/ncs/v2.4.0/nrfxlib/softdevice_controller/include -isystem C:/ncs/v2.4.0/nrfxlib/crypto/nrf_cc310_platform/include -fno-strict-aliasing -Og -imacros C:/Users/ASUS/Downloads/WS360_v2-master/WS360_v2-master/build/zephyr/include/generated/autoconf.h -fno-common -g -gdwarf-4 -fdiagnostics-color=always -mcpu=cortex-m4 -mthumb -mabi=aapcs -mfpu=fpv4-sp-d16 -mfloat-abi=hard --sysroot=C:/ncs/toolchains/31f4403e35/opt/zephyr-sdk/arm-zephyr-eabi/arm-zephyr-eabi -imacros C:/ncs/v2.4.0/zephyr/include/zephyr/toolchain/zephyr_stdint.h -Wall -Wformat -Wformat-security -Wno-format-zero-length -Wno-pointer-sign -Wpointer-arith -Wexpansion-to-defined -Wno-unused-but-set-variable -Werror=implicit-int -fno-pic -fno-pie -fno-asynchronous-unwind-tables -fno-reorder-functions --param=min-pagesize=0 -fno-defer-pop -fmacro-prefix-map=C:/Users/ASUS/Downloads/WS360_v2-master/WS360_v2-master=CMAKE_SOURCE_DIR -fmacro-prefix-map=C:/ncs/v2.4.0/zephyr=ZEPHYR_BASE -fmacro-prefix-map=C:/ncs/v2.4.0=WEST_TOPDIR -ffunction-sections -fdata-sections -specs=nano.specs -std=c99 -MD -MT CMakeFiles/app.dir/src/peripherals/ws360_uart.c.obj -MF CMakeFiles\app.dir\src\peripherals\ws360_uart.c.obj.d -o CMakeFiles/app.dir/src/peripherals/ws360_uart.c.obj -c ../src/peripherals/ws360_uart.c
In file included from C:/ncs/v2.4.0/zephyr/include/zephyr/toolchain/gcc.h:92,
                 from C:/ncs/v2.4.0/zephyr/include/zephyr/toolchain.h:50,
                 from C:/ncs/v2.4.0/zephyr/include/zephyr/sys/time_units.h:10,
                 from C:/ncs/v2.4.0/zephyr/include/zephyr/sys/util.h:582,
                 from C:/ncs/v2.4.0/zephyr/include/zephyr/devicetree.h:21,
                 from C:/ncs/v2.4.0/zephyr/include/zephyr/device.h:12,
                 from ../src/peripherals/uart_async_adapter.h:22,
                 from ../src/peripherals/ws360_uart.c:1:
C:/ncs/v2.4.0/zephyr/include/zephyr/device.h:84:41: error: &amp;#39;__device_dts_ord_85&amp;#39; undeclared here (not in a function); did you mean &amp;#39;__device_dts_ord_45&amp;#39;?
   84 | #define DEVICE_NAME_GET(dev_id) _CONCAT(__device_, dev_id)
      |                                         ^~~~~~~~~
C:/ncs/v2.4.0/zephyr/include/zephyr/toolchain/common.h:132:26: note: in definition of macro &amp;#39;_DO_CONCAT&amp;#39;
  132 | #define _DO_CONCAT(x, y) x ## y
      |                          ^
C:/ncs/v2.4.0/zephyr/include/zephyr/device.h:84:33: note: in expansion of macro &amp;#39;_CONCAT&amp;#39;
   84 | #define DEVICE_NAME_GET(dev_id) _CONCAT(__device_, dev_id)
      |                                 ^~~~~~~
C:/ncs/v2.4.0/zephyr/include/zephyr/device.h:210:37: note: in expansion of macro &amp;#39;DEVICE_NAME_GET&amp;#39;
  210 | #define DEVICE_DT_NAME_GET(node_id) DEVICE_NAME_GET(Z_DEVICE_DT_DEV_ID(node_id))
      |                                     ^~~~~~~~~~~~~~~
C:/ncs/v2.4.0/zephyr/include/zephyr/device.h:227:34: note: in expansion of macro &amp;#39;DEVICE_DT_NAME_GET&amp;#39;
  227 | #define DEVICE_DT_GET(node_id) (&amp;amp;DEVICE_DT_NAME_GET(node_id))
      |                                  ^~~~~~~~~~~~~~~~~~
../src/peripherals/ws360_uart.c:70:36: note: in expansion of macro &amp;#39;DEVICE_DT_GET&amp;#39;
   70 | static const struct device *uart = DEVICE_DT_GET(DT_CHOSEN(nordic_nus_uart));
      |                                    ^~~~~~~~~~~~~
../src/peripherals/ws360_uart.c: In function &amp;#39;uart_test_async_api&amp;#39;:
../src/peripherals/ws360_uart.c:238:20: error: &amp;#39;const struct uart_driver_api&amp;#39; has no member named &amp;#39;callback_set&amp;#39;
  238 |         return (api-&amp;gt;callback_set != NULL);
      |                    ^~
../src/peripherals/ws360_uart.c: In function &amp;#39;start_uart&amp;#39;:
../src/peripherals/ws360_uart.c:449:9: warning: implicit declaration of function &amp;#39;configure_gpio&amp;#39; [-Wimplicit-function-declaration]
  449 |         configure_gpio();
      |         ^~~~~~~~~~~~~~&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;I suspect there may be an issue with the CMakeFiles. Additionally, I would greatly appreciate it if you could suggest the best approach to seamlessly integrate the &amp;#39;peripheral_uart&amp;#39; code with the main application code. Or any other link that may be helpful.&lt;/p&gt;
&lt;p&gt;Thank you for your assistance.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Integration Error When Adding BLE Functionality to nRF52840 Custom Board Application</title><link>https://devzone.nordicsemi.com/thread/459170?ContentTypeID=1</link><pubDate>Wed, 06 Dec 2023 12:25:00 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:08b1b242-afec-4259-b7d4-9541d9cc8f76</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;You need to define the &amp;#39;nordic_nus_uart&amp;#39; property in your devicetree to inform the application which USB/UART interface you intend to use for serial port emulation. The peripheral_uart sample uses UART0 by default:&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;/ {
	chosen {
		nordic,nus-uart = &amp;amp;uart0;
	};
};&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Vidar&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>