- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
on my CYT4BF device i have an Autosar Application running only on CM7 core. For Bootcore CM0+ there is no application available. How do i manage the correct startup and "running" behaviour for the CM0+ core?
Thanks,
Martin
Solved! Go to Solution.
- Labels:
-
TRAVEO™ T2G
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Please go through the first question in the following document to check if your system call is working fine - https://community.infineon.com/t5/Knowledge-Base-Articles/Traveo-II-Automotive-Body-Controller-FAQ-B...
- You can also go through '37. Nonvolatile Memory Programming' chapter in the Architecture TRM to learn more about system calls.
- As already mentioned in my previous response, the following application note has the detailed startup code for CM0+ core - https://www.infineon.com/dgdl/Infineon-AN220118_GETTING_STARTED_WITH_TRAVEO_II_FAMILY_MCUS-Applicati...
- You can also go through the actual startup file present in the SDL to understand the steps better. You can download the latest version of the SDL from here - https://www.infineon.com/cms/en/product/microcontroller/32-bit-traveo-t2g-arm-cortex-microcontroller...
- Since this is an MCAL related question, I request you to contact your local sales representative or FAE to get more support.
Regards.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Martin,
You can find the CPU startup sequence for CYT4B in section 3.2.3 of the following application note - https://www.infineon.com/dgdl/Infineon-AN220118_GETTING_STARTED_WITH_TRAVEO_II_FAMILY_MCUS-Applicati...
Let me know if this answers your question.
Regards.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
In my autosar application for CM7 the ECU is hanging at function: Fls_InvokeFMAPI
The Elektrobit support answered to this issue:
"Fls driver can be run from CM7 itself. Actual programming is initiated through system calls which can be executed only from CM0+. Fls driver uses IPC to invoke the system calls in CM0+.
So whenever you use Fls in the application, core CM0+ needs to run because FLS will use system calls from that core.
If CM0+ is not started and runing, the Fls driver hangs in Fls_InvokeFMAPI same as customer reported. "
My conclusion is that the CM7 uses IPC messages for invoking system calls on CM0+. The root cause of this issue potentially is on CM0+ core. How can i check if CM0+ is running correctly?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Please go through the first question in the following document to check if your system call is working fine - https://community.infineon.com/t5/Knowledge-Base-Articles/Traveo-II-Automotive-Body-Controller-FAQ-B...
- You can also go through '37. Nonvolatile Memory Programming' chapter in the Architecture TRM to learn more about system calls.
- As already mentioned in my previous response, the following application note has the detailed startup code for CM0+ core - https://www.infineon.com/dgdl/Infineon-AN220118_GETTING_STARTED_WITH_TRAVEO_II_FAMILY_MCUS-Applicati...
- You can also go through the actual startup file present in the SDL to understand the steps better. You can download the latest version of the SDL from here - https://www.infineon.com/cms/en/product/microcontroller/32-bit-traveo-t2g-arm-cortex-microcontroller...
- Since this is an MCAL related question, I request you to contact your local sales representative or FAE to get more support.
Regards.