Marek,
Carlos mentioned on July 1 that there is a patch Freescale is working on to fix this issue. Now on July 21 you mention the error is fixed and will publish the hot fix soon.
Could you be so kind as to define "soon"?
Before the end of July?
Sometime in August?
Before the end of 2016?
I need to know so I can decide whether to scrap the idea of using the MK02 for 2016 products and just stick with the MKL05 that is already on existing products. I was hoping to utilize the floating point precision, extra flash memory, 16bit ADC, and being able to move on up to the east side, to a deluxe apartment in the sky.
Thanks