I'd like to use the S32DS for ARM V2.2, S32K144EVB, to connect to a PC via USB to check examples and debug them. However, the connection isn't recognized, so I'm asking for help.
Hi @Lee7,
Please help me by providing some additional information.
Firstly, check if Multilink's firmware is up to date, and if the EVB is powered correctly; either with a 12V jack (J107 in 1-2 position), or with USB (J107 in 2-3 position).
Is this the first time trying to connect to the board? Have you successfully programmed the chip before? Have you tried to connect through an external debugger (not OpenSDA)?
Also, please try connecting with an empty project —either a hello world, or a blink example from SDK).
You can try to use Kinetis Recovery Tool to halt the MCU. Please refer to the community's posts: Solved: The GDB Server was not able to establish a connection to the target processor. - NXP Communi....
Lastly, you can also try to attach to the running MCU to see if the application is stuck somewhere:
I will be waiting for your response. Best regards,
Julián
Thanks for Reply @Julián_AragónM
Firstly, check if Multilink's firmware is up to date, and if the EVB is powered correctly; either with a 12V jack (J107 in 1-2 position), or with USB (J107 in 2-3 position).
-> I'm not sure if multilink's firmware is up to date. I recently tried to solve this problem by putting OpenSDA_V2_1, V3_2.bin into EVB-S32K144(D:), but I'm not sure if it worked. Currently, when the board is powered on, LEDs D1(Red), D2, D3(Green) are on.
Is this the first time trying to connect to the board? Have you successfully programmed the chip before? Have you tried to connect through an external debugger (not OpenSDA)?
-> This is my first time downloading or debugging a program. I'm experiencing almost the same issue when trying to connect to a sample MCU via PEMicro.
Also, please try connecting with an empty project —either a hello world, or a blink example from SDK).
-> All are impossible
You can try to use Kinetis Recovery Tool to halt the MCU. Please refer to the community's posts: Solved: The GDB Server was not able to establish a connection to the target processor.
-> Even if I unplug and plug pins 1 - 2 of j107, there is no response.
Lastly, you can also try to attach to the running MCU to see if the application is stuck somewhere:
->I checked the checkbox and debugged, and it seems to connect, but the status is as below.
Hi @Lee7,
If your D1 LED (Reset) is always on, then your S32K144 is continuously on reset. It may be caused by no correct program flashed into it.
Please try to Enter OpenSDA Bootloader Mode and then click SDA_INFO.HTML check the Application Version.
If Application Version is: 1.19 (ok), then you can try to drop srec file to EVB-S32K144. I have attached a hello_world.srec for you to test. The red & green RGB LEDs should be blinking:
If this still does not work, I'm afraid the device may be locked. As last resort, you can try to change the OpenSDA to SEGGER J-Link and refer to this community post: Unbricking S32K146. It shows how to unlock MCU by issuing J-Link Commander commands.
Please keep in mind that if the device is secured, with mass erase disabled, there is no way to recover. You can try to solder a new MCU on top of the EVB.
Best regards,
Julián
