1 Known Issues for the MCC Melody PIC16/18 Diagnostic Library
Provides a list of known issues in the PIC16/18 Diagnostic Library.
| Issue | Issue Title | Affected Component(s) | Issue Description | Workaround |
|---|---|---|---|---|
| FUSA_8BIT_LIB-9706 | Setting the TMR1 period for Clock Line Frequency does not resolve the 500ms MCC warning | SW_CLOCK_PERIODIC_MONITOR_02 | When setting the Timer Period in TMR1 for SW_CLOCK_PERIODIC_MONITOR_02, it should in turn automatically set the Actual Timer field to a value that is ≥ to 500ms < than 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 SW_CLOCK_PERIODIC_MONITOR_02 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. |
| M8PD-11272 | Timer1_HasOverflowOccurred() API is
missing from the TMR1 PLIB, causing a failure in the PIC16/18 Diagnostic
Library | SW_CLOCK_PERIODIC_MONITOR_02 | SW_CLOCK_PERIODIC_MONITOR_02 fails to compile with the
latest TMR1 PLIB due to the missing Timer1_HasOverflowOccurred()
API. | In Content Manager, revert the TMR1 PLIB version to any version prior to v5.0.0. |