Pickit2 problems

For Flowcode users to discuss projects, flowcharts, and any other issues related to Flowcode 5.
To post in this forum you must have a registered copy of Flowcode 5 or higher.

Moderator: Benj

Post Reply
DannyBerry
Posts: 29
Joined: Tue Aug 30, 2011 9:20 pm
Has thanked: 11 times
Been thanked: 1 time

Pickit2 problems

Post by DannyBerry »

I recently upgraded this to v2.61 and now I can't compile to chip from within flowcode. It only works with compile to hex. Problem with that is having to open another program just to burn the file to the chip. Does anybody have any suggestions on how to fix this other than uninstalling and going back to the original. I did this upgrade to list a chip that wasn't avaibale in the original.

Thanks,

Danny

User avatar
Benj
Matrix Staff
Posts: 15312
Joined: Mon Oct 16, 2006 10:48 am
Location: Matrix TS Ltd
Has thanked: 4803 times
Been thanked: 4314 times
Contact:

Re: Pickit2 problems

Post by Benj »

Hi Danny,

One option is to use the PICkit standalone programming utility and switching on the hex file monitoring functionality. This basically keeps scanning a hex file on your machine. When the hex file changes the updated program is automatically sent to the device.

You should however be able to use the command line tool still via Flowcode independent of the version of standalone PICkit software you are using. Maybe go into the Chip -> Compiler options menu and try clicking restore defaults and see if this makes any difference.

Let me know how you get on.

DannyBerry
Posts: 29
Joined: Tue Aug 30, 2011 9:20 pm
Has thanked: 11 times
Been thanked: 1 time

Re: Pickit2 problems

Post by DannyBerry »

switching on the hex file monitoring functionality
Hi Ben,

I don't see where you are talking about setting this in the stand alone programmer. Can you post a screen shot of it.

Thanks,

Danny

User avatar
Benj
Matrix Staff
Posts: 15312
Joined: Mon Oct 16, 2006 10:48 am
Location: Matrix TS Ltd
Has thanked: 4803 times
Been thanked: 4314 times
Contact:

Re: Pickit2 problems

Post by Benj »

Hi Danny,

Its a button at the bottom right hand side of the window with the text "Auto Import Hex + Write Device" Click it and it will ask for the hex file to monitor.

One downside of this I have noticed is that while the hex file is being written by the compiler the PICkit software may pop up error windows saying it cant read the hex file. If you minimise the PICkit window and keep Flowcode etc on the top then it should all work well and you shouldn't have to keep clicking to close the error windows. Then when your done you can use the control + f4 shortcut to get rid of them all.

DannyBerry
Posts: 29
Joined: Tue Aug 30, 2011 9:20 pm
Has thanked: 11 times
Been thanked: 1 time

Re: Pickit2 problems

Post by DannyBerry »

Oh...OK,

Thanks for the quick reply Ben.. :D

DannyBerry
Posts: 29
Joined: Tue Aug 30, 2011 9:20 pm
Has thanked: 11 times
Been thanked: 1 time

Re: Pickit2 problems

Post by DannyBerry »

Benj wrote:Hi Danny,



You should however be able to use the command line tool still via Flowcode independent of the version of standalone PICkit software you are using. Maybe go into the Chip -> Compiler options menu and try clicking restore defaults and see if this makes any difference.

Let me know how you get on.
I tried default settings...didn't work...Put it back to the way I had it before...still doesn't work straight out of flowcode pressing the compile to chip Icon....Can you take a look at the attachment and see if anything looks out of the ordinary...Brandon has these same settings and his works...?

Thanks,
Danny
Attachments
Flowcode first lesson_rev2.msg.txt
(4.65 KiB) Downloaded 304 times

DannyBerry
Posts: 29
Joined: Tue Aug 30, 2011 9:20 pm
Has thanked: 11 times
Been thanked: 1 time

Re: Pickit2 problems

Post by DannyBerry »

I figured out how to get it back working.....I overwrote the pk2DeviceFile.dat file with the one that I had dated 1/9/2009. The one with the update to pickit2 V2.61 dated 10/4/2011 is where the problem lies....Hope this helps anybody else that might fall into the same trap..... :)

I'm sure there is a solution to it ...if anybody knows..I'm all ears..... :? but for now ..at least I'm back to square one...with a one button click from within flowcode.

Thanks,

Danny

Post Reply