Kirk Wallace wrote: > I have the first pass of my AVR PWM interface working. I have two .comps > (conv_u32_bits.comp, pd_strobe.comp, > http://www.wallacecompany.com/machine_shop/EMC2/AVR/ ) > > that convert a u32 to individual bits that I can hook up to parport > pins, then a delay so that I can strobe the data latch on the AVR. This > may be a silly question, but, it seems that the parport driver's main > function is to break the data register into bit pins, should I look at > simplifying or adding a u32 pin to the parport driver to write a byte > rather than pins? I don't want to invest a lot of time figuring this out > if what I am already doing is the best I can do. > I wouldn't be opposed to having an option (like in and out) to treat the data port as a number instead of an array of bits. I don't have a strong opinion on whether should be a load-time option like in/out or another driver, either would work fine. > Right now I'm getting a four bit nibble input every servo period. In the > long run, I hope to get an eight bit byte into the AVR every other base > period (data on odd, latch on even). > Hmmm. You might think about making a "parport data" driver. Address input, R/W select input, data in/out ... I'm not sure exactly how it should work, but the idea is more or less to treat the port as a parallel port instead of as an array of pins.
- Steve ------------------------------------------------------------------------------ Lotusphere 2011 Register now for Lotusphere 2011 and learn how to connect the dots, take your collaborative environment to the next level, and enter the era of Social Business. http://p.sf.net/sfu/lotusphere-d2d _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
