Demonstrate data exchange across 2 AMDS boards

[mohamed-dek1]

Context

Related Issues / PRs: (To do: list all related issues)

• Design and Implement a Daisy Chain Protocol to be used with the AMDS and FBC #80
• Implement daisy-chain firmware and demonstrate first data exchange on AMDS #92
• Design a spec for the Daisy Chain Protocol #91
• Modify the AMDS firmware to receive, handle, and send data from another AMDS as per the DCP spec. #100

We are trying to implement the Daisy Chain Protocol that is listed above. Once the base functionality is confirmed, we need to demonstrate that it works with 2 AMDS boards. Although this might not meet the timing requirements we're looking for, there will be a new issue tracking the improvements to the changes and extending it to 3 boards.

Approach

Close this issue by:

• Demonstrating data exchange across 2 AMDS boards
• Demonstrate the AMDC receiving and processing 2 AMDS boards worth of data

[mohamed-dek1]

Per 3/18 this comment:

The AMDS firmware changes have been tested and show that an AMDS is able to acquire its own data along with another AMDS's data and send it over to the AMDC. The current issue is that the AMDC is unable to show the data because it's timing out. The AMDS IP Core changes need to be reviewed so that the data doesn't time out.

[mohamed-dek1]

Per 3/19 this comment:

@elsevers, I've demonstrated the ability of the AMDS and AMDC to send and process data daisy-chained across 2 AMDS boards. The issue below will be tracking further modifications so that the changes meet the timing requirements necessary for this project. I believe this issue and adjacent ones can be closed. Can you review the comment linked above?

• Demonstrate 3x AMDS’s in series using the DCP meeting timing requirements #95

[elsevers]

@mohamed-dek1. Nice work!

See my comment here:

• Modify the AMDS firmware to receive, handle, and send data from another AMDS as per the DCP spec. #100 (comment)

I am ready for you to close these out as soon as you have created a PR in both repos and indicated we have achieved this milestone in the comments on those PRs.

[mohamed-dek1]

@elsevers, the 2 PRs below have been created to track the additional changes to meet timing requirements. Each PR has a comment mentioning the milestone and is also closing an issue related to it.

• Add AMDC Firmware changes to implement the DCP AMDC-Firmware#500
• Add AMDS firmware changes to implement the DCP #102

[mohamed-dek1]

Per this comment:

I will be closing this issue. The issue below will be tracking the changes to meet timing requirements.

• Demonstrate 3x AMDS’s in series using the DCP meeting timing requirements #95