Hey thanks for the quick answer.
So following the recommendation
- from a new project - import the project KSDK_1.3.0 USB Host at
KSDK_1.3.0\examples\twrk65f180m\demo_apps\usb\host\cdc\cdc_serial
which creates a virtual project - host_cdc_serial_freertos_twrk65f180m mapped to
C:\Freescale\KSDK_1.3.0\examples\twrk65f180m\demo_apps\usb\host\cdc\cdc_serial\freertos\kds
then update the board files - board.c/.h files to reflect my custom board based on the K26
which are in a virtual folder /host_cdc_serial_freertos_twrk65f180m/board
and I think maps to the physical tree/files
C:\Freescale\KSDK_1.3.0\examples\twrk65f180m
I'm wondering it seems like the the USB adapter sources have a different OS Abstraction that the rest of the KSDK_1.3
cdc_serial.c uses
OS_Task_create(Task_Start, NULL, 4L, 3000L, "task_start", NULL);
which comes from
C:\Freescale\KSDK_1.3.0\usb\adapter\sources\sdk\adapter_sdk.h
were as say the "Low power manager RTOS demo" task is different
OSA_TaskCreate(task_lpm, (uint8_t *)"lpm", TASK_LPM_STACK_SIZE, task_lpm_stack, TASK_LPM_PRIO, (task_param_t)0, false, &task_lpm_task_handler);
Which is the latest leading edge? Is it OSA_TaskCreate() and do you know of any issues if the the USB OS_Task_create() is replaced/merged in with other nonUSB KSDK_1.3.0 OSA abstraction examples like the "power_manager_rtos_demo"?
many thanks