LOG ISSUE IN NRF CONNECT SDK

[Embel_Tech]

      I am currently working on interfacing an external flash memory IC (Winbond W25FV series) with the Nordic nRF52832 on my custom board, using the nRF Connect SDK.

      However, I am facing an issue with the log output — the LOG_INF() messages are not printing as expected, even though I have enabled logging in my prj.conf file.

     I will share the following for your review and input:

• My prj.conf project configuration

• The device tree source (DTS) or overlay file

          Please review the configuration and provide your suggestions or corrections to help resolve the logging issue.

   

Fullscreen prj.file.txt Download

# Logging
CONFIG_LOG=y
CONFIG_USE_SEGGER_RTT=y
CONFIG_LOG_BACKEND_RTT=y
# Enable GPIO and SPI
CONFIG_GPIO=y
CONFIG_SPI=y
CONFIG_PRINTK=y
CONFIG_CONSOLE=y

Fullscreen dts.file.txt Download

/dts-v1/;
#include <nordic/nrf52832_qfaa.dtsi>
#include "My_custom_board-pinctrl.dtsi"

/ {
	model = "Custom Board auto generated by nRF Connect for VS Code";
	compatible = "embel_technologies,My-custom-board";

	chosen {
		zephyr,sram = &sram0;
		zephyr,flash = &flash0;
		zephyr,code-partition = &slot0_partition;
	};
};

&flash0 {
	partitions {
		compatible = "fixed-partitions";
		#address-cells = <1>;
		#size-cells = <1>;

		boot_partition: partition@0 {
			label = "mcuboot";
			reg = <0x00000000 DT_SIZE_K(48)>;
		};

		slot0_partition: partition@c000 {
			label = "image-0";
			reg = <0x0000c000 DT_SIZE_K(220)>;
		};

		slot1_partition: partition@43000 {
			label = "image-1";
			reg = <0x00043000 DT_SIZE_K(220)>;
		};

		storage_partition: partition@7a000 {
			label = "storage";
			reg = <0x0007a000 DT_SIZE_K(24)>;
		};
	};
};

&spi1 {
    compatible = "nordic,nrf-spi";
    status = "okay";
    cs-gpios = <&gpio0 26 GPIO_ACTIVE_LOW>;  // CS on P0.26

    pinctrl-0 = <&spi1_default>;
    pinctrl-1 = <&spi1_sleep>;
    pinctrl-names = "default", "sleep";
};
&pinctrl {
	spi1_default: spi1_default {
		group1 {
			psels = <NRF_PSEL(SPIM_SCK, 0, 30)>,
				<NRF_PSEL(SPIM_MOSI, 0, 29)>,
				<NRF_PSEL(SPIM_MISO, 0, 27)>;
		};
	};

	spi1_sleep: spi1_sleep {
		group1 {
			psels = <NRF_PSEL(SPIM_SCK, 0, 30)>,
				<NRF_PSEL(SPIM_MOSI, 0, 29)>,
				<NRF_PSEL(SPIM_MISO, 0, 27)>;
			low-power-enable;
		};
	};
};&gpiote {
    status = "okay";
};

&gpio0 {
    status = "okay";
    gpiote-instance = <&gpiote>;
};

  

[Hung Bui]

Hi, 

Have you managed to print log on RTT in any example ? I don't think the external flash memory IC  has anything to do with RTT logging. 
Please try to test with the attached helloworld sample. 

hello_world_RTT.zip

[Embel_Tech]

Hello,

  I will check logging for the code provided by you, Also

"I have tested the beacon code, and it is logging without any issues."

[Hung Bui]

Please double check that you don't have 

CONFIG_NCS_SAMPLES_DEFAULTS=y 

as it set CONFIG_LOG_DEFAULT_MINIMAL=y which doesn't allow RTT logging. 

[Embel_Tech]

      Hello, I verified that the "Hello World" example runs successfully on the DK. However, when I run it on the custom board, no logs are printed. 

   Here is Configuration for custom board:

 

CONFIG_USE_SEGGER_RTT=y

CONFIG_LOG_BACKEND_RTT=y 

CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y

CONFIG_LOG=y

[Hung Bui]

Hi, 
Please check if you can run anything on the custom board ? blink an LED ? UART logging ? 
Just want to check if the board actually working. 

Have you tried to flash the same firmware built for the DK on the custom board ?