Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

MOA pipepline #6

Open
BlazeCode2 opened this issue Oct 16, 2018 · 1 comment
Open

MOA pipepline #6

BlazeCode2 opened this issue Oct 16, 2018 · 1 comment

Comments

@BlazeCode2
Copy link
Contributor

BlazeCode2 commented Oct 16, 2018 •
edited
Loading

Hi,
The neighbourExtractor is not passing the data valid and frame valid signals correctly when simulated. And can you tell me the purpose of frame valid and data valid signals in the first convolution layer.
@KamelAbdelouahab
Copy link
Collaborator

Hello,

Indeed, the current version of the MOA is buggy and I have little time to spend on it now :s
What I suggest is to get rid of it for now and use the "default" implementation of dot products with a MAC operation.
Basically, in the DotProduct.vhd file, the MCM and MOA instances are replaced by a pipelined MAC operation. refer to KamelAbdelouahab/haddoc2@ff32608 for details.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@KamelAbdelouahab @BlazeCode2