Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs for tricore #3819

Merged
merged 6 commits into from
Aug 28, 2024
Merged

docs for tricore #3819

merged 6 commits into from
Aug 28, 2024

Conversation

memsharded
Copy link
Member

@memsharded memsharded added this to the 2.7.0 milestone Aug 27, 2024
Copy link

@photex photex left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Couple of comments. I'm now checking on the devkit linker script for the TC377TX and whether its enough to provide that to link the test elf.

examples/cross_build/tricore.rst Outdated Show resolved Hide resolved
tools.build:compiler_executables={"c":"tricore-elf-gcc","cpp":"tricore-elf-g++"}


This assumes the compiler is installed in the system path, and its executables are called ``tricore-elf-gcc`` and ``tricore-elf-g++``.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

An open source gcc toolchain is available on GitHub: https://github.com/EEESlab/tricore-gcc-toolchain-11.3.0

Is that helpful to mention here?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not necessarily at this stage, but if we built a full working example (which is the final goal), then it would be perfect to use such open source toolchain

@memsharded
Copy link
Member Author

I have a quick question, are there other architectures besides the ones you added to settings.yml that starts with tcXXX, and you just added the most common ones? Or did you add all tricore known architectures?

.. note::

- This support is new and experimental. Please create a ticket in https://github.com/conan-io/conan/issues for any feedback or issues
- Linking applications (like if using ``conan new cmake_exe``) requires a specific linker script, definition of entry-points, etc.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are some example linker scripts available on Github https://github.com/Infineon/AURIX_code_examples/blob/master/code_examples/iLLD_TC37x_ADS_SCR_Blinky_LED_LK_1/Lcf_Gnuc_Tricore_Tc.lsl

These scripts will setup gcc exception handling tables, but iLLD provides key entry points and startup code that are expected by these linker scripts.

You can see this in the included iLLD source in the same example:

@photex
Copy link

photex commented Aug 27, 2024

I have a quick question, are there other architectures besides the ones you added to settings.yml that starts with tcXXX, and you just added the most common ones? Or did you add all tricore known architectures?

These are all of the architectures currently supported by tricore-gcc and are the current production tricore ISAs. There are older variants, they would only be supported by proprietary compilers as far as I'm aware.

The latest chips will be the TC4x series, and I'm not aware of any hardware even being available yet.

@memsharded memsharded closed this Aug 27, 2024
@memsharded memsharded reopened this Aug 27, 2024
@memsharded memsharded merged commit 91b662d into conan-io:develop2 Aug 28, 2024
2 checks passed
@memsharded memsharded deleted the feature/tricore branch August 28, 2024 14:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants