Hi Diego, > I compiled your code with this command: > sdcc -mpic14 -p16f88 main.c > I tested in proteus simulator and it works too. I measured times > and it > should be:Led on for about 165msLed off for abour 165ms
So the code is good and my analogic should show something like 2.5v ... but it stay at 0. > Have you checked that pic is flashed right? I mean reading PIC > code memory and comparing with your hex. Yes, in both Piklab and ic-prog and even with ic-prog after flashing using Piklab. I think my powersupply is too noisy and the xtal doesn't stabilize ... so the PIC doesn't start. I'll try this evening with a dead PC supply and with a capacity close to the PIC ... and I will cross my finder. It is right to keep MCTRL flying ? I mean I'll use it in future as normal input so, as per my config, PIC reset is disabled so flying input may not disturb isn't it ? Bye Laurent --- The misspelling master is on the Web. _________ 100 % Dictionnary Free ! / /( / Dico / / Pleins d'autres fautes sur /________/ / (#######( / http://destroyedlolo.info Quoi, des fautes d'orthographe! Pas possible ;-D. ------------------------------------------------------------------------------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev _______________________________________________ Sdcc-user mailing list Sdcc-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sdcc-user
