S32K116EVB FreeMaster Connection Failure

[BoardFreak]

Hi,

I have an S32K116EVB board and I am currently trying to establish a connection with the freemaster program. The board is not detectable by freemaster in any way. I have tried all existing manual instructions from nxp website but to no avail. I am using a micro usb connection to my PC and the mass storage does appear in my computer workspace.

Also, how do I initiate the jumpstart program? Where do I need to copy the contents of the jumpstart file? None of these have been specified so I would appreciate if anyone could help me figure this out.

Thanks in advance

[Robin_Shen]

Hi

Please check your S32K116EVB is  S32K116EVB2Q048  or S32K116EVB-Q048. S32K116EVB-Q048 has been replaced by S32K116EVB2Q048 in a few years, so here is S32K116EVB2Q048 for description. Due to the difference between these two board and the FreeMASTER JumpStart Project is developed on S32K116EVB-Q048, so you may need to check these points:

Point 1.Your S32K116EVB2Q048 may no preloaded with the JumpStart code. You can drop the S32K116_EVB_JumpStart_Firmware.srec(...\S32K116EVB_JumpStart_FreeMaster \S32K116_EVB_JumpStart_Firmware\Debug) into mass storage device.

Point 2. The default jumper setting of J109 J110 J111 on S32K116EVB2Q048 is not connect MCU pins to LED. In order to use these LEDs, you need to change the jumper setting .

Then open S32K116_EVB_JumpStart.pmpx and follow the Tool->Connection Wizard... should be able to connect with FreeMASTER.

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.
-------------------------------------------------------------------------------

[BoardFreak]

Hi Robin,

Thank you for your response. 

In regards to your points:

Point 1) I have downloaded the jumpstart kit and copied the firmware file on to the mass storage that appears when I plug the circuit to the computer. But again, the freemaster is not able to detect my board. The COM3 is assigned to my board and I checked it through device manager. As for the connection settings, the transfer rate is set to 115200, and the connection type is BDM with OpenSDA.

Point 2) Could you please elaborate more as to how I can change the settings? Do I need to make changes through wires connecting the J109, J110, and J111 ports?

Thank you in advance 

[BoardFreak]

Update:

I managed to switch the J107 pins and distribute power to the MCU. Upon doing so, I was able make jumpstart program recognize my board not through opensda, but through plug-in mode. It shows the connection details at the bottom of the screen. I have also switched the RGB J109, J110, and J111 positions to 2-3 pins.

However, the RGBs still won't turn on through jumpstart app. Also, the touch sensors and potentiometer are also null and not working. The debug log shows constant errors.

I also used the Kinetics Recovery tool to see if it would solve the issue and it appears it only works when the MCU pins at J10 are located at 2-3 (3.3v). Now the red led (not the RGB) is constantly on.

[Robin_Shen]

First, I want to make sure we're talking about a schematic that matches your board, otherwise things get complicated. Please take pictures at the top and bottom of the board. Here you can see that the customer got a different version S32K116EVB2Q048: https://community.nxp.com/t5/S32K/S32K116-EVB-debugging-with-PE-Multilink-FX-RESET-issue/m-p/1449185

I managed to switch the J107 pins and distribute power to the MCU. Upon doing so, I was able make jumpstart program recognize my board not through opensda, but through plug-in mode.

There is no difference between J107 on REV A and REV A2. Connect 1-2 will power the board by J16 external power supply. Connect 2-3 will power the board by USB cable J7. Only when the USB cable is plugged, the OpenSDA will be shown in Windows Operation System.(For FreeMASTER connection, USB cable is required.)

it only works when the MCU pins at J10 are located at 2-3 (3.3v).

Connect 2-3 of J10 will power the MCU 5V.

Did Kinetics Recovery tool halt MCU? After halt MCU, you should be able to debug or program S32K116. (You can also try to close Kinetics Recovery tool and then drop srec into mass storage device S32K116EVB )

Now the red led (not the RGB) is constantly on.

If the SDA_RST_LED(D1) is lighting, then RESET_S32K(MCU) may resetting. Only after S32K116 is program new code will the resetting disappear.

[BoardFreak]

Hi Robin, 

Thank you for your response. I have attached pictures of my board to this post. As for the Kinetics Recovery Tool, yes it was able to halt the MCU but only when I positions the J10 PINs on 2-3 (3.3v). Otherwise, if I set the J10 to 1-2 position, the kinetics recovery tool will not be able to halt the process. This problem also persists when connecting the board to FreeMaster via Plug-in. When I position the J10 PINs on 1-2, I get an error saying "Cannot force background mode". But when I position J10 on 2-3, the connection will be established. I have also attached the corresponding screenshots of my progress to this post.

Kindly let me know of what you think.

Thank you

[Robin_Shen]

Don't know why drop srec did not work on your board. Here you can see the LASTSTAT.TXT will show Completed after I drop srec into MSD. And then the RGB led will blinking(JumpStart project is running).

Have you tried Flash from file tool in S32DS for ARM2.2? (Import a S32K116 project and select srec then click Flash)

Once the RGB led is blinking, you can connect it with FreeMASTER.(...\S32K116EVB_JumpStart_FreeMaster\S32K116_EVB_JumpStart_PC\S32K116_EVB_JumpStart.pmpx) I don't have S32K116EVB2Q048 on hand, so just test it on S32K116EVB-Q048.(See the attached video)

[BoardFreak]

Hi Robin,

Thanks for the advice, I tried what you had proposed and by flashing the hello_world on to the firmware I was able to get the RGB blinking. However a couple of problems still persist:

1) The board is still not detectable even after the flashing process by the FreeMaster_Jumpstart application. When trying to connect via UART I get an error saying no UART communication found. 

2) After copying the firmware again to the storage, the text document says "ready" instead of "completed"

3) This is quite weird and I do not know why it is happening, but when I switch the MCU voltage from 2-3 position (3.3v) to 1-2 (5v) the flashing process through S32D encounters an error.

4) The Kinetics Recovery Tool cannot halt the MCU after I flashed the hello_world project. The RGB continues to blink and I do not know how to stop it. (Even after deleting the firmware from storage)

I am not sure if I have a faulty board or not, but I appreciate your patience and advice.

Looking forward to hear back from you.

P.S: I have attached all the corresponding error messages to this post.

[Robin_Shen]

Connect 2-3 of J10 should power the MCU with 5V. Don't know why you said 3.3v.

Seems that Flash from file tool in S32DS for ARM2.2 works. (Import a S32K116 project and select srec then click Flash), so that your board will blinking RGB.

Drop srec did not work may due to the problem of your OpenSDA circuit.

FreeMaster_Jumpstart application need to communication through OpenSDA UART. So would you please check these circuit of OpenSDA?

If these circuit error, then I am afraid you need to connect external TTL-USB serial board at PTB0 and PTB1.