PIC18LF26K83, CAN, and PPS (v5.091) [Solved]

newguy · Joined: 24 Jun 2004 Posts: 1907

Has anyone managed to get CAN working on one of these things? I have CANRX connected to PIN_B2 (which is the default for PPS) and CANTX connected to PIN_B1. CANTX doesn't have a default; in fact, even though the processor has only one CAN peripheral, there exists a CANTX0 and CANTX1 in the list of PPS remappable outputs. I can't find anything definitive in the Microchip documentation (data sheet and a migration guide I found which outlines what to do when porting from 18FxxK80 to the 'K83). I assume that CANTX0 is the proper output, but I tried CANTX1 as well with absolutely no luck.

That aside, I do have CAN reception working. I cannot transmit any CAN packets.

In frustration I changed the PPS1WAY fuse to NOPPS1WAY so that I could try the pps_select() function and have a look at the disassembly. From what I can gather, the compiler is accessing the wrong page (and wrong register) for the PPSLOCK register. I gave up trying to trace what it was doing beyond that and instead hard coded the absolute address of the PPSLOCK register and the RB1PPS register as opposed to using the getenv() function after using said function didn't allow me to transmit CAN packets.

Pretty much at my wits end with this.

Ttelmah · Joined: 11 Mar 2010 Posts: 19506

The 'standard' way to handle PPS and CAN on the CCS drivers, is to do this:

newguy · Joined: 24 Jun 2004 Posts: 1907

I installed 5.093 (latest version I have) and it's not any better. I can see at the top of main that the

Ttelmah · Joined: 11 Mar 2010 Posts: 19506

Once a PPS selection is done it overrides any existing peripherals.

Can confirm I just tried 5.093, and it still uses the wrong addresses.
The fix is in 5.094 unfortunately....

newguy · Joined: 24 Jun 2004 Posts: 1907

Combination of one wrong register address definition, a somehow corrupted CCS installation, and a CCS acknowledged issue with their pps_select() function all added up to about one full day (and one sleepless night) of headaches for me. Solved now.

As an aside: has anyone else noticed that windows 10 and CCS don't seem to get along from time-to-time? This is now the 3rd time in the last year or so on 2 different machines that my CCS installation just starts to behave really badly. Like making code changes and compiling those changes, but the contents of the output hex file not actually changing...?

Ttelmah · Joined: 11 Mar 2010 Posts: 19506

I think there is an issue that CCS still likes to talk at times to it's files
in the program files directory, which can cause permission problems.
This affects quite a few things like registry keys as well. Basically if you
attempt to write to a location that Windows considers 'protected', the write
will fail. If the virtualisation is enabled, it instead
directs the write to a shadow 'copy' of the required location, stored in the
user data.
This is File & Registry virtualisation.

If your system has this virtualisation disabled, this could result in data loss
(since Windows 10 will not allow the write to occur).
This is in:

\Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options

run secpol.msc
local policies tab
security options tab.

Then look for
'User Account control Virtualize file and registry write failures'.

This must be enabled to allow applications that use the older Windows
security options to work. If it isn't, turn it on. Reboot after enabling.

PCM programmer · Joined: 06 Sep 2003 Posts: 21708

Ttelmah · Joined: 11 Mar 2010 Posts: 19506

I say how to do this in the lines after.

It's not a 'folder', it's part of the Windows configuration data.

secpol.msc accesses it as outlined.

They are actually stored in a combination of places. The registry, and
%WINDIR%\system32\grouppolicy

You can also access them using gpedit.msc, instead of secpol.msc, and
then the location is the whole string given.

temtronic · Posted: Sat Sep 05, 2020 5:36 am

One day Mr. T's head will explode from all the data that's in it !!! Laughing

Ttelmah · Joined: 11 Mar 2010 Posts: 19506

I have days at work, where I say, that I need to go and put my head
in a bucket of cold water. It feels like it wants to explode....

newguy · Joined: 24 Jun 2004 Posts: 1907

Weird, virtualization is actually enabled on both my machines. No idea why my installations get corrupted from time to time.

PCM programmer · Joined: 06 Sep 2003 Posts: 21708

Me too. Already enabled.

Ttelmah · Joined: 11 Mar 2010 Posts: 19506

OK.

I have never seen this issue. Have currently about twenty copies of the
compiler all installed in separate directories, and can use them from
Win XP, Win7, Win10 32 & Win 10 64.
Only difference is that these are all 'virtual' copies of Windows, since I run
in a Mac. I also though have a copy on my laptop, which is also Win 10,
and this too has never displayed an issue. The virtualisation should not
change anything, the Windows all run just as normal versions.
However one difference, is in all cases I locate the actual source files
in my own 'source data' directory, and then have sub-directories for each
project. This is owned by me, and has R/W permissions for me. I never
leave the sources in the default/standard locations.
I suspect it has to be a Windows permissions issue of some sort. These
are (unfortunately) sometimes quite common, since Windows shifted to
trying to tighten it's security behaviour up.