ICD & PBP && how to get it to work

[Bruce]

I don't have a 4550 to test, but it works fine with an 18F4431. See attached.

Does it work if you try something simple like this?

Pause 10     ' This statement is placed at beginning of code for ICD use
;--- if you un-comment these, you must comment the ones in the .inc file--
ASM ; 18F2550/4550, 8mhz crystal
   __CONFIG   _CONFIG1L, _PLLDIV_2_1L & _CPUDIV_OSC4_PLL6_1L & _USBDIV_2_1L
   __CONFIG   _CONFIG1H, _FOSC_HSPLL_HS_1H
   __CONFIG   _CONFIG2L, _PWRT_ON_2L & _BOR_OFF_2L & _VREGEN_ON_2L
   __CONFIG   _CONFIG2H, _WDT_ON_2H & _WDTPS_512_2H
   __CONFIG   _CONFIG3H, _PBADEN_OFF_3H ; PortB resets as digital
   __CONFIG   _CONFIG4L, _LVP_OFF_4L & _XINST_OFF_4L
ENDASM
 
 DEFINE OSC 16
 
 MyVar VAR BYTE
  
Main:  
  FOR MyVar = 0 TO 50
   HIGH 0
   PAUSE 5
   LOW 0
   PAUSE 5
  NEXT
  GOTO Main
  
  END

If the above works, then it may be something in your code causing the problem
or maybe a bad ICD model file?

Sorry I can't offer more help, but I haven't used MCS+ ICD in years.

Have you tried contacting Mecanique for tech support?

[jellis00]

I don't have a 4550 to test, but it works fine with an 18F4431. See attached.

Does it work if you try something simple like this?

Pause 10     ' This statement is placed at beginning of code for ICD use
;--- if you un-comment these, you must comment the ones in the .inc file--
ASM ; 18F2550/4550, 8mhz crystal
   __CONFIG   _CONFIG1L, _PLLDIV_2_1L & _CPUDIV_OSC4_PLL6_1L & _USBDIV_2_1L
   __CONFIG   _CONFIG1H, _FOSC_HSPLL_HS_1H
   __CONFIG   _CONFIG2L, _PWRT_ON_2L & _BOR_OFF_2L & _VREGEN_ON_2L
   __CONFIG   _CONFIG2H, _WDT_ON_2H & _WDTPS_512_2H
   __CONFIG   _CONFIG3H, _PBADEN_OFF_3H ; PortB resets as digital
   __CONFIG   _CONFIG4L, _LVP_OFF_4L & _XINST_OFF_4L
ENDASM
 
 DEFINE OSC 16
 
 MyVar VAR BYTE
  
Main:  
  FOR MyVar = 0 TO 50
   HIGH 0
   PAUSE 5
   LOW 0
   PAUSE 5
  NEXT
  GOTO Main
  
  END

If the above works, then it may be something in your code causing the problem
or maybe a bad ICD model file?

Sorry I can't offer more help, but I haven't used MCS+ ICD in years.

Have you tried contacting Mecanique for tech support?

I pasted your code into my MCS+ and ran the ICD and it still doesn't show the Variables Tab (see attached image).
I notice that the image of your ICD run shows a couple of additional items in the Tool Bar that mine doesn't show. It makes me wonder if there is a version difference between us that may be causing my problem. My version of MCS+ is 3.0.0.5. What is yours??

I am also going to send your image and my image to Mechanique and ask them what is going on. I really appreciate your help on this

[Bruce]

MCS+ 3.0.0.5 on Windows XP.

[jellis00]

MCS+ 3.0.0.5 on Windows XP.

Bruce, if you would be so kind, would you please put your cursor on each of the four icons on the right end of the 1st Tool Bar line of your version of MCS+ and then tell me what their individual descriptions are? Once I know what these missing icons are for I want to ask mechanique why they don't appear on my version of 3.0.0.5 when running XP.
Thanks!
JE

[Bruce]

Those are icons for the MCS+ boot-loader. Loader Read, Verify, Erase, Information.

[jellis00]

Thanks to Darrel Taylor's response at techsupport assitant at meLabs, I have solved this mysterious problem. Let me explain, because this may be encountered by other users of the Micro Code Studio Plus (MCS+) ICD.

It turns out that the ICD model that came on my CD-ROM that delivered MCS+ to me was not correct for the 18F4550. Darrel had downloaded this .inc file from the Beta models and emailed it to me. When I replaced the ICD model I had for the 18F4550 with the one he sent I started seeing Variables Tab.
The icons I thought I was missing in the tool bar only show when using a boot loader, as explained by Bruce Rentron in above post.
Chasing down this problem took 3 days out of my time....no thanks to Mecanique's tech support who never responded to my emailed request for support.

[Bruce]

That was one of my suspicions, but I'm glad you got it sorted.

Post #15 above;

or maybe a bad ICD model file?

no thanks to Mecanique's tech support who never responded to my emailed request for support.

Bummer, but that does reinforce my little ending blurb in post #10 above...;o)