arch/tricore: add support for tc4xx series chips and boards by zhangyu-duck · Pull Request #18391 · apache/nuttx

zhangyu-duck · 2026-02-13T08:11:26Z

Note: Please adhere to Contributing Guidelines.

Summary

Two main updates:

Uses the official Infineon ILLD repository instead of a private repository.
Adds support for tc4xx series chips and boards

Impact

support tc4xx chip

Testing

Both cmake and makefile methods can compile tc3xx/tc4xx.
pass ostest, basic functions are normal

nsh> hello
Hello, World!! tc4 ostest
nsh>

i give tc4 ostest.log in attach files
tc4_ostest.log

anchao · 2026-02-13T08:38:47Z

arch/tricore/src/illd/tc3xx/Configurations/Ifx_Cfg_Ssw.c

+/**********************************************************************************************************************
+ * \file Ifx_Cfg_Ssw.c
+ * \brief Configuration file for the Startup Software
+ * \copyright Copyright (C) Infineon Technologies AG 2019


Can Ifx_*.c use the iLLD implementation?I'm not sure if introducing Infineon's license is feasible, or could we submit the differences as a patch file?

i will check it

We feel that these files may still be changed in the future, and it's not convenient to upload them as a patch list.
i have rewrite them and only keep something we need. and replace with SPDX license.

jerpelea

please document all non Apache license file to
https://github.com/apache/nuttx/blob/master/LICENSE

jerpelea

please add SPDX license identifiers to all files not only Apache licensed ones

zhangyu-duck · 2026-02-13T11:45:37Z

please add SPDX license identifiers to all files not only Apache licensed ones

ok，thanks, i have updata code

zhangyu-duck · 2026-02-13T11:45:54Z

please add SPDX license identifiers to all files not only Apache licensed ones

get it, thanks

acassis

@zhangyu-duck please update the Documentation https://nuttx.apache.org/docs/latest/platforms/tricore/index.html to include these new chips.

Unfortunately our Documentation is very non-standardized, some Documentation arch are very good, others are very primitive (let say not helpful). So, I suggest you to use https://nuttx.apache.org/docs/latest/platforms/arm/imxrt/index.html as a good reference.

arch/tricore/include/tc3xx/irq.h

arch/tricore/src/illd/tc4xx/Libraries/doc/iLLD-TC4xx-Releasenotes.pdf

linguini1

I guess since this modifies the TC3xx logic as well, could you please include an OSTest log from a tc3 board? The tc4 log looks good.

arch/tricore/src/illd/tc4xx/Libraries/doc/iLLD-TC4xx-UM.chm

arch/tricore/src/tc3xx/Kconfig

arch/tricore/src/tc4da/CMakeLists.txt

arch/tricore/src/tc4da/Make.defs

linguini1 · 2026-02-13T18:01:51Z

arch/tricore/src/tc4xx/Kconfig

+	select UART0_SERIALDRIVER
+	select ARCH_HAVE_SERIAL_TERMIOS
+
+config CPU_COREID


TC4XX_CPU_COREID

It's may better to use the same name, so that the common upper-level code of TC3/TC4 doesn't need to be modified.

I would suggest moving the config option to a higher level tricore Kconfig then, one that's common to both.

arch/tricore/src/tc4xx/tc4xx_libc.c

arch/tricore/src/tc4xx/tc4xx_dummy.c

linguini1 · 2026-02-13T18:10:10Z

Also I won't block the PR about this since I have pretty much no familiarity with the tricore architecture, but is it necessary to use the SDK? It seems like this PR needs to include a lot of workarounds for quirks with the SDK (like the libc stubs and patch files). Is it at all possible to avoid using the SDK directly? I know a few other archs in NuttX use this approach (hence why I don't think it's a dealbreaker or anything), but I also know the preferred method is to avoid using vendor SDKs/HALs entirely if possible.

perform type conversion to eliminate warnings Signed-off-by: zhangyuan29 <zhangyuan29@xiaomi.com>

add arch.h in irq.h Signed-off-by: zhangyuan29 <zhangyuan29@xiaomi.com>

tc3 and tc4 use common irq.h Signed-off-by: zhangyu117 <zhangyu117@xiaomi.com>

support tc4evb board, so need adjust some Kconfig Signed-off-by: zhangyu117 <zhangyu117@xiaomi.com>

rename tc3xx.cmake to chip.cmake Signed-off-by: zhangyuan29 <zhangyuan29@xiaomi.com>

Let the linker script decide the location of the heap. Signed-off-by: zhangyuan29 <zhangyuan29@xiaomi.com>

zhangyu-duck · 2026-02-14T03:32:31Z

Also I won't block the PR about this since I have pretty much no familiarity with the tricore architecture, but is it necessary to use the SDK? It seems like this PR needs to include a lot of workarounds for quirks with the SDK (like the libc stubs and patch files). Is it at all possible to avoid using the SDK directly? I know a few other archs in NuttX use this approach (hence why I don't think it's a dealbreaker or anything), but I also know the preferred method is to avoid using vendor SDKs/HALs entirely if possible.

Sorry, Infineon's Tricore chip heavily relies on ILLD's library functions, making it difficult to render effectively. The original TC3 series chips also did this before.

zhangyu-duck · 2026-02-14T03:35:57Z

@zhangyu-duck please update the Documentation https://nuttx.apache.org/docs/latest/platforms/tricore/index.html to include these new chips.

Unfortunately our Documentation is very non-standardized, some Documentation arch are very good, others are very primitive (let say not helpful). So, I suggest you to use https://nuttx.apache.org/docs/latest/platforms/arm/imxrt/index.html as a good reference.

ok, get it

zhangyu-duck · 2026-02-14T03:41:03Z

@zhangyu-duck please update the Documentation https://nuttx.apache.org/docs/latest/platforms/tricore/index.html to include these new chips.

Unfortunately our Documentation is very non-standardized, some Documentation arch are very good, others are very primitive (let say not helpful). So, I suggest you to use https://nuttx.apache.org/docs/latest/platforms/arm/imxrt/index.html as a good reference.

add new chip named tc4xx and board tc4evb Signed-off-by: zhangyu117 <zhangyu117@xiaomi.com>

acassis · 2026-02-14T11:47:45Z

@simbit18 do you know if LVGL v9.2 files were removed from their site?

====================================================================================
Configuration/Tool: raspberrypi-4b/lvgl
2026-02-14 04:31:13
------------------------------------------------------------------------------------
  Cleaning...
  Configuring...
  Building NuttX...
[v9.2.1.zip]
  End-of-central-directory signature not found.  Either this file is not
  a zipfile, or it constitutes one disk of a multi-part archive.  In the
  latter case the central directory and zipfile comment will be found on
  the last disk(s) of this archive.
unzip:  cannot find zipfile directory in one of v9.2.1.zip or
        v9.2.1.zip.zip, and cannot find v9.2.1.zip.ZIP, period.
make[3]: *** [Makefile:77: lvgl] Error 9
make[3]: Target 'context' not remade because of errors.
make[2]: *** [Makefile:57: /github/workspace/sources/apps/graphics/lvgl_context] Error 2
make[2]: Target 'context_all' not remade because of errors.
make[1]: *** [Makefile:187: context] Error 2
make: *** [tools/Unix.mk:458: /github/workspace/sources/apps/.context] Error 2
make: Target 'all' not remade because of errors.
/github/workspace/sources/nuttx/tools/testbuild.sh: line 385: /github/workspace/sources/nuttx/../nuttx/nuttx.manifest: No such file or directory
  [1/1] Normalize raspberrypi-4b/lvgl

We need to create our own mirror at github.com/nuttx/

parthitce · 2026-02-14T12:14:58Z

Also I won't block the PR about this since I have pretty much no familiarity with the tricore architecture, but is it necessary to use the SDK? It seems like this PR needs to include a lot of workarounds for quirks with the SDK (like the libc stubs and patch files). Is it at all possible to avoid using the SDK directly? I know a few other archs in NuttX use this approach (hence why I don't think it's a dealbreaker or anything), but I also know the preferred method is to avoid using vendor SDKs/HALs entirely if possible.

On this note, we are already in the phase of developing iLLD independent Tricore support. Although this isn't mature yet, plans are tracked here 1. Also you can find development tree with various branches 2 named dev/infineon/tricore-xxyy, for example working variant of UART 3. Our main goal is get to upstream NuttX during the course of this year.

linguini1 · 2026-02-14T14:46:37Z

On this note, we are already in the phase of developing iLLD independent Tricore support. Although this isn't mature yet, plans are tracked here 1. Also you can find development tree with various branches 2 named dev/infineon/tricore-xxyy, for example working variant of UART 3. Our main goal is get to upstream NuttX during the course of this year.

Woah awesome news! Thanks!

simbit18 · 2026-02-15T12:45:55Z

@simbit18 do you know if LVGL v9.2 files were removed from their site?

Hi @acassis There were temporary issues downloading the package.

acassis · 2026-02-15T13:01:14Z

@simbit18 do you know if LVGL v9.2 files were removed from their site?

Hi @acassis There were temporary issues downloading the package.

Thank you @simbit18

parthitce · 2026-02-17T15:57:21Z

@zhangyu-duck are these changes tested with Tasking only or OSS GCC can also be used?

zhangyu-duck requested review from Donny9, Ouss4, acassis, anchao, jerpelea, masayuki2009, raiden00pl, simbit18 and xiaoxiang781216 as code owners February 13, 2026 08:11

github-actions bot added Arch: tricore Issues related to the TriCore architecture from Infineon Board: tricore Size: XL The size of the change in this PR is very large. Consider breaking down the PR into smaller pieces. labels Feb 13, 2026

zhangyu-duck force-pushed the tricore_tc4_board branch from 7682822 to 31c2ea0 Compare February 13, 2026 08:33

zhangyu-duck requested review from davids5 and johannes-nivus as code owners February 13, 2026 08:33

github-actions bot added the Area: Tooling label Feb 13, 2026

anchao requested changes Feb 13, 2026

View reviewed changes

zhangyu-duck force-pushed the tricore_tc4_board branch 2 times, most recently from 745ed4d to 4edecbe Compare February 13, 2026 08:49

jerpelea changed the title ~~Tricore tc4 board~~ arch/tricore: add support for tc4xx series chips and boards Feb 13, 2026

jerpelea requested changes Feb 13, 2026

View reviewed changes

zhangyu-duck force-pushed the tricore_tc4_board branch from 4edecbe to d2a6f48 Compare February 13, 2026 11:42

acassis requested changes Feb 13, 2026

View reviewed changes

linguini1 reviewed Feb 13, 2026

View reviewed changes

arch/tricore/include/tc3xx/irq.h Outdated Show resolved Hide resolved

linguini1 reviewed Feb 13, 2026

View reviewed changes

arch/tricore/src/illd/tc4xx/Libraries/doc/iLLD-TC4xx-Releasenotes.pdf Outdated Show resolved Hide resolved

linguini1 requested changes Feb 13, 2026

View reviewed changes

zyfeier and others added 6 commits February 14, 2026 11:13

arch/tricore: fixed cxx build issue

5e03d0d

perform type conversion to eliminate warnings Signed-off-by: zhangyuan29 <zhangyuan29@xiaomi.com>

arch/tricore: include arch.h in irq.h

fcda650

add arch.h in irq.h Signed-off-by: zhangyuan29 <zhangyuan29@xiaomi.com>

arch/tricore: adjust arch-related irq.h

6736ede

tc3 and tc4 use common irq.h Signed-off-by: zhangyu117 <zhangyu117@xiaomi.com>

arch/tricore: Adjust the related structures of arch and chip.

af0d723

support tc4evb board, so need adjust some Kconfig Signed-off-by: zhangyu117 <zhangyu117@xiaomi.com>

tricore/cmake: change tc3xx.cmake to chip.cmake

6bbc914

rename tc3xx.cmake to chip.cmake Signed-off-by: zhangyuan29 <zhangyuan29@xiaomi.com>

arch/tricore: change heap symbol to support multi config

39a9f2f

Let the linker script decide the location of the heap. Signed-off-by: zhangyuan29 <zhangyuan29@xiaomi.com>

zhangyu-duck requested a review from linguini1 February 14, 2026 03:30

zhangyu-duck requested a review from acassis February 14, 2026 03:32

zhangyu-duck closed this Feb 14, 2026

zhangyu-duck reopened this Feb 14, 2026

zhangyu-duck force-pushed the tricore_tc4_board branch from d2a6f48 to c194f89 Compare February 14, 2026 03:42

github-actions bot added the Area: Documentation Improvements or additions to documentation label Feb 14, 2026

arch/tricore: support tc4evb board

c080e06

add new chip named tc4xx and board tc4evb Signed-off-by: zhangyu117 <zhangyu117@xiaomi.com>

zhangyu-duck force-pushed the tricore_tc4_board branch from c194f89 to c080e06 Compare February 14, 2026 03:46

jerpelea approved these changes Feb 17, 2026

View reviewed changes

acassis approved these changes Feb 17, 2026

View reviewed changes

Conversation

zhangyu-duck commented Feb 13, 2026

Summary

Impact

Testing

Uh oh!

anchao Feb 13, 2026

Choose a reason for hiding this comment

Uh oh!

zhangyu-duck Feb 13, 2026

Choose a reason for hiding this comment

Uh oh!

zhangyu-duck Feb 13, 2026

Choose a reason for hiding this comment

Uh oh!

jerpelea left a comment

Choose a reason for hiding this comment

Uh oh!

jerpelea left a comment

Choose a reason for hiding this comment

Uh oh!

zhangyu-duck commented Feb 13, 2026

Uh oh!

zhangyu-duck commented Feb 13, 2026

Uh oh!

acassis left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

linguini1 left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

linguini1 Feb 13, 2026

Choose a reason for hiding this comment

Uh oh!

zhangyu-duck Feb 14, 2026

Choose a reason for hiding this comment

Uh oh!

linguini1 Feb 14, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

linguini1 commented Feb 13, 2026

Uh oh!

zhangyu-duck commented Feb 14, 2026

Uh oh!

zhangyu-duck commented Feb 14, 2026

Uh oh!

zhangyu-duck commented Feb 14, 2026

Uh oh!

acassis commented Feb 14, 2026

Uh oh!

parthitce commented Feb 14, 2026

Uh oh!

linguini1 commented Feb 14, 2026

Uh oh!

simbit18 commented Feb 15, 2026

Uh oh!

acassis commented Feb 15, 2026

Uh oh!

parthitce commented Feb 17, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

9 participants