S32K144 Debugging pins are disabled. How to recover the board?

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

S32K144 Debugging pins are disabled. How to recover the board?

ソリューションへジャンプ
316件の閲覧回数
Kunal_Gettobyte
Contributor III

I am using NXP S32K144 IC and while creating its demo project on S32 Design Studio via Autosar MCAL layer during the configuring of Port Driver SWD pins:

  1. PTA4: JTAG SWD
  2. PTA5: System Reset
  3. PTA10: JTAG TDO
  4. PTC5: JTAG TDI
  5. PTC4: JTAG CLK

 

These are configured as UnusedPort pins and theri debugging fucntionality is removed.

Now when i am trying to program them via Jlink, i am getting this error:

SWD selected. Executing JTAG -> SWD switching sequence.
- Connect Under Reset
- SWD selected. Executing JTAG -> SWD switching sequence.
- Communication error while accessing MDM-AP.
- Connect Under Reset
- InitTarget() end - Took 377ms
- InitTarget() start
- SWD selected. Executing JTAG -> SWD switching sequence.
- Connect Under Reset
- SWD selected. Executing JTAG -> SWD switching sequence.
- Communication error while accessing MDM-AP.
- Connect Under Reset
- InitTarget() end - Took 374ms
- ERROR: Failed to connect.
Could not establish a connection to target.
- ERROR: Connect failed

 

What should i do now? Is their any way i can recover the chip? or is my chip and board damaged now?

Isnt their any other way to get it back?

Will flashing the code in it via uart using rappid bootloader, solve the problem?

0 件の賞賛
返信
1 解決策
296件の閲覧回数
danielmartynek
NXP TechSupport
NXP TechSupport

Hi @Kunal_Gettobyte,

The pins are configured for SWD/JTAG/Reset_b after Power-on reset until they are reconfigured by the application.

The debugger will have to halt the execution in this short window.

PE Micro have Kinetis_Recovery_Utility.exe

With Lauterbach we can use:

 

system.CPU S32K144
wait state.power()
system.attach

 

Regarding J-link, this should work:

https://wiki.rdu.im/_pages/Notes/HOWTOs/howto-recover-swd-after-disabled-with-jlink.html

 

Regards,

Daniel

元の投稿で解決策を見る

0 件の賞賛
返信
5 返答(返信)
286件の閲覧回数
Kunal_Gettobyte
Contributor III

Via this method, the chips which are brick because of CSEc peripheral of S32K144 can those also be recovered?

And in the shared link for Jlink, it says to execute halt commands. What Jlink Halt are their which needs to be executed. Can you guide us on that too.

 

Thanks and Regards

Kunal Gupta

0 件の賞賛
返信
282件の閲覧回数
danielmartynek
NXP TechSupport
NXP TechSupport

No, it cannot recover the MCUs bricked by the CSEc engine.

Refer to https://wiki.segger.com/J-Link_Commander or contact SEGGER support, J-link is not an NXP product.

 

Regards,

Daniel

0 件の賞賛
返信
280件の閲覧回数
Kunal_Gettobyte
Contributor III

So is their any way on how to recover the MCU's which are bricket by CSEc. With PeMicro and Lauterback, they will not get recover via that also?

0 件の賞賛
返信
276件の閲覧回数
danielmartynek
NXP TechSupport
NXP TechSupport

This is a completely different topic, it has nothing to do with the SWD/JTAG/Reset_b pins discussed in this thread.

 

BR, Daniel

0 件の賞賛
返信
297件の閲覧回数
danielmartynek
NXP TechSupport
NXP TechSupport

Hi @Kunal_Gettobyte,

The pins are configured for SWD/JTAG/Reset_b after Power-on reset until they are reconfigured by the application.

The debugger will have to halt the execution in this short window.

PE Micro have Kinetis_Recovery_Utility.exe

With Lauterbach we can use:

 

system.CPU S32K144
wait state.power()
system.attach

 

Regarding J-link, this should work:

https://wiki.rdu.im/_pages/Notes/HOWTOs/howto-recover-swd-after-disabled-with-jlink.html

 

Regards,

Daniel

0 件の賞賛
返信