• AVR Freaks

Hot!Does Target Device ID (0x0) is an Invalid Device ID mean device is blown?

Author
JustRob
Super Member
  • Total Posts : 631
  • Reward points : 0
  • Joined: 2008/09/04 12:49:27
  • Location: Hudson Massachusetts United States
  • Status: offline
2021/03/03 15:17:46 (permalink)
0

Does Target Device ID (0x0) is an Invalid Device ID mean device is blown?

I just spun a new circuit board.  I'm using the ICD3 with the pic18lf47k42 in the 44 tqfp package with only the 3.3v regulator circuit, the pic with its decoupling caps and the ICD3 interface hardware (connector, mclr 1k pullup and decoupling cap) installed.
 
I have verified 3.3v to the power pins and gnd to its respective pins.  I have also wrung out the ICSPDAT and ICSPCLK signals from the connector to the pic.  I have tried 3 different pics and all having the same results.
 
The old circuit board works so it's not the ICD3 or the connectors.
 
With the ICD3 ICSPDAT and ICSPCLK lines wrung out point to blown devices more than communication issues?

Sometimes the obstacles in our path ARE our path!
 
https://abateandempower.com/
#1

14 Replies Related Threads

    ric
    Super Member
    • Total Posts : 30244
    • Reward points : 0
    • Joined: 2003/11/07 12:41:26
    • Location: Australia, Melbourne
    • Status: offline
    Re: Does Target Device ID (0x0) is an Invalid Device ID mean device is blown? 2021/03/03 15:40:20 (permalink)
    0
    What do you mean by "wrung out"?
    Maybe just "run out".
     
    Usually this inidcates that DAT and CLK have been accidentally swapped, or something is stopping MCLR being raised to the correct voltage.
    Are you using HV, or LVP mode for programming?
     

    I also post at: PicForum
    Links to useful PIC information: http://picforum.ric323.co...opic.php?f=59&t=15
    NEW USERS: Posting images, links and code - workaround for restrictions.
    To get a useful answer, always state which PIC you are using!
    #2
    JustRob
    Super Member
    • Total Posts : 631
    • Reward points : 0
    • Joined: 2008/09/04 12:49:27
    • Location: Hudson Massachusetts United States
    • Status: offline
    Re: Does Target Device ID (0x0) is an Invalid Device ID mean device is blown? 2021/03/03 15:49:08 (permalink)
    0
    I mean the ICSP data and clock signals are going to the correct pins.
     
    Are you using HV, or LVP mode for programming?

    I tried to find that setting in properties but could not find it.  I was previously set for LVP but I'd like to verify it.
     
    Looking at the layout I think I'm severely choking my ground plane from the ICD3 connector to the pic and the power connector.
     
    See attached pic of layout.  The deans connectors are in the lower-left, the ICD3 connector (thru-hole pins) is in the upper-right with the pic below it.
     
    post edited by JustRob - 2021/03/03 15:58:45

    Attached Image(s)


    Sometimes the obstacles in our path ARE our path!
     
    https://abateandempower.com/
    #3
    ric
    Super Member
    • Total Posts : 30244
    • Reward points : 0
    • Joined: 2003/11/07 12:41:26
    • Location: Australia, Melbourne
    • Status: offline
    Re: Does Target Device ID (0x0) is an Invalid Device ID mean device is blown? 2021/03/03 15:53:19 (permalink)
    0
    You haven't mentioned if you are controlling the programmer with MPLABX, or the IPE.
    The method to select LVP/HVP differs between them.
    If the PIC has previously been programmed with the LVP bit turned off, then LVP programming will not detect the chip.
     
     

    I also post at: PicForum
    Links to useful PIC information: http://picforum.ric323.co...opic.php?f=59&t=15
    NEW USERS: Posting images, links and code - workaround for restrictions.
    To get a useful answer, always state which PIC you are using!
    #4
    JustRob
    Super Member
    • Total Posts : 631
    • Reward points : 0
    • Joined: 2008/09/04 12:49:27
    • Location: Hudson Massachusetts United States
    • Status: offline
    Re: Does Target Device ID (0x0) is an Invalid Device ID mean device is blown? 2021/03/03 16:01:02 (permalink)
    0
    You haven't mentioned if you are controlling the programmer with MPLABX, or the IPE.

    Sorry, I'm using the MPLABX IDE

    Sometimes the obstacles in our path ARE our path!
     
    https://abateandempower.com/
    #5
    du00000001
    Just Some Member
    • Total Posts : 4148
    • Reward points : 0
    • Joined: 2016/05/03 13:52:42
    • Location: Germany
    • Status: online
    Re: Does Target Device ID (0x0) is an Invalid Device ID mean device is blown? 2021/03/03 16:31:37 (permalink)
    0
    Hi Rob,
     
    one side of the PCB without the schematics (relevant when it comes to HVP vs. LVP) is not much to judge upon. And somewhat lighter purple vs. darker purple is difficult to judge upon in itself.
    What's your CAD program? Might be better to provide the CAD files.
     
    Re "choking the GND": currently maybe (just "maybe"). But that's usually nothing some well-place vias wouldn't be able to cure.

    PEBKAC / EBKAC / POBCAK / PICNIC (eventually see en.wikipedia.org)
    #6
    JustRob
    Super Member
    • Total Posts : 631
    • Reward points : 0
    • Joined: 2008/09/04 12:49:27
    • Location: Hudson Massachusetts United States
    • Status: offline
    Re: Does Target Device ID (0x0) is an Invalid Device ID mean device is blown? 2021/03/03 16:53:02 (permalink)
    0
    The top side.  And this is the actual photo from OSH Park online fab.  I will post the layout cad files tomorrow.
     
    Thanks

    Attached Image(s)


    Sometimes the obstacles in our path ARE our path!
     
    https://abateandempower.com/
    #7
    du00000001
    Just Some Member
    • Total Posts : 4148
    • Reward points : 0
    • Joined: 2016/05/03 13:52:42
    • Location: Germany
    • Status: online
    Re: Does Target Device ID (0x0) is an Invalid Device ID mean device is blown? 2021/03/03 17:19:55 (permalink)
    0
    Oops. Copper pouring is not prohibitedon the top side!  wink

    Currently it looks like your GND is really a bit poor around the debug I/F. But nothing some copper pour on top plus some vias (GND - to connect top and bottom pours) wouldn't cure.

    PEBKAC / EBKAC / POBCAK / PICNIC (eventually see en.wikipedia.org)
    #8
    JustRob
    Super Member
    • Total Posts : 631
    • Reward points : 0
    • Joined: 2008/09/04 12:49:27
    • Location: Hudson Massachusetts United States
    • Status: offline
    Re: Does Target Device ID (0x0) is an Invalid Device ID mean device is blown? 2021/03/04 08:26:19 (permalink)
    0
    @ric
    If the PIC has previously been programmed with the LVP bit turned off, then LVP programming will not detect the chip.

     
    Here's my configuration settings:
    // CONFIG1L
    #pragma config FEXTOSC = OFF // External Oscillator Selection (Oscillator not enabled)
    #pragma config RSTOSC = HFINTOSC_64MHZ// Reset Oscillator Selection (HFINTOSC with HFFRQ = 64 MHz and CDIV = 1:1)

    // CONFIG1H
    #pragma config CLKOUTEN = OFF // Clock out Enable bit (CLKOUT function is disabled)
    #pragma config PR1WAY = ON // PRLOCKED One-Way Set Enable bit (PRLOCK bit can be cleared and set only once)
    #pragma config CSWEN = OFF // Clock Switch Enable bit (The NOSC and NDIV bits cannot be changed by user software)
    #pragma config FCMEN = ON // Fail-Safe Clock Monitor Enable bit (Fail-Safe Clock Monitor enabled)

    // CONFIG2L
    #pragma config MCLRE = EXTMCLR // MCLR Enable bit (If LVP = 0, MCLR pin function is port defined function; If LVP =1, RE3 pin fuction is MCLR)
    #pragma config PWRTS = PWRT_OFF // Power-up timer selection bits (PWRT is disabled)
    #pragma config MVECEN = ON // Multi-vector enable bit (Multi-vector enabled, Vector table used for interrupts)
    #pragma config IVT1WAY = ON // IVTLOCK bit One-way set enable bit (IVTLOCK bit can be cleared and set only once)
    #pragma config LPBOREN = OFF // Low Power BOR Enable bit (ULPBOR disabled)
    #pragma config BOREN = SBORDIS // Brown-out Reset Enable bits (Brown-out Reset enabled , SBOREN bit is ignored)

    // CONFIG2H
    #pragma config BORV = VBOR_2P7 // Brown-out Reset Voltage Selection bits (Brown-out Reset Voltage (VBOR) set to 2.7V)
    #pragma config ZCD = OFF // ZCD Disable bit (ZCD disabled. ZCD can be enabled by setting the ZCDSEN bit of ZCDCON)
    #pragma config PPS1WAY = ON // PPSLOCK bit One-Way Set Enable bit (PPSLOCK bit can be cleared and set only once; PPS registers remain locked after one clear/set cycle)
    #pragma config STVREN = ON // Stack Full/Underflow Reset Enable bit (Stack full/underflow will cause Reset)
    #pragma config DEBUG = OFF // Debugger Enable bit (Background debugger disabled)
    #pragma config XINST = OFF // Extended Instruction Set Enable bit (Extended Instruction Set and Indexed Addressing Mode disabled)

    // CONFIG3L
    #pragma config WDTCPS = WDTCPS_31// WDT Period selection bits (Divider ratio 1:65536; software control of WDTPS)
    #pragma config WDTE = OFF // WDT operating mode (WDT Disabled; SWDTEN is ignored)

    // CONFIG3H
    #pragma config WDTCWS = WDTCWS_7// WDT Window Select bits (window always open (100%); software control; keyed access not required)
    #pragma config WDTCCS = SC // WDT input clock selector (Software Control)

    // CONFIG4L
    #pragma config BBSIZE = BBSIZE_512// Boot Block Size selection bits (Boot Block size is 512 words)
    #pragma config BBEN = OFF // Boot Block enable bit (Boot block disabled)
    #pragma config SAFEN = OFF // Storage Area Flash enable bit (SAF disabled)
    #pragma config WRTAPP = OFF // Application Block write protection bit (Application Block not write protected)

    // CONFIG4H
    #pragma config WRTB = OFF // Configuration Register Write Protection bit (Configuration registers (300000-30000Bh) not write-protected)
    #pragma config WRTC = OFF // Boot Block Write Protection bit (Boot Block (000000-0007FFh) not write-protected)
    #pragma config WRTD = OFF // Data EEPROM Write Protection bit (Data EEPROM not write-protected)
    #pragma config WRTSAF = OFF // SAF Write protection bit (SAF not Write Protected)
    #pragma config LVP = OFF // Low Voltage Programming Enable bit (Low voltage programming enabled. MCLR/VPP pin function is MCLR. MCLRE configuration bit is ignored)

    // CONFIG5L
    #pragma config CP = OFF // PFM and Data EEPROM Code Protection bit (PFM and Data EEPROM code protection disabled)

    // CONFIG5H

     
    In the project properties under ICD3>program options neither high voltage programing nor low voltage programing boxes are checked.  Thoughts (before I spin a new board making sure the ICD3 connector has an adequate ground)?

    Sometimes the obstacles in our path ARE our path!
     
    https://abateandempower.com/
    #9
    Mysil
    Super Member
    • Total Posts : 4130
    • Reward points : 0
    • Joined: 2012/07/01 04:19:50
    • Location: Norway
    • Status: online
    Re: Does Target Device ID (0x0) is an Invalid Device ID mean device is blown? 2021/03/04 09:49:06 (permalink)
    0
    Hi,
    In Configuration settings shown in message #9:   LVP = OFF
    but comments on the same line indicate the opposite!
    This indicate that Configuration setting have been manually changed, Without correcting the comment!
     
    If:   ... LVP = OFF  in Configuration settings, then you Must set HVP programming check box in Project Properties.
     
        Mysil
    #10
    JustRob
    Super Member
    • Total Posts : 631
    • Reward points : 0
    • Joined: 2008/09/04 12:49:27
    • Location: Hudson Massachusetts United States
    • Status: offline
    Re: Does Target Device ID (0x0) is an Invalid Device ID mean device is blown? 2021/03/04 10:26:16 (permalink)
    0
    I checked the HVP programming check box in project properties but I still get the "Target Divice ID (0x0) is Invalid" error.

    Sometimes the obstacles in our path ARE our path!
     
    https://abateandempower.com/
    #11
    GilJ
    Super Member
    • Total Posts : 119
    • Reward points : 0
    • Joined: 2011/04/05 02:36:47
    • Location: 0
    • Status: offline
    Re: Does Target Device ID (0x0) is an Invalid Device ID mean device is blown? 2021/03/04 11:29:03 (permalink)
    0
    Hi, I can't see clearly, but it seems there is only a trace from MCLR pin to the programming connector. MCLR should be tied to Vdd with 10K resistor.
    #12
    JustRob
    Super Member
    • Total Posts : 631
    • Reward points : 0
    • Joined: 2008/09/04 12:49:27
    • Location: Hudson Massachusetts United States
    • Status: offline
    Re: Does Target Device ID (0x0) is an Invalid Device ID mean device is blown? 2021/03/04 12:07:28 (permalink)
    0
    Yes, I have a pullup on the circuit board.
     
    As I look at the layout I feel I need to move the pic and ICD3 connector closer to the power connector along with moving a lot of the circuitry.  I'm making the ground plane a lot more solid where it needs to be.

    Sometimes the obstacles in our path ARE our path!
     
    https://abateandempower.com/
    #13
    NKurzman
    A Guy on the Net
    • Total Posts : 19192
    • Reward points : 0
    • Joined: 2008/01/16 19:33:48
    • Location: 0
    • Status: offline
    Re: Does Target Device ID (0x0) is an Invalid Device ID mean device is blown? 2021/03/04 12:47:15 (permalink)
    0
    Did you owm the pins for shorts?
    I assume All Power Pins and All Grounds are connected.
    That The The PIC has Power.
     
    #14
    ric
    Super Member
    • Total Posts : 30244
    • Reward points : 0
    • Joined: 2003/11/07 12:41:26
    • Location: Australia, Melbourne
    • Status: offline
    Re: Does Target Device ID (0x0) is an Invalid Device ID mean device is blown? 2021/03/04 14:27:50 (permalink)
    0
    owm -> ohm
    i.e. do a resistance check with a meter.
     

    I also post at: PicForum
    Links to useful PIC information: http://picforum.ric323.co...opic.php?f=59&t=15
    NEW USERS: Posting images, links and code - workaround for restrictions.
    To get a useful answer, always state which PIC you are using!
    #15
    Jump to:
    © 2021 APG vNext Commercial Version 4.5