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.)
J107 SCH-47484 REV A.png
J107 SCH-47484 REV A2.png
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.
J10 SCH-47484 REV A and REV A2.png
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.
J104 SCH-47484 REV A and REV A2.png