600+ errors when building K60D100M Demo Project

[steeevo]

Hi, I'm new to programming with kinetis. I did get a simple program running with KDS, but in wanting to learn more about more feaures on the board I wanted to compile and reload the board with the demo project aht the board comes with out of the box.

In doing so, I read that I need to install Codewarrior as well as MQX, which I did. I compiled the libraries and tried compiling the demo project but I'm getting all kinds of errors when compiling the demo project. the libraries seem to compile just fine.

Does anyone have any insight on what the issue may be?

Also, are there any books on programming these tower boards with KDS or code warrior? more specifically working with the various data bus types I2C, UART, CAN etc?

Thank you

[steeevo]

That was a great response.

After reading this googling around today I'm convinced that I should use an OS.

for a little insighn on my first project I'll be working with CAN bus protocols such as NMEA2000, J1931, K-Line and other similar CAN bus networks.

I also have another project that will need to send out multicast messages over TCP/IP

It also seems like Freescale pushed their own OS, MQX what are your thoughts on MQX?

[mjbcswitzerland]

Steven

For CAN see http://www.utasker.com/docs/uTasker/uTaskerCAN.PDF (and video at FlexCAN.wmv - YouTube)

For Multicast (IGMP) see http://www.utasker.com/docs/uTasker/uTasker_IGMP.pdf

I can't comment on MQX since I don't use it - you will need to make your own tests to find out what works best for you.

Regards

Mark

Kinetis: µTasker Kinetis support

K60: µTasker Kinetis TWR-K60N512 support / µTasker Kinetis TWR-K60D100M support / µTasker Kinetis TWR-K60F120M support

For the complete "out-of-the-box" Kinetis experience and faster time to market

[steeevo]

For some reason the Debug version won't compile but the release version does.

however, I can't get the memory game to work nor does the http server respond.

The accelerometer demo, touch pad demo, usb mouse demo, and terminal demo work fine. 

I haven't tried the SD card yet

Any info on this issue would be appreciated.

But I'm still interested in books on kinetis using either KDS or codewarrior.

[mjbcswitzerland]

Steven

If you have difficulies with Ethernet carefully check the jumper settings - see chapter 7 of http://www.utasker.com/docs/KINETIS/uTaskerV1.4_Kinetis_demo.pdf

See also the following:µTasker Kinetis TWR-K60D100M support which gives a reference for testing the Ethernet on your board. Note especially the warning in red there about the backplane reset line (can hold the Ethernet PHY in Reset) being connected to the SD card, depending on the position of J1 on the TWR-K60D100M.

I never heard of a book on these subjects. There are a couple of more general ones listed at:

http://mcuoneclipse.com/books/

Otherwise there are many documents and articles that can be studied.

Regards

Mark

Kinetis: µTasker Kinetis support

K60: µTasker Kinetis TWR-K60N512 support / µTasker Kinetis TWR-K60D100M support / µTasker Kinetis TWR-K60F120M support

For the complete "out-of-the-box" Kinetis experience and faster time to market

[mjbcswitzerland]

P.S.

It may be that the debug target is set up to run in SRAM and won't fit when you have  lot of functionality enabled.

P.P.S.

You can find documents on using most Kinetis peripherals at µTasker - Documentation

Regards

Mark

Kinetis: µTasker Kinetis support

K60: µTasker Kinetis TWR-K60N512 support / µTasker Kinetis TWR-K60D100M support / µTasker Kinetis TWR-K60F120M support

For the complete "out-of-the-box" Kinetis experience and faster time to market

[steeevo]

Thanks Mark, I'll go through those documents that you posted.

But Before I go through those examples etc. ..I have a few more questions.

What is uTasker? is this still part of freescale? and I'm still confused as to if I should be using codewarrior or if I should be using KDS. I did get a small sample project running in KDS being that it seems to be a bit more

Can you explain the advantages of each? as well as why I would want to run MQX or another RTOS over just running my program on the bare board?

I know this is a lot of questions but I do appreciate  you reponding to me or even giving me documents to read on the IDE's

I just don't want to jump in feet first and hit some limitation that causes me to start over in another IDE.

[mjbcswitzerland]

Steven

uTasker is a framework for Kinetis which allows all KE, KV, KL and K parts to be used with (almost) any IDE and with a single project code (including a boot loader supporting various methods [with KBOOT compatibility for all boards] and an application framework which has been verified on all boards and in all configurations, so needs no porting or further work for industrial usage). That means that almost all Kinetis drivers are include, TCP/IP stack with many protocols, USB device stack, graphics library, MODBUS stack, file systems, plus it allows simulation in (approx.) real time to make development, debugging and maintenance as efficient as possible. IDEs that work with it are at:

http://www.utasker.com/kinetis/compilers.html

uTasker is not a part of the Freescale SW. It is a development that has been performed for HCS12, Coldfire and Kinetis parts (concentrates on certain Freescale parts) and there has been a certain amount of interraction with Freescale over the years but no direct links. The history of the project is at µTasker history. The project is supported (here, at the uTasker forum: µTasker Forum - Index or personally by email or telephone for registered users).

If you are using new Kinetis parts you MUST use KDS since CW won't support them. The K60 is on the boarder-line; if you find it works with KDS you should go for that, otherwise you will need to use CW. uTasker users don't have any issues since they can switch between the two and other IDEs without any concequences (apart from a potential learning curve to get the most out of the individual IDE debugger's capabilities if there are big differences). Since KDS and CW are however almost identical (although projects created with one can't be opened by the other) there is almost zero learning involved when moving between them.

The uTasker uses a simple co-operative scheduler which suits users who prefer to be in the bare-metal area (which is a surprisingly high percentage of companies - the biggest worry of many is that its approx. 2k of OS code is already too much overhead and added complication....). You will need to compare yourself since there are often personal preferences involved rather than real technical reasons. In any case, an OS (or simple scheduler) will usually make any project development easier, faster and more reliable. Today however one "understands" the drivers, stacks, libraries etc. as part of the "OS" and so having code that has been optimised and proven in many projects over long periods of time will usually be a better starting point that writing everything from scratch.

If your project is very simple then there is no reason to use an OS. But as soon as it gets to a point where there are more than one or two interfaces and modules needed to be maintained you will probably find it helps a great deal to use one. Also, it is possible to "successfully" build projects using many methods - including writing everything from scratch in assembler. It will certainly work but it will tend to take many times longer and be much more difficult to maintain than using a framework that has been shaped through many years of work specifically for the job (in each case the project will be "successful" but it may have taken 10x the time and effort to reach the same definition of successful). Basically if you find yourself investing more than a day or two writing and debugging code that is not specific to your actual application (that is code and functionality of the project that involves drivers, general peripherals, standard communication stacks or internal process control) then this is probably time that could have been saved by building the application on an existing framework.

Regards

Mark

Kinetis: µTasker Kinetis support

K60: µTasker Kinetis TWR-K60N512 support / µTasker Kinetis TWR-K60D100M support / µTasker Kinetis TWR-K60F120M support

For the complete "out-of-the-box" Kinetis experience and faster time to market