Updated User Documentation (markdown)
parent
50a7b3e1e4
commit
675aeadcaa
|
|
@ -112,19 +112,18 @@ Last is the [Symbiyosys Formal Verification](https://symbiyosys.readthedocs.io/e
|
|||
|
||||
# Simulation
|
||||
Import all simulation files under [./testbench](https://github.com/AngeloJacobo/DDR3_Controller/tree/main/testbench) to Vivado then run simulation. The `ddr3_dimm_micron_sim_behav.wcfg` contains the waveform. Shown below are the clocks:
|
||||
|
||||
|
||||

|
||||
|
||||
`command_used` shows the command issued at a specific time. As shown below, during reads the `dqs` should toggle and `dq` should have a valid value, else they must be in high-impedance `Z`.
|
||||
|
||||
As shown below, `command_used` shows the command issued at a specific time. During reads the `dqs` should toggle and `dq` should have a valid value, else they must be in high-impedance `Z`. Precharge and activate also happens between reads when row addresses are different.
|
||||

|
||||
|
||||
|
||||
|
||||
|
||||
A part of internal test is to do alternate write then read consecutively as shown below. The data written must match the data read. `dqs` should also toggle along with the data written and read.
|
||||

|
||||
|
||||
|
||||
There are counters for the number of correct and wrong read data: `correct_read_data` and `wrong_read_data`. As shown below, the `wrong_read_data` must remain zero while `correct_read_data` must increment until it reaches the maximum (3499 on this example).
|
||||

|
||||
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue