Oh the pain...FRDM-KL43Z

[rnk2014]

Just received my KL43Z and anxiously began to try and use it.

As I uncover the tools I need to apply I'm discovering that things are not all sweetness and light in KL43Z-land.  I found the standalone KSDK for the KL43Z and installed it.

As I said, that standalone SDK which is supposed to support the KL43Z, and some of the fields get filled when I try to build a "new" application, but when I compile it and attempt to debug it, I get a "error in services launch sequence" of which the details say it is a missing device name.  So I turned back to the debug setup and the debug tools thinking perhaps I've skipped a step (of course the doc doesn't have much in the way of details about how to do this).

Back at the "quick start guide" (sheesh!) I plug the USB port into the SDA connector it shows up as a USB drive as expected.  The little self test program is flashing away with the LEDs and saying hello to me on the led's (over and over).  Reading the details in the users guide and the SDA users guide I'm told that if I put a SREC file into that drive it will be loaded.  I take the demo KL43Z file and drop it in there -  and the status file says it is "programming".  Maybe so - but there is no evidence from the board that that is happening.  In fact, it just keeps flashing those leds -  "hello"  "hello".....

Undaunted by the complications so far, I then go to the OpenSDA vendor to try and download the SDA software (thinking that I need to do that step) but their website doesn't respond (at all).

Being resourceful, I then go to the FRDM-K22F seminar kit and find the jlink image that worked just fine with the K22F at the seminar and try to load it.  Nope, nothing happens there either.

So I think I've passed the "RTFM" test, and on bended knee I ask whether *anyone* can point me at a solution.

Rich

[rnk2014]

Still trying to get anything happening with a FRDM-KL43Z board.  This morning I had a little extra time to retrace my steps to make sure I've done a "clean" installation.

Beginning with a different computer, (Windows 7)  which has never had Kinetis on it I did the following.

1.  Installed a copy of KDS-v1.1.1

2.  Installed a copy of the KSDK_1.0.0 for KL43Z

3.  Installed the eclipse update contained in the KSDK_1.0.0 for KL43Z

I still cannot do anything meaningful with the KL43Z board via USB.  It just comes up in Demo mode.

I created a "new" program.  It found the FRDM-KL43Z processor expert configs and created a template.  Under main.c of that template I just identified a variable "int a;" and then set it to zero "a=0;" - nothing else.

I then did a build and attempted to do any debugging.  No joy.  I tried a jlink and another SDA debugger from the KL43Z QSK but nothing gets a response from the KL43Z board (which acts like it isn't recognizing anything via the SDA port - The properly named files appear when it is plugged in, but it doesn't seem to be responding at all.

So, I believe I've installed the right software, but it isn't clear that the FRDM-KL43Z board is responding.  Not clear if this is because of what I'm loading into it, or the configuration of the board.  I've never had the KL43Z board work before (new, bought from Mouser) and since I don't know how it should behave I'm just grasping at straws here.

Any KL43Z Guru's out there looking to be a hero?

Rich

[Alice_Yang]

Hi Rich,

On my side , it can work well.

1) Please refer to the "FRDM-KL43Z_QSG.pdf"  update the bootloader :

2)  if you want run the KSDK demo , Please refer to "C:\Freescale\KSDK_1.0.0-KL03Z\doc\Kinetis SDK User's Guide for the FRDM-KL43Z "  -> 4.4 .

pay attention to :it must be "building the platform  "

3) When debug , configure like this

If still have any question , contact me !

Best Regards,

Alice

------------------------------------------------------------------------------------------

If this post answers your question, please click the Correct Answer button.

-----------------------------------------------------------------------------------

If this post help your question, please click the helpful Answer button.

[rnk2014]

I am travelling the rest of this week, but will try that when I return.  Thanks for the help, more to come...

Rich

[Alice_Yang]

OK,  have a good time !:smileyhappy:

Alice

[mjbcswitzerland]

Rich

If you find the FRDM-KL43Z support lacking in the KSDK you can take a look at the following:

µTasker FRDM-KL43Z support

µTasker TWR-KL43Z48M support

It works out-of-thebox with CW, KDS, IAR, Keil, Crossworks, Atollic, Green Hills, GCC and can be built and simulated with VisualStudio.

Applications written with it for the KL43 will also work on any other K, KE or KL device (with the necessary peripherals) with little or no porting effort.

Regards

Mark

Kinetis: http://www.utasker.com/kinetis.html

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

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

[rnk2014]

Mark,

Thanks for the response.  I've been out of town and then down with the flu so I apologize for not getting back right away.

I must be exceptionally dense, but it seems as if no matter what I try with the KL43F modules I have, I am unable to accomplish anything except watch the never-ending self-test program executing.

Per the uTasker page, I downloaded the first two .BIN files associated with uTasker for Kinetis, and in each case I attempted to place them into the shared drive that appears when I plug in my FRDM-KL43Z (plugged in with SW1 held doen).  The files show they are downloading to the shared drive, and the status response returns with "completed", however the demo program still continues to run and apparently nothing else happens with the module.  Unplugging the module and re-plugging it in does nothing.  Am I missing something here?

I had purchased two of these modules from Mouser, and they both are behaving the same way.  I just don't get it.

Rich

[Jorge_Gonzalez]

Hello Rich,

Just trying to bring you some additional help.

From reading all your conversation above it is not clear if you differentiate between BOOTLOADER mode and MSD programmer mode, so just to clarify:

- Bootloader: If you connect the board with reset button hold down, a volume called BOOTLOADER is showed in your PC. Here you would copy the OpenSDA applications (.SDA extension) such as the one in Mark's attachment.

- MSD programmer: When you connect the board *without* holding reset, a disk with name FRDM-KL43Z appears on your PC. In this disk is for you to load the .srec demo files or any other srec file which was generated for KL43. If the board has the .sda combined firmware (MSD + Debug), then this mode also serves as debug port.

Are both volumes appearing as expected on your computer?

When you connect the board without pressing reset, you should also find this in your Device Manager:

The KDS settings should look like this:

Also you tried to load a FRDM-K22F image. This will not work since that is for a later OpenSDA (v2.1), check this link: OpenSDAv2

Try loading the one Mark shared.

Finally, if you understand all of this and you are doing everything correctly, it may be other factors such as Antivirus or file commander. One quick test is to use the copy command in cmd instead of drag and drop. For these tips please read the next short article:

FRDM Board not responding? Check your Virus Scanner! | MCU on Eclipse

Regards!
Jorge Gonzalez

[mjbcswitzerland]

Hi

To avoid confusion:

>>In this disk is for you to load the .srec demo files or any other srec file which was generated for KL43

Also binary files are accepted by the loader so it is not restricted to srecs.

Regards

Mark

Kinetis: http://www.utasker.com/kinetis.html

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

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

[rnk2014]

Hi Mark and Jorge,

We're getting buried under snow here in Ohio, so it is an excellent time to sort all of this out for myself :smileyhappy:

After Mark's first message I began to back trace my steps.  As I said above, I had my first contact with all this at a seminar where we were quickly shown some methods to program the K22F, and then given some tools.  The presentations were rapid fire so when we began actually doing things with the code the instructor moved pretty fact through the class PowerPoint slides.  Technically I'm no slouch, but misunderstanding something but believing you "got it" can take you on a wild goose chase when suddenly you discover there are no more bread crumbs.

So this morning I began carefully retrying things, one thing at a time on the KL43Z, and then observing what it did (green led flashing or not, status on boot drive different, etc.)  Coming from a PIC development environment, I'm accustomed to having much more feedback from the tools as I use them.  At some point I picked up a thread, and slowly began to understand what worked with what, and then using that information to piece things together (that was 2 hours ago :smileyhappy: ).

Right now I have successfully (repeatedly) been able to load images into the board via SDA as well as the MBED tools. I then got things so that the debugger would work, and with a little experimentation I found a combination of debug configs that didn't fail (I had to use the KL46Z image in the debugger because the KL43Z apparently is not supported.

Right now I'm working on a simple application that flashes a LED which I will load as a .srec file to complete the loop and ensure I'm really understanding the entire process.

I should say that if your only source of info is the many different kinetis FRDM platforms, it is easy to get confused by the different points each picks up the picture.  For me, as soon as I was able to do something and the board agreed with me about what was to be done, things began making sense.

I won't be overconfident and say I understand it all now, but I'm much closer.  Thanks for the assistance from you both and from Alice Yang too.

Rich

[mjbcswitzerland]

Rich

I don't think that you are doing anything incorrectly - when a software (whatever it is and also if it couldn't actually run) is dragged and dropped onto the FRDM.KL43Z disk it causes a delete of the entire flash as first step and then programs the (new) code.

If the original SW is still running after doing this it means that the inbuilt loader didn't do this action, although the status (in LASTSTAT.TXT) shows that it completed.

What OS does you use on the PC? If you use Windows 8.1 and the loader on the board is an older on  it may be due to an incompatibility with the operation - in this case you can update the loader from the P&E package - see https://www.pemicro.com/opensda/faqs/faqs.cfm

I have attached the latest version for your board.There are also newer mbed versions at the mbed site but these won't work with KDS so generally the P&E one should be used.

To program it power the board with the RESET button leld down and it will appear as a hard disk but wit the name "BOOTLOADER" insted. Drag and drop the file to the disk and then re-power to move back to the normal mode.

If none of this helps you could try using the Flash utility in KDS instead to load binaries but the embedded loader is much faster and convenient (as long as it works).

Regards

Mark

Kinetis: http://www.utasker.com/kinetis.html

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

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

[Alice_Yang]

Hi Rich,

Does the project create by yourself  can build , while can not debug ?

And the demo code can work well ?

Please attach the error screenshot .

And  i test on it on my side at once.

Alice

[rnk2014]

If I just do a build with a simple main.c, it looks like it builds okay (can't know until I run the debugger :smileyhappy: )

I've tried many different attempts of placing the .srec programs into the shared drive but as I said earlier, nothing seems to work.  The status textfile sometimes says "programming" or "complete" but usually it says "ready".  In all cases the demo program just keeps thunking away and there is no response from the board in any case.

Rich

[Alice_Yang]

Hi Rich,

Which version of KSDK do you use ?

So far ,the latest version KSDK1.1.0 not support FRDM-KL43.

And which IDE do you use ?

BR

Alice

[rnk2014]

Hi Alice,

I've been using the KDSK_1.0.0 version.  As I drilled deeper into the question I found an item on the forum which advised using

"Freescale Kinetis SDK_1.0.0 for the FRDM-KL43Z-Windows installer".  It did bring along the chip descriptor files along with it, but nothing worked.

The stack I have now is what I got at the Freedom Seminar:  Kinetis SDK_1.0.0  on top of Freescale's KDSK_1.0.0  with the Freescale SDK upgrade for KDSK_1.0.0.  I then installed the FRDM-KL43Z SDK_1.0.0 and applied the enclosed eclipse update from it.

I am considering removing it all and then starting over with just the KL43Z SDK however based on how the KL43Z itself acts when I plug it in I'm wondering if there is another component (such as a USB driver or some such thing) that is broke.   The system I'm doing this on is my laptop running 32bit Windows 7.

Rich

[rnk2014]

Correction, SDK1.1.0 is installed but the freescale KDSK is KSDK_1.0.0

Rich