That's by accident and not by design! Try touching the reset pin with your fingers or switch on a fluorescent light bulb in the room, it will probably reset, or if you toggle the pin(s) next to reset pin, it might cause a reset due to capacitive coupling (which is quite high on bread boards) Albert
----- Original Message ----- From: "funlw65" <[email protected]> To: "jallib" <[email protected]> Sent: Wednesday, November 11, 2009 10:22 PM Subject: [jallib] Re: Blink a led with a 12f629 Hi Albert, I tried right now on a bread board and is working with and without pull-up resistor on MCLR. Vasi On Nov 11, 9:09pm, "a.faber" <[email protected]> wrote: > Hi Jan Willem, > Can you also describe your schematic, i.e. do you use a de-coupling > capacitor close the the power lines, how about the reset line, do you have > a > pull-up resistor? > Albert > > ----- Original Message ----- > From: "Jan Willem" <[email protected]> > To: "jallib" <[email protected]> > Sent: Wednesday, November 11, 2009 5:45 PM > Subject: [jallib] Re: Blink a led with a 12f629 > > > Hi Rob, > > > I have copy your code (the following) into my Jal Edit and i have > > compile it: > > > ======================================================= > > > include 12f629 -- target PICmicro > > -- > > -- This program uses the internal oscillator at 4MHz > > pragma target clock 4_000_000 -- oscillator frequency > > -- configuration memory settings (fuses) > > pragma target OSC INTOSC_NOCLKOUT -- internal oscillator > > pragma target WDT disabled -- no watchdog > > pragma target MCLR external -- reset externally > > -- > > enable_digital_io() -- disable analog I/O (if any) > > -- > > -- You may want to change the selected pin: > > alias led is pin_A0 > > pin_A0_direction = output > > -- > > forever loop > > led = on > > _usec_delay(250000) > > led = off > > _usec_delay(250000) > > end loop > > > ====================================================== > > > The next .hex file is created: > > > ====================================================== > > :020000040000FA > > :100000000508A200073099008316051083122214F8 > > :100010002208850083120313FB30A000C630A10024 > > :100020000A128A11A10B10280A128A11A00B0E289D > > :10003000000022102208850083120313FB30A00069 > > :10004000C630A1000A128A11A10B22280A128A11B5 > > :08005000A00B20280000062887 > > :02400E00F4318B > > :00000001FF > > ====================================================== > > > When i load this .hex file into my 12F629 chip, pin A0 is not going > > high and low. > > You have tested your code (your .hex file) in your 12F629 chip en > > pinA0 is going high and low OK. > > Can you give me, or can you compare what the different is between your > > and my .hex file? The only reason that your code is working OK at your > > chip and not at my chip, is that your .hex file is not the same as > > my .hex file. > > PinA0 of my chip is OK, because when i load the .hex file of Wouter, > > pinA0 is going high and low. > > > I am very interesting what your .hex file is. > > > Best regards, Jan Willem --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
