• Disclaimer: This Vendor's Forum is a paid-for commercial area. Unlike the rest of diyAudio, the Vendor has complete control of what may or may not be posted in this forum. If you wish to discuss technical matters outside the bounds of what is permitted by the Vendor, please use the non-commercial areas of diyAudio to do so.

Support for Botic Linux driver

First of all, playing DSD512 on MPD requires a big endian format like DSD_U32_BE. However the debian system on BBB only support a DSD format of little endian type like DSD_U32_LE, which can not play the DSD source higher than DSD256. So, using MPD on botic BBB for the purpose of playing DSD512 can be said almost impossible.
...

Thank you for taking the time to clarify all that Twluke. It saved a lot of time and and prevented a lot of frustration trying to achieve the impossible (at least as things stand now).

I’ll keep an eye on Coroner21’s progress (I would only wish that I could have something to contribute).
 
I’ll keep an eye on Coroner21’s progress (I would only wish that I could have something to contribute).

No worries, it has all been done already... In general DSD512 should work just fine using the code in my github repository, however unfortunately MPD currently has an issue with DSD on ARM architecture, see also DSD on ARM is broken * Issue #469 * MusicPlayerDaemon/MPD * GitHub.

Therefore I have currently disabled 32 bit wide DSD processing per default. I only have some DSD64 files and do not really care too much about it. If you want to test it with another player, you are welcome to try and I can help setting it up.
 
First of all, playing DSD512 on MPD requires a big endian format like DSD_U32_BE. However the debian system on BBB only support a DSD format of little endian type like DSD_U32_LE, which can not play the DSD source higher than DSD256. So, using MPD on botic BBB for the purpose of playing DSD512 can be said almost impossible.

twluke, could you elaborate on the background of this? From my understanding DSD_U32_LE or DSD_U32_BE should be technically fully equivalent and since ARM is actually a little endian architecture I would even expect that DSD_U32_LE would be the right way to go? Why should there be a problem playing back DSD on MPD in case DSD_U32_LE is used?
 
twluke, could you elaborate on the background of this? From my understanding DSD_U32_LE or DSD_U32_BE should be technically fully equivalent and since ARM is actually a little endian architecture I would even expect that DSD_U32_LE would be the right way to go? Why should there be a problem playing back DSD on MPD in case DSD_U32_LE is used?
Good question. This BE/LE issue on MPD can be well explained by the URL below, that was posted by @linweaker, a leading expert in the field of native DSD on MPD on Jun 21, 2016.

Amanero card now supporting DSD native * Issue #12 * lintweaker/xmos-native-dsd * GitHub

You might want to continue to read that thread further more, focusing on the critical comments on this MPD issue from @jlaako, the author of HQ player. Finally you'll find that how and why Domenico, the author of Amanero firmware, has been hardly struggling with this issue to achieve native DSD support for DSD512 on Amanero. It's MPD, right or wrong, causing this sample format issue for native DSD512.

Regards,
 
Last edited:
For the lazy or not so linux-savy users I have uploaded one complete image: 2019-01-06_nhz6wnwr | Files.fm.

After download verify following sha256 checksum before proceeding:
Code:
5a808d79d3450dcaa4674937bed0b31d57316794efa7b066d857db8cd0104890

To write it to the sdcard (min. 4GB required) issue
Code:
xzcat botic.img.xz | dd of=/dev/mmcblkX

The file is down. any chance to reup please.

Branko
 
Unfortunately I cannot find it anymore and most probably deleted it. When I find some time I can try to re-generate another image based on the latest versions.

In the meantime I can only recommend you to try the Arch install yourself and compile the kernel image based on instructions provided on the GitHub repository: GitHub - coroner21/linux-am33xbot: Arch Linux ARM Kernel with botic patches

It should not be that complicated... :)
 
Unfortunately I cannot find it anymore and most probably deleted it. When I find some time I can try to re-generate another image based on the latest versions.

In the meantime I can only recommend you to try the Arch install yourself and compile the kernel image based on instructions provided on the GitHub repository: GitHub - coroner21/linux-am33xbot: Arch Linux ARM Kernel with botic patches

It should not be that complicated... :)

Thank you,

will try. But have never done before.
 
Is there a way to use the bbb with botic (Hermes, Cronus) to play my Apple Music (AirPlay) ?
I don't believe there is a native application for Linux which can directly access Apple Music ...
but you should be able to stream Apple Music from an iPhone or iPad to your BeagleBone Black, by installing shairport-sync

How to install shairport-sync? Sorry, I can only speculate with my limited knowledge of Linux - there's a pre-compiled binary for Debian Stretch here -
Debian -- Package Download Selection -- shairport-sync_2.8.6-1_armhf.deb
but Botic4 is based on Debian Wheezy, so I'm not sure if this deb file will be compatible.
You might need to compile shairport-sync from source.
You may need to ask the experts here, such as twluke.
 
Success!

Now can use Roon for my local music over BBB-->Hermes-->Cronus.
And as long as Apple Music is not supported by Roon can stream Apple music via Shairport-sync to BBB.

Installation was straight in Debian stretch:
"# apt-get install shairport-sync"
Installed also all dependencies itself.
"# systemctl enable shairport-sync"
"# systemctl start shairport-sync"
After reboot everything worked out fine :))
 
Hello to everyone.
I’m new to the BBB/Hermes/Cronus. And I have no much experience to it. Just started to learn and do some homework. With it I had a lot of help from fancolargo and wlowes. (thanks guys!)
I ask you for a lot of patience :)
I start to understand the idea and how it works. I have updated my botic and made it to the eMMc sucsessfuly. In that stage I’m very proud of me :)
I’m user of dddac1794 and JRiver. For now all my files are stored on my home theatre PC.
I rather imagine my BBB to work as a uPnP/DLNA that supports up to 24bits and 192kHz for my JRiver.
I was trying to install squeezlite from this site: Botic HOWTOs for driver & tools - Google Docs
But i have got a bunch of 404 error entries, unable to locate packages, and command not found. Maybe link to the servers are outdated. I don’t know.
Colud you help me out and give me some advices on what choices do I have to get this done? Is there any other solution than squeezlite?
I saw a nice software called CA-NetAudio that does just that. Streams anything to BBB with hi resolution. It is just UPnP client and sends everything nicely form JRiver to BBB. But does not have botic drivers for our precious cape boards.
Is there a way to install it onto our botic? Or othervice, is there a way to install botic driver onto exising lets say CA-NetAudio?
I saw you are much experienced botic experts so maybe you could propose me something that works well and does not have to be free but simple and specialised with UPnP or DLNA for a PC?

Best regards.
 
Last edited:
4.5.0-botic7-rc1
Should I update to 4.8? And without MPD?

Thanks
Yes, you should. You can install MPD later. Also, please let me know whether the distro of your debian is stretch or not by 'lsb_release -a'.

If so, after installing botic 4.8, do this:

apt-get update
apt-get upgrade

After that, you can install squeezelite.

apt-get install squeezelite

If you want to have MPD, too, you can also install MPD. Both apps can be used by switching.

Also, as you have a Windows server for data storage, please confirm that you have cifs-utils installed. If not, download it:

apt-get install cifs-utils

And also, did you check your /etc/fstab?

You can cifs-mount the remote sever by editing /etc/fstab. Sample files will be found by googling.

Please let me the results later.

Regards,
 
Just look into the /boot/uEnv.txt of your SD card, at the bottom of which you'll find the line like below:

#cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh

Just comment out this line and then boot from this SD card. After that the card will flash the eMMC and the contents of the SD card will be all copied to it. This way, you can always boot from the on-board eMMC.

Regards,

Thank you. for your advices twluke

I'm on. But there is a problem. I have installed a new botic as fred_com presented in post #2471. Also using that debian link for Debian 9.3.
Then before I started to proceed to the rest of the instalations that you asked me to do I wanted to place botic on eMMC using your guide quoted above.
After taking out the comment from #cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh I rebooted. System started copying process. After removing SD and booting I had all four leds lit and nothing else was happening. I tried to boot back from SD card but instead system started to copy os to the eMMC again.
And this process repeats itself all over again.
For the first time i thought that I screw sometnig up while installing botic. But after clean reinstalling everything it is happening again. I clean installed the botic twice.

What can I do?
 
-snip-
After removing SD and booting I had all four leds lit and nothing else was happening.-snip-
What can I do?

Recently I found the cause of this problem and posted it in #2674.

Probably there will be two methods to solve this inconvenience:
The first one is to edit the /boot/uEnv.txt of the newly created SD card before going to eMMC flash.

The second one is to edit the /boot/uEnv.txt of the system in the flashed eMMC by booting from SD card and mounting the eMMC in /mnt or other your preferred directory.

The goal is almost there. I hope both methods will work for you!

Regards,