gateware: Rework the low-level line state monitoring ticks
The 'tick' system was meant to allow the firmware to monitor the
low level state of the line, beyong just "not aligned", but it was
never really useful in the present state.
Now we have more tick source available (but only one can be measured
at the same time). More specifically, the firmware can monitor the
presence/absence of raw pulses (LOS condition), it can also monitor
the number of '1' pulses to detect an AIS signals, or simply the rate
of RX pulses (to tune the local oscillator to incoming signal rate).
Signed-off-by: Sylvain Munaut <tnt@246tNt.com>
Change-Id: I31fa8a717a26643f1b6ca5644bee1d8c41a2512e
diff --git a/gateware/e1-tracer/rtl/top.v b/gateware/e1-tracer/rtl/top.v
index 0e76c5a..8e1d67b 100644
--- a/gateware/e1-tracer/rtl/top.v
+++ b/gateware/e1-tracer/rtl/top.v
@@ -80,7 +80,7 @@
wire [(WB_N*32)-1:0] wb_rdata_flat;
// Ticks
- wire [1:0] tick_e1_rx;
+ wire [7:0] tick_e1;
wire tick_usb_sof;
// Clocks / Reset
@@ -136,7 +136,7 @@
.wb_m_we (wb_we),
.wb_m_cyc (wb_cyc),
.wb_m_ack (wb_ack),
- .tick_e1_rx (tick_e1_rx),
+ .tick_e1 (tick_e1),
.tick_usb_sof (tick_usb_sof),
.clk_sys (clk_sys),
.rst_sys (rst_sys),
@@ -167,7 +167,7 @@
misc misc_I (
.btn (btn),
- .tick_e1_rx (tick_e1_rx),
+ .tick_e1 (tick_e1),
.tick_usb_sof (tick_usb_sof),
.rst_req (rst_req),
.wb_addr (wb_addr[7:0]),