fix: clarify comments — AGC width, dual-USB docstring, BE datasheet ref

This commit is contained in:
Jason
2026-04-16 17:51:09 +05:45
parent 7a35f42e61
commit 161e9a66e4
2 changed files with 5 additions and 4 deletions
+2 -2
View File
@@ -29,7 +29,7 @@ module usb_data_interface (
// FT601 Interface (Slave FIFO mode)
// Data bus
inout wire [31:0] ft601_data, // 32-bit bidirectional data bus
output reg [3:0] ft601_be, // Byte enable (active-HIGH per FT601 datasheet / AN_378)
output reg [3:0] ft601_be, // Byte enable (active-HIGH per DS_FT600Q-FT601Q Table 3.2)
// Control signals
// VESTIGIAL OUTPUTS — kept for 200T board port compatibility.
@@ -374,7 +374,7 @@ always @(posedge ft601_clk_in or negedge ft601_effective_reset_n) begin
// Word 4: AGC metrics + range_mode
status_words[4] <= {status_agc_current_gain, // [31:28]
status_agc_peak_magnitude, // [27:20]
status_agc_saturation_count, // [19:12]
status_agc_saturation_count, // [19:12] 8-bit saturation count
status_agc_enable, // [11]
9'd0, // [10:2] reserved
status_range_mode}; // [1:0]
+3 -2
View File
@@ -47,8 +47,9 @@ class STM32USBInterface:
Used ONLY for receiving GPS data from the MCU.
FPGA register commands are sent via FT2232H (see FT2232HConnection
from radar_protocol.py). The old send_start_flag() / send_settings()
FPGA register commands are sent via the USB data interface — either
FT2232HConnection (production) or FT601Connection (premium), both
from radar_protocol.py. The old send_start_flag() / send_settings()
methods have been removed — they used an incompatible magic-packet
protocol that the FPGA does not understand.
"""