Can't connect to S32K148 via USB OpenSDA

[luk90as]

I can't connect the S32K148 to flash or debug it. When the evb is connected, the device is shown in the device manager as well as in the explorer. But when I try to connect to the board using S32DS for Arm v2.2, the program is unable to connect.

The system is running on windows 11. The bootloader Version 1.13. The Application Version is 1.21.

[VaneB]

Hi @luk90as 

S32DS For Arm 2.2 does not support Windows 11. The below are the supported host operating systems (OS):

• Microsoft® Windows® 7 32-bit and 64-bit
• Microsoft® Windows® 8/8.1 32-bit and 64-bit
• Microsoft® Windows® 10 32-bit and 64-bit
• Ubuntu LTS 16.04 64-bit
• Debian 8 64-bit
• CentOS 7 64-bit

S32DS supports all editions of the operating systems listed above and is limited only by the requirements of the Java Runtime Environment.

B.R.

VaneB

[manish16911]

Hi @VaneB 

Even i am facing same issue. I am using windows 10 and was able to flash code and enter debug mode via open SDA. But all of sudden i dont know what happened it stopped working for me.

I tried updating OpenSDA MSD update(bootloader) as well but no luck. I am not sure how to overcome this situation.

[kef2]

I'm not sure it is the same issue, I had couple years ago. Accidentally secured target MCU led to onboard OpenSDA always keeping (ehhh, not sure) RESET??? pin low, which didn't even allow to use external JTAG dongle to reprogram MCU. To disengage broken OpenSDA, you need to disconnect USB cable, which is nice way to power board when CAN isn't required. So external power instead of USB, external JTAG like P&E Multilink, unsecuring MCU, and .. onboard OpenSDA is usable again...

I don't remember, is RESET low lighting RED?? LED? With broken OpenSDA USB connected, RED light was always on.