Hi Ian
1. You will find all linker script files in
\Applications\uTaskerV1.4\KinetisCodeWarrior\Linker_Files but if you don't have the latest version V1.4.5 there may still be some missing. They are easy to create though - it is just the RAM and Flash settings that need to be adjusted. I have attached the
KL_256_32.ld that I have.
2. What I have done in the lastest version is pass the tool patch to the BAT file using
..\generate.bat "${ARM_GNU_TOOLS_HOME}/bin"In the bat file I have
set toolpath=%1
%toolpath%\arm-none-eabi-objcopy --output-target=binary uTaskerV1_4.elf uTasker_V1.4.bin
%toolpath%\arm-none-eabi-objcopy --output-target=srec uTaskerV1_4.elf uTasker_V1.4.srec
%toolpath%\arm-none-eabi-objcopy --output-target=ihex uTaskerV1_4.elf uTasker_V1.4.hexThis ensures that the same tools are used as by CW and also doesn't require the PC to have a path setting for this.
In the stand-along GCC build I simply add a path in the bat file itself:
SET PATH=%PATH%;C:/Program Files/CodeSourcery/Sourcery G++ Lite/binIn this case you need to know where the build tools are located and modify the bat file, but this has to be done only once.
Unfortunately I couldn't get the tool path passing to work in the new KDS (it doesn't seem to allow using path variables in the parameter passing process) so it is also necessary to set the local path manually at the moment (if not already set in the PC's path variables, where it can also be manually added).
3. The Freedom boards tend to be delivered with a MSD loader installed but not the debugger (not very logical). To install the OpenSDA debugger you can follow the guide here:
http://www.pemicro.com/opensda/In the firmware Apps zip file there are lots of OpenSDA debugger images for all FRDM boards and just set the KRDM-KL46 to the boot loader mode by powering it with the loader switch held down, then drag the corresponding file, "MSD-DEBUG-FRDM-KL46Z48M_Pemicro_v114.SDA" is the one I used, to it (it appears as hard drive). Then restart the board and you should be able to connect/load/debug.
I had to do this with all of the FRDM boards that I worked with, apart from the new FRDM-K64F which has a different variation...
Good luck
Regards
Mark
Regards
Mark