rt-thread.git/bsp/cvitek/cv18xx_aarch64/board, branch copilot/remove-vbus-code-implementation

bsp: cvitek: Canonically rename some macro definitions

2024-08-20T01:52:18Z

Analysis: Some macro definition names are not standardized and lack prefixes. Solution: Add BSP_ prefix to GPIO_IRQ_BASE SYS_GPIO_IRQ_BASE PLIC_PHY_ADDR TIMER_CLK_FREQ UART_IRQ_BASE I2C_IRQ_BASE. Signed-off-by: Shicheng Chu <1468559561@qq.com>

bsp: cvitek: fix cv18xx_aarch64 mnt init blocking

2024-07-25T13:35:48Z

The aarch64 core of duo on the master cannot enter the console interface. It can only print the RT flag and hold it. Analysis: The latest commit that can work is ae6a328 ("Add psoc62, 61 config"). This phenomenon will occur after adding 754c59a ("[Feature] DFS mount auto by kernel parameters"). The specific reason is that when aarch bsp enables the device tree, the current u-boot will pass in bootargs, which contains "root=/dev/mmcblk0p2 rootwait rw", which means that the kernel is required to wait until the rootfs in /dev/mmcblk0p2 loaded successfully. However, the current aarch64 bsp default does not implement sdmmc device mounting, causing the kernel file system mounting module (rootfs_mnt_init() of components/drivers/core/mnt.c) to enter an infinite loop waiting. Solution: At present, we do not plan to modify the startup parameters of u-boot. The temporary solution adopted is to create a pseudo /dev/mmcblk0p2 device during the board initialization process, and then cancel the pseudo device after mnt is completed. This allows the kernel boot to be completed successfully. Signed-off-by: Shicheng Chu <1468559561@qq.com> Reviewed-by: Chen Wang

Merge pull request #9221 from Z8MAN8/cvitek_arm_uart

2024-07-25T10:58:34Z

bsp: cvitek: add missing soc type for aarch64

bsp: cviteK: update board init for aarch64

2024-07-24T11:44:52Z

When compiling CV18xx_arch64, have a error: can not find "rt_fdt_commit_memregion_early" Analysis: b785ef9 ("[libcpu][aarch64]memory setup using memblock ") no longer support "rt_fdt_commit_memregion_early", become use "rt_memblock_reserve_memory" Solution: Refer to the bsp/qemu-virt64-aarch64/drivers/board.c delete "rt_fdt_commit_memregion_early" Signed-off-by: Shicheng Chu <1468559561@qq.com> Reviewed-by: Chen Wang

bsp: cvitek: add missing soc type for aarch64

2024-07-24T11:29:46Z

When compiling CV18xx_arch64, there are the following errors: 1. missing soc type for aarch64 2. uart device objects defined but not used Analysis: a63c07f ("bsp: cvitek: new design for pinmux") and 114e143("bsp:cvitek: add pinmux for uart"), CV18xx_arch64 is not considered. Solution: Refer to the cv18xx_riscv format to add the corresponding chip type SOC_Type_SG2002, as well as the corresponding macro for the serial port pins and interrupts Signed-off-by: Shicheng Chu <1468559561@qq.com> Reviewed-by: Chen Wang

[bsp][cvitek] Initialize the Milk-V Duo 256M using the device tree (#8841)

2024-04-23T15:09:45Z

Initialize the board using the device tree

[bsp][cvitek] 在Milk-V Duo 256M开发板中支持ARM核运行RT-Thread标准版和Smart版内核 (#8800)

2024-04-16T01:49:41Z

* Supports ARM core of Milk-V Duo 256M development board * add fip.bin(arm)