Yesterday, I have received the pic12f635 samples. So, I have done some testings.
I have applied the "chip definition for the PIC12F635"-patch by Alexander Zangerl, but that patch doesn't seem to work for me. This is what I get: | pts/5 jan ~/picprog.12f635/picprog-1.8.3$ ./picprog --pic /dev/ttyS1 --output /tmp/pic1.hex | Picprog version 1.8.3, Copyright © 2006 Jaakko Hyvätti <[EMAIL PROTECTED]> | Picprog comes with ABSOLUTELY NO WARRANTY; for details | type `picprog --warranty'. This is free software, | and you are welcome to redistribute it under certain conditions; | type `picprog --copying' for details. | | /dev/ttyS1:PIC programmer missing or chip fault | /dev/ttyS1:2006:unable to read pic device id | pts/5 jan ~/picprog.12f635/picprog-1.8.3$ So, autodetecting the chip fails. If I add the -d pic12f635 option I get: | pts/5 jan ~/picprog.12f635/picprog-1.8.3$ ./picprog --pic /dev/ttyS1 -d pic12f635 --output /tmp/pic1.hex | Picprog version 1.8.3, Copyright © 2006 Jaakko Hyvätti <[EMAIL PROTECTED]> | Picprog comes with ABSOLUTELY NO WARRANTY; for details | type `picprog --warranty'. This is free software, | and you are welcome to redistribute it under certain conditions; | type `picprog --copying' for details. | | Device pic12f635, program memory: 1024, data memory: 128. | Reading program memory, | reading data memory, | reading id words, | reading fuses, | done. However, If I remove the pic12f635 from my programmer, it gives the same result (no error like chip is missing). So, I doubt that reading the pic12f635 is really working for me. I have also tested it with piklab-prog <http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=387703>. With piklab-prog, reading the pic seems to be working fine, so I think I have correctly connected the pic12f635 with my programmer ;-) | pts/5 jan ~/picprog.12f635/picprog-1.8.3$ piklab-prog -d 12F635 -p direct -c read /tmp/testpic.hex | Piklab version: 0.12.2 (rev. distribution) | programmer: direct | device: 12F635 | Using port from configuration file. | Connecting Direct Programmer on Serial Port (/dev/ttyS1) with device 12F635... | Set target self powered: false | Connected | Read id: 12F635 (rev. 4) | Reading device memory... | Read memory: Configuration Bits | Read memory: User IDs | Read memory: Calibration | Read memory: Code memory | Read memory: Data EEPROM | Reading done Piklab-prog does give an error¹ when I remove the pic12f635 from my programmer. So, at the moment I have no idea how to solve this problem. But I'll try to take a closer look at this problem the coming days. [¹] (Error: Missing or incorrect device (Read id is 0x3FFF).) -- Met vriendelijke groetjes - Jan Wagemakers - - Debian GNU/Linux 4.0 - Up : 46 days -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
