Hi
First time I've submitted to this group and unfortunately it has to be to ask some kind soul for some help.
For the last 5 years I have been supporting a 10-year old PIC 16C57 program by 'tinkering' - i.e by editing the assembler, using MPLAB and sending the HEX file to the factory for them to test it in the product hardware. This has been adequate for the low impact modifications that have been required.
However, I now have to do a serious modification to this program which will require *me* to do thorough testing. I have retrieved my MPSTART-16C chip programmer from its box (where it's been for the last 5 years) set it up and connected it to COM1 on a WIn98 PC using the 9-pin 'D' connector straight through lead supplied with the kit. Although MPSTART appears to successfully connect to the programmer without any 'squeeks', it will only ever read back all zeroes from any chip, blank or otherwise. The LED on the programmer *does* light up while comms are apparently occurring. The PICSTART manual does not specify the serial baud rate, number of data bits or parity (but does mention the use of hardware flow control).
I am hoping that the symptoms are not caused by a dead programmer but that I simply have the wrong comms configuration.
The last time the programmer was used, it was connected to a real
*DOS* PC but unfortunately I can find no notes about how I got it working first time round.So . . please can anybody confirm what the comms configuration should be?
TIA
pOTRice