Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob

CSV error event timing in TRAVEO™ T2G MCU

CSV error event timing in TRAVEO™ T2G MCU

Matsuzawa
Employee
Employee
10 questions asked 5 questions asked 10 sign-ins

Japanese-Translation: TRAVEO™ T2G MCU におけるCSVエラーイベントタイミング

CSV can detect clock errors even when the monitored clock stops. This KBA explains when CSV detects clock errors.

The CSV uses two clocks to detect clock errors. One is the monitored clock, which is related to the duration of the monitor event (“Period”). The other is the reference clock, which is related to the Lower/Upper limit.

The CSV detects clock errors at either of the following times:
    1) If the reference clock count was outside the Lower limit when the monitor event occurred.
    2) When the count of the reference clock reaches the Upper limit before the monitor event occurs.

Basically, the CSV checks that the reference clock is within the Lower/Upper limits when the monitor event is occurred with above timing 1). However, monitor event does not occur when the monitored clock is stopped. In this case, the CSV can detect clock errors with above timing 2).

Below are the normal or error patterns, respectively.

0) Normal pattern

Normal pattern.png

1) Error pattern 1 (Monitor event <= Lower limit)

Matsuzawa_7-1684834209655.png

2) Error pattern 2 (Monitor event > Upper limit or Monitored clock is stopped)

Matsuzawa_5-1684834142282.png

More information

  • TRAVEO™ T2G Architecture TRM
  • SETTING CSV PARAMETERS, TRAVEO(TM) T2G FAMILY (002-32474)

More like this (optional)

  • None

Note:

 This KBA applies to the following series of TRAVEO™ T2G MCUs:

  • TRAVEO™ T2G CYT2xx series
  • TRAVEO™ T2G CYT3xx series
  • TRAVEO™ T2G CYT4xx series
0 Likes
100 Views