-
Notifications
You must be signed in to change notification settings - Fork 6.9k
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
Develop/ram console option known addr buf #68452
Develop/ram console option known addr buf #68452
Conversation
cf3e9e0
to
18d8ba5
Compare
This update fixed some check failures. |
18d8ba5
to
8a64dfb
Compare
6c7ea74
6c7ea74
to
7ae1799
Compare
Updated to fix LONG_LINE check warning. |
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.
This will conflict with the HWMv2 so we will block this till the collab branch merges
Okay, will rebase then. |
84716af
to
8671935
Compare
@kartben can you review the changes to your change request |
Earlier comments regarding documentation have been addressed
8671935
to
cbf420b
Compare
In arm64 linker script, create a memory region and section for each device tree node with compatible string "zephyr,memory-region". Signed-off-by: Hou Zhiqiang <[email protected]>
It has been added in the arm64 common linker script, so also update the one of mimx9 SoCs. Signed-off-by: Hou Zhiqiang <[email protected]>
Leave one byte from the CONFIG_RAM_CONSOLE_BUFFER_SIZE to ensure the NULL-termination. Signed-off-by: Hou Zhiqiang <[email protected]>
Currently, the ram_console buffer is defined as a global var, its address is determined during the building and may be changed when code update. This is not a problem if the ram_console is just used in debug purpose. While in the heterogeneous SoCs, there can be multiple MPU Cores and several MCU cores, it can run multiple OS/bare-metal instances on these cores, but the UART ports may be not enough, so the ram_console can be leveraged. To make it easy to use, it's better make the console buffer fixed and predefined. This patch adds a option to link the console buffer to a given section, through the "zephyr,memory-region" device tree node, then the address can be known from the device tree node and easy to check from other cores running Linux/U-Boot. To use this option, the chosen property 'zephyr,ram-console' must be added, the following is a example: chosen { zephyr,ram-console = &ram_console; }; ram_console: memory@93d00000 { compatible = "zephyr,memory-region"; reg = <0x93d00000 DT_SIZE_K(4)>; zephyr,memory-region = "RAM_CONSOLE"; }; Signed-off-by: Hou Zhiqiang <[email protected]>
The ram-console snippet disabled UART console and enabled the RAM console with the option link the RAM console buffer to a dedicate section in a new added memory-region. Signed-off-by: Hou Zhiqiang <[email protected]>
cbf420b
to
47d631a
Compare
@carlocaione could you please refresh your +1? thanks! |
This PR added an option for RAM console driver to locate the console buffer to a predefined memory region, so that the RAM console can be used easily, and also added an example on imx8mmevk.