Ok, this old phart will figure something else out... LOL!
The goal was to save you time.
So, unless you have something quick, like a screen grab or something, I'll figure out a way around this.
It sort of looks like Shaggy did a good job if scanning through the code and changing pieces. There still needs to be some debugging - which is normal. I mean he's changed many of the I/O pins; there's bound to be a reversed pin or reversed tris bit, etc. One little "1" instead of a "0" could cause all sorts of interesting stuff..
I'm trying to figure out how the code can be **sort of** processor independant, at least with the ones we're using. ( 4011, 6015, 6010A )
In that light, it seems like some small mods to how things are defined and initialized should do that. It may be possible to do something kind of smart like an "if this processor, call this header"
It also looks like there is some redundant code in the UART.c - I need to look into this closer...
- E*clipse