-
Notifications
You must be signed in to change notification settings - Fork 17
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
added link to andlo script to install AIYv1 #49
base: master
Are you sure you want to change the base?
Conversation
@@ -24,7 +24,7 @@ a headless raspbian image is also maintained by the community | |||
| ReSpeaker | 2-mic<br>4-mic squared<br>4-mic linear<br>6-mic | 2-mic<br>4-mic squared<br>4-mic linear<br>6-mic | manual install | | |||
| USB | Yes | Yes | Yes | | |||
| SJ-201 | Yes | Yes | **WIP** | | |||
| Google AIY v1 | Yes<br>*manual configuration* | Yes<br>*manual installation* | manual install | | |||
| Google AIY v1 | Yes<br>*manual configuration* | Yes<br>*manual installation* | [manual install](https://github.com/andlo/picroft-google-aiy-voicekit-skill/blob/master/install_AIY.sh) | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@j1nx can you review this, i think this script is doing much more than is needed
perhaps add a new helper script directly to ovos-raspbian repo
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am on the process of that now. This does way more, and some is not applicable
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Line 13 to 21 needs checking, what those firmware package does exactly. Then migrated to ovos-i2csound detection and configuration system.
The rest is all simple stuff that can be done already within that system. (This answes my own question at the other PR)
I just tested what it takes to make the aiy voicehat v1 get detected by pulse and alsa. All that is needed is the dtoverlay to be added to config.txt |
for dynamic setup of hardware in buildroot would be great to find out what is connected before adding the dtoverlay at PHAL level we can probably just check for dtoverlay=googlevoicehat-soundcard and decide to load it based on that? also not perfect, this would for example conflict with chatterbox hat which also uses it but has different button polarity LEDs and such |
Auto detecting the v1 might be difficult. The v2 you can see with i2cdetect. I'm not sure how the dtoverlay interfers with other overlays, or if you can have multiple, but if the dtoverlay for the hat is active, the v2 bonnet does not work correctly |
Googling a bit I found this https://raspberrypi.stackexchange.com/questions/39153/how-to-detect-what-kind-of-hat-or-gpio-board-is-plugged-in-if-any I am not in front of my rpi now, so I cannot check, but I am really curious |
This is a PR that show i2c connections for the v2 voicebonnet |
Looked at this, however this detection is for when the dtovwerlays are already loaded and an EEPROM has been read. For us to dynamically loading the overlays, it will not work. Currently we are doing it to scan the bus for know signatures and certain assumtions. It then loads the right device tree overlay for linux to pick it up. |
No description provided.