-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
Cannot see both bootloader and application RTT output #53544
Comments
#53569 and zephyrproject-rtos/segger#17 should fix the issue. |
Tested with both patches manually applied on nRF Connect SDK v2.0.2 and works as expected. Would be great to see in a release. Not relevant for me, but I think this could be a regression for some users. If both |
Thank you for your comment. |
This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time. |
Hi, I would like to remove the stale label for this issue. |
This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time. |
Any luck? |
This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time. |
@giansta I'll assume the issue has been fixed. Feel free to reopen if necessary. |
|
Hi @jhedberg |
This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time. |
Still seeing this. I suspected that the buffers were in different locations for mcuboot and the app. 2 years old already. I mean, there are older bugs 🤷🏼♂️ |
This bug affects stm, or really any device that uses a JLink. Given that there is a possible fix for it, it would be nice to get it in soon-ish. |
When attaching the SEGGER J-Link RTT Viewer to a nRF52 based target, in most cases only the logs from application are visible and not the logs from MCUboot, more seldom only logs from MCUboot.
Expected behaviour: both logs from MCUboot and from application are expected to be visible, like using serial or SWO.
Found solution:
The issue is due to the fact that the viewer or debugger looks in the target memory for RTT control block and buffer, searching for the "SEGGER RTT" signature. As MCUboot and application have them at different addresses, it either finds one or the other. The solution would be having them at same address for both and avoiding the application to re-initialize them if already initialized by MCUboot.
Confirmation and fixing hints can be found i.e. in https://devzone.nordicsemi.com/f/nordic-q-a/30310/easy-way-to-merge-bootloader-and-application-rtt-output
In the Nordic SDK this patch works well.
In Zephyr CONFIG_SEGGER_RTT_SECTION_DTCM defines a different section (
.dtcm_data
) for RTT control block and buffer, yet it seems that:orphan section .dtcm_data
warning is given by the linker;SEGGER_RTT.c
module needs patches to initialize properly the variables in `.dtcm_data' section and to not initialize them if already done by MCUboot.I could verify that the two fixing above solve the issue and both logs are finally visible.
I didn't find any other open issue or PR mentioning it. I'll propose new PRs for the above changes, unless a better solution exists.
Impact: difficult to debug and diagnose proprietary DFU.
Environment:
The text was updated successfully, but these errors were encountered: