"getenv" doesn't know all the CLC register names

[bschriek]

PCW Compiler IED, PCB, PCM 5.118
This problem is already posted before!
Just another example....

[Ttelmah]

So, tell CCS.

That way they'll update these on the next release. Posting this here is
rather pointless.

[bschriek]

Yes, I all ready did.

[temtronic]

I wouldn't expect CCS to fix this 'overnight'. Their compilers have 1,000s of PICs to deal with,100s of 'bugs' and a handful of programmers.
It takes TIME to open up a bug report, properly test and confirm,decide on a 'fix',recode, retest, confirm 'fix' DID fix the original bug AND not introduce a new 'bug'.
I can see a lot of time to do this.Hmm, is your reported bug JUST for the PIC you use or is it in the family or worse case, common to all PICS ? If 'in the family', that could mean 20-100 more PICs that need to be updated and tested.

[Ttelmah]

I think it'd be 'next release'. Like the binary database of chip features, I expect
this is actually a database that is compressed and built inside the compiler.

[bschriek]

It seems the 16F17114, 16F18114, 16F17124 and 16F18124 have the same problem.

[waffles]

After looking at the datasheet for the 16F18124 I'm not sure what the issue is?

It doesn't have distinct registers for each module - you select what CLC you want to configure via the CLCSELECT register.

[bschriek]

Underneath the comment of Richard (CCS Support).
Clear description and I will try it asap, Thanks!


For whichever chip your using there will be the following built-in
> functions for the CLC peripheral:
>
> setup_clcX()
> clcX_setup_input()
> clcX_setup_gate()
>
> X being the CLC peripheral you want to setup, for a device with 4 CLC
> peripherals it can be 1..4. The following is an example showing how
> to setup CLC1 in OR XOR mode so that it will do an XOR of the inputs
> on CLCIN0 and CLCIN1 pins:
>
> //Initialize the CLC1 peripheral in or-xor mode
> setup_clc1(CLC_ENABLED | CLC_MODE_OR_XOR);
>
> //Setup the CLC1 inputs
> clc1_setup_input(1, CLC_INPUT_CLCIN0); //input 1 set to CLCIN0
> clc1_setup_input(2, CLC_INPUT_CLCIN1); //input 2 set to CLCIN1
> clc1_setup_input(3, CLC_INPUT_CLCIN0); //input 3 set to CLCIN0, not
> using this input
> clc1_setup_input(4, CLC_INPUT_CLCIN0); //input 4 set to CLCIN0, not
> using this input
>
> //Setup the CLC1 gates
> clc1_setup_gate(1, CLC_GATE_NON_INVERTED_INPUT_1); //set gate 1 to
> non inverting input 1
> clc1_setup_gate(2, CLC_GATE_CLEAR); //set gate 2 to always
> output 0
> clc1_setup_gate(3, CLC_GATE_NON_INVERTED_INPUT_2); //set gate 3 to
> non inverting input 2
> clc1_setup_gate(4, CLC_GATE_CLEAR); //set gate 4 to always
> output 0
>
> The setups for CLC2, CLC3 and CLC4 would be similar, just change the
> calls to the functions to setup_clc2(), clc2_setup_input() and
> clc2_setup_gate() for CLC2, setup_clc3(), clc3_setup_input() and
> clc3_setup_gate() for CLC3, and setup_clc4(), clc4_setup_input() and
> clc4_setup_gate() for CLC4. The built-in functions will automatically
> set the CLCSELECT register based on which CLC you're setting up.
>
> If you want to manually setup the CLC peripherals then you'll need to
> set the CLCSELECT register to the one you want to setup, before
> writing the CLCnCON, CLCnGLS0, CLCnGLS1, CLCnGLS2, CLCnGLS3, CLCnPOL,
> CLCnSEL0, CLCnSEL1, CLCnSEL2 and CLCnSEL3 registers. Write 0 to the
> CLCSELECT register to setup CLC1, write 1 to the CLCSELECT register to
> setup CLC2, write 2 to the CLCSELECT register to setup CLC3 and write
> 3 to the CLCSELECT register to setup CLC4.
>
> Richard
> CCS Support

[Ttelmah]

Ah,
So there isn't actually a CLC2CON register. There is a single CLCnCON
register, which talks to CLC1, 2, 3 etc., according to char is in CLCSELECT.
That needs careful reading of the data sheet to see.....