Hello,
I am currently a trainee practicing with the S32K118 microcontroller.
I have installed versions 2.2 and 3.5 of the S32DS Tool on a Windows 11 system. For the toolchain, I am using GCC 6.3 for Arm 32-bit Bare-Metal, and the SDK version is 4.0.1.
During debugging, I noticed that the standalone mode does not work in the Semihost Console. To address this, I selected the P&E interface, configured the debugging type, and performed the flashing process.
However, after removing the debug-related code and powering off/on the application, it does not operate correctly.
Could you help identify the reason why it works fine on other systems but fails on mine? Any guidance would be appreciated!
Hello @Juns.
I suggest to checking for any differences between your computer and Design Studio setups and the others where everything works as expected. Also, on the computers where the logic works, the application also function after a power reset?
I will be waiting for your response.
- RomanVR.
and @RomanVR
Thank you again for your response! And I found another issue—there's no separate "Generate Code" folder, and since I'm using the UJA chip, when I go into that folder, there are no files. So I wonder if this is the problem. Please check it! I posted the full response in the thread since I can't upload the images as two separate answers. Please take a look!
Hi @Juns
I tested the "lpit_periodic_interrupt_s32k118" example on the S32K118EVB-Q048 to try to recreate the issue you mentioned. I found that when a debug session is active, the code works as expected. However once the session is terminated, the MCU stays in a "freeze" state and the code stops working, although if the power supply is disconnected and connected again, the code runs properly without having an active debug session. Have you observed this behavior if the supply is disconnected and connected again?
About the flashing process, if you can successfully open a debug session, this means that the code is being also flashed to the MCU, therefore the code should run as expected by just being able to debug the code.
Finally, about the "Generate Code" folder, this is only created in S32DS 2.2 since it uses Processor Expert to load the configuration files of the drivers used in the project, meanwhile S32DS 3.5 uses Configuration Tools, hence the difference between the generated files among the versions involved.
Please let me know if this is useful.
- RomanVR.