AURIX™ Forum Discussions

Hi,

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

hanumana.gowda@veoneer.com

+91-9902768459

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.

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.

Hello ,

dear experts,

The Aurix Evt board  is KIT_A2G_TC367_5V_TFT.  Workding environment is  Aurix Development Studio V1.5

A TC367 project which works fine before.

After the reset section  is moved  from default 0x80000000 to 0x80020000 like below

An error is reported when try to start the mini winger debugger

After I restore the LCF_STARTPTR_CPU0 and LCF_STARTPTR_NC_CPU0 to default value 0x80000000 (given by Aurix Design Studio), the SW can work fine again.

I guess the reason is the BMHD is not point to address 0x8002000 ? So how to change the BMHD and flash into correct UCB?

the changed LSL file is attached for your reference. (zip format)

thansk and BR

Zhou Yi

Hi,

I am looking for details of on which nm technology is used for Aurix SAK-TC387QP-160F300S MCU manufacturing.

Please share the information required.

Regards,

Harish.S

Hi Dear Infineon Team

These two MCU chips: SAK-TC277TP-64F200N DC and SAL-TC277TP-64F200N, 

the max operation temperature is different in datasheet.

So, my questions:

1. Is it a change in materials or design that causes this difference?

2. Is there any difference in Epoxy Molding Compound or Tg and CTE value between these two MCU ?

On a project i'm working on, i have to change the compiler from 4.6.6.1 to 4.6.3.0.

I discovered that both compilers call the CRC32 instruction, but i get different result for the same data.

Any ideas are welcome, where should i look ? has anyone encountered this kind of behavior before ?

Thanks in advance.