S32K中的主题 Re: Debugger not getting attached to SoC

Debugger not getting attached to SoC

SanketTEL — Tue, 15 Sep 2020 10:14:05 GMT

I am using S32K142 EVB,and i-SYSTEM IC5000 debugger, after recently i flashed a code into the S32K142 EVB i am getting SoC ATTACHING status in winIDEA(i-SYSTEM debugger), after which i am not able to flash new code into the target nor i am able to mass erase from winIDEA.

Please support for this.

Re: Debugger not getting attached to SoC

danielmartynek — Fri, 18 Sep 2020 08:07:33 GMT

Hi,

I would recommend contacting i-system.

Or can you find the error message in the i-system documentation?

I can't tell what is the issue from the description.

It could be a HW issue, power supply, disabled JTAG/SWD ports, or the MCU might be locked with Mass erase disabled.

BR, Daniel

Re: Debugger not getting attached to SoC

SanketTEL — Mon, 21 Sep 2020 07:09:07 GMT

Hi Daniel,

Can you suggest if there is any way to recover from this locked state?

Re: Debugger not getting attached to SoC

danielmartynek — Tue, 22 Sep 2020 08:32:30 GMT

Hi,

Once the Mass erase is disabled either in the Flash Configuration Field or due to allocate CSEc keys and the MCU is secure, there is no way to recover it. But if the MCU was locked, the debugger would inform you. I don't know what is the error message from the debugger here.

Regards,

Daniel

Re: Debugger not getting attached to SoC

jeevanthomas — Wed, 12 Apr 2023 08:21:42 GMT

Hi all,

My team is facing the same issue after using S32K3xx controller and i-SYSTEM IC5000 debugger.

For example, we added the WDG and GPT module of AUTOSAR into the project.

Right during Gpt_Init(), the board is bricking and the debugger looses control of the MCU.

And this is not a one off incident.

Just some additional information:

When we try to recover the bricked boards using Lauterbach, it shows the board is in a BUSFAULT exception.

But I'm wondering why a similar message was not shown using WinIDEA and i-SYSTEM IC5000 debugger.

Have a feeling that if any of the fault exceptions (BUSFAULT, USAGEFAULT, MEMFAULT etc.) occurs in WinIDEA, it's ending up with a bricked board.

Has anybody else faced a similar issue?

If there is a solution, would you be able to share how you guys solve such issues?

Right now, for us, the only recovery solution is through Lauterbach (and unfortunately this is expensive and we have to depend on other team)

Re: Debugger not getting attached to SoC

danielmartynek — Mon, 17 Apr 2023 12:09:47 GMT

Hi @jeevanthomas,

Please create a new thread as this is not related to the original topic (different MCU, etc).

BR, Daniel