• AVR Freaks

Hot!Problem With Debugging On the dsPIC33CH Curiosity Development Board

Author
Post
Essentials Only Full Version
Fred E
New Member
  • Total Posts : 15
  • Reward points : 0
  • Joined: 2011/11/27 10:36:49
  • Location: 0
  • Status: offline
2019/10/13 11:59:26 (permalink)
0

Problem With Debugging On the dsPIC33CH Curiosity Development Board

I am using the dsPIC33CH Curiosity board (purchased about a week ago from Mouser) under MPLABX v5.25 using the XC16 compiler.   I am using the demonstration program for this Curiosity board located here:
 
https://www.microchip.com/developmenttools/ProductDetails/PartNO/DM330028
 
as well as another project that I wrote.  
 
I have tried three different debuggers (the onboard PKOB (connected directly to my Surface PRO USB port), the PICKit 3, and the ICD 3, all with the latest firmware) and still I have this problem.....
 
The Device ID seems to be badly confused on this board and it refuses to allow me to download the Debug version of my program to the board.
 
I can program the non-debug (Production) version of both the demo program and my program  and it works just fine...  Both programs compile fine and run correctly when downloaded as Production versions....
 
The problem is, no matter what debugger I use (PKOB, ICD-3, or PicKit 3), when I hook up the debugger, I get the following message in red:
 
Target Device ID (0x7d540000) is an Invalid Device ID. Please check your connections to the Target Device. 
 
Most Target Device ID's that I've seen are 16 bit numbers and I've never seen one like "7d540000".  
 
What is going wrong?   Is there anyway I can fix this problem, or do I have a defective dsPIC33CH Curiosity Board?
#1

4 Replies Related Threads
    SMALLSMT
    New Member
    • Total Posts : 16
    • Reward points : 0
    • Joined: 2017/08/14 01:41:40
    • Location: 0
    • Status: offline
    Re: Problem With Debugging On the dsPIC33CH Curiosity Development Board 2019/11/01 14:01:00 (permalink)
    0
    I received the same problem and believe it depends on new verison of development board.
    Microchip used different CPU on development boards dspic33ch512mp508
    #2
    NorthGuy
    Super Member
    • Total Posts : 5754
    • Reward points : 0
    • Joined: 2014/02/23 14:23:23
    • Location: Northern Canada
    • Status: offline
    Re: Problem With Debugging On the dsPIC33CH Curiosity Development Board 2019/11/01 16:53:02 (permalink)
    0
    For debugging, you need to set the correct ICS bits in your FICD configuration. These bits select the pair of PGEC/PGED pins which is going to be used for the debugging. If you specify a wrong pair, the debugging won't work.

    Northern Software Inc
    #3
    NorthGuy
    Super Member
    • Total Posts : 5754
    • Reward points : 0
    • Joined: 2014/02/23 14:23:23
    • Location: Northern Canada
    • Status: offline
    Re: Problem With Debugging On the dsPIC33CH Curiosity Development Board 2019/11/01 16:59:19 (permalink)
    0
    0x7d54 is the correct device id for  dsPIC33CH512MP508. If the tools are confused with that, this must be a bug. The only way to fix it is to file a ticket with Microchip. This is the user forum and Microchip doesn't follow it.

    Northern Software Inc
    #4
    Howard Long
    Super Member
    • Total Posts : 721
    • Reward points : 0
    • Joined: 2005/04/04 08:50:32
    • Status: offline
    Re: Problem With Debugging On the dsPIC33CH Curiosity Development Board 2019/11/02 03:00:35 (permalink)
    4 (1)
    I've reproduced your error exactly, and I have a solution for you.
     
    It looks like you're using the code for the DM330028 board, and not the code for the DM330028-2.
     
    The older DM330028 board uses a dsPIC33CH128MP508, whereas the newer DM330028-2 uses a dsPIC33CH512MP508.
     
    The code you should be using is here:  https://www.microchip.com/Developmenttools/ProductDetails/DM330028-2
    #5
    Jump to:
    © 2019 APG vNext Commercial Version 4.5