-
Notifications
You must be signed in to change notification settings - Fork 4
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
YOLO3 workload #5
Comments
IIRC I just followed along with the original documentation here: https://github.com/CSL-KU/firesim-nvdla#running-yolov3-on-nvdla. You will probably have to modify the FireMarshal workload files / FireSim config files a bit (FireMarshal: to match the FireMarshal version in CY, inherit from the nvdla workload |
Thank you @abejgonzalez,
|
Frankly I don't remember since this was so long ago. I would try to update the YOLO3 workload instead of going to a lower version of Linux... Sorry I can't be of more help. |
Thank you @abejgonzalez, I am grateful for any help. Managed to build the YOLO3 workload with the newer libraries. Now the execution hangs at the following point. Maybe you can give me a hint where it could fail here.
|
Hi @manox .Have you fix this problem about GLIBC_2.26? |
That was quite a long time ago and I don't think I followed it up. Sorry. |
Hello @manox , I have resolved this issue. I previously used the official nvdla_runtime, so displays GLIBC error, but when I use the nvdla-workload/nvdla-base/build-umd.sh script to generate my own nvdla_ runtime, it runs normally. |
Hi @abejgonzalez,
In an chipyard NVDLA integration PR conversation (ucb-bar/chipyard#505 (comment)) you said you have been able to run a YOLO3 workload.
Is this still possible and if so, can you briefly explain how? Thank you!
The text was updated successfully, but these errors were encountered: