Announcements

Equip yourself to optimize AURIX™ MCUs for Evs at the EV Webinar. Click here to register.

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

AURIX™ Forum Discussions

Not applicable
Hi,

after flashing (iROM) the LCDDemo provided by the Free Aurix Entry Toolchain, the TC2X7 V1.0 Application Kit Board is performing an reset within an second after every startup of the application. Therefore i can't flash the board by the Toolchain anymore, because no connection can be estabiled or the board is disconnected after the board resets.

Is there any possiblity to halt the board after the startup and stop the execution of the the application code e.g. by an hardware pin, so that i can erase the application code or flash a new one?

I'm thankful for every hint, which could lead to an solution of my problem!

Best regards
Lukas
0 Likes
24 Replies
Not applicable
Hi,

I have a similar Problem:
After flashing the Time Demo from Hitex, the application runs for 2 seconds. After that, the board seems to be go in a sleep mode.
By pressing the WakeUp Button, the application runs for 2 seconds again.
If i press the Reset Button periodicly the Board goes not in sleep mode.
I can't flashing the board again (via PLS and Memtool).
The DAS Device Scanner shows: "no device (DAS JDS Application Kit TC277 V1.0)"
After pressing "wake Up" it shows: "TriCore Family (Memtool can be connected at this moment)"
After 2 seconds: "no device (DAS JDS Application Kit TC277 V1.0)" is shown again.
Memtool fails (Suspend Watchdog Timer is activated in Memtool Setup)

How can I now flash the board again?

Best regards
Henning
0 Likes
Not applicable
Hi Henning,

that's exactly the same problem I have ^^ Until now, I didn't found any solution. Still working on it.

Best regards
Lukas
0 Likes
User9888
Level 3
Level 3

Hi Luka, Henning,

I think this may be the result of what's been described in application note AP32260 (logon to myinfineon first), which happened to me too. The application note describes the cause (TLF35584 ending up in failsafe mode and cutting off the power supply to the CPU) and offers two solutions.

The first solution uses a Lauterbach or PLS debugger script to quickly configure the CPU in SPI mode and attempts to switch off TLF35584 through this protocol.

The second uses a hardware solution also explained in the application note. This basically attempts to wire pin TM to VCC. In my case I was using application kit TC2X7. With the help of a colleague I checked its schematics and found that removing resistor R128 would probably do the trick. And it did. I have now regained control of my board.

Hope this helps,

Henk-Piet Glas
Technical Product Specialist
0 Likes
Not applicable
Thank you Henk-Piet.

I have the Application Kit TC277_TFT. Resistor R128 is there, but Resistor R127 is missing. (is marked as opt in schematic).
So I have to remove R128 and to bridge the open connection for R127.
Than +5V is on TM. Right?

Kind Regards

Henning
0 Likes
User9888
Level 3
Level 3
HRechenberg wrote:
Thank you Henk-Piet.

I have the Application Kit TC277_TFT. Resistor R128 is there, but Resistor R127 is missing. (is marked as opt in schematic).
So I have to remove R128 and to bridge the open connection for R127.
Than +5V is on TM. Right?

Kind Regards

Henning


Hi Henning,

That's right. I checked my board just now to make sure (it's been a while); I removed R128 and bridged (a missing) R127 to +5V.

Best regards,

Henk-Piet Glas
Technical Product Specialist
0 Likes
Not applicable
Thanks Henk-Piet,

its working!
0 Likes
Not applicable
Hi Henk-Piet,

thank you for your help! I will try it later this day!

Best regards
Lukas
0 Likes
Not applicable
Works perfectly! Thank you very much, Henk-Piet!
0 Likes
User9888
Level 3
Level 3

Hi Lukas, Hemming,

Good to hear you guys are up and running again!

Best regards,

Henk-Piet Glas
Technical Product Specialist
0 Likes
Not applicable
Hi

I have the same Problem and I wonder whether I could use the miniWiggler V3 to take the TLF35584 out of failsafe mode.
I did not purchase it yet, that is why I did not already try it.
Does anyone have experience on that?

Regards
Florian
0 Likes
User9888
Level 3
Level 3
Enigma_ wrote:
Hi

I have the same Problem and I wonder whether I could use the miniWiggler V3 to take the TLF35584 out of failsafe mode.
I did not purchase it yet, that is why I did not already try it.
Does anyone have experience on that?

Regards
Florian


Hi Florian,

It’s possible I think, but maybe someone else wishes to chime in, in case I’m off. Earlier in this thread I mentioned that application note AP32260 (logon to myinfineon first) explains two solutions. One we already discussed. The other is by means of a PLS/Lauterbach debugger script that configures the CPU for SPI as a means to disable TLF35584. Those scripts are included in the application note plus a detailed explanation. Using this approach the mini-wiggler is only a means to an end. Of course either debugger must support it, which I suppose they do.

Henk-Piet Glas
Technical Product Specialist
0 Likes
Not applicable
Hi,

I'm asking if the mentioned solution will recover the TLF35584 and return it to its safe state and the microcontroller will function properly after that.
or a permanent failure is occurred in the micro-controller which caused fail state by the regulator and the mentioned solution is intended to be used only in order to reflash the kit?

Thanks
0 Likes
Not applicable
Hello all,

thank you for giving the hint with the Application Note 32260, Henk-Piet. I read through it completly. Since my Triboard Inverter Kit with Aurix TC264D and TLF35584 has an extensive grounded TM Pin, i am not able to connect that pin to 5V, neither to remove a resistor because there is none. So I chose the software solution with the PLS debugger. Since I use a differnt QSPI Modul and different Hardware Pins I changed the initialisation sequence as explained in the AP32260.
Somehow if I try to connect the message pops up: Executing init commands failed.
Maybe someone has an idea what is wrong in my code.

SET 0xF0001D00 0x8 //Clock Control Register
SET 0xF0001D10 0x03C04 //Globalcon
SET 0xF0001D04 0x0 //PISEL
SET 0xF0001D14 0x14000000 //GLOBALCON1
SET 0xF0001D24 0x501 //ECON1 für slso1 und slso9
SET 0xF0001D48 0x2000000 //SSOC

SET 0xF003B000 0x00 //Port 10 Output Register initialisieren
SET 0xF003B010 0x980000 //Serial Clock P10.2, P10_IOCR0
SET 0xF003B010 0x98980000 //SDI P10.3, P10_IOCR0
SET 0xF003B040 0x0 //Port 10 Pad Driver Mode 0 Register initialisieren
SET 0xF003B044 0x0 //Port 10 Pad Driver Mode 1 Register initialisieren
SET 0xF003B014 0x9000 //SCS P10.5 P10_IOCR4
SET 0xF003B040 0x0 //Port 10 Pad Driver Mode 0 Register initialisieren
WAIT 5
SET 0xF0001D54 0xFFF //FLAGSCLEAR
SET 0xF0001D60 0x97A10001 //BACONENTRY
SET 0xF0001D10 0x01003C04 //GLOBALCON


SET 0xF0001D64 0x8756 //DATAENTRY, write first spi word
WAIT 5
SET 0xF0001D54 0x200 //FLAGSCLEAR
WAIT 5
SET 0xF0001D54 0x400
SET 0xF0001D64 0x87DE
WAIT 5
SET 0xF0001D54 0x200
WAIT 5
SET 0xF0001D54 0x400
SET 0xF0001D64 0x86AD
WAIT 5
SET 0xF0001D54 0x200
WAIT 5
SET 0xF0001D54 0x400
SET 0xF0001D64 0x8625
WAIT 5
SET 0xF0001D54 0x200
WAIT 5
SET 0xF0001D54 0x400
SET 0xF0001D64 0x8D27
WAIT 5
SET 0xF0001D54 0x200
WAIT 5
SET 0xF0001D54 0x400
SET 0xF0001D64 0x8A01
WAIT 5
SET 0xF0001D54 0x200
WAIT 5
SET 0xF0001D54 0x400
SET 0xF0001D64 0x87BE
WAIT 5
SET 0xF0001D54 0x200
WAIT 5
SET 0xF0001D54 0x400
SET 0xF0001D64 0x8668
WAIT 5
SET 0xF0001D54 0x200
WAIT 5
SET 0xF0001D54 0x400
SET 0xF0001D64 0x877D
WAIT 5
SET 0xF0001D54 0x200
WAIT 5
SET 0xF0001D54 0x400
SET 0xF0001D64 0x8795 //DATAENTRY write last SPI Word
WAIT 5
SET 0xF0001D54 0x200
WAIT 5
SET 0xF0001D54 0x400

Regards
Felix
0 Likes
Not applicable
I appreciate the Technical Product Specialist. very cooperative.. other than I have faced this problem, you solved quickly
0 Likes
User9888
Level 3
Level 3
Camryn64 wrote:
I appreciate the Technical Product Specialist. very cooperative.. other than I have faced this problem, you solved quickly


Hi Camryn64,

Thanks very much for saying that. FYI, recently I was doing some tests using Infineon memtool, and I found that it has a "execute initialisation commands on reset" menu item. In addition I noticed that it already contains some commands that start with this comment:

; Workaround for TLE35584 A-Step Bug

So presumably connecting with memtool will disable the watchdog and restore the connection to your board. You'd then somehow need to add that same workaround into the startup code of your application.

The startup code makes a callback to function _call_init() which you may populate for yourself with user initialisation code, for example the above workaround. To make sure the startup code actually calls this function you need to enable preprocessor macro __CALL_INIT. To make sure you timely meet feeding the watchdog, you may need to reposition _call_init() to an earlier point in time; at this point it's called prior to calling the main entry point. This way you should be able to use the TASKING debugger to debug your application.

Of course the hardware workaround still holds as well, with the added advantage that you needn't make changes to your code.

Best regards,

Henk-Piet Glas
Technical Product Specialist
0 Likes
User14162
Level 1
Level 1
Hi,

I have TC2X4 Application kit. i tried the same procedure i.e. removed R128 and place it at R127. But no fortune.
I saw someone else had the same problem and he created a thread about it but the thread has no replies. Please guide, what can i do to solve this problem?

Best Regards,

Usman
0 Likes
User19734
Level 1
Level 1
5 replies posted First reply posted First question asked
Hi everyone,
same is happening to me.
I have a TC2x7 application kit which keeps resetting after i downloaded an example project from Aurix development studio...
I tried the hardware solution, since i can no longer connect, but it is not working for me.

Looking at the board i see i already do NOT have R128, while i have R127. Using an oscilloscope i see i have the 5V on pin TM for about 2 seconds, then it goes to 0 for less then a second, then goes back to 5V and so on...

What can i do to restore the board?

thanks,
Miglio
0 Likes
MoD
Employee
Employee
25 likes received 50 solutions authored 100 sign-ins
The "problem" here is, that the window watchdog and error monitoring of the TLF35584 is active which result in periodically reset and power shutdown. The window watchdog and error monitoring can be switched off by HW via the MPS (earlier TM) pin on TLF35584. On Application is this done via resistor R127. They must be assemble with 0R and R127 should be removed or changed to 20K. If this is already done then no action needed on this board. Unfortunately this is not working with the A-step of TLF35584. The TLF35584 is an A-step when the marking is 35584VS1 or 35584VS2. In this case the switch off of the safety feature via HW is not possible. Always possible is the switch off via SW. For this please see AP32260. Note that after power off/on any software disabled watchdog will be enabled and must be disabled via software again. Therefore the user software must also contain this handling to be able to run standalone.
0 Likes
User19734
Level 1
Level 1
5 replies posted First reply posted First question asked
Thanks for the answer!

So, just to be sure i've understand correctly:
- my TLF component is marked as TLF35584VS1, so the HW solution is not doable due to the A-step thing.
- because of the constant reset of the board, i'm not able to establish connection with any SW, so also the SW solution is not doable. (disabling watchdogs via software is something to keep in mind for the future, but it is not a solution for the current situation)

In conclusion, the answer to the question "what can i do to restore the board?", is nothing... the board is lost.

I'd like to know if that's the case, so i'll just stop wasting my time trying to revive it.


Thanks,
Miglio
0 Likes
MoD
Employee
Employee
25 likes received 50 solutions authored 100 sign-ins
Only when the marking is 35584VS1 in 1 line it is an A-step.
From your description of error it is an A-step but this not match with your mentioned marking.
Unfortunately I am not familiar with the AURIX developer studio but there should be any possibility to execute a script as described in AP32260
0 Likes
User19734
Level 1
Level 1
5 replies posted First reply posted First question asked
Ok, the marking on my component is
Infineon
35584VS1
2B GE446

So i believe it's an A-step.

Unluckily the research of AP32260 (and lots of related terms) from Infineon home page, gave no positive results.

I fear the only option left is to get a miniWiggler and use it to flash the board using the JTAG or DAP connettor. To do so i should use the DAS tools, which i already have installed, but even them requires to establish a connection with the board... and i can't do it!

I'm relly out of option.

Thanks for the help and the explanation.
0 Likes
MoD
Employee
Employee
25 likes received 50 solutions authored 100 sign-ins
Yes, your board has a TLF35584 A-step assembled.
AP32260 should be available via myicp.infineon.com
You can reprogram the device also via memtool (can be found on Infineon website).
Attached the script which must be executed after reset in memtool.
Please note that maybe you must retry the connect.

0 Likes
User19734
Level 1
Level 1
5 replies posted First reply posted First question asked
From what i can see, also memtool require to establish a connection with the target; but if the TLF is cutting off the supply, causing the reset of the board, how can i keep up a connection with the board?
0 Likes
MoD
Employee
Employee
25 likes received 50 solutions authored 100 sign-ins
In the memtool you must add the commands in the script.
Open Target -> Setup...
Select Connect / Reset
Select Execute Initialisation Commands on Reset (mark on before the text)
In the field below add the complete lines from the script
Left with OK
You will not be connected in the first tentative. You must Retry many times because there is only a small time window after reset which you must meet…

Make sure that you will program any sw which support the switch off by sw (see AP32260).
0 Likes