Hello Marcin Kajor:
You have good suggestions there from Mark and Soledad.
In KDS if starting a new project for Kwikstik (K40DX256) there are two options:
One of these will generate hardfaults due to changes in silicon from Rev 1.x to Rev 2.x. Details in AN4445.
I am not sure which specific part number is in your Kwikstik, so I would try with both. Also make sure that the device MK40DX256xxx10 is specified in the J-Link debug configuration, as stated in the next document:
GDB Debugging with Kinetis Design Studio
Regards!,
Jorge Gonzalez
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------
Hi
To be more complete - CW10.6 is probably the "standard" IDE used with the Kwikstik (because it was the one available when it came out and, since the Kwikstik is quite old now, probably it is used only little with never tools) but they will all basically work.
For people who can only use free tool chains CooCox is worth a mention since it is quite slick (another Eclipse based one but streamlined to be very easy to work with) although is missing some debugger/device support.
The Kwikstik (all versions - controlled by a define "KWIKSTIK_V3_V4" for backward compatibility to V5) is also fully supported in the uTasker project µTasker Kinetis support (as seen there, there is a list of about 10 tool chains that it can be used with without needing to worry about compatibility or porting efforts).
For accelerated developments it can also be built and simulated (for testing and debugging) using VisualStudio (Express edition is also free). Below is a screen shot showing how the Kwikstik looks when worked with.
Regards
Mark
