[EP/tx_head_proc] bugfix: we had a problem with handling the error from PCS - if…

[EP/tx_head_proc] bugfix: we had a problem with handling the error from PCS - if it occured when already the next frame was being set (addr), the PCS got confused

[EP/tx_head_proc] bugfix: we had a problem with handling the error from PCS - if…
[EP/tx_head_proc] bugfix: we had a problem with handling the error from PCS - if it occured when already the next frame was being set (addr), the PCS got confused
4944aa44 · Maciej Lipinski · dafd057e · 4944aa44
Commit 4944aa44 authored Feb 20, 2014 by Maciej Lipinski
Hide whitespace changes
Inline Side-by-side

Showing with 7 additions and 0 deletions

ep_tx_header_processor.vhd modules/wr_endpoint/ep_tx_header_processor.vhd +7 -0

No files found.
--- a/modules/wr_endpoint/ep_tx_header_processor.vhd
+++ b/modules/wr_endpoint/ep_tx_header_processor.vhd
@@ -327,6 +327,13 @@ begin  -- behavioral
        if(pcs_error_i = '1') then
          state      <= TXF_IDLE;
          wb_out.rty <= '1';
+          ----------------------------------------------------------------------------------
+          src_fab_o.error  <= '1'; -- nasty-bug-fix: it might happen that PCS throws error
+                                   -- to a previous frame, but we already start sending
+                                   -- the next one, in this case the frame is stopped being
+                                   -- sent but PCS does not know why... in the end we see
+                                   -- two SOFs in PACs
+          ----------------------------------------------------------------------------------                         
        elsif(abort_now = '1') then
          -- abort the current frame
          state            <= TXF_ABORT;