Actions
Forum Thread Details
  • State Verified Answer
  • Replies 15 replies
  • Answers 1 answer
  • Subscribers 474 subscribers
  • Views 1684 views
  • Users 0 members are here
Related

Freescale Kinetis software & mbed.org compiler

Former Member

Has anyone any experience (successful preferably) at exporting code from mbed to Kinetis SDK?

I have been playing with a FRDM K64F board and found it much easier to create code using the mbed compiler.

However debugging is a complete mystery to me ( other than printf statements)

The learning curve for KDSK etc is extreemly steep.

My main misfortune is to use WIN8.1

secondly to choose a recently released mbed device where most documentation is for something else!

So a few pointers would be gratefully received.

georgemm101

Parents
  • 0

    In mbed, right click on your project and select "Export Program..."

    image

     

    Then in the dialog box that comes up, select the Kinetis Design Studio toolchain under "Export Toolchain:" and then click on the Export button. You could of course also select the other available toolchains like Keil or IAR.

    image

     

    The website will think for a while and then give you a zip file to download. Unzip it, and import it into KDS like normal (see here for an example: [FRDM-K64F + Kinetis Design Studio (KDS) + Software Dev Kit (SDK)] Tutorial: Toggling an RGB LED without Processor expert).

     

    It'll compile and there are OpenOCD/CMSIS-DAP debug configurations already prepopulated to easily start debugging via the OpenSDAv2 circuit on the board.

     

    Inside that zip directory you can also find the KSDK HAL code at \<project_name>\mbed\TARGET_K64F\TARGET_Freescale\TARGET_KPSDK_MCUS\TARGET_KPSDK_CODE

    This obviously is only true for devices supported by KSDK and mbed enabled, so the FRDM-K64F and FRDM-K22F

Reply
  • 0

    In mbed, right click on your project and select "Export Program..."

    image

     

    Then in the dialog box that comes up, select the Kinetis Design Studio toolchain under "Export Toolchain:" and then click on the Export button. You could of course also select the other available toolchains like Keil or IAR.

    image

     

    The website will think for a while and then give you a zip file to download. Unzip it, and import it into KDS like normal (see here for an example: [FRDM-K64F + Kinetis Design Studio (KDS) + Software Dev Kit (SDK)] Tutorial: Toggling an RGB LED without Processor expert).

     

    It'll compile and there are OpenOCD/CMSIS-DAP debug configurations already prepopulated to easily start debugging via the OpenSDAv2 circuit on the board.

     

    Inside that zip directory you can also find the KSDK HAL code at \<project_name>\mbed\TARGET_K64F\TARGET_Freescale\TARGET_KPSDK_MCUS\TARGET_KPSDK_CODE

    This obviously is only true for devices supported by KSDK and mbed enabled, so the FRDM-K64F and FRDM-K22F

Children
  • 0 in reply to Former Member

    As with everything to do with kinetis, its the detail that counts!

    Importing the project is half the battle. I was unable to do any debugging until the Segger openSDA Bootloader was installed in the K64F Board ( not the mbed version).

    I never finished debugging, for that matter i never really stated as i got distracted by KDS V2.0 being released.

    So now I am back at square one.image

    KDS2 .0 is another story, typical of the lack of attention to detail by Freescale.

    Do they do Quality at Freescale?

    Does anybody check the release before it goes out?

    I guess we have to install the KDSK again! what else is missing?

    I have spent weeks struggling with the beta version, and 1.1.1, so now its start over............

    I am rapidly loosing the will to live.....

    Is there a product that works first time

    george

  • 0 in reply to Former Member

    That's why I wait for others to cross the frontier!image

     

    Clem

  • 0 in reply to Former Member

    Hi george,

    You have to install the KSDK eclipse plugin first. That plugin is what tells KDS (and other eclipse based tools) about Kinetis SDK.  Instructions are in Section 4.4.1 of the C:\Freescale\KSDK_1.0.0\doc\Kinetis SDK K64 User's Guide.pdf

     

      Then when using the new project wizard, you also have to make sure you're selecting a device/board supported by Kinetis SDK.

     

      You don't have to re-install KSDK. Hope that helps.

     

    -Anthony

  • 0 in reply to Former Member

    Hi George

     

    Please keep living ... we are here to support you ;D

     

    Based on your description, I understand that you are using a FRDM-K64F hardware, right ?

     

    To debug with Kinetis Design Studio, you need to reprogram the OpenSDA debug interface of your FRDM-K64F which is preprogrammed in factory with the mbed mode. Simply keep reset button press while plugging the -mini-USB cable to the USB port corresponding to the OpenSDA interface. In windows file explorer, you will see a new drive Bootloader. Drag n drop the Segger JLink v2.0 file inside then unplug and replug your usb cable. Bootloader drive should have disappeared and you should have a new JLink device in Device Manager. Your board is now setup to debug in KDS.

     

    As mentioned by Anthony KDS is the compiler/debugger toolchain and KSDK is a library/driver package. To avoid a frequent KDS update as soon as a new Kinetis derivatives are launched, Freescale has developped KSDK separately to the compiler/debugger. To get KSDK available in KDS 2.0, no need to reinstall it, you just need to go to Help/Install New Software make Add, then Archive and select the file "SDK_1.0.0-GA_Update_for_Eclipse.zip" available at KSDK_1.0.0\tools\eclipse_update as explained in the Kinetis SDK User Guide.

     

    To save your time, I recommend you to follow Bheema's first step tutorials for Freedom with KDS and SDK available at Freescale Freedom development platform

     

    Don't hesitate if you have additional questions.