| Age | Commit message (Collapse) | Author |
|---|
|
|
|
* bsp/stm32: Separate stm32mp1 hal drivers
* bsp/stm32: change stm32mp1 .config
|
|
|
|
|
|
|
|
fixed the abnormal operation of ci files
|
|
|
|
|
|
|
|
error.
|
|
|
|
修复手动生成编译的error
|
|
|
|
* [component/lwp]add annotation for lwp elf.
* Update components/lwp/lwp_elf.c
Co-authored-by: Copilot <[email protected]>
---------
Co-authored-by: Copilot <[email protected]>
|
|
When run kconfig, see warnings as followings:
Kconfig:5: warning: BSP_ROOT has 'option env="BSP_DIR"',...
Kconfig:10: warning: RTT_ROOT has 'option env="RTT_DIR"',...
Kconfig:15: warning: PKGS_ROOT has 'option env="PKGS_DIR"',...
...
warning: the choice symbol PKG_USING_ZLIB_LATEST_VERSION (...)
is selected by the following symbols, but select/imply has no
effect on choice symbols
- BSP_ROOTFS_TYPE_CROMFS (defined at Kconfig:41)
warning: the value '0xF00000000' is invalid for C908_PLIC_PHY_ADDR...
Trying to cleanup Kconfig and re-run menuconfig to update.
Signed-off-by: Chen Wang <[email protected]>
|
|
|
|
* [hc32] Add the ev_hc32f4a8_lqfp176 board and modify some bsp drivers.
|
|
RT_WLAN_EVT_SCAN_REPORT (#10237)
|
|
|
|
|
|
该问题由5b3320624da5149fc21c2d3e1f321d855e3d0dfe引入，导致工具链编译时加上了 -std=gnu99,其他架构是否出问题暂时未知
|
|
The original method of packaging and burning kernel
depends on installing the K230 RTOS SDK. It is quite
cumbersome. Now the relevant logic is extracted and
a small tool rttpkgtool is created to package the
rtthread.bin.
Considering that rttpkgtool still needs to compile
opensbi when packaging k230, which means that a
separate cross-toolchain needs to be installed.
Therefore, in order not to affect the CI operation,
the current packaging logic is not integrated into
POST_ACTION in rtconfig.py, but requires kernel
developers to run the build script separately for
packaging.
Signed-off-by: Chen Wang <[email protected]>
|
|
[action/ci] add qemu-pre-build-and-post-build for RT_SMART build
|
|
|
|
|
|
|
|
|
|
|
|
Signed-off-by: Chen Wang <[email protected]>
|
|
Signed-off-by: Chen Wang <[email protected]>
|
|
The original code used immediate values directly when it
came to memory layout, which was not a good programming
habit.
Now we use macros and try to be compatible with SDK
configuration values in the SDK compilation environment.
The main changes are to clean up board.h, and extract
some memory layout constants to define a new header
file mem_layout.h.
Also update KERNEL_VADDR_START to the default value for
Smart, so we can use it as base to calculate other mapping
address.
Signed-off-by: Chen Wang <[email protected]>
|
|
For linker script, use constant macro defined from
rtconfig.h, not immediate value.
Also cleanup the link_statksize.lds, it is also not
needed when using new mechanism.
Signed-off-by: Chen Wang <[email protected]>
|
|
KERNEL_VADDR_START changed to 0xffffffc000020000.
__STACKSIZE__ changed to 65536.
Signed-off-by: Chen Wang <[email protected]>
|
|
Signed-off-by: Wang Chen <[email protected]>
|
|
Some changes to support canmv board, such as:
- Address constant, some may need be set as configuration later.
- link script
- build script
Signed-off-by: Wang Chen <[email protected]>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
([#10176](https://github.com/hydevcode/rt-thread/issues/10176))
|
|
Regarding link script, some memory offsets and sizes are different
between the standard version and the smart version (such as
"__STACKSIZE__", kernel start address, kernel memory size, etc.).
Original solution is replacing link scripts and use INCLUDE,
which is relatively complicated.
This improvement uses macros to replace constants in the link
script. The preprocessing mechanism provided by gcc is used
to dynamically replace constant values during the build process.
In addition, the kernel load address (the corresponding
KERNEL_VADDR_START for smart) was originally configured as
0xFFFFFFC000200000, which is default value of riscv with
kernelmap enabled (0xffffffc000000000) plus offset to skip over
bootloader (0x200000). This caused a trouble: due to
default bsp configuration is for smart, if we switched to the
standard version and build, and then switched back to the smart
version, the value of KERNEL_VADDR_START will be default back to
0xffffffc000000000, which is different from the original configuration
value, resulting in the need to manually reconfigure it, which
is easy to forget and cause problems.
The current solution is to use the default value
0xffffffc000000000 in the configuration. Add offset to the code
and link script when using it.
This patch update the default .config and rtconfig.h for cv18xx_riscv.
Signed-off-by: Chen Wang <[email protected]>
|
