| Author |
 Topic  |
|
|
motc
USA
2 Posts |
 Posted - 05/08/2026 : 20:10:06
|
I have a HEX file that is used to program a PIC18F2420. When read in by USBPrg 6.39 the fields in the Configuration tab are populated correctly, as the configuration information is in the HEX file. When the same file is read into USBPrg 7.40, the fields in the Configuration tab don't change at all. Furthermore, the method to change the fields in 7.40 appears to be faulty or have shortcomings, since it can't replicate the exact values I get automatically in 6.39 by forcibly choosing items from the combo boxes because I can't directly enter the corresponding hex values. Why this regression? Is there a way to bring in the values that were in the input file all along without having to enter them manually? My programmer is a GQ-4X V4 and I have USBPrg 7.40. A colleague has a GQ-3X and runs USBPrg 6.39. He is able to program the PIC18F2420 without any issues and I cannot, despite having a newer device with more recent software.
|
|
| Reply #1
anniel
2629 Posts |
Posted - 05/09/2026 : 05:15:25
|
quote:
Originally posted by motc
I have a HEX file that is used to program a PIC18F2420. When read in by USBPrg 6.39 the fields in the Configuration tab are populated correctly, as the configuration information is in the HEX file. When the same file is read into USBPrg 7.40, the fields in the Configuration tab don't change at all. Furthermore, the method to change the fields in 7.40 appears to be faulty or have shortcomings, since it can't replicate the exact values I get automatically in 6.39 by forcibly choosing items from the combo boxes because I can't directly enter the corresponding hex values. Why this regression? Is there a way to bring in the values that were in the input file all along without having to enter them manually? My programmer is a GQ-4X V4 and I have USBPrg 7.40. A colleague has a GQ-3X and runs USBPrg 6.39. He is able to program the PIC18F2420 without any issues and I cannot, despite having a newer device with more recent software.
Ask your colleague for the PIC18F2420 device line he is using and add it to your customdevices.txt or devices.txt. |
 |
|
| Reply #2
motc
USA
2 Posts |
Posted - 05/09/2026 : 06:28:15
|
Thanks for your advice. I'm not sure why an earlier version of the software would have an improved entry in the devices.txt file or how it would make the software work more comprehensively. Here are mine for version 7.40.
$ grep PIC18F2420 *.txt
devices.txt:Name="PIC18F2420*DIP28",ID="XXXX",Class="PIC18F2XXX_4XXX",Category="MCU",MFG="Microchip",Package="DIP28",PINVCC="ZIF32_PIN28";
devices.txt:Name="PIC18F2420*ICSP",ID="XXXX",Class="PIC18F2XXX_4XXX",Category="MCU",MFG="Microchip",Package="DIP40",ChipMode="ICSP",Adapter="ICSP/PIC adapter+";
supportedList.txt:PIC18F2420*DIP28,,
supportedList.txt:PIC18F2420*ICSP(Adadper:ICSP/PIC adapter+),,
|
|
|
| |
Topic |
|
|
|
PIC18F2420 Configuration Bits Not Read In
