Assuming the RuneAudio is using the "standard" Archlinux release for BBB, I think you just need to search for
"ArchLinuxARM-am33x"
which will find results such as this -
https://github.com/archlinuxarm/PKGBUILDs/blob/master/core/linux-am33x/PKGBUILD
And I think the kernel source is here -
Index of /pub/archlinuxarm/armv7h/core/
linux-am33x-3.12.8-1-armv7h.pkg.tar.xz
"ArchLinuxARM-am33x"
which will find results such as this -
https://github.com/archlinuxarm/PKGBUILDs/blob/master/core/linux-am33x/PKGBUILD
And I think the kernel source is here -
Index of /pub/archlinuxarm/armv7h/core/
linux-am33x-3.12.8-1-armv7h.pkg.tar.xz
Pre-compiled modules for Arch Linux ARM has been added.
http://bbb.ieero.com/
Notice #1: I'm not going to add more distributions.
Notice #2: It's still early driver with debug messages enabled. Please test it!
http://bbb.ieero.com/
Notice #1: I'm not going to add more distributions.
Notice #2: It's still early driver with debug messages enabled. Please test it!
@ Miero: thanks for your work-
@ glt, thanks for your very useful articles, especially for layman people like me.
@ glt, thanks for your very useful articles, especially for layman people like me.
Miero, away from home at the moment but will test in a couple of days.
Assuming will need to test with 48k file, what will the driver do with a 41k file?
I am a bit lost in this development. I'll have my BBB in two months, so I have to stick with the Rasberry Pi for the time being. I am enjoying it, using both the I2S and I2C to control the DAC. If there is interest I can share the results (that are kind of trivial) here or in a dedicated thread. What I am trying to do is to modify volumio to make it use I2C to control the volume. Now I manage to do it only with command line. Help is also appreciated.
Does the driver developed for BBB do the same ?
What's the final goal of the whole development ?
Thanks,
D.
Does the driver developed for BBB do the same ?
What's the final goal of the whole development ?
Thanks,
D.
The driver from Miero enables i2s on the BBB board for the 3 indicated OSes. In addition It supports the yet unavailable "clock cape" that is needed to support the 44.1k family and low jitter clocks.
Goals:
- full support for TPA I2S cape
- add DSD
- BBB also as USB DAC for PC
- I2C control of Buffalo
- full support for TPA I2S cape
- add DSD
- BBB also as USB DAC for PC
- I2C control of Buffalo
I don't want to distort the discussion or get into a support discussion, but I have failed to get Miero's I2S driver working with my BBB> I dropped the current Debian Wheezy onto an SD card, followed Miero's instructions but APLAY -l finds no DAC hardware.
The process seems to work fine, just the outcome fails to yield the required result.
I tried twice, reformatting the card. I had to add Alsa to get Aplay -l to run at all.
It is probably me being a Linux thicky, just thought the feedback might help.
I tried loading it on top of Volumio also (which uses Debian as a base), without positive results.
The process seems to work fine, just the outcome fails to yield the required result.
I tried twice, reformatting the card. I had to add Alsa to get Aplay -l to run at all.
It is probably me being a Linux thicky, just thought the feedback might help.
I tried loading it on top of Volumio also (which uses Debian as a base), without positive results.
Goto, please send me in PM following info:
- output of "uname -a" command
- last 10-20 lines of output of "dmesg" command executed right after the "echo BB-BONE-BOTIC1 > ..."
- output of "uname -a" command
- last 10-20 lines of output of "dmesg" command executed right after the "echo BB-BONE-BOTIC1 > ..."
Here is a very early preview if the "Botic" cape. The Botic is a creek in Prague. The name is a tribute to the work Miero has done on the driver for the project. I liked the name - so it is sticking. 🙂
Some feature will be (not all populated on the layout yet)
1) Buffered PCM/DSD out (DSD will take some driver work) The buffer protects the BBB from accidental overloading of the outputs.
2) I2C out
3) Dual ultra low jitter clocks with outputs for DACs which need them.
4) Optional external power.
5) On board linear reg for the clock/mux/buffers.
6) ADC and/or Rotary encoder input to control volume externally.
7) I2C display could also be used.
Some feature will be (not all populated on the layout yet)
1) Buffered PCM/DSD out (DSD will take some driver work) The buffer protects the BBB from accidental overloading of the outputs.
2) I2C out
3) Dual ultra low jitter clocks with outputs for DACs which need them.
4) Optional external power.
5) On board linear reg for the clock/mux/buffers.
6) ADC and/or Rotary encoder input to control volume externally.
7) I2C display could also be used.
Attachments
russ, any chance we could have a dac onboard, such as the es90023 for simple lower cost integrated music server? Could be optional and I believe there is a large demand for such a product. It would be great for the secondary system, bedroom, etc.
Thanks! There is still some work to be done on it.
I forgot to add that we should also be able to support up to 8 channel output. Disregard the number of uFL connectors, as there will be more. 🙂 Also headers too.
I think I may do a seperate cape for those wanting a simple but high quality DAC. ES9023 would indeed be a solid choice.
I will mull it over.
I forgot to add that we should also be able to support up to 8 channel output. Disregard the number of uFL connectors, as there will be more. 🙂 Also headers too.
I think I may do a seperate cape for those wanting a simple but high quality DAC. ES9023 would indeed be a solid choice.
I will mull it over.
Simple Cape
Hi Russ,
My preference would be for a simple cape as you have already described. Adding an on-board DAC seems like another direction (although it would be useful). My own needs are for extracting I2S signals out of my BBB and feeding them directly into my TPA BII.
Currently I am using a BBB with USB output feeding my TPA USB receiver, into my BII. Fantastic sound. Substituting the BBB for my mac removed most (but not all) of the drop-outs. I measured the signals from #P9-28 -29 and -30 with my scope and did not find square waves. But my BBB is configured according to Chris Connaker's instructions on ComputerAudiophile's website.
I've been following this thread with keen interest and want to thank the members for their valuable contributions. I am looking forward to the Botic.
- David
Hi Russ,
My preference would be for a simple cape as you have already described. Adding an on-board DAC seems like another direction (although it would be useful). My own needs are for extracting I2S signals out of my BBB and feeding them directly into my TPA BII.
Currently I am using a BBB with USB output feeding my TPA USB receiver, into my BII. Fantastic sound. Substituting the BBB for my mac removed most (but not all) of the drop-outs. I measured the signals from #P9-28 -29 and -30 with my scope and did not find square waves. But my BBB is configured according to Chris Connaker's instructions on ComputerAudiophile's website.
I've been following this thread with keen interest and want to thank the members for their valuable contributions. I am looking forward to the Botic.
- David
Excitement builds!
Wow! And my BBB is scheduled to arrive tomorrow. Very exciting, and I know premature for questions, but:
1. Would this then allow for synchronous link with BIIIse?
2. Seems like having clean power at both BBB and the Botic will be great- is ground isolation an issue? (Using two supplies, should a common ground be used to avoid loops?)
Have been using my BIIIse into my amp direct the past few weeks and tweaking Audirvana filter settings, the SQ just keeps getting better and better. The Botic/buffalo will be anxiously awaited!
Thanks again for your energy and collective talents in making this happen.
Wow! And my BBB is scheduled to arrive tomorrow. Very exciting, and I know premature for questions, but:
1. Would this then allow for synchronous link with BIIIse?
2. Seems like having clean power at both BBB and the Botic will be great- is ground isolation an issue? (Using two supplies, should a common ground be used to avoid loops?)
Have been using my BIIIse into my amp direct the past few weeks and tweaking Audirvana filter settings, the SQ just keeps getting better and better. The Botic/buffalo will be anxiously awaited!
Thanks again for your energy and collective talents in making this happen.
My vote is for a simple board much as Russ has shared. DACs or SPDIF can be off board. Only thing is I would prefer a header for I2S out rather than U.FL or possibly both.
Great work guys.
Great work guys.
Russ,
How about pads for an I2S-out header to allow easy connection of a Teleporter? That could also be the point for adding a Q&D ES9023-DAC card!
Greg in Mississippi
How about pads for an I2S-out header to allow easy connection of a Teleporter? That could also be the point for adding a Q&D ES9023-DAC card!
Greg in Mississippi
Vote #2. If the I2S outputs were only to be provided from the Botic cape as U.FL connectors, wiring 3 u.FL cables to a (nearby) teleporter would be somewhat kludgey. A pin-compatible header for the Teleporter would be great.
Pin headers will definitely be included - I always planned to make it easy to use the teleporter - especially for stereo use. 🙂