On Thu, 22 Jan 2004 14:27:00 -0500, you wrote: >A lot of experience has taught me to not trust anyone or thing that I = don't >have to. If the space is available, the change in boot time will not be >noticable and you will never know what trouble you missed... > >John Ferrell >6241 Phillippi Rd >Julian NC 27283 >Phone: (336)685-9606 >johnferrell@earthlink.net >http://DixieNC.US >NSRCA 479 AMA 4190 W8CCW >"My Competition is Not My Enemy" > >----- Original Message ----- >From: "Michael Rigby-Jones" >To: >Sent: Thursday, January 22, 2004 9:41 AM >Subject: Re: [PIC:] pin function defaults... > > >> >-----Original Message----- >> >From: John Ferrell [mailto:johnferrell@EARTHLINK.NET] >> >Sent: 22 January 2004 14:23 >> >To: PICLIST@MITVMA.MIT.EDU >> >Subject: Re: [PIC:] pin function defaults... >> > >> > >> >It does take code space but the only safe way is to initialize >> >everthing present as step one in your startup code. John >> >> Are you saying that Microchips default register values at reset are >> unreliable? I've not had a problem initialising only the functions I = use >> and leaving the rest. The brownout detect or watchdog timer should = reset >> everything to the state shown in the datasheets (apart from RCON >obviously). There is no inherent problem, but there are things that can come back to = bite you, like when you do 'goto start' and expect this to be the same as a reset... (In this particular case, allowing the WDT to time out is a safer option = as it forces a real reset). =20 -- http://www.piclist.com hint: PICList Posts must start with ONE topic: [PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads