Hello good people!
I can only find host/device examples, and I would like to understand how to use the OTG MQX driver, through the MAX3353 chip in my TWR-K60D100M (and later port it to my custom board).
There is not USB OTG support in stack for now.
The MAX3353 is therefore bypassed.
Hello, what does it mean "to use"? Do you want to use the OTG capability, i.e. to change the function from host to device and vice versa?
Exactly. I want my board to be dual - once it will act as a host, and other time as a device.
I've noticed that the MAX3353 chip is part of the TWR-K60D100M, and is controlled by I2C lines. I know that there is an USB OTG driver support in MQX, but couldn't find any code examples.
Are there any plans for the near future?
Yes. Please take this information as not confirmed yet, but after MQX 4.0.1 release there is plan to incorporate OTG functionality. Some work is already done.
We have been waiting for OTG and Composite device in MQX on kinetis for over a year.
Medical Stack v4 has these. What is the hold-up?
Please let us know what timescale we still have to wait before this might be completed.
excuse me, but I am not marketer or decision taker, so I can never tell you the exact date. It's not up to me to decide. I know only that there are plans after 4.0.1, but if the plan will not be approved because of higher priority things the implementation will be postponed later.
Juraj, I understand - not your fault.
I was really hoping composite device and OTG would be in 4.0.0
Now that it is not, I wonder how many more months our product development will be held up. We don't need HNP etc., just a simple CDC/MSD (device) + HID/printer (host) example.
"Plug into a PC, get a removable drive, plug a printer in and press "print", get hard-copy output.
Is it true there is no public "roadmap" for MQX releases? We just have to "wait and see"?
unfortunatelly we do not publish any official roadmap. For now, you can use MCU with more controllers and you can enable the functionality for both of them. But probably this is not the case you are interested in.
Retrieving data ...