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

CHaiDNN on other boards #43

Closed
MiguaMG opened this issue Aug 4, 2018 · 6 comments
Closed

CHaiDNN on other boards #43

MiguaMG opened this issue Aug 4, 2018 · 6 comments
Labels
question Further information is requested

Comments

@MiguaMG
Copy link

MiguaMG commented Aug 4, 2018

Dear all,

Has anyone tested CHaiDNN on other type of boards besides zcu102 and zcu104?
In particular I'm thinking on the possibility of using the light version of CHaiDNN (Diet CHaI) on low cost boards (such as the Zybo, Pynq ...). The idea would be using CNNs with very few layers, so presumably there should be enough hardware to handle that.

@nkpavan
Copy link
Contributor

nkpavan commented Aug 7, 2018

Hi @MiguaMG ,
We have not tried building CHaiDNN for Zybo or Pynq boards. You can try building it for low cost boards, given the device you are targeting has sufficient resources to fit DietCHai. You can find the DietCHai resource utilization here.

@Dhananjayadmd
Copy link

Even ZC702 board does not have sufficient resource for DietCHai. Do you have any plan to downscale the design further and give support for ZC702 board?

@trihook
Copy link

trihook commented Aug 20, 2018

@nkpavan Does DietCHai was supported in CHaiDNN v2 ?

@bhargavajs07
Copy link

bhargavajs07 commented Oct 14, 2018

Hello @Dhananjayadmd, I too was trying to build the CHaiDNN framework (in DietCHai mode by mapping only the conv layer to the HW accel, Pooling and DeCONV in S.W) targeting the XC7Z020 device(on ZedBoard) as the platform(using Xilinx SDx v2018.1) .

And I got the an error : ps_e_S_AXI_HP*_FPD for in* cannot be found in the platform ( similar to the one reported in #30 by the OP).
The solution you suggested there, was to rename the ports to zynq_ultra_ps_e_0_S_AXI_HP*_FPD seems to be specific to the ultrascale devices.

Could you please tell if you too came across similar issue, if so, how did you fix it ?

@VishalX VishalX added the question Further information is requested label Oct 23, 2018
@VishalX
Copy link
Collaborator

VishalX commented Oct 29, 2018

@Dhananjayadmd @MiguaMG,

Please refer to issue #93.

@VishalX
Copy link
Collaborator

VishalX commented Nov 2, 2018

Closing. Reopen if required.

@VishalX VishalX closed this as completed Nov 2, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

6 participants