AURIX™ Forum Discussions
We are currently working on a flexray driver for TC387 evaluation Kit. We are currently using the iLLD available in myInfineon.
Our test environment is
1. TC387 Evaluation Kit
2. Tasking Compiler
3. iLLD_1_0_1_9_0__TC38A
We integrated the driver in our systems. We observed the following.
1. We have done all the Init configuration as recommended.
2. The ERAY0_SUCC1.CMD is in 'RUN' state and not moving to “Normal Active “ or “Normal Passive” mode. All nodes and pins are configured correctly. But POCS is in "Integration Listen" state.
3. We could understand that iLLD drivers were not “Tested “. But can you please help us in understanding what could be the problem here?
4. Please share if you have any AppNotes which would help us in understanding the E-Ray driver.
Please let us know if you need any further information
Regards,
R.Sreedhar Show Less
The description:“This type of access is used for intermediate checkpoints between WDT services. This may be used (e.g. in conjunction with the timestamp count checking feature or sequence passwords) for task sequence or execution time monitoring. ”
I do not know how to use "Check Access " for task sequence or execution time monitoring.Could you give me some code example or application for this feature.Thanks a lot.
Show Less
Can you please share the SCR RTC configuration in Standby mode and Normal mode.?
Can Aurix support 32bit input capture?
(I understood Aurix(TC3) support 16 bit capture for CCU6 and 24 bit capture for GTM. Is it right?)
Thank you & Best Regards,
1. For some reason, the TC387 is assembled on the bottom of PCBA, and it will be soldered twice. In the second reflow soldering, the TC387 will be on the bottom of PCBA, is there any risk for the soldering quality?
2. If TC387 is flashed first, and then reflow soldered, will the MCUprogram be lost or bit error, or is there any other risk?
Show LessHello all,
I am new to Infineon and FreeRTOS and I am currently planning to run FreeRTOS on Infineon TC397 ADAS board. I am facing compiler and linker errors while building the demo code by FreeRTOS (RTOS demo project for Infineon TriCore TC1782 using the HighTec GCC compiler and PLS UDE debugger under Eclipse (freertos.org)) in order to modify the code to TC397. Please help me in getting a FreeRTOS demo code for TC397 which can be compiled using HighTec IDE.
Show LessHi,
I am working with TC399x AURIX MCU.
I2C Channel 1 is configured in Standard Mode and acting as Master.
I am using Asynchronous mode to read and write.
here are the steps,
1. AsyncWrite with device address (Data Transfer and Protocol Interrupt is hit) and the controller is changed to read mode
2. AsyncRead with device address (Data Transfer interrupt hit) and But the controller doesn't seem to acknowledge the received data. because of this, the MCU protocol interrupt is not hit.
The above is observed only during debugging with breakpoints.
however, if I don't set breakpoint, there is no issue as AsyncWrite and AsyncRead is working fine.
Could you please help me with this?
Thanks and Regards,
Hanumanagowda M S
+91-9902768459
Show Less
When using the code example to test SCU_WDT(in debug mode ), there are some question as follows:
when execute code line 61: IfxScuWdt_serviceCpuWatchdog(IfxScuWdt_getCpuWatchdogPassword()); /* Service the CPU0WDT */,then use the "printf" to print the REG "SCU_WDTCPU0SR" , the value of "SCU_WDTCPU0SR" shows as follows:
I think the WDTCPU0 is not really enabled,because the SCU_WDTCPU0SR.B.TIM = 0xFFFC and this value has never changed.
so, how to really enable the WDTCPU0 in debug mode?
Looking forward to your reply.
Show Less
Hello,
How to configure SCR RTC to get Interrupt in every one second. Can you please check and provide the feedback.
Dear ,
OEM ask we lock MCU when SOP.
By following this thread:
Password Protected JTAG Flashing Query - Infineon Developer Community
I tried lock debug port by configure UCB_DBG via infineon memtool , it worked as expectlly; but when I tried to connect MCU via memtool again with password it not worked.
But I can lock/unlock MCU via lauterbach successfully.
this is not a good way for aftermarket.
Could you please tell me the correct steps or configuration to unlock debug inteface with password via memtool;
Memtool information:
Version 2021.08
Build 5012
Fronted version 1.24.8
server version 1.40.12
thanks for your support.
Show Less