ICD & PBP && how to get it to work

[phoenix_1]

If you're using MCS+ ICD, then you should not be trying to use the standard serial
communicator in MCS+.

Inside the ICD window HSEROUT will display whatever you send in the lower section of
the ICD window. When it lands on an HSEROUT while running the ICD, and small serial
ICD terminal window will automatically pop-up asking for input.

DEFINE LOADER_USED 1 ' using MCS+ bootloader
DEFINE OSC 20 ' <-- DEFINE your OSC speed. gotta have this for MCS ICD.

MyVar VAR BYTE

Loop2:
      HSERIN [MyVar] ' <-- window pops-up waiting for input
      HSEROUT ["MyVar = ",DEC MyVar,13,10] '<-- displays input
      PAUSE 500
      GOTO Loop2

I've attached a screen capture of the above running in MCS+ ICD. Tested on an
18F4431.

If you still have trouble try blinking an LED with the ICD just to make sure you have
everything setup properly.

One question :
If I want to use ICD with 18F4550

    DEFINE LOADER_USED 1 ' using MCS+ bootloader
    DEFINE OSC 48

I get error from MCSP that can't find OSC48 setup for ICD in any file...
Any help please.
Regard's

[Darrel Taylor]

You can't use the ICD with the PIC running at greater than 40Mhz.
There's no real reason other than MCS+ won't let you.

But, you can increase the divider so the the core runs at a lower freq.
_CPUDIV_OSC3_PLL4_1L will give 24mhz.

Then change to DEFINE OSC 24.

Also, the ICD is not compatible with standard USB routines.
It will likely drop the connection to the PC because it's not servicing fast enough. (Unless using USB_ASM_Service.pbp)
<br>

[phoenix_1]

You can't use the ICD with the PIC running at greater than 40Mhz.
There's no real reason other than MCS+ won't let you.

But, you can increase the divider so the the core runs at a lower freq.
_CPUDIV_OSC3_PLL4_1L will give 24mhz.

Then change to DEFINE OSC 24.

Also, the ICD is not compatible with standard USB routines.
It will likely drop the connection to the PC because it's not servicing fast enough. (Unless using USB_ASM_Service.pbp)
<br>

OK Darrel ,
I only test ICD on 18F4550.
In Proton+ I was probe and work OK. But I was edit .XML to accept 48Mhz clock and at that freq. need to use 115200 speed in definition of HSEROUT ..
That is problem in PBP ICD 100% but we or I cant edit .ICD file for new devices...

I was probe your suggesst an work 100% ok.
In my code for test I not use USB. Only simple keypad reding + LCDOUT.

Best regards

[jellis00]

One question :
Originally Posted by Bruce
If you're using MCS+ ICD, then you should not be trying to use the standard serial
communicator in MCS+.

Inside the ICD window HSEROUT will display whatever you send in the lower section of
the ICD window. When it lands on an HSEROUT while running the ICD, and small serial
ICD terminal window will automatically pop-up asking for input.


Code:
DEFINE LOADER_USED 1 ' using MCS+ bootloader
DEFINE OSC 20 ' <-- DEFINE your OSC speed. gotta have this for MCS ICD.

MyVar VAR BYTE

Loop2:
HSERIN [MyVar] ' <-- window pops-up waiting for input
HSEROUT ["MyVar = ",DEC MyVar,13,10] '<-- displays input
PAUSE 500
GOTO Loop2I've attached a screen capture of the above running in MCS+ ICD. Tested on an
18F4431.

If you still have trouble try blinking an LED with the ICD just to make sure you have
everything setup properly.

Where did this quote come from since I don't see it in this thread. I would like to go to it and review the referenced image.

[Darrel Taylor]

Where did this quote come from...not in this thread??

Post #5, this thread.