...I've attached the full project...
Thank you for sharing.
Here's my take on it...
I started to open your project in MPLABX version 5.05. It asked whether I wanted to update from older version of MPLABX, so I said no.
I opened your project in MPLABX version 4.20 and started MCC. (MCC plugin version 3.55.1 is installed)
Pin Module "Easy Setup" showed RB15 with IOC "any" but the Registers window of the Pin Module showed CNIEB15 as "Disabled," which is consistent with the statement you showed in the generated pin_manager code. I selected IOC "none" in the Pin Module and verified that the generated pin_manager.c file does not have a statement for CNIEB15.
I have found that (sometimes) when I manually change something in the "Registers" view of an MCC module, future changes in the "Easy Setup" do not override the previous setting. (Not just the Pin Module)
So if, somehow, one of the register settings was changed (maybe inadvertently by the user or maybe by some bug in MCC) things got out of sync. In this case changing the IOC to "none" and back to "any" had no effect. (Sometimes things like this make a difference; this time it didn't.)
So here's what I did next...
In the Pin Manager Grid View, I removed RB15 as a GPIO input (by clicking the padlock) of RB15 in the GPIO line, then added it back.
In the MCC Interrupt Module window, I checked the "Enabled" box for CNI and in the Pin Module "Easy Setup" window, I selected "any" for RB15. Now when I look at CNIEB15 in the CNENB register in the Pin Module "Registers" window, it shows "enabled"
The generated pin_manager.c now has
CNENBbits.CNIEB15 = 1; // Pin : RB15
IEC1bits.CNIE = 1; // Enable CNI interrupt
Note that I did not have this particular problem with a "fresh build" of an MCC project for this chip with MPLABX version 5.05 (MCC plugin 3.65.1) Same for adding IOC functionality to a previous project in version 5.05. I didn't try manual changes to see if they screw the pooch. (There is a limit to my so-called spare time.)
Bottom line: Don't know whether this is an easily repeatable (and therefore 'easily' fixable) bug in MCC, but I think the MCC guys have been very, very responsive in overcoming problems like this when you give them details of your dilemma.
post edited by davekw7x - 2018/10/14 15:57:47