Inquiry regarding Start GDB Semihosting Job in S32DS

[trunie1]

Hello. 

When I click Debug configurations and press Debug to flash, the following error occurs.

It flashed normally until yesterday, but this has been happening since today. What can I fix?

Note1. The same error occurs when both USB Multilink and OPENSDA are selected in Interface.
Note2. I already referred to the link below. I uninstalled PE micro, and then reinstalled it again. (But the older version does not appear, only the latest version appears. So I installed the latest version)

https://community.nxp.com/t5/S32K/Internal-error-during-Start-GDB-Semihosting-Job-on-S32DS/td-p/1730...

Note3. As shown above, S32DS does not enter debugging mode. However, under the following conditions, s32k144EVB and MCAT are connected.
condition : After cutting off the power supplied to the board, re-supply power to the board to make the board operate. -> Double-click the S32K_BLDC_Sensorless.pmp file on S32DS to open MCAT -> When I click the GO icon, the board and MCAT are connected.
OPENSDA doesn't work on S32DS, so why does it work on MCAT? (I think it stops during the flash process)

BEST REGARDS

trunie

[Robin_Shen]

Hi trunie,

A1\A2. If you uninstall PEMicro and reinstall it and still only see the latest version of the software, then you may have to reinstall S32DS. 

A3. When you debug for the first time, you have downloaded the program into S32K144. This project is set to connect to FreeMASTER (MCAT) through UART, so you can connect to MCAT after powering on again.

Best Regards,
Robin
-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!

- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------

[trunie1]

Hi. Robin

Thank you for your reply

The focus of my question is how can I flash the MCU (S32K144 or S32K148)? In this case, Should I reinstall S32DS?

Best regards,
trunie

[trunie1]

Hi. Robin

I am waiting for your answer to the question I wrote above. Should I reinstall S32DS really?

And regarding A3, when I flashed the board, an error occurred in OpenSDA and the board and PC were not connected. But why is the board and PC connected when running MCAT?

The problem now is that OpenSDA does not connect when flashing. Why doesn't it connect only when I flash it?

Best regards,
trunie

[Robin_Shen]

I think reinstalling S32DS for ARM is a faster solution. Because you mentioned that it is no longer possible to downgrade the PEMicro software in S32DS. Then be careful not to update the PEMicro software after reinstalling S32DS and it should not be updated to the problematic new version.

If programming via OpenSDA is no longer possible, then please refer to the discussion in: S32K144 D2 RED LED is ON always, try to use the P&E Recovery Utility.

[trunie1 · Accepted solution]

Hi. Robin

After deleting S32DS installed on my PC, I reinstalled S32DS
- version : S32 Design Studio for ARM v2.2

Then, I ran S32DS, opened the example project, and flashed it to S32K144EVB through J7(OpenSDA USB), and it worked normally.

However, when I flash it through J12 (OpenSDA JTAG), the board cannot be connected to the PC. Flash is only possible through J7, but seems not possible through J12. Am I right?

Thank you
Best regards,
trunie

[Robin_Shen]

J12 is the debug interface of onboard OpenSDA(Kinetis MCU K20). If you want to debug S32K144, please use J14.

[trunie1]

I confirmed that it flashed through J14.
Thank you

Best regards,
trunie