From: Neil D. <ne...@da...> - 2020-03-12 10:43:34
|
Hi, I am using usbpicprog from the Ubuntu PPA at version 1.0.5-4 amd64. The device I am working with, a PIC18LF26K22, produces the following assertion when the device is selected. pictype.h(433): assert "acc <= nbits" failed in GetBitSize(). Selecting a PIC18F26K22 (the 5V powered part) does not generate this assertion. The assertion dialog presents the options to Stop or Continue so is this assertion non-fatal and am I OK to continue using the program? Regards,Neil Darlow -- Sent with Evolution Mail on Linux Mint 19.3 Tricia. |
From: Neil D. <ne...@da...> - 2020-03-12 10:43:36
|
Hi, I am using usbpicprog from the Ubuntu PPA at version 1.0.5-4 amd64. The device I am working with, a PIC18LF26K22, produces the following assertion when the device is selected. pictype.h(433): assert "acc <= nbits" failed in GetBitSize(). Selecting a PIC18F26K22 (the 5V powered part) does not generate this assertion. The assertion dialog presents the options to Stop or Continue so is this assertion non-fatal and am I OK to continue using the program? Regards, Neil Darlow -- Sent with Evolution Mail on Linux Mint 19.3 Tricia. |
From: Frans S. <fra...@gm...> - 2020-03-12 10:53:32
|
Dear Neil Darlow, It has been a long term since I worked on usbpicprog. I guess there is a problem in the xml file for the PIC18LF26K22 or it's interpretation. I will certainly not harm to continue using the application, however I can't guarantee that the programming of this device will be 100% successful. Regards, Frans On 3/12/20 11:17 AM, Neil Darlow via Usbpicprog-technical wrote: > Hi, > > I am using usbpicprog from the Ubuntu PPA at version 1.0.5-4 amd64. > > The device I am working with, a PIC18LF26K22, produces the following > assertion when the device is selected. > > > pictype.h(433): assert "acc <= nbits" failed in GetBitSize(). > > > Selecting a PIC18F26K22 (the 5V powered part) does not generate this > assertion. > > The assertion dialog presents the options to Stop or Continue so is > this assertion non-fatal and am I OK to continue using the program? > > Regards, > Neil Darlow > > -- > Sent with Evolution Mail on Linux Mint 19.3 Tricia. > > > _______________________________________________ > Usbpicprog-technical mailing list > Usb...@li... > https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical |
From: Neil D. <ne...@da...> - 2020-03-12 17:16:04
|
Hi Frans, I browsed the source code and determined, as you did, that it was a problem with the XML file. I reconciled the XML file with the PIC18LF26K22 Data Sheet and found a number of errors and omissions (things like EEPROM size, missing protection block settings etc.). I've managed to create a working XML file that should suit my needs. Given the diversity of the PIC ecosystem, if you ever decide to revisit the project, it would be an idea to create the XML files from Microchip header files using an automated mechanism. Regards,Neil Darlow On Thu, 2020-03-12 at 11:53 +0100, Frans Schreuder wrote: > Dear Neil Darlow, > > It has been a long term since I worked on usbpicprog. I guess > there is a problem in the xml file for the PIC18LF26K22 or it's > interpretation. > > I will certainly not harm to continue using the application, > however I can't guarantee that the programming of this device > will > be 100% successful. > > Regards, > > Frans > > > > On 3/12/20 11:17 AM, Neil Darlow via > Usbpicprog-technical wrote: > > > > > > > > Hi, > > > > > > > > I am using usbpicprog from the Ubuntu PPA at version 1.0.5-4 > > amd64. > > > > > > > > The device I am working with, a PIC18LF26K22, produces the > > following assertion when the device is selected. > > > > > > > > > > > > > > pictype.h(433): assert "acc <= nbits" failed in > > GetBitSize(). > > > > > > > > > > > > > > Selecting a PIC18F26K22 (the 5V powered part) does not > > generate this assertion. > > > > > > > > The assertion dialog presents the options to Stop or Continue > > so is this assertion non-fatal and am I OK to continue > > using the > > program? > > > > > > > > Regards, > > Neil Darlow > > > > > > > > > > -- > > > > Sent with Evolution Mail on Linux > > Mint 19.3 Tricia. > > > > > > > > > > > > > > > > > > > > > > _______________________________________________Usbpicprog- > > technical mailing lis...@li... > > https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical > > > > > > > > _______________________________________________Usbpicprog-technical > mailing lis...@li... > https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical -- Sent with Evolution Mail on Linux Mint 19.3 Tricia. |
From: Frans S. <fra...@gm...> - 2020-03-12 17:41:57
|
Dear Neil, Thanks for the message. Could you fork the github project and commit the changed xml file, then I can merge it back to the official repo. If that is too much work you can also send me the xml so I can commit the changes. Regards, Frans Op do 12 mrt. 2020 18:16 schreef Neil Darlow via Usbpicprog-technical < usb...@li...>: > Hi Frans, > > I browsed the source code and determined, as you did, that it was a > problem with the XML file. > > I reconciled the XML file with the PIC18LF26K22 Data Sheet and found a > number of errors and omissions (things like EEPROM size, missing protection > block settings etc.). > > I've managed to create a working XML file that should suit my needs. Given > the diversity of the PIC ecosystem, if you ever decide to revisit the > project, it would be an idea to create the XML files from Microchip header > files using an automated mechanism. > > Regards, > Neil Darlow > > On Thu, 2020-03-12 at 11:53 +0100, Frans Schreuder wrote: > > Dear Neil Darlow, > > It has been a long term since I worked on usbpicprog. I guess there is a > problem in the xml file for the PIC18LF26K22 or it's interpretation. > > I will certainly not harm to continue using the application, however I > can't guarantee that the programming of this device will be 100% successful. > > Regards, > > Frans > On 3/12/20 11:17 AM, Neil Darlow via Usbpicprog-technical wrote: > > Hi, > > I am using usbpicprog from the Ubuntu PPA at version 1.0.5-4 amd64. > > The device I am working with, a PIC18LF26K22, produces the following > assertion when the device is selected. > > > pictype.h(433): assert "acc <= nbits" failed in GetBitSize(). > > > Selecting a PIC18F26K22 (the 5V powered part) does not generate this > assertion. > > The assertion dialog presents the options to Stop or Continue so is this > assertion non-fatal and am I OK to continue using the program? > > Regards, > Neil Darlow > > -- > > > Sent with Evolution Mail on Linux Mint 19.3 Tricia. > > > > _______________________________________________ > > Usbpicprog-technical mailing list > > Usb...@li... > > https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical > > > _______________________________________________ > > Usbpicprog-technical mailing list > > Usb...@li... > > https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical > > > -- > > Sent with Evolution Mail on Linux Mint 19.3 Tricia. > _______________________________________________ > Usbpicprog-technical mailing list > Usb...@li... > https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical > |