The "wizard" part could generate standard netlist / part list format for its own graphic representation, or import to schematic capture such as KiCad and Eagle. The 10Fxxxx, 12Fxxxx, 16Fxxxx and 18Fxxxx jal include files can offer the following:
1) Select Family in list Box, 10F, 12F, 16F, 18F, 18FxxJ or K 2) Via listbox with type ahead and only that family, select CPU 3) Graphic of Chip appears: Select package 4) Each pin has a text box (for user "alias blink_led as pin_b0" etc code generation) and a list box with select pin function. (all the info comes from existing JAL files). Tick box for SW or HW implementation (SW version of course increases possible options such as RS232 Serial or I2C) 5) Possible "Fuse" options are shown and user can edit list box/check box. 6) The code file with correct chip include, fuse pragmas and user alias and library includes is generated. The app searches the JAL include path for chip definitions and a user editable file that references libraries, so only the .ini/.wiz or whatever definition file (XML?) needs changed when libraries are added. Each library entry may need "pin features" required or chips or min/max clock speed. We should find a way of doing this in a library file rather than current adhoc comments about defining pins before the include statement. Any starter pack should have download links for kicad and Eagle as it's pretty stupid to not use schematic capture for circuit. It allows checking. Even plug in breadboard can be done with error checking in the Schematic -> PCB Layout part. -- 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.
