-
Notifications
You must be signed in to change notification settings - Fork 13
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
edgetpu_demo
fails on tflite
version conflict
#108
Comments
It looks like the original error was with the
Can you please post a reference to the |
|
https://coral.ai/docs/dev-board/get-started#run-demo
|
8: Run a model using the PyCoral API
|
Shouldn't Google's tutorial for their product work by any chance? Or does Google produce garbage too? |
The reason this community issue tracker exists is that Google is doing a questionable job maintaining the public-facing Coral software. |
edgetpu_demo
fails on tflite
version conflict
Ad hominem attacks, "Google produce garbage", are an unfortunate way to achieve the goal of getting their demo software working. If you are trying to get their Dev Board to work with the demo software outside of its configured demonstration, good luck. I've spent a considerable amount of time studying their code and effort to get gstreamer working (to the point of installing a Gentoo chroot environment with a high watermark of gstreamer, and trying to make it work, and have concluded that for the Dev Board, anything outside of the sample is going to be risky business. I was able to get some MP4 files to load, e.g., such as those Reolink generates, but they had to be reprocessed in order to not be rejected by the demo implementation of gstreamer. I determined that the video samples themselves, while taken from the same source, a German photographer's duly and appropriate license that allows Google to redistribute his work, were different depending on which options you feed to the software. This subtle distinction is nowhere disclosed. I decided to no longer try to make the Dev Board do anything more than demonstrate a proof of concept and I am awaiting the arrival of the USB version which has been back-ordered at UK Farnell for months and was estimated to be shipping in June -- which it hasn't. I ran into memory problems using my Gentoo chroot version despite giving lots of swap space. The Coral chip is a marvelous innovation, it simply is not available at this time, July 2022, and I am waiting with great expectations the arrival of the USB version so I can implement it on a Linux system I have complete control of, e.g. Gentoo. Oh, and Mendel innovation has ceased, so working within the Mendel environment is now relegated to the category of historic interest. I would say the Google Team became very much aware of the limitations of the Dev Board and therefor introduced the USB version so its true virtues could be harnessed in a suitable environment by patient and determined software developers. |
Another possibility occurred to me. Reinstall the last version of the OS, do not perform any updates, do not set users, do not rename and try the instructions on a completely clean machine. However, I need advice on how to do it. We tried to reinstall according to the instructions for the initial installation and it does not work. Can someone advise me how to do this? |
The text was updated successfully, but these errors were encountered: