Hi
On May 31, 2022 10:38 pm I posted a bug report named
PIC16(L)F18446.fcdx with wrong definitions .
You promptly solved this uC definitions and all compile well.
The problem is, even with an absolute simple flowchart like this
timer 2 is still not working.
It simulates as if all is correct (functioning as expected) but, after compiled (no errors)
and transfered to the real PIC16LF18446 it doesn't work
If you could look at this before we enter the weekend I will appreciate it very much.
PIC16(L)F18446.fcdx with wrong definitions (continuation)
-
- Posts: 52
- http://meble-kuchenne.info.pl
- Joined: Mon Jan 04, 2021 8:08 pm
- Has thanked: 7 times
- Been thanked: 4 times
PIC16(L)F18446.fcdx with wrong definitions (continuation)
Last edited by miggarc on Sat Jun 11, 2022 6:20 pm, edited 5 times in total.
Many thanks in advance,
Miguel Garcia,
Electronic Systems Developer
-
- Matrix Staff
- Posts: 1465
- Joined: Sat Dec 05, 2020 10:32 am
- Has thanked: 204 times
- Been thanked: 347 times
Re: PIC16(L)F18466.fcdx with wrong definitions (continuation)
I don't have any hardware to test and I'm not familiar with that particular chip, but try putting the following statements into a C icon just before you enable the interrupt:
The first statement ensures the clock source is the main Fosc clock rather that whatever is set in the PPS (Peripheral Pin Select).
Code: Select all
T2CLKCONbits.CS = 2;
T2HLTbits.MODE = 0;
Re: PIC16(L)F18446.fcdx with wrong definitions (continuation)
Hi Steve
Your cue did the trick .
How do I mark this as solved ?
Your cue did the trick .
How do I mark this as solved ?
Last edited by miggarc on Sat Jun 11, 2022 6:20 pm, edited 1 time in total.
Many thanks in advance,
Miguel Garcia,
Electronic Systems Developer
-
- Matrix Staff
- Posts: 1465
- Joined: Sat Dec 05, 2020 10:32 am
- Has thanked: 204 times
- Been thanked: 347 times
Re: PIC16(L)F18466.fcdx with wrong definitions (continuation)
Great news, thanks. I'll ask for the fix to be added to the chip definition file.
I think to mark it as solved you can edit your original post and change the subject line, e.g. by adding "[SOLVED]" to the end of it.
I think to mark it as solved you can edit your original post and change the subject line, e.g. by adding "[SOLVED]" to the end of it.
Re: PIC16(L)F18446.fcdx with wrong definitions (continuation)
Hi...
I was thinking about marking this topic as Solved but, at the very last moment before I did it, another related problem arose:
I found result frequency doesn't change with different options from Clock Source Select ,
at least for any PIC16LF18446 timer interrupt properties where this drop down exists: TMR0, 1,3 and 5 .
Some examples ...
I was thinking about marking this topic as Solved but, at the very last moment before I did it, another related problem arose:
I found result frequency doesn't change with different options from Clock Source Select ,
at least for any PIC16LF18446 timer interrupt properties where this drop down exists: TMR0, 1,3 and 5 .
Some examples ...
- Attachments
-
- 2.jpg (33.52 KiB) Viewed 3279 times
-
- 1.jpg (33.52 KiB) Viewed 3279 times
Last edited by miggarc on Sat Jun 11, 2022 6:21 pm, edited 1 time in total.
Many thanks in advance,
Miguel Garcia,
Electronic Systems Developer
-
- Matrix Staff
- Posts: 1465
- Joined: Sat Dec 05, 2020 10:32 am
- Has thanked: 204 times
- Been thanked: 347 times
Re: PIC16(L)F18466.fcdx with wrong definitions (continuation)
We are aware of this issue. Please see here:
https://www.flowcode.co.uk/forums/viewt ... 6844#p6844
https://www.flowcode.co.uk/forums/viewt ... 6844#p6844