Hi Rob, The basic idea of board/test files is: - A board file defines the chip, oscillator and pins used for specific tasks (like pwm, lcd in 4 and/or 8 bit mode etc). It assigns the logical name to a pin and defines a logical name for the corresponding direction pin (if required). - A test file uses there defines and of cource the registers for the functionality.
If for a specific board (chip)/test combination is lacking certain settings (like 16F88 to run i2c_hw_master), then compilation will fail and the sample will be removed. So the result is that only compilable samples will be generated. Of course this is not a guarantee that it works, but until now I haven't seen a sample that didnt... 2009/3/2 Rob Hamerling <[email protected]>: > > But the variations are bigger > than for the blink-an-LED samples. I think a properties-table is needed > to obtain a workable script. If you have suggestions: welcome! After the above, my question is what would that table do beyond the described above? Joep --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jallib?hl=en -~----------~----~----~----~------~----~------~--~---
