Part Number: TMS320F280049
When the customer uses the CLB module for current protection, their counter module is configured as follow. The reason for setting two adjacent matches is that the customer is worried that the counter will not be detected, so it is detected and protected within two counting times.
A strange phenomenon occurred during the experiment. The action of match1 is normal, that is, when the counter value is equal to 20, it is set to 1, otherwise it is zero. However, the action of match2 is abnormal. when the counter value is equal to 21, it is set to 1,but when the counter value is other values, the counter value is still not cleared. The above situation causes match2 always be 1 after the previous fault is cleared, so the system cannot return to normal operation. It should be noted that this phenomenon cannot be reproduced every time, there may be a one-half chance. I want to confirm whether this problem may occur in the design of the counter module in our CLB when it implements the match of adjacent count values? And how to avoid it?











