Skip to content

Conversation

@miguelafsilva5
Copy link
Member

@miguelafsilva5 miguelafsilva5 commented Aug 29, 2025

PR Description

This PR introduces the initial support for Infineon Tricore architectures.
This PR requires #218 to support boot from flash with a non-unified memory model.
The current state of this port supports baremetal and freeRTOS guests in single or multicore setups. At the moment, each guest is given an unique ID, and each core only executes one guest.

The following list shows what is missing:

  • DMA virtualization/isolation
  • History re-write and commit clean up
  • CI integration
  • bao-demos integration

@miguelafsilva5 miguelafsilva5 force-pushed the feat/tricore branch 2 times, most recently from f92535a to 57284c8 Compare September 1, 2025 14:05
@danielRep danielRep force-pushed the feat/non-unified-mem branch from 9ad59e5 to 474545c Compare September 1, 2025 15:56
@miguelafsilva5 miguelafsilva5 force-pushed the feat/tricore branch 2 times, most recently from b9e1caf to 7da4f29 Compare September 3, 2025 12:51
@danielRep danielRep force-pushed the feat/non-unified-mem branch 2 times, most recently from 829c219 to 61b37aa Compare September 3, 2025 13:06
@miguelafsilva5 miguelafsilva5 force-pushed the feat/tricore branch 4 times, most recently from 0e5ea75 to bf61453 Compare September 8, 2025 09:37
@danielRep danielRep force-pushed the feat/non-unified-mem branch 2 times, most recently from 674ffd5 to 3d1e91a Compare September 8, 2025 11:01
@danielRep danielRep force-pushed the feat/non-unified-mem branch from 3d1e91a to 53e6ea9 Compare September 9, 2025 13:40
@miguelafsilva5 miguelafsilva5 force-pushed the feat/tricore branch 2 times, most recently from 44a2cbb to 3d6619f Compare September 10, 2025 10:18
Base automatically changed from feat/non-unified-mem to main September 10, 2025 13:32
@miguelafsilva5 miguelafsilva5 force-pushed the feat/tricore branch 6 times, most recently from bffccac to 661df87 Compare September 15, 2025 13:43
@miguelafsilva5 miguelafsilva5 force-pushed the feat/tricore branch 2 times, most recently from ba20ef7 to f2194f5 Compare September 24, 2025 10:31
@miguelafsilva5 miguelafsilva5 force-pushed the feat/tricore branch 2 times, most recently from b062b10 to aae7e86 Compare October 3, 2025 13:36
@miguelafsilva5 miguelafsilva5 force-pushed the feat/tricore branch 6 times, most recently from b6524b4 to c23100e Compare October 22, 2025 14:29
The cpu variable from struct addr_space was not being used
throughout the code.

Signed-off-by: Miguel Silva <[email protected]>
The mmio regions present in the platform description are to be mapped
accessible for all address spaces.

Signed-off-by: Miguel Silva <[email protected]>
Each architecture needs to implement their access control function.
This function is called during the dev init for vms, and is executed instead
of the original memory mapping.

Signed-off-by: Miguel Silva <[email protected]>
miguelafsilva5 and others added 5 commits October 27, 2025 14:54
All address spaces now have their unique ID. The only exception is the
hypervisor itself that always has ID=0.

Signed-off-by: Miguel Silva <[email protected]>
Refactored slightly the root pool bitmap base to improve clarity of code
Removed the passing of load_addr as argument since it can be defined as
a global variable in each arch boot file.

Signed-off-by: Daniel Oliveira <[email protected]>
Signed-off-by: Miguel Silva <[email protected]>
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