-
Notifications
You must be signed in to change notification settings - Fork 6.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
debug: tracing: Add Segger RTT linker section options #53569
debug: tracing: Add Segger RTT linker section options #53569
Conversation
5bc4d75
to
1ed0a56
Compare
Expected to fix #53544 with zephyrproject-rtos/segger#17 in Segger repo |
1ed0a56
to
f16648e
Compare
@nordic-krch Seems OK to me, but mind having a look since you maintain the Segger integration? |
If you mean that the approval depends on the approval of the segger PR, I totally agree :-) |
f16648e
to
dc86be9
Compare
The following west manifest projects have been modified in this Pull Request:
Note: This message is automatically posted and updated by the Manifest GitHub Action. |
32093e9
to
9c52b9e
Compare
9c52b9e
to
59be1f1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you also update west so that it points to the changes in segger repo?
drivers/debug/Kconfig.rtt
Outdated
@@ -74,6 +74,9 @@ config SEGGER_RTT_SECTION_NONE | |||
config SEGGER_RTT_SECTION_DTCM | |||
bool "Place RTT data in the DTCM linker section" | |||
|
|||
config SEGGER_RTT_SECTION_FIXED_ADDR | |||
bool "Place RTT data in specific linker section with fixed address" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
don't we want default y
? If bootloader is not used then it has no difference and when bootload is used then probably most users would like to get logs from bootloader and application.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agree, done.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we could depend on the fact that we use Cortex-M here (since it's not supported by linker scripts of other architectures)?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've added a if CPU_CORTEX_M
, thanks.
59be1f1
to
c2e9d2d
Compare
@giansta needs rebase |
@ioannisg @bbolen @microbuilder @povergoing @nordic-krch @MarekPieta since this is a very old PR and gets merge conflicts can you review and approve if you find it acceptable so that the module update can be merged and this is able to be merged without encountering another merge conflict? |
Allows optionally placing Segger RTT data either in a specific linker section that is located at RAM start, or in a specific linker section defined by a memory region in DTS, as third and fourth alternative to the DTCM section or the default data section. This is useful to share the fixed address for different programs, typically bootloader and application, and have seamless logging. Signed-off-by: Giancarlo Stasi <[email protected]>
Use recommended write API that internally locks RTT usage and checks if the RTTcontrol block initialization is done. Signed-off-by: Giancarlo Stasi <[email protected]>
Allows RTT inizialization function to either init Cntrol Block always or initialize only after checking it it's not already initialized by another program, typically by a bootloader. Signed-off-by: Giancarlo Stasi <[email protected]>
a876d07
to
42f1b2c
Compare
@nordic-krch would be good to try to get this and the associated Segger PR in for 3.7? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Definite improvement
@giansta thanks so much for your patience. |
Thanks @carlescufi! Anyway, this PR requires even zephyrproject-rtos/segger#17 |
Hi, after merging this PR not working tests: on nrf52840dk/nrf52840.
bisect shows that commit: 711ed08 Edit: added issue #77058 |
@gchwier I think it might be because zephyrproject-rtos/segger#17 still hasn't been merged? cc @carlescufi |
@kartben I've used that PR and looks that it does not help, still the same issue. |
Kconfig options for RTT control block initialization and linker section were added in zephyrproject-rtos#53569, however the Zephyr west.yml was not updated to incorporate the Segger repository changes to make use of the new Kconfig options. This fixes that. Signed-off-by: Bryce Wilkins <[email protected]>
Kconfig options for RTT control block initialization and linker section were added in zephyrproject-rtos#53569, however the Zephyr west.yml was not updated to incorporate the Segger repository changes to make use of the new Kconfig options. This fixes that. Signed-off-by: Bryce Wilkins <[email protected]>
Kconfig options for RTT control block initialization and linker section were added in zephyrproject-rtos#53569, however the Zephyr west.yml was not updated to incorporate the Segger repository changes to make use of the new Kconfig options. This fixes that. Signed-off-by: Bryce Wilkins <[email protected]>
Kconfig options for RTT control block initialization and linker section were added in zephyrproject-rtos#53569, however the Zephyr west.yml was not updated to incorporate the Segger repository changes to make use of the new Kconfig options. This fixes that. Signed-off-by: Bryce Wilkins <[email protected]>
Kconfig options for RTT control block initialization and linker section were added in zephyrproject-rtos#53569, however the Zephyr west.yml was not updated to incorporate the Segger repository changes to make use of the new Kconfig options. This fixes that. Signed-off-by: Bryce Wilkins <[email protected]>
Kconfig options for RTT control block initialization and linker section were added in #53569, however the Zephyr west.yml was not updated to incorporate the Segger repository changes to make use of the new Kconfig options. This fixes that. Signed-off-by: Bryce Wilkins <[email protected]>
Allows optionally placing Segger RTT data either in a specific
linker section that is located at RAM start, or in a specific linker
section defined by a memory region in DTS, as third and fourth
alternative to the DTCM section or the default data section.
This is useful to share the fixed address for different programs,
typically bootloader and application, and have seamless logging.
Signed-off-by: Giancarlo Stasi [email protected]
fixes #53544