KL27Z256 USB CDC communication using KDS 3.0/KSDK 1.3.0 and PEx

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

KL27Z256 USB CDC communication using KDS 3.0/KSDK 1.3.0 and PEx

Jump to solution
1,242 Views
andrelemke
Contributor III

Hi! I'm new here in this community and in the world of ARM processors...

 

I'm working with the KL27 microcontroller series and I had some problems to make USB CDC communications work.

I follow some articles on the internet, and I saw that some people had troubles with the Kinetis Software Devlopment Kit, and solve it in simple ways.

 

The main problem is that I'm using the KL27Z256 microcontroller in a project. I can't use de "virtual_com" example provided by KSDK, because it's dedicated to KL27Z64 or FRDM-KL27 and I'm not getting sucess changing just the series number of microntroller in the compiler configurations.

Well... I found another article on the web, in this forum I think, here is the link: USB Device CDC on KSDK PEx components and KDS 3.0 and KSDK 1.2.0 or KSDK  1.3.0 .

 

I used the component "fsl_usb_framework" provided by the Processor Expert Library, configured it, and included the libraries from the directory: C:\Freescale\KSDK_1.3.0\usb\usb_core\device\sources\classes.

I tried to use the "fsl_usb descriptors" to generate the "usb_descriptor.c/.h" archives and can't initializate the components. I think it's a bug from PEx!?

 

Finally, it doesn't work. My Windows show a message like: "unknown device" or "driver error". The image below shows it (sorry portuguese):

 

128290_128290.pngpastedImage_3.png

 

I updated the driver from the "virtual_com" example ".inf" for FRDM-KL27Z, and it doesn't work.

 

Somebody know how can I change the target processor of the "virtual_com" FRDM-KL27Z app example for the KL27Z256 processor?

If we could use the Processor Expert tools with the KSDK  is the best way for me, because I need to use the SPI interfaces and LPUART, and it's the best way for me in this time.

 

Thank's!!! Sorry my English...

Labels (1)
1 Solution
562 Views
PitOn
Contributor III

p.s

Check Set Build Options

Stack Size 0x1000

Heap Size 0x0400

View solution in original post

3 Replies
562 Views
PitOn
Contributor III

Hi !

Temporarily give up mode CDC, check in the other mode are supported PE , for example HID.

Best regards.

Konstantin.

563 Views
PitOn
Contributor III

p.s

Check Set Build Options

Stack Size 0x1000

Heap Size 0x0400

562 Views
andrelemke
Contributor III

Hi Konstantin Grjznov!

Really Thank you for repply!

I tried to change the configurations like you sad. But doens't work again.

It's funny because I tried contrary what you said, and it works.

The configuration that I used is shown below:

pastedImage_0.png

The driver was recongnized, and the communication is ok!

pastedImage_1.png

A test is shown below:

pastedImage_2.png

Really thank you Konstantin!!!

0 Kudos