[beagleboard] Suggestion for connecting multiple components to Beaglebone black through usb.

Hello, I am working on a project, in which beaglebone black is used. The components to be connected to beaglebone black are Sensehub (which consists of accelerometer) and a webcam.As sensehub cannot be directly connected to beaglebone black directly, we connected it to launch-XL, which

[beagleboard] Re: Enable UART pins on BBB with Ubuntu 16.04 Kernel 4.4.68

Hello, I've also faced the same issue. Even though I tried editing the /boot/uEnv.txt file, I cannot enable uart cape_enable=bone_capemgr.enable_partno=BB-UART2 I had to use config-pin P9_21 uart config-pin P9_22 uart to enable my uart2 channel. @Zach : Please try the same and let me know.

[beagleboard] Re: Configuring GPIO pins as active high

Thanks @Robert I could solve the issue by setting active_low value in /sys/class/gpio/gpio66 But I think that's not the recommended method. Comments please!! On Friday, 23 February 2018 18:06:48 UTC+5:30, Salah Abdul Gafoor wrote: > > Hi, > > I want to configure some of my gpio pins (P8_07 to

Re: [beagleboard] Disconnect HDMI cape from Cape Manager

By this I mean I have my uEnv.txt configured in this way and I see these messages. Not that it fixed it. Thanks. On Monday, February 26, 2018 at 7:10:39 PM UTC-8, Kenny Koller wrote: > > Thanks. I had a line in there to disable it but have commented it out. > > > uname_r=3.8.13-bone62 > > >

Re: [beagleboard] Disconnect HDMI cape from Cape Manager

Thanks. I had a line in there to disable it but have commented it out. uname_r=3.8.13-bone62 optargs=quiet drm.debug=7 findfdt=setenv fdtfile am335x-boneblack.dtb cape_enable=capemgr.enable_partno=BB-SPIDEV0 #cape_disable=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN On

Re: [beagleboard] Disconnect HDMI cape from Cape Manager

Check /boot/uEnv.txt to see if its being loaded in there On 2/26/2018 8:04 PM, Kenny Koller wrote: > I am running the 3.8 kernel on an Arrow Beaglebone Black Industrial. I > have rebuilt the device tree blob to exclude HDMI but I still see the > error messages below. What is the best way to stop

[beagleboard] Disconnect HDMI cape from Cape Manager

I am running the 3.8 kernel on an Arrow Beaglebone Black Industrial. I have rebuilt the device tree blob to exclude HDMI but I still see the error messages below. What is the best way to stop these from occuring? Are there configuration files for the cape manager? Thanks Duchess: dmesg | grep

[beagleboard] RE: how can we tell system to shutdown on a power fail, using systemd and apcid

seems they omitted the "AC" interrupt in the patch https://patchwork.kernel.org/patch/9782813/ therefore the system will not power down on power fail like it used to -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed

[beagleboard] Using Playstation Eye's microphone array on Beaglebone Blue

Hi, So I am trying to use Playstation Eye's microphone array to perform some sound source localization tasks on my beaglebone blue. I am using an ubuntu image from: https://jh.app.box.com/v/530-707-Dropbox And I am using a software called HARK: https://www.hark.jp/ I suspect Playstation Eye

Re: [beagleboard] PRUs realtime data acquisition, I2C bus and ADC

The IIO ADC driver can run at 800K samples per second. Here is the patch that made that possible. https://patchwork.kernel.org/patch/9391487/ I can confirm that I have tested the driver at 800Ksps and it works fine as long as you have a proper low impedance source for each ADC channel. CPU

Re: [beagleboard] PRUs realtime data acquisition, I2C bus and ADC

Thanks John, I am now working with the starterware_PRU but I did not find examples for using the McSPI with the PRU, do you think it will be hard to adapt the initial code to the PRU ? Thanks Pierrick Le lundi 19 février 2018 23:15:50 UTC-5, john3909 a écrit : > > Like I said, it was

Re: [beagleboard] PRUs realtime data acquisition, I2C bus and ADC

Thanks John, I am now working with the starterware_PRU but i did not find examples for using the McSPI with the PRU, do you think it will be hard to adapt the initial code to the PRU ? By the way, looking to the IIO driver documentation, it seems that for the AM335x chip the max sampling

[beagleboard] Re: shutdown procedure required for beaglebone black ??

Can you use a remote bottom. Does this start-stop bottom come out on the terminal strip? -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop

Re: [beagleboard] BeagleBone Black Boot optimization

That 4.14 kernal definitely improved the boot times compared to what I was seeing and what I posted here: https://github.com/RobertCNelson/boot-scripts/issues/10 However, I am still getting a boot time of close to a minute (~32 seconds for both *dev-mmcblk1p1.device* and

[beagleboard] Linux classes at Embedded World

If you are at Embedded World, see https://www.embedded-world.eu/program.html and search for "Introduction to Embedded Linux". First session is completely full, but they've added at least one more. You can also find folks from Texas Instruments, Octavo Systems, GHI Electronics, Element14,

[beagleboard] Beaglebone Black boot from NAND

Hi there, I'm playing with BBB black at the moment. Using the following article https://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-Bootloader:U-Boot I got it work as described. Now I have a custom board based on BBB with NAND installed ( MT29F4G16ABADAWP ). The only way

[beagleboard] How handle interrupts in ARM from PRU

Hi guys, I'm new in embedded systems and me English is not very good, but I will try. I have a board like the beaglebone with buildroot system, and the board has a ARM main processor and 2 pru. I installed the remoteproc lib in the board for communicate the PRU -> ARM via interrupt. I dont

[beagleboard] Log file from daemon.log

Hi, My distribution is: BeagleBoard.org Debian Image 2016-12-09 >From one of my units I am able to see the dhcp request from the usb0 like this: Feb 25 22:26:03 beaglebone dnsmasq-dhcp[689]: DHCPINFORM(usb0) 192.168.7.1 38:d2:69:57:cc:c2 Feb 25 22:26:03 beaglebone dnsmasq-dhcp[689]:

[beagleboard] 8.6 IoT Devbian Image Issue

Hi, Recently I downloaded the 8.6-IoT image from your website and after I flash the image I am able to log in the console for the first 10 seconds over the usb port then after that I was unable to log in any more. I tried other Debian images and this always works. I only seen this issue on the

[beagleboard] PocketBeagle not booting issue

Hello all, I've been experimenting with the working PocketBeagle and possibly modified the uEnv.txt file using the Cloud9 IDE terminal. Then I tried to reboot the board with the shutdown –r now command. The board didn't reload successfully, and after rebooting manually only the power LED was

Re: [beagleboard] Re: Problem with PINMUX - WARNING: missing PINMUX driver

the errors you are seeing is because the pins are not setup pins get setup by using an overlay at boot time verify the overlay you require is being loaded in /boot/uEnv.txt as of any 4.x  kernel everything must be loaded at boot time from that file the cape manager is not used On 2/26/2018

Re: [beagleboard] U-boot dtbo

Hi Wulf Man...Thanks very much for the response. I tried your suggestion of putting the custom cape in the next line, but could not see a change in the dmesg. It really seems like the /boot/uEnv.txt file is not being reference at all. Alan On Sunday, February 25, 2018 at 9:07:31 PM