Compiled projects do not run properly on this chip after updating on 4/9/2019.
I had to re-install Flowcode to fix a similar problem back in early March.
I updated Flowcode on 4/9. I remember that there were a couple PIC 16LF15354 changes included in this update.
I am now stuck. re-installing did not work. I also re-installed from earlier downloads to no avail. It looks like Flowcode applies all the latest updates to older downloads also.
I don't know if it is a PIC support issue, or some other thing corrupting my hex files.
Help!
Did PIC 16LF15354 support change?
Moderator: Benj
- Benj
- Matrix Staff
- Posts: 15312
- Joined: Mon Oct 16, 2006 10:48 am
- Location: Matrix TS Ltd
- Has thanked: 4803 times
- Been thanked: 4314 times
- Contact:
Re: Did PIC 16LF15354 support change?
Hello,
Does the chip now run at all or is it a problem specific to a certain component? Can you try a 1 second flasher test to confirm if the chip is running.
Looking at the 16LF15354 definition file these are the changes that have been made.
Does the chip now run at all or is it a problem specific to a certain component? Can you try a 1 second flasher test to confirm if the chip is running.
Looking at the 16LF15354 definition file these are the changes that have been made.
Regards Ben Rowland - MatrixTSL
Flowcode Product Page - Flowcode Help Wiki - Flowcode Examples - Flowcode Blog - Flowcode Course - My YouTube Channel
Flowcode Product Page - Flowcode Help Wiki - Flowcode Examples - Flowcode Blog - Flowcode Course - My YouTube Channel
Re: Did PIC 16LF15354 support change?
OK, I found the problem. I'm not surprised that the issue was on my side.
The one IOC PORTABC interrupt I'm using was set incorrectly.
I only wanted to look at RB7 falling edge. Somehow, multiple IO pins were selected for triggering also. Looking back several on versions of my code, this interrupt was set this way all along. I have no idea how my program worked properly before. Something in the update caused this issue to surface.
Thank you again for the speedy support provided.
Bep
The one IOC PORTABC interrupt I'm using was set incorrectly.
I only wanted to look at RB7 falling edge. Somehow, multiple IO pins were selected for triggering also. Looking back several on versions of my code, this interrupt was set this way all along. I have no idea how my program worked properly before. Something in the update caused this issue to surface.
Thank you again for the speedy support provided.
Bep