• State Not Answered
  • Replies 5 replies
  • Subscribers 25 subscribers
  • Views 152 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 288756
Options

NCS why LOG_ERR() no output?

user106325

Hello 

NCS1.9.99,VSCode,nRF5340DK,

printk() output ok.

why LOG_ERR() no output?

#
# Copyright (c) 2022 Nordic Semiconductor ASA
#
# SPDX-License-Identifier: LicenseRef-Nordic-5-Clause
#

# General
CONFIG_DEBUG=y
CONFIG_DEBUG_INFO=y
CONFIG_ASSERT=y
CONFIG_STACK_USAGE=y
CONFIG_THREAD_RUNTIME_STATS=y
CONFIG_STACK_SENTINEL=y
CONFIG_INIT_STACKS=y

# Uart driver
CONFIG_SERIAL=y

# Logging
CONFIG_LOG=y
CONFIG_LOG_MODE_DEFERRED=y
CONFIG_LOG_BACKEND_UART=y
CONFIG_LOG_BACKEND_RTT=n
CONFIG_LOG_DEFAULT_LEVEL=4
CONFIG_NEWLIB_LIBC_FLOAT_PRINTF=y
CONFIG_LOG_TAG_MAX_LEN=2
CONFIG_LOG_TAG_DEFAULT="--"

# Console related defines
CONFIG_CONSOLE=y
CONFIG_RTT_CONSOLE=y
CONFIG_UART_CONSOLE=y

# Shell related defines
CONFIG_SHELL=y
CONFIG_KERNEL_SHELL=y
CONFIG_USE_SEGGER_RTT=y
## Disable logs on RTT
CONFIG_SHELL_RTT_INIT_LOG_LEVEL_NONE=y
CONFIG_SHELL_BACKEND_RTT=y
CONFIG_SHELL_BACKEND_SERIAL=n
CONFIG_SHELL_VT100_COLORS=y
CONFIG_SHELL_STACK_SIZE=1024
CONFIG_SHELL_CMD_BUFF_SIZE=128
## Reduce shell memory usage
CONFIG_SHELL_WILDCARD=n
CONFIG_SHELL_HELP_ON_WRONG_ARGUMENT_COUNT=n
CONFIG_SHELL_STATS=n
CONFIG_SHELL_CMDS=n
CONFIG_SHELL_HISTORY=y

# Turn off default shell commands
CONFIG_I2C_SHELL=n
CONFIG_HWINFO_SHELL=n
CONFIG_CLOCK_CONTROL_NRF_SHELL=n
CONFIG_FLASH_SHELL=n
CONFIG_DEVICE_SHELL=n

# Enable BT debug
CONFIG_BT_DEBUG_LOG=y
CONFIG_BT_LOG_LEVEL_WRN=y

   

Best regards

Parents Reply Children
  • 0 in reply to user2116

    Hi,

    thanks for reply,

    i'm uart terminal,printk() show ok,

    but LOG_ERR()  LOG_DBG() no output,

    and RTT no output.

    In fact, I just only want to use uart.

      

    Best regards

  • 0 in reply to user106325

    Hi 

    You are using deferred logging, which means that the log messages will not be printed right away, rather they will be buffered in RAM and printed later on from a separate thread. 

    printk() on the other hand will print to the UART immediately. 

    Looking at your SerialTool screenshot it does look like there are some debug messages printed on lines 3, 4 and 5. 
    Could you share the entire log printout, by copying the text rather than taking a screenshot?

    Best regards
    Torbjørn

  • 0 in reply to user2116

    Hi,

    the main codes:

    void main(void)
{
	int ret;

	printk("nRF5340 APP core started\n");
	LOG_ERR("nRF5340 APP core started...\n");

	while(true){k_msleep(1000);}
}

    the log:

    *** Booting Zephyr OS build v2.7.99-ncs1-2212-g038a2de883a0  ***
nRF5340 APP core started
-- [00:00:00.437,408] <dbg> nrf5340_audio_dk_nrf5340_cpuapp: core_config: Setting gpiote latency to low power
-- [00:00:00.437,469] <dbg> nrf5340_audio_dk_nrf5340_cpuapp: remoteproc_mgr_boot: Network MCU released.
-- [00:00:00.445,770] <err> main: nRF5340 APP core started...


     

    i add "nrf5340_audio_dk_nrf5340_cpuapp" to nRF5340-DK,  i've not change codes or config

    (except:CONFIG_TRANSPORT_BIS=y  CONFIG_AUDIO_SOURCE_I2S=y and main where(true{}))   

      

    thanks

    Best regards

  • 0 in reply to user106325

    Hi

    I don't see any problems here. 

    Line 5 of your log is showing the LOG_ERR message, no?

    Best regards
    Torbjørn

Related
Terms of service