AURIX™ Forum Discussions

[User19305]

Hello Everyone,

I'm using a TC299 on a custom PCB. After a while, the MCU started to behave faulty. First, isystem debugger was unable to reset the device, hence it was unable to program the device. At this point I was able to flash my hex file with Infineon memtool, and miniwigler . Later, the memtool started to fail during erease operation. It doesn't prompt any error code. Otherwise I'm still able to connect to the target, and read specific address ranges. BMHD areas are filled correctly, so the device is not in bootstrap loader mode, and the debug interface isn't locked. What could cause such a situation? Are there any method to restore the mcu?

[NeMa_4793301]

How many times have you flashed PFLASH and/or the UCBs? The datasheet specifies the maximum number of program/erase cycles.

[User19305]

Don't know exactly, but about 10-30 times

[MoD]

Which error code you get, which messages? What you are programming? Also some UCBs?

[User19305]

I have attached a screenshoot from the memtool. There is no error code prompted. I try to program the pflash from 0xA0000000 to 0xA000FFFF. UCB-s are not changed. BMHD areas are valid.

[MoD]

The is a menu point Log, Is there any error message?
Can you readout some register with a debugger? Which debugger?

[User19305]

I have attahed the log file output. Reading out is working. I'm using a DAP miniwigler3 as debugger

[cwunder]

Did you change the RAM initialization via the PROCOND?
I have seen this when RAMIN=NoInit meaning the SSW will not initialize the RAM's.
afaik most debuggers will download a flash driver to PSPR RAM of CPU0. If this has not been written at least once there will be ECC errors in the RAM and the driver will fail.

[User19305]

I didn't changed it