FlooNoC icon indicating copy to clipboard operation
FlooNoC copied to clipboard

Determining request or response source in the FlooNoC

Open mubashir913 opened this issue 1 year ago • 1 comments

In FlooNoC, since all incoming non-atomic request going to slave and response coming back from the slave, have identical AXI4 ID, while atomic requests have unique IDs, then if we want to know at the slave side the source of the request, or if we want to know at the master side the source of the response, how can it be done? Should I use the src_id in the header of the request/response. For example, for AW signal, will I have to use the floo_req_in.narrow_aw.hdr.src_id to check where this request is coming from?

mubashir913 avatar May 07 '24 13:05 mubashir913

Yes you are correct, the source can only be identified on the NoC side with the src_id field in the header. AXI requests coming from the NoC don't contain any information anymore about the actual source, since the ID is remapped at entry as you mentioned.

fischeti avatar May 08 '24 15:05 fischeti