Sending strings using USB_Class_CDC_Send_Data

kevinlfw — Tue, 26 Jul 2016 15:36:07 GMT

I'm using the USB CDC VCOM code found in KSDK 1.3.0 and I'm attempting to write a string to my terminal. The call is simple:

USB_Class_CDC_Send_Data(applicationHandle, DIC_BULK_IN_ENDPOINT, "Hello, World!", 13);

I've also tried casting (uint8_t*)"Hello, World!". Both methods print some non ASCII characters:

So I played around with it and did this:

uint8_t *buffer;

buffer = malloc(size);

memcpy(buffer, "Hello, World!", 13);

USB_Class_CDC_Send_Data(applicationHandle, DIC_BULK_IN_ENDPOINT, buffer, 13);

and it prints:

I don't believe I should have to copy the buffer in order to print the message, so what am I doing wrong; or what is the SDK doing that's preventing me from simply printing out a specified byte sequence.

Re: Sending strings using USB_Class_CDC_Send_Data

ivadorazinova — Thu, 18 Aug 2016 13:28:27 GMT

Hi Kevin,

I apologize for the late response.

This behaviour is expected and is correct.

If you refer to structure of the function, there is expected pointer on buffer.

uint8_t* app_buff,

usb_status USB_Class_CDC_Send_Data

(

cdc_handle_t cdc_handle,

uint8_t ep_num,

uint8_t* app_buff,

uint32_t size

)

Because - if you hand over text parameter (instead of pointer on buffer), there will be displayed content which is on this address in hexa.

I hope this explains your question.

Best Regards,

Iva

Kinetis Software Development KitのトピックSending strings using USB_Class_CDC_Send_Data

Sending strings using USB_Class_CDC_Send_Data

Re: Sending strings using USB_Class_CDC_Send_Data