RE: C-header generator

Former Member — Thu, 02 Dec 2010 14:18:12 GMT

I think it should be the schematic which would define the pin names. The schematic pins should be annotated with pin directions, maybe from the IC library. They can be in, out, i/o, or special/alternate function. This would allow the header generator to define either specific pin names for each, or a generic name which supports all directions and special or alternate functions.

RE: C-header generator

Former Member — Mon, 19 Jul 2010 13:29:29 GMT

Matt Collinge wrote on Mon, 19 July 2010 08:50

I think a tool (or a script, TBD) able to read .sch file and generate
.c/.h file with #define will spare a lot of time.

I mean something able to outputs something like (in case of a PIC):

#define PORTAbits.RA3 LED

I have something like that in my PIC http://www.embedinc.com/pic but it

doesn't interface with Eagle. Check out the

http://www.embedinc.com/pic/prepic.txt.htm commands /INBIT and /OUTBIT.

These allow you to define a symbolic name for each I/O line and how it is

used.

I hadn't thought of merging this with Eagle schematics, but that's a good

idea. I'm not sure which direction it should work in though. If starting

with Eagle, the net name connected to a pin can become the pin name in the

PIC source code, but it won't know the pin direction. It will be tricky to

automate this, but it could be possible. Going the other direction may

make more sense in that the source code should probably be the master

definition and the schematic should reflect it. However, I don't think pin

directions can be changed on the fly for a instance of a part in the

schematic. Actually this is a problem with both methods.

Web access to CadSoft support forums at www.eaglecentral.ca. Where the CadSoft EAGLE community meets.