Following up on tonight's talk, Micro Controller Usb Devices

[Antonio Sun]

Hi,

Excellent talk tonight, Jan. Pure Excellent!

I just want to follow up on my question, which is on the micro controller
programming side. Could you give us a brief idea what micro controller
programming is all about please, Jan?

I.e.,

- to read the voltage, or capacity, or RPM, can you just do a USB read, or
you have to do some programming, e.g., to have the MC to prepare the data
then put the data at dual band usb ram before reading? Same question goes
for the DAC converter as well. How ready-to-use it is? Briefly explanation
would be good enough for me.
- Beside programming MC to provide the above read/write, what other typical
things you can program the MC to do? I guess you can use complicated logic
when programming it, right?
- Do you think the following would be a typical real-life usage of the MCs?
You write to MC a certain bytes, representing some certain
commands/instructions; MC correctly interprets those instructions and
"calls" the "predefined procedures" to carry out the tasks. Then you send
out the instruction for reading back the data, and then read them back,
right?
- Since MC have no cache, then I guess to get the correct RPM value, you
have to pull the data from its USB as fast as possible, If so, it still
seems a problem to me that Linux is not a real time OS. I've leaned that MC
can get those readings at pretty predictable interval, but at the end of
the day, wouldn't how fast/predictable the USB host can read them back
still be the problem?

Last questions, please explain very briefly, how can the USB host know that
there are still unused USB bandwidths?

Thanks again for the excellent talk.

Antonio

PS, Scott, I didn't find the slides from the meeting info page @
http://gtalug.org/wiki/Meetings:2013-03. where can I find it?

Thanks.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gtalug.org/pipermail/legacy/attachments/20130312/32abfbd8/attachment.html>