Getting started with an MK20DN

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

Getting started with an MK20DN

2,227件の閲覧回数
ryan_pearson
Contributor III

I am trying to get started with an MK20DN64VFM5 that we've committed to using on our board.  I've tried several ways to get it going with no luck.  I tried the getting started steps for the FRDM-K20D50M found here.

 

FRDM-K20D50M|Freedom Development Platform|Kinetis | NXP 

 

I hit a snag in the getting started guide when the hello world project does not build in IAP.

 

I have also tried generating a simple project with KDS, and choosing MK20DN64xxx5 as the device.  It builds.  I tried to debug with a segger j-link to no avail.

 

Can you provide the settings I should use in the debug configuration GUI for a j-link?  Is there a better getting started guide I should follow?

ラベル(1)
0 件の賞賛
返信
7 返答(返信)

2,121件の閲覧回数
Sabina_Bruce
NXP Employee
NXP Employee

Hi Ryan,

Thats good news!

You can also take a look at the following examples for the K20. It may help you as reference, let me know if you need anything else.

Kinetis 50MHz bare metal sample code 

Thank you,

Sabina

0 件の賞賛
返信

2,121件の閲覧回数
ryan_pearson
Contributor III

Thanks, I'm having trouble porting the IAR/CW code intro KDS, however.  I managed to compile it, but received a code generation error.  Is there an example made for KDS? 

0 件の賞賛
返信

2,121件の閲覧回数
ryan_pearson
Contributor III

Alternately, I'm having trouble building examples in IAR.  I get the error "Cannot open source file "freedom.h".  I'm not sure where to add search paths, if that's my issue in IAR.

0 件の賞賛
返信

2,121件の閲覧回数
ryan_pearson
Contributor III

Actually, I see the include directories under Pre-processor.  "$PROJ_DIR$\..\..\..\src\platforms" is already there, where the freedom.h file resides.

0 件の賞賛
返信

2,121件の閲覧回数
mjbcswitzerland
Specialist V

Hi

https://github.com/uTasker/uTasker-Kinetis
FRDM-K20D50M supported in KDS and IAR

http://www.utasker.com/kinetis/compilers.html
https://www.youtube.com/watch?v=K8ScSgpgQ6M

Download, build and productive work can begin.....

Regards

Mark

0 件の賞賛
返信

2,121件の閲覧回数
Sabina_Bruce
NXP Employee
NXP Employee

Hello Ryan,

From the behavior you are experiencing I would recommend checking the hardware on your board and making sure it is the same as the debugger in the Kinetis Peripheral Module Quick Reference. I would also make sure you have the latest Segger drivers you can use the following document as a reference:

Updating Segger Tools in Eclipse Kinetis Design Studio | MCU on Eclipse 

Once you have reviewed the hardware on your board and updated the drivers try running your simple project on KDS again and let me know the results. 

Thank you,

Sabina

0 件の賞賛
返信

2,121件の閲覧回数
ryan_pearson
Contributor III

Thank you, we did discover a hardware problem and are now able to debug with our j-link.

I'm now building and debugging with KDS.  I tried to configure and toggle a port pin with no luck so far.  I suspect I'm missing a lot of processor initialization code in my project, and I am now planning on copying one of the IAR examples into KDS.

0 件の賞賛
返信