• AVR Freaks

Hot![SOLVED] PIC12F675 debugger module AC162050 lost its OSCCAL calibration value..

Author
jpdesroc
Starting Member
  • Total Posts : 85
  • Reward points : 0
  • Joined: 2011/01/31 11:20:06
  • Location: 0
  • Status: offline
2019/07/01 14:38:56 (permalink)
0

[SOLVED] PIC12F675 debugger module AC162050 lost its OSCCAL calibration value..

I used a PIC12F675 AC162050 debugger header module
to debug this tinny chip over the last years with success.
But yesterday while doing some programming tests
in MPLAB X IDE with PicKit3
it seems I lost the OSCCAL internal value
of the chip for the internal oscillator..
All the infos I found on the web so far is to
get OSCCAL value back to a standard PIC12F675,
But the actual PIC that's on the debugger header
is a special PIC12F675-ICD 14 pins IC to free up
the final 8 pins socket connected to the target board.
The only thing now that 'connects' to this debugger module
is using MPLAB IDE v8.92 with a ICD3
with the RJ connector to the AC162050 debugger module.
Doing so I get the following message:

MPLAB ICD 3 detected
Connecting to MPLAB ICD 3...
Running self test...
Self test completed
Firmware Suite Version...... 01.40.05
Firmware type................Midrange
MPLAB ICD 3 Connected.
Target Detected
Device ID Revision = 00000002
ICD3Err0085: The target has invalid calibration data (3fff)

But there is no way I found to force a OSCCAL value
in the 12F675-ICD IC inside MPLAB IDE using a ICD3 so,
I tried to use a PicKit3 with its standalone program (PicKit3 Programmer v3.10)
to force a value in the OSCCAL memory address.
The problem now is that the AC162050 module only
has a RJ connector to communicate with the PIC
and the PicKit3 has a 6 pins female header (with the pins connected correctly to the RJ)
so I had to make a 6 pins to RJ adapter to the debugger..
Now in the PicKit3 Programmer v3.10,
only the PicKit3 is detected and when I select
the PIC12F675 chip the program says
"No device detected".

By the way all the above tests were done
using a reliable target board with its supply @ +5VDC.
No supply from the debuggers.

I'm in a dead end now..
Can somebody help ?
Thanks.

J-Pierre
post edited by jpdesroc - 2020/07/13 07:15:29
#1

18 Replies Related Threads

    du00000001
    Just Some Member
    • Total Posts : 3979
    • Reward points : 0
    • Joined: 2016/05/03 13:52:42
    • Location: Germany
    • Status: offline
    Re: PIC12F675 debugger module AC162050 lost its OSCCAL calibration value.. unusable now ? 2019/07/02 00:47:47 (permalink)
    0
    WhilevI have no experience with the PIC16F675, I know how to dig in he forums :)
     
    Maybe of special interest:
    https://www.microchip.com....aspx?m=309921&p=1
     
    Otherwise, g..gl. is quite efficient in searching the forums. E.g.
    https://www.google.com/se...amp;client=firefox-b-m
    post edited by du00000001 - 2020/07/09 07:29:43

    PEBKAC / EBKAC / POBCAK / PICNIC (eventually see en.wikipedia.org)
    #2
    jpdesroc
    Starting Member
    • Total Posts : 85
    • Reward points : 0
    • Joined: 2011/01/31 11:20:06
    • Location: 0
    • Status: offline
    Re: PIC12F675 debugger module AC162050 lost its OSCCAL calibration value.. unusable now ? 2020/07/08 08:22:04 (permalink)
    0
    The first request of this old topic (still not resolved) was:
    PIC12F675 debugger module AC162050 lost its OSCCAL calibration value.. unusable now ?
    All the posts I found were about the PIC12F675 IC itself.. not its AC162050 debugger module.
    So far when connecting the AC162050 module to the PICKit 2 Software via the RJ connector
    I can read, write, erase the module but the OSCCAL memory location 0x03FF stays at a value of 3FFF.
    The Tools/OSCCAL/ Set manually or Auto Regenerate commands don't work..
    I get the message "Regenerating OSCCAL Failed ! Unable to connect to calibration executive. "
    The Set Manually command does not work either..
    What can be done to this debugger module to get it work ?
    Again this problem IS NOT related to standard 8 pijns PIC12F675
    but to their debugger module.
    I'm stuck..
     
    post edited by jpdesroc - 2020/07/08 08:23:33
    #3
    Jim Nickerson
    User 452
    • Total Posts : 6752
    • Reward points : 0
    • Joined: 2003/11/07 12:35:10
    • Location: San Diego, CA
    • Status: offline
    Re: PIC12F675 debugger module AC162050 lost its OSCCAL calibration value.. unusable now ? 2020/07/08 08:31:54 (permalink)
    0 (2)
    #4
    dan1138
    Super Member
    • Total Posts : 3917
    • Reward points : 0
    • Joined: 2007/02/21 23:04:16
    • Location: 0
    • Status: offline
    Re: PIC12F675 debugger module AC162050 lost its OSCCAL calibration value.. unusable now ? 2020/07/08 11:00:49 (permalink)
    +1 (1)
    jpdesroc
    The first request of this old topic (still not resolved) was:
    PIC12F675 debugger module AC162050 lost its OSCCAL calibration value.. unusable now ? ...

    Have you tired connecting the PGC and PGD signals from the modular connector to the GPIO pins they are on for the "normal" PIC12F675?
     
    I suspect that the ICD version used on the AC162050 does not have the PGC/PGD pins as PORT bits. This this could be why the calibration executive fails.
    #5
    jpdesroc
    Starting Member
    • Total Posts : 85
    • Reward points : 0
    • Joined: 2011/01/31 11:20:06
    • Location: 0
    • Status: offline
    Re: PIC12F675 debugger module AC162050 lost its OSCCAL calibration value.. unusable now ? 2020/07/09 07:10:05 (permalink)
    0
    Thank you for your help here..
     
    The AC162050 is there to free up the GPIO pins on the final bottom 8 pins socket from the PGC & PGD programming uses. That is the reason why I bought it years ago..
     
    S
    dan1138
    I suspect that the ICD version used on the AC162050 does not have the PGC/PGD pins as PORT bits. This this could be why the calibration executive fails.

    If it 's the case why all the other memory addresses can be read/write & erased ?
    I'm pretty sure the PGC/PGD pins are not connected to the PORT bits.
    That should be the debugger module's primary purpose..
    #6
    dan1138
    Super Member
    • Total Posts : 3917
    • Reward points : 0
    • Joined: 2007/02/21 23:04:16
    • Location: 0
    • Status: offline
    Re: PIC12F675 debugger module AC162050 lost its OSCCAL calibration value.. unusable now ? 2020/07/09 13:01:43 (permalink)
    +1 (1)
    jpdesroc
    Thank you for your help here..
     
    The AC162050 is there to free up the GPIO pins on the final bottom 8 pins socket from the PGC & PGD programming uses. That is the reason why I bought it years ago..
     
    dan1138
    I suspect that the ICD version used on the AC162050 does not have the PGC/PGD pins as PORT bits. This this could be why the calibration executive fails.

    If it's the case why all the other memory addresses can be read/write & erased ?
    I'm pretty sure the PGC/PGD pins are not connected to the PORT bits.
    That should be the debugger module's primary purpose..

    But then you are not using the AC162050 for its primary purpose, you are trying to restore the oscillator calibration using a method that seems only designed to work on production parts.

    If the AC162050 were made to TEMPORARILY appear like a production part then the calibration executive may actually run to completion.

    So my suggestion to connect the PIC12F675 pin 7, GP0, to the PCD line and pin 6, GP1, to the PGC line of the modular connector could make the calibration process work.
    #7
    jpdesroc
    Starting Member
    • Total Posts : 85
    • Reward points : 0
    • Joined: 2011/01/31 11:20:06
    • Location: 0
    • Status: offline
    Re: PIC12F675 debugger module AC162050 lost its OSCCAL calibration value.. unusable now ? 2020/07/09 13:55:10 (permalink)
    0
    dan1138
    If the AC162050 were made to TEMPORARILY appear like a production part then the calibration executive may actually run to completion.

    So my suggestion to connect the PIC12F675 pin 7, GP0, to the PCD line and pin 6, GP1, to the PGC line of the modular connector could make the calibration process work.



    So If I understand you correctly you suggest connecting pin 7 (GPO0) of the debugged 8 pins male DIP connector
    to the RG connector's PCD line
    and
    connect pin 6 (GPO1) of the final 8 pins male DIP connector to the RG connector's PGC line ?
     
    And doing so, Should all the programming be done on the AC162050's 8 pins male DIP or the RG connector ?
    post edited by jpdesroc - 2020/07/09 15:47:02
    #8
    dan1138
    Super Member
    • Total Posts : 3917
    • Reward points : 0
    • Joined: 2007/02/21 23:04:16
    • Location: 0
    • Status: offline
    Re: PIC12F675 debugger module AC162050 lost its OSCCAL calibration value.. unusable now ? 2020/07/09 16:25:50 (permalink)
    +1 (1)
    jpdesroc
    dan1138
    If the AC162050 were made to TEMPORARILY appear like a production part then the calibration executive may actually run to completion.

    So my suggestion to connect the PIC12F675 pin 7, GP0, to the PCD line and pin 6, GP1, to the PGC line of the modular connector could make the calibration process work.



    So If I understand you correctly you suggest connecting pin 7 (GPO0) of the debugged 8 pins male DIP connector to the RG connector's PCD line and connect pin 6 (GPO1) of the final 8 pins male DIP connector to the RG connector's PGC line ?
     
    And doing so, Should all the programming be done on the AC162050's 8 pins male DIP or the RG connector ?



    If by RG connector you mean the 6-pin modular connector mounted to the AC162050 module, then yes.
     
    With those TEMPORARY connections in place the calibration process "should" work regardless of how the PICkit is connected. Use the modular or DIP pins, BUT NOT BOTH, to connect to the PICkit.
    #9
    jpdesroc
    Starting Member
    • Total Posts : 85
    • Reward points : 0
    • Joined: 2011/01/31 11:20:06
    • Location: 0
    • Status: offline
    Re: PIC12F675 debugger module AC162050 lost its OSCCAL calibration value.. unusable now ? 2020/07/09 16:57:45 (permalink)
    0
    Ok I'll try that early tomorrow and get back to you !
     
    Many Thanks for your precious help..
     
    Jean-Pierre
    #10
    jpdesroc
    Starting Member
    • Total Posts : 85
    • Reward points : 0
    • Joined: 2011/01/31 11:20:06
    • Location: 0
    • Status: offline
    Re: PIC12F675 debugger module AC162050 lost its OSCCAL calibration value.. unusable now ? 2020/07/10 11:05:46 (permalink)
    0
    > So my suggestion to connect the PIC12F675 pin 7, GP0, to the PCD line
    > and pin 6, GP1, to the PGC line of the modular connector
    > could make the calibration process work.

    > With those TEMPORARY connections in place the calibration process "should" work
    > regardless of how the PICkit is connected. Use the modular or DIP pins,
    > BUT NOT BOTH, to connect to the PICkit.

    Ok I made the 2 suggested temporary wire connections:
    AC162050 8DIP male pin 7(GP0) connected to ICD connector PCD line
    AC162050 8DIP male pin 6(GP1) connected to ICD connector PGC line

    First test:
    I used a PICKit 3 connected to the AC162050 RG connector to test the OSCCAL programming
    with PICKit 3Plus Programmer.
    The software can see the PICKit3 and the selected PIC12F675 device
    but still.. trying to change the OSCCAL from 3FFF to another value like 348F,  OSCCAL is stuck at value 3FFF.
    I get the OSCCAL message "Invalid Value 3FFF".

    Second test:
    I used a PICKit 2 connected to the AC162050 RG connector to test the OSCCAL programming
    with PICKit 2Plus Programmer.
    The software can see the PICKit2 and the selected PIC12F675 device
    but still.. using menu OSCCAL/Set Manualy or /Auto Regenerate
    to change the OSCCAL from 3FFF to another value like 348F,  OSCCAL is stuck at value 3FFF.

    I get the OSCCAL message "Invalid Value 3FFF"
    or
    "Regenerating OSCCAL Failed !
    Unable to connect to calibration executive.."

    These 2 connections did not change anything.

    As I said previously I CAN read/write and erase the PIC2F675 debugger module
    with any of the above software connected to the module's RG connector..
    I wrote some dummy values anywhere in the memory
    and read them back clearly afterward.
    This is ONLy the OSCCAL address that does not respond.
    #11
    dan1138
    Super Member
    • Total Posts : 3917
    • Reward points : 0
    • Joined: 2007/02/21 23:04:16
    • Location: 0
    • Status: offline
    Re: PIC12F675 debugger module AC162050 lost its OSCCAL calibration value.. unusable now ? 2020/07/10 12:50:17 (permalink)
    0
    So my idea is a bad one, but wait I've got another. This time I can prove it's a better idea.
     
    I do not have an AC162050 but I do have a close relative the AC162057 for the PIC16F676 etc.
     
    I have found that the PICkit2 can do a manual write to the OSCCAL location.
     
    The attached file is a ZIP of a screen vid capture of me do just that today.
     
    I did this on the stock AC162057, without the temporary wires to the PGD & PGC pins.
     
    Notes:
    The PICkit2 must find the target device using its automatic search.
    Manually selecting the target device prevents writes to the OSCCAL location.
     
    <EDIT>
     I have found that the PICKit2 v2.61 application will erase the OSCCAL instruction word when the application is started with the target device attached.
     
    I have found that the PICKit3 v3.10 application does a better job. This application is available in the Microchip download archive.
     
    Attached are ZIP files of screen vids of using both.
     
    post edited by dan1138 - 2020/07/10 14:31:57
    #12
    jpdesroc
    Starting Member
    • Total Posts : 85
    • Reward points : 0
    • Joined: 2011/01/31 11:20:06
    • Location: 0
    • Status: offline
    Re: PIC12F675 debugger module AC162050 lost its OSCCAL calibration value.. unusable now ? 2020/07/10 13:20:16 (permalink)
    0
    Hi dan1138,
     
    So you accidentally erased your debugger module's OSCCAL ?
    Now we'll be 2 to try to solve this problem ?
    By the way I opened a case on july 9th at Microsoft Support about this problem..
    I received 2 acknowledge emails letting me know they are
    working on this problem. So far no replies.
    Microchip should just answer a CLEAR solution on how
    to avoid and solve this OSCCAL deprogramming issue on debugger module.
    At more than $50 these modules should be reprogrammable OSCCAL wise..
     
    post edited by jpdesroc - 2020/07/10 13:22:14
    #13
    dan1138
    Super Member
    • Total Posts : 3917
    • Reward points : 0
    • Joined: 2007/02/21 23:04:16
    • Location: 0
    • Status: offline
    Re: PIC12F675 debugger module AC162050 lost its OSCCAL calibration value.. unusable now ? 2020/07/10 14:34:27 (permalink)
    0
    Found a way to get it to program and why my AC162057 got corrupted.
     
    I have edited my post
    #14
    jpdesroc
    Starting Member
    • Total Posts : 85
    • Reward points : 0
    • Joined: 2011/01/31 11:20:06
    • Location: 0
    • Status: offline
    Re: PIC12F675 debugger module AC162050 lost its OSCCAL calibration value.. unusable now ? 2020/07/10 17:24:37 (permalink)
    0
    I checked your 2 videos.
    I've done the same procedures you did within  PICKit 2 and then PICKit 3 software.
    i've been able to change the OSCCAL value with a different one on each software.
    But no matter what the last software I used to change the OSCCAL value,
    when I closed that program and started it back with the same debugger connections,
    initiated a READ, the OSCCAL had kept its bad 3FFF value still (!!! ???)
    I'm starting to get stunned..
     
     
    #15
    dan1138
    Super Member
    • Total Posts : 3917
    • Reward points : 0
    • Joined: 2007/02/21 23:04:16
    • Location: 0
    • Status: offline
    Re: PIC12F675 debugger module AC162050 lost its OSCCAL calibration value.. unusable now ? 2020/07/10 18:20:05 (permalink)
    +2 (2)
    The steps I followed with the PICKit2 are:
     
    1 - Unplug every thing
    2 - Connect PICKit2 to the Windows USB
    3 - Launch the PICKit2 v2.61 application
    4 - Connect the AC162057 to the PICKit2
    5 - Click the "Read" button
    6 - Confirm that the target was identified and read
    7 - Select the Tools->OSCCAL->Set Manually
    8 - Use value 348C
    9 - Click "Set"
    10 - Click "Read"
    11 - Verify that the OSCCAL value change to 348C
    12 - Disconnect target from PICKit2
    13 - Close the PICKit2 v2.61 application
     
    To validate the OSCCAL value was actually written to flash I did these steps:
     
    1 - Unplug every thing
    2 - Connect PICKit2 to the Windows USB
    3 - Launch the PICKit2 v2.61 application
    4 - Connect the AC162057 to the PICKit2
    5 - Click the "Read" button
    6 - Confirm that the target was identified and read
    7 - Verify that the OSCCAL value is 348C
    8 - Disconnect target from PICKit2
    9 - Close the PICKit2 v2.61 application
     
    Note that I am only connecting the AC162057 to the PICKit and the PICKit is providing the VDD.
     
    Also the AC162057 is not plugged into any target PCB the DIP pins are floating in free air.
    post edited by dan1138 - 2020/07/10 18:21:09
    #16
    jpdesroc
    Starting Member
    • Total Posts : 85
    • Reward points : 0
    • Joined: 2011/01/31 11:20:06
    • Location: 0
    • Status: offline
    [SOLVED] PIC12F675 debugger module AC162050 lost its OSCCAL calibration value.. 2020/07/11 07:31:29 (permalink)
    0
    YES !!!!!
    That worked !
    I will carefully copy this procedure in my files for any
    possible OSCCAL value lost..
    A GREAT Thank You to you !
    jean-Pierre
    post edited by jpdesroc - 2020/07/13 07:17:48
    #17
    jpdesroc
    Starting Member
    • Total Posts : 85
    • Reward points : 0
    • Joined: 2011/01/31 11:20:06
    • Location: 0
    • Status: offline
    [SOLVED] PIC12F675 debugger module AC162050 lost its OSCCAL calibration value.. 2020/07/12 09:53:28 (permalink)
    +1 (1)
    I made a small program that generates a 10usec square wave period on GPIO1.
    I first used an external 4Mhz crystal, measured the GPIO1 period, then used the internal 4Mhz clock
    and compared both readings. I finally tweaked the OSCCAL at 0x3493 to get
    the same period readings using a PICKit 2 and the suggested procedure listed above.
    Many thanks again.. My AC162050 is now usable !
    post edited by jpdesroc - 2020/07/13 07:18:13
    #18
    jpdesroc
    Starting Member
    • Total Posts : 85
    • Reward points : 0
    • Joined: 2011/01/31 11:20:06
    • Location: 0
    • Status: offline
    Re: PIC12F675 debugger module AC162050 lost its OSCCAL calibration value.. unusable now ? 2020/07/13 07:14:27 (permalink)
    -1 (1)
    Solved !
    post edited by jpdesroc - 2020/07/13 07:16:23
    #19
    Jump to:
    © 2020 APG vNext Commercial Version 4.5