| View previous topic :: View next topic | 
	
	
		| Author | Message | 
	
		| Langton 
 
 
 Joined: 29 Nov 2009
 Posts: 25
 
 
 
			    
 
 | 
			
				| Debugging compatibility |  
				|  Posted: Thu Jan 16, 2020 4:18 pm |   |  
				| 
 |  
				| Hi Chaps, 
 I'm using a dsPIC33CK256MP508 on a Realice with MPLAB X and PCD5 vers 5.090
 
 Upon attempting debugging I'm getting this error...
 
 Error#164  Selected part does not have ICD debug capability
 
 Page 537 of the datasheet states that this chip does have debugging functionality with Realice.
 
 I did email support almost 1 1/2 weeks ago but have had no reply.
 
 Any input would be much appreciated.
 |  | 
	
		|  | 
	
		| temtronic 
 
 
 Joined: 01 Jul 2010
 Posts: 9589
 Location: Greensville,Ontario
 
 
			    
 
 | 
			
				|  |  
				|  Posted: Fri Jan 17, 2020 12:07 pm |   |  
				| 
 |  
				| I'd email them again, a 'gentle' reminder... something like ' I'm just checking to see if you've made any progress on .......' Often people get busy, things come up (car crashes, bad weather, flu) and  work may not get passed onto another persons desk....
 It might be a 'fixed' bug, maybe a newer version will work for you ?
 |  | 
	
		|  | 
	
		| Langton 
 
 
 Joined: 29 Nov 2009
 Posts: 25
 
 
 
			    
 
 | 
			
				|  |  
				|  Posted: Fri Jan 17, 2020 1:53 pm |   |  
				| 
 |  
				| Just got a reply. 
 Microchip have not supplied CCS with the necessary data to employ debugging atm. So presently, there is no debugging capability for all CH and CK parts.
 |  | 
	
		|  | 
	
		| Ttelmah 
 
 
 Joined: 11 Mar 2010
 Posts: 19967
 
 
 
			    
 
 | 
			
				|  |  
				|  Posted: Fri Jan 17, 2020 2:05 pm |   |  
				| 
 |  
				| What puzzles me though is if you are in MPLAB, it is the Microchip debugging tools you will be using. The problem will be that the code needs
 to actually load the ICD executive, and be compiled with the fuses
 changed to match debugger operation, but the compiler shouldn't really
 need to know anything.
 I have previously been able to debug a processor that wasn't supported
 by loading the hex into MPLAB, with it configured for the processor. This
 though was with MPLab, not MPLAB-X.
 |  | 
	
		|  | 
	
		| Langton 
 
 
 Joined: 29 Nov 2009
 Posts: 25
 
 
 
			    
 
 | 
			
				|  |  
				|  Posted: Fri Jan 17, 2020 7:15 pm |   |  
				| 
 |  
				| The answer read like this... 
 We have not been able to get the debugging spec from Microchip.  We recently tried again with no response.
 We are just now trying other avenues within Microchip to try to get an answer.
 
 For now we do not have debug support for CH/CK parts.  We will put support in as soon as we get the specification
 from Microchip.
 
 For now, I'll do dev on a similar chip and then cross it over to the CK. Hopefully there will be a resolve sooner rather than later.
 |  | 
	
		|  | 
	
		| razor 
 
 
 Joined: 26 Feb 2022
 Posts: 1
 Location: Spain
 
 
			    
 
 | 
			
				|  |  
				|  Posted: Sat Feb 26, 2022 4:08 am |   |  
				| 
 |  
				| Hi experts, 
 I'm new with CCS and dsPIC33CK familiy (but many years with CCS & PIC16F & PIC18F). I'm using a dsPIC33CK64MP105 on a PICKit4 (and ICD3) with MPLAB X and PCD 5.107. I'm able to program the device but I'm not able to start debugging any board (we have several prototypes). Always reporting "device not ready for debuging... common cause oscillator or PGD/PGC pins..". Same results in an evaluation board (dsPICDEM MCSM).
 
 Does anybody know if CCS 5.107 has already debug support for this dsPIC33CK64MP105?
 
 Thanks!
 |  | 
	
		|  | 
	
		|  |