I am progressing very well with my rs232 project using the PIC16F877A and can now send various rs 232 byte commands from several push button commands on input ports of the chip.
It will also work with PIC16F876A.
However IT will not work with either PIC16F88 or with PIC16f628
I am making sure that all jumper settings are ok on RS232 E-Block and that flow code settings are set correctly.
When using PIC16F88and trying to programme it, all I get is this message:-
"Flowcode was unable to compile the flowcharts C code due to the following errors:
No compilation error information is available"
The flow chart that I am using is identical to the one I have been using with PIC16F877A apart from telling Fowcode that the chip is a different one.
As for the PIC16F628:-
The chip appears to be getting programmed OK, its just that it doesn't do any thing apart from LB2 LED being lit.
I am still going forward which is the main thing but am still confused as to why the other two chips wont work.
Any help will be appreciated.
RS232
- Steve
- Matrix Staff
- Posts: 3433
- Joined: Tue Jan 03, 2006 3:59 pm
- Has thanked: 114 times
- Been thanked: 422 times
There is a trick to see the compilation errors, which might explain more about why the 16F88 program is failing. See this topic:
http://matrixmultimedia.com/mmforums/viewtopic.php?t=36
I'd also suggest making sure your program does not access PORTC anywhere (including in the property page for the RS232 component - i.e. with the hardware flow control settings) - PORTC exists on the 876 but not on either of the other chips you mention.
If you're still stuck, please send the FCF file to our support address and we'll see what we can do.
http://matrixmultimedia.com/mmforums/viewtopic.php?t=36
I'd also suggest making sure your program does not access PORTC anywhere (including in the property page for the RS232 component - i.e. with the hardware flow control settings) - PORTC exists on the 876 but not on either of the other chips you mention.
If you're still stuck, please send the FCF file to our support address and we'll see what we can do.