bslathi19
  • Joined on 2025-11-07
bslathi19 pushed to master at bslathi19/alibaba_pcie 2025-11-15 15:51:25 -08:00
cc40760c66 Change from using the value of the macro to just an ifdef
bslathi19 pushed to master at bslathi19/alibaba_pcie 2025-11-15 15:44:34 -08:00
462a3cb158 Fix gty ip path
bslathi19 pushed to master at bslathi19/alibaba_pcie 2025-11-15 15:42:19 -08:00
d32d31cead Add basic tb that shows it kind of works
4bd09e8f83 Add eth dma wrapper
Compare 2 commits »
bslathi19 commented on issue bslathi19/alibaba_pcie#2 2025-11-15 10:53:49 -08:00
Link PCIe to Ethernet

Bruh this already exists, its just called taxi_dma_client_axis_(source/sink)

bslathi19 closed issue bslathi19/alibaba_pcie#2 2025-11-15 10:53:49 -08:00
Link PCIe to Ethernet
bslathi19 opened issue bslathi19/alibaba_pcie#2 2025-11-14 22:41:13 -08:00
Link PCIe to Ethernet
bslathi19 commented on issue bslathi19/alibaba_pcie#1 2025-11-12 22:53:41 -08:00
PCIe DMA

Yes, that fixes it.

bslathi19 closed issue bslathi19/alibaba_pcie#1 2025-11-12 22:53:41 -08:00
PCIe DMA
bslathi19 pushed to master at bslathi19/alibaba_pcie 2025-11-12 22:52:05 -08:00
31513dc16a Add link to BASER from taxi tb
bslathi19 pushed to master at bslathi19/alibaba_pcie 2025-11-12 22:51:15 -08:00
0a5fa2cf48 Add 25g phy
bslathi19 pushed to master at bslathi19/alibaba_pcie 2025-11-11 23:08:22 -08:00
13b238e51e Enable Client Tag, remove ILA
bslathi19 commented on issue bslathi19/alibaba_pcie#1 2025-11-11 22:52:52 -08:00
PCIe DMA

Interesting, in the example they enable client tag, should we try that?

bslathi19 commented on issue bslathi19/alibaba_pcie#1 2025-11-11 22:18:10 -08:00
PCIe DMA

ok the only thing of note here that I can think of is that the sequence number is the same: 0. Do we need to change it so that we send different sequence numbers?

bslathi19 commented on issue bslathi19/alibaba_pcie#1 2025-11-11 21:57:50 -08:00
PCIe DMA

Here are the RC and RQ busses for the FIRST transfer, this is the one that is successful.

bslathi19 commented on issue bslathi19/alibaba_pcie#1 2025-11-11 21:15:54 -08:00
PCIe DMA

So the problem is that we are not writing to the memory again. We are seeing wr_cmd_valid for the first write, but not the second one. But read is still happening, so we are reading the nonsense data.

bslathi19 commented on issue bslathi19/alibaba_pcie#1 2025-11-10 22:40:32 -08:00
PCIe DMA

Huh, It looks like even though we read the second data, the data that we are writing back is still the old data. So its coming from the FPGA, not from the PC.

bslathi19 commented on issue bslathi19/alibaba_pcie#1 2025-11-10 22:39:05 -08:00
PCIe DMA

so for the RQ and RC streams, they are both 256 bit with 8 bits of keep only, RQ is 62 bits and RC has 75 bits of user.

So we can do a 75 bit tuser,

data: 256 keep: 8 user: 75 last:…

bslathi19 commented on issue bslathi19/alibaba_pcie#1 2025-11-09 22:34:49 -08:00
PCIe DMA

Hmm supposedly the core is still incrementing the tag when we send the request. I think we will need to look at the actual axi streams. they are like 256 bits wide though so it will be a pretty…

bslathi19 pushed to master at bslathi19/alibaba_pcie 2025-11-09 22:26:30 -08:00
df377dda5d Add ILA for debugging dma requests
bslathi19 commented on issue bslathi19/alibaba_pcie#1 2025-11-09 22:21:38 -08:00
PCIe DMA

Maybe we need to look at the RQ and RC interfaces? It might be that we are not getting a response from the cpu again? Maybe the CPU needs to see a second tag or something?