We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
For USB as a host, I require these two header files which is fundamentally used by other configure file.
Device: EFM32GG Application: USB HOST
Which is kind of getting away from the the point of using the CMSIS API's which are supposed to reduce the workload right?
Reducing, or change who does it, but perhaps not eliminated. It almost certain requires some work to change the paradigm, and become familiar with it. And it still requires buy-in by those you expect to conjure up the code and provide it to you. The model is presumably that the device vendor should do so, and that Keil/ARM provides some examples/templates.
I'm sure Keil is focused on the demands of license paying customers, with the most seats, and most popular/current micros.
Perhaps the file you are missing is device specific, with a generalize name for the other abstractions? www.keil.com/.../group__usb__interface__gr.html
Hi Weston,
I acknowledge and accept everything in your above message as I do ARM’s response and position. I have now moved to a different platform, which has the examples I need. Once I have all the elements for my project working, I will in all probability need to purchase a license (and I have a quote from them for future reference). I’m sure that ARM recognises the value of its MDK LITE as a gateway into embedded development for its students and tries to offer all the support it can. It’s just unfortunate that I chose a platform that didn’t have the examples I needed. But I guess that’s just par for the course and part of the learning experience.
Kind Regards to all