zhangyu-duck opened a new pull request, #21305: URL: https://github.com/apache/nuttx/pull/21305
*Note: Please adhere to [Contributing Guidelines](https://github.com/apache/nuttx/blob/master/CONTRIBUTING.md).* ## Summary Use the chip family (tc3xx/tc4xx) as ARCH_CHIP instead of the single part name (tc397/tc4da): - make ARCH_CHIP_TC3XX/TC4XX selectable, drop ARCH_CHIP_TC397/TC4DA and select the concrete part (TC39X/TC4DX) via a choice in the family Kconfig - merge src/{tc397,tc4da} into src/{tc3xx,tc4xx}, move include/{tc397,tc4da} to include/{tc3xx,tc4xx}, and drop the ARCH_SUBDIR indirection from CMake and Makefile - move boards/tricore/{tc397,tc4da} and the related documentation to {tc3xx,tc4xx}, update defconfigs and board Kconfig - add CONFIG_CPU_CLOCK_FREQUENCY to replace the iLLD IFX_CFG_CPU_CLOCK_FREQUENCY in up_perf_init() - move the TASKING fake libc_fpu stubs to common/tricore_libc.c and drop the empty libos dummy library These changes are kept in one commit since they have to land together to keep the tree buildable. This is the first PR of the TriCore series: this PR -> #21150 -> trap p2 -> #21151 -> irq pr2 -> irq pr3 -> irq pr4. ## Impact TriCore architecture and boards only (arch/tricore, boards/tricore, Documentation). Board directories and Kconfig symbols are renamed (ARCH_CHIP_TC397/TC4DA -> ARCH_CHIP_TC3XX/TC4XX), out-of-tree TriCore boards need to update their defconfig. No impact on other architectures. ## Testing Built triboard_tc4x9_com:nsh (TC4xx, cmake) and a2g-tc397-5v-tft:nsh (TC3xx, both make and cmake) with tricore-elf-gcc on Ubuntu host. Each commit passes checkpatch and builds on its own. Tested on both TC4xx (TC4x9) and TC3xx (TC397) boards: system boots normally and ostest passes. ``` nsh> uname -a NuttX 13.1.0 c49abcfca40 Oct 31 2026 21:23:37 tricore triboard_tc4x9_com nsh> ostest ... ostest_main: Exiting with status 0 ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
