Serin timeout not working properly!

[Bruce]

The 12F635 only has 64 bytes SRAM so if you're using DT ints with a PBP int handler you may need to free up some SRAM, and keep your int handler as simple as possible.

Hard to say without seeing what you're doing.

[Megahertz]

Hi Bruce, it seems we jumped across each others post at the same time. I have succeeded in building the project but a warning is there.

Warning[206] D:\BACKUP.........TXRX.ASM 752 : Found call to macro in column 1. (INT_CREATE)

Should I worry about it? Thanks for all the help.


P.S. Is there any online calculator around which can easily advise me when to expect the interrupt with TMR1 with 1:8 prescaler (4MHz) and also if DT Interrupts work with TMR0 in 12F635?

[Bruce]

Have you tried moving INT_CREATE out of column 1?

Edit: Look for a copy of Mister Es' calculator. Should be a link in a thread around here somewhere.

I don't think the calculator is going to help with what works & doesn't with DT ints, but Darrel already
answered part of your question back in this thread: http://www.picbasic.co.uk/forum/showthread.php?t=12354

[Megahertz]

Have you tried moving INT_CREATE out of column 1?

Column 1 ? What does it mean? Is it putting the ASM code somewhere in the middle of the code? Sorry for my ignorance on this topic.

[Bruce]

INT_CREATE in Column 1

ASM
INT_LIST  macro ; IntSource,     Label,    Type, ResetFlag?
    INT_Handler    RX_INT,  _DoIntStuff,   PBP,  yes
    endm
INT_CREATE               ; Creates the interrupt processor

    INT_ENABLE   RX_INT     ; enable external UART RX interrupts  
ENDASM

INT_CREATE not in Column 1

ASM
INT_LIST  macro ; IntSource,     Label,    Type, ResetFlag?
    INT_Handler    RX_INT,  _DoIntStuff,   PBP,  yes
    endm
    INT_CREATE               ; Creates the interrupt processor

    INT_ENABLE   RX_INT     ; enable external UART RX interrupts  
ENDASM

[Megahertz]

Thank you Bruce. I learned something today that what a single press on the tab key can do for your code.

You are truly a master.
Thanks again.

[Archangel]

Column 1 ? What does it mean? Is it putting the ASM code somewhere in the middle of the code? Sorry for my ignorance on this topic.

Column 1: leftmost column of each line. Asm is picky about where you put things, just start the line with several spaces.

[Megahertz]

Hi, I am back again with a problem. This time it looks like the interrupt is serviced but only once and code does not move forward. Can you please have a look at my code and advise me if I am doing it right ?

Define          OSC     4      ' OSCCON defaults to 4MHz on reset

INCLUDE "DT_INTS-14.bas"     ; Base Interrupt System
INCLUDE "ReEnterPBP.bas"     ; Include if using PBP interrupts
Include "modedefs.bas"

@ __CONFIG _INTRC_OSC_NOCLKOUT & _WDT_ON & _PWRTE_ON & _MCLRE_OFF & _CP_ON & _BOD_ON & _CPD_ON & _IESO_OFF & _FCMEN_ON & _WUREN_OFF

' Pin Definations are here
ToTx  	             var     GPIO.2     
ToRx		var	GPIO.3
Monitor		var  	GPIO.4
T1CON=49
main:
        ' Initialize the processor
        TRISIO = %011000        
        CMCON0 = 7              
        GPIO=0			       
        OPTION_REG = %00000111  
        WDA.4=1  : WPUDA.4=1
ASM
INT_LIST  macro    ; IntSource,    Label,  Type, ResetFlag?
       INT_Handler    TMR1_INT,  _Setval,   PBP,  yes
   endm
	INT_CREATE               ; Creates the interrupt processor
ENDASM

start0:
gpio.0=1 ' LED1

start:
		gpio.1=1 ' LED 2
@   INT_ENABLE   TMR1_INT
		Serin ToRx, N2400,["pp3"],code
@   INT_DISABLE   TMR1_INT
                           if code=0 then goto start0
                           ' ELSE CHECK OTHER VALUES FOR THE RECEIVED CODE
goto start0

Setval:
     code=0
	gpio.0=0 : pause 200
@ INT_RETURN

When power is applied this is what happens:
1) Both LED1 & LED2 glow
2) LED 1 (gpio.0) goes off
and system stays like this though LED should turn ON after 200mS. Please help me know what am I doing wrong?

[Bruce]

Sounds like it's working exactly like it should be.

1. TMR1 interrupts while it's sitting in your SERIN routine waiting for 3 ASCII characters
followed by the byte that gets placed in code (which by the way hasn't been declared).

2. Once the interrupt service routine executes, it returns right back to your SERIN
routine with the LED off.

Insert a toggle command in your int handler for a quick visual indication of the int handler
executing. That would tell you it's working or not.

And -as-is, it's never going to execute any code below your SERIN routine unless all 3 ASCII
characters + the byte that goes into your undeclared code VAR are received.