<?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>&amp;quot;Undefined Reference&amp;quot; on the linker level</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/39503/undefined-reference-on-the-linker-level</link><description>Hi. I am a beginner with nrf52832. Trying to get Bluetooth and UART and a I2C peripheral working at the same time. I had a working version of the I2C peripheral and UART working together and tried to merge Bluetooth in, referencing the ble_app_uart example</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 06 Dec 2018 03:45:35 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/39503/undefined-reference-on-the-linker-level" /><item><title>RE: "Undefined Reference" on the linker level</title><link>https://devzone.nordicsemi.com/thread/160492?ContentTypeID=1</link><pubDate>Thu, 06 Dec 2018 03:45:35 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:15a3fa2e-eca4-4658-927e-81c1bcd044a2</guid><dc:creator>Connie Violet</dc:creator><description>&lt;p&gt;OK. Turned out that when I combine our program with the example I had our version of sdk_config.h in the project directory but also the example&amp;#39;s sdk_config.h in the config folder which cause the problem. It was solved by removing the config holder and also the related line in the Makefile.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: "Undefined Reference" on the linker level</title><link>https://devzone.nordicsemi.com/thread/153676?ContentTypeID=1</link><pubDate>Fri, 19 Oct 2018 14:37:04 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cbc81d93-e9ce-419c-8205-9f7868099077</guid><dc:creator>J&amp;#248;rgen Holmefjord</dc:creator><description>&lt;p&gt;I have reported both your concerns to&amp;nbsp;our SDK team. We will see if we can get something better for future releases.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: "Undefined Reference" on the linker level</title><link>https://devzone.nordicsemi.com/thread/153575?ContentTypeID=1</link><pubDate>Fri, 19 Oct 2018 07:59:50 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f1a1f509-8e63-42b9-b6b6-3c1bb5b94f8c</guid><dc:creator>awneil</dc:creator><description>&lt;p&gt;Absolutely!&lt;/p&gt;
&lt;p&gt;That&amp;#39;s exactly my point!&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;The module documentation does not clearly describe what settings need to be made.&lt;/li&gt;
&lt;li&gt;&lt;span&gt;The module documentation does not clearly state what&amp;nbsp;files need to be added to the project.&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;Dependencies are poorly documented.&lt;/span&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Another one this morning:&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/39627/error-l6218e"&gt;https://devzone.nordicsemi.com/f/nordic-q-a/39627/error-l6218e&lt;/a&gt;&amp;nbsp;- relates to app_uart &amp;amp; nrfx_twim&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;So let&amp;#39;s look at the UART documentation:&lt;/p&gt;
&lt;p&gt;&lt;a href="https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk5.v15.2.0/group__app__uart.html?cp=4_0_0_6_11_57"&gt;https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk5.v15.2.0/group__app__uart.html?cp=4_0_0_6_11_57&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Under &amp;#39;&lt;a href="https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk5.v15.2.0/group__app__uart__config.html" rel="noopener noreferrer" target="_blank"&gt;UART driver configuration&lt;/a&gt;&amp;#39;&lt;/p&gt;
&lt;p&gt;Again, we have&amp;nbsp;APP_UART_ENABLED &amp;quot;Set to 1 to enable&amp;quot;, but no clear definition of &lt;em&gt;&lt;strong&gt;where&lt;/strong&gt;&lt;/em&gt; to do that - just the cryptic &amp;quot;&lt;span&gt;This is an NRF_CONFIG macro&amp;quot;.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;And I do not see anywhere that it tells you that files need to be added to the project - let alone what those files are!&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;This appears to be a classic case of documentation written by coder!&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;a class="internal-link view-user-profile" href="https://devzone.nordicsemi.com/members/joh2"&gt;J&amp;oslash;rgen Holmefjord&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/a&gt;&amp;nbsp;- perhaps we could discuss doing an external review? PM me ...&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: "Undefined Reference" on the linker level</title><link>https://devzone.nordicsemi.com/thread/153540?ContentTypeID=1</link><pubDate>Thu, 18 Oct 2018 23:53:03 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:572bef1f-5b36-4fec-ad4b-75879ad92ce4</guid><dc:creator>Ladasky</dc:creator><description>&lt;p&gt;&lt;a href="http://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.sdk5.v12.3.0%2Fsdk_config.html&amp;amp;cp=4_0_7_1_6"&gt;http://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.sdk5.v12.3.0%2Fsdk_config.html&amp;amp;cp=4_0_7_1_6&lt;/a&gt;&amp;nbsp;states:&lt;/p&gt;
&lt;p&gt;&amp;quot;&lt;span&gt;All examples contain a &lt;span style="text-decoration:underline;"&gt;full&lt;/span&gt; configuration header file in which only the used modules are enabled.&amp;quot; (emphasis mine)&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;With all due respect, this statement is untrue.&amp;nbsp; &lt;/span&gt;&lt;/p&gt;
&lt;p&gt;I just wrote a short program which simply counts the lines in each sdk_config.h file in SDK 12.3 which is&amp;nbsp;designated for the PCA10040 board (the ones we use).&amp;nbsp; Here is the output.&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span&gt;dtm/direct_test_mode/pca10040/blank/config/sdk_config.h: 135&lt;br /&gt;dtm/direct_test_mode/pca10040/s332/config/sdk_config.h: 135&lt;br /&gt;dtm/direct_test_mode/pca10040/s132/config/sdk_config.h: 135&lt;br /&gt;dtm/dtm_serialization/pca10040/ser_s132_spi/config/sdk_config.h: 915&lt;br /&gt;dtm/dtm_serialization/pca10040/ser_s132_uart/config/sdk_config.h: 746&lt;br /&gt;dtm/dtm_serialization/pca10040/ser_s132_hci/config/sdk_config.h: 753&lt;br /&gt;dtm/dtm_serialization/pca10040/ser_s132_spi_5W/config/sdk_config.h: 753&lt;br /&gt;ble_peripheral/ble_app_beacon/pca10040/s132/config/sdk_config.h: 3797&lt;br /&gt;ble_peripheral/ble_app_hids_keyboard/pca10040/ser_s132_spi/config/sdk_config.h: 3797&lt;br /&gt;ble_peripheral/ble_app_hids_keyboard/pca10040/s132/config/sdk_config.h: 3797&lt;br /&gt;ble_peripheral/ble_app_hids_keyboard/pca10040/ser_s132_uart/config/sdk_config.h: 3797&lt;br /&gt;ble_peripheral/ble_app_hids_keyboard/pca10040/ser_s132_hci/config/sdk_config.h: 3797&lt;br /&gt;ble_peripheral/experimental_ble_app_bms/pca10040/s132/config/sdk_config.h: 3797&lt;br /&gt;ble_peripheral/ble_app_hrs_freertos/pca10040/s132/config/sdk_config.h: 3811&lt;br /&gt;ble_peripheral/ble_app_gls/pca10040/ser_s132_spi/config/sdk_config.h: 3804&lt;br /&gt;ble_peripheral/ble_app_gls/pca10040/s132/config/sdk_config.h: 3804&lt;br /&gt;ble_peripheral/ble_app_gls/pca10040/ser_s132_uart/config/sdk_config.h: 3797&lt;br /&gt;ble_peripheral/ble_app_gls/pca10040/ser_s132_hci/config/sdk_config.h: 3797&lt;br /&gt;ble_peripheral/ble_app_cts_c/pca10040/ser_s132_spi/config/sdk_config.h: 3804&lt;br /&gt;ble_peripheral/ble_app_cts_c/pca10040/s132/config/sdk_config.h: 3804&lt;br /&gt;ble_peripheral/ble_app_cts_c/pca10040/ser_s132_uart/config/sdk_config.h: 3804&lt;br /&gt;ble_peripheral/ble_app_cts_c/pca10040/ser_s132_hci/config/sdk_config.h: 3804&lt;br /&gt;ble_peripheral/ble_app_cscs/pca10040/ser_s132_spi/config/sdk_config.h: 3797&lt;br /&gt;ble_peripheral/ble_app_cscs/pca10040/s132/config/sdk_config.h: 3797&lt;br /&gt;ble_peripheral/ble_app_cscs/pca10040/ser_s132_uart/config/sdk_config.h: 3797&lt;br /&gt;ble_peripheral/ble_app_cscs/pca10040/ser_s132_hci/config/sdk_config.h: 3797&lt;br /&gt;ble_peripheral/ble_app_alert_notification/pca10040/ser_s132_spi/config/sdk_config.h: 3804&lt;br /&gt;ble_peripheral/ble_app_alert_notification/pca10040/s132/config/sdk_config.h: 3804&lt;br /&gt;ble_peripheral/ble_app_alert_notification/pca10040/ser_s132_uart/config/sdk_config.h: 3804&lt;br /&gt;ble_peripheral/ble_app_alert_notification/pca10040/ser_s132_hci/config/sdk_config.h: 3804&lt;br /&gt;ble_peripheral/ble_app_uart/pca10040/s132/config/sdk_config.h: 3811&lt;br /&gt;ble_peripheral/ble_app_bps/pca10040/ser_s132_spi/config/sdk_config.h: 3804&lt;br /&gt;ble_peripheral/ble_app_bps/pca10040/s132/config/sdk_config.h: 3804&lt;br /&gt;ble_peripheral/ble_app_bps/pca10040/ser_s132_uart/config/sdk_config.h: 3804&lt;br /&gt;ble_peripheral/ble_app_bps/pca10040/ser_s132_hci/config/sdk_config.h: 3804&lt;br /&gt;ble_peripheral/ble_app_eddystone/pca10040/s132/config/sdk_config.h: 3804&lt;br /&gt;ble_peripheral/ble_app_rscs/pca10040/ser_s132_spi/config/sdk_config.h: 3797&lt;br /&gt;ble_peripheral/ble_app_rscs/pca10040/s332/config/sdk_config.h: 3797&lt;br /&gt;ble_peripheral/ble_app_rscs/pca10040/s132/config/sdk_config.h: 3797&lt;br /&gt;ble_peripheral/ble_app_rscs/pca10040/ser_s132_uart/config/sdk_config.h: 3797&lt;br /&gt;ble_peripheral/ble_app_rscs/pca10040/ser_s132_hci/config/sdk_config.h: 3797&lt;br /&gt;ble_peripheral/ble_app_hrs/pca10040/ser_s132_spi/config/sdk_config.h: 3827&lt;br /&gt;ble_peripheral/ble_app_hrs/pca10040/s332/config/sdk_config.h: 3827&lt;br /&gt;ble_peripheral/ble_app_hrs/pca10040/s132/config/sdk_config.h: 3837&lt;br /&gt;ble_peripheral/ble_app_hrs/pca10040/ser_s132_uart/config/sdk_config.h: 3827&lt;br /&gt;ble_peripheral/ble_app_hrs/pca10040/ser_s132_hci/config/sdk_config.h: 3827&lt;br /&gt;ble_peripheral/ble_app_hrs/pca10040/ser_s132_spi_5W/config/sdk_config.h: 3827&lt;br /&gt;ble_peripheral/experimental_ble_app_hids_keyboard_pairing_nfc/pca10040/s132/config/sdk_config.h: 3937&lt;br /&gt;ble_peripheral/experimental_ble_app_buttonless_dfu/pca10040/s132/config/sdk_config.h: 3797&lt;br /&gt;ble_peripheral/ble_app_hids_mouse/pca10040/ser_s132_spi/config/sdk_config.h: 3797&lt;br /&gt;ble_peripheral/ble_app_hids_mouse/pca10040/s132/config/sdk_config.h: 3797&lt;br /&gt;ble_peripheral/ble_app_hids_mouse/pca10040/ser_s132_uart/config/sdk_config.h: 3797&lt;br /&gt;ble_peripheral/ble_app_hids_mouse/pca10040/ser_s132_hci/config/sdk_config.h: 3797&lt;br /&gt;ble_peripheral/experimental_ble_app_hrs_pairing_nfc/pca10040/s132/config/sdk_config.h: 3951&lt;br /&gt;ble_peripheral/experimental_ble_app_blinky/pca10040/ser_s132_spi/config/sdk_config.h: 3797&lt;br /&gt;ble_peripheral/experimental_ble_app_blinky/pca10040/s132/config/sdk_config.h: 3797&lt;br /&gt;ble_peripheral/experimental_ble_app_blinky/pca10040/ser_s132_uart/config/sdk_config.h: 3797&lt;br /&gt;ble_peripheral/experimental_ble_app_blinky/pca10040/ser_s132_hci/config/sdk_config.h: 3797&lt;br /&gt;ble_peripheral/ble_app_proximity/pca10040/s132/config/sdk_config.h: 3811&lt;br /&gt;ble_peripheral/experimental_ble_app_cgms/pca10040/s132/config/sdk_config.h: 3797&lt;br /&gt;ble_peripheral/ble_app_hts/pca10040/ser_s132_spi/config/sdk_config.h: 3797&lt;br /&gt;ble_peripheral/ble_app_hts/pca10040/s132/config/sdk_config.h: 3797&lt;br /&gt;ble_peripheral/ble_app_hts/pca10040/ser_s132_uart/config/sdk_config.h: 3797&lt;br /&gt;ble_peripheral/ble_app_hts/pca10040/ser_s132_hci/config/sdk_config.h: 3797&lt;br /&gt;ble_peripheral/ble_app_ancs_c/pca10040/ser_s132_spi/config/sdk_config.h: 3811&lt;br /&gt;ble_peripheral/ble_app_ancs_c/pca10040/s132/config/sdk_config.h: 3811&lt;br /&gt;ble_peripheral/ble_app_ancs_c/pca10040/ser_s132_uart/config/sdk_config.h: 3804&lt;br /&gt;ble_peripheral/ble_app_ancs_c/pca10040/ser_s132_hci/config/sdk_config.h: 3804&lt;br /&gt;ble_peripheral/ble_app_template/pca10040/s132/config/sdk_config.h: 3797&lt;br /&gt;ble_peripheral/experimental_ble_app_lns/pca10040/ser_s132_spi/config/sdk_config.h: 3797&lt;br /&gt;ble_peripheral/experimental_ble_app_lns/pca10040/s132/config/sdk_config.h: 3797&lt;br /&gt;ble_peripheral/experimental_ble_app_lns/pca10040/ser_s132_uart/config/sdk_config.h: 3797&lt;br /&gt;ble_peripheral/experimental_ble_app_lns/pca10040/ser_s132_hci/config/sdk_config.h: 3797&lt;br /&gt;ble_peripheral/experimental_bluetoothds_template/pca10040/s132/config/sdk_config.h: 3797&lt;br /&gt;ble_peripheral/experimental_ble_app_queued_writes/pca10040/s132/config/sdk_config.h: 3797&lt;br /&gt;ble_peripheral/ble_app_pwr_profiling/pca10040/ser_s132_spi/config/sdk_config.h: 3797&lt;br /&gt;ble_peripheral/ble_app_pwr_profiling/pca10040/s132/config/sdk_config.h: 3797&lt;br /&gt;ble_peripheral/ble_app_pwr_profiling/pca10040/ser_s132_uart/config/sdk_config.h: 3797&lt;br /&gt;ble_peripheral/ble_app_pwr_profiling/pca10040/ser_s132_hci/config/sdk_config.h: 3797&lt;br /&gt;ble_central/ble_app_uart_c/pca10040/ser_s132_spi/config/sdk_config.h: 3818&lt;br /&gt;ble_central/ble_app_uart_c/pca10040/s132/config/sdk_config.h: 3818&lt;br /&gt;ble_central/ble_app_multilink_central/pca10040/s132/config/sdk_config.h: 3804&lt;br /&gt;ble_central/experimental/ble_app_blinky_c/pca10040/s132/config/sdk_config.h: 3804&lt;br /&gt;ble_central/experimental/ble_app_rscs_c/pca10040/ser_s132_spi/config/sdk_config.h: 3804&lt;br /&gt;ble_central/experimental/ble_app_rscs_c/pca10040/s132/config/sdk_config.h: 3804&lt;br /&gt;ble_central/ble_app_hrs_c/pca10040/ser_s132_spi/config/sdk_config.h: 3834&lt;br /&gt;ble_central/ble_app_hrs_c/pca10040/s132/config/sdk_config.h: 3844&lt;br /&gt;nfc/experimental_writable_ndef_msg/pca10040/blank/config/sdk_config.h: 754&lt;br /&gt;nfc/wake_on_nfc/pca10040/blank/config/sdk_config.h: 699&lt;br /&gt;nfc/record_text/pca10040/blank/config/sdk_config.h: 753&lt;br /&gt;nfc/record_launch_app/pca10040/blank/config/sdk_config.h: 753&lt;br /&gt;nfc/adafruit_tag_reader/pca10040/blank/config/sdk_config.h: 1250&lt;br /&gt;nfc/record_url/pca10040/blank/config/sdk_config.h: 753&lt;br /&gt;peripheral/rng/pca10040/blank/config/sdk_config.h: 3797&lt;br /&gt;peripheral/rng/pca10040/s132/config/sdk_config.h: 3797&lt;br /&gt;peripheral/uart/pca10040/blank/config/sdk_config.h: 516&lt;br /&gt;peripheral/pwr_mgmt/pca10040/blank/config/sdk_config.h: 848&lt;br /&gt;peripheral/csense_drv/pca10040/blank/config/sdk_config.h: 992&lt;br /&gt;peripheral/blinky/pca10040/blank/config/sdk_config.h: 3797&lt;br /&gt;peripheral/blinky/pca10040/s132/config/sdk_config.h: 3797&lt;br /&gt;peripheral/temperature/pca10040/blank/config/sdk_config.h: 479&lt;br /&gt;peripheral/rtc/pca10040/blank/config/sdk_config.h: 695&lt;br /&gt;peripheral/preflash/pca10040/blank/config/sdk_config.h: 853&lt;br /&gt;peripheral/wdt/pca10040/blank/config/sdk_config.h: 796&lt;br /&gt;peripheral/csense/pca10040/blank/config/sdk_config.h: 1064&lt;br /&gt;peripheral/twi_master_with_twis_slave/pca10040/blank/config/sdk_config.h: 909&lt;br /&gt;peripheral/radio/transmitter/pca10040/blank/config/sdk_config.h: 633&lt;br /&gt;peripheral/radio/receiver/pca10040/blank/config/sdk_config.h: 626&lt;br /&gt;peripheral/uicr_config/pca10040/blank/config/sdk_config.h: 122&lt;br /&gt;peripheral/saadc/pca10040/blank/config/sdk_config.h: 1007&lt;br /&gt;peripheral/qdec/pca10040/blank/config/sdk_config.h: 721&lt;br /&gt;peripheral/spi/pca10040/blank/config/sdk_config.h: 821&lt;br /&gt;peripheral/pwm_library/pca10040/blank/config/sdk_config.h: 789&lt;br /&gt;peripheral/blinky_systick/pca10040/blank/config/sdk_config.h: 135&lt;br /&gt;peripheral/fpu_fft/pca10040/blank/config/sdk_config.h: 479&lt;br /&gt;peripheral/fpu_fft/pca10040/s132/config/sdk_config.h: 608&lt;br /&gt;peripheral/fpu_fft/pca10040/blank_irq/config/sdk_config.h: 479&lt;br /&gt;peripheral/fpu_fft/pca10040/s132_irq/config/sdk_config.h: 608&lt;br /&gt;peripheral/blinky_freertos/pca10040/blank/config/sdk_config.h: 699&lt;br /&gt;peripheral/ppi/pca10040/blank/config/sdk_config.h: 692&lt;br /&gt;peripheral/twi_master_using_app_twi/pca10040/blank/config/sdk_config.h: 960&lt;br /&gt;peripheral/i2s/pca10040/blank/config/sdk_config.h: 700&lt;br /&gt;peripheral/pwm_driver/pca10040/blank/config/sdk_config.h: 876&lt;br /&gt;peripheral/gpiote/pca10040/blank/config/sdk_config.h: 776&lt;br /&gt;peripheral/simple_timer/pca10040/blank/config/sdk_config.h: 791&lt;br /&gt;peripheral/spis/pca10040/blank/config/sdk_config.h: 793&lt;br /&gt;peripheral/twi_scanner/pca10040/blank/config/sdk_config.h: 614&lt;br /&gt;peripheral/template_project/pca10040/blank/config/sdk_config.h: 3367&lt;br /&gt;peripheral/radio_test/pca10040/blank/config/sdk_config.h: 516&lt;br /&gt;peripheral/led_softblink/pca10040/blank/config/sdk_config.h: 622&lt;br /&gt;peripheral/lpcomp/pca10040/blank/config/sdk_config.h: 614&lt;br /&gt;peripheral/ram_retention/pca10040/blank/config/sdk_config.h: 122&lt;br /&gt;peripheral/pin_change_int/pca10040/blank/config/sdk_config.h: 563&lt;br /&gt;peripheral/twi_sensor/pca10040/blank/config/sdk_config.h: 614&lt;br /&gt;peripheral/timer/pca10040/blank/config/sdk_config.h: 630&lt;br /&gt;peripheral/flashwrite/pca10040/blank/config/sdk_config.h: 479&lt;br /&gt;peripheral/low_power_pwm/pca10040/blank/config/sdk_config.h: 615&lt;br /&gt;peripheral/bsp/pca10040/blank/config/sdk_config.h: 633&lt;br /&gt;peripheral/fatfs/pca10040/blank/config/sdk_config.h: 718&lt;br /&gt;ble_central_and_peripheral/experimental/ble_app_multirole_lesc/pca10040/s132/config/sdk_config.h: 3818&lt;br /&gt;ble_central_and_peripheral/experimental/ble_app_hrs_rscs_relay/pca10040/s132/config/sdk_config.h: 3818&lt;br /&gt;ble_central_and_peripheral/experimental/ble_app_att_mtu_throughput/pca10040/s132/config/sdk_config.h: 3884&lt;br /&gt;ble_central_and_peripheral/ble_connectivity/pca10040/ser_s132_spi/config/sdk_config.h: 862&lt;br /&gt;ble_central_and_peripheral/ble_connectivity/pca10040/ser_s132_uart/config/sdk_config.h: 661&lt;br /&gt;ble_central_and_peripheral/ble_connectivity/pca10040/ser_s132_hci/config/sdk_config.h: 675&lt;br /&gt;ble_central_and_peripheral/ble_connectivity/pca10040/ser_s132_spi_5W/config/sdk_config.h: 862&lt;br /&gt;multiprotocol/experimental_ble_app_gzll/pca10040/s132/config/sdk_config.h: 3811&lt;br /&gt;multiprotocol/ble_ant_app_hrm/pca10040/s332/config/sdk_config.h: 1155&lt;br /&gt;proprietary_rf/esb_ptx/pca10040/blank/config/sdk_config.h: 479&lt;br /&gt;proprietary_rf/esb_prx/pca10040/blank/config/sdk_config.h: 479&lt;br /&gt;proprietary_rf/gzll/experimental/gzp_dynamic_pairing/device/pca10040/blank/config/sdk_config.h: 602&lt;br /&gt;proprietary_rf/gzll/experimental/gzp_dynamic_pairing/host/pca10040/blank/config/sdk_config.h: 602&lt;br /&gt;proprietary_rf/gzll/experimental/gzll_ack_payload/device/pca10040/blank/config/sdk_config.h: 602&lt;br /&gt;proprietary_rf/gzll/experimental/gzll_ack_payload/host/pca10040/blank/config/sdk_config.h: 602&lt;br /&gt;proprietary_rf/gzll/experimental/gzp_desktop_emulator/pca10040/config/sdk_config.h: 516&lt;br /&gt;proprietary_rf/esb_low_power_ptx/pca10040/blank/config/sdk_config.h: 479&lt;br /&gt;proprietary_rf/esb_low_power_prx/pca10040/blank/config/sdk_config.h: 479&lt;br /&gt;dfu/bootloader_secure/pca10040/config/sdk_config.h: 515&lt;br /&gt;dfu/bootloader_secure/pca10040_debug/config/sdk_config.h: 654&lt;br /&gt;dfu/experimental_ant_bootloader/pca10040/dual_bank_ant_s332/config/sdk_config.h: 868&lt;br /&gt;dfu/experimental_ant_bootloader/pca10040/dual_bank_ant_s212/config/sdk_config.h: 868&lt;br /&gt;dfu/experimental_ant_bootloader/ota_tester/pca10040/s332/config/sdk_config.h: 527&lt;br /&gt;dfu/experimental_ant_bootloader/ota_tester/pca10040/s212/config/sdk_config.h: 527&lt;br /&gt;ant/ant_time_synchronization/tx/pca10040/s212/config/sdk_config.h: 786&lt;br /&gt;ant/ant_time_synchronization/rx/pca10040/s212/config/sdk_config.h: 809&lt;br /&gt;ant/ant_search_sharing/pca10040/s212/config/sdk_config.h: 839&lt;br /&gt;ant/ant_broadcast/tx/pca10040/s212/config/sdk_config.h: 786&lt;br /&gt;ant/ant_broadcast/rx/pca10040/s212/config/sdk_config.h: 786&lt;br /&gt;ant/ant_cw_mode/pca10040/s212/config/sdk_config.h: 640&lt;br /&gt;ant/ant_continuous_scanning_controller/pca10040/s212/config/sdk_config.h: 797&lt;br /&gt;ant/ant_high_duty_search_and_background_scanning/pca10040/s212/config/sdk_config.h: 797&lt;br /&gt;ant/ant_multi_channels/tx/pca10040/s212/config/sdk_config.h: 774&lt;br /&gt;ant/ant_multi_channels/rx/pca10040/s212/config/sdk_config.h: 797&lt;br /&gt;ant/ant_debug/pca10040/s212/config/sdk_config.h: 826&lt;br /&gt;ant/ant_background_scanning/pca10040/s212/config/sdk_config.h: 797&lt;br /&gt;ant/ant_plus/ant_hrm/hrm_tx/pca10040/s212/config/sdk_config.h: 1072&lt;br /&gt;ant/ant_plus/ant_hrm/hrm_rx/pca10040/s212/config/sdk_config.h: 993&lt;br /&gt;ant/ant_plus/ant_sdm/sdm_tx/pca10040/s212/config/sdk_config.h: 1238&lt;br /&gt;ant/ant_plus/ant_sdm/sdm_rx/pca10040/s212/config/sdk_config.h: 1138&lt;br /&gt;ant/ant_plus/ant_bpwr/bpwr_rx/pca10040/s212/config/sdk_config.h: 1122&lt;br /&gt;ant/ant_plus/ant_bpwr/bpwr_tx/pca10040/s212/config/sdk_config.h: 1201&lt;br /&gt;ant/ant_plus/ant_bsc/bsc_tx/pca10040/s212/config/sdk_config.h: 1135&lt;br /&gt;ant/ant_plus/ant_bsc/bsc_rx/pca10040/s212/config/sdk_config.h: 1083&lt;br /&gt;ant/experimental/ant_shared_channel/slave/pca10040/s212/config/sdk_config.h: 644&lt;br /&gt;ant/experimental/ant_shared_channel/master_to_master/pca10040/s332/config/sdk_config.h: 741&lt;br /&gt;ant/ant_relay_demo/pca10040/s212/config/sdk_config.h: 835&lt;br /&gt;ant/ant_message_types/master/pca10040/s332/config/sdk_config.h: 774&lt;br /&gt;ant/ant_message_types/master/pca10040/s212/config/sdk_config.h: 774&lt;br /&gt;ant/ant_async_transmitter/pca10040/s212/config/sdk_config.h: 797&lt;br /&gt;ant/ant_fs/client/pca10040/s212/config/sdk_config.h: 926&lt;br /&gt;ant/ant_io_demo/ant_io_rx/pca10040/s212/config/sdk_config.h: 802&lt;br /&gt;ant/ant_io_demo/ant_io_tx/pca10040/s212/config/sdk_config.h: 797&lt;br /&gt;ant/ant_scan_and_forward/pca10040/s212/config/sdk_config.h: 802&lt;br /&gt;ant/ant_search_uplink/pca10040/s212/config/sdk_config.h: 792&lt;br /&gt;ant/ant_multi_channels_encrypted/tx/pca10040/s212/config/sdk_config.h: 781&lt;br /&gt;ant/ant_multi_channels_encrypted/rx/pca10040/s212/config/sdk_config.h: 811&lt;br /&gt;ant/ant_advanced_burst/pca10040/s212/config/sdk_config.h: 781&lt;br /&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;span&gt;These files differ by A LOT.&amp;nbsp; It&amp;#39;s not just which flags are 1 and which flags are 0.&amp;nbsp; Hundreds, even thousands&amp;nbsp;of lines may differ.&amp;nbsp; Some flags are only defined in certain sdk_config.h files.&amp;nbsp;&amp;nbsp;&lt;/span&gt;&lt;span&gt;I have found it challenging to identify the differences between sdk_config.h files, and to merge them when I need multiple subsystems to work together.&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: "Undefined Reference" on the linker level</title><link>https://devzone.nordicsemi.com/thread/153354?ContentTypeID=1</link><pubDate>Thu, 18 Oct 2018 02:12:08 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:222c92bd-24c2-4bb3-b70c-b57e1ea17f02</guid><dc:creator>Connie Violet</dc:creator><description>&lt;p&gt;Hi, Jorgen. I did checked and made sure that this part in my sdk_config.h look the same as what you pasted here but it did not solve the problem, and that was why I made this post.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: "Undefined Reference" on the linker level</title><link>https://devzone.nordicsemi.com/thread/153327?ContentTypeID=1</link><pubDate>Wed, 17 Oct 2018 16:35:39 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f7c68bdb-a43c-4b47-81b7-e6aa0fe8b740</guid><dc:creator>awneil</dc:creator><description>&lt;p&gt;That&amp;#39;s good to hear!&lt;/p&gt;
&lt;p&gt;So, for input to that task, let&amp;#39;s just look at the TWI driver as an example:&lt;/p&gt;
&lt;p&gt;&lt;a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk5.v15.2.0/group__nrfx__twi.html"&gt;http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk5.v15.2.0/group__nrfx__twi.html&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;I don&amp;#39;t see anything there at all which tells which files need to be added to a Project.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;There is a link to &amp;quot;&lt;a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk5.v15.2.0/group__nrfx__twi__config.html"&gt;TWI peripheral driver configuration&lt;/a&gt;&amp;quot;&lt;/p&gt;
&lt;p&gt;This does list&amp;nbsp;&lt;span&gt;NRFX_TWI_ENABLED - and says&amp;nbsp; &amp;quot;set to 1 to&amp;nbsp;activate&amp;quot;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;But it&amp;#39;s not really clear &lt;em&gt;&lt;strong&gt;where&lt;/strong&gt;&lt;/em&gt; that setting has to be made.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;There&amp;#39;s a note saying, &amp;quot;This is an NRF_CONFIG macro&amp;quot; - but what does that mean?&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;I guess it&amp;#39;s&lt;/span&gt;&lt;span&gt;&amp;nbsp;supposed to tell us that it&amp;#39;s in &lt;strong&gt;sdk_config.h&lt;/strong&gt; - is it?&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;It would be clearer if that were explicitly stated - with a link to the&amp;nbsp;&lt;strong&gt;sdk_config.h&lt;/strong&gt;&amp;nbsp;documentation.&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: "Undefined Reference" on the linker level</title><link>https://devzone.nordicsemi.com/thread/153233?ContentTypeID=1</link><pubDate>Wed, 17 Oct 2018 12:39:29 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:37269a03-079c-4d2b-bffe-05a550d19b31</guid><dc:creator>J&amp;#248;rgen Holmefjord</dc:creator><description>&lt;p&gt;Like I said, I agree that this is not well documented. We have an internal task requesting more documentation on library dependency documentation.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: "Undefined Reference" on the linker level</title><link>https://devzone.nordicsemi.com/thread/153225?ContentTypeID=1</link><pubDate>Wed, 17 Oct 2018 12:11:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6e5c4a93-d8c1-417e-b189-b84e429813ff</guid><dc:creator>awneil</dc:creator><description>[quote userid="14926" url="~/f/nordic-q-a/39503/undefined-reference-on-the-linker-level/153211"]this is more related to the modules themselves, rather than the sdk_config.h file[/quote]
&lt;p&gt;Indeed.&lt;/p&gt;
&lt;p&gt;But see my linked thread - I didn&amp;#39;t see anywhere that told me what files I needed to include!&lt;/p&gt;
[quote userid="14926" url="~/f/nordic-q-a/39503/undefined-reference-on-the-linker-level/153211"]the compiler will give you hints to what needs to be included/enabled[/quote]
&lt;p&gt;Indeed - but we&amp;#39;re back to development by reverse-engineering again.&lt;/p&gt;
&lt;p&gt;We shouldn&amp;#39;t have to discover this stuff by trial &amp;amp; error - it should be clearly documented up-front.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: "Undefined Reference" on the linker level</title><link>https://devzone.nordicsemi.com/thread/153211?ContentTypeID=1</link><pubDate>Wed, 17 Oct 2018 11:39:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:777ee2bc-d3f7-473a-9278-bd6d75a9055b</guid><dc:creator>J&amp;#248;rgen Holmefjord</dc:creator><description>&lt;p&gt;I agree that dependencies could have been documented better, but this is more related to the modules themselves, rather than the sdk_config.h file. You still needs to include the source files of the dependent modules.&lt;/p&gt;
&lt;p&gt;It might take some iterations to add all sub-modules that a module depends on, but the compiler will give you hints to what needs to be included/enabled.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: "Undefined Reference" on the linker level</title><link>https://devzone.nordicsemi.com/thread/153015?ContentTypeID=1</link><pubDate>Tue, 16 Oct 2018 09:35:39 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e61bcb57-f39a-49f5-9119-f3c3e905e298</guid><dc:creator>awneil</dc:creator><description>&lt;p&gt;and why does the forum quote feature keep going wrong like that - ie, the quoted text is outside the quote marker!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: "Undefined Reference" on the linker level</title><link>https://devzone.nordicsemi.com/thread/153012?ContentTypeID=1</link><pubDate>Tue, 16 Oct 2018 09:34:18 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:28a0e1f0-bad8-4511-8777-f87fdede07a2</guid><dc:creator>awneil</dc:creator><description>&lt;p&gt;[quote userid="14926" url="~/f/nordic-q-a/39503/undefined-reference-on-the-linker-level/153008"][/quote]&lt;/p&gt;
&lt;p&gt;I think it is explained well in the &lt;a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk5.v15.2.0/sdk_config.html?cp=4_0_0_1_6"&gt;documentation&lt;/a&gt;:&lt;/p&gt;
&lt;p&gt;&lt;em&gt;&amp;quot;Every module in SDK contains at least one configuration option that enables this module&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;I didn&amp;#39;t find that it was always easy to identify &lt;em&gt;&lt;strong&gt;what&lt;/strong&gt;&lt;/em&gt; configuration option(s) is/are required by a particular module.&lt;/p&gt;
&lt;p&gt;Especially as some (many? most?) modules have dependencies on other modules.&lt;/p&gt;
&lt;p&gt;Plus the added confusion of there often being NRFX and &amp;quot;legacy&amp;quot; versions of the same thing ...&lt;/p&gt;
&lt;p&gt;eg, see:&amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/39469/linking-mpu6050-sensor-with-ble-uart/152957#152957"&gt;https://devzone.nordicsemi.com/f/nordic-q-a/39469/linking-mpu6050-sensor-with-ble-uart/152957#152957&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;See also:&amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/34739/how-to-add-simple-timer-to-a-project/133302#133302"&gt;https://devzone.nordicsemi.com/f/nordic-q-a/34739/how-to-add-simple-timer-to-a-project/133302#133302&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: "Undefined Reference" on the linker level</title><link>https://devzone.nordicsemi.com/thread/153008?ContentTypeID=1</link><pubDate>Tue, 16 Oct 2018 09:23:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f7af12b7-a86f-4fc4-bc0f-a213a2249d0f</guid><dc:creator>J&amp;#248;rgen Holmefjord</dc:creator><description>[quote userid="6462" url="~/f/nordic-q-a/39503/undefined-reference-on-the-linker-level/153004"]However, in this case, I would have thought you would have got compile errors?[/quote]
&lt;p&gt;As long as the header file where the function is declared is included, you will not get compilation error. If header file is included but source file is not included in project, you will get this linker error.&lt;/p&gt;
[quote userid="6462" url="~/f/nordic-q-a/39503/undefined-reference-on-the-linker-level/153004"]this one is a frequent cause of confusion - so maybe there&amp;#39;s a clue for Nordic there, that it needs to be better explained...?[/quote]
&lt;p&gt;I think it is explained well in the &lt;a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk5.v15.2.0/sdk_config.html?cp=4_0_0_1_6"&gt;documentation&lt;/a&gt;:&lt;/p&gt;
&lt;p&gt;&lt;em&gt;&amp;quot;Every module in SDK contains at least one configuration option that enables this module. If the module is disabled, then even if source code is added to the project, it is not compiled because the module implementation is conditionally included.&amp;quot;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;I will say that is should be expected of customers to read through the &lt;a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk5.v15.2.0/nrf51_getting_started.html?cp=4_0_0_1"&gt;Getting Started section&lt;/a&gt; of the SDK documentation to get familiar with the SDK before starting to develop applications.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: "Undefined Reference" on the linker level</title><link>https://devzone.nordicsemi.com/thread/153004?ContentTypeID=1</link><pubDate>Tue, 16 Oct 2018 09:12:42 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:89dbd91e-52da-4072-9ff4-a0e1f89956e5</guid><dc:creator>awneil</dc:creator><description>[quote userid="14926" url="~/f/nordic-q-a/39503/undefined-reference-on-the-linker-level/152988"]You have not included the source file that implements the functions in your project[/quote]
&lt;p&gt;This is a standard &amp;#39;C&amp;#39; issue - nothing specifically to do with Nordic.&lt;/p&gt;
&lt;p&gt;However, in this case, I would have thought you would have got compile errors?&lt;/p&gt;
[quote userid="14926" url="~/f/nordic-q-a/39503/undefined-reference-on-the-linker-level/152988"]ou have not enabled the module in your project&amp;#39;s sdk_config.h file.[/quote]
&lt;p&gt;This one is specific to the way Nordic configure their SDKs.&lt;/p&gt;
&lt;p&gt;As&amp;nbsp;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;a class="internal-link view-user-profile" href="https://devzone.nordicsemi.com/members/joh2"&gt;J&amp;oslash;rgen Holmefjord&lt;/a&gt;&amp;nbsp;said, this one is a frequent cause of confusion - so maybe there&amp;#39;s a clue for Nordic there, that it needs to be better explained...?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: "Undefined Reference" on the linker level</title><link>https://devzone.nordicsemi.com/thread/152988?ContentTypeID=1</link><pubDate>Tue, 16 Oct 2018 08:34:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0a067b28-a98d-4a66-bc0d-c4dcfe6cbcc2</guid><dc:creator>J&amp;#248;rgen Holmefjord</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;This is caused by one of (or both) the following things:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;You have not included the source file that implements the functions in your project. In SDK 12.3.0, these functions are implemented in the source file &amp;#39;nRF5_SDK_12.3.0_d7731ad\components\drivers_nrf\twi_master\nrf_drv_twi.c&amp;#39;&lt;/li&gt;
&lt;li&gt;You have not enabled the module in your project&amp;#39;s sdk_config.h file. Check if you can find TWI_ENABLED in the file, and set it to 1. If you cannot find this section in the sdk_config.h file in the BLE project, you need to copy the entire section related to the TWI master driver from one of the TWI master projects and add it to the sdk_config.h file of your BLE project.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="c_cpp"&gt;// &amp;lt;e&amp;gt; TWI_ENABLED - nrf_drv_twi - TWI/TWIM peripheral driver
//==========================================================
#ifndef TWI_ENABLED
#define TWI_ENABLED 1
#endif
#if  TWI_ENABLED
// &amp;lt;o&amp;gt; TWI_DEFAULT_CONFIG_FREQUENCY  - Frequency
 
// &amp;lt;26738688=&amp;gt; 100k 
// &amp;lt;67108864=&amp;gt; 250k 
// &amp;lt;104857600=&amp;gt; 400k 

#ifndef TWI_DEFAULT_CONFIG_FREQUENCY
#define TWI_DEFAULT_CONFIG_FREQUENCY 26738688
#endif

// &amp;lt;q&amp;gt; TWI_DEFAULT_CONFIG_CLR_BUS_INIT  - Enables bus clearing procedure during init
 

#ifndef TWI_DEFAULT_CONFIG_CLR_BUS_INIT
#define TWI_DEFAULT_CONFIG_CLR_BUS_INIT 0
#endif

// &amp;lt;q&amp;gt; TWI_DEFAULT_CONFIG_HOLD_BUS_UNINIT  - Enables bus holding after uninit
 

#ifndef TWI_DEFAULT_CONFIG_HOLD_BUS_UNINIT
#define TWI_DEFAULT_CONFIG_HOLD_BUS_UNINIT 0
#endif

// &amp;lt;o&amp;gt; TWI_DEFAULT_CONFIG_IRQ_PRIORITY  - Interrupt priority
 

// &amp;lt;i&amp;gt; Priorities 0,2 (nRF51) and 0,1,4,5 (nRF52) are reserved for SoftDevice
// &amp;lt;0=&amp;gt; 0 (highest) 
// &amp;lt;1=&amp;gt; 1 
// &amp;lt;2=&amp;gt; 2 
// &amp;lt;3=&amp;gt; 3 
// &amp;lt;4=&amp;gt; 4 
// &amp;lt;5=&amp;gt; 5 
// &amp;lt;6=&amp;gt; 6 
// &amp;lt;7=&amp;gt; 7 

#ifndef TWI_DEFAULT_CONFIG_IRQ_PRIORITY
#define TWI_DEFAULT_CONFIG_IRQ_PRIORITY 7
#endif

// &amp;lt;e&amp;gt; TWI0_ENABLED - Enable TWI0 instance
//==========================================================
#ifndef TWI0_ENABLED
#define TWI0_ENABLED 1
#endif
#if  TWI0_ENABLED
// &amp;lt;q&amp;gt; TWI0_USE_EASY_DMA  - Use EasyDMA (if present)
 

#ifndef TWI0_USE_EASY_DMA
#define TWI0_USE_EASY_DMA 1
#endif

#endif //TWI0_ENABLED
// &amp;lt;/e&amp;gt;

// &amp;lt;e&amp;gt; TWI1_ENABLED - Enable TWI1 instance
//==========================================================
#ifndef TWI1_ENABLED
#define TWI1_ENABLED 0
#endif
#if  TWI1_ENABLED
// &amp;lt;q&amp;gt; TWI1_USE_EASY_DMA  - Use EasyDMA (if present)
 

#ifndef TWI1_USE_EASY_DMA
#define TWI1_USE_EASY_DMA 0
#endif

#endif //TWI1_ENABLED
// &amp;lt;/e&amp;gt;

// &amp;lt;e&amp;gt; TWI_CONFIG_LOG_ENABLED - Enables logging in the module.
//==========================================================
#ifndef TWI_CONFIG_LOG_ENABLED
#define TWI_CONFIG_LOG_ENABLED 0
#endif
#if  TWI_CONFIG_LOG_ENABLED
// &amp;lt;o&amp;gt; TWI_CONFIG_LOG_LEVEL  - Default Severity level
 
// &amp;lt;0=&amp;gt; Off 
// &amp;lt;1=&amp;gt; Error 
// &amp;lt;2=&amp;gt; Warning 
// &amp;lt;3=&amp;gt; Info 
// &amp;lt;4=&amp;gt; Debug 

#ifndef TWI_CONFIG_LOG_LEVEL
#define TWI_CONFIG_LOG_LEVEL 3
#endif

// &amp;lt;o&amp;gt; TWI_CONFIG_INFO_COLOR  - ANSI escape code prefix.
 
// &amp;lt;0=&amp;gt; Default 
// &amp;lt;1=&amp;gt; Black 
// &amp;lt;2=&amp;gt; Red 
// &amp;lt;3=&amp;gt; Green 
// &amp;lt;4=&amp;gt; Yellow 
// &amp;lt;5=&amp;gt; Blue 
// &amp;lt;6=&amp;gt; Magenta 
// &amp;lt;7=&amp;gt; Cyan 
// &amp;lt;8=&amp;gt; White 

#ifndef TWI_CONFIG_INFO_COLOR
#define TWI_CONFIG_INFO_COLOR 0
#endif

// &amp;lt;o&amp;gt; TWI_CONFIG_DEBUG_COLOR  - ANSI escape code prefix.
 
// &amp;lt;0=&amp;gt; Default 
// &amp;lt;1=&amp;gt; Black 
// &amp;lt;2=&amp;gt; Red 
// &amp;lt;3=&amp;gt; Green 
// &amp;lt;4=&amp;gt; Yellow 
// &amp;lt;5=&amp;gt; Blue 
// &amp;lt;6=&amp;gt; Magenta 
// &amp;lt;7=&amp;gt; Cyan 
// &amp;lt;8=&amp;gt; White 

#ifndef TWI_CONFIG_DEBUG_COLOR
#define TWI_CONFIG_DEBUG_COLOR 0
#endif

#endif //TWI_CONFIG_LOG_ENABLED
// &amp;lt;/e&amp;gt;

#endif //TWI_ENABLED
// &amp;lt;/e&amp;gt;&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;If you had spent 1 minute searching DevZone for the errors you are experiencing, you would have found countless other questions answering how to solve this issue.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;br /&gt;Jørgen&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>