Apr 08, 2020
02:18 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Apr 08, 2020
02:18 AM
Hello,
We are using Tricore TC275TF, we are using __syscall Tin 1 to generate the TRAP. But after certain time when we call syscall it is not generating the TRAP.
Could you please share the more information in which condition Syscall will not get triggered?
Regards,
Bhagyashri
We are using Tricore TC275TF, we are using __syscall Tin 1 to generate the TRAP. But after certain time when we call syscall it is not generating the TRAP.
Could you please share the more information in which condition Syscall will not get triggered?
Regards,
Bhagyashri
- Tags:
- IFX
- sycall trap issue
3 Replies
Apr 08, 2020
04:41 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Apr 08, 2020
04:41 AM
There is no way to disable a trap.
Make sure BTV didn't get changed, and make sure you're looking at the right CPU - e.g., CPU1_BTV for CPU1.
Also make sure you've got enough context save areas.
Make sure BTV didn't get changed, and make sure you're looking at the right CPU - e.g., CPU1_BTV for CPU1.
Also make sure you've got enough context save areas.
Apr 09, 2020
02:16 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Apr 09, 2020
02:16 AM
Hello,
Thank you for your reply. The exception and all interrupts are getting executed correctly till 3-4 hrs later we observed _Syscall interrupt is not getting triggered.
We are using _Syacall Class 6 Tin 1 for Context switching. What could be be the other possibilities which may stop exception TRAP to not get generated?
Regards,
Bhagyashri
Thank you for your reply. The exception and all interrupts are getting executed correctly till 3-4 hrs later we observed _Syscall interrupt is not getting triggered.
We are using _Syacall Class 6 Tin 1 for Context switching. What could be be the other possibilities which may stop exception TRAP to not get generated?
Regards,
Bhagyashri
Apr 09, 2020
04:29 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Apr 09, 2020
04:29 AM
The only thing that can stop a SYSCALL trap from occurring is running out of context save areas (a Free Context List Depletion).
If the Base Trap Vector register is corrupted, then the trap vector will not be pointing to where you expect.
If the Context Save Areas are corrupted, or if the FCX or PCX registers are corrupted, it may lead to other Context Management traps.
If the Base Trap Vector register is corrupted, then the trap vector will not be pointing to where you expect.
If the Context Save Areas are corrupted, or if the FCX or PCX registers are corrupted, it may lead to other Context Management traps.