topic Re: Replaced Freedom KL25 - now OpenSDA doesn't work in Kinetis Microcontrollers

Replaced Freedom KL25 - now OpenSDA doesn't work

frankvanhooft — Wed, 02 Jan 2013 05:57:41 GMT

I've replaced the KL25Z128 on the Freedom board with a replacement KL25Z128 (after I killed the original one). Now when I try to connect to the board in CodeWarrior I get this message:

Error 17926. Target MCU mismatch. OpenSDA hardware only supports debugging the resident target processor.

Now what? It would appear from this error message that OpenSDA is locked to the "PKL25" processor on the Freedom boards, and placing an "MKL25" processor upsets it. Is this correct? (And why is it called "OpenSDA" anyway - shouldn't it actually be called "ProprietarySDA" or "ClosedSourceSDA"? But I digress.)

Any pointers on fixing this would be appreciated. Thanks.

Re: Replaced Freedom KL25 - now OpenSDA doesn't work

apanecatl — Thu, 03 Jan 2013 17:06:27 GMT

You will not be able to use the board, the mcus installed in the freedom boards are tied to them through their unique Kinetis ID, if the IDs do not match to what the firmware has been taught they should be, the board will not work.

Re: Replaced Freedom KL25 - now OpenSDA doesn't work

JimDon — Thu, 03 Jan 2013 17:20:15 GMT

Are you saying that you can not replace the KL25Z128 even with another KL25Z128?

You have to throw the board away?

I expected that you could use the SDA to debug your own hardware as long as it was the same chip.

Things like this have been done in the past, locking a debugger to a particular chip, but never to a unique instance.

Please say it ain't so!

Re: Replaced Freedom KL25 - now OpenSDA doesn't work

frankvanhooft — Mon, 07 Jan 2013 01:58:26 GMT

Well I'll be darned if I know why they call this the "Freedom" board with "Open" SDA. I've used many a development board in my time, and this one is close to the top of the list of "Proprietary, closed, limited-use only" boards I've had the misfortune to use. Someone at Freescale had a pretty strong sense of irony when they came up with those product names. Probably shooting for a career in politics.

There's no doubt that the programming interface is locked to the processor. Replacing the processor with an "identical" one most certainly does not work. Do Freescale really expect us to replace the entire board when we wire it to custom hardware and something goes wrong? Apparently they do. And do they tell us this fact on the Freedom board webpage or in the documentation? Not that I've seen.

Perhaps one day the source for the SDA processor will be released. Maybe. It gets asked a lot on these forums, but it hasn't happened yet. Being able to remove that restriction would be a huge step forward.

I've spent the past several days frustratingly attempting to find a way to program the KL25Z128, given that the SDA interface is deliberately broken. What's finally worked has been to take a revision 5 Kinetis KwikStik board, and wiring off the J-Link interface it provides. Here's how to hook it up:

For the 10-pin header J8 on the Kwikstik board:

1 - Vref (connect to the VCC on your KL25Z128)

2 - SWDIO

4 - SWCLK

9 - GNDdetect - tie this to GND

3 - 5 - GND

Other pins are no-connect. Note that reset is not connected, nor is it required. (Of course you need to disconnect the SDA chip on the Freedom board - however you do that is up to you.)

The little "power" switch on the KwikStik board must be "off".

Then in CodeWarrior you need to set the debug interface to J-Link. Make sure you select "SWD" in the appropriate sub-menu (tab) - it seems to default to "JTAG" and that won't work.

Finally, with this ugly hardware hacking, I'm back to where I was several days ago - able to program the KL25Z128 again. What a lot of pointless work and wasted time - Freescale certainly isn't making it easy for their customers. I hope this posting helps others. Good luck.

Re: Replaced Freedom KL25 - now OpenSDA doesn't work

pgo — Wed, 09 Jan 2013 06:18:49 GMT

Hi Frank,

I quite agree with the comments about OpenSDA and I'm still waiting for the information that would allow me to make use of it in an "open" fashion. This is certainly what the name implies and is supported by what appears to be official Freescale statement. Hopefully this will be rectified in the (near?) future.

However, in fairness, the debugger included in the Freedom boards is not opensource nor does it makes claims of being so. It is a particular application loaded using the OpenSDA bootloader. I believe it is a closed source debugger firmware produced by P&E micro and I can understand their preference for tying it to a particular chip type to prevent undermining their commercial products. I believe they have been somewhat stung previously in this area (people using what was meant to be limited use programming interface on a demo board as a general programmer.) Tying it to a particular chip using the UUID on the chip does seem a bit excessive!

Note that this application is not the same as the OSBDM-JM60 debuggers included on some of the other Freescale boards (e.g many tower boards). The source code for these is readily available.

bye

Re: Replaced Freedom KL25 - now OpenSDA doesn't work

gurindersinghgi — Wed, 09 Jan 2013 11:24:02 GMT

I totally agree , Being said "Open" i still haven't read about its source being open, more over There is NO literally NO LINUX Support , Freescale is stick to its silly PE Component which i personally, really don't like, and Great to hear that Freescale has dropped free support : if you want PE Component , well you have to buy it :smileysad: thats sad, now we have to

1st pay for CW, then for any PE component we need , then for GDB Debugger (Yes OpenSDA sounding open is really not open you even have to pay for even GDB , means how does that sound Open !!)

I am very very Dissapointed :smileysad:

Re: Replaced Freedom KL25 - now OpenSDA doesn't work

pgo — Fri, 11 Jan 2013 09:16:18 GMT

Hi Frank,

Just to point out some further options.

There is a CMSIS-DAP OpenSDA plugin that can be loaded into the FRDM-KL25 board that allows it to be used with a range of programs supporting that debugger interface e.g. Keil. There is some information here:

The step to use CMSIS-DAP to debug the Freescale freedom board &laquo; CooCox Forum

The latest version of USBDM provides a OpenSDA version that works with the FRDM-KL25. It supports Codewarrior and provided utilities allow unrestricted programming of any connected Kinetis chip. It turns the FRDM-KL25 in to a general purpose BDM. It is actually open source.

http://usbdm.sourceforge.net/

bye

Re: Replaced Freedom KL25 - now OpenSDA doesn't work

quevedo — Fri, 18 Jan 2013 12:11:27 GMT

Hello,

I had a similar problem with my FRDM board. I bricked the KL25 (I used the Flash app, and loaded an ELF file by mistake, and it protected my processor against program and erase), and replaced it on the board (MKL version). However, my CW10.3 continued debugging the board, until I uninstalled Beta version, and installed Release. From that moment on, the debugger app gives the same error message presented in the original post. I tried it in another computer, with CW beta, and it worked! Again, I installed Release version on the second computer... and now I only get the same error.

If I load the Flasher app, I am still able to load binary files, but I cannot debug it anymore.

Thanks for enlighting me about the problem. Even P&E support cannot find a solution. Now I noticed that I forgot to mention to support that the original KL25 was replaced.

I looked at the workarounds presented by pgo. Using the CMSIS-DAP demands another IDE, since CW does not support it. And I could not find the OpenSDA version for USBDM. Can anyone provide a direct link for the USBDM?

Thanks

Re: Replaced Freedom KL25 - now OpenSDA doesn't work

pgo — Sat, 19 Jan 2013 03:44:39 GMT

Hi Antonio,

The OpenSDA version of USBDM is included in the latest version 4.10.4 available at:

USBDM - Browse /Version 4.10.4/Installation at SourceForge.net

It is included as part of the installation (look in the menu USBDM 4.10.4->BDM Flash Images). You will also need the appropriate driver installation.

bye

Re: Replaced Freedom KL25 - now OpenSDA doesn't work

quevedo — Mon, 21 Jan 2013 10:51:35 GMT

Thanks. I am just having problems to install the driver. I am using a winXP 32-bit with an AMD 64-bit processor. I suppose I have to use the 32-bit driver... but when I connect my FRDM board with the USBDM loaded, I get an error installing the driver.

I used zadig to install the USBDM driver, and now it works perfectly. I have created a new project using USBDM connection, and now I can debug my project.

Does anyone know how can I change the debugger connection from OpenSDA to USBDM, in projects already generated?

Thanks

Re: Replaced Freedom KL25 - now OpenSDA doesn't work

pgo — Mon, 21 Jan 2013 13:25:36 GMT

Hi Antonio,

Try the following:

Run->Debug Configurations...
Select the Launch configuration in the Tree control on the left
Click the Edit button next to the Connection drop-down box
Change the connection type to USBDM ARM Interface
Change the connection frequency to 12 MHz.

bye

Re: Replaced Freedom KL25 - now OpenSDA doesn't work

quevedo — Mon, 21 Jan 2013 14:55:05 GMT

Thanks pgo! That worked perfectly!

Now I am back to business. I wonder if Frank, the original poster, tried USBDM.

Re: Replaced Freedom KL25 - now OpenSDA doesn't work

pgo — Mon, 21 Jan 2013 16:12:24 GMT

Glad to hear that it worked.

You indicated above that the driver install (.msi file) failed to install the drivers but zadig succeeded.

zadig creates a driver directory in the root of C: I believe. Would you be able to zip this and post it? It might allow me to work out what is wrong with the .msi file.This problem appears to be specific to AMD machines and I don't have one for testing.

Thanks

Re: Replaced Freedom KL25 - now OpenSDA doesn't work

quevedo — Tue, 22 Jan 2013 13:37:02 GMT

Dear pgo,

Here is the folder created by zadig, fully zipped.

Good luck!

Antonio

Re: Replaced Freedom KL25 - now OpenSDA doesn't work

pgo — Sat, 26 Jan 2013 04:50:45 GMT

Thanks Antonio,

Unfortunately I can't see anything special about the settings used compared to those in the installer. I'll have to look elsewhere.

Did you get an error message when you tried the USBDM 32-bit installer or did the installation just not work?

thanks for your assistance.

bye

Re: Replaced Freedom KL25 - now OpenSDA doesn't work

frankvanhooft — Mon, 28 Jan 2013 03:37:36 GMT

"I wonder if Frank, the original poster, tried USBDM."

I have not, although I'm pleased to see the activity here. I've set up our system with a J-Link from a KwikStik board (as I described above how to do) and we've been using that ever since - it's working quite well.

Re: Replaced Freedom KL25 - now OpenSDA doesn't work

quevedo — Thu, 31 Jan 2013 17:16:29 GMT

As far as I remember, my Windows tried to install the USBDM 32-bit, and at the end I got a message telling that the driver could not be installed, that's all.

Re: Replaced Freedom KL25 - now OpenSDA doesn't work

gurindersinghgi — Fri, 01 Feb 2013 05:04:20 GMT

I tried USBDM and its working fine for me , i do have an question as freescale stopped supporting linux , there is no Codewarrier 10.3 for linux and CodeWarrier 10.2 dosent support MKL25xxxx Series, so , is there any way setting up CMSIS /USBDM / etc. for gdb debugging under linux.

Re: Replaced Freedom KL25 - now OpenSDA doesn't work

pgo — Fri, 01 Feb 2013 06:30:55 GMT

Hi Gurinder,

There is a brief description of how to set up Eclipse+Codesourcery+GDB+USBDM here:

USBDM: CodeSourcery ARM

This is for windows but a similar setup works for Linux. The required GDB sprite is included in the latest USBDM Linux version.

I'm currently working on an Eclipse plugin that should make it a little easier to setup.

bye

Re: Replaced Freedom KL25 - now OpenSDA doesn't work

brionfinlay — Mon, 11 Feb 2013 19:57:15 GMT

Frank,

I have been trying to reproduce your solution with the kwikstick board but have not yet been able to get it to work.

I get an error "An error occurred while trying to write memory. The Debugger can not write memory."

I "disconnected" the SDA chip on the freedom board by cutting jumper J11 per the freedom board schematic. Is that what you did or did you do something more when removing the SDA chip?

I have examined the lines with an oscilloscope and have confirmed that the kwikstick is sending signals to the freedom board.

Were there any other settings that you changed in the debug configuration for the jlink?