• AVR Freaks

Hot!Device not found (No VDD) error, but voltages/signals look good

Author
rangeck
New Member
  • Total Posts : 25
  • Reward points : 0
  • Joined: 2011/03/01 14:13:58
  • Location: 0
  • Status: offline
2020/06/05 08:39:21 (permalink)
0

Device not found (No VDD) error, but voltages/signals look good

Hello all,
 
I have a new prototype PCB using a PIC32MX120F032D and I cannot get MPLAB X IDE/IPE (v5.15) and ICD3/4 to connect to it. The error it supplies is "Target device was not found (could not detect target voltage VDD)". I have 
  • I have 4x of these PCBs and they all behave the same
  • I can connect to all sorts of other microchip processor based boards fine
  • I've used both ICD3 and ICD4 to try to connect
  • Used several RJ11 cables for the ICD 
  • Rebooted several times
  • Used both MPLAB IDE and IPE to try to connect
  • Tried powering the board through the ICD to just access the processor (board's input 5V disconnected) – in both IDE and IPE
  • Processor pins 6/29/39 (VSS) have continuity to ground
  • Processor pins 28 and 40 (VDD) have 3.3V
  • Debug header pin 1(MCLR) is at 3.3V, pin 2(VDD) is at 3.3V, pin 3 has continuity to ground. Debug header pin ordering is correct (MCLR, VDD, GND, PGD, PGC, no connection)
    • On the scope the 3.3V looks nice and clean
I'm a bit at a loss of how to get this working. Does anyone have any further ideas of things to check or advice?
post edited by rangeck - 2020/06/05 11:05:56
#1

10 Replies Related Threads

    nigelwright7557
    Super Member
    • Total Posts : 441
    • Reward points : 0
    • Joined: 2006/11/06 08:15:51
    • Location: 0
    • Status: offline
    Re: Device not found (No VDD) error, but voltages/signals look good 2020/06/05 08:51:17 (permalink)
    0
    I had a similar problem with a pickit3.
    It turned out to be my 6 way ribbon cable had a broken wire at one end.
    It was well used so had probably just worn out or got pulled.
    Given it says target vdd not found I would check for 3v3 at programmer end of ribbon cable (if your using one)
    Or plug programmer straight into pcb without a cable.
     
     
     
    #2
    du00000001
    Just Some Member
    • Total Posts : 3778
    • Reward points : 0
    • Joined: 2016/05/03 13:52:42
    • Location: Germany
    • Status: offline
    Re: Device not found (No VDD) error, but voltages/signals look good 2020/06/05 10:07:20 (permalink)
    0
    Provided your programmer is connected the right way and the cable is  not broken: is VDD connected to the correct pin on your prototype? GND as well?
    Welcome to the community of prototype board users!  :)

    PEBKAC / EBKAC / POBCAK / PICNIC (eventually see en.wikipedia.org)
    #3
    rangeck
    New Member
    • Total Posts : 25
    • Reward points : 0
    • Joined: 2011/03/01 14:13:58
    • Location: 0
    • Status: offline
    Re: Device not found (No VDD) error, but voltages/signals look good 2020/06/05 10:09:27 (permalink)
    0
    The ICD3 and ICD4 that I use has an RJ11 telephone style cable. I've switched that cable out (as well as switching between ICD3/4). 
     
    The VDD signal on pin 2 measures as 3.3V with a meter as well as it is a clean 3.3V with no drops measured with an oscilliscope
    #4
    du00000001
    Just Some Member
    • Total Posts : 3778
    • Reward points : 0
    • Joined: 2016/05/03 13:52:42
    • Location: Germany
    • Status: offline
    Re: Device not found (No VDD) error, but voltages/signals look good 2020/06/05 10:12:15 (permalink)
    0
    Provided you have the selftest adapter at hand: connect this one and check the ICD(s).
    Considering you've tried both ICDs: are you sure about the pin numbering scheme?

    PEBKAC / EBKAC / POBCAK / PICNIC (eventually see en.wikipedia.org)
    #5
    rangeck
    New Member
    • Total Posts : 25
    • Reward points : 0
    • Joined: 2011/03/01 14:13:58
    • Location: 0
    • Status: offline
    Re: Device not found (No VDD) error, but voltages/signals look good 2020/06/05 10:28:40 (permalink)
    0
    Both ICD3 and ICD4 connect to other boards with the exact same debug connector pinout. I've verified the debug connector is soldered well and even checked continuity between the debug connector pins and the associated processor pins (MCLR/PGD/PGC). 3.3V and GND is verified as well. There are 4 of these boards as well and I would imagine it hard to believe all 4 exhibited the same soldering problem so I think that is out
     
    My company uses PIC micro-controllers almost exclusively and I've worked with them for 10 years now. The PCB designer EE and I are flabbergasted.. 
    #6
    rangeck
    New Member
    • Total Posts : 25
    • Reward points : 0
    • Joined: 2011/03/01 14:13:58
    • Location: 0
    • Status: offline
    Re: Device not found (No VDD) error, but voltages/signals look good 2020/06/05 10:30:31 (permalink)
    0
    Its gotta be something with the prototype board itself, but I can't fathom what with verifying the processor has power and grounds all connected and the debug header looking proper
     
    #7
    NKurzman
    A Guy on the Net
    • Total Posts : 18779
    • Reward points : 0
    • Joined: 2008/01/16 19:33:48
    • Location: 0
    • Status: offline
    Re: Device not found (No VDD) error, but voltages/signals look good 2020/06/05 11:33:04 (permalink)
    0
    "I would imagine it hard to believe all 4 exhibited the same soldering problem"
    actually, you would.  Boards should be made consistently.
    Did you measure Vdd between the connector pin and the connector ground pin?
     
    And your ICD3 and ICD 4 work on different Board correctly?
     
     
     
    #8
    rangeck
    New Member
    • Total Posts : 25
    • Reward points : 0
    • Joined: 2011/03/01 14:13:58
    • Location: 0
    • Status: offline
    Re: Device not found (No VDD) error, but voltages/signals look good 2020/06/05 11:46:08 (permalink)
    0
    I hadn't explicitly measured the voltage between the VDD and GND debug pins (GND test point and VDD). I just measured between the actual debug pins though and it is 3.3V
     
    I wonder if there isn't some other ICD error or related error that is just generalized to "no VDD found"
     
    My ICD3 and ICD4 both connect to other boards just fine. They are different product boards but a few even utilize the exact same processor and same debug connector pinout and related passive components (3.3V bypass cap, MCLR resistors/cap, etc)
     
    *pulls hair out*
    #9
    du00000001
    Just Some Member
    • Total Posts : 3778
    • Reward points : 0
    • Joined: 2016/05/03 13:52:42
    • Location: Germany
    • Status: offline
    Re: Device not found (No VDD) error, but voltages/signals look good 2020/06/05 11:58:43 (permalink)
    0
    rangeck
    I hadn't explicitly measured the voltage between the VDD and GND debug pins (GND test point and VDD). I just measured between the actual debug pins though and it is 3.3V
     
    I wonder if there isn't some other ICD error or related error that is just generalized to "no VDD found"
     
    My ICD3 and ICD4 both connect to other boards just fine. They are different product boards but a few even utilize the exact same processor and same debug connector pinout and related passive components (3.3V bypass cap, MCLR resistors/cap, etc)
     
    *pulls hair out*



    You may become bald searching the fault on the ICDs' side. Looks like some fault on your PCBs.
    IF you measure 3.3 V between VDD and GND on the debug connector (better: the other end of the debug cable), I'd bet on having gotten the pin numbering from the wrong side. Or RJ45 connector populated on the wrong side of the board. Can happen ...

    PEBKAC / EBKAC / POBCAK / PICNIC (eventually see en.wikipedia.org)
    #10
    ric
    Super Member
    • Total Posts : 27630
    • Reward points : 0
    • Joined: 2003/11/07 12:41:26
    • Location: Australia, Melbourne
    • Status: online
    Re: Device not found (No VDD) error, but voltages/signals look good 2020/06/05 15:34:13 (permalink)
    0
    du00000001
    ...
    IF you measure 3.3 V between VDD and GND on the debug connector (better: the other end of the debug cable), I'd bet on having gotten the pin numbering from the wrong side. Or RJ45 connector populated on the wrong side of the board. Can happen ...

    Many don't notice the numbering is mirrored between the ICD end and the device end.
    I agree, reversed connection is the most likely cause.
     

    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!
    #11
    Jump to:
    © 2020 APG vNext Commercial Version 4.5