XMC1400 boot kit bricked

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

cross mob
User15071
Level 1
Level 1
Hi,

I have already bricked 3 XMC1400 evaluation boards by loading invalid software, after which each start of a debugger induces the following error message:
"DAP error while reading DP-Ctrl-Stat register".
I cannot communicate with the target - I tried with Memtool & debugger(s).
Is there any way _at all_ to delete internal flash? According to the user manual boot mode is only configured by writing to the BMI register, but if there is no SWD communication anymore - I cannot do that!
I guess an alternative is to remove the chip from our design altogether - as Infineon fails to respond to my requests for help!

Thanks in advance
0 Likes
2 Replies
jferreira
Employee
Employee
10 sign-ins 5 sign-ins First like received
Hi,

Possible reasons why the debugger cannot connect to the device after programming?
1. The application/board is using the pins assigned to the debug interface
2. The application disabled the debug interface or reconfigures the BMI

Could you add a delay in your application in main() before the logic of your application? This should give enough time to debugger to connect.
You could as well use of any of the HAR (Halt after reset) BMI modes.

Regards,
Jesus
0 Likes
User15071
Level 1
Level 1
Hi,
A delay did it - thanks.
The root cause was, I think, an invalid vector table in SRAM.
0 Likes