Memory Write/Read feature for remote memory access #1475
Unanswered
ThibFrgsGmz
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
For a project, I need two key features for our FSW that I didn't see as being natively available (or at least matching my need) and I'm having a hard time seeing how to implement it easily.
Could I have your advice please?
Our FSW must have two key features:
memory write
consisting of a request and a response (TBC).memory read
, also consisting of a request and a response.Memory write
would be used to reload aFSW
, modify parameters at specific addresses, or configure electronic devices (DDR, sensor,...) arranged on an AMBA bus for example.Memory read
would be used to retrieve areas of memory for diagnostic purposes, or to more easily retrieve electronic device data.From the
GSE
point of view, I imagine to have on the front-end GDS:write request
, a field for the upload address and a field to the binary file to upload.read request
, a field for the address, another for the buffer size. And also a path to the file to be filled with the memory dump (this file is not transmitted to the FSW, it is retrieved by the GSE for the response and where it puts the buffer content).What do you recommend?
How do you see it? Would a single component named e.g. "RemoteMemoryAccess" do on the FSW side, maybe two?
Are there any existing components that should be used as a base?
Beta Was this translation helpful? Give feedback.
All reactions