rt-thread.git/bsp/cvitek, branch copilot/fix-fpu-initialization-issue

feat:clang format ignore migration

2025-10-28T06:13:56Z

[format][version]: synchronize bsp version configuration

2025-10-23T14:06:51Z

bsp/cvitek: Increase the value of RT_NAME_MAX

2025-09-25T05:03:00Z

Otherwise report runtime error: [E/kernel.obj] Object name sys workq exceeds RT_NAME_MAX=8, consider increasing RT_NAME_MAX. (obj_name_len <= RT_NAME_MAX - 1) assertion failed at function:rt_object_allocate, line number:520 Increase the value of RT_NAME_MAX to 16 for c906B. The value of RT_NAME_MAX for BSP of C906L and ARM core already meet the requirement of more than 8. Signed-off-by: Chen Wang

Fix the crash of the SPI driver under the smart mode

2025-07-04T12:51:04Z

Signed-off-by: flyingcys flyingcys@163.com

format: update all series of BSP configuration items (#10406)

2025-06-17T07:42:49Z

bsp: cvitek: riscv: use marco for linker script

2025-04-22T01:48:53Z

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

bsp: cvitek: use rttpkgtool for aarch64

2025-03-29T00:55:40Z

Fixed #9968 1.Using scripts in rttpkgtool to make firmware. 2.Deleted duplicate prebuild files. 3.Modify README.md Signed-off-by: YunZhan Huang <1583267844@qq.com>

bsp: cvitek: fix build warnings for spi

2025-03-24T12:38:08Z

See https://github.com/RT-Thread/rt-thread/issues/10138. Signed-off-by: Chen Wang

bsp: cvitek: add howto configure pinmux in README (#10142)

2025-03-24T07:47:57Z

Add description on how to configure pinmux in menuconfig for cvitek products. Add myself to maintainer list in README.md. Signed-off-by: Chen Wang

[bsp][cvitek] fix spi driver build error

2025-03-24T01:24:11Z

Build error: 'struct _device_spi' has no member named 'base_addr' Analyze: the name should be dws.regs Solution: change base_addr to dws.regs Signed-off-by: zdtyuiop4444