RTT not appearing in modified ble_app_uart example

RE: RTT not appearing in modified ble_app_uart example

Simonr — Mon, 16 Aug 2021 08:17:49 GMT

Hi Jake

The RETARGET_ENABLED will let youinclude the retarget layer for stdio functions. This is necessary to use printf to transmit data over UART, which is what your application tried doing when you had this define set to 1 and would be why the logging didn't go to RTT.

By default, all functions should already only be called from inside the SDK, with the path being set to ../../../SDK, setting the path prior to the SDK version to be relative.

Best regards,

Simon

RE: RTT not appearing in modified ble_app_uart example

jake11212 — Fri, 13 Aug 2021 16:43:51 GMT

I changed RETARGET_ENABLED to 0 and this fixed it, RTT is now working, thanks so much for working with me for so long!

What does RETARGET_ENABLED actually do? I checked the documentation page but there wasn't a description for it.

I wasn't getting any issues on my end with the bool switch statement or snprintf, and I didn't make any changes to SEGGER_RTT_Syscalls_SES.c to get it to run on my end so I'm not sure why it caused issues for you. I can look into it more if you'd like but my main problem is solved.

[quote userid="75734" url="~/f/nordic-q-a/78157/rtt-not-appearing-in-modified-ble_app_uart-example/324751#324751"]It took a minute to get the device up and running due to the paths you mentioned, but it was easy enough to remedy on my end when I knew. However, I had some trouble building due to this function in your main.c:[/quote]

This is outside the scope of the question, but how do you avoid this issue with the paths so that it can build purely from within the SDK?

RE: RTT not appearing in modified ble_app_uart example

Simonr — Fri, 13 Aug 2021 06:49:02 GMT

Hi Jake

It took a minute to get the device up and running due to the paths you mentioned, but it was easy enough to remedy on my end when I knew. However, I had some trouble building due to this function in your main.c:

 
  switch(writeBool) 
  { 
     case 0 : 
        snprintf(intermediate, sizeof(intermediate), "S: %x:%x:%d %x/%x/%x", rx_data[2], rx_data[1], rx_data[0], rx_data[5], rx_data[4], rx_data[6]);
        break;

     case 1 : 
        snprintf(intermediate, sizeof(intermediate), "E: %x:%x:%d %x/%x/%x", rx_data[2], rx_data[1], rx_data[0], rx_data[5], rx_data[4], rx_data[6]);
        break;

     default :
        break;
  }

First off, I get a warning because the switch condition has a boolean value, and tit seems like the snprintf functions are interfering with the way SEGGER_RTT_Syscalls_SES.c does RTT. If I commented this function out and set the RETARGET_ENABLED define in sdk_config.h to 0 on my end, RTT seems to work fine in the RTT Viewer, as it prints the wake up process every few seconds:

I think you need to rework this function as it seems to be the culprit to why the RTT viewer doesn't work. Please note that I didn't get the example running while using this function, so what changes did you make to other files, like the SEGGER_RTT_Syscalls_SES.c to get it to run on your end?

Best regards,

Simon

RE: RTT not appearing in modified ble_app_uart example

jake11212 — Wed, 11 Aug 2021 17:16:04 GMT

[quote userid="75734" url="~/f/nordic-q-a/78157/rtt-not-appearing-in-modified-ble_app_uart-example/324439#324439"]I was referring to defines like NRF_LOG_CLI_CMDS and NRF_CLI_ENABLED, which are set to 0 (and need to be enabled to use the CLI) in the ble_app_uart sdk_config.h file. I'm not sure if this is what's causing the lack of RTT logging, but it's worth a shot.[/quote]

I tried that out but still no luck.

[quote userid="75734" url="~/f/nordic-q-a/78157/rtt-not-appearing-in-modified-ble_app_uart-example/324439#324439"]Can you upload a .zip file with your project that can be placed in the SDK and run, so I don't have to use time reproducing the exact project you have?[/quote]

Sure, although when I give the paths for library locations to the preprocessor, those paths will be based on the location of my SDK on my hard drive. How do I get around this? I think what I did should work as I made sure all the referenced locations were just to the SDK and the SDK is just sitting at the top of a directory on my drive. Let me know if you have issues with it. It worked for me but it had to be within a folder within examples. On my machine the path is: D:\nRF5SDK1702d674dde\nRF5_SDK_17.0.2_d674dde\examples\peripheral\RebuildDemoV1.0. I added a chart of the logic too which should hopefully make it easier to follow what's going on.

One thing I noticed rebuilding was that when I was adding the necessary sections for fstorage/fds/twi/crc16 to the config file that there were duplicates of some statements. All the files I added to the config file are commented at the top of the page but I was wondering if there might be some issues from things being defined twice/turned on at the top/back off later.

devzone.nordicsemi.com/.../RebuildDemoV1.0.zip devzone.nordicsemi.com/.../Software-Logic-Chart.pdf

RE: RTT not appearing in modified ble_app_uart example

Simonr — Wed, 11 Aug 2021 10:59:02 GMT

Sorry, I was referring to defines like NRF_LOG_CLI_CMDS and NRF_CLI_ENABLED, which are set to 0 (and need to be enabled to use the CLI) in the ble_app_uart sdk_config.h file. I'm not sure if this is what's causing the lack of RTT logging, but it's worth a shot.

As I'm running out of leads as to what is causing this, I think I might need to try reproducing this on my end, as looking at it first hand usually makes it easier to spot what's causing it. Can you upload a .zip file with your project that can be placed in the SDK and run, so I don't have to use time reproducing the exact project you have?

Best regards,

Simon

RE: RTT not appearing in modified ble_app_uart example

jake11212 — Tue, 10 Aug 2021 20:32:44 GMT

[quote userid="75734" url="~/f/nordic-q-a/78157/rtt-not-appearing-in-modified-ble_app_uart-example/324249#324249"]What I did notice though, is that there are some CLI defines (amongst other things) disabled in the ble_app_uart example's config file. Have you remembered to enable these to go with the additional peripherals you're using?[/quote]

Which defines need to be enabled and what effects would CLI have on RTT? I don't think I understand the interaction and there are a lot of CLI defines so I'm not sure what changes I need to make or should try.

RE: RTT not appearing in modified ble_app_uart example

Simonr — Tue, 10 Aug 2021 12:53:04 GMT

Yes, the UART backend for logging is disabled by setting the NRF_LOG_BACKEND_UART_ENABLED to 0 in sdk_config.h. My mistake, this define is not used in the ble_app_uart example, as the UART backend is not used for logging, but for the application and NUS service instead.

What I did notice though, is that there are some CLI defines (amongst other things) disabled in the ble_app_uart example's config file. Have you remembered to enable these to go with the additional peripherals you're using?

The description of NRF_LOG_BACKEND_UART_ENABLED is wrong in the Infocenter it seems. I have reported this to our tech. doc. writers. Thank you for pointing that out!

Best regards,

Simon

RE: RTT not appearing in modified ble_app_uart example

jake11212 — Mon, 09 Aug 2021 17:16:26 GMT

[quote userid="75734" url="~/f/nordic-q-a/78157/rtt-not-appearing-in-modified-ble_app_uart-example/324035#324035"]So in your modified example project, the application is able to run past NRF_LOG_INFO() without asserting, correct?[/quote]

Yes.

[quote userid="75734" url="~/f/nordic-q-a/78157/rtt-not-appearing-in-modified-ble_app_uart-example/324035#324035"]Can you also confirm that the UART backend for logging is disabled and that only the RTT is enabled for logging, as enabling both might cause trouble.[/quote]

logging UART is just enabled through the code:

NRF_LOG_BACKEND_UART_ENABLED

in the sdk_config.h file correct? I can't find this anywhere in the config file which is strange since using UART with putty still works. Could this be enabled elsewhere? I also noticed on the page I linked for NRF_LOG_BACKEND_UART_ENABLED that the description says "enable RTT backend." Is this a mistake? Or does the UART backend enable both?

RE: RTT not appearing in modified ble_app_uart example

Simonr — Mon, 09 Aug 2021 13:36:40 GMT

So in your modified example project, the application is able to run past NRF_LOG_INFO() without asserting, correct? Can you also confirm that the UART backend for logging is disabled and that only the RTT is enabled for logging, as enabling both might cause trouble.

Best regards,

Simon

RE: RTT not appearing in modified ble_app_uart example

jake11212 — Fri, 06 Aug 2021 03:22:01 GMT

I'm using in-place processing. I had been using deferred previously with the only call to NRF_LOG_PROCESS() in the idle_state_handle(), but I changed some of the sleep mode behavior from the ble_app_uart example and changed to in place processing at that point as well since I thought the new sleep behavior would alter the processing.

RE: RTT not appearing in modified ble_app_uart example

Simonr — Thu, 05 Aug 2021 08:14:54 GMT

Hi again

Okay, this seems strange, not able to spot anything that should mess up RTT logging. Are you using deferred or in place processing? If deferred, where is NRF_LOG_PROCESS() called in your application?

Best regards,

Simon

RE: RTT not appearing in modified ble_app_uart example

jake11212 — Wed, 04 Aug 2021 15:43:36 GMT

[quote userid="75734" url="~/f/nordic-q-a/78157/rtt-not-appearing-in-modified-ble_app_uart-example/323257#323257"]What pins are your application using for TWI communication?[/quote]

I'm using Pin P0.14 for GPIO and P0.22 and P0.23 for SCL and SDA.

[quote userid="75734" url="~/f/nordic-q-a/78157/rtt-not-appearing-in-modified-ble_app_uart-example/323257#323257"]and what changes did you make to the sdk_config.h file exactly? [/quote]

The changes I made to the config file were:

#ifndef NRF_FSTORAGE_ENABLED

#define NRF_FSTORAGE_ENABLED 1

#endif

 

#ifndef NRF_FSTORAGE_PARAM_CHECK_DISABLED

#define NRF_FSTORAGE_PARAM_CHECK_DISABLED 0

#endif

 

#ifndef NRF_FSTORAGE_SD_QUEUE_SIZE

#define NRF_FSTORAGE_SD_QUEUE_SIZE 4

#endif

 

#ifndef NRF_FSTORAGE_SD_MAX_RETRIES

#define NRF_FSTORAGE_SD_MAX_RETRIES 8

#endif

 

#ifndef NRF_FSTORAGE_SD_MAX_WRITE_SIZE

#define NRF_FSTORAGE_SD_MAX_WRITE_SIZE 4096

#endif

#ifndef FDS_ENABLED

#define FDS_ENABLED 1

#endif

 

#ifndef FDS_VIRTUAL_PAGES

#define FDS_VIRTUAL_PAGES 30

#endif

 

#ifndef FDS_VIRTUAL_PAGE_SIZE

#define FDS_VIRTUAL_PAGE_SIZE 1024

#endif

 

#ifndef FDS_VIRTUAL_PAGES_RESERVED

#define FDS_VIRTUAL_PAGES_RESERVED 0

#endif

 

#ifndef FDS_BACKEND

#define FDS_BACKEND 2

#endif

 

#ifndef FDS_OP_QUEUE_SIZE

#define FDS_OP_QUEUE_SIZE 4

#endif

 

#ifndef FDS_CRC_CHECK_ON_READ

#define FDS_CRC_CHECK_ON_READ 1

#endif

 

#ifndef FDS_CRC_CHECK_ON_WRITE

#define FDS_CRC_CHECK_ON_WRITE 0

#endif

 

#ifndef FDS_MAX_USERS

#define FDS_MAX_USERS 4

#endif

 

#ifndef NRF_BALLOC_CLI_CMDS

#define NRF_BALLOC_CLI_CMDS 1

#endif

 

#ifndef NRF_QUEUE_CLI_CMDS

#define NRF_QUEUE_CLI_CMDS 1

#endif

 

#ifndef NRF_CLI_ENABLED

#define NRF_CLI_ENABLED 1

#endif

 

#ifndef NRF_CLI_ARGC_MAX

#define NRF_CLI_ARGC_MAX 12

#endif

 

#ifndef NRF_CLI_BUILD_IN_CMDS_ENABLED

#define NRF_CLI_BUILD_IN_CMDS_ENABLED 1

#endif

 

#ifndef NRF_CLI_CMD_BUFF_SIZE

#define NRF_CLI_CMD_BUFF_SIZE 128

#endif

 

#ifndef NRF_CLI_ECHO_STATUS

#define NRF_CLI_ECHO_STATUS 1

#endif

 

#ifndef NRF_CLI_WILDCARD_ENABLED

#define NRF_CLI_WILDCARD_ENABLED 0

#endif

 

#ifndef NRF_CLI_METAKEYS_ENABLED

#define NRF_CLI_METAKEYS_ENABLED 0

#endif

 

#ifndef NRF_CLI_PRINTF_BUFF_SIZE

#define NRF_CLI_PRINTF_BUFF_SIZE 23

#endif

 

#ifndef NRF_CLI_HISTORY_ENABLED

#define NRF_CLI_HISTORY_ENABLED 1

#endif

 

#ifndef NRF_CLI_HISTORY_ELEMENT_SIZE

#define NRF_CLI_HISTORY_ELEMENT_SIZE 32

#endif

 

#ifndef NRF_CLI_HISTORY_ELEMENT_COUNT

#define NRF_CLI_HISTORY_ELEMENT_COUNT 8

#endif

 

#ifndef NRF_CLI_VT100_COLORS_ENABLED

#define NRF_CLI_VT100_COLORS_ENABLED 1

#endif

 

#ifndef NRF_CLI_STATISTICS_ENABLED

#define NRF_CLI_STATISTICS_ENABLED 1

#endif

 

#ifndef NRF_CLI_LOG_BACKEND

#define NRF_CLI_LOG_BACKEND 1

#endif

 

#ifndef NRF_CLI_USES_TASK_MANAGER_ENABLED

#define NRF_CLI_USES_TASK_MANAGER_ENABLED 0

#endif

 

#ifndef NRF_CLI_BLE_UART_CONFIG_LOG_ENABLED

#define NRF_CLI_BLE_UART_CONFIG_LOG_ENABLED 0

#endif

 

#ifndef NRF_CLI_BLE_UART_CONFIG_LOG_LEVEL

#define NRF_CLI_BLE_UART_CONFIG_LOG_LEVEL 3

#endif

 

#ifndef NRF_CLI_BLE_UART_CONFIG_INFO_COLOR

#define NRF_CLI_BLE_UART_CONFIG_INFO_COLOR 0

#endif

 

#ifndef NRF_CLI_BLE_UART_CONFIG_DEBUG_COLOR

#define NRF_CLI_BLE_UART_CONFIG_DEBUG_COLOR 0

#endif

 

#ifndef NRF_CLI_LIBUARTE_CONFIG_LOG_ENABLED

#define NRF_CLI_LIBUARTE_CONFIG_LOG_ENABLED 0

#endif

 

#ifndef NRF_CLI_LIBUARTE_CONFIG_LOG_LEVEL

#define NRF_CLI_LIBUARTE_CONFIG_LOG_LEVEL 3

#endif

 

#ifndef NRF_CLI_LIBUARTE_CONFIG_INFO_COLOR

#define NRF_CLI_LIBUARTE_CONFIG_INFO_COLOR 0

#endif

 

#ifndef NRF_CLI_LIBUARTE_CONFIG_DEBUG_COLOR

#define NRF_CLI_LIBUARTE_CONFIG_DEBUG_COLOR 0

#endif

 

#ifndef NRF_CLI_UART_CONFIG_LOG_ENABLED

#define NRF_CLI_UART_CONFIG_LOG_ENABLED 0

#endif

 

#ifndef NRF_CLI_UART_CONFIG_LOG_LEVEL

#define NRF_CLI_UART_CONFIG_LOG_LEVEL 3

#endif

 

#ifndef NRF_CLI_BLE_UART_CONFIG_INFO_COLOR

#define NRF_CLI_BLE_UART_CONFIG_INFO_COLOR 0

#endif

 

#ifndef NRF_CLI_BLE_UART_CONFIG_DEBUG_COLOR

#define NRF_CLI_BLE_UART_CONFIG_DEBUG_COLOR 0

#endif

 

#ifndef NRF_CLI_LIBUARTE_CONFIG_LOG_ENABLED

#define NRF_CLI_LIBUARTE_CONFIG_LOG_ENABLED 0

#endif

 

#ifndef NRF_CLI_LIBUARTE_CONFIG_LOG_LEVEL

#define NRF_CLI_LIBUARTE_CONFIG_LOG_LEVEL 3

#endif

 

#ifndef NRF_CLI_LIBUARTE_CONFIG_INFO_COLOR

#define NRF_CLI_LIBUARTE_CONFIG_INFO_COLOR 0

#endif

 

#ifndef NRF_CLI_LIBUARTE_CONFIG_DEBUG_COLOR

#define NRF_CLI_LIBUARTE_CONFIG_DEBUG_COLOR 0

#endif

 

#ifndef NRF_CLI_UART_CONFIG_LOG_ENABLED

#define NRF_CLI_UART_CONFIG_LOG_ENABLED 0

#endif

 

#ifndef NRF_CLI_UART_CONFIG_LOG_LEVEL

#define NRF_CLI_UART_CONFIG_LOG_LEVEL 3

#endif

 

#ifndef NRF_QUEUE_CONFIG_LOG_ENABLED

#define NRF_QUEUE_CONFIG_LOG_ENABLED 0

#endif

 

#ifndef NRF_BALLOC_CLI_CMDS

#define NRF_BALLOC_CLI_CMDS 1

#endif

 

 

#ifndef NRF_CLI_ENABLED

#define NRF_CLI_ENABLED 1

#endif

 

#ifndef NRF_CLI_ARGC_MAX

#define NRF_CLI_ARGC_MAX 12

#endif

 

#ifndef NRF_CLI_BUILD_IN_CMDS_ENABLED

#define NRF_CLI_BUILD_IN_CMDS_ENABLED 1

#endif

 

#ifndef NRF_CLI_CMD_BUFF_SIZE

#define NRF_CLI_CMD_BUFF_SIZE 128

#endif

 

#ifndef NRF_CLI_ECHO_STATUS

#define NRF_CLI_ECHO_STATUS 1

#endif

 

#ifndef NRF_CLI_WILDCARD_ENABLED

#define NRF_CLI_WILDCARD_ENABLED 0

#endif

 

#ifndef NRF_CLI_METAKEYS_ENABLED

#define NRF_CLI_METAKEYS_ENABLED 0

#endif

 

#ifndef NRF_CLI_PRINTF_BUFF_SIZE

#define NRF_CLI_PRINTF_BUFF_SIZE 23

#endif

 

#ifndef NRF_CLI_HISTORY_ENABLED

#define NRF_CLI_HISTORY_ENABLED 1

#endif

 

#ifndef NRF_CLI_HISTORY_ELEMENT_SIZE

#define NRF_CLI_HISTORY_ELEMENT_SIZE 32

#endif

 

#ifndef NRF_CLI_HISTORY_ELEMENT_COUNT

#define NRF_CLI_HISTORY_ELEMENT_COUNT 8

#endif

 

#ifndef NRF_CLI_VT100_COLORS_ENABLED

#define NRF_CLI_VT100_COLORS_ENABLED 1

#endif

 

#ifndef NRF_CLI_STATISTICS_ENABLED

#define NRF_CLI_STATISTICS_ENABLED 1

#endif

 

#ifndef NRF_CLI_LOG_BACKEND

#define NRF_CLI_LOG_BACKEND 1

#endif

#ifndef NRF_LOG_CLI_CMDS

#define NRF_LOG_CLI_CMDS 1

#endif

 

#ifndef NRF_CLI_BLE_UART_CONFIG_LOG_ENABLED

#define NRF_CLI_BLE_UART_CONFIG_LOG_ENABLED 0

#endif

 

#ifndef NRF_CLI_BLE_UART_CONFIG_LOG_LEVEL

#define NRF_CLI_BLE_UART_CONFIG_LOG_LEVEL 3

#endif

 

#ifndef NRF_CLI_BLE_UART_CONFIG_INFO_COLOR

#define NRF_CLI_BLE_UART_CONFIG_INFO_COLOR 0

#endif

 

#ifndef NRF_CLI_BLE_UART_CONFIG_DEBUG_COLOR

#define NRF_CLI_BLE_UART_CONFIG_DEBUG_COLOR 0

#endif

 

#ifndef NRF_CLI_LIBUARTE_CONFIG_LOG_ENABLED

#define NRF_CLI_LIBUARTE_CONFIG_LOG_ENABLED 0

#endif

 

#ifndef NRF_CLI_LIBUARTE_CONFIG_LOG_LEVEL

#define NRF_CLI_LIBUARTE_CONFIG_LOG_LEVEL 3

#endif

 

#ifndef NRF_CLI_LIBUARTE_CONFIG_INFO_COLOR

#define NRF_CLI_LIBUARTE_CONFIG_INFO_COLOR 0

#endif

 

#ifndef NRF_CLI_LIBUARTE_CONFIG_DEBUG_COLOR

#define NRF_CLI_LIBUARTE_CONFIG_DEBUG_COLOR 0

#endif

 

#ifndef NRF_CLI_UART_CONFIG_LOG_ENABLED

#define NRF_CLI_UART_CONFIG_LOG_ENABLED 0

#endif

 

#ifndef NRF_CLI_UART_CONFIG_LOG_LEVEL

#define NRF_CLI_UART_CONFIG_LOG_LEVEL 3

#endif

 

#ifndef NRF_CLI_UART_CONFIG_INFO_COLOR

#define NRF_CLI_UART_CONFIG_INFO_COLOR 0

#endif

 

#ifndef NRF_CLI_UART_CONFIG_DEBUG_COLOR

#define NRF_CLI_UART_CONFIG_DEBUG_COLOR 0

#endif

 

#ifndef NRF_CLI_USES_TASK_MANAGER_ENABLED

#define NRF_CLI_USES_TASK_MANAGER_ENABLED 0

#endif

 

#ifndef NRF_CLI_UART_ENABLED

#define NRF_CLI_UART_ENABLED 1

#endif

 

#ifndef NRF_QUEUE_CLI_CMDS

#define NRF_QUEUE_CLI_CMDS 1

#endif

 

#ifndef NRF_QUEUE_CONFIG_LOG_LEVEL

#define NRF_QUEUE_CONFIG_LOG_LEVEL 3

#endif

 

#ifndef NRF_QUEUE_CONFIG_LOG_INIT_FILTER_LEVEL

#define NRF_QUEUE_CONFIG_LOG_INIT_FILTER_LEVEL 3

#endif

 

#ifndef NRF_QUEUE_CONFIG_INFO_COLOR

#define NRF_QUEUE_CONFIG_INFO_COLOR 0

#endif

 

#ifndef NRF_QUEUE_ENABLED

#define NRF_QUEUE_ENABLED 1

#endif

 

#ifndef NRF_QUEUE_CLI_CMDS

#define NRF_QUEUE_CLI_CMDS 1

#endif

 

#ifndef NRF_CLI_LIBUARTE_CONFIG_LOG_ENABLED

#define NRF_CLI_LIBUARTE_CONFIG_LOG_ENABLED 0

#endif

 

#ifndef NRF_CLI_LIBUARTE_CONFIG_LOG_LEVEL

#define NRF_CLI_LIBUARTE_CONFIG_LOG_LEVEL 3

#endif

 

#ifndef NRF_CLI_LIBUARTE_CONFIG_INFO_COLOR

#define NRF_CLI_LIBUARTE_CONFIG_INFO_COLOR 0

#endif

 

#ifndef NRF_CLI_LIBUARTE_CONFIG_DEBUG_COLOR

#define NRF_CLI_LIBUARTE_CONFIG_DEBUG_COLOR 0

#endif

 

#ifndef NRF_CLI_UART_CONFIG_LOG_ENABLED

#define NRF_CLI_UART_CONFIG_LOG_ENABLED 0

#endif

 

#ifndef NRF_CLI_UART_CONFIG_LOG_LEVEL

#define NRF_CLI_UART_CONFIG_LOG_LEVEL 3

#endif

 

#ifndef NRF_CLI_UART_CONFIG_INFO_COLOR

#define NRF_CLI_UART_CONFIG_INFO_COLOR 0

#endif

 

#ifndef NRFX_TWIM_ENABLED

#define NRFX_TWIM_ENABLED 1

#endif

 

#ifndef NRFX_TWIM0_ENABLED

#define NRFX_TWIM0_ENABLED 0

#endif

 

#ifndef NRFX_TWIM1_ENABLED

#define NRFX_TWIM1_ENABLED 0

#endif

 

#ifndef NRFX_TWIM_DEFAULT_CONFIG_FREQUENCY

#define NRFX_TWIM_DEFAULT_CONFIG_FREQUENCY 26738688

#endif

 

#ifndef NRFX_TWIM_DEFAULT_CONFIG_HOLD_BUS_UNINIT

#define NRFX_TWIM_DEFAULT_CONFIG_HOLD_BUS_UNINIT 0

#endif

 

#ifndef NRFX_TWIM_DEFAULT_CONFIG_IRQ_PRIORITY

#define NRFX_TWIM_DEFAULT_CONFIG_IRQ_PRIORITY 6

#endif

 

#ifndef NRFX_TWIM_CONFIG_LOG_ENABLED

#define NRFX_TWIM_CONFIG_LOG_ENABLED 0

#endif

 

#ifndef NRFX_TWIM_CONFIG_LOG_LEVEL

#define NRFX_TWIM_CONFIG_LOG_LEVEL 3

#endif

 

#ifndef NRFX_TWIM_CONFIG_INFO_COLOR

#define NRFX_TWIM_CONFIG_INFO_COLOR 0

#endif

 

#ifndef NRFX_TWIM_CONFIG_DEBUG_COLOR

#define NRFX_TWIM_CONFIG_DEBUG_COLOR 0

#endif

 

#ifndef NRFX_TWIM_NRF52_ANOMALY_109_WORKAROUND_ENABLED

#define NRFX_TWIM_NRF52_ANOMALY_109_WORKAROUND_ENABLED 0

#endif

 

#ifndef NRFX_TWI_ENABLED

#define NRFX_TWI_ENABLED 1

#endif

 

#ifndef NRFX_TWI0_ENABLED

#define NRFX_TWI0_ENABLED 0

#endif

 

#ifndef NRFX_TWI1_ENABLED

#define NRFX_TWI1_ENABLED 0

#endif

 

#ifndef NRFX_TWI_DEFAULT_CONFIG_FREQUENCY

#define NRFX_TWI_DEFAULT_CONFIG_FREQUENCY 26738688

#endif

 

#ifndef NRFX_TWI_DEFAULT_CONFIG_HOLD_BUS_UNINIT

#define NRFX_TWI_DEFAULT_CONFIG_HOLD_BUS_UNINIT 0

#endif

 

#ifndef NRFX_TWI_DEFAULT_CONFIG_IRQ_PRIORITY

#define NRFX_TWI_DEFAULT_CONFIG_IRQ_PRIORITY 6

#endif

 

#ifndef NRFX_TWI_CONFIG_LOG_ENABLED

#define NRFX_TWI_CONFIG_LOG_ENABLED 0

#endif

 

#ifndef NRFX_TWI_CONFIG_LOG_LEVEL

#define NRFX_TWI_CONFIG_LOG_LEVEL 3

#endif

 

#ifndef NRFX_TWI_CONFIG_INFO_COLOR

#define NRFX_TWI_CONFIG_INFO_COLOR 0

#endif

 

#ifndef NRFX_TWI_CONFIG_DEBUG_COLOR

#define NRFX_TWI_CONFIG_DEBUG_COLOR 0

#endif

 

#ifndef TWI_ENABLED

#define TWI_ENABLED 1

#endif

 

#ifndef TWI_DEFAULT_CONFIG_FREQUENCY

#define TWI_DEFAULT_CONFIG_FREQUENCY 26738688

#endif

 

#ifndef TWI_DEFAULT_CONFIG_CLR_BUS_INIT

#define TWI_DEFAULT_CONFIG_CLR_BUS_INIT 0

#endif

 

#ifndef TWI_DEFAULT_CONFIG_HOLD_BUS_UNINIT

#define TWI_DEFAULT_CONFIG_HOLD_BUS_UNINIT 0

#endif

 

#ifndef TWI_DEFAULT_CONFIG_IRQ_PRIORITY

#define TWI_DEFAULT_CONFIG_IRQ_PRIORITY 6

#endif

 

#ifndef TWI0_ENABLED

#define TWI0_ENABLED 1

#endif

 

#ifndef TWI0_USE_EASY_DMA

#define TWI0_USE_EASY_DMA 1

#endif

 

#ifndef TWI1_ENABLED

#define TWI1_ENABLED 1

#endif

 

#ifndef TWI1_USE_EASY_DMA

#define TWI1_USE_EASY_DMA 1

#endif

 

#ifndef TWIM_NRF52_ANOMALY_109_WORKAROUND_ENABLED

#define TWIM_NRF52_ANOMALY_109_WORKAROUND_ENABLED 0

#endif

 

#ifndef TWIS_CONFIG_LOG_ENABLED

#define TWIS_CONFIG_LOG_ENABLED 0

#endif

 

#ifndef TWIS_CONFIG_LOG_LEVEL

#define TWIS_CONFIG_LOG_LEVEL 3

#endif

 

#ifndef TWIS_CONFIG_INFO_COLOR

#define TWIS_CONFIG_INFO_COLOR 0

#endif

 

#ifndef TWIS_CONFIG_DEBUG_COLOR

#define TWIS_CONFIG_DEBUG_COLOR 0

#endif

 

#ifndef TWI_CONFIG_LOG_ENABLED

#define TWI_CONFIG_LOG_ENABLED 0

#endif

 

#ifndef TWI_CONFIG_LOG_LEVEL

#define TWI_CONFIG_LOG_LEVEL 3

#endif

 

#ifndef TWI_ENABLED

#define TWI_ENABLED 0

#endif 

 

#ifndef TWI0_ENABLED

#define TWI0_ENABLED 0

#endif

 

#ifndef TWI_CONFIG_LOG_ENABLED

#define TWI_CONFIG_LOG_ENABLED 0

#endif

 

#ifndef TWI_CONFIG_LOG_LEVEL

#define TWI_CONFIG_LOG_LEVEL 3

#endif

 

#ifndef TWI_CONFIG_INFO_COLOR

#define TWI_CONFIG_INFO_COLOR 0

#endif

 

#ifndef TWI_CONFIG_DEBUG_COLOR

#define TWI_CONFIG_DEBUG_COLOR 0

#endif

 

#ifndef TWI_CONFIG_INFO_COLOR

#define TWI_CONFIG_INFO_COLOR 0

#endif

 

#ifndef TWI_CONFIG_DEBUG_COLOR

#define TWI_CONFIG_DEBUG_COLOR 0

#endif

 

#ifndef NRF_CLI_UART_CONFIG_DEBUG_COLOR

#define NRF_CLI_UART_CONFIG_DEBUG_COLOR 0

#endif

 

#ifndef NRF_SECTION_ITER_ENABLED

#define NRF_SECTION_ITER_ENABLED 1

#endif

 

#ifndef NRF_SORTLIST_ENABLED

#define NRF_SORTLIST_ENABLED 1

#endif

 

#ifndef NRF_STRERROR_ENABLED

#define NRF_STRERROR_ENABLED 1

#endif

 

#ifndef NRF_QUEUE_CONFIG_DEBUG_COLOR

#define NRF_QUEUE_CONFIG_DEBUG_COLOR 0

#endif

 

#ifndef NRF_CLI_UART_CONFIG_INFO_COLOR

#define NRF_CLI_UART_CONFIG_INFO_COLOR 0

#endif

 

#ifndef NRF_CLI_UART_CONFIG_DEBUG_COLOR

#define NRF_CLI_UART_CONFIG_DEBUG_COLOR 0

#endif

 

#ifndef NRF_CLI_UART_ENABLED

#define NRF_CLI_UART_ENABLED 1

#endif

 

#ifndef FDS_CRC_CHECK_ON_READ

#define FDS_CRC_CHECK_ON_READ 1

#endif

 

#ifndef FDS_CRC_CHECK_ON_WRITE

#define FDS_CRC_CHECK_ON_WRITE 0

#endif

 

#ifndef NRF_BALLOC_CLI_CMDS

#define NRF_BALLOC_CLI_CMDS 1

#endif

 

#ifndef NRF_CLI_UART_ENABLED

#define NRF_CLI_UART_ENABLED 1

#endif

[quote userid="75734" url="~/f/nordic-q-a/78157/rtt-not-appearing-in-modified-ble_app_uart-example/323257#323257"]What libraries have you added exactly,[/quote]

Board support:

Ses_startup_nrf_common.s

Application:

cli.c

Drivers:

nrf_drv_twi.c

nrfx_twim.c

nrfx_twi.c

Libraries:

Nrf_queue.c

Nrf_queue.h

Nrf_fstorage_sd.c

Nrf_fstorage.c

Nrf_cli_uart.c

Nrf_cli.c

Fds.c

Crc16.c

[quote userid="75734" url="~/f/nordic-q-a/78157/rtt-not-appearing-in-modified-ble_app_uart-example/323257#323257"]Does your modified project run as expected without logging?[/quote]

Yes. I have been using putty to debug over UART but we are changing to a custom PCB and will be needing RTT in the future.

Thanks for the help so far!

RE: RTT not appearing in modified ble_app_uart example

Simonr — Wed, 04 Aug 2021 09:09:40 GMT

[quote user="jake11212"]I gave this a try and was able to get RTT viewer 7.0 working for the default ble_app_uart but not with my modified version.[/quote]

Okay, so one of the modifications you've done is hindering the RTT backend to log for some reason. What pins are your application using for TWI communication? What libraries have you added exactly, and what changes did you make to the sdk_config.h file exactly?

Does your modified project run as expected without logging?

Best regards,

Simon

RE: RTT not appearing in modified ble_app_uart example

jake11212 — Tue, 03 Aug 2021 20:33:12 GMT

[quote userid="75734" url="~/f/nordic-q-a/78157/rtt-not-appearing-in-modified-ble_app_uart-example/323099#323099"]Can you confirm that NRF_LOG_ENABLED and NRF_LOG_BACKEND_RTT_ENABLED are set to 1 in your project's sdk_config.h header file? [/quote]

Yep, double checked these and both are set to 1.

[quote userid="75734" url="~/f/nordic-q-a/78157/rtt-not-appearing-in-modified-ble_app_uart-example/323099#323099"]NRF_FPRINTF_FLAG_AUTOMATIC_CR_ON_LF_ENABLED set to 1 as well?[/quote]

Yes, it was set to 1. I tried setting it to 0 but this didn't fix the issue.

[quote userid="75734" url="~/f/nordic-q-a/78157/rtt-not-appearing-in-modified-ble_app_uart-example/323099#323099"]You can alternatively try using the RTT Viewer to see if that works[/quote]

I gave this a try and was able to get RTT viewer 7.0 working for the default ble_app_uart but not with my modified version.

[quote userid="75734" url="~/f/nordic-q-a/78157/rtt-not-appearing-in-modified-ble_app_uart-example/323099#323099"]Can you also confirm whether or not you're working on a development kit or a custom board?[/quote]

This is all done on the nRF52DK.

RE: RTT not appearing in modified ble_app_uart example

Simonr — Tue, 03 Aug 2021 12:34:20 GMT

Can you confirm that NRF_LOG_ENABLED and NRF_LOG_BACKEND_RTT_ENABLED are set to 1 in your project's sdk_config.h header file? Is NRF_FPRINTF_FLAG_AUTOMATIC_CR_ON_LF_ENABLED set to 1 as well? If so, try setting it to 0, as SEGGER Embedded Studios for some reason doesn't like this define. You can alternatively try using the RTT Viewer to see if that works. Can you also confirm whether or not you're working on a development kit or a custom board?

Best regards,

Simon