CDC on KL27Z256

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

CDC on KL27Z256

961 Views
glennbrookes
Contributor I

Since updating form KSDK1.1 I'm having big problems with project implementing CDC virtual com using MKL27Z256.

I am not able to successfully move from the bare metal demo on FRDMKL27Z  (uses MKL27Z64) to my own board using an MK27Z356VMP4.

I really would prefer use processor expert (and now FreeRTOS) as I already have many components configured from before the update disaster.

Unfortunately the FSL_USB_CDC_Device component which looked just the job does not support the  KL27 family ??

 

Even when starting a new project from scratch the reuslts were the same,  I could get the project to compile and run on target but the USB would not enumerate.

A USB sniffer suggests there was no response to requests, as though the function to return device descriptor was not being called 

 

Any help / working demo would be gratefully received.

 

am using KDS 3.2 and have tried KSDS 1.2 and KSDK1.3. with applied KDS eclipse updates.

 

Thanks

Glenn

Labels (1)
Tags (1)
0 Kudos
Reply
3 Replies

642 Views
ivadorazinova
NXP Employee
NXP Employee

Hi Glenn,

No, it is not possible to use the component FSL_USB_CDC_Device in PEx for KL27Z256. Because this component is not supported by PEx with KSDK.

I suggest to use KSDK example without PEx.

All these examples you will find under C:\Freescale\KSDK_1.3.0\examples\frdmkl27z\demo_apps\usb\device\cdc\virtual_com

or use the newest KSDK 2.0 (your MCU is supported - without PEx)

C:\Freescale\KSDK 2.0\SDK_2.0_MKL27Z256xxx4\boards\frdmkl43z\usb_examples

I hope this helps.

Best Regards,

Iva

642 Views
glennbrookes
Contributor I

Hi Iva,

My project has a significant number of PEx components, and application code using the methods of those components for DMA, I2C, DAC, ADC, TPM,  GPIO and OSA tasks (FreeRTOS).  The only problem area is with USB.

On reading about KDSK 2 I notice,  processor expert has been dropped, and porting from KDSK1.2 to KDSK2 is a difficult job, with  creation of a new KDSK 2 project being the favoured method.

Before I embark on a move to KDSK2 can you confirm what work is required with the now redundant PEx components. 

Alternatively is it possible to build a KDSK2 library supporting USB CDC device and just make the relevant calls from my existing project, to minimise the work involved.  

Many thanks

Glenn

0 Kudos
Reply

642 Views
ivadorazinova
NXP Employee
NXP Employee

Hi Glenn, 

I apologize for my late response.

Please, what do you mean by redundant PEx components ?

PEx does not support KSDK2.0. Please see https://mcuoneclipse.com/2016/05/15/mother-of-components-processor-expert-with-nxp-kinetis-sdk-v2-0-...

You can take a look at Pins Tool

https://mcuoneclipse.com/2016/06/08/tutorial-muxing-with-the-new-nxp-pins-tool/

and also interesting article

https://mcuoneclipse.com/2016/01/29/first-nxp-kinetis-sdk-release-sdk-v2-0-with-on-demand-package-bu...

Best Regards,

Iva

0 Kudos
Reply