bootloader "PIC Not responding" message

[wirelessage]

Hello all:

I have a PIC18F2680. I am using the CCS Bootloader client to talk to my firmware.
Before using the loader code to download firmware, I am just trying to get the communication going between the client and firmware and running into some issues.

I am getting a "PIC Not responding" message on the PC with the following log:
APRO v4.07
Compiler : Delphi 2006
Operating System : Windows XP 5.1 Service Pack 3
Device: \\.\COM1
Date/time: 15/02/13, 11:44:37
Time Type SubType Data OtherData
-------- -------- ------------ -------- ---------
0000.085 TrDatChg Avail 00000001
0000.091 TrgHdAlc Window 003005A0
0000.092 Dispatch WriteCom 00000001 ;
0000.092 Dispatch WriteCom 00000001 H
0000.092 Dispatch WriteCom 00000001 E
0000.092 Dispatch WriteCom 00000001 L
0000.092 Dispatch WriteCom 00000001 L
0000.092 Dispatch WriteCom 00000001 O
0000.092 Dispatch WriteCom 00000001 [0D]

I am suspecting it be a flow control (timeout) issue. I know that the firmware is receiving these bytes. But I suspect the PC is not getting any messages back from the firmware. However, in order to debug this I need to know what the CCS Client is configured for?
Can anyone shed some light on the ccs bootloader client Flowcontrol configuration??
Also, is the source code for this client available?
I have my firmware setup to 9600baud,no parity,8bit,
The Client side is setup 9600 Baud, no parity, 8 bit, XON/XOFF Flow control.

[bkamen]

When you say "bootloader client" - I'm assuming you have compiled the bootloader with CCS and programmed it to the PIC...

And now you are using another PC program (3rd party or written by you) to send the application code to the PIC's bootloader for programming, yes?

If this is the case, there IS a CCS Bootloader program called SIOW.exe which is what you COULD be using to test the bootloader. After all, the PIC bootloader sends out commands back to the PC client while it's doing its work so that the PC program doesn't overrun the bootloader while it's programming.

-Ben
_________________
Dazed and confused? I don't think so. Just "plain lost" will do. :D

[wirelessage]

- I am using CCS compiler to generate my firmware hex file and program that into the PIC.
- When I say bootloader client, I am referring to the "ccs bootloader" program one can download from CCS website. I call it a client because it "initiates" the connection to talk to the firmware.

- Using the CCSBOOTLOADER.EXE is great, but I would prefer to have the code for it to know what it is doing; that way I can debug what is going on (with the commands the EXE is sending and expecting from the PC side).

[bkamen]