Forum - Recent Threads

I2S input - Beaglebone Black

Former Member — Thu, 07 Jul 2016 13:31:44 GMT

Hello guys,

I am new with linux and the beaglebone. I have a project that will use the same processor of the beaglebone black, so I`ve decided to use this board to build a prototype. The kernel from my beaglebone black is 3.8.13-bone47 and I am using a BlueGiga board to send I2S (using 3 wires) audio to the beaglebone. My goal is to make the beaglebone receive I2S (maybe using arecord - alsa), compress the audio using opus enconder and send it to a web browser. At this moment, I am able to receive a audio from a web radio in wav format (I need to change that to audio receive from BlueGiga), encode the audio to opus format and send to a web browser (I create a server that runs inside the beaglebone). However, I am having a lot of difficulties to turn the beaglebone able to receive I2S. I am trying to use the device tree overlay but without success. I disable the HDMI in the Uenv.txt and I am able to achieve the new overlay (I check the slots and the pins modes). However, I can`t use arecord because alsa do not recognize the audio coming from the bluegiga using wires. My dts file is:

/dts-v1/;

/plugin/;

/ {

compatible = "ti,beaglebone", "ti,beaglebone-black";

part-number = "BBB-AUDIO-01";

version = "00A0", "A0";

exclusive-use =

"P9.27", /* mcasp0_fsr */

"P9.30", /* mcasp0_axr0 */

"P8.35", /* mcasp0_aclkr */

"mcasp0";

/* the offsets come from the bone.js file from adafruit */

fragment@0 {

target = <&am33xx_pinmux>;

__overlay__ {

tdm_pins: tdm_pins {

pinctrl-single,pins = <

0x1a4 0x20 /* P9.27 INPUT/MODE 0*/

0x198 0x20 /* P9.30 */

0x0d0 0x23 /* P8.35 */

};

fragment@1 {

target = <&mcasp0>;

__overlay__ {

compatible = "ti,omap2-mcasp-audio";

pinctrl-names = "default";

pinctrl-0 = <&tdm_pins>;

status = "okay";

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

tdm-slots = <2>;

num-serializer = <16>;

serial-dir = < /* 0: inactive, 1:TX, 2:RX */

2 0 0 0

0 0 0 0

tx-num-evt = <1>;

rv-num-evt = <1>;

};

fragment@2 {

target = <&ocp>;

__overlay__ {

sound {

compatible = "ti,da830-evm-audio";

ti,model = "DA830 EVM";

ti,audio-codec = <&tlv320aic3x>;

ti,mcasp-controller = <&mcasp0>;

ti,codec-clock-rate = <12000000>;

ti,audio-routing =

"LINE1L", "Line In",

"LINE1R", "Line In";

};

Thank guys for the help.

ps: I can see the I2S with a scope after the BLUEGIGA.

BBB- camera interfacing

Former Member — Mon, 21 Mar 2016 05:37:24 GMT

i am working with image processing on BBB. i am little confuse in camera selection that which camera will be more compatible to use with BBB.for capturing images i m thinking to use 'OV9655' camera but i am not sure about it. can anyone suggest me better option or any other camera?

RE: BBB- camera interfacing

clem57 — Tue, 22 Mar 2016 10:09:36 GMT

mk.

From what I can tell, these are for Dual-Port SRAMs only which ultimately may apply. But there are many proposals in the world, few truly become standards. This fails the mustard. Focus on well supported things. You have given no reason for 3 different objects. Are they rooms or a museum piece? Security? Purpose could determine hardware resources.

clem57

PS why is this post in beagle bone radio Internet? Anything to do with your purpose?

RE: BBB- camera interfacing

Former Member — Tue, 22 Mar 2016 07:22:37 GMT

ok.. thats might be good approach. i have also heard about gpmc(general purpose memory controller) interface. they are also use to transmit capture images from camera to beagle but i am unable to find its tutorials thats why don't have too much detail about them.what do you think about it?

RE: BBB- camera interfacing

clem57 — Mon, 21 Mar 2016 15:04:52 GMT

To use them at the same time would require a board for each basically. Microprocessors have limited bandwidth to I/O when you run them with Linux because of real time requirements hard to meet. But you could dedicate a micro-controller to each and tie to a single microprocessor for all 3 using a high speed UART or I2C.

Clem

RE: BBB- camera interfacing

Former Member — Mon, 21 Mar 2016 11:04:22 GMT

i have found some more cameras but when i think about the three camera interfacing then i get confused. like, one camera that i found was "LI-LBCM3M1 Leopard Imaging"

it has 32 output ports. so for using one might be possible but when 3 cameras are concerned then it will create problem cx bbb dont have too much ports for this.

RE: BBB- camera interfacing

Former Member — Mon, 21 Mar 2016 10:57:30 GMT

basically, i have to do camera interfacing with 3 cameras on bbb under linux which will capture the images of three different objects. but initially i have to focus on only one camera. so while deciding any suitable camera i have to keep this in mind that what ever i select for one, i have to do that with remaining two also.

RE: BBB- camera interfacing

clem57 — Mon, 21 Mar 2016 10:45:31 GMT

Well in general that is a good choice. But to suggest one, you need to tell more on expected use and application areas. More parameters you give, the better suggestion.

Clem

RE: Which book is easy to understand the Beaglebone ?

kcsekhar — Sun, 29 Nov 2015 07:19:16 GMT

thanks for sure i will be checking out the book soon

Which book is easy to understand the Beaglebone ?

kcsekhar — Sun, 29 Nov 2015 07:10:40 GMT

please suggest me a book on beagle bone !

RE: Which book is easy to understand the Beaglebone ?

scitechindian — Sun, 29 Nov 2015 07:16:51 GMT

we have a book on beagle bone at @makershive you can come and review

Buy Getting Started with Beaglebone Book Online at Low Prices in India | Getting Started with Beaglebone Reviews & Ratin…

Beaglebone Black AM335x

imrank340@gmail.com — Tue, 14 Jul 2015 18:07:50 GMT

Hello,

I wonder you can please shed some light on my problem.
1/ I build a kernel 3.14.47 success fully for the Beaglebone Black
2/ Build the Modules ie. libs
3/ Stole tisdk-rootfs-image-am335x-evm.tar.gz for the rootfs file system
4/ replaced boot/zImage with my new image and am335x-boneblack.dtb file
6/ created a micro SD and booted the BBB from the SD card.
7/ The BOOT process gone successfully and system has boot and prompted at beagbone~$
8/ at promtp 'root' I managed to logged in
9/ But when I ran lsmod command. I cannot see any driver been loaded in the kernel.
10/ lsmod did not browse any kernel space loaded driver on to the screen
11/ I wonder what I am doing wrong?

I will be grateful if you can shed light on this problem.
Thank you,

Is dual booting is possible with beagle bone black just like with pc

garg1387 — Fri, 15 May 2015 16:16:08 GMT

want to start board in dual boot mode any idea ???

RE: Is dual booting is possible with beagle bone black just like with pc

clem57 — Thu, 21 May 2015 01:05:04 GMT

By default, the eMMC will boot unless a SD card is inserted before with a good OS.

Clem

RE: Is dual booting is possible with beagle bone black just like with pc

gdstew — Fri, 15 May 2015 18:58:27 GMT

Since the BeagleBoard Black uses u-boot it can be set up to boot kernels from several places. I have an old LinuxStamp (Atmel ARM core with 32 MB) from many years ago that I have u-boot set up to

boot from the removable SD card or using dhcp/bootp or tftp on the network along with nfs to provide the root file system for these network boot options. This is an old version of u-boot and there may be

different options or better ways to do this now but this is fairly straight forward.

This is the u-boot configuration I used, note that in this case the serial port is being used for the console terminal:

ecb_at91> printenv

bootdelay=2

baudrate=115200

ethaddr=00:00:00:00:00:5b

loadaddr=0x20200000

bootcmd=run tboot

bootfile=/srv/tftp/linux-2.6.24.3-lnst.img

netmask=255.255.255.0

hostname=lnst

ipaddr=192.168.1.51

serverip=192.168.1.11

dt_bootargs=mem=32M root=/dev/nfs nfsroot=192.168.1.11:/home/gary7/My_projects/Embedded/LinuxStamp/rootfs ip=192.168.1.51 console=ttyS0,115200n8

f_bootargs=mem=32M ip=192.168.1.51 console=ttyS0,115200n8

dboot=setenv bootargs ${dt_bootargs}; bootp; bootm 20200000

fboot=setenv bootargs ${f_bootargs}; bootm C0021840

tboot=setenv bootargs ${dt_bootargs}; tftpboot; bootm 20200000

stdin=serial

stdout=serial

stderr=serial

Commands for multi-boot environment. These are run from the u-boot prompt, in this case ecb_at91>, which is entered by pressing any key when prompted by u-boot.

Note that the bootdelay command sets the amount of time you have to press the key.

run dboot for dhcp boot (bootcmd=bootp; bootm 20200000)

run fboot for flash boot (bootcmd=bootm C021840)

run tboot for tftp boot (bootcmd=tftpboot; bootm 20200000), this is the default automatic boot (from bootcmd=run tboot)

Most of the u-boot options are fairly obvious, I will attempt to answer any questions for ones that are not so obvious. Also, I suggest reading the the u-boot

documentation at least as far as boot options and how to change/save them are concerned.

Edited to add:

If you have multiple flash devices (nand and SD card) the device will be needed to set the root path (root=) in the boot arguments.

RE: BeagleBone Black - WiFi hangs on boot

clem57 — Wed, 08 Apr 2015 09:20:37 GMT

Cron would be the place to look. Start with no interface or in DOWN mode. Later use cron to bring it UP. If cron not work, spawn a task that sleeps for 5 minutes in python before issing UP command to iface.

clem

BeagleBone Black - WiFi hangs on boot

Former Member — Wed, 08 Apr 2015 08:34:13 GMT

Hey guys,

I am running the latest Ubuntu build on a Rev C BeagleBone Black. I am using a wifi dongle into the usb port on the board. The problem is that the wifi hangs on connecting to the access point about half the time on boot. When it does connect, it sometimes does not get the DNS servers and I must restart the networking service. Any ideas on how to get it to boot without attempting to connect for 5+ minutes?