KDS IDE V1.0.1 MCU supported

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

KDS IDE V1.0.1 MCU supported

Jump to solution
1,265 Views
simonpietro
Contributor II

Hi All

I am wondering about the new KDS IDE V1.0.1.

This new version of KDS supports KW2 Kinetis family and BeeStack.

If isn't, presumably it will available in the future versions?

Regards

Simone

Labels (1)
1 Solution
801 Views
BlackNight
NXP Employee
NXP Employee

The W family is not yet supported in KDS, and subject of planning and further releases. I do not expect it to be supported in KDS in the near future.

As Marc is saying, it is a Cortex M4 part, so generially it is supported. But KDS does not come with dedicated Processor Expert or Kinetis SDK support for it it.

Eric

View solution in original post

0 Kudos
6 Replies
802 Views
BlackNight
NXP Employee
NXP Employee

The W family is not yet supported in KDS, and subject of planning and further releases. I do not expect it to be supported in KDS in the near future.

As Marc is saying, it is a Cortex M4 part, so generially it is supported. But KDS does not come with dedicated Processor Expert or Kinetis SDK support for it it.

Eric

0 Kudos
801 Views
ignisuti_
Contributor IV

It's been almost a year since the last update on this. Has anything changed?

I'm now trying to port some old code from a MC13213 to a KW2x tower kit, but I can't find a way to program the tower kit via CodeWarrior or KDS.

I've also downloaded the BeeKit and exported a Solution to CodeWarrior. That gave me some odd results. It looked like it downloaded and I was debugging, but no code was visible on the screen. More like the Stack Pointer was off at some random address.

I don't need Processor Expert or any fancy support items as I plan to build all the code from the ground up. I just need a way to download code to the tower kit via a debugging tool that will let me step through and debug code. Can anyone help with this?

801 Views
simonpietro
Contributor II

2) Devices Supported in V1.0.1

===========================================================================

Processor Expert projects:

- All Kinetis ARM Cortex-M0+ and Cortex-M4(F) devices supported by Processor Expert.

Kinetis SDK projects:

- K64F (MK64FN1M0VMD12 only)

Bare Projects (no SDK and no Processor Expert projects)

- K64F, KL25Z

PS: The KW2 family is part of Cortex-M4(F) devices supported by Processor Expert...??

Simone

0 Kudos
801 Views
mjbcswitzerland
Specialist V

Simone

It is possible to develop and build projects for any Kinetis processor using KDS (it acts as an editor and make file manager for the GCC tool chain).

The question is whether you can debug comfortably with it on the processor in questio because it may be missing soem debugger suipport and register views, although I believe that these can usually be added as plug-ins.

Regards

Mark

0 Kudos
801 Views
simonpietro
Contributor II

Hi Mark,

I think that theoretically is possible to build project for all Kinetis but in practice is hard.

Infact , i launched the KDS to create a new Kinetis project,

and opened the File menu, then select New > Project > Kinetis Design

Studio Project to start the New Kinetis Design Studio Project wizard.

The wizard shows as list of Kinetis only this :

- Kinetis E

- Kinetis K

- Kinetis L

- Kinetis V

Do you know some workaround for Kinetis W?

Regards,

Simone

0 Kudos
801 Views
mjbcswitzerland
Specialist V

Simone

I use the K, E and L parts and haven't yet used the W parts.

In the case of L and E there is no real difference for a project setup (both contain the Cortex M0+ core and have the same code/data memory layout). The K and KW parts both contain Cortex M4 and have the same code/data memory layout so I would use a K setup to start with.

If you are however reliant on the environment setting up a framework with the correct header files etc. you may have to do this from hand in case there is really no help built in. It is also worth doing once so that you know where everything is and then are not so reliant of a certain tool.

Regards

Mark