Nov 16, 2017
07:10 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Nov 16, 2017
07:10 AM
Hello,
I'm trying to load .cmm file through TRACE32. When ever i tried, it showing "Emulator Debug Port Secure" error. Can any one tell me,
what could be the reason and how to solve this issue? Please find attached the screen shot for the same. Thanks in advance.
I'm trying to load .cmm file through TRACE32. When ever i tried, it showing "Emulator Debug Port Secure" error. Can any one tell me,
what could be the reason and how to solve this issue? Please find attached the screen shot for the same. Thanks in advance.
- Tags:
- IFX
22 Replies
Not applicable
Nov 21, 2017
01:28 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Nov 21, 2017
01:28 AM
Are you using the Trace on a brand new controller without software or bootloader?
Nov 21, 2017
03:07 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Nov 21, 2017
03:07 AM
Yes. I am flashing software in new controller(first time flashing in to TC275 controller). Could you please tell what could be the reason.
Regards,
Pradeep
Regards,
Pradeep
Not applicable
Nov 22, 2017
01:37 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Nov 22, 2017
01:37 AM
I had a similar problem von TC277, you don't have a bootloader so that there is no function able the Trace. The JTAG is a seperate module which isn't able to communicate with the rest of the uC.
My solution was to use the bootstrap loader, which exists on every device hardcoded for a first connection.
You have to use pins 14.0 and 14.1 either for ASC (UART) or CAN connection to flash a bootloader.
Infineon offers an application note with example software to flash by bootstrap (AP32272).
When you flashed it for a first time with the bootloader from the AP the connection with Trace works afterwards.
My solution was to use the bootstrap loader, which exists on every device hardcoded for a first connection.
You have to use pins 14.0 and 14.1 either for ASC (UART) or CAN connection to flash a bootloader.
Infineon offers an application note with example software to flash by bootstrap (AP32272).
When you flashed it for a first time with the bootloader from the AP the connection with Trace works afterwards.
Mar 04, 2020
05:03 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Mar 04, 2020
05:03 AM
Hello,
I have written the invalid values to the BMHD0 where there is no values in the other BMHDs. This invalid value locks the ECU.

According to the schematic, it is not possible for the other startup procedure. The following image shows the schematic.

I need the support to come solve this issue. Thanks in advance.
I have written the invalid values to the BMHD0 where there is no values in the other BMHDs. This invalid value locks the ECU.
According to the schematic, it is not possible for the other startup procedure. The following image shows the schematic.
I need the support to come solve this issue. Thanks in advance.
Mar 04, 2020
08:38 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Mar 04, 2020
08:38 PM
Hi
What value did u program the BMHD0?
Did u erase the BMHD0 without programming?
What is the status of ESR0?
Is it HIGH or LOW?
How do you control HWCFG3? By DIP switch or the onboard pull-up? HWCFG3 need to be LOW to use HWCFG4 & HWCFG5 for booting.
Can you then change DIP switch of HWCFG4 & HWCFG5 to OFF(HIGH) & reset the target board.
Now try to connect using the debugger again.
What value did u program the BMHD0?
Did u erase the BMHD0 without programming?
What is the status of ESR0?
Is it HIGH or LOW?
How do you control HWCFG3? By DIP switch or the onboard pull-up? HWCFG3 need to be LOW to use HWCFG4 & HWCFG5 for booting.
Can you then change DIP switch of HWCFG4 & HWCFG5 to OFF(HIGH) & reset the target board.
Now try to connect using the debugger again.
Mar 09, 2020
09:22 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Mar 09, 2020
09:22 PM
Hello,
The BMHD1, BMHD2, BMHD3 are erased. Instead of writing the valid values, accidently i have written the invalid values in the BMHD0.

Since, we are using "Internal Start from Flash" method to flash the ECU, the HWCFG[4] and HWCFG[5] pins are left open. It is not possible to follow bootstrap methods.
While giving CPU Reset via Trace32, the PORST pin get toggled from HIGH-LOW-HIGH and the ESR0 pin is toggled from LOW-HIGH-LOW.
The BMHD1, BMHD2, BMHD3 are erased. Instead of writing the valid values, accidently i have written the invalid values in the BMHD0.
Since, we are using "Internal Start from Flash" method to flash the ECU, the HWCFG[4] and HWCFG[5] pins are left open. It is not possible to follow bootstrap methods.
While giving CPU Reset via Trace32, the PORST pin get toggled from HIGH-LOW-HIGH and the ESR0 pin is toggled from LOW-HIGH-LOW.
Mar 10, 2020
12:42 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Mar 10, 2020
12:42 AM
Hi
there are total 4 sets of BMHDx_ORIG & BMHDx_COPY, if BMHD0_ORIG is wrong, it will look at BMHD0_COPY, and the sequence follows to BMHD1/2/3.
you mentioned u erased BMHD1/2/3, this will prevent the TC29x from booting because of ERRORED condition in UCB for confirmation code (ie, 0x43211234 = unlocked), normally the debugger advises u from erasing them.
in an UCB errored state, the SSW recognizes this as failed Flash startup and consequently doesn’t boot the device as indicated by ESR0 LOW.
there are total 4 sets of BMHDx_ORIG & BMHDx_COPY, if BMHD0_ORIG is wrong, it will look at BMHD0_COPY, and the sequence follows to BMHD1/2/3.
you mentioned u erased BMHD1/2/3, this will prevent the TC29x from booting because of ERRORED condition in UCB for confirmation code (ie, 0x43211234 = unlocked), normally the debugger advises u from erasing them.
in an UCB errored state, the SSW recognizes this as failed Flash startup and consequently doesn’t boot the device as indicated by ESR0 LOW.
Mar 10, 2020
02:06 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Mar 10, 2020
02:06 AM
Hello,
Thanks for the information.
Is there any way to recover from this issue?
Thanks for the information.
Is there any way to recover from this issue?
Mar 10, 2020
02:43 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Mar 10, 2020
02:43 AM
VincentWan wrote:
Hi
there are total 4 sets of BMHDx_ORIG & BMHDx_COPY, if BMHD0_ORIG is wrong, it will look at BMHD0_COPY, and the sequence follows to BMHD1/2/3.
you mentioned u erased BMHD1/2/3, this will prevent the TC29x from booting because of ERRORED condition in UCB for confirmation code (ie, 0x43211234 = unlocked), normally the debugger advises u from erasing them.
in an UCB errored state, the SSW recognizes this as failed Flash startup and consequently doesn’t boot the device as indicated by ESR0 LOW.
Hi,
the answer above is valid for TC39x.
Correction to my reply above:
it should read:
there are total 4 sets of BMHDx, if BMHD0 is wrong, it will look at BMHD1/2/3 in sequence.
you mentioned u erased BMHD1/2/3, this will prevent the TC29x from booting because of ERRORED condition in UCB for confirmation code (ie, 0x43211234 = unlocked), normally the debugger advises u from erasing them.
in an UCB errored state, the SSW recognizes this as failed Flash startup and consequently doesn’t boot the device as indicated by ESR0 LOW.
Mar 10, 2020
02:51 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Mar 10, 2020
02:51 AM
shirly wrote:
Hello,
Thanks for the information.
Is there any way to recover from this issue?
Hi,
if the UCB is errored, there is no way to recover it.
we advises customer to never erase the UCB.
For development purpose, only need to always use unlocked code (ie, 0x43211234) for confirmation code.
Mar 11, 2020
02:20 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Mar 11, 2020
02:20 AM
Hello,
Is it possible to come out of this issue?
Do you have any solution for this?
Is it possible to come out of this issue?
Do you have any solution for this?
Mar 11, 2020
08:10 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Mar 11, 2020
08:10 PM
Hi,
if u have erased the UCB confirmation code. there is no way to recover the chip.
if u have erased the UCB confirmation code. there is no way to recover the chip.
Mar 11, 2020
11:20 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Mar 11, 2020
11:20 PM
Hello,
I have erased only the BMHDs, not UCB. The UCB blocks are configured as NOP which means cannot be erased. Please check the following configurations in the .cmm file.

I believe that UCB portions are not erased. But i am not able to see the content of the memory.
I have erased only the BMHDs, not UCB. The UCB blocks are configured as NOP which means cannot be erased. Please check the following configurations in the .cmm file.
I believe that UCB portions are not erased. But i am not able to see the content of the memory.
Mar 12, 2020
01:18 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Mar 12, 2020
01:18 AM
Hi,
I mixed up BMHDx for TC39x & TC29x.
No UCB and confirmation code for TC29x BMHDx.
I see that u have configured for ABM mode in the BMHD with PINDIS = 1
since the memory range to be checked is wrongly programmed.
the SSW will enter Generic bootstrap loader mode @ P14.0 / P14.1
if you have access to Memtool & port pins 14.0 & P14.1, u can connect using Memtool to reprogram the TC29x.
I mixed up BMHDx for TC39x & TC29x.
No UCB and confirmation code for TC29x BMHDx.
I see that u have configured for ABM mode in the BMHD with PINDIS = 1
since the memory range to be checked is wrongly programmed.
the SSW will enter Generic bootstrap loader mode @ P14.0 / P14.1
if you have access to Memtool & port pins 14.0 & P14.1, u can connect using Memtool to reprogram the TC29x.
Mar 12, 2020
02:42 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Mar 12, 2020
02:42 AM
Hello,
As i have already told that the pins are not taken out in the ECU Schematic.
As i have already told that the pins are not taken out in the ECU Schematic.
Mar 12, 2020
06:59 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Mar 12, 2020
06:59 PM
L1800Turbo wrote:
I had a similar problem von TC277, you don't have a bootloader so that there is no function able the Trace. The JTAG is a seperate module which isn't able to communicate with the rest of the uC.
My solution was to use the bootstrap loader, which exists on every device hardcoded for a first connection.
You have to use pins 14.0 and 14.1 either for ASC (UART) or CAN connection to flash a bootloader.
Infineon offers an application note with example software to flash by bootstrap (AP32272).
When you flashed it for a first time with the bootloader from the AP the connection with Trace works afterwards.
Hi: L1800Turbo!
Can u send the AP32272 to me ! I can not find it !
Thanks!
Mar 12, 2020
11:29 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Mar 12, 2020
11:29 PM
shirly wrote:
Hello,
As i have already told that the pins are not taken out in the ECU Schematic.
Hi
I tried programming the values in the BMHD0 with BMHD1/2/3 erased and still can connect using the debugger.
not sure are u using script to connect to the board or using the CPU -> System window to connect?
Mar 17, 2020
03:00 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Mar 17, 2020
03:00 AM
Hello,
what is the State of HWCFG4 and HWCFG5 in your schematic?
what is the State of HWCFG4 and HWCFG5 in your schematic?
Mar 17, 2020
09:21 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Mar 17, 2020
09:21 PM
Hi
I am using the IFX starterkit.
Both HWCFG4/5 are HIGH.
On your schematic, if u pulled HWCFG3 to LOW & with HWCFG6 pulled HIGH, HWCFG4/5 will be HIGH.
I am using the IFX starterkit.
Both HWCFG4/5 are HIGH.
On your schematic, if u pulled HWCFG3 to LOW & with HWCFG6 pulled HIGH, HWCFG4/5 will be HIGH.
Jun 04, 2020
05:36 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Jun 04, 2020
05:36 AM
Hello,
The ALM3[6] (SRI frequency Out of Range) is raised during runtime. This Alarm is triggered sporadically.
What are the root causes for this Alarm?
Note: There are no other alarms triggered.
The ALM3[6] (SRI frequency Out of Range) is raised during runtime. This Alarm is triggered sporadically.
What are the root causes for this Alarm?
Note: There are no other alarms triggered.
Jun 04, 2020
07:14 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Jun 04, 2020
07:14 AM
This could be a problem with the clock monitor setup, or (rarely) with the internal 100 MHz backup oscillator.
Could this be an older AURIX that is affected by CCU_TC.002 in the errata sheet? (i.e., don't use CCUCON3/CCUCON4.xxxSEL=2 or 3)
Could this be an older AURIX that is affected by CCU_TC.002 in the errata sheet? (i.e., don't use CCUCON3/CCUCON4.xxxSEL=2 or 3)
Jun 07, 2020
10:47 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Jun 07, 2020
10:47 PM
Hello,
The CCUCON3 and CCUCON4 configurations are seems to be correct. The following are the values loaded in the Clock Monitor Registers.
SCU_CCUCON3.U |= 0x00281028;
SCU_CCUCON4.U |= 0x00141414;
Any other things to be checked?
The CCUCON3 and CCUCON4 configurations are seems to be correct. The following are the values loaded in the Clock Monitor Registers.
SCU_CCUCON3.U |= 0x00281028;
SCU_CCUCON4.U |= 0x00141414;
Any other things to be checked?