I am writing an Over the Air user application firmware update feature making use of the swap-able flash oin a FRDM K64F. Is there a document that provides a flash memory address of where to write the user application binary before doing the swap?

[johnelliott]

I have plenty of information regarding how to swap the address space of the 2 flash areas, but nothing says exactly where to write the user application binary image. If I attempt to write at 0x00080000 as the start of the upper block, the write fails almost immediately.

Is there some reserved address space at the beginning of the flash? If so, where does the application binary go?

[mjbcswitzerland]

Hi

There is a professional implementation at http://www.utasker.com/kinetis/FRDM-K64F.html (see right at the bottom of page) which you could use in case you prefer to save development time.

See also the discussion at:

https://community.nxp.com/message/586326#586326

The address of 0x80000 is correct but maybe you have an issue with the flash swap indicator(?)

Attached is the uTasker Flash driver (single file solution for all K,KW,KV,KL,KE, KEA flash features which is IDE and chip-independent) as reference - search for SUPPORT_SWAP_BLOCK to locate code relevant to the flash swap. The Flash and the flash swap process is also simulated in the uTasker simulator which allows developers to work more efficiently that using traditional tools.

Regards

Mark

[johnelliott]

Thank you for the response.

That wasn't my problem but it did get me started on a path that led to the

solution.

Problem is solved.

Best regards,

John Elliott

Firmware Engineer II

SKF Condition Monitoring