Hi, I'm Yonghee Lee and working as soft engineer with Aurix TC377.
The thing I want to ask you to answer is that the internal die temperature can be used for safety (ISO26262).
The MCU will be monitoring the internal die temperature of TC377 and checking if it is out of range about operation.
I am wondering If the above system can meet the safety requirements or there is some system using die temperature for safety.
Please let me know if you have an idea about the question.
Thank you.Show Less
I need to monitor a 19.2MHz clock with our TC367DP MCU using the MCAL drivers. Any suggestion what configuration is needed on EB Tresos and how to measure it?
I am currently working with the safety OS in TC397. The microOS module is enabled and also the MicroKernel in OS configuration is enabled. Already for the Can Demo along with the package 3 ISR's are configured but with the same pririty. when a new ISR is added to OS configuration, liking error is shown as in attachement
What could be the reason and how can a new ISR be added to Micro kernel enabled configuration.Show Less
I am using DMA to communicate with ASCLIN_LIN. I realized transferring the data from one array to another array. However, when I tried to transfer the data from one array to the data register of ASCLIN_LIN, the data transfer failed and DMA interrupt failed.
What's the reason?
I have a TC265 B-Step on a custom board with the debug interface lock enabled in the UCB.
I am able to connect to the microntroller with the correct password using the Memtool in combination with the miniWiggler 2.0 and DAS V7.1.8 64 bit. However, if I deinstall this version of DAS and install DAS V7.3.7 64bit, I am not able to connect and unlock the debug interface anymore. But normal connect on TC265 B-Step devices with unlocked debug interfaces still works.
Is this a bug of the current version of DAS? Or am I missing some configuration?
Any help is much appreciated, since I would like to use the current version of DAS.
In our Project we are using the EDSADC to generate the exciter signal and also read back the resolverposition.
Now to my question: our Debugger is always showing the Value 0x0F for the Filed SDCAP in the Register EDSADC_CGSYNCx. According to the manual this value should represent the phase delay between the exciter signal (after my filter stage, so it is a nice sine wave and not the pulsed signal that the EDSADC is generating) and the cosine/sine wave repsective to their channel. With an oscilloscope I measured a phase shift of about 8-9µs at a signal period of 102,4µs. In have configured 64 samples per period. So I would expect the EDSADC to show a value of about 8-9µs/102,4µs*64 = 5-6. I believe this value should give me a maximum amplitude of the Integration result, stored in IVALx.
So I did some further testing and this are the results:
So in the Graph i do not see the maximum of those integrals at 0xF which is the value of SDCAP nor on my calculated values of 5 or 6. Where is the error in my understanding?
Thanks for clarifying!Show Less
shortly I will start to evaluate the demo board for the TC397. I download the Aurix Studio and found that is provided with the winIDEA solution to debug/program purpose. I will use it with the Infineon DAP miniWiggler.
My question is related with the winIDEA: in the GUI I found this:
Do I need a license in order to program/debug a demo project? Or it is possible to debug without a license (or DEMO mode)?
I follow the simple "SMU_Fault_Signaling_1_KIT_TC297_TFT" to add FSP function into my program.
I add the follwing code:
After power-off reset, the ESR0 keep light on.
On using FlsLoader_Write(0x80640000, 32, &alignedPageBuffer) API to write a page in PFLASH2 of AURIX TC397XX, Program Fetch Synchronous Error (PSE) Trap is occurred and Fetch Bus Error (FBE) is raised in CPU->CPU0->PMI->PSTR (Program Synchronous Trap Register).
After debugging I figured out that any assembly instruction (e.g., ld16.w, addi, ige.u, sh and etc) at P:0x80022940 causes this issue.
If I placed a loop that contains __asm__ volatile ("nop" ::: "memory") before the line causing the issue (so that the code below the loop is shifted away from 0x80022940), the trap NOT occurred. However, the data did not reflected to the memory (although FlsLoader_Write returns E_OK and PMU->DMU->ERRSR register is 0x0)
I need to know why this is happening to solve it permanently.Show Less