Hardware not recognised

Moderator: flatmax

Post Reply
leonuys
Posts: 2
Joined: Mon Oct 24, 2016 11:37 pm

Hardware not recognised

Post by leonuys » Mon Oct 24, 2016 11:47 pm

This may be my own fingers getting in the way, but I have 3x Audio Injector cards, and a RasPi 3 and a RasPi 2Bv2. I get very similar results and swopping out cards makes no difference. Here is a snippet from my DMESG:

[ 5.372224] audioinjector-audio soc:sound: ASoC: CODEC DAI wm8731-hifi not registered
[ 5.372252] audioinjector-audio soc:sound: snd_soc_register_card failed (-517)
[ 5.512929] wm8731 1-001a: Assuming static MCLK
[ 5.513710] wm8731 1-001a: Failed to issue reset: -5
[ 5.513821] wm8731: probe of 1-001a failed with error -5
[ 5.526488] audioinjector-audio soc:sound: ASoC: CODEC DAI wm8731-hifi not registered
[ 5.526515] audioinjector-audio soc:sound: snd_soc_register_card failed (-517)
[ 5.533690] audioinjector-audio soc:sound: ASoC: CODEC DAI wm8731-hifi not registered
[ 5.533697] usbcore: registered new interface driver brcmfmac
[ 5.533726] audioinjector-audio soc:sound: snd_soc_register_card failed (-517)
[ 5.652894] random: nonblocking pool is initialized
[ 5.680538] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: May 27 2016 00:13:38 version 7.45.41.26 (r640327) FWID 01-df77e4a7
[ 5.710891] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code
[ 5.730225] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code

Can somebody point me in a direction where I can look please?
Leon Uys

flatmax
Posts: 609
Joined: Sat Jul 23, 2016 11:39 pm

Re: Hardware not recognised

Post by flatmax » Wed Oct 26, 2016 6:12 pm

Hi there,

I would like to help you solve this problem.

Below [1] is an example of a successful startup. IT should fail around 4 times and then succeed ... can you please confirm that this doesn't happen on your system.
Now the good news is that your device tree is loading properly.

Can you please tell me how you installed your software to support the Audio injector ?

Did you try to use the scripts provided on this forum ? If not is it possible to start with a clean SDCARD with the latest Rasbian image fresh install and run the automated installation process.

Otherwise I am still happy to help you, however it would be nice to see if we can get a working version with one of your Pis before we proceed.


thanks
Matt
[1] An example output from dmesg on successful startup.
[ 8.211314] audioinjector-audio soc:sound: ASoC: CPU DAI (null) not registered
[ 8.211339] audioinjector-audio soc:sound: snd_soc_register_card failed (-517)
[ 8.213179] audioinjector-audio soc:sound: ASoC: CODEC DAI wm8731-hifi not registered
[ 8.213206] audioinjector-audio soc:sound: snd_soc_register_card failed (-517)
[ 8.354007] audioinjector-audio soc:sound: ASoC: CODEC DAI wm8731-hifi not registered
[ 8.354032] audioinjector-audio soc:sound: snd_soc_register_card failed (-517)
[ 8.361066] usbcore: registered new interface driver brcmfmac
[ 8.364969] audioinjector-audio soc:sound: ASoC: CODEC DAI wm8731-hifi not registered
[ 8.364996] audioinjector-audio soc:sound: snd_soc_register_card failed (-517)
[ 8.475933] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[ 8.506091] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: May 27 2016 00:13:38 version 7.45.41.26 (r640327) FWID 01-df77e4a7
[ 8.534765] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code
[ 8.539510] wm8731 1-001a: Assuming static MCLK
[ 8.553331] audioinjector-audio soc:sound: wm8731-hifi <-> 3f203000.i2s mapping ok
Check out our audiophile quality crossovers : https://bit.ly/2kb1nzZ
Please review the Zero sound card on Amazon USA : https://www.amazon.com/dp/B075V1VNDD
---
Check out our new forum on github : https://github.com/Audio-Injector

leonuys
Posts: 2
Joined: Mon Oct 24, 2016 11:37 pm

Re: Hardware not recognised

Post by leonuys » Fri Oct 28, 2016 8:18 pm

Thanks Matt. Apologies for the long reply, but I decided to do a systematic investigation to locate the problem, and I'm using alternative hardwares to eliminate problem areas by duplicating some components with known working parts, e.g. power supplies.
Hardware: 3x Audio Injector cards ordered from eBay (all give same results)
SD Cards: (i) 8Gb SanDisk Ultra (10) (ii) 8Gb generic (4) (iii) 16Gb SanDisk Ultra (10)
Power supply two x adaptors (2A/1.5A) two x cables measured with in-line USB meter ~0.2-0.3A at 5.11v (“borrowed” from working Weather Station)
Two RasPi’s 2 B+ V1.2 and 3
Software: Jessie, latest available Oct 2016: 2016-09-23-raspbian-jessie.img
Procedure:
With RasPi3, no A-I card, 16G SD card:
1. Insert newly burnt SD card, power-on, message “resizing”, continues booting to desktop (takes long?)
2. Start - Preferences - RasPi Configuration - System - Expand Filesystem - reboot (a little faster this time)
3. Connect to home WiFi
4. Start - Preferences - RasPi Configuration - Localisation - Set Keyboard (US International) - (test) -reboot
5. Start - Preferences - RasPi Configuration - Localisation - Set Timezone - Africa Johannesburg -reboot
6. (not changing WiFi country yet, has no immediate impact)
7. Start - Preferences - RasPi Configuration - Interfaces - shows SPI and I2C disabled, might have to revisit
8. Start - Preferences - Audio Device Settings - shows bcm2835 (ALSA Mixer)
9. At this time, no strange or error messages in dmesg. A copy is saved.
9.1 diversion sudo apt-get doing some updates , is upgrade necessary?
9.2 Is it necessary to do the A-I tree setup first?
10. Powerdown; insert Audio Injector; Powerup
11. Same messages in dmesg, and ALSA still pointing to on-board device
12. (interesting: I didn’t install chromium, but it was there, nice!) goto flatmax.org/phpbb and download audio.injector.scripts_0.1-1_all.deb and run setup (asking for password) no messages
13. Reboot, dmesg 2, then run install script (is sudo required?) audioInjector-setup.sh (bumps to rpi-4.4.y linux tree warning which might have some issues, then downloads about 51Mb firmware revision, no reported errors)
14. Reboot, dmesg 3, errors.
14.1 When checking configuration it says: No ALSA audio devices were detected. Enable the internal audio device, or connect a USB or HAT audio device.
15. Go for broke, update and upgrade, selects about 72 files / 20Mb. Takes a while, lots of disk i/o.
15.1 Gives info message about /etc/sudoers.d/010_pi-nopasswd file.
15.2 lightdm.conf “Y” to install new version
15.3 at some point change smb workgroup to save copies of files on server
16. Reboot, dmesg 4, errors. (oops deleted by accident)
17. Go back to config and enable SPI/I2C,
18. Reboot, dmesg 5, still having errors, and error message when checking No ALSA audio devices were detected. Enable the internal audio device, or connect a USB or HAT audio device.
19. ?

My best guess is that things go belly-up around step 13, but I am unable to see why. I do not get the dmesg message audioinjector-audio soc:sound: wm8731-hifi <-> 3f203000.i2s mapping ok

What would be the best thing to do next?

Thank you.
Leon
Attachments
RPi_AudioInjector_Logs.zip
Progressive versions of dmesg as installation progressed
(32.93 KiB) Downloaded 78 times

flatmax
Posts: 609
Joined: Sat Jul 23, 2016 11:39 pm

Re: Hardware not recognised

Post by flatmax » Sun Oct 30, 2016 7:17 pm

Hey there,

Here is the short summary. I followed your steps exactly.... with the exception of step 9.1 where I do a full update, however I don't think this would make a difference.
After step 14, your sound card should be installed and working. I have attached my output from
dmesg.post.step.14.txt.zip
dmesg post step 14
(8.17 KiB) Downloaded 93 times
I am going to contact you off forum to find a replacement or refund solution which you will be happy with. Thank you for posting your steps.

For the long version ...
I am following your steps ...

1. Insert newly burnt SD card, power-on, message “resizing”, continues booting to desktop (takes long?)
I downloaded 2016-09-23-raspbian-jessie.zip
2. Start - Preferences - RasPi Configuration - System - Expand Filesystem - reboot (a little faster this time)
3. Connect to home WiFi
Pi2 for this test, no wifi, so I used an RJ45 cable.
4. Start - Preferences - RasPi Configuration - Localisation - Set Keyboard (US International) - (test) -reboot
5. Start - Preferences - RasPi Configuration - Localisation - Set Timezone - Africa Johannesburg -reboot
Hello Africa, I have joined your timezone.
6. (not changing WiFi country yet, has no immediate impact)
7. Start - Preferences - RasPi Configuration - Interfaces - shows SPI and I2C disabled, might have to revisit
8. Start - Preferences - Audio Device Settings - shows bcm2835 (ALSA Mixer)
9. At this time, no strange or error messages in dmesg. A copy is saved.
9.1 diversion sudo apt-get doing some updates , is upgrade necessary?
I don't think it is necessary. I rant "sudo apt-get update" then "sudo apt-get upgrade"
9.2 Is it necessary to do the A-I tree setup first?
Nope ... the script run below will do this for you.
10. Powerdown; insert Audio Injector; Powerup
11. Same messages in dmesg, and ALSA still pointing to on-board device
12. (interesting: I didn’t install chromium, but it was there, nice!) goto flatmax.org/phpbb and download audio.injector.scripts_0.1-1_all.deb and run setup (asking for password) no messages
13. Reboot, dmesg 2, then run install script (is sudo required?) audioInjector-setup.sh (bumps to rpi-4.4.y linux tree warning which might have some issues, then downloads about 51Mb firmware revision, no reported errors)
14. Reboot, dmesg 3, errors.
At this point, the audio injector will be working - not in your case.
I stopped at this point.
14.1 When checking configuration it says: No ALSA audio devices were detected. Enable the internal audio device, or connect a USB or HAT audio device.
15. Go for broke, update and upgrade, selects about 72 files / 20Mb. Takes a while, lots of disk i/o.
15.1 Gives info message about /etc/sudoers.d/010_pi-nopasswd file.
15.2 lightdm.conf “Y” to install new version
15.3 at some point change smb workgroup to save copies of files on server
16. Reboot, dmesg 4, errors. (oops deleted by accident)
17. Go back to config and enable SPI/I2C,
18. Reboot, dmesg 5, still having errors, and error message when checking No ALSA audio devices were detected. Enable the internal audio device, or connect a USB or HAT audio device.
19. ?
Check out our audiophile quality crossovers : https://bit.ly/2kb1nzZ
Please review the Zero sound card on Amazon USA : https://www.amazon.com/dp/B075V1VNDD
---
Check out our new forum on github : https://github.com/Audio-Injector

stooby
Posts: 6
Joined: Wed Jan 25, 2017 6:49 pm
Location: California

Re: Hardware not recognised

Post by stooby » Sat Jan 28, 2017 4:54 am

Interesting info about what to look for in the dmesg log to confirm whether or not the AudioInjector is setup correcrtly. I'm having a similar difficulty getting my AudioInjector to work with a Raspi 3 and jackd. My dmesg log does appear to show the messages indicating it's been setup successfully...(excerpt):

Code: Select all

[    5.082847] audioinjector-audio soc:sound: ASoC: CPU DAI (null) not registered
[    5.082874] audioinjector-audio soc:sound: snd_soc_register_card failed (-517)
[    5.085375] audioinjector-audio soc:sound: ASoC: CODEC DAI wm8731-hifi not registered
[    5.085403] audioinjector-audio soc:sound: snd_soc_register_card failed (-517)
[    5.191872] wm8731 1-001a: Assuming static MCLK
[    5.199535] audioinjector-audio soc:sound: wm8731-hifi <-> 3f203000.i2s mapping ok
[    5.202015] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[    5.219936] usbcore: registered new interface driver brcmfmac
[    5.371163] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: May 27 2016 00:13:38 version 7.45.41.26 (r640327) FWID 01-df77e4a7
[    5.381335] random: nonblocking pool is initialized
[    5.404739] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code
[    5.528751] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code
However, I also get these messages at the end of my dmesg log:

Code: Select all

[   15.247680] bcm2835-i2s 3f203000.i2s: I2S SYNC error!
[   15.316710] bcm2835-i2s 3f203000.i2s: I2S SYNC error!
[   15.347683] bcm2835-i2s 3f203000.i2s: I2S SYNC error!
[   15.355656] bcm2835-i2s 3f203000.i2s: I2S SYNC error!
[   16.247528] bcm2835-dma 3f007000.dma: DMA transfer could not be terminated
[   16.250734] bcm2835-dma 3f007000.dma: DMA transfer could not be terminated
[  712.825543] bcm2835-i2s 3f203000.i2s: I2S SYNC error!
[  712.828145] bcm2835-i2s 3f203000.i2s: I2S SYNC error!
[  744.834102] bcm2835-dma 3f007000.dma: DMA transfer could not be terminated
[  744.836332] bcm2835-dma 3f007000.dma: DMA transfer could not be terminated
[ 1035.051222] bcm2835-i2s 3f203000.i2s: I2S SYNC error!
[ 1035.054734] bcm2835-i2s 3f203000.i2s: I2S SYNC error!
[ 1067.062714] bcm2835-dma 3f007000.dma: DMA transfer could not be terminated
[ 1067.063996] bcm2835-dma 3f007000.dma: DMA transfer could not be terminated
[ 1271.300710] bcm2835-i2s 3f203000.i2s: I2S SYNC error!
[ 1271.303291] bcm2835-i2s 3f203000.i2s: I2S SYNC error!
[ 1303.307895] bcm2835-dma 3f007000.dma: DMA transfer could not be terminated
[ 1303.309535] bcm2835-dma 3f007000.dma: DMA transfer could not be terminated
[ 1400.549605] bcm2835-i2s 3f203000.i2s: I2S SYNC error!
[ 1400.552969] bcm2835-i2s 3f203000.i2s: I2S SYNC error!
[ 1432.557247] bcm2835-dma 3f007000.dma: DMA transfer could not be terminated
[ 1432.558060] bcm2835-dma 3f007000.dma: DMA transfer could not be terminated
[ 1467.060488] bcm2835-i2s 3f203000.i2s: I2S SYNC error!
[ 1467.063314] bcm2835-i2s 3f203000.i2s: I2S SYNC error!
[ 1499.070342] bcm2835-dma 3f007000.dma: DMA transfer could not be terminated
[ 1499.071412] bcm2835-dma 3f007000.dma: DMA transfer could not be terminated
[ 1507.889024] bcm2835-i2s 3f203000.i2s: I2S SYNC error!
[ 1507.893362] bcm2835-i2s 3f203000.i2s: I2S SYNC error!
[ 1535.635887] bcm2835-dma 3f007000.dma: DMA transfer could not be terminated
[ 1535.636674] bcm2835-dma 3f007000.dma: DMA transfer could not be terminated
This log was made during a boot after I had enabled the i2s and i2c interfaces by uncommenting them in the /boot/config.txt file. I noticed that these are disabled (commented out) by default, but assumed that the AudioInjector would need these enabled to function. It doesn't work with my jackd though, so I also tested w/ the i2s and i2c interfaces disabled (commented out in the /boot/config.txt), but still get the same result.

Additionally, after following the setup procedure outlined in the forum (I did the automated install using the .deb package and setup script), I get the following error message:

Code: Select all

pi@sm_rpi:~ $ alsactl --file /usr/share/doc/audioInjector/asound.state.RCA.thru.test restore
pi@sm_rpi:~ $ audioInjector-test.sh
couldn't find the sox command please install the sox pacakge
I can post additional info about the error logs I get from jackd, but thought I'd share an initial description of the issues I'm encountering first. Thank you for your help!

Post Reply

Who is online

Users browsing this forum: No registered users and 3 guests