Hello Rutvij
The KL16 is a KL26 without USB. Therefore KL16 is supported in the KL26 (FRDM-KL26Z) configuration by simply not using USB.
When you used KBOOT together with the FRDM-KL26Z which interface did you use? As I wrote before I though that SPI was using the same protocol as UART and so I don't yet understand how loading code from an SPI EEPROM is supported by KBOOT.
Concerning porting - of course everything can be ported, it is just a question of the development effort (and associated costs). KBOOT extensions in the uTasker serial loader are quite simple since all operation can be simulated. If a basic KBOOT protocol script can be defined for the interface in question the work may take a couple of hours for all IDEs and Kinetis parts. Porting original KBOOT KL25 to KL26 (and essentially KL16) code should also not be that involved, although the concept does involve creating a completely new project for the target in question rather than being target independent as in the uTasker project. This therefore needs to be repeated for every different IDE and Kinetis target making about 500x more work - if only one IDE/target is involved it is of course not a big deal.
Regards
Mark
Kinetis: µTasker Kinetis support
KL26: µTasker Kinetis FRDM-KL26Z support / µTasker Kinetis Teensy LC support
For the complete "out-of-the-box" Kinetis experience and faster time to market