AnsweredAssumed Answered

Changing processor - doesn't work on desktop after, export/download/processor type

Question asked by Robert Lewis on Apr 3, 2017
Latest reply on Apr 13, 2017 by Robert Lewis

I was able to download V2.0 and configure an MK60DN512VLL10 processor without problem on my desktop pc. I downloaded V3.0 of the config tool, and built a V2.2 SDK for the MK20DX256VLL10 processor with the IAR toolset and some middleware. When I try to use the MK20DX256VLL10 package nothing happens.


I successfully went to file /export/download/processor K type and the whole set downloaded. But when I try to use the above package again nothing happens. This works correctly on my Notebook computer but not the desktop. The first processor package I downloaded to the Notebook was the MK20DX256VLL10 so maybe that is related, and the first package I downloaded on the desktop was the MK60DN512VLL10 and that works.


I took the MK20dx256VLL10.mex file from the notebook and loaded it into the desktop. It fails to load and says:

When I check the SDK version it says v2.0 even though I am using V2.2.... I put that down to sloppy versioning in the tool but that is an assumption. The config tool on the notebook is v3.0 and the sdk is definitely v2.2, so I don't know why the config tool can't read its own .mex file. Something is misaligned somewhere.


Is there somewhere that the paths can be checked or changed on the config tool? This has stopped the project until we can generate the pin mux code.


Thanks for any help offered.