Matrix user forums

Hello

I have new install v6 and have the error at compiling.
The code run in Simulation well.
Pleas help

Regards Wolfgang

Hi Wolfgang,

We are looking into the problem. Seems to only be effecting a very small percentage of our users. Are you using Avast anti virus by any chance?

hello Beny
yes,I use avast.
I deseable it bevor the new installing v6,because avast say the "fc_launcher.exe" is in the Quarantäne Folder.
but I put it bak...
The error , I have also if I deactivate avast.

Regards wolfgang

Hello Benj

On my Workstation,I deinstall avast and zonealarm.
After a new install v6,I have the same error.

Regards wolfgang

Hello Benj

Any News?

Regards Wolfgang

Hello Benj

I dont no the Situation,must I stop my proj. with these chip?
A other Problem with EXTI1 :
If jou test the c_code the value for pps-pin is set in bit0 to bit7 but it must set in bit8 to bit15.....

// Unterbrechung
// Unterbrechung: Aktiviere INT1
INTCON2bits.INT1EP = 0;
RPINR0 = (RPINR0 & 0xFF00) | 20; >>>>>> dont work on hardware
IEC1bits.INT1IE = 1;

// Unterbrechung
// Unterbrechung: Aktiviere INT1
INTCON2bits.INT1EP = 0;
RPINR0 = ((RPINR0 & 0x00ff) | (20 << 8 )); >>>>> work on Hardware
IEC1bits.INT1IE = 1;

Regards Wolfgang

Hello

Hope for a answer

wolfgang

Hello,

Thanks for the spot, Just having a look through now to see if these devices need any other fixes.

Hello Wolfgang,

Thanks for letting us know about the issue.

Right here are all the definition files that this bug effects. Hopefully it should now be fixed but let me know how you get on.

To apply the fix please extract the contents of the archive into your "C:\Program Files (x86)\Flowcode 6\FCD\PIC16" directory before restarting Flowcode.

Hello Benj

Now it set the bits corect,but my Problem compile to hex ;the error exists still.

Regards Wolfgang

Hello Wolfgang,

Just tried a compile here using that device and it's working fine.

In Avast have you white listed the fc_licensing.exe file? Might also be worth checking the files Avast has blocked and seeing if any others are related to Flowcode.

If you disable Avast but do not white list the file then Avast will continue to block it.

Personally I used to love Avast but installing it recently on my server caused it to come to a crawl so it seems to have become very bloated and I certainly wouldn't recommend it to anyone any more. AVG had the exact same problem a few years back. NOD32 seems very good and stable but you have to pay for a license.