topic Re: how to dump(LOAD) application firmware (.bin) code to FRDMK64 using KDS IDE in Kinetis Design Studio

how to dump(LOAD) application firmware (.bin) code to FRDMK64 using KDS IDE

sudhakarp — Thu, 11 Jun 2015 06:18:29 GMT

Hi,

i want to dump(LOAD) application firmware (.bin) code to FRDMK64 using KDS IDE Debug.

without MBED option is possible to load code using KDS IDE only? i think using DEBUG option we can do, but i dnt know how to do that one. we need any extra debugger device for that.

If debug possible mean how to do that one?

regards,

sudhakar p

Re: how to dump(LOAD) application firmware (.bin) code to FRDMK64 using KDS IDE

ZhangJennie — Thu, 11 Jun 2015 07:06:01 GMT

Hi sudhakar p

as I know, without MBED, other debug interface doesn't support bin format.

Have a great day,
Zhang Jun

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

Re: how to dump(LOAD) application firmware (.bin) code to FRDMK64 using KDS IDE

sudhakarp — Thu, 11 Jun 2015 07:25:19 GMT

hi,

suppose if i have .elf or .hex means is possible? how to do that one.

and also mention which format?

thanks and regards,

sudhakar p

Re: how to dump(LOAD) application firmware (.bin) code to FRDMK64 using KDS IDE

ZhangJennie — Thu, 11 Jun 2015 07:58:21 GMT

hi sudhakar p

you ca use either .elf or .s19 file to burn flash.

besides debugger, you can also use simple flash to burn elf or s19 to flash.

Have a great day,
Zhang Jun

Re: how to dump(LOAD) application firmware (.bin) code to FRDMK64 using KDS IDE

sudhakarp — Thu, 11 Jun 2015 08:16:39 GMT

hi,

i am getting following error in console

P&E GDB Server, Version 5.13.02.00

Loading library C:\Freescale\KDS_2.0.0\eclipse\plugins\com.pemicro.debug.gdbjtag.pne_1.1.7.201410171532\win32\gdi\unit_ngs_arm_internal.dll ... Done.

Command line arguments: -device=K64FN1M0M12 -startserver -singlesession -serverport=7224 -interface=OPENSDA -speed=5000 -port=USB1 -USE_CYCLONEPRO_RELAYS=0 -FORCE_MASS_ERASE=0

Device selected is k64fn1m0m12

User Specified Hardware Selection : Interface=OPENSDA and Port=USB1

Connecting to target.

Error opening selected communication interface

Error - Port not found.

Can not enter background mode .

Unable to initialize PEDebug.

PE-ERROR: Failed to Initialize Target

Server running on 127.0.0.1:7224

Connection from "127.0.0.1" via 127.0.0.1

PE-ERROR: Target is not connected

Disconnected from "127.0.0.1" via 127.0.0.1

Target Disconnected.