2012-11-02, 18:54:50
(This post was last modified: 2012-12-22, 00:51:02 by Mikael Gustavsson.)
Hi,
I have been looking at the ds30 loader GUI and I think I have found a bug, or at least I don't understand whats happening.
I am using a 12F1840 part and the bootloader is identified and works however, the bootloader start address in debug mode and the graphical representation appears to be wrong.
Using the default bootloader placement (BLPLW) of 256, after the device has been programmed I pull the flash from the device and the bootloader starts at F00. But the debug mode in the GUI with custom bootloader unticked says start address of 0xF40.
Also toggling the custom bootloader selection on and off with a placement of 6 pages from end, it doesn't show a change in the graphical representation, however F00 (the default) is 8 pages from the end.
The only reason I spotted this was I reduced the placement to 192, to make use of a little more space. And was having trouble finding the right settings for the loader gui. Does anyone else see this?
Cheers,
Wip
I have been looking at the ds30 loader GUI and I think I have found a bug, or at least I don't understand whats happening.
I am using a 12F1840 part and the bootloader is identified and works however, the bootloader start address in debug mode and the graphical representation appears to be wrong.
Using the default bootloader placement (BLPLW) of 256, after the device has been programmed I pull the flash from the device and the bootloader starts at F00. But the debug mode in the GUI with custom bootloader unticked says start address of 0xF40.
Also toggling the custom bootloader selection on and off with a placement of 6 pages from end, it doesn't show a change in the graphical representation, however F00 (the default) is 8 pages from the end.
The only reason I spotted this was I reduced the placement to 192, to make use of a little more space. And was having trouble finding the right settings for the loader gui. Does anyone else see this?
Cheers,
Wip