- Error Starting Debugger - Debug Executive not supported by

[SPCH]

Quick note - I've spent the last two weeks (off and on) going through this Forum looking for a solution. - Background follow details.

Can't run ICD - I'm getting the error message:
- Error Starting Debugger
- Debug Executive not supported by Programmer

mikroProg for PIC, dsPIC and PIC32 - PID: MIKROE-764

Windows 10 64bit (loaded 64bit - latest windows version - not specified as 10 - downloaded from mikroe.com)
mikroC Pro for Pic version 7.1.0
mikroProg Suite version 2.51
WDM Internal Version 6.00.16386
mikfoProg Firmware Verison v01.16.12.21 (note: in Select USB Programmer Device it states v2.11, highlighted in blue)

PIC18K14L22
Nothing connected pin wise - matches that in mikroProg manual page 19
program is simple main() with included while(1) loop
Build/Debugger type
Build Type: ICD Debug
Debugger mikroICD


Verified MCLR and debug is enabled in configuration bits - (only from Project Edit screen)
Oscillator Selection: Internal RC oscillator

Tried both external and internal power (from program pod)
Tried closing programmer prior to F9 - Run debugger
Verified PIC is supported in Prog history - v2.1 support added

mikroProg works flawlessly as a programmer - multiplexer pins operate as expected.

Can someone point me towards a specific setup for a simple PIC?
Are my drivers goofy?
Should I be using an external oscillator?

--------------------------

History - I've been using the mikroC for Pic since 2014 - been programming firmware since 1975 (yes - there were 4 bit micros back then) Intel, Motorola, Zilog, Renesas, other. Programming devices up until two weeks ago was through microChip pikKit 2. I wanted a single solution and liked the multiplexing option so purchased the mikroProg for PIC.

Something's up - as I don't see a tremendous number of others having this issue.

[SPCH]

Additional info:
Installed drivers as Administrator - actually went in and uninstalled and re-installed again this morning
Could not find Scheme for P18F14K22 (under "Edit Project")
When attempting to load any other Scheme I get the error message: "Bad format of scheme file"

[strahinja.jacimovic]

Hi,

mikroProg for PIC programmer comes with mikroICD support.

Could you please explain how you connected the mikroProg with your MCU?
If you have a custom board, please attach the snippet of your schematic showing the mikroProg-MCU connections.

How are you powering your board, are you using an external power source?

You can power the device from mikroProg directly.
In compiler click on Tools>MikroProg Power Options to enable powering the device from mikroProg while debugging.

Also, MCLR pin in Configuration Bits ("Edit Project") needs to be enabled for the debug to work fine.

As for the scheme, you can't load a scheme for another MCU for your PIC. It has to be a PIC18F14K22 scheme. You would have to set those fields by hand.
You can find everything you need in order to set things up correctly in the datasheet on the manufacturers official site:
http://www.microchip.com/wwwproducts/en/PIC18F14K22

Kind regards,

[SPCH]

Strahinja - thank you for the response. Here's answers to your questions:

I attached three images: two are actual photos of the board the third is the schematic. Note schematic does not show cap across power. Sorry about the large photos - still figuring out how this works.

I attempted powering both directly via the mikroProg as well as an external power supply - neither worked.

The MCLR pin is enabled - in the project edit menu. I've also verified the correct configuration bit is enabled when selected.

My comment about scheme was following up on another comment I ran across in another post. Just more information - I'll leave it up to you if it's important or not.

I uninstalled everything from the computer (compiler and prog files/ drivers) and reinstalled as administrator this morning - no change (still does not work)

Thanks again for your assistance.
Peter

[strahinja.jacimovic]

Hi,

Do you have some load on PGC and PGD lines?

Kind regards,

[SPCH]

There is no load on either pin 19 - PGD or pin 18 - PGC. There are no pins setup as weak pull ups either.
Wiring is as shown in the photo.

Here is the code: Note that there are no libraries included.

void main() {

int i ;

while (1){
i++ ;
}

}

Here are the compile and link messages:

0 1 mikroCPIC1618.exe -MSF -DBG -pP18F14K22 -UICD -RA -GC -DL -O11111114 -fo8 -N"D:\MicroPIC Projects\TEST\TT.mcppi" -SP"C:\Program Files (x86)\mikroC PRO for PIC\Defs\" -SP"C:\Program Files (x86)\mikroC PRO for PIC\uses\P18\" -SP"D:\MicroPIC Projects\TEST\" -SP"C:\Users\Public\Documents\Mikroelektronika\mikroC PRO for PIC\Defs\" -SP"C:\Users\Public\Documents\Mikroelektronika\mikroC PRO for PIC\uses\P18\" "TT.c" "__Lib_Math.mcl" "__Lib_MathDouble.mcl" "__Lib_System.mcl" "__Lib_Delays.mcl"
0 1139 Available RAM: 491 [bytes], Available ROM: 16384 [bytes]
0 122 Compilation Started P18F14K22.c
1433 123 Compiled Successfully P18F14K22.c
0 122 Compilation Started __Lib_Delays.c
172 123 Compiled Successfully __Lib_Delays.c
0 122 Compilation Started TT.c
10 123 Compiled Successfully TT.c
4 1164 Variable 'i' has been eliminated by optimizer TT.c
0 127 All files Compiled in 46 ms
0 1144 Used RAM (bytes): 0 (1%) Free RAM (bytes): 491 (99%) Used RAM (bytes): 0 (1%) Free RAM (bytes): 491 (99%)
0 1144 Used ROM (bytes): 32 (1%) Free ROM (bytes): 16352 (99%) Used ROM (bytes): 32 (1%) Free ROM (bytes): 16352 (99%)
0 125 Project Linked Successfully TT.mcppi
0 1004 COFF file successfully generated COFF file successfully generated
0 128 Linked in 235 ms
0 129 Project 'TT.mcppi' completed: 453 ms
0 103 Finished successfully: 04 Jan 2018, 01:30:49 TT.mcppi

[strahinja.jacimovic]

Hi,

You could try giving your variable 'i' a starting value.
Something like this:

int i=0;

I think you are just in an indefinite loop without actually doing anything, because it says the following: "Variable 'i' has been eliminated by optimizer TT.c"

You could try this. Other than that, I'm not quite sure what the problem could be. Everything else seems to be in order.

I would have to consult with my colleagues before giving you an indefinite answer.

Kind regards,

[SPCH]

The intent was to demonstrate the minimum size of code where the ICE would still not operate. You are correct, it is a loop - that was the intent, just enough to compile.

By the way - you gave me an indefinite answer - I look forward to a definite answer.

Thanks for your time - I look forward to using the tool I purchased as intended.

Peter