1 Known Issues

Provides a list of known issues in the MCC Melody PIC16/18 IEC60730 Class B Library.

IssueIssue TitleAffected Component(s)Issue DescriptionWorkaround
FUSA_8BIT_LIB-9889Usage of PAGEMASK to avoid fixup overflow errors(1357) in the PIC16 Stack March diagnostic test does not work with XC8 v2.39PIC16F Stack March Diagnostic The PIC16F Stack March test code fails to compile with the XC8 compiler v2.39 when integrated with other diagnostic modules.For all the inline assembly GOTO instructions, replace the usage of the PAGEMASK macro with the direct address/label.


Example #1:

Change
__asm("GOTO" ___mkstr(PAGEMASK(STACKFAIL)));
To
__asm("GOTO STACKFAIL");

Example #2:

Change
__asm("GOTO" ___mkstr(PAGEMASK(Wr0)));
To
__asm("GOTO Wr0");

FUSA_8BIT_LIB-9706Setting the TMR1 period for Clock Line Frequency does not resolve the 500ms MCC warningClock Frequency Line DiagnosticWhen setting the Timer Period in TMR1 for the Clock Frequency Line diagnostic it should in turn automatically set the Actual Timer field to a value that is ≥ to 500ms and < 501ms. Although the Actual Timer is set within the defined range, the MCC Notification warning which states that the TMR1 Period must be 500ms does not resolve.Currently, a workaround for resolving this MCC warning is unavailable as the issue is sourced from the payload in the TMR1 driver that is meant to trigger the resolution of this warning.

Despite this, the functionality of the Clock Frequency Line test is not affected and will still use the Actual Timer value under the condition that it is ≥ 500ms, and < 501ms. Therefore, this MCC warning can be ignored.