Search Results - MEL PICBASIC Forum


Search:

Type: Posts; User: louislouis; Keyword(s):

Search: Search took 0.00 seconds.

  1. Re: Using as many internal peripherals as possible.

    Thank you, Richard, for the explanation.
    Now I have a clearer understanding of how to work with variables and share them in ASM and PBP.

    Active TMR1, yes. I just forgot to comment on this line....
  2. Re: Using as many internal peripherals as possible.

    What I trying. Omit PBP code from ASM interrupt routine.
    But this try not work, of course.
    Where is the problem?


    #CONFIG
    __config _CONFIG1, _FOSC_INTOSC & _WDTE_OFF & _PWRTE_ON &...
  3. Re: Using as many internal peripherals as possible.

    Thanks Richard for the answer. I understand. In more complex cases, this could cause problems.
    In my case, it works, but it is not correct to combine it like this.
    So in PBP use only On Interrupt...
  4. Re: Using as many internal peripherals as possible.

    In my minimalist mania, I tried using interrupts. On pin RA3 hooked up 10k pullup and pushbutton to ground. On pin RA5 LED. First I tried the On Interrupt statement from PBP not work at all. Then I...
  5. Re: Using as many internal peripherals as possible.

    I tested your codes, both works. The second example with TMR1 I like the most because maintain 4MHz clock. And yes, it compiles only 34 words. Just one more word than mine when I manipulate the clock...
  6. Re: Using as many internal peripherals as possible.

    Even better, only 33 words.



    #CONFIG
    __config _CONFIG1, _FOSC_INTOSC & _WDTE_OFF & _PWRTE_ON & _MCLRE_OFF & _CP_OFF & _CPD_OFF & _BOREN_ON & _CLKOUTEN_OFF & _IESO_ON & _FCMEN_ON
    __config...
  7. Using as many internal peripherals as possible.

    Hi,

    I wonder how small the code can it be if I use as many internal peripherals as I could (and I know).
    The task is simple, alternately slowly flash LEDs on ports RA0 and RA1. If the supply ...
Results 1 to 7 of 7