Hello Youngdae,
It is difficult to determine the cause from the limited information you have provided, however, some common causes for connection issues are:
1) S32 Debug Probe is not powered. Usually occurs when ethernet connection is used, it is easy to forget that ethernet does not provide power.
2) EVB is not powered. Sometimes it is necessary to change jumper settings and the board should be powered off when these are changed, but it is easy to forget to turn the power switch back on afterward. It should be noted, the power switch on the RDB2 board has 3 positions, only one of which is correct to power the board, please check that you are selecting the correct switch position.
3) JTAG cable is not fully seated on the connector at either the S32 Debug Probe device end or the EVB end.
4) The probe tip which connects the JTAG cable to the S32 Debug Probe device is not fully seated on the connector to the S32 Debug Probe device.
5) The EVB is setup to boot from SD card and the SD card is loaded with Linux BSP and installed to the SD card slot. The Linux BSP can interfere with the S32 Debug Probe communications with the target.
6) The S32 Debug Probe has specific voltage requirements (specified in the included S32 Debug Probe user guide). If a different power supply is used vs. the one included in the RDB2 kit, then it is possible that the voltage on the JTAG line is not correct for S32 Debug Probe usage.
I would recommend that you try to use the button 'Test Connection' from within the Debug Configuration menu to confirm that the HW setup and communication settings are correct. This is much quicker than using the 'Debug' button for only checking the connection status.
If you confirm all of the above, and it is still not working, please let us know.
Best Regards,
Mike
