On 2 Sep 2008, at 10:03 , Rob Hamerling wrote: > Eur van Andel wrote: > >>>> OPTION_REG_T0CS = off > >> Only for 10F's, but it should go into the device files, and into the >> enable_dig_io() procedure. > > OK! I'll do that > But in the meantime I've done some datasheet scanning and think it is > also useful for the 12F508,509 and 16F505 (maybe even more). Please > check.
Confirmed. Also for PIC12F510, PIC16F506, PIC16F526. Not for the 12F609, 12F615, 12F629, 12F635, 12F636, 12F639 or 12F675. Also not for the PIC16F5X. >>>> pragma MCLR external > >> All that have, should declare MCLR external. Programming an internal >> MCLR PIC depends on a very specific power-up sequence which can >> baffle newbies. This should be in the BLINK files only, for now. > > I assume you are referring to the Vpp-before-Vdd sequence when MCLR is > configured 'internal'. I do. > That applies to only a minority of chips, I > think. 72 have internal MCLR, of the 10F, 12F and 16F: > G5-fiwihex:~/jalv2/jallib/unvalidated/include/device eur$ grep MCLR > *.jal | grep -v 18f | grep -v 18lf | wc > 72 360 2935 But not all require the Vpp-before-Vdd. http://www.electro-tech-online.com/micro-controllers/17354-pic- programmer-winpicprog-my-findings.html#post103132 I don't fully understand this table, but it seems these PICs have the problem: > [edited] > ID6TBL dt 0x00,0x00, "508 ", 0x0000 ;12F508 > dt 0x0F,0x80, "629 ", 0x0000 ;12F629 (*) 8.5-13.5 VPP > dt 0x0F,0xA0, "635 ", 0x0000 ;12F635 10.0-13.0 VPP > dt 0x0F,0xC0, "675 ", 0x0000 ;12F675 (*) 8.5-13.5 VPP > dt 0x04,0x60, "683 ", 0x0000 ;12F683 10.0-13.0 VPP > ; > dt 0x10,0x40, "627A", 0x0000 ;16F627A 10.0-13.5 VPP > dt 0x10,0x60, "628A", 0x0000 ;16F628A 10.0-13.5 VPP > dt 0x10,0xC0, "630 ", 0x0000 ;16F630 8.5-13.5 VPP > dt 0x10,0xA0, "636 ", 0x0000 ;16F636 10.0-13.0 VPP > ; dt 0x10,0xA0, "639 ", 0x0000 ;16F639 10.0-13.0 VPP > dt 0x11,0x00, "648A", 0x0000 ;16F648A 10.0-13.5 VPP > dt 0x10,0xE0, "676 ", 0x0000 ;16F676 8.5-13.5 VPP > dt 0x10,0x80, "684 ", 0x0000 ;16F684 10.0-13.0 VPP > ; dt 0x04,0xA0, "685 ", 0x0000 ;16F685 10.0-13.0 VPP > ; dt 0x13,0x20, "687 ", 0x0000 ;16F687 10.0-13.0 VPP > dt 0x11,0x80, "688 ", 0x0000 ;16F688 10.0-13.0 VPP > ; dt 0x13,0x40, "689 ", 0x0000 ;16F689 10.0-13.0 VPP > ; dt 0x14,0x00, "690 ", 0x0000 ;16F690 10.0-13.0 VPP > > ; dt 0x12,0x00, "785 ", 0x0000 ;16F785 10.0-12.0 > VDD/VPP > ; dt 0x13,0xE0, "913 ", 0x0000 ;16F913 10.0-12.0 > VDD/VPP > ; dt 0x13,0xC0, "914 ", 0x0000 ;16F914 10.0-12.0 VDD/VPP > ; dt 0x13,0xA0, "916 ", 0x0000 ;16F916 10.0-12.0 VDD/VPP > ; dt 0x13,0x80, "917 ", 0x0000 ;16F917 10.0-12.0 > VDD/VPP > But OK, I'll put it in the blink programs, it won't harm. OK. > However I think in the 18Fs the MCLR EXTERNAL has a different meaning. > So it should not appear in the blink programs for the 18Fs. Well, I hope it works. --- ir EE van Andel [EMAIL PROTECTED] http://www.fiwihex.nl Fiwihex B.V. Wierdensestraat 74, NL7604BK Almelo, Netherlands tel+31-546-491106 fax+31-546-491107 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/jallib?hl=en -~----------~----~----~----~------~----~------~--~---
