KL43Z continued drama...

[rnk2014]

Hi All,

A few hours ago I was feeling all was right with my little corner of the universe (besides a raging snowstorm) but I may have been premature in that thought.  Back then I'd actually gotten my KL43Z board working and I even was beginning to understand what it the board was doing too!

At the time, before I set this aside to do my weekend chores, I'd decided that if I could toss together a simple led flashing routine and be able to go through the full process, end to end (build, load, execute), then I could feel satisfied that I'd overcome my learning curve speed bumps.

Not long thereafter I hit another brick wall, and I'm hoping my hangup this time is just that I'm still not savvy enough to get myself out of the Freescale tech jungle just yet.

Here is the problem:  Using processor expert (and in the myriad of examples I've found), to use the on-board LED's you find the device name that the compiler libraries understand to be the LED (such as LED1 or LED_RED, or what have you) and then you find the processor expert "call" to toggle the LED perhaps just make a direct call to the LED name and turn it "on" and "off".

Unlike the KL46Z and the K22F, I cannot locate these elements within the KL43Z processor expert.  One website I found suggested it needed to be "imported" but I have already imported the KL43Z code for Eclipse.  Other pages identify a directory called "Drivers" under the SDK, but that just isn't there for the KL43Z.  Looking on these forums I see that the KL43Z does not have support with code warrior of one version or another, and I'm beginning to wonder if I'm searching for something that isn't there.  I've downloaded and installed the KL43Z quick start package and various other things I've found that looked hopeful, but no joy yet.

So let me ask outright, for the KL43Z, is it necessary for me to just do all the nitty-gritty software hookups in my own code, outside of Processor expert, presumably because the KL43Z isn't fully supported?

I appreciate the help I've gotten so far, so these are just general questions to help me determine how much work I have ahead of me.

Rich

[adriancano]

Hi,

I have some points to share, I hope that with this the information will be clear for you:

• Indeed, as you mentioned, CodeWarrior does not support KL43 devices, nor the PEx (I am referring to the PEx that uses the LDD drivers). If you have some doubts about the difference check this thread Re: SDK vs PDD(without SDK)
• To have support for KL43 devices under KDS you need to download the standalone version for KL43 devices based on the KSDK 1.0.0 from HERE look at the supported devices table at the bottom of the page. Install the eclipse update, please follow the steps in the attached file that colleague Jorge Gonzalez has posted before.
• Once the eclipse update is installed in your KDS you can create a new project for the FRDM-KL43Z board.

         

• You can check the KSDK and Processor Expert options.

         

Please check the points mentioned and let me know your results.

Hope this information can help you

Best Regards,
Adrian Sanchez Cano
Technical Support Engineer
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

[rnk2014]

Thanks for the response Adrian,

I have downloaded the KL43Z quickstart, and I have installed the the SDK update into eclipse successfully.

I am able to create a KL43Z project using the method you are showing, but the problem was a matter of making use of the processor expert

to permit identification of the Red and Green LED's on the KL43Z board, and to pull drivers in from PEx.  I am stalemated in that

part, i.e. determine the symbolic names of the on-board functions and effectively place that into my simple program.  That is where

I got stuck.

I have a K22F board on another machine and am able to use PEx on it without too much pain, but the KL43Z PEx seems to either

radically different, or is missing something.  I looked online and was unable to find anything detailed outside of general comments

about using PEx.

Rich

[adriancano]

Hi,

The KSDK you used for FRDM-KL46 or FRDM-K22F boards is different from the one for the FRDM-KL43Z board. The first one is based on the KSDK version 1.1.0 and the one for the KL43 is based on a later version, the 1.0.0. That is the reason why you find some differences in the configurations.

Also, the BSP of the FRDM-KL43Z using processor expert is not completely defined. I assume this changes will be included in the next KSDK release for the FRDM-KL43Z, meanwhile, the hard job is to define the board pins. I am attaching a video that shows how to configure some board pins to be used in a simple program. Please refer to the video for more details. \

:smileyinfo: I am using the Standalone options, in the new Processor Expert project wizard, because I prefer to do it like that.

Hope this information can help you

Best Regards,
Adrian Sanchez Cano
Technical Support Engineer
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

[rnk2014]

Hi Adrian,

Yes, I am aware of the different models.  I've configured a laptop only for the KL43Z.  When I did use code from the KL46 was when I was casting around trying to find *something* that would work with the debugger.

If you could be so Kind, could you correct this list as to what I should be using for that board?

Kinetis SDK 1.0.0 or 2.2.0?

Freescale KSDK 1.1.0 installed to eclipse from the FRDM-KL43Z quick start guide?

Do I need to install anything else besides these?  Are there any other "add on's" that include updates for PE or other microcode?

All in all, I'm looking for one configuration that I can claim "works" so I can proceed on to actually do some work here. :-)

Rich

[adriancano]

Hi,

To work with the FRDM-KL43Z and KSDK you need to instal:

• KDS v 2.0.0
• KSDK for FRDM-KL43Z
• Install the Eclipse update described in the according the PDF file I attached in my first response.
• Update the OpenSDA firmware for the FRDM-KL43Z: MSD-DEBUG-FRDM-KL43Z48M_Pemicro_v116.SDA available in the FRDM-KL43Z Quick Start Package

Hope this information can help you

Best Regards,
Adrian Sanchez Cano
Technical Support Engineer
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

[mjbcswitzerland]

Rich

Just a reminder - you can get KDS support for KL43 and K22 boards (and almost all other Freescale boards) in the uTasker framework, whereby the same project will run on both boards without issues of library compatibility etc.

It is also free for hobby and non-commercial use but you may find it easier to start with and it additionally allows you to simulate the boards for faster development.

Sorry to be persistent but it is also painful watching your pain when it is known that there is a simple solution which avoids the (temporary) complications - after a couple of days experience you should really be doing interesting projects rather than still hitting walls.

Send me a personal message and I can give you the latest version that will work out-of-the-box with KDS on your boards and when you are feeling fully proficient there is nothing stopping you moving back to the other solutions once they have been released or their intermediate difficulties resolved.

Regards

Mark

Kinetis: µTasker Kinetis support

KL43: µTasker FRDM-KL43Z support  / µTasker TWR-KL43Z48M support

K22: µTasker Kinetis FRDM-K22F support / µTasker Kinetis TWR-K22F120M support

For the complete "out-of-the-box" Kinetis experience and faster time to market

[rnk2014]

Mark,

I haven't had much luck with the precompiled uTasker images so far.  I'll spend a little more time with it over the next week.  Sorry to be dragging this out but my spare time comes in small chunks.

Rich

[mjbcswitzerland]

Hi Rich

I don't understand what you mean by not having much luck with the uTasker images?

These can be loaded with the OpenSDA loader and run on the FRDM-KL43Z - eg. "uTaskerV1.4.8_FRDM_KL43Z_MSD_CDCx3_RF.bin"

Do you have a different revision of the board that causes problems [I test on 700-28061 REV A / SCH-28062 REV C] or do you have a problem with installing USB drivers or some other difficulty?

Note that the images are just examples of a few configurations but with the framework you can build these or other configurations yourself.

Regards

Mark

Kinetis: µTasker Kinetis support

KL43: µTasker FRDM-KL43Z support  / µTasker TWR-KL43Z48M support

K22: µTasker Kinetis FRDM-K22F support / µTasker Kinetis TWR-K22F120M support

For the complete "out-of-the-box" Kinetis experience and faster time to market

[rnk2014]

Hi Mark, and thanks for spending the time to help talk me through this.

Initially, the KL43Z module I had was unresponsive as I struggled to understand if it was even able to communicate with my platform.  Since I'd never used SDA before (except during the walkthrough with the K22F at the Arrow class) I spent much of my time trying to figure out how to get the compiler/debugger to interact with the board (without too much luck then).  Much of the online discussion presumes you have a clear mental picture of what happens in each instance.  I'm technically savvy but I've come to embedded computing via PIC/AVR, neither of which relied on SDA that I had encountered.

Then I had a breakthrough and was able to get one of the demo applications to respond, and slowly I was able to piece together a picture of what was actually happening.  Finally I was able (at least) to work my way through using the SDA loader.  Interspersed with this was a number of sessions with the Kinetis/Eclipse platform, scratching my head and trying to figure out where my disconnect was there.  If I built and compiled a simple application leveraging the KL46 library the debugger *sorta* worked but the KL43Z libraries kept getting various errors.

When I originally tried loading the uTasker, it wasn't clear to me what exactly the communications mechanism was for it, (browser?  Serial port?) and since I was just trying it on a lark (and not really believing it was going to make things any clearer for me over with the compiler) I was already struggling to keep from getting totally confused, so I set it aside for the time being.

Rich

[mjbcswitzerland]

Rich

Thanks you the feedback - I will assume that there was not problem with the binaries in this case.

Running the binaries will of course not help in solving KDS difficulties, to solve these you will need to import the KDS project used to build the binaries.

As I noted before this is available if required by sending me a personal message.

Since I don't think that there are any misunderstandings remaining I don't think that I can contribute here any more.

Regards

Mark

Kinetis: µTasker Kinetis support

KL43: µTasker FRDM-KL43Z support  / µTasker TWR-KL43Z48M support

K22: µTasker Kinetis FRDM-K22F support / µTasker Kinetis TWR-K22F120M support

KDS/CW Import: µTasker Kinetis Compiler Information / uTasker for Kinetis using CodeWarrior - YouTube

For the complete "out-of-the-box" Kinetis experience and faster time to market