• AVR Freaks

PICkit2 Devicefile Editor

Page: < 12345.. > >> Showing page 2 of 6
Author
Post
Essentials Only Full Version
dougy83
New Member
  • Total Posts : 28
  • Reward points : 0
  • Joined: 2008/06/06 02:06:39
  • Location: 0
  • Status: offline
RE: PICkit2 Devicefile Editor 2010/03/28 22:37:57 (permalink)
0
The PK2 devicefile editor version 1.0.0.5 is now available at the above site. It should fix the issue with the missing serialization attribute.
#21
xiaofan
Super Member
  • Total Posts : 6247
  • Reward points : 0
  • Joined: 2005/04/14 07:05:25
  • Location: Singapore
  • Status: offline
RE: PICkit2 Devicefile Editor 2010/03/29 00:10:49 (permalink)
0
Thanks a lot. It seems to work well now!

  USB_Links and libusb
#22
dtran11
Super Member
  • Total Posts : 244
  • Reward points : 0
  • Joined: 2009/10/20 08:33:03
  • Location: 0
  • Status: offline
RE: PICkit2 Devicefile Editor 2010/03/29 07:00:05 (permalink)
0
Thanx for the update. I am trying to add the new PIC32 (5/6/7) series.
It looks to me like I only need to copy from any existing PIC32 config
and change the PartName, DeviceID, and ProgramMem. Am I right?
#23
xiaofan
Super Member
  • Total Posts : 6247
  • Reward points : 0
  • Joined: 2005/04/14 07:05:25
  • Location: Singapore
  • Status: offline
RE: PICkit2 Devicefile Editor 2010/03/29 07:25:08 (permalink)
0
ORIGINAL: dtran11

Thanx for the update. I am trying to add the new PIC32 (5/6/7) series.
It looks to me like I only need to copy from any existing PIC32 config
and change the PartName, DeviceID, and ProgramMem. Am I right?


It may or may not work. The programming specification may not be the same (I did not check). But no harm trying.

  USB_Links and libusb
#24
dtran11
Super Member
  • Total Posts : 244
  • Reward points : 0
  • Joined: 2009/10/20 08:33:03
  • Location: 0
  • Status: offline
RE: PICkit2 Devicefile Editor 2010/03/29 08:33:47 (permalink)
0
I will try later tonight and update you guys.

Thanks.
#25
dtran11
Super Member
  • Total Posts : 244
  • Reward points : 0
  • Joined: 2009/10/20 08:33:03
  • Location: 0
  • Status: offline
RE: PICkit2 Devicefile Editor 2010/03/29 16:50:24 (permalink)
0
Where do I get the DeviceID from for the new PIC32's? I tried the device IDs located
in C:\Program Files\Microchip\MPLAB IDE\Device but it doesn't work.
#26
dtran11
Super Member
  • Total Posts : 244
  • Reward points : 0
  • Joined: 2009/10/20 08:33:03
  • Location: 0
  • Status: offline
RE: PICkit2 Devicefile Editor 2010/03/29 18:16:24 (permalink)
0
NVM got it to work. In case anyone is trying to do this. Look in the Device folder mentioned above
and look for your device. Open the .dev file and look for something similar to this line:

devid (region=0xffffffff-0xffffffff idmask=0xff000 id=0x430e053)

At first I thought the id was 0x430e053 but it didn't work. Then I saw the idmask and if you apply that
to the id you will get 0xe000.

I have gotten the PICKit2 to see my pic32mx795 chip. About to load hex soon. will update.
#27
dtran11
Super Member
  • Total Posts : 244
  • Reward points : 0
  • Joined: 2009/10/20 08:33:03
  • Location: 0
  • Status: offline
RE: PICkit2 Devicefile Editor 2010/03/29 18:24:36 (permalink)
0
I have gotten my Hex to load successfully with the PICKit2 standalone app
but my firmware is not running.

Any clues?
#28
xiaofan
Super Member
  • Total Posts : 6247
  • Reward points : 0
  • Joined: 2005/04/14 07:05:25
  • Location: Singapore
  • Status: offline
RE: PICkit2 Devicefile Editor 2010/03/29 18:30:54 (permalink)
0
ORIGINAL: dtran11

I have gotten my Hex to load successfully with the PICKit2 standalone app
but my firmware is not running.

Any clues?


So you have to make sure that your firmware works first. In that case, then you check if your modification of the devicefile is really correct or not. After that, you can say PICKit 2 standalone GUI does not work with your PIC32.

If you have a known-good programmer like ICD 3, then you can use it to verify the content of the flash written by PICkit 2.

BTW, it is better that you export the hex file from MPLAB and then load it from the standalone GUI. Sometimes the compiler generated hex file may miss some configuration settings.

  USB_Links and libusb
#29
dtran11
Super Member
  • Total Posts : 244
  • Reward points : 0
  • Joined: 2009/10/20 08:33:03
  • Location: 0
  • Status: offline
RE: PICkit2 Devicefile Editor 2010/03/29 18:34:02 (permalink)
0
I tried loading the led_message example that comes with the microchip c32 library
and it worked.

When I try to load my own program it doesn't work. I know it is not the code because
I have been successfully loading it with my pickit3.

Maybe it is not able to load more advance programs?

#30
dtran11
Super Member
  • Total Posts : 244
  • Reward points : 0
  • Joined: 2009/10/20 08:33:03
  • Location: 0
  • Status: offline
RE: PICkit2 Devicefile Editor 2010/03/29 18:47:02 (permalink)
0
YES IT WORKSSSS!!!!

I had to remove this config line from my code in order for the
pickit2 to program correctly:

#pragma config DEBUG = ON // Background Debugger Enable

#31
xiaofan
Super Member
  • Total Posts : 6247
  • Reward points : 0
  • Joined: 2005/04/14 07:05:25
  • Location: Singapore
  • Status: offline
RE: PICkit2 Devicefile Editor 2010/03/29 19:35:33 (permalink)
0
That is great! Maybe you want to share your modification. Thanks.

  USB_Links and libusb
#32
dtran11
Super Member
  • Total Posts : 244
  • Reward points : 0
  • Joined: 2009/10/20 08:33:03
  • Location: 0
  • Status: offline
RE: PICkit2 Devicefile Editor 2010/03/29 19:47:28 (permalink)
0
I only have the PIC32MX795 series to test with so I will only post the
settings for that.

First duplicate item PIC32MX460F512L from the parts list then change to these
settings:

PartName: PIC32MX795F512H
DeviceID: 0x0000E000
ProgramMem: 0x00020BFC


Thanks dougy83 for making a wonderful program, and xiaofan for helping out
with my issues.
#33
PKUser
New Member
  • Total Posts : 14
  • Reward points : 0
  • Joined: 2008/05/19 08:38:44
  • Location: 0
  • Status: offline
RE: PICkit2 Devicefile Editor 2010/04/06 17:45:13 (permalink)
0
Doug,

I owe you a pint. The pk2cmd would fail verify on the config word on a 18F83J11. Using your app. I changed the ConfigBlank byte 3 to 0x0FFF (from 0x0000) and all is well.  The 83J11 uses only three bytes of the four and the verify would trip up at

Address  Good     Bad
0x1ffe    0xFFFF 0xF000

Cheers,

Chad Southwell
Photon Kinetics
Beaverton, OR
#34
FunnyNYPD
Super Member
  • Total Posts : 1553
  • Reward points : 0
  • Joined: 2007/09/28 20:06:59
  • Location: USA & Canada
  • Status: offline
RE: PICkit2 Devicefile Editor 2010/04/08 10:59:43 (permalink)
0
Now the PK2 has been expanded not only for more PIC devices, but also to the AVR world. Interesting, isn't it?
http://www.auelectronics.com/forum/index.php/topic,119.msg309.html#msg309

Funny N., Au Group Electronics, www.AuElectronics.com
On-line Store: http://auelectronics.com/products/ Blog: http://augroups.blogspot.com/
Forum: http://auelectronics.com/forum/
#35
DarioG
Allmächtig.
  • Total Posts : 54081
  • Reward points : 0
  • Joined: 2006/02/25 08:58:22
  • Location: Oesterreich
  • Status: offline
RE: PICkit2 Devicefile Editor 2010/04/08 11:12:27 (permalink)
0
nice one indeed Smile

I hope Microchip is happy about it !

GENOVA :D :D ! GODO
#36
FunnyNYPD
Super Member
  • Total Posts : 1553
  • Reward points : 0
  • Joined: 2007/09/28 20:06:59
  • Location: USA & Canada
  • Status: offline
RE: PICkit2 Devicefile Editor 2010/04/08 11:31:14 (permalink)
0
Using the PK2 VPP pin as reset-pin for AVR MCU actually is a good idea. Our engineer just hope they swap the function of pin 5 and 6 to avoid the function limit on pin 6 (ST type Input). Pin 6 will work good as a output, but not so MCU-friendly when it is used as input. Good to know there are still something going on after Microchip's end of life announcement for PK2.
post edited by FunnyNYPD - 2010/04/08 11:32:14

Funny N., Au Group Electronics, www.AuElectronics.com
On-line Store: http://auelectronics.com/products/ Blog: http://augroups.blogspot.com/
Forum: http://auelectronics.com/forum/
#37
Ninestone
Super Member
  • Total Posts : 456
  • Reward points : 0
  • Joined: 2008/02/17 13:41:32
  • Location: 0
  • Status: offline
RE: PICkit2 Devicefile Editor 2010/04/08 15:58:15 (permalink)
0
Now the PK2 has been expanded not only for more PIC devices, but also to the AVR world. Interesting, isn't it?
http://www.auelectronics.com/forum/index.php/topic,119.msg309.html#msg309


I wouldn't bandy that about... it's strictly against the Microchip license for pk2, and therefore illegal...

#38
dougy83
New Member
  • Total Posts : 28
  • Reward points : 0
  • Joined: 2008/06/06 02:06:39
  • Location: 0
  • Status: offline
RE: PICkit2 Devicefile Editor 2010/04/22 08:24:43 (permalink)
0
Thanks for the feedback, it's good to hear that the program actually works ok.

Re the PK2AVRISP being an illegal use of the PK2, how is that the case? I don't remember having to sign a license agreement when I bought my PK2. The only agreement I saw related to modifying or distributing the code (firmware or software) provided by Microchip for use with other micros. PK2AVRISP does neither.
#39
Ninestone
Super Member
  • Total Posts : 456
  • Reward points : 0
  • Joined: 2008/02/17 13:41:32
  • Location: 0
  • Status: offline
RE: PICkit2 Devicefile Editor 2010/04/22 09:15:43 (permalink)
0
Here's the license agreement from the firmware:
* Software License Agreement
 *
 * The software supplied herewith by Microchip Technology Incorporated
 * (the “Company”) for its PICmicro® Microcontroller is intended and
 * supplied to you, the Company’s customer, for use solely and
 * exclusively on Microchip PICmicro Microcontroller products. The
 * software is owned by the Company and/or its supplier, and is
 * protected under applicable copyright laws. All rights are reserved.
 * Any use in violation of the foregoing restrictions may subject the
 * user to criminal sanctions under applicable laws, as well as to
 * civil liability for the breach of the terms and conditions of this
 * license.


Here's the one from the SW 'about' box, which is agreed to when it's installed:
Copyright (c) 2006-2009, Microchip Technology Inc. All rights reserved. 

You may use, copy, modify and distribute the Software for use with Microchip
products only.  If you distribute the Software or its derivatives, the Software
must have this entire copyright and disclaimer notice prominently posted in a
location where end users will see it (e.g., installation program, program
headers, About Box, etc.). 

Same thing in the source for the GUI and pk2cmd SW.

Using the SW-FW API to communicate with the pickit2 would probably count as a derivative of the software, and using the firmware is still applicable to its license.  Somehow I doubt PK2AVRISP was developed without looking at and using from any Microchip supplied source code.  In any case, the firmware is still being used, but not with Microchip products only.
#40
Page: < 12345.. > >> Showing page 2 of 6
Jump to:
© 2019 APG vNext Commercial Version 4.5