Matrix user forums

Hi

I'm electronic teacher in France.

Sorry for my bad Englih

I use Flowcode V3.2.40 .I have try to run PKITKIT2 in commande line with pkΓ©cmd.exe and line option.
BUT PICkit2 give an error message CONFIG WORD no find.....
The .HEX file produce by FLowcode don't have the config word inside.

I know why ,FLOWCODE V3 don't use MPLAB ,don't use MPASM and so can't give the good hex file!!!
FlowcodeV3 use BOOSTC compiler assembler et not MPASM!!!!
I have use #pragma DATA config,0x3F39 but Flowcode MAKE NOTHING!!!!

MY FIRST QUESTION IS :HOW TO PASS THE CONFIG WORD OF PIC to PICKIT2 under FLOWCODE V3 ??????

MERCI D'AVANCE
BEst regard

T.ROMANO

MY SECOND QUESTION IS :HOW BUILD UNDER FLOWCODE V3 the hex file with PIc config word in it???

Hello

Use the chip - configure menu to edit the configuration details. If you did not install PPP when you installed Flowcode then the configuration function will not work correctly. You can download PPP from our downloads section.

Hi

I have PPV3 but I don't want use it as programmer ,I want PICKIT2 only.I know that Chip->Config....
This had in C file the #pragma DATA 0x2007,0x3F39 (it's an example for PIC16F877)

I want use in the menu Chip->Option at the line Programmer call the pk2cmd.exe ,this call PICKIT2 automatic with command line.
My probleme is that if I delete PPV3 from option->programmer menu in FLowcode, Flowcode don't insert the config word in the hex file!!!!!!

It s work with Flowcode 2!! because MPLAB include the config word in hex file but not FLowcode 3 .

Have you a solution

Merci de votre rΓ©ponse

Regards

T.Romano

Hello

Please see this forum posting regarding your question.

http://www.matrixmultimedia.com/mmforum ... sers#p3928

The link Ben gave is not applicable any more. This is how we linked with PICkit2 before we created a custom version of Microchip's command line interface programmer.

The following post is more appropriate:
http://www.matrixmultimedia.com/mmforum ... f=5&t=4161

My Pickit software suddenly stopped working last week. I got it working again by removing NET Framework Service Pack 1 which I think was auto installed by Windows update last week. I am going to ask Microchip if they know about this ‘bug’.