Hi Kerry,
Thank you for answering my question.
I followed your suggestion and used the loadbin in the J-Link commander and surprisingly it works. But the KDS is still being not able to connect to the MK22.

In the commander the sequence is:
1- launch commander -> Jlink.exe
2- type -> device mk22fn1m0xxx12
3- type -> connect
4- it will ask the programmer type - SWD, and speed -> 100
5- then should connect
6- type -> erase
7- check if is unsecured, type - mem 40c 1 (it will show the FSEC status, it should be "FE")
8- if is not "FE", try erase again, and connect again.
9- type mem40c 1, it should show "FE"
10- type loadbin <your_file.bin> 0
11- if everything is ok it will load the file
If you mess up the sequence, and get errors, just poer on/off the board and restart the commander.
Took me a while to figure out the right way to do the file upload because I was tricked by the IDE, it works perfectly for other MCUs, but does not work for the K22. I do not know why.
The hardware needs to include:
1- Resitor of 10ohm and capacitor of 47mF to slow down the power up just for the first upload, put them in a proto-board and connect a power supply set at 3V4.
2- Pull up resistors (4.7K) for SWD_DIO and RESET_b
3- Pull up resistor in EZP_CS is not required
4- The 3V3 regulator requires capacitors in VIN and VOUT. Resitor of 10ohm and capacitor of 47mF are not required after the first upload, I did disable the EZ port at POR by software in my sketch, so it will not come up on POR.
So, this is based on the best of my abilities, it might have other ways but this is the one that works for me.
But I still do not know why the IDE cannot flash the board, would be nice to solve this issue, because is more practical using the IDE alone, instead IDE + commander.
Best Regards,
Antonio Oliveira