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

Physical I/O interaction with constrain file (*.xdc) #49

Open
teerameth opened this issue Mar 18, 2022 · 2 comments
Open

Physical I/O interaction with constrain file (*.xdc) #49

teerameth opened this issue Mar 18, 2022 · 2 comments

Comments

@teerameth
Copy link

I have already made myself through examples to create accelerated ROS2 node in this repo but I haven't seen any detail about interfacing to physical pin which usually determined by *.xdc files in Vivado. Did I miss something or I have to do some additional steps ?
I plane to change from normal HLS workflow to KRS in my senoir thesis, if there is a tutorial about interfacing to physical hardware it will be perfect !
Thank in advance.

@vmayoral
Copy link
Contributor

@teerameth can you elaborate? What exactly are you looking for in connection with ROS? Note KRS focuses on the ROS integration, but the default (and traditional) Vitis and Vivado flows remain usable, as always.

Can you provide a draft example of what you’d like to see and what such a “ROS example” will achieve? Be specific about hardware interfacing please.

@teerameth
Copy link
Author

I'm looking for something like "Node that read digital input from some digital pin then publish as ROS topic" or "ROS2 service which recieve I2C address then scanning via digital pins (as SCL, SDA) and return whoami register of avaliable devices".
Thankyou.

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

No branches or pull requests

2 participants