-
Notifications
You must be signed in to change notification settings - Fork 298
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
This is not working - No Respeaker card gets installed #30
Comments
@jabulonboaz Please login gitter at Beijing time zoon 10 am. I will teach you how to do this. setup by setup. |
@jabulonboaz Do you online ? Please response me. |
Big thanks to @Pillar1989 for finding in the issue and fixing it for me. Apparently the new drivers would not install due to an i2c configuration or enable issue that neded to be performed in raspi-config. Standing by for @Pillar1989 to post here the options that he changed for others that might run into the same issue to beniefit from too. |
Can someone post the fix here please? |
I enabled i2c using raspi-config but it still does not work. Can @Pillar1989 please put the details of the fix here. Thanks. |
@cogmeta i am waiting for @Pillar1989 to to clarify it as when he did it it was via team viewer and he told me he will provide full instructions, He did it too fast so i could not follow everything but its like a few commands only, whilst you wait here is the relevant "history" of cmd form my pi that gives a clue as to what he did and by following the bellow i belive you will succeed: 8 git clone https://github.com/respeaker/seeed-voicecard -b install @cogmeta bear in mind that we did this with a new clean install of a Raspbian Jessie lite and installing the respeaker 2mic drivers was the first step before i proceeded with the installation of AlexaPi . Now before i started installing AlexaPi i blacklisted the RPi internal sound card just in case, like this: Then when you come back to the terminal you do "aplay -l" and you are only left with the respeaker 2mic voice card. When i completed the AlexaPi installation its was working straight away i never need to do anything in the audio settings of the AlexaPi configuration file. I did made one change though and that was to activate GPIO 17 on the AlexaPi configuration file for the repseaker button to work and be able to activate Alexa from there too as well as my voice - this you can find in the final part of the instructions given in the respeaker git by @Pillar1989 in this link good luck @cogmeta |
@Pillar1989 one thing i cannot figure out is when i adjust the volume in "alsamixer" and then i store it using "sudo alsactl store" the seeings reset after reboot and Alexa is too loud at maximum audio level - how can i save the alsamixer settings for ever? |
Thank you so much @jabulonboaz. I followed all the steps but no luck so far. Will keep digging further. |
It is little frustrating and annoying that seeed studio is makes us wait (possibly hundreds of us) for what might be a small fix. This is not a professional behaviour. I can expect and live with it if it were a open source contribution but not from a company who got paid for the product they have sold and expected to provide a speedy fix when things are not working. |
@cogmeta try also to do this: "Enable/Disable SPI interfaces and automatic loading of the SPI kernel module, needed for products such as PiFace." Enable the "automatic loading of SPI kernel" i have no idea what it is but just emailed Pillar1989 asking if he can come back to us and he provided this enigmatic short answer from the Raspberry pi foundation web site: He also just wrote this: "then "ls /dev/i2c-1", check the i2c interface works. then restart seeed-voicecard service(sudo systemctl restart seeed-voicecard)" |
@jabulonboaz You are awesome. That fixed it. You have to enable enable SPI and I2C in interfacing options using raspi-config. Thank you so much. For others, who are facing similar problem, please try this.
then install seeed-voicecard and reboot. Additionally you might have to do this sudo systemctl restart seeed-voicecard |
It was @Pillar1989 that provided it so thanks to him. I am happy yours is working too now and we have a way to reproduce it @cogmeta. |
@jabulonboaz Surely, we will help you with that. We have 10 more such devices to install and check and then I will get back to you with solution for the LED. We owe you one :) Thanks a lot |
Do not enable SPI @congmeta i just did to try play with the LEDs but it rigs AlexaPi and will just say yes but no answer |
Help anyone please ? Even if i restore my build from a clone i build of my SD card when it was working i have the same behaviour. Alexa says hello at boot and responds with hello when u talk to her but does not respond further with an answer. Something to do with these SPI settings? |
AlexaPi stoped working after i enabled SPI then i disable it again but nothing.
Alexa says hello at boot and recognises the hot word when i say alexa she comes back with hello but never responds further to any questions.
Please help.
Sent from Blue<http://www.bluemail.me/r?b=11998>
On 11 Feb 2018, at 14:01, Cogmeta <[email protected]<mailto:[email protected]>> wrote:
Folks, in addition you
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#30 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AczgGh_7vmdkvGTIYgc_TVofiXVgE90Iks5tTvLHgaJpZM4SAEHv>.
|
@jabulonboaz we are actually building our own assistant like Alexa so we are not really testing Alexa or google home. But, yes I was able to install the seeed voice card successfully and both mic and audio jack are working fine. |
I think for your case problem is more likely with Alexa itself, most likely network issue. SPI settings should not affect it. Can you do both aplay and arecord tests to check if the card is installed properly. |
Happy to test it too when u guys are ready |
can you do following tests to see if audio input and output are working fine $arecord --format=S16_LE --duration=5 --rate=16000 --file-type=raw out.raw You should be able to record and hear back your voice if both both audio in and out are working fine. |
pi@raspberrypi:~ $ sudo arecord -f S16_LE -r 16000 -D your_input_device test.wav alsa-info.sh 100%[=====================================>] 27.22K --.-KB/s in 0.02s 2018-02-11 17:01:07 (1.26 MB/s) - ‘alsa-info.sh’ saved [27872/27872] ALSA Information Script v 0.4.64This script visits the following commands/files to collect diagnostic dmesg See 'alsa-info.sh --help' for command line options. cat: '/sys/module/snd_soc_simple_card/parameters/*': No such file or directory Your ALSA information is located at http://www.alsa-project.org/db/?f=b74386dedb4be67b75c6bbdf4674c8939b 4958d1 |
Feb 11 16:55:50 raspberrypi python[466]: INFO: AVS token: Requesting a new one |
these are my logs help anyone pls? |
Feb 11 17:17:38 raspberrypi python[470]: ALSA lib pcm_dmix.c:990:(snd_pcm_dmix_open) The dmix plugin supports only playback stream |
I rebuild-ed everything from scratch over and over, the sound card installed and works fine, Alexa listens and response with yes but never continues to replay to the question i asked. Feb 11 19:30:17 raspberrypi python[474]: INFO: Checking Internet Connection ... |
I have also raised an issue at the AlexaPi git: |
http://www.alsa-project.org/db/?f=1bfc46ac5afe839401bc592ecf43f70c3b25e93c detailed audio debug logs here @Pillar1989 |
pi@raspberrypi:~ $ sudo journalctl -u AlexaPi |
I am using the currently latest version of Raspbian Lite (2017-11-29), and I came across the same problem after installing seeed-voicecard. I solved it by installing the i2c-tools package and restarting the voicecard service as follows: |
@hexbioc thank you! I was missing that part with the i2c-tools |
(b462e8a) I'm sorry for this issue. I have updated install scripts. |
Thanks! This worked for me, but the key thing is that you have to reboot multiple times! Reboot after enabling SPI and I2C, uninstall seed-voicecard then reboot, install seeed-voicecard then reboot. |
Again @Pillar1989 like i mentioned to you in different streams thank you for trying but the new build command does not build anything.
pi@raspberrypi:~ $ arecord -f cd | aplay
arecord: main:788: audio open error: No such file or directory
aplay: playback:2787: read error
pi@raspberrypi:~ $
I followed your new guide to the letter:
"git clone https://github.com/respeaker/seeed-voicecard -b install
cd seeed-voicecard/
pi@raspberrypi:~/seeed-voicecard $ sudo ./install.sh "
pi@raspberrypi:~ $ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: ALSA [bcm2835 ALSA], device 0: bcm2835 ALSA [bcm2835 ALSA]
Subdevices: 8/8
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3
Subdevice #4: subdevice #4
Subdevice #5: subdevice #5
Subdevice #6: subdevice #6
Subdevice #7: subdevice #7
card 0: ALSA [bcm2835 ALSA], device 1: bcm2835 ALSA [bcm2835 IEC958/HDMI]
Subdevices: 1/1
Subdevice #0: subdevice #0
is this suppose to run on Raspbian stretch with desktop only? I m on Raspbian Jessie lite. DO i need to install a specific version of python maybe?
The install only gets instaled when i execute git clone https://github.com/respeaker/seeed-voicecard.git
with ".git" at the end but then i run into all the other problems i described in the other posts.
The text was updated successfully, but these errors were encountered: