Addressing multiple PORTs using one Variable

[richard]

By changing pinsel var you can select different portc pins
if you need the remaining portc pins then more code is needed

' PIC 16F690 @20MHz#CONFIG
    __config _FCMEN_OFF &_IESO_OFF &_CPD_OFF &_WDT_OFF &_HS_OSC &_BOR_OFF &_CP_OFF &_PWRTE_OFF &_MCLRE_OFF
#ENDCONFIG


TRISC = %00000000


DEFINE OSC 20




pinsel  var byte 
pinsel   = 128 ;  64 FOR RC:6    32 FOR RC:5 ETC 




MAIN:


    PORTC        = PORTC  | pinsel


        ASM
            nop
            nop
            nop
        ENDASM
    PORTC = 0         ' have this syntax for tests only here
        ASM
            nop
        ENDASM
        
    GOTO MAIN
END

[richard]

have you tried to light a rgb led strip with a 690 @20mHz yet ?
i have doubts that such a slow chip will do the deed

[Ioannis]

have you tried to light a rgb led strip with a 690 @20mHz yet ?
i have doubts that such a slow chip will do the deed

That's why I proposed APA102 chips. Not strict on the clock frequency.

Ioannis

[flotulopex]

have you tried to light a rgb led strip with a 690 @20mHz yet ?

Check this:

[flotulopex]

And here's the project's code for now.

[Ioannis]

Have not checked al of your code, but in the ***_B routine you include many time the same code. Why not insert it one time and then use GoSub to it? Better efficiency and memory usage.

Also I see you insist on using this difficult protocol. Consider the APA101 as it is less strict and can be used on slow MCUs

Ioannis

[flotulopex]

I tried to not repeat the code and use GOTOs or GOSUBS but then, if I do so, the NeoPixel string won't work anymore.

Would the use of an alternative LED string as you mention sove the problem of the ports/code/timing?

I can change for another system but would you have a code snippet to help me started with APA102 please? I've never heard about this one before.h