Uart Device from zephyr get eroor

RE: Uart Device from zephyr get eroor

Naeem Maroof — Mon, 12 Aug 2024 09:25:35 GMT

Hi Chuck,

As the nature of query has changed (from uart/overlay to classes/c++), I would request you to create a newer ticket for that. This would help cataloging different queries and would help others using DevZone as well.

Thank you.

RE: Uart Device from zephyr get eroor

ChuckRui — Tue, 06 Aug 2024 09:36:19 GMT

Now I can run it successfully, maybe because of some configuration reasons that the program does not work properly.

[quote userid="119245" url="~/f/nordic-q-a/113288/uart-device-from-zephyr-get-eroor/495186"]We have official migration guides here: Migration Guides NCS[/quote]

According to The migration guide you provided, I see a reference to "The event_types.h header file was removed" (see below).

I wonder if V2.6.1 uses the Nrf class to implement the task scheduling mechanism instead of the event queue mechanism used in V2.3.0.

V2.3.0

V2.6.1

If I need to add custom events, do I need to implement them based on the Nrf class, or can I go back to the previous AppEvent class？

Best regards，

Chuck

RE: Uart Device from zephyr get eroor

Naeem Maroof — Mon, 05 Aug 2024 15:44:28 GMT

I could not compile your project

Are you compiling for 52840? Are you using mcumanager?

Please share how are you configuring the build.

Also, at compile time, some configs would not get set.

Please see if there are any conflicts and the final value of configurations in the ./bild/zephyr/.config file

RE: Uart Device from zephyr get eroor

ChuckRui — Fri, 26 Jul 2024 08:23:13 GMT

devzone.nordicsemi.com/.../light_5F00_bulb_5F00_1.zip

Could you help me find out what the problem is?
Because I have tested many times, the same configuration can be successfully compiled on NCSV2.3.0, and then RTT can display Zephyr logs, but NCSV2.6.1 can be successfully compiled on the prerequisite, RTT after burning no reaction

RE: Uart Device from zephyr get eroor

ChuckRui — Wed, 24 Jul 2024 09:45:27 GMT

I also tried to direct the replication/v2.6.1 NRF/samples/matter/light_bulb project copy, and then modify the PRJ. Conf file,
And add the following configuration
# Reduce application size
CONFIG_USE_SEGGER_RTT=y
CONFIG_RTT_CONSOLE=y
CONFIG_UART_CONSOLE=n
#CONFIG_LOG_BACKEND_RTT=y
CONFIG_LOG_BACKEND_UART=n
Then burn and compile, it seems that RTT still does not react

RE: Uart Device from zephyr get eroor

ChuckRui — Wed, 24 Jul 2024 09:19:23 GMT

Hi，

I have another problem, I want to implement the migration to V2.6.1, but I use the same configuration in prj.conf (as shown below), on V2.3.0, I can see zephyr logs through RTT, but when I open RTT on V2.6.1, there is no log display, I read the link you gave me. The migration guidelines seem to have no RTT related aspects, I wonder why?

V2.3.0 prj.conf

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

# Enable CHIP
CONFIG_CHIP=y
CONFIG_CHIP_PROJECT_CONFIG="src/chip_project_config.h"
# 32773 == 0x8005 (example lighting-app)
CONFIG_CHIP_DEVICE_PRODUCT_ID=257
CONFIG_STD_CPP14=y

# Enable CHIP pairing automatically on application start.
CONFIG_CHIP_ENABLE_PAIRING_AUTOSTART=y

# Add support for LEDs and buttons on Nordic development kits
CONFIG_DK_LIBRARY=y
CONFIG_PWM=y

# Bluetooth Low Energy configuration
CONFIG_BT_DEVICE_NAME="MatterLight"

# Other settings
CONFIG_THREAD_NAME=y
CONFIG_MPU_STACK_GUARD=y
CONFIG_RESET_ON_FATAL_ERROR=n
CONFIG_CHIP_LIB_SHELL=y

# Reduce application size
#CONFIG_USE_SEGGER_RTT=n


# Changes the clock soucrce to the internal RC oscillator
CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y
CONFIG_CLOCK_CONTROL_NRF_K32SRC_XTAL=n

# enable uart driver
CONFIG_SERIAL=y
CONFIG_UART_ASYNC_API=y
CONFIG_UART_INTERRUPT_DRIVEN=y
CONFIG_SHELL_PROMPT_UART=""


# Enable RTT
CONFIG_USE_SEGGER_RTT=y
CONFIG_RTT_CONSOLE=y
CONFIG_UART_CONSOLE=n
#CONFIG_LOG_BACKEND_RTT=y
CONFIG_LOG_BACKEND_UART=n


CONFIG_LOG_DEFAULT_LEVEL=2
CONFIG_MATTER_LOG_LEVEL_INF=y
CONFIG_ASSERT_VERBOSE=n

# Enable OTA
CONFIG_CHIP_DFU_OVER_BT_SMP=y
CONFIG_BOOTLOADER_MCUBOOT=y

# Set Sofeware Version
CONFIG_CHIP_DEVICE_SOFTWARE_VERSION=1
CONFIG_CHIP_DEVICE_SOFTWARE_VERSION_STRING="1.0"
CONFIG_CHIP_DEVICE_HARDWARE_VERSION=1
#CONFIG_MCUBOOT_IMAGE_VERSION="0.0.1+2"

# Enable Factory Data
CONFIG_CHIP_FACTORY_DATA=y
#CONFIG_CHIP_FACTORY_DATA_BUILD=y

CONFIG_SPEED_OPTIMIZATIONS=y

V2.6.1 prj.conf

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

# Enable CHIP
CONFIG_CHIP=y
CONFIG_CHIP_PROJECT_CONFIG="src/chip_project_config.h"
# 32773 == 0x8005 (example lighting-app)
CONFIG_CHIP_DEVICE_PRODUCT_ID=257
CONFIG_STD_CPP17=y

# Enable CHIP pairing automatically on application start.
CONFIG_CHIP_ENABLE_PAIRING_AUTOSTART=y

# Add support for LEDs and buttons on Nordic development kits
CONFIG_DK_LIBRARY=y
CONFIG_PWM=y

# Bluetooth Low Energy configuration
CONFIG_BT_DEVICE_NAME="MatterLight"

# Other settings
CONFIG_THREAD_NAME=y
CONFIG_MPU_STACK_GUARD=y
CONFIG_RESET_ON_FATAL_ERROR=n
CONFIG_CHIP_LIB_SHELL=y

# Reduce application size
#CONFIG_USE_SEGGER_RTT=n


# Changes the clock soucrce to the internal RC oscillator
CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y
CONFIG_CLOCK_CONTROL_NRF_K32SRC_XTAL=n

# enable uart driver
CONFIG_SERIAL=y
CONFIG_UART_ASYNC_API=y
CONFIG_UART_INTERRUPT_DRIVEN=y
CONFIG_SHELL_PROMPT_UART=""


# Enable RTT
CONFIG_USE_SEGGER_RTT=y
CONFIG_RTT_CONSOLE=y
CONFIG_UART_CONSOLE=n
#CONFIG_LOG_BACKEND_RTT=y
CONFIG_LOG_BACKEND_UART=n


CONFIG_LOG_DEFAULT_LEVEL=2
CONFIG_MATTER_LOG_LEVEL_INF=y
CONFIG_ASSERT_VERBOSE=n

# Enable OTA
CONFIG_CHIP_DFU_OVER_BT_SMP=y
CONFIG_BOOTLOADER_MCUBOOT=y

# Set Sofeware Version
#CONFIG_CHIP_DEVICE_SOFTWARE_VERSION=1
#CONFIG_CHIP_DEVICE_SOFTWARE_VERSION_STRING="1.0"
#CONFIG_CHIP_DEVICE_HARDWARE_VERSION=1
#CONFIG_MCUBOOT_IMAGE_VERSION="0.0.1+2"

# Enable Factory Data
CONFIG_CHIP_FACTORY_DATA=y
#CONFIG_CHIP_FACTORY_DATA_BUILD=y

CONFIG_SPEED_OPTIMIZATIONS=y

The only difference is that V2.6.1 and V2.3.0 use the CPP versions of V17 and V14
CONFIG_STD_CPP17=y
CONFIG_STD_CPP14=y

V2.3.0

It's worth mentioning that I haven't burned the factory data yet.

V2.6.1

Best regards,

Chuck

RE: Uart Device from zephyr get eroor

Naeem Maroof — Tue, 23 Jul 2024 10:54:21 GMT

Hi,

We have official migration guides here: Migration Guides NCS

/best regards,

Naeem

RE: Uart Device from zephyr get eroor

ChuckRui — Tue, 23 Jul 2024 06:50:08 GMT

OMG，I was careless.Thank you~

By the way,Is there a migration guide? I want to migrate from V2.3.0 to the NCS version V2.7.0 that supports Matter1.3 authentication and find a lot of changes in the code, including the task mechanism. Is app_event not used in the new version of NCS? Includes the following files in the path also changed the "replication/v2.7.0 / NRF/samples/matter/common/", how can faster to migrate.

Best regards,

Chuck

RE: Uart Device from zephyr get eroor

Naeem Maroof — Mon, 22 Jul 2024 14:10:19 GMT

You have disabled uart1 in the overlay: