The software divider is already applied according to the clk_44k1 and clk_48k parameters. So IMHO it has to be solved in HW.
For example Hermes-BBB board does have MCLK divider for /1, /2 and /4.
Yes this is precisely the reason the Cronus/Hermes-BBB solution employs a divider. 🙂
Yes this is precisely the reason the Cronus/Hermes-BBB solution employs a divider. 🙂
Thanks for this comment. Then I'll try again this 98.304 clock with this divider on the Cronus board, which is now expected to be just around the corner to my door in a few weeks 🙂.
At this setting - does not work playback MPD always pause
Changed to 16385, playback of files works
If you set 16386 feeling that awaits BBB MCLK, and he is on P9_25
Changed to 16385, playback of files works
If you set 16386 feeling that awaits BBB MCLK, and he is on P9_25
Last edited:
I've marked this to Issue tracker and I'll verify it later.
But it is strange. Please recheck that the same value is printed using following command:
There should be 16386. Not 0x16386 or so...
But it is strange. Please recheck that the same value is printed using following command:
cat /sys/module/snd_soc_botic/parameters/mcasp_format
There should be 16386. Not 0x16386 or so...
config:At this setting - does not work playback MPD always pause
Changed to 16385, playback of files works
If you set 16386 feeling that awaits BBB MCLK, and he is on P9_25
Code:
root@wired-bbb:~# cat /boot/uboot/uEnv.txt|grep snd_soc
[COLOR=RoyalBlue]optargs=coherent_pool=1M snd_soc_botic.ext_masterclk=7 snd_soc_botic.dsd_format_switch=3 snd_soc_botic.serconfig=--MM snd_soc_botic.pinconfig=compat snd_soc_botic.mcasp_format=16386[/COLOR]
root@wired-bbb:~# play -r 96000 -c 2 -n synth sin 1000 vol -3db
[COLOR=Red]play FAIL formats: can't open output file `default': snd_pcm_hw_params error: Invalid argument[/COLOR]
Code:
root@wired-bbb:~# cat /boot/uboot/uEnv.txt|grep snd_soc
[COLOR=RoyalBlue]optargs=coherent_pool=1M snd_soc_botic.ext_masterclk=7 snd_soc_botic.dsd_format_switch=3 snd_soc_botic.serconfig=-S-- snd_soc_botic.pinconfig=compat snd_soc_botic.mcasp_format=16386[/COLOR]
root@wired-bbb:~# play -r 96000 -c 2 -n synth sin 1000 vol -3db
[COLOR=RoyalBlue]
Encoding: n/a
Channels: 2 @ 32-bit
Samplerate: 96000Hz
Replaygain: off
Duration: unknown
In:0.00% 00:00:01.71 [00:00:00.00] Out:164k [-=====|=====-] Hd:3.0 Clip:0[/COLOR]
Last edited:
Need help on flashing Botic, anyone?
🙁 So, I downloaded the bbb-demo-botic-v3-2gb.img.gz file
and ungziped it, copied image to SD card, tried to flash it
to BBB-C. Let it run for over an hour & a half, the BBB LEDS
never stopped blinking. Powered it down, pulled the SD out &
powered back on. No LEDS lit, other than the POWER LED.
😕 Got a copy of "bone-debian-jessie-console-armhf-2015-04-09-2gb.img" version for flashing to the eMMC
and "bone-debian-7.8-lxde-4gb-armhf-2015-03-01-4gb.img" version
for booting from to microSD card.
Flashed the 2015-04-09 image to BBB, same results as Botic flash, no go!😡
Put the 2015-03-01 version in card reader and BBB booted up, from
the SD card!? 😕
How do I get the Botic image to boot from the eMMC!
🙁 So, I downloaded the bbb-demo-botic-v3-2gb.img.gz file
and ungziped it, copied image to SD card, tried to flash it
to BBB-C. Let it run for over an hour & a half, the BBB LEDS
never stopped blinking. Powered it down, pulled the SD out &
powered back on. No LEDS lit, other than the POWER LED.
😕 Got a copy of "bone-debian-jessie-console-armhf-2015-04-09-2gb.img" version for flashing to the eMMC
and "bone-debian-7.8-lxde-4gb-armhf-2015-03-01-4gb.img" version
for booting from to microSD card.
Flashed the 2015-04-09 image to BBB, same results as Botic flash, no go!😡
Put the 2015-03-01 version in card reader and BBB booted up, from
the SD card!? 😕
How do I get the Botic image to boot from the eMMC!
I assume you have read instructions at the end of http://bbb.ieero.com/ page.
Does the flash command report success?
Does the flash command report success?
flashing with an official images
with botic the process coping image to card same, but flashing
(see miero's post above)
with botic the process coping image to card same, but flashing
(see miero's post above)
Flashing
Thank you very much!!!😀
I did not know about the /boot/uEnv.txt file and enabling eMMC Flasher.
Thought I could flash by inserting the SDD image card then hold the
'User Boot' button down and plugging in the power. That's what the
info for BBB on the Adafruit-dot-com says to do. 🙄
So, I changed the uEnv.txt to enable flashing on power up &
it worked!!! 😎 I loaded a version of Debian.
Again, thank you, from an old retired COBOL programmer/analyst.
I did some scripting for IBM/AIX(Unix), it's been 12 years tho.
ICHI 🙂
Thank you very much!!!😀
I did not know about the /boot/uEnv.txt file and enabling eMMC Flasher.
Thought I could flash by inserting the SDD image card then hold the
'User Boot' button down and plugging in the power. That's what the
info for BBB on the Adafruit-dot-com says to do. 🙄
So, I changed the uEnv.txt to enable flashing on power up &
it worked!!! 😎 I loaded a version of Debian.
Again, thank you, from an old retired COBOL programmer/analyst.
I did some scripting for IBM/AIX(Unix), it's been 12 years tho.
ICHI 🙂
flashing with an official images
with botic the process coping image to card same, but flashing
(see miero's post above)
I assume you have read instructions at the end of http://bbb.ieero.com/ page.
Does the flash command report success?
Thank you for the reply! 🙂
Yes, I saw the instructions at the end of the page,
but I really didn't get it.
Is it saying that the eMMC can be flashed when
logged on via Putty?
Is the Botic distribution a complete replacement
of the OS or does it only load new drivers?
Does Botic output the audio data to the USB port also???
Since I'm waiting for delivery of Cronus etc from TP, I'd
like to give a listen via USB from the BBB.
Thank you again for your reply and a BIG thank you
for your work on Botic!
ICHI
Thank you very much!!!😀
I did not know about the /boot/uEnv.txt file and enabling eMMC Flasher.
ICHI 🙂
In /boot/uEnv.txt:
##enable BBB: eMMC Flasher: #cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh is this what you are referring to?
I can not find these lines on the uEnv.txt file on the folder but just the one below
##These are needed to be compliant with Angstrom's 2013.06.20 u-boot.
loadaddr=0x82000000
fdtaddr=0x88000000
rdaddr=0x88080000
initrd_high=0xffffffff
fdt_high=0xffffffff
##These are needed to be compliant with Debian 2014-05-14 u-boot.
loadximage=load mmc 0:2 ${loadaddr} /boot/vmlinuz-${uname_r}
loadxfdt=load mmc 0:2 ${fdtaddr} /boot/dtbs/${uname_r}/${fdtfile}
loadxrd=load mmc 0:2 ${rdaddr} /boot/initrd.img-${uname_r}; setenv rdsize ${filesize}
loaduEnvtxt=load mmc 0:2 ${loadaddr} /boot/uEnv.txt ; env import -t ${loadaddr} ${filesize};
check_dtb=if test -n ${dtb}; then setenv fdtfile ${dtb};fi;
loadall=run loaduEnvtxt; run check_dtb; run loadximage; run loadxrd; run loadxfdt;
mmcargs=setenv bootargs console=tty0 console=${console} ${optargs} ${cape_disable} ${cape_enable} root=/dev/mmcblk0p2 rootfstype=${mmcrootfstype} ${cmdline}
uenvcmd=run loadall; run mmcargs; bootz ${loadaddr} ${rdaddr}:${rdsize} ${fdtaddr};
You're using Angstrom, I'm using Debian on the BBB. That must be the difference. Here is a cat of the uEnv.txt file
root@beaglebone:/boot# cat uEnv.txt
#Docs: Beagleboard:U-boot partitioning layout 2.0 - eLinux.org
uname_r=3.8.13-bone70
#dtb=
cmdline=quiet init=/lib/systemd/systemd
##Example
#cape_disable=capemgr.disable_partno=
#cape_enable=capemgr.enable_partno=
##Disable HDMI/eMMC
#cape_disable=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN,BB-BONE-EMMC-2G
##Disable HDMI
#cape_disable=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN
##Disable eMMC
#cape_disable=capemgr.disable_partno=BB-BONE-EMMC-2G
##Audio Cape (needs HDMI Audio disabled)
#cape_disable=capemgr.disable_partno=BB-BONELT-HDMI
#cape_enable=capemgr.enable_partno=BB-BONE-AUDI-02
##enable BBB: eMMC Flasher:
##make sure, these tools are installed: dosfstools rsync
##cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh
😉 ICHI
root@beaglebone:/boot# cat uEnv.txt
#Docs: Beagleboard:U-boot partitioning layout 2.0 - eLinux.org
uname_r=3.8.13-bone70
#dtb=
cmdline=quiet init=/lib/systemd/systemd
##Example
#cape_disable=capemgr.disable_partno=
#cape_enable=capemgr.enable_partno=
##Disable HDMI/eMMC
#cape_disable=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN,BB-BONE-EMMC-2G
##Disable HDMI
#cape_disable=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN
##Disable eMMC
#cape_disable=capemgr.disable_partno=BB-BONE-EMMC-2G
##Audio Cape (needs HDMI Audio disabled)
#cape_disable=capemgr.disable_partno=BB-BONELT-HDMI
#cape_enable=capemgr.enable_partno=BB-BONE-AUDI-02
##enable BBB: eMMC Flasher:
##make sure, these tools are installed: dosfstools rsync
##cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh
😉 ICHI
In /boot/uEnv.txt:
##enable BBB: eMMC Flasher: #cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh is this what you are referring to?
I can not find these lines on the uEnv.txt file on the folder but just the one below
##These are needed to be compliant with Angstrom's 2013.06.20 u-boot.
loadaddr=0x82000000
fdtaddr=0x88000000
rdaddr=0x88080000
initrd_high=0xffffffff
fdt_high=0xffffffff
##These are needed to be compliant with Debian 2014-05-14 u-boot.
loadximage=load mmc 0:2 ${loadaddr} /boot/vmlinuz-${uname_r}
loadxfdt=load mmc 0:2 ${fdtaddr} /boot/dtbs/${uname_r}/${fdtfile}
loadxrd=load mmc 0:2 ${rdaddr} /boot/initrd.img-${uname_r}; setenv rdsize ${filesize}
loaduEnvtxt=load mmc 0:2 ${loadaddr} /boot/uEnv.txt ; env import -t ${loadaddr} ${filesize};
check_dtb=if test -n ${dtb}; then setenv fdtfile ${dtb};fi;
loadall=run loaduEnvtxt; run check_dtb; run loadximage; run loadxrd; run loadxfdt;
mmcargs=setenv bootargs console=tty0 console=${console} ${optargs} ${cape_disable} ${cape_enable} root=/dev/mmcblk0p2 rootfstype=${mmcrootfstype} ${cmdline}
uenvcmd=run loadall; run mmcargs; bootz ${loadaddr} ${rdaddr}:${rdsize} ${fdtaddr};
I assume you have read instructions at the end of http://bbb.ieero.com/ page.
Does the flash command report success?
Ok, so today I tried four times to flash as outlined in the directions at the end of the page. Still cannot get to diyAudio server HTTPS page mpd nor using putty as root with botic password, says invalid password.
Attached is txt file of output after /opt/scripts/tools/eMMC/beaglebone-black-make-microSD-flasher-from-eMMC.sh execute. In it I see two 'error' messages, I don't know if they are the problem?
View attachment Botic load 11pm.txt
Where can I get the Debian version you are using?You're using Angstrom, I'm using Debian on the BBB. That must be the difference. Here is a cat of the uEnv.txt file
##enable BBB: eMMC Flasher:
##make sure, these tools are installed: dosfstools rsync
##cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh
😉 ICHI
Angstrom is Debian too rt?😱
Where can I get the Debian version you are using?
Angstrom is Debian too rt?😱
Here.....
http://beagleboard.org/latest-images
I assume you have read instructions at the end of http://bbb.ieero.com/ page.
Does the flash command report success?
Well, after chasing my tail all day yesterday I've found that the instructions at the end of http://bbb.ieero.com/ page don't actually flash the eMMC from the SD card, it copies the contents of eMMC to the SD card.
Saw this when I copied Botic IMG file to SD card and verified by viewing a .txt file on the SD card, a .txt file contained the word Botic.
Logged onto BBB used the command given by instructions at the end of http://bbb.ieero.com/ page, when done removed SD card and read it on PC and the .txt file previously with the word Botic in it did not contain the word Botic??? 😱 😕
- Home
- More Vendors...
- Twisted Pear
- Support for Botic Linux driver