Hello,
i have a working code which uses
CMP_INT and TMR1_INT.
I want when TMR1_INT event triggered ,
to change the period (or Frequency as entered) and reload the TMR1 with a new value.
Is...
Type: Posts; User: LakisFM1; Keyword(s):
Hello,
i have a working code which uses
CMP_INT and TMR1_INT.
I want when TMR1_INT event triggered ,
to change the period (or Frequency as entered) and reload the TMR1 with a new value.
Is...
Thank you guys!
Very clear response...
This is simple Led-blink code that does not work.
LED5 flashes normally, and LED 4 stable HIGH.................
Using a 12F1822 (RA4 is not open collector in this PIC).
OK !
It is not so difficult to read.
Thanks again!
Lakis from Thessaloniki.
Ioannis , geia !
Is it possible to post the modified optimized code for the 16F1827?
Thank you.
Lakis.
springtank's solution worked for me totally fine on pbp 2.6 (Thanks one more time!)
A compiled .hex file of 1822 , also worked 'as is' on the 1840!
I used many registers in my program (can't...
Thank you!
I thought the differences in the .inc were also about the registers ,
so i had to verify that aaaaaall the registers of the 12F1840 are in same addresses as the 16F1828. :numbness:
...
Would it be too much if i ask you to attach the modified .inc file ?
Thank You in any case !
I must note i used a 12F1822 @32 MHz and the I2Cbus was running at slow speed !. I don't think the code is fast enough for a 400KHz bus! :(
ASM
__CONFIG _CONFIG1, _FOSC_INTOSC & _WDTE_ON & _PWRTE_ON & _MCLRE_OFF & _CP_OFF & _CPD_OFF & _BOREN_OFF & _CLKOUTEN_OFF & _IESO_OFF & _FCMEN_OFF
__CONFIG _CONFIG2, _WRT_OFF & _PLLEN_ON &...
Hello , did you finally managed to play with the 12F1840 ?
I mean you used 12F1822 Hex ?
But i think Microcode Studio wouldn't give error (and quit) when try to write more than 2048 words ?
...
I am happy to say that the bit-banging I2C monitor is done.
It is written all in PBP , and uses interrupts for the input-bit sensing using a...12F1822 at... 32MHz of course.
Tommorow i will...
While speed-optimizing an IRQ Bit-bang routine i am working on now , i though it would be useful to use the EUSART Synchronous Slave Reception mode (asuming using the 2 EUSART pins of course).
Eg.
...
Many many Thank you for the replies.
I thought that reading the Addresses and Data but instead of ACK , i would always use byte NACKing (though it was invisible on the bus)
as it is referred in...
Building an I2C monitor with a 12F1822 and i want to monitor at least 4 addresses.
I use SSP1MSK = 000001 for that , and then i filter the 4 addresses from the SSP1BUFF.
But i think that I2C...
Problem solved!
I had to use
ASM
__CONFIG _CONFIG1, _FOSC_INTOSC & _WDTE_OFF & _PWRTE_ON & _MCLRE_OFF & _CP_OFF & _CPD_OFF & _BOREN_OFF & _CLKOUTEN_OFF & _IESO_OFF & _FCMEN_OFF
...
Overwriting previous address contents (8007) :(
Nop ,
these configs are for the MPASM assembler - which i use ,
since PM (of the PBP 2.60c i use) does not support the 12F1822.
ps. just saw you're from Thessaloniki too :)
so , Kalo...
Oh , it's been 7 years and this thread is still hot!
Here is my configuration problem using PIC12F1822.
As long as i red the manuals i guess the correct is
@ __CONFIG1 _FOSC_INTOSC & _<blah...
Thanks for the interest but all these are for MPASM.... i am not sure if i can handle MPASM.... if until tommorow morning have no reply i will try using MPASM.
unfortunately as i said i don't use MPASM ....
(PBP 2.60C)
@ DEVICE PIC16F88, INTRC_OSC_NOCLKOUT
@ DEVICE PIC16F88, WRT_OFF
@ DEVICE PIC16F88, DEBUG_OFF
@ DEVICE PIC16F88, CCPMX_OFF
@ DEVICE PIC16F88, MCLR_OFF
@ DEVICE PIC16F88, PROTECT_OFF
@ DEVICE...
:angel: T H A N K S !!!! ..... THAT WAS IT! :angel:
(and solved all the problems ... including the strange behaviour of GPIO.0....)
Hello to all,
i am having a headache using CALL in 12F510...see that...
The PIC gets a continuous CLK in pins GPIO.3 and .4
(This is only a testing part of the full program , in order to...
with a small 40pin ICsocket > 6pin breadboard...
I retried second time to use 2.55 still not working, so back to 2.40 for sure.
I suspect is a bug of the Firmware 2.32.00 used both in 2.61 and...