Package: picprog
Version: 1.8.3-1
Severity: normal
Picprog lacks the chip definition for the PIC12F635,
which is easy to fix:
--- picprog-1.8.3/hexfile.cc 2006-09-25 01:05:41.000000000 +1000
+++ /home/az/hexfile.cc.patched 2007-02-28 12:29:01.000000000 +1000
@@ -224,9 +224,12 @@
{"pic12ce674", 2048, 1, 0, 1, 14, 0, 0, eprom, 16, eeprom, -1},
{"pic12f629", 1024, 1, 0x3000, 1, 14, 0, 0, flash4, 128, eeprom, 0x0f80},
{"pic12f675", 1024, 1, 0x3000, 1, 14, 0, 0, flash4, 128, eeprom, 0x0fc0},
{"pic16c505", 1024, 1, 0, 1, 12, 0, 0, eprom, 0, rom, -1},
+ // 635: has 2 calibration words in 2008 and 2009, no osccal
+ {"pic12f635", 1024, 0, 0x3000, 1, 14, 0, 0, flash4, 128, eeprom, 0x0fa0},
+
+
// 18f original series
// Multi-panel writes
// Write Buffer Size 8
----
However, picprog doesn't properly read the two extra config/calibration
words that the 635 has at 0x2008 and 0x2009: if the config size is
set to three (0x2007 is always a config word on the older PICs),
then picprog dies on reading with
"programmer missing or chip fault
2008:unable to read pic."
Other programs (like pikdev/pkp and the Microchip windows tools) read 2008 and
2009 on the tested chip/programmer combo just fine, therefore I think
that picprog is at fault here.
regards
az
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (980, 'testing'), (970, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.18
Locale: LANG=C, LC_CTYPE=de_AT (charmap=ISO-8859-1)
Versions of packages picprog depends on:
ii libc6 2.3.2.ds1-22sarge5 GNU C Library: Shared libraries an
ii libgcc1 1:3.4.3-13sarge1 GCC support library
ii libstdc++5 1:3.3.5-13 The GNU Standard C++ Library v3
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
