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.

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

c++ API not reacting to changes in VHDL components under loopy workflow #8

Closed
AndrewSftD opened this issue Apr 24, 2014 · 5 comments
Closed
Assignees
Labels

Comments

@AndrewSftD
Copy link

loopy seems to be ignoring changes in VHDL components when creating the host-side API. More extensive testing required. And perhaps bug fix or complete change to generic API generation process.

@AndrewSftD
Copy link
Author

Update: Have done more extensive testing, this issue in now confirmed.

@cdeschryver
Copy link
Member

this should be fixed for the next milestone with the stable ML-605 release...

@cdeschryver
Copy link
Member

Idea: checksum with warning / error if bitstream does not match current API

mweberUKL pushed a commit to mweberUKL/msdlib.loopy that referenced this issue Jul 17, 2014
… and output to constants-file of board- and client-api; adding of protocol to check correct version still tbd
@mweberUKL
Copy link
Collaborator

I added the checksum over the config file (bdf-file) to the generation process. The checksum is saved in both the board-side and the host-side driver. I also added a function to perform the check that the checksum on the board matches the checksum in the host-driver (called check_checksum() ).

The feedback of the function is not perfect. It simply exits the complete host-program and prints an error message to the console. Maybe we can think about a better feedback and a possibility to react to the error.

I tried the checksum check on the AxiFIFO example. It seams to work reliably. Maybe somebody else can check to implementation before we merge into the may repository.

https://github.com/mweberUKL/msdlib.loopy/tree/development

@mweberUKL
Copy link
Collaborator

Checksum works as a safety procedure (kills the program if checksum does not match). See issue #20 for further improvements.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants