S32DS PEmicro Connection Assistant

[Djuric]

Hello,

Until recently I was able to debug code normally on my development board S32K3X4EVB-T172

with S32DS. All of a sudden, when I start the debugging process, I get this message PEmicro Connection Assistant, An error occured while connectiong to the interface

I updated the extension to the latest version but it doesn't help.

This message also started appearing:

Literally everything was working normally until a few days ago....

Please help.

Thank you.

[Djuric]

Hello @Julián_AragónM ,

Thanks for your reply.
These three LEDs are on, you can see in the picture.

I tried on another computer with no success.

I have Windows 11.

None of Xilinx aplications/drivers have been installed.

Is there any free SW tool I could use to erase the entire contents of the controller memory (except the S32DS)?

[temp_user]

How do you solve this issue finally? I met the same situation as well.

[Djuric]

I didn't solve it. The evaluation board is still bricked. I also tried with an external Cyclone debugger to access the chip through the JTAG 20 pin port. It is simply not possible to load SW to memory or erase ir. I think the problem is in FS26 chip that is stuck and I don't know how to get it unstuck.

[temp_user]

I suspect there maybe some issue in SBC. So did you try to reset sbc or maybe change the sbc chip? Did you have any attempt in SBC?

[Djuric]

I think we're talking about the same thing.  FS26 = SBC

https://www.nxp.com/products/power-management/pmics-and-sbcs/safety-sbcs/safety-system-basis-chip-wi...

No, I have not been able to reset this chip to normal state.

[temp_user]

bad news....
Yes, I am talking about FS26... After I check the description of this ticket, I think we met the same situation. But worst news is that I think the FS26 of my board may be destroy...And I am asking nxp for support but it always late response... Anyways, one more question from my side, you mentioned that you tried to erase all the memories of MCU(s32k344) by debug port, but it failed. And if sbc is not in normal work then MCU(s32k344) will not be powered on and MCU can not connect to debugger. So did you connect external power supply when you debug? If yes, I want to know your operation. Thank you very much.

[Djuric]

An external 12 volt power supply should always be connected to the evaluation board, regardless of whether you are debugging via the USB or JTAG port.
Basically, I tried to use an external Cyclone debugger to access the microcontroller via the JTAG port and erase it. It didn't work.

[Julián_AragónM]

Hi @Djuric,

I can see that LED D15 RST_OSDA is on. Also, neither D4 nor D5 are turned on.

Please check if the either power supply is connected properly, or if the voltage level is lower that the specified [+12.0V to ≥2Amps].

NXP Does not provide SW tools for erasing the memory apart from S32DS, but you can look into third party, such as PROG Flash Programming Software or J-Link Flash.

Best regards,
Julián 

[Djuric]

The power supply that powers the board is fine. Paid tools such as PROG Flash Programming Software or J-Link Flash. are not an option for me right now.

[Djuric]

@Julián_AragónM I suspect the FS26 chip (in S32K3X4EVB-T172) is causing the problem. Do you have any way to restore it to default setting. Somehow to reset it, to enable normal functioning?

[Julián_AragónM]

Hi @Djuric,

Below is a process for SPI commands to let FS26 enter normal mode. For your reference. 

[Djuric]

@Julián_AragónM  and how exactly do you suggest I do this, given the fact that I can't connect to the microcontroller (EV board)?

[Julián_AragónM]

Hi @Djuric

Sorry for the delay, does this issue also happens when a blank project is debugged? Do you have any debugging tool (PE Micro or J-link) to test the connection?

Please make sure the debug configurations are correct:

Also, if you do not have HSE enabled, make sure the flash algorithm selection in Advanced Options is set correctly.

Best regards,
Julián

[Julián_AragónM]

Hi @Djuric,

Is the reset LED turned on? Could you possibly try to use the probe on different computer?

Have you installed in the meantime some other software on your computer (e.g. Xilinx)?

P&E Drivers for Windows utilize the 3rd party service Jungo WinDriver to enable USB support under windows 10. Xilinx also uses WinDriver for their driver packages, but older versions. Starting with the P&E Driver package 11.7, a conflict between P&E Drivers and software IDES that rely on older Jungo driver packages might occur.

Best regards,
Julián