MK10DX256VLH7, Have you ever programmed this part?

[toddheckleman]

Hi everyone,

This is a hard question that may not have an answer.  

 How do you setup MCUXpresso to program a MK10DX256VLH7?   

We are trying to port MK02 code to a MK10DX256VLH7 and there appears to be no way to even program the device let alone port code to it.   I find this hard to believe and NXP would not allow this to happen.   Talk about code protection, LOL. 

We designed in a  MK10DX256VLH7 and now it appears that we are stuck. 

Any comments, suggestions, opinions would greately be appreciated.   

Thank you for your time and any help you can provide. 

[mjbcswitzerland]

Hi Todd

if you don't find a K10DX256 debug target try using K20 or K60 equivalents. As long as there is no check for the exact part number the flash is the same and should program.

For the next product development consider the uTasker project as base since it ensures operation on all Kinetis parts without needing to port code (note also that a K02 project will run on K12 as long as a few basic shared options are used - eg. ensuring the FPU is not enabled and that DMA channels use is restricted to 4).
Furthermore it allows you to use KDS, MCUXpresso and various other tools with no additional effort - using KDS or CW you will find it easier to work with older parts like the K10 since they were main steam when these tools were 'in'. The newer tools look to be focusing more on newer parts.

Regards

Mark

Complete Kinetis solutions, training and support: http://www.utasker.com/kinetis.html
Kinetis K60/K10:
- http://www.utasker.com/kinetis/TWR-K60N512.html
- http://www.utasker.com/kinetis/TWR-K60D100M.html
- http://www.utasker.com/kinetis/TWR-K60F120M.html
- http://www.utasker.com/kinetis/ELZET80_NET-KBED.html
- http://www.utasker.com/kinetis/ELZET80_NET-K60.html

[toddheckleman]

Hi Mark

Thank you for the response, I will look in the u-tasker project. The K12 has a few wiring reworks that we are trying to avoid. We may have to to get the project out in a weeks time.

Thank you

Todd

On Monday, April 8, 2019, 8:03:03 PM EDT, mjbcswitzerland <admin@community.nxp.com> wrote:

|

NXP Community

|

Re:  MK10DX256VLH7, Have you ever programmed this part?

reply from Mark Butcher in Kinetis Microcontrollers - View the full discussion

Hi Todd

if you don't find a K10DX256 debug target try using K20 or K60 equivalents. As long as there is no check for the exact part number the flash is the same and should program.

For the next product development consider the uTasker project as base since it ensures operation on all Kinetis parts without needing to port code (note also that a K02 project will run on K12 as long as a few basic shared options are used - eg. ensuring the FPU is not enabled and that DMA channels use is restricted to 4).

Furthermore it allows you to use KDS, MCUXpresso and various other tools with no additional effort - using KDS or CW you will find it easier to work with older parts like the K10 since they were main steam when these tools were 'in'. The newer tools look to be focusing more on newer parts.

Regards

Mark

Complete Kinetis solutions, training and support: http://www.utasker.com/kinetis.html

Kinetis K60/K10:

- http://www.utasker.com/kinetis/TWR-K60N512.html

- http://www.utasker.com/kinetis/TWR-K60D100M.html

- http://www.utasker.com/kinetis/TWR-K60F120M.html

- http://www.utasker.com/kinetis/ELZET80_NET-KBED.html

- http://www.utasker.com/kinetis/ELZET80_NET-K60.html

Reply to this message by replying to this email, or go to the message on NXP Community

Start a new discussion in Kinetis Microcontrollers by email or at NXP Community

Following Re:  MK10DX256VLH7, Have you ever programmed this part? in these streams: Inbox

This email was sent by NXP Community because you are a registered user.

You may unsubscribe instantly from NXP Community, or adjust email frequency in your email preferences

[mjbcswitzerland]

Todd

I have developed a product that uses either a K02F or K12 since they are foot-print compatible (in this application at least) and the same binary operates (as long as a few non-common peripherals are avoided) on both. The reason was due to second sourcing due to supply chain difficulties last year.

Your application or hardware design may have exceptions and not allow this.

Regards

Mark

[kerryzhou]

Hi Todd heckleman,

   This question is the same post as your another post:

What tools are used to program the MK10DX256VLH7?,  

  Which I already reply you.

Wish it helps you!

If you still have question about, please kindly let me know.
Have a great day,
Kerry

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

- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------