AnsweredAssumed Answered

Port application from KL25Z128 to KL25Z64

Question asked by Alexander Agudelo on Nov 22, 2015
Latest reply on Nov 23, 2015 by SCOTT MILLER

Hi, I've been working on a project using the FRDM-KL25Z as development board, but the end goal was always to use the KL25Z64 as target MCU. I thought that migrating from the big brother version would be just a matter of using the "common" pins to both packages and make a few amendments to the linker file, but there seems to be more to it, isn't it?

 

The project started using mbed's libraries and migrating it to KDS at this stage is not an option unfortunately. I know my custom hardware works because:

 

* I replaced the device with the KL25Z128, and flashing the version of the code for this target (the code used in the dev boards) works fine.

* I also created a simple blinking LED app using KDS with PE for the KL25Z64, and it works ok as well.

 

I'm attaching my original linker and startup files (for the KL25Z128).  I just changed the MEMORY section FLASH and RAM values to match those of the KL25Z64:

 

MEMORY {   VECTORS (rx) : ORIGIN = 0x00000000, LENGTH = 0x00000400   FLASH_PROTECTION (rx) : ORIGIN = 0x00000400, LENGTH = 0x00000010   FLASH (rx) : ORIGIN = 0x00000410, LENGTH = 64K - 0x00000410   RAM (rwx) : ORIGIN = 0x1FFFF800, LENGTH = 8K - 0xC0 }

 

Note: the RAM ORIGIN was changed to the value used by linker file produced by PE for this target (MKL25Z64xxx4_flash.ld).

 

Any advice would be greatly appreciated!

 

Regards,

 

Alex.

Original Attachment has been moved to: mbed_MKL25Z4.ld.zip

Attachments

Outcomes