DEFINE OSC 8 will do but also alter everything based on timing such as HSEROUT/HSERIN/PAUSE etc etc.
OSC is always defined anyways, even if you don't type the DEFINE OSC line. If you don't type...
Type: Posts; User: mister_e; Keyword(s):
DEFINE OSC 8 will do but also alter everything based on timing such as HSEROUT/HSERIN/PAUSE etc etc.
OSC is always defined anyways, even if you don't type the DEFINE OSC line. If you don't type...
Not sure if this have been covered, but however. I'm actually working with a PIC16F616, there's no interrupt on PORTB change on this one, but Interrupt on PORTA change, great Microchip ;)
From...
But yeah... we know how Microchip work... hard to tell if it will always work... on all PIC :D
Worth a try!
.Damn.. way to slow this time :D
my solution was..
asm
RXBnIF=RXB1IF
TXBnIF=TXB2IF
FIFOWMIF=RXB0IF
you can use
@ INT_ENABLE RX_INT
and
@ INT_DISABLE RX_INT
look post 296... if i was right, your PIC will wait 'till the next time it receive ^SMGL: when the timeout is not used.
LMAO! well this avatar is really me... if you feel concern... i'm sorry :D
I see some other potential problem in the above anyways.
From one of his previous post he says that
^SMGL: 1,"REC...
As you're using HSERIN/HSEROUT, shouldn't RX_INT be PBP type instead?
Don't forget to add ReEnterPBP.bas in your INCLUDE list.
NO.. ;) at least give more details... error message, code etc etc
Make sure you're using MPASM to compile :o
If you set it to YES, you don't need to clear the interrupt flags manually, DT's INT will do it for you.
If you set it to NO, the program won't reset the interrupt flag, so you'll have to do it...
And all this with a minimum of efforts ;)
TX or RX? Not sure why you want to monitor TX event so far, RX would be more valuable.
Nah, it's not a dumb question. Knowing what happened last week, it's probably normal than few things are missing on his website.
I've attach ALL files.
and one suggestion, add
@ errorlevel -306
as MPLAB output list a $%$%^ load of those annoying...
The problem is due to your LCD DEFINES
' LCD Display
' -----------
DEFINE LCD4X20
DEFINE LCD_DREG PortD ' Set LCD Data to PortD
DEFINE LCD_DBIT ...
is this happen to ANY PBP program or just when using DT-INT.
I don't know why it shouldn't. can you at least post some code OR the errors message + PIC#
Maybe on POST 116 which is few time after the Green splat thingy ;)
http://www.picbasic.co.uk/forum/showpost.php?p=25297&postcount=116
somehow strange but you could still try to uncheck the Case Sensitive option in MCS.
<table><td>http://www.mister-e.org/Pics/Angry_barbarian</td><td>It really drives me nuts when it work here but not elsewhere. Ok then just copy/paste your code here and place it between code...
It happen because you probably have selected INH8XS file format under the MPASM check box. use INHX8M instead.
Yes indeed, CTRL + PrintScr, then you paste it in Paint or whatever else to edit...
did you get...
<img SRC="http://www.picbasic.co.uk/forum/attachment.php?attachmentid=1438&stc=1&d=1172848778">
If so, make sure you have selected MPASM in the View>> Compile And Program option...
mmm, weird, no problem here. so we talk about
http://darreltaylor.com/DT_INTS-14/combine.html
If so, did you add something special in the code or you're using EXACTLY the following...
LED1 ...
2.46 or higher (2.47 here)
MPASM... just download the latest version of MPLAB 7.51 (maybe 7.52 now).
Yup! seems mine is different... looking on another forum thread (12 Bytes code one ;) ) i know we don't have the same MPLAB version... 7.50 Here, MPASM 5.06
Here's a .inc file quote]
...
http://www.mister-e.org/Pics/HatsOff.gif
Yup it's working really well indeed. Interesting how it could be handled as ASM... Being said, it open a wide range of USB testpoints as well.
Oh......