TWR-KW21D256 versus TWR-KW24D512 programming

[ignisuti_]

I have both tower kits and have updated both so they are capable of MSD and Debug options. I've verified the correct firmware is on each via the SDA_INFO.HTM file.

I can program the KW21 board with my P&E Multilink from CW10.6, but not the KW24. Any suggestions on what I might need to check?

[mjbcswitzerland]

Hi

Maybe you can help - I have also both TWR-K21D256 and TWR-K24D512.

Neither of them can be worked with via the OpenSDA bebugging interface as they are delivered - this is the information that the TWR-K21D256 shows:

Board Name is: TWR-MKW21D
MicroBoot Kernel Version is: 1.05
Bootloader Version is: 1.10
Installed Application: PEMicro TWR-MKW21D256 Mass Storage App
Application Version is: 1.13
DUID is: 30133938-8F0281CF-374AD80E-B76DE678
EUID is: 2691A239-2068873D-1849FA19-957668D6
TUID is: 74823938-827381B6-372DB805-A6BBE577
TOA is: 86B6E505-BB4C2173-41D8FC3D-EEB43B9B
TOA2 is: 86B6E505-BF442213-2D14B424-B5F25614

SUID is: 86B6E505-473303CC-37239804-8003EC65

This looks like it is a mass storage application and not a debugger. On the P&E web site there is a newest version for thsi board which is presumably a debugger. However, unlike any other OpenSDA based boards from Freescale it doesn't look possible to program it by powering the board with the reset button held down.

How is it therefore possible to use the debugger on the board when it is not programmed and also doesn't allow it to be programmed? Is there another technique to activate the OpenSDA's loader on this board?

Regards

Mark

[mjbcswitzerland]

Hi All

Another confusing point to WIndows 8.1 or MAC OS X (and possibly Linux) users is that the demo software that is pre-loaded on the board gets immediately distroyed if the board is powered by the USB cable, due to the fact that the OpenSDA mass storage device thinks that some software is being loaded and deletes anything that happens to be there.

It took me some time to realise what was going on because I could have sworn that there was demo SW running on both new boards when I first powered them but both seemed to die and couldn't attach to the debugger. Only when loading code via mass storage device from Windows 7 did it actually run and it was again killed when powering with a Windows 8.1 PC.

So I'll need to work with Windows 7 - via mass storage loader - without debugger until some way can be found to update the old OpenSDA part....

Regards

Mark

[bobpaddock]

Prevent System Volume Information folder creation on USB

Windows 8 by default writes information to USB drives, this needs to be turned off (Microsoft should have never turned on in the first place!).  This causes no end of trouble with Embedded Devices that have no idea what to do with these things Windows is trying to feed them.

Lets hope Windows 10 (There are 10 kinds of people in the world, those that understand binary and those that don't) does better...  Windows 2 the next step in deevolution...

[mjbcswitzerland]

Hello Bob

Also MACs do the same so it is not just a Windows 8.1 thing - it just appeared with the Windows 8.1 upgrade.

I am aware of the actions involved since I analysed and updated USB-MSD applications to be able to handle it - discussed at µTasker USB-MSD Loader Mac OS X Compatibility

I would like to (temporarily) disable it on the Windows 8.1 machine that I am working with but none of the guides to do it are working - I can only use the regedit method (gpedit is missing) but then there is no windows search directory in the SOFTWARE\Policies\Microsoft\Windows folder as everyone writes there normally is. So I am stuck with it. That is why I just use a Windows 7 machine instead when working with the boards (although without any debugging capability).

On the other hand I prefer to mostly have is like this so that I can check compatibilities - my post is not essentially to ask for help in disabling the behaviour but rather to see whether anyone knowns how to update the old OpenSDA on the board (to add debugging) - the same issue has been there for many other Freescale boards that I test but this is the first one that can't update itself!

It is more a heads up for people receiving new TWR-KW2x boards (with old OpenSDA) and having the impression that the board "dies" after a few seconds (which was my first impression unti I realised it did the same on each new board that I tried with).

Regards

Mark

[bobpaddock]

"...there is no windows search directory ..."

No there isn't, as explained in step#3 "Windows Search", note the space, must be created as a new key.

Once the key is there, changing the value between '1' (don't mess up USB devices) and '0' for screw up the world, will let you have it both ways with an annoying regedit/reboot cycle.

[mjbcswitzerland]

Bob

Thanks for that; I missed the fact that the key had to be created!

Since I reboot on average once every 10 weeks (when something finally goes wrong with the system and there is no choice) I am not a fan of the reboot needed between changes (also going through the complicated way of allowing it to load unsigned drivers since some of the development tools required won't work without this setting) but I'll give it a go at next opportunity.

Regards

Mark

[jeremyzhou]

Hi Joe,

After had a brief look through your statement, I've got that TWR-KW24D512 can be able to debug or program through OpenSDA interface, however failed via P&E Multilink. But TWR-KW21D256 can work well with both of these tools.

I'd like to suggest that you need to check the hardware configuration of the TWR-KW24D512 likes the jumper connectors setting.

And I was wondering if you can share the error of P&E Multilink program the TWR-KW24D512.

Hope it helps and I'm looking forward to your reply.
Have a great day,
Ping

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

[ignisuti_]

Jeremy,

The jumpers look correct to me. They match the other development board which appears to be working fine.

Attached are the errors I'm seeing.

[ignisuti_ · Accepted solution]

Okay, I got it going. My Target Type was the issue.

I had it configured for a 256 part thinking it would work for both 256 and 512, but turns out it's the other way around. When I configured it for a 512 part, it worked on both.

[jeremyzhou]

Hi Joe,

I'm glad to hear that you had figured out the root cause of this issue.

If you have any further questions about it, please feel free to contact with me.

If you don't have, would you please help to close this SR? Then you'll receive a survey in a moment and please fill it out.

Thanks a lot.
Have a great day.
Ping

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