UserID4331231
Occasional ContributorJoined 11 months ago
User Profile
Occasional Contributor
User Widgets
Contributions
Questa-sim waveform- How to export to CSV?
I am using Questasim for doing waveform debug. I want to dump current waveform as CSV to apply some analytics on it. When I go to FIle > Export option "waveform" option is greyed out and is not available. I see "Image" option which I dont want; and "VCD" option is also greyed out. please help me on how can i export waveforms I see into CSV format.F-Tile Ethernet Hard IP Design Example - Testbench
I have a question regarding this Ftile Ethernet hard IP example Design. I am able to generate this example design for 400gbe. I am able to load this design (sof) to MA2700Kit. I was able to run tcl script and internal loopback test was successful. I was also able to run testbench basic_avl_tb_top.sv and VSIM run was successful. I have following questions and areas where I need help. At line 144 and 145 in basic_avl_tb_top.sv I can see that Tx outputs are assigned Rx input pins. I would like to understand reason for doing this? I mean shouldn’t the RX lines driven by tasks/function to simulate incoming packets over the ethernet link? I want to modify the testbench to simulate Receiving of a particular 98 byte ethernet frame, and check how mac segmented interface is behaving to communicate this frame; So i can write my custom RTL block to receive it properly. I need help developing tasks/function to simulate incoming packets over the ethernet link. Thank youF-tile-ethernet-hard-ip TX/RX MAC Segmented Client Interface
https://docs.altera.com/r/docs/683023/25.1.1/f-tile-ethernet-hard-ip-user-guide/tx-mac-segmented-client-interface "i_tx_mac_inframe" signal is explained as " Indicates valid data in each segment for specific rate. Along with the previous segment's inframe signal, this signal indicates the SOP and EOP location." i dont understand the underlined part of explanation. how does i_tx_mac_inframe indicates start of packer (SOP) and end of packet (EOP). can someone please elaborate on this with a couple of examples also another question is how to interpret i_tx_mac_data signals if i_tx_mac_valid == 1'b1 and i_tx_mac_inframe [15:0] == 16'h0 ?Re: JTAG timing violations
I have created another SDC file with "JTAG Signal Constraints" template added. The original SDC already have create_clock -name {altera_reserved_tck} -period 30 [get_ports {altera_reserved_tck}] set_clock_groups -asynchronous -group {altera_reserved_tck} still getting JTAG path violation as aseen in the screenshot. the slack increased to -48.914 as Data Required Time of ~44 was added Vs the last run.Re: JTAG timing violations
I added another SDC file containing JTAG signal Constraints template but I still have JTAG violation the first SDC have create_clock -name {altera_reserved_tck} -period 30 [get_ports {altera_reserved_tck}] set_clock_groups -asynchronous -group {altera_reserved_tck} and the second SDC have JTAG Signal Constraints as generated by steps mentioned above. the slack increased to -48.914 as it added Data required time -44.688 Vs in previous run it was reported as 0.JTAG timing violations
Hello Following are my project details LAST_QUARTUS_VERSION "25.1.0 Pro Edition" DEVICE AGIB027R29A1E2VC "Agilex 7" in SDC file - I have create_clock -name {altera_reserved_tck} -period 30 [get_ports {altera_reserved_tck}] set_clock_groups -asynchronous -group {altera_reserved_tck} I am getting timing violation in JTAG path (n/a domain). Lets ignore IOPLL domain violations for this thread. Attached is the timing compilation results for "n/a" path. I need your help in resolving JTAG timing violations. I tried to refer earlier threads on the "JTAG violations" but its not quite helping so opening this thread. thanksRe: IOPLL related clock constraints
module "custom_mem_bridge_2port_0" definition includes instantiation for dual ported memory as following. altera_syncram altera_syncram_component ( .address_a (address), .address_b (address2), .byteena_a (byteenable), .byteena_b (byteenable2), .clock0 (clk), .clocken0 (ram_clocken0), .data_a (writedata), .data_b (writedata2), .q_a (q_a), .q_b (q_b), .rden_a (read), .rden_b (read2), .wren_a (wren_a), .wren_b (wren_b), .aclr0 (1'b0), .aclr1 (1'b0), .address2_a (1'b1), .address2_b (1'b1), .addressstall_a (1'b0), .addressstall_b (1'b0), .clock1 (1'b1), .clocken1 (1'b1), .clocken2 (1'b1), .clocken3 (1'b1), .eccencbypass (1'b0), .eccencparity (8'b0), .eccstatus (), .sclr (1'b0) ); defparam altera_syncram_component.intended_device_family = "Agilex 7", altera_syncram_component.lpm_type = "altera_syncram", altera_syncram_component.operation_mode = "BIDIR_DUAL_PORT", altera_syncram_component.ram_block_type = "AUTO", altera_syncram_component.byte_size = 8, altera_syncram_component.numwords_a = 1024, altera_syncram_component.numwords_b = 1024, altera_syncram_component.width_a = 64, altera_syncram_component.width_b = 64, altera_syncram_component.widthad_a = 10, altera_syncram_component.widthad_b = 10, altera_syncram_component.width_byteena_a = 8, altera_syncram_component.width_byteena_b = 8, altera_syncram_component.address_reg_b = "CLOCK0", altera_syncram_component.byteena_reg_b = "CLOCK0", altera_syncram_component.indata_reg_b = "CLOCK0", altera_syncram_component.outdata_reg_a = "UNREGISTERED", altera_syncram_component.outdata_aclr_a = "NONE", altera_syncram_component.outdata_sclr_a = "NONE", altera_syncram_component.outdata_reg_b = "UNREGISTERED", altera_syncram_component.outdata_aclr_b = "NONE", altera_syncram_component.outdata_sclr_b = "NONE", altera_syncram_component.clock_enable_input_a = "NORMAL", altera_syncram_component.clock_enable_output_a = "BYPASS", altera_syncram_component.clock_enable_input_b = "NORMAL", altera_syncram_component.clock_enable_output_b = "BYPASS", altera_syncram_component.read_during_write_mode_port_a = "NEW_DATA_NO_NBE_READ", altera_syncram_component.read_during_write_mode_port_b = "NEW_DATA_NO_NBE_READ", altera_syncram_component.read_during_write_mode_mixed_ports = "DONT_CARE", altera_syncram_component.init_file = INIT_FILE, altera_syncram_component.init_file_layout = "Port_A";Re: IOPLL related clock constraints
I am attaching setup report here. I see most of the violation paths are from RAM block - to AVMM interconnect internal buffer. I need help removing these violations. The "custom_mem_bridge_2port_0" is dual ported memory ip wrapped into some logic which adds fanout as it provides copy of AVMM signals from mentoring purpose only, there is no combination logic here. just additional fanouts to S1 and S2 ports goint into DFF inputs and DFF output are used to get copy of AVMM activities for monitoring purpose.
