PIC 16C57 - yes - a 10 year old project needs modifying - please read

Discussion in '8bit Microcontrollers' started by pOTRice, Mar 10, 2008.

  1. pOTRice

    pOTRice Guest

    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
     
    pOTRice, Mar 10, 2008
    #1
    1. Advertisements

  2. pOTRice

    Tom Guest

    Re: PIC 16C57 - yes - a 10 year old project needs modifying - pleaseread

    pOTRice wrote:
    > 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

    As far as I can remember, it used 9600 8N1
    I still have mine around here someplace too. :)
     
    Tom, Mar 10, 2008
    #2
    1. Advertisements

  3. pOTRice

    pOTRice Guest

    On Mon, 10 Mar 2008 21:25:57 GMT, Tom <> wrote:

    >pOTRice wrote:
    >> 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

    >As far as I can remember, it used 9600 8N1
    >I still have mine around here someplace too. :)



    Many thanks for your quick reply Tom.
    However, that was just the answer I didn't want to hear - that was the
    first setting I tried (it was the default in Win98).
    Starts to look like it may be the programmer.
    A first trawl around the net suggests that the 16C57 really is
    unsupported now. (I have no idea where my client actually buys them)
    Some of the third parties' programmers specifically exclude it.
    I believe I may have access to another MPSTART-16C programmer so may
    be able to borrow that.

    Thanks again

    pOTRice
     
    pOTRice, Mar 10, 2008
    #3
  4. pOTRice

    Tom Guest

    Re: PIC 16C57 - yes - a 10 year old project needs modifying - pleaseread

    pOTRice wrote:
    > On Mon, 10 Mar 2008 21:25:57 GMT, Tom <> wrote:
    >
    >
    >>pOTRice wrote:
    >>
    >>>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

    >>
    >>As far as I can remember, it used 9600 8N1
    >>I still have mine around here someplace too. :)

    >
    >
    >
    > Many thanks for your quick reply Tom.
    > However, that was just the answer I didn't want to hear - that was the
    > first setting I tried (it was the default in Win98).
    > Starts to look like it may be the programmer.
    > A first trawl around the net suggests that the 16C57 really is
    > unsupported now. (I have no idea where my client actually buys them)
    > Some of the third parties' programmers specifically exclude it.
    > I believe I may have access to another MPSTART-16C programmer so may
    > be able to borrow that.
    >
    > Thanks again
    >
    > pOTRice

    Well, I found my Picstart 16B1, and I still have two 16C57-RC/P's and
    one 16C57-JW-S1 too. If you can communicate with the programmer then
    you have the settings right. I just found two floppy disks with what I
    think is the software too.
     
    Tom, Mar 11, 2008
    #4
    1. Advertisements

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.
Similar Threads
  1. PleaseHelp

    University final year project, please read.

    PleaseHelp, Apr 7, 2004, in forum: General Electronics
    Replies:
    2
    Views:
    874
    PleaseHelp
    Apr 8, 2004
  2. tone

    16c57 PIC programmer

    tone, Jul 18, 2005, in forum: Electronic Equipment
    Replies:
    1
    Views:
    860
    Nospam
    Jul 21, 2005
  3. Clive Long,UK

    7 PIN DIN input at back of 10-year (?) old Hitachi CPT2478

    Clive Long,UK, Jan 2, 2004, in forum: Electronic Repair
    Replies:
    1
    Views:
    487
    stevec2005
    Jan 13, 2005
  4. tone

    16c57 PIC programmer

    tone, Jul 18, 2005, in forum: Electronic Repair
    Replies:
    6
    Views:
    1,203
  5. PleaseHelp

    University final year project, please read.

    PleaseHelp, Apr 7, 2004, in forum: Misc Electronics
    Replies:
    2
    Views:
    595
    Andre
    Apr 9, 2004
  6. Kilowatt

    10 year old AC

    Kilowatt, Jul 1, 2004, in forum: Electrical Engineering
    Replies:
    3
    Views:
    361
    AC/DCdude17
    Jul 2, 2004
  7. ElectrocutedBaboon
    Replies:
    5
    Views:
    759
    ElectrocutedBaboon
    Feb 19, 2013
  8. rogerds
    Replies:
    8
    Views:
    228
    Alec_t
    Oct 6, 2016
Loading...