AURIX™ Forum Discussions
Hi,
I have a sensor connected at analog pin AN3 of TC389QP-160 Evaluation board whose values are being read using EVADC Group0 Channel 3 and result register at EVADC_G0RESD2.
I am not able to monitor the converted values from Sensor in Trace32 watch window. On checking at EVADC result register, it is always zero. The observation is same for other configured analog pins through EB-tresos . However, DIO pins are working properly for both of the input/output configurations.
I am not sure about whether that is a hardware pin issue or EVADC is not working. I would first like to analyze if there is an issue with EVADC on the hardware board.
There seems to be no issue with the software as same software is working fine on other TC389QP-160 board and the sensor values from EVADC can be monitored properly.
Please suggest some ways to debug the EVADC issue.
Show LessHello,
i would like to ask for help regarding debug interface lock (software implementation) on Aurix litekit 275 .
Debug lock was implemented according to AP32389 application note. Debug interface is locked successfully, however we can not unlock it. We were using memtool.
I would like to ask for help regarding unlocking device what should i try to unlock it. I read almost all forum topics regarding similar issue.
Also is there any known issues when implementing interface lock with code and unlocking it with memtool?
Error code i receive.
Any kind of advise, response would be appreciated.
Regards,
Jan
Show Less
Hello,
I am using a SAL-TC377TP-96F300S AA device. Can you please clarify if AMU.LMU_DAM functional block is available in this device ?
I went through the AURIX TC37x User Manual and Appendix and there is no reference/mention of AMU.LMU_DAM block anywhere.
SM is the only documentation which says The AMU.LMU_DAM main purpose is to provide two high-performance ASC modelling units, however it is not clear if TC377TP device has these units or not.
Appreciate any feedback on this topic
Show Less
Hi,
I'm reading the password from COMDATA Register of CBS for disabling the Debug password protection. The password is 8 word long and after reading the 1st word I'm trying to set the CW_ACK bit which will acknowledge the client to send the second word. so immediately after setting the bit CW_ACK it is not reflected in the register and it is going into the trap table.
So, can i set the CW_ACK directly or is there any other procedure to set the CW_ACK.
or
If there is any other procedure to read the 8 word password from COMDATA register. If there is any sample code it would be much more helpful for analysing.
Regards
J Gopinadh.
Show LessHello,
How can the effectiveness of the external capacitor be evaluated for EDSADC? There is no information about the internal switched capacitor or other circuit elements, or sampling times from what I can see. Only the RMS current draw and equivalent resistance.
Thank you,
Shaun
I am building a project which consist of 500+ files
I am facing an issue with linking stage, It completes the compilation and assembling part. When it comes to linking part, its showing error "unresolved externals".....from .o files. Can anyone suggest a method or know how to resolve this error?
Show LessI downloaded below version of iLLD package from Infineon (version 1.11.0) and trying to port the example to Tasking compiler and I am running into below error.
- iLLD_1_0_1_11_0__TC37A
- iLLD_1_0_1_11_0__TC3xx_Demos/GtmAtomPwmHlDem
I am using TC377TP MCU and want to port ATOM demo to tasking compiler (Version: 6.3r1).
I have chosen to use the startup files included in “iLLD_1_0_1_11_0__TC37A” instead of generating the startup files from Tasking. I prefer to use the startup files from Infineon instead of Tasking for my application.
I am able to compile all the files correctly, however I am running into below linking problem.
I reviewed the linker file of Tasking and the symbol names are different. Does anyone have the linker file that works with this configuration ?
ltc E106: unresolved external: __USTACK0 - (Ifx_Ssw_Tc0.o)
ltc E106: unresolved external: __CSA0 - (Ifx_Ssw_Tc0.o)
ltc E106: unresolved external: __ISTACK0 - (Ifx_Ssw_Tc0.o)
ltc E106: unresolved external: __CSA0_END - (Ifx_Ssw_Tc0.o)
ltc E106: unresolved external: __START1 - (Ifx_Ssw_Tc0.o)
ltc E106: unresolved external: __TRAPTAB_CPU0 - (Ifx_Ssw_Tc0.o)
ltc E106: unresolved external: __INTTAB_CPU0 - (Ifx_Ssw_Tc0.o)
ltc E106: unresolved external: __USTACK1 - (Ifx_Ssw_Tc1.o)
ltc E106: unresolved external: __TRAPTAB_CPU1 - (Ifx_Ssw_Tc1.o)
ltc E106: unresolved external: __INTTAB_CPU1 - (Ifx_Ssw_Tc1.o)
ltc E106: unresolved external: __ISTACK1 - (Ifx_Ssw_Tc1.o)
ltc E106: unresolved external: __INTTAB_CPU2 - (Ifx_Ssw_Tc2.o)
ltc E106: unresolved external: __CSA1 - (Ifx_Ssw_Tc1.o)
ltc E106: unresolved external: __CSA1_END - (Ifx_Ssw_Tc1.o)
ltc E106: unresolved external: __START2 - (Ifx_Ssw_Tc1.o)
ltc E106: unresolved external: __USTACK2 - (Ifx_Ssw_Tc2.o)
ltc E106: unresolved external: __TRAPTAB_CPU2 - (Ifx_Ssw_Tc2.o)
ltc E106: unresolved external: __ISTACK2 - (Ifx_Ssw_Tc2.o)
ltc E106: unresolved external: __CSA2 - (Ifx_Ssw_Tc2.o)
ltc E106: unresolved external: __CSA2_END - (Ifx_Ssw_Tc2.o)
Show Less
Hello,
I get a KIT_A2G_TC387_5V_TFT and use the "AURIX_code_examples-master\code_examples\SPI_TLF_1_KIT_TC397_TFT" demo code want to debug the SPI, but after bulid shows "ctc E498: Vector table numbers are not allowed for TriCore "tc1.3"", what should I do fot this?
Thank you!
Show LessDear Aurix users,
I have a question about ECC mechanism in TC23x device.
As far as I know, ECC can correct one bit error in data read (DSPR).
Can ECC correct one bit error in data write (DSPR)?
Show Less