Hard Processor System Technical Reference Manual: Agilex™ 5 SoCs

ID 814346
Date 11/27/2024
Public
Document Table of Contents

A.4.3.4. Watchdog Causes HPS Warm Reset Event

In the following diagram, the h2f_gp_out[1] goes low when h2f_reset is asserted high and remains low until the HPS software drives it high.

Figure 337. Watchdog Causes HPS Warm Reset Event
The following list shows the sequence of events:
  1. h2f_user0_clock stops running.
  2. HPS is reset, indicated by h2f_reset is asserted high and h2f_watchdog _reset is asserted high.
  3. CPU is reset, becomes non-operational.
  4. h2f_gp_out[1] is reset to low, due to the HPS reset.
  5. h2f_user0_clock begins running at boot clock frequency.
  6. h2f_reset is de-asserted low and h2f_watchdog_reset is de-asserted low.
  7. CPU is released from reset, becomes operational and begins running FSBL.
  8. FSBL software configures PLLs, h2f_user0_clock is tuned to configured frequency.
  9. Software asserts h2f_gp_out[1] to high.
Note: Make sure your FPGA logic can handle the h2f_user0_clock stopping above. that is, you must implement asynchronous reset using h2f_gp_out[1].
Note: Software is not able to set h2f_gp_out[1] = 0 before entering an HPS Warm Reset caused by a Watchdog event.