tks Dave
i do not have 15k-40k resistor,however, i disable mclr in the conf: mclre_off_3h
but nothing happens, i check the resistors tomorrow,
tks Dave
i do not have 15k-40k resistor,however, i disable mclr in the conf: mclre_off_3h
but nothing happens, i check the resistors tomorrow,
Your code has some issues
I can't verify your config settings as I no longer use that ancient old complier [you could at least update to 2.6c]Code:INCLUDE "h:\AllDigital.pbp" why ? ASM __CONFIG _CONFIG1H, _FOSC_INTIO67_1H & _FCMEN_OFF_1H & _IESO_OFF_1H __CONFIG _CONFIG2H, _WDTEN_ON_2H & _WDTPS_512_2H __CONFIG _CONFIG3H, _CCP2MX_PORTC_3H & _PBADEN_OFF_3H & _LPT1OSC_OFF_3H & _HFOFST_ON_3H & _MCLRE_ON_3H __CONFIG _CONFIG4L, _STVREN_ON_4L & _LVP_OFF_4L & _XINST_OFF_4L ENDASM OSCCON = $70 '$70 Internal oscillator is set to 16MHz $62 ' 8mhz--- '; Primary Clock is selected as system clock. OSCTUNE = $40 'HFINTOSC selected; PLL enabled; Factory calibrated frequency define OSC 64 ADCON0 = 0 why ? CM1CON0.7 = 0 why ? CM2CON0.7 = 0 why ? portb = 0 why ? latb = 0 why ? trisb = 0 is this really what you want ? '------------------------------------------ i var byte m var byte main_program: gosub blink 'call suroutin to blink a led GOTO main_program '============================================== blink: high portb '= $ff ' light the led for acertain amount of time this is not a legitimate use of HIGH for i = 0 to 100 'loop to maintain the led on FOR M = 0 TO 10 pause 1 NEXT NEXT low portb '= 0 'tuen off the led for certain amount of time this is not a legitimate use of LOW for i = 0 to 50 'loop to maintain the led off FOR M = 0 TO 10 pause 1 NEXT NEXT return '------------------------------------------- end
assuming your config and osc settings are workable then this code is tested an works for me ,
1k r in series with led, vdd 5v 4.7k pullup on mclr
Code:ASM __CONFIG _CONFIG1H, _FOSC_INTIO67_1H & _FCMEN_OFF_1H & _IESO_OFF_1H __CONFIG _CONFIG2H, _WDTEN_ON_2H & _WDTPS_512_2H __CONFIG _CONFIG3H, _CCP2MX_PORTC_3H & _PBADEN_OFF_3H & _LPT1OSC_OFF_3H & _HFOFST_ON_3H & _MCLRE_ON_3H __CONFIG _CONFIG4L, _STVREN_ON_4L & _LVP_OFF_4L & _XINST_OFF_4L ENDASM OSCCON = $70 '$70 Internal oscillator is set to 16MHz $62 ' 8mhz--- '; Primary Clock is selected as system clock. OSCTUNE = $40 'HFINTOSC selected; PLL enabled; Factory calibrated frequency define OSC 64 ANSELH = 0 trisb=%11111110 pause 2000 '------------------------------------------ i var byte m var byte main_program: gosub blink 'call subroutine to blink a led GOTO main_program '============================================== blink: LATB.0=1 ; light the led on portb.0 for a certain amount of time for i = 0 to 100 'loop to maintain the led on FOR M = 0 TO 10 pause 1 NEXT NEXT LATB.0=0 'turn off the led for certain amount of time for i = 0 to 50 'loop to maintain the led off FOR M = 0 TO 10 pause 1 NEXT NEXT return '------------------------------------------- end
Warning I'm not a teacher
HELLO rICHARD,
Thk for ur reply,
the code displayed there is for timer, interrupt, and digital conversion.
that run well for several years.
your code is also not run at all on my breadboard.
the ANSELH is not used in my code due to the fact the PBADEN_OFF_3H is off.
about the version of the pbp, it is not relevant to the fail i think so.
1 think i pay attention to is the effect of charge accumulated on the breadboard (run @64mhz). but the pcb no charge on it..
i replayed another small breadboard , but the situation has not been better.
Suspect your breadboard if it is older than 1 year, the sockets corrode and become insulators.
define OSC 64 ' does NOT make the pic oscillate at 64 mhz, it simply adjusts PBP's timing to accomodate that speed, so if you are running at say 4mhz then whatever you expect to happen in 1 second will take 4/64 or 16 seconds to happen. I think your config will not allow 64mhz as you need PLL FOSC = HSPLL HS oscillator, PLL enabled (Clock Frequency = 4 x FOSC1)
Last edited by Archangel; - 10th December 2016 at 07:03.
If you do not believe in MAGIC, Consider how currency has value simply by printing it, and is then traded for real assets.
.
Gold is the money of kings, silver is the money of gentlemen, barter is the money of peasants - but debt is the money of slaves
.
There simply is no "Happy Spam" If you do it you will disappear from this forum.
HELLO,
Tks for ur idea,
it is true that the breadboard is older than 1 year. but the
however, the same breadboard connection and pcb ( i design it and product it) the pic that was programmed a month before is ran perfectly now
but the same program is burned into the chip NOT RUN AT ALL now ON BOTH BREADBOARD AND PCB
about the osc @64mhz and 4mhz, r really different:
let's say
PAUSE 500 @64MHS OSC : the led blinks faster than
PAUSE 500 @4MHZ (by inspection)
i really do not know the pic runs @64mhz or not. but at this speed, it can handle 6-8 p10 led modules (in my case)
i include a short video that is on the market for several years that i had sold,
i try to upload but fail.
i will reload later
HELLO,
HERE IS THE LINK:
last night i though when the breadboard becomes isolation (due to plug and unplug the chip may times)
so the zip socket on the programmer gets the same situation?
but the programmed chip (last month) runs well right now on the on both pcb and breadboard-
i can eliminate all off the situation then conclude that the programmer fails- but i check the code from the chip is ok (like the code compiled)
now i m like "a dog runs after its queue".
hello every body
finally the program runs as posted on the first post- nothing change- and just go back to another computer (complete format the system...) and run win xp- pbp version 5
tks for all
Bookmarks