Lots of different kinds of drivers available and basically they take an input signal (usually low voltage/low current) and output a signal (usually higher voltage/current) capable of driving whatever it is connected to. The driven device could be for communications (line drivers), sensors (ultrasonic, IR, light, magnetic, RF, etc), mechanical devices (motors, solenoids, etc) or electrical (lights, heaters, etc).
Miles, you can't just run a driver; you must run a demo app that uses it. The demos provide example code that shows how to start the driver and use its methods. In the proptool, in the dropdown above the current directory view, select "propeller library - demos" instead of just "propeller library." Then pick something like tv_text_demo.spin and click on that. You might have to rejigger the pins but most of the parallax written demos will run as is on a demoboard (like duh). Then you can look at the code and see how the demo includes the tv_text object, starts it up, sets the pins up, and how you call it to display text.
Another way to think of what's called a driver is that of a pre-written piece of code that takes care of the details of managing a particular I/O device or class of devices. TV.spin for example manages the details of generating a TV signal that displays a buffer of "tiles" which are 16 x 16 pixel or 16 x 32 pixel areas of the TV screen. These tiles can be used for characters or graphics.
Comments
Thanks,
Miles