Post by thread:[PIC] pk2cmd -d command fails

If this is an improper forum for questions relating to the pk2cmd release, please direct me to where I can ask questions. I believe I have the utility installed properly on my MacBook. I run 'pk2cmd -?v' and the program responds with the following: bash-3.2$ pk2cmd -?v Executable Version: 1.10.00 Device File Version: 1.51.00 OS Firmware Version: 2.30.01 Operation Succeeded bash-3.2$ This would seem to imply that the Pickit2 is seen, and that the files required for the program to operate are in the proper directories. I tried to power up the low pin count board and received the following response: bash-3.2$ pk2cmd t PICkit 2 found with Operating System v2.30.01 Use -D to download minimum required OS v2.31.00 or later bash-3.2$ OK, it needs an updated operating system, so I use the -D command and get the following: bash-3.2$ pk2cmd -d PICkit 2 found with Operating System v2.30.01 Use -D to download minimum required OS v2.31.00 or later Error opening hex file. bash-3.2$ So now I'm lost. I did not find a discussion forum on Microchip's website, perhaps because they say this program is unsupported. I'm sure there are people here that may be able to help me along. Thanks in advance for any help. Joe

Joe, have you tried using -D instead of -d as a command line parameter to the program? Regards, - Marcel On Wed, Jul 2, 2008 at 1:05 PM, Joseph Bento <spam_OUTjosephTakeThisOuTkirtland.com> wrote: {Quote hidden}> If this is an improper forum for questions relating to the pk2cmd > release, please direct me to where I can ask questions. > > I believe I have the utility installed properly on my MacBook. I run > 'pk2cmd -?v' and the program responds with the following: > > bash-3.2$ pk2cmd -?v > > Executable Version: 1.10.00 > Device File Version: 1.51.00 > OS Firmware Version: 2.30.01 > > > Operation Succeeded > bash-3.2$ > > This would seem to imply that the Pickit2 is seen, and that the files > required for the program to operate are in the proper directories. > > I tried to power up the low pin count board and received the following > response: > > bash-3.2$ pk2cmd t > PICkit 2 found with Operating System v2.30.01 > Use -D to download minimum required OS v2.31.00 or later > > bash-3.2$ > > OK, it needs an updated operating system, so I use the -D command and > get the following: > > bash-3.2$ pk2cmd -d > PICkit 2 found with Operating System v2.30.01 > Use -D to download minimum required OS v2.31.00 or later > Error opening hex file. > > bash-3.2$ > > So now I'm lost. I did not find a discussion forum on Microchip's > website, perhaps because they say this program is unsupported. I'm > sure there are people here that may be able to help me along. > > Thanks in advance for any help. > > Joe > > > > > > -

Hi Marcel and all, I have an update... Unbeknownst to me at the time, the needed operating system was apparently downloaded to the Mac's desktop - at least that's where I found the file. I then retried the -d command with the PK2V023100.hex filename following, and it installed properly. It looks as though everything is working now - I just need to become comfortable with the command line. I'll probably be jumping around between pk2cmd and MPLAB before I finally am confident enough to remove Parallels and XP. According to the readme included with the program, the commands are apparently not case sensitive. Thanks, all. This list is a great learning tool. Joe On Jul 1, 2008, at 10:18 PM, Marcel Birthelmer wrote: {Quote hidden}> Joe, > have you tried using -D instead of -d as a command line parameter to > the > program? > Regards, > - Marcel > > On Wed, Jul 2, 2008 at 1:05 PM, Joseph Bento <.....josephKILLspam@spam@kirtland.com> > wrote: > >> If this is an improper forum for questions relating to the pk2cmd >> release, please direct me to where I can ask questions. >> >> I believe I have the utility installed properly on my MacBook. I run >> 'pk2cmd -?v' and the program responds with the following: >> >> bash-3.2$ pk2cmd -?v >> >> Executable Version: 1.10.00 >> Device File Version: 1.51.00 >> OS Firmware Version: 2.30.01 >> >> >> Operation Succeeded >> bash-3.2$ >> >> This would seem to imply that the Pickit2 is seen, and that the files >> required for the program to operate are in the proper directories. >> >> I tried to power up the low pin count board and received the >> following >> response: >> >> bash-3.2$ pk2cmd t >> PICkit 2 found with Operating System v2.30.01 >> Use -D to download minimum required OS v2.31.00 or later >> >> bash-3.2$ >> >> OK, it needs an updated operating system, so I use the -D command and >> get the following: >> >> bash-3.2$ pk2cmd -d >> PICkit 2 found with Operating System v2.30.01 >> Use -D to download minimum required OS v2.31.00 or later >> Error opening hex file. >> >> bash-3.2$ >> >> So now I'm lost. I did not find a discussion forum on Microchip's >> website, perhaps because they say this program is unsupported. I'm >> sure there are people here that may be able to help me along. >> >> Thanks in advance for any help. >> >> Joe >> >> >> >> >> >> --

Hi all, A little bit hijacking this topic, hope you don't mind Joseph but I think you question is answered already :-) So my problem with pk2cmd for linux is that the /proc/bus/usb/ tree is tied to root user root group. I can change the permission temporary, however, each and every time I unplug and replug the device it appears on a different device number even if I plug it back into the same connector. This means a new entry appears on the /proc/bus/usb/<busno>/... tree with the default root:root ownership and access rights. And this leads to the problem that each and every time I have to issue a chmod or chown command with sudo to be able to use pk2cmd on my own user priviledge. So the question is if anyone knows hows to make these ownership or rights permanent so no tricks needed to use pk2cmd. Thanks Tamas On Wed, Jul 2, 2008 at 5:46 AM, Joseph Bento <josephKILLspamkirtland.com> wrote: {Quote hidden}> Hi Marcel and all, > > I have an update... Unbeknownst to me at the time, the needed > operating system was apparently downloaded to the Mac's desktop - at > least that's where I found the file. I then retried the -d command > with the PK2V023100.hex filename following, and it installed > properly. It looks as though everything is working now - I just need > to become comfortable with the command line. I'll probably be jumping > around between pk2cmd and MPLAB before I finally am confident enough > to remove Parallels and XP. > > According to the readme included with the program, the commands are > apparently not case sensitive. > > Thanks, all. This list is a great learning tool. > > Joe > > > > On Jul 1, 2008, at 10:18 PM, Marcel Birthelmer wrote: > > > Joe, > > have you tried using -D instead of -d as a command line parameter to > > the > > program? > > Regards, > > - Marcel > > > > On Wed, Jul 2, 2008 at 1:05 PM, Joseph Bento <.....josephKILLspam.....kirtland.com> > > wrote: > > > >> If this is an improper forum for questions relating to the pk2cmd > >> release, please direct me to where I can ask questions. > >> > >> I believe I have the utility installed properly on my MacBook. I run > >> 'pk2cmd -?v' and the program responds with the following: > >> > >> bash-3.2$ pk2cmd -?v > >> > >> Executable Version: 1.10.00 > >> Device File Version: 1.51.00 > >> OS Firmware Version: 2.30.01 > >> > >> > >> Operation Succeeded > >> bash-3.2$ > >> > >> This would seem to imply that the Pickit2 is seen, and that the files > >> required for the program to operate are in the proper directories. > >> > >> I tried to power up the low pin count board and received the > >> following > >> response: > >> > >> bash-3.2$ pk2cmd t > >> PICkit 2 found with Operating System v2.30.01 > >> Use -D to download minimum required OS v2.31.00 or later > >> > >> bash-3.2$ > >> > >> OK, it needs an updated operating system, so I use the -D command and > >> get the following: > >> > >> bash-3.2$ pk2cmd -d > >> PICkit 2 found with Operating System v2.30.01 > >> Use -D to download minimum required OS v2.31.00 or later > >> Error opening hex file. > >> > >> bash-3.2$ > >> > >> So now I'm lost. I did not find a discussion forum on Microchip's > >> website, perhaps because they say this program is unsupported. I'm > >> sure there are people here that may be able to help me along. > >> > >> Thanks in advance for any help. > >> > >> Joe > >> > >> > >> > >> > >> > >> --

On Wed, Jul 2, 2008 at 3:24 PM, Tamas Rudnai <EraseMEtamas.rudnaispam_OUTTakeThisOuTgmail.com> wrote: > So my problem with pk2cmd for linux is that the /proc/bus/usb/ tree is tied > to root user root group. I can change the permission temporary, however, > each and every time I unplug and replug the device it appears on a different > device number even if I plug it back into the same connector. This means a > new entry appears on the /proc/bus/usb/<busno>/... tree with the default > root:root ownership and access rights. And this leads to the problem that > each and every time I have to issue a chmod or chown command with sudo to be > able to use pk2cmd on my own user priviledge. > > So the question is if anyone knows hows to make these ownership or rights > permanent so no tricks needed to use pk2cmd. That depends on the distribution. Please read the following links: http://www.gphoto.org/doc/manual/permissions-usb.html Also you can search my blog. http://mcuee.blogspot.com/search/label/PICKit This is also evolving quite fast. For example, I need to use a new method called PolicyKit under Fedora 9. http://groups.google.com/group/pickit-devel/browse_thread/thread/86c67b83202815cf Regards, Xiaofan

Thanks Xiaofan for the quick answer, your blog and the other link seems to be perfect to solve my problem - will try it in the evening. Tamas On Wed, Jul 2, 2008 at 9:33 AM, Xiaofan Chen <xiaofancspam_OUTgmail.com> wrote: {Quote hidden}> On Wed, Jul 2, 2008 at 3:24 PM, Tamas Rudnai <@spam@tamas.rudnaiKILLspamgmail.com> > wrote: > > So my problem with pk2cmd for linux is that the /proc/bus/usb/ tree is > tied > > to root user root group. I can change the permission temporary, however, > > each and every time I unplug and replug the device it appears on a > different > > device number even if I plug it back into the same connector. This means > a > > new entry appears on the /proc/bus/usb/<busno>/... tree with the default > > root:root ownership and access rights. And this leads to the problem that > > each and every time I have to issue a chmod or chown command with sudo to > be > > able to use pk2cmd on my own user priviledge. > > > > So the question is if anyone knows hows to make these ownership or rights > > permanent so no tricks needed to use pk2cmd. > > That depends on the distribution. > > Please read the following links: > http://www.gphoto.org/doc/manual/permissions-usb.html > > Also you can search my blog. > http://mcuee.blogspot.com/search/label/PICKit > > This is also evolving quite fast. For example, I need to > use a new method called PolicyKit under Fedora 9. > > http://groups.google.com/group/pickit-devel/browse_thread/thread/86c67b83202815cf > > Regards, > Xiaofan > -

Thanks Xiaofan, Just modified the udev settings as mentioned on the first link you gave and it solved the problem. Even could get it work with VirtualBox, which I currently evaluating if that runs the XP correctly. Now I can use the Win client as well as MPLAB+PicKit2 inside that VirtualBox machine. BTW, it seems that the firmware is more fresh supplied with pk2cmd for Linux than the PicKit2 2.50 tool for Windows. Tamas On Wed, Jul 2, 2008 at 10:04 AM, Tamas Rudnai <KILLspamtamas.rudnaiKILLspamgmail.com> wrote: {Quote hidden}> Thanks Xiaofan for the quick answer, your blog and the other link seems to > be perfect to solve my problem - will try it in the evening. > > Tamas > > > > On Wed, Jul 2, 2008 at 9:33 AM, Xiaofan Chen <RemoveMExiaofancTakeThisOuTgmail.com> wrote: > >> On Wed, Jul 2, 2008 at 3:24 PM, Tamas Rudnai <spamBeGonetamas.rudnaispamBeGonegmail.com> >> wrote: >> > So my problem with pk2cmd for linux is that the /proc/bus/usb/ tree is >> tied >> > to root user root group. I can change the permission temporary, however, >> > each and every time I unplug and replug the device it appears on a >> different >> > device number even if I plug it back into the same connector. This means >> a >> > new entry appears on the /proc/bus/usb/<busno>/... tree with the default >> > root:root ownership and access rights. And this leads to the problem >> that >> > each and every time I have to issue a chmod or chown command with sudo >> to be >> > able to use pk2cmd on my own user priviledge. >> > >> > So the question is if anyone knows hows to make these ownership or >> rights >> > permanent so no tricks needed to use pk2cmd. >> >> That depends on the distribution. >> >> Please read the following links: >> www.gphoto.org/doc/manual/permissions-usb.html >> >> Also you can search my blog. >> http://mcuee.blogspot.com/search/label/PICKit >> >> This is also evolving quite fast. For example, I need to >> use a new method called PolicyKit under Fedora 9. >> >> groups.google.com/group/pickit-devel/browse_thread/thread/86c67b83202815cf >> >> Regards, >> Xiaofan >> --