Forum - Recent Threads

I am getting only 1 channel out of 2, for each serial pin in Beaglebone AI

mqya95 — Mon, 21 Mar 2022 09:53:32 GMT

Hello I want to record 8 channels from TIDA-01454 CMB into a Beaglebone AI. As the CMB is built with two PCM1864 ADCs and it is also a Beagle board, I followed this guide(https://www.ti.com/lit/an/sprac97/sprac97.pdf) with some changes(channels_max=16).

I have managed to record audio from 4 of the 8 microphones that the CMB has(I just tap the mic to check if that one is working). However I want to record the 8 channels. Currently the working microphones are MIC1, MIC4, MIC5 and MIC8, although I would say there is much noise.The CMB has 4 data output pins, I suppose each one transmits 2 channels, so the problem is that each pin is getting mono instead of stereo. This might be because a problem in DTS, therefore this is my dts file:

pcm5102a: pcm5102a { 

     #sound-dai-cells = <0>; 

     compatible = "ti,pcm5102a"; 

     status = "okay"; 

  }; 

   

   

  sound {compatible = "simple-audio-card"; 

    simple-audio-card,format = "i2s"; 

    simple-audio-card,name = "PCM5102a"; 

    simple-audio-card,bitclock-master = <&sound1_master>; 

    simple-audio-card,frame-master = <&sound1_master>; 

    simple-audio-card,bitclock-inversion; 

     

     

    simple-audio-card,cpu { 

            sound-dai = <&mcasp1>; 

    }; 

    sound1_master: simple-audio-card,codec { 

        #sound-dai-cells = <0>; 

        sound-dai = <&pcm5102a>; 

          //clocks = <&mcasp1_fck>; 

          //clock-names = "mclk"; 

      }; 

  }; 

&mcasp1 { 

    #sound-dai-cells = <0>; 

    pinctrl-names = "default"; 

    pinctrl-0 = <&mcasp1_pins>; 

    status = "okay"; 

    op-mode = <0>; /* MCASP_IIS_MODE */ 

    tdm-slots = <2>; 

    num-serializer = <4>; 

    serial-dir = < /* 1 TX 2 RX 0 unused */ 

        2 2 0 0 0 0 0 0 0 0 2 2

      >; 

    rx-num-evt = <4>; 

    tx-num-evt = <4>; 

};

The serial-dir is that way because I use mcasp1_axr0, mcasp1_axr1, mcasp1_10 and mcasp1_axr11 ,those are the ones available in Beaglbone AI. I connected the pins DATA1-MiniDSP, DATA2-MiniDSP, DATA3-MiniDSP and DATA4-MiniDSP in J5(of the CMB) to these pins in my Beaglebone:


P9.18b                               173 fast rx       0 mcasp 0 d0       mcasp@48460000 (mcasp1_pins)
P9.17b                               174 fast rx       0 mcasp 0 d1       mcasp@48460000 (mcasp1_pins)
P9.30                                183 fast rx       0 mcasp 0 d10      mcasp@48460000 (mcasp1_pins)
P9.28                                184 fast rx       0 mcasp 0 d11      mcasp@48460000 (mcasp1_pins)

I also conected DATA1-MiniDSP, LRCLK and BCLK to an external I2S DAC to make a test and I could hear MIC1 and MIC2. So I can assure that outputs are coming in stereo. My problem is that when connect the outputs to Beaglebone and record, I just get 1 of those 2 channels for each DOUT. I checked all of them just in case with the external I2S DAC:

Data 1 is giving MIC1 and MIC2

Data 2 is giving MIC5 and MIC6

Data 3 is giving MIC3 and MIC4

Data 4 is giving MIC7 and MIC8

In case it helps, here is myDummy CODEC:

#include <linux/init.h>
#include <linux/module.h>
#include <linux/platform_device.h>

#include <sound/soc.h>

static struct snd_soc_dai_driver pcm5102a_dai = {
	.name = "pcm5102a-hifi",
	.playback = {
		.channels_min = 2,
		.channels_max = 2,
		.rates = SNDRV_PCM_RATE_8000_192000,
		.formats = SNDRV_PCM_FMTBIT_S16_LE |
			   SNDRV_PCM_FMTBIT_S24_LE |
			   SNDRV_PCM_FMTBIT_S32_LE
	},
	.capture = { 

		.stream_name = "Capture", 

		.channels_min = 1, 

		.channels_max = 16, 

		.rates = SNDRV_PCM_RATE_8000_192000, 

		.formats = SNDRV_PCM_FMTBIT_S16_LE | 

			SNDRV_PCM_FMTBIT_S24_LE | 

			SNDRV_PCM_FMTBIT_S32_LE 

	}, 
};

static struct snd_soc_codec_driver soc_codec_dev_pcm5102a;

static int pcm5102a_probe(struct platform_device *pdev)
{
	return snd_soc_register_codec(&pdev->dev, &soc_codec_dev_pcm5102a,
			&pcm5102a_dai, 1);
}

static int pcm5102a_remove(struct platform_device *pdev)
{
	snd_soc_unregister_codec(&pdev->dev);
	return 0;
}

static const struct of_device_id pcm5102a_of_match[] = {
	{ .compatible = "ti,pcm5102a", },
	{ }
};
MODULE_DEVICE_TABLE(of, pcm5102a_of_match);

static struct platform_driver pcm5102a_codec_driver = {
	.probe		= pcm5102a_probe,
	.remove		= pcm5102a_remove,
	.driver		= {
		.name	= "pcm5102a-codec",
		.of_match_table = pcm5102a_of_match,
	},
};

module_platform_driver(pcm5102a_codec_driver);

MODULE_DESCRIPTION("ASoC PCM5102A codec driver");
MODULE_AUTHOR("Florian Meier <florian.meier@koalo.de>");
MODULE_LICENSE("GPL v2");

and also my CMB configuration:

uint8_t U1_PCM1864_CONFIG[][2] = { 

{0x00, 0x00}, // Change to Page 0 

{0x01, 0x40}, // PGA CH1_L to 32dB 

{0x02, 0x40}, // PGA CH1_R to 32dB 

{0x03, 0x40}, // PGA CH2_L to 32dB 

{0x04, 0x40}, // PGA CH2_R to 32dB 

{0x05, 0x86}, // Enable SMOOTH PGA Change; Independent Link PGA; 

{0x06, 0x41}, // Polarity: Normal, Channel: VINL1[SE] 

{0x07, 0x41}, // Polarity: Normal, Channel: VINR1[SE] 

{0x08, 0x44}, // Polarity: Normal, Channel: VINL3[SE] 

{0x09, 0x44}, // Polarity: Normal, Channel: VINR3[SE] 

{0x0A, 0x00}, // Secondary ADC Input: No Selection 

{0x0B, 0x44}, // RX WLEN: 24bit; TX WLEN: 24 bit; FMT: I2S format 

{0x10, 0x03}, // GPIO0_FUNC - SCK Out; GPIO0_POL - Normal 

{0x11, 0x50}, // GPIO3_FUNC - DOUT2; GPIO3_POL - Normal 

{0x12, 0x04}, // GPIO0_DIR - GPIO0 - Output 

{0x13, 0x40}, // GPIO3_DIR � GPIO3 - Output 

{0x20, 0x11}  // MST_MODE: Master; CLKDET_EN: Disable 

}; 

  

uint8_t U2_PCM1864_CONFIG[][2] = { 

{0x00, 0x00}, // Change to Page 0 

{0x01, 0x40}, // PGA CH1_L to 32dB 

{0x02, 0x40}, // PGA CH1_R to 32dB 

{0x03, 0x40}, // PGA CH2_L to 32dB 

{0x04, 0x40}, // PGA CH2_R to 32dB 

{0x05, 0x86}, // Enable SMOOTH PGA Change; Independent Link PGA; 

{0x06, 0x41}, // Polarity: Normal, Channel: VINL1[SE] 

{0x07, 0x41}, // Polarity: Normal, Channel: VINR1[SE] 

{0x08, 0x44}, // Polarity: Normal, Channel: VINL3[SE] 

{0x09, 0x44}, // Polarity: Normal, Channel: VINR3[SE] 

{0x0A, 0x00}, // Secondary ADC Input: No Selection 

{0x0B, 0x44}, // RX WLEN: 24bit; TX WLEN: 24 bit; FMT: I2S format 

{0x10, 0x00}, // GPIO0_FUNC – GPIO0; GPIO0_POL - Normal 

{0x11, 0x50}, // GPIO3_FUNC - DOUT2; GPIO3_POL - Normal 

{0x12, 0x00}, // GPIO0_DIR - GPIO0 - Input 

{0x13, 0x40}, // GPIO3_DIR � GPIO3 - Output 

{0x20, 0x01}  // MST_MODE: Slave; CLKDET_EN: Enable 

};

So what is wrong? How can I get all the mics?

AI training online

clem57 — Thu, 05 Dec 2019 20:31:19 GMT

For anyone is interested, there is now a free AI course by IBM using Coursea platform. Since it is delivered online, you can partake as you wish around the world. Check it out at this topic thread .

Clem

BB AI and OpenCV 3.3+

vlasov01 — Fri, 25 Oct 2019 02:09:45 GMT

I know BB AI comes with OpenCV 3.2.

I'd like to use BB AI with OpenCV Deep Neural Networks (dnn module) on my project. It comes with OpenCV 3.3 or later.

I'm wondering if anyone was able to get OpenCV 3.3 or later for BB AI?

If yes, are you still benefiting from BB AI hardware accelerators?

Problems getting started or is it dead??

phoenixcomm — Mon, 21 Oct 2019 10:14:37 GMT

players.brightcove.net/.../index.html

I got my BB AI about a week ago I had problems getting the fan mounted. But when I plug it in via USBA > USBC type 3 cable but all I get is this. Is my BB dead?

Thanks

Cris H.

problem was thas the motherboard didn't do it. I bought a wall rat from 5-blow and now it boots!

NOW how to change the static addresses

Boot up Sequence for BB-AI

clem57 — Wed, 09 Oct 2019 18:38:15 GMT

Looking in Ti's documentation, I found:

The following boot modes are supported:

• NOR Flash boot • NAND Flash boot

• SD boot • eMMC boot

• QSPI_1 boot (1-bit SPI flash memories)

• QSPI_4 boot (4-bit (Quad) SPI flash memories)

• SATA boot • Universal Asynchronous Receiver/Transmitter (UART) boot

• Universal Serial Bus (USB) boot (like an ethernet card, not as mass storage)

• HS USB 2.0 boot (like an ethernet card, not as mass storage)

If the first boot source fails to boot, the ROM will move on to the next one in the sequence. Keep in mind that some boot sources take some time to timeout if that boot source isn't available. To understand details on different boot modes, see the device-specific technical reference manual (TRM).

Key Boot Considerations are:

• It is recommended to include population options for other boot modes to aid in development

• Boot pins have other functions after reset. Make sure your board design takes this into account when choosing pull-up/down resistors for the boot pins

Installing OpenCV is Like...

14rhb — Wed, 09 Oct 2019 09:00:13 GMT

After several days into attempting to install OpenCV on my BB-AI it feels like I'm at about 0:15s into this video !

https://www.youtube.com/watch?v=wmFzGXy5uYc

Maybe some pointers for others are in my iBox posts:

iBox: #2 Setting up the BB-AI

iBox: #3 Is it a cat, a plane, a moth?

I also tried cross compiling on my faster PC with the aim of porting the code across afterwards, but that too failed with the libpython2-dev:armhf library not being found. After much adjustment of my machine on the Linux command line I'm also no nearer on that approach.

But it did make me think, hence this question rather than a blog post:

If I were to compile the OpenCV on my other machine and port it across to the BB-AI then has someone else done this? e.g. why am I sitting waiting days for the BB-AI to run CMAKE if it could be done externally and highly likely someone already has.

I've learnt many Linux commands along the way and have a rough understanding of what cross-compiling is.....so progress todate has been worthwhile still

Neuromophic Computing

clem57 — Tue, 08 Oct 2019 14:48:06 GMT

Neuromorphic computing is an emerging technology that has actually been emerging for quite some time. It was first proposed in the 1980s by Carver Mead to take advantage of some of the technologies emerging in very large-scale integration (VLSI). The idea was to put a large array of analog circuits on a single chip where all of the individual analog blocks were designed to leverage our knowledge of:

Biologically based neural architectures in living nervous systems.
New machine learning algorithms.
Physical microelectronics.

One of the driving forces in this computing domain is because the end is in sight for the dramatic exponential growth of single processor von Neuman computer architectures. (Of course, it is the driving force for parallelism, quantum computing, etc. Who doesn't stay up nights worrying about the day when we can't compute any faster?!)

What do you know about this topic?

Some Thoughts about BB-AI

clem57 — Sat, 05 Oct 2019 18:57:14 GMT

First Off...

So far in exploring the BB-AI, I like the potential of what it can do. But the first is the heat issue. I think this is solvable, but much consideration needs to be given with the usage of capes. The software quality is high. It uses Debian directive which is much like Rasbian or the Pi. I found a fairly good video that is a review of the board.

www.youtube.com/watch

Skip forward to about 4:00 and watch from there. I am oing to use this to post pointers to other things (vision of course LOL). So stay tuned for more revelations to come. In the meantime, Use the comments below for criticism, wits, and any other observations. I will of course address them as time permits...

Keep up the faith and we will conquer this together...

Updating Linux... 10/06/19

After thinking about the troubles of using the 16 GB eMMC flash, I decided to pursue another method much safer and less error prone.

I solved this one by the following steps:

Downloaded the latest image for Beagle Bone AI from BeagleBone.org
Used Etcher to burn the image to a fairly large SD card. I used a good named brand...
Booted the Beagle Bone AI with card inserted.
Checked space with df -h
Run shell /opt/scripts/tools/grow_partition.sh
Reboot BB-AI.
Check space again with df -h You should see / expanded to the rest of the card.
Run sudo apt update
Run sudo apt upgrade
Now if you want, flash eMMC. I chose not to do this step. I would be careful since you could run into troubles if the card now exceeds 16 G
Enjoy the new and improved Linux!

Btw, I intend to dump the card to a file in case I wish to start from this point again...

Possible help for BB-AI heat problem

clem57 — Fri, 04 Oct 2019 03:57:32 GMT

I did some investigation and found the BB-AI uses a governor of policy0 which is a custom setting. So I am testing setting the normal conservative to reduce the heat.

Here are the two commands:

sudo cpufreq-set -c 0 -g conservative

sudo cpufreq-set -c 1 -g conservative

I will monitor these overtime and report results...

Clem

Not enough disk space for apt upgrade on Beaglebone AI

weiwei2 — Fri, 04 Oct 2019 01:50:55 GMT

I face a not enough space left on device after attempting to do sudo apt upgrade on the device.

the same scenario happen if i try to update the cloud9 by pulling by following example in https://beagleboard.org/upgrade

i also try to follow https://www.hackster.io/175809/tidl-on-beaglebone-ai-1ee263 but all of these will fail at the same 'not enough space scenario'

originally i thought the 8GB sd card i use is really insufficient then i change to a much bigger one and realize problem persists....then it must be something wrong

below is my sudo apt update and the subsequent sudo apt upgrade procedure

debian@beaglebone:/var/lib/cloud9$ sudo apt update

[sudo] password for debian:

Ign:1 http://deb.debian.org/debian stretch InRelease

Get:2 http://deb.debian.org/debian stretch-updates InRelease [91.0 kB]

Get:3 http://repos.rcn-ee.com/debian stretch InRelease [3,064 B]

Get:4 http://deb.debian.org/debian-security stretch/updates InRelease [94.3 kB]

Get:5 http://deb.debian.org/debian stretch Release [118 kB]

Get:6 http://deb.debian.org/debian stretch Release.gpg [2,365 B]

Get:7 http://deb.debian.org/debian stretch-updates/main armhf Packages [27.3 kB]

Get:8 http://repos.rcn-ee.com/debian stretch/main armhf Packages [1,066 kB]

Get:9 http://deb.debian.org/debian-security stretch/updates/main armhf Packages [484 kB]

Get:10 http://deb.debian.org/debian-security stretch/updates/contrib armhf Packages [1,764 B]

Get:11 http://deb.debian.org/debian-security stretch/updates/non-free armhf Packages [1,272 B]

Get:12 http://deb.debian.org/debian stretch/main armhf Packages [6,915 kB]

Get:13 http://deb.debian.org/debian stretch/contrib armhf Packages [42.1 kB]

Get:14 http://deb.debian.org/debian stretch/non-free armhf Packages [59.7 kB]

Fetched 8,906 kB in 17s (511 kB/s)

Reading package lists... Done

Building dependency tree

Reading state information... Done

56 packages can be upgraded. Run 'apt list --upgradable' to see them.

debian@beaglebone:/var/lib/cloud9$ sudo apt upgrade

Reading package lists... Done

Building dependency tree

Reading state information... Done

Calculating upgrade... Done

The following packages have been kept back:

chromium

The following packages will be upgraded:

base-files bb-cape-overlays bonescript e2fslibs e2fsprogs gpiod libcomerr2 libcpupower1 libcups2 libexpat1 libexpat1-dev libgd3 libglib2.0-0 libgpiod2 libicu57 libiio-utils libiio0

libldap-2.4-2 libldap-common libmariadbclient18 libnghttp2-14 libnginx-mod-http-auth-pam libnginx-mod-http-dav-ext libnginx-mod-http-echo libnginx-mod-http-geoip

libnginx-mod-http-image-filter libnginx-mod-http-subs-filter libnginx-mod-http-upstream-fair libnginx-mod-http-xslt-filter libnginx-mod-mail libnginx-mod-stream libpam-systemd libpq5

libss2 libssl1.0.2 libssl1.1 libsystemd0 libudev-dev libudev1 libxslt1.1 linux-cpupower linux-libc-dev nginx nginx-common nginx-full openssh-client openssh-server openssh-sftp-server

openssl systemd systemd-sysv tzdata udev unzip usbutils

55 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.

Need to get 32.0 MB of archives.

After this operation, 194 kB of additional disk space will be used.

E: You don't have enough free space in /var/cache/apt/archives/.

subsequently i do a fdisk -l for my very huge sd card after reading about https://www.linuxquestions.org/questions/debian-26/no-space-left-on-device-880308/ but unsure if i can follow it

here's my fdisk output

debian@beaglebone:/var/lib/cloud9$ sudo fdisk -l

Disk /dev/mmcblk0: 119.3 GiB, 128043712512 bytes, 250085376 sectors

Units: sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disklabel type: dos

Disk identifier: 0xf7146e7c

Device Boot Start End Sectors Size Id Type

/dev/mmcblk0p1 * 8192 7372799 7364608 3.5G 83 Linux

Disk /dev/mmcblk1: 14.6 GiB, 15678308352 bytes, 30621696 sectors

Units: sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disklabel type: dos

Disk identifier: 0x209da4b7

Device Boot Start End Sectors Size Id Type

/dev/mmcblk1p1 * 8192 30621695 30613504 14.6G 83 Linux

Disk /dev/mmcblk1boot1: 4 MiB, 4194304 bytes, 8192 sectors

Units: sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/mmcblk1boot0: 4 MiB, 4194304 bytes, 8192 sectors

Units: sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

debian@beaglebone:/var/lib/cloud9$

Day One Vision Thing

clem57 — Sun, 29 Sep 2019 17:50:20 GMT

Background

So about a year ago, I went traveling to China or Shanghai more specifically. While traveling the streets and subways/buses I began to notice a pattern in the streets. It seem intentional, so I ask what this was. I was told it was for the blind. Here is a set of photos showing the pattern: The one in the middle is most complicated since it lines for direction and swirls for off the track. Although you cannot see the edge for the one on the right,

the end near the street has points/dots signifying end for crossing street. As a blind person hits these by dragging the cane, they can know direction and end of side walk.

Mission

Can I devise an electronic substitute to work in the other parts of the world that can assist a blind person like the above examples. This is where the Beagle Bone AI comes in. I would like it to recognize the sidewalk and intersections. When these are detected, a audio alert is given for the user to guide them. Also as a bonus effort, can cars be detected and lights be detected, so more audio alerts can help cross the street. To add fun and make this interesting I plan to involve the community with other blogs and occasional polls to guide the project.

First Poll

For the first poll and help, I need to decide a a project name. Have have a few choices and will pick the best or most popular one. Please leave any comments or reasons why you think yours is better than the others. Thank you!

Go to Help me with title for Vision Thing

Beaglebone Ai Heating Issues

ipv1 — Sat, 28 Sep 2019 16:51:46 GMT

While experimenting with the device, I found that the board would shutdown without warning. The reasons is...

Now I tried a number of combos like us the USB tether, connect with display(yes I have the cursed microHDMI cable) and use standalone but every time, it just overheats if I do anything.

Idle temps are high too. Was wondering if I got a bad board or is it everyone?