Yes, ports will be in a sequential order.
I'll be using ports:
- Seconds: PORTC.3
- Minutes Units: PORTC.4
- Minutes Thenths: PORTC.5
- Hours Units: PORTC.6
- Hours Tenths: PORTC.7
16F690 has:
PORTA.0..5
PORTB.4..7
PORTC.0..7
Yes, ports will be in a sequential order.
I'll be using ports:
- Seconds: PORTC.3
- Minutes Units: PORTC.4
- Minutes Thenths: PORTC.5
- Hours Units: PORTC.6
- Hours Tenths: PORTC.7
16F690 has:
PORTA.0..5
PORTB.4..7
PORTC.0..7
Last edited by flotulopex; - 25th July 2024 at 07:41.
Roger
By changing pinsel var you can select different portc pins
if you need the remaining portc pins then more code is needed
Code:' 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
Warning I'm not a teacher
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
Warning I'm not a teacher
Last edited by Ioannis; - 25th July 2024 at 22:21.
have you tried to light a rgb led strip with a 690 @20mHz yet ?
Check this:![]()
Roger
And here's the project's code for now.
Roger
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
Bookmarks