Hello all,
I have removed the devkit-motorGD board from the pins of the eval board. When I plug in the OpenSDA USB to my laptop, the LED next to the OpenSDA MCU goes on and stays on. But, when I try to build and flash a simple hello world code from the standard simulink function libraries provided by NXP, the same LED blinks 7 times in approximately 2-3 seconds and stays off for another 2-3 second and repeat. This is after the code geenration is complete.
If I plug out and plug in again, we go back to the LED staying on. A simple UART terminal like Putty doesnt show anything on the communication line.
I tried the hello world code before and it worked. It just simply stopped working one fine day. Probably an incomplete/corrupted image has been flashed which is why it is in this unusual state.
Can someone help me with how to mass erase memory? Is there any documentation I can refer to?
Apologies if the question is too basic and is already answered. Do let me know if any more information is needed.
Thanks!
There is no issue with D2 being ON. This LED indicates that OpenSDA is functioning correctly. However, based on the image you shared, I noticed that D3 is OFF. D3 corresponds to the PWR_LED, which should be ON to confirm that VDD is properly supplied.
From what I can see in your board image, the jumper J107 appears to be set to position 1-2, which means the board expects to be powered by a 12V external power source. However, you have only connected the cable to OpenSDA. If you intend to power the board via the USB micro connector, then J107 should be set to position 2-3. Please verify and adjust this jumper setting accordingly.
Additionally, I recommend referring to the Getting Started with the S32K116EVB2Q048 Evaluation Board.
Hi @VaneB
THank you for your response. I want to elaborate the issue I am facing.
I have connected my s32k116 simply through the USB to my laptop:
The D2 LED is solid ON:
I wrote a simple LED blinking code in baremetal C. I created a debug configuration as shown:
When I click on Debug, this comes up:
It doesnt make sense for me to try and change the port.
When I cancel the dialog, this comes up:
I also tried checking the Emergency Kinetis Device Recovery by Full Chip Erase.
It gave me the same result. Please let me know if you have any insights. Your help would be much appreciated!
Thank you!
Do you mean the D2 LED (SDA_LED)? If it is on, there is no issue. It indicates that OpenSDA is powered and functioning correctly.
However, if you are referring to the D1 LED (SDA_RST_LED), that means the MCU is in a constant reset state. Let me suggest checking out the following NXP Community thread, which provides a detailed guide and troubleshooting steps.
The red light of the OPENSDA is always on, and the program cannot be debugged
@VaneB Thank you so much for your response. I will definitely try that out. Before I proceed though, I had one question. As I mentioned, the LED next to the OpenSDA MCU is solid ON when I plug-in the USB. Does this indicate that the S32K116 is in bootloader mode? If yes, is it possible/okay to mass erase in bootloader mode?
Thank you once again for your reponse!
To perform a mass erase, you can use an external debugger such as PEMicro, Segger, or a similar tool. For detailed guidance, I recommend reviewing Section 3.2 of the following application note: AN12130 – Production Flash Programming Best Practices for S32K1xx MCUs. It outlines key steps and important considerations for flash programming and mass erase procedures.
Additionally, I have included a few helpful links below that provide further information and support:
S32 Design Studio & Flash Mass erase
Unlocking and Erasing FLASH with Segger J-Link
S32Kxxx - SEGGER Knowledge Base
BR, VaneB