Re: [beagleboard] Weird Problem using GPIOs on BBB

Attached. One is the cpp code and other is the bash script. cpp code uses the GPIO class from the attached GPIO.7z . On Thursday, July 14, 2016 at 9:50:45 AM UTC+5:30, William Hermans wrote: > > Let's put it this way. No code, no help . . . > > On Wed, Jul 13, 2016 at 9:19 PM, William Hermans

Re: [beagleboard] BeagleBone Black is not Boot

try 9600 baud On 7/13/2016 7:14 PM, Sangyong Lee wrote: > Thank you for reply. > > I was tried connect to debug mode used serial cable. > > but, is not connect. It has been shown a lot of broken character on > the screen. > (setting = Baud 115,200 / Bits 8 / Parity N / Stop Bits 1 / Handshake >

Re: [beagleboard] Weird Problem using GPIOs on BBB

Let's put it this way. No code, no help . . . On Wed, Jul 13, 2016 at 9:19 PM, William Hermans wrote: > > #code2 > //create an instance of gpio41 > //set direction as OUT > //set value as 1 > usleep(10); > //set value 0 > > Output : Toggle doesnt happens > > Whats this ?

Re: [beagleboard] Weird Problem using GPIOs on BBB

#code2 //create an instance of gpio41 //set direction as OUT //set value as 1 usleep(10); //set value 0 Output : Toggle doesnt happens Whats this ? This is not code. At best it's comments, and usleep(). On Wed, Jul 13, 2016 at 9:02 PM, Raulp wrote: > OK let em

Re: [beagleboard] Weird Problem using GPIOs on BBB

OK let em explain a bit more : #code 1 sudo echo 41 > export cd gpio41 sudo chmod 666 direction sudo chmod 666 value sudo echo out > direction sudo echo 1 > value sleep 1 sudo echo 0 > value Output : Toggle on the GPIO 41 #code2 //create an instance of gpio41 //set direction as OUT //set

Re: [beagleboard] BeagleBone Black is not Boot

Make sure all flow control is of. I've purchased some cables where TX and RX are reversed, check that well On 14 Jul 2016 12:14, "Sangyong Lee" wrote: > Thank you for reply. > > I was tried connect to debug mode used serial cable. > > but, is not connect. It has been shown

Re: [beagleboard] BeagleBone Black is not Boot

Thank you for reply. I was tried connect to debug mode used serial cable. but, is not connect. It has been shown a lot of broken character on the screen. (setting = Baud 115,200 / Bits 8 / Parity N / Stop Bits 1 / Handshake None ) I will browse the another method. 2016년 7월 13일 수요일 오전 10시 4분

Re: [beagleboard] 802.11 Mesh Network with WiLink 8

mesh networks use a 802.11.15.4 link layer From: "pedrotecc...@gmail.com" To: BeagleBoard Sent: Wednesday, July 13, 2016 5:30 PM Subject: [beagleboard] 802.11 Mesh Network with WiLink 8 Hi, I am trying to create a 802.11 Mesh

Re: [beagleboard] 802.11 Mesh Network with WiLink 8

Hi Pedro, On Wed, Jul 13, 2016 at 10:30 PM, wrote: > Hi, > > I am trying to create a 802.11 Mesh Network using BBG-W. It seems to me > that it should be possible as TI has advertised that their WiLink 8 modules > are capable of this type of network. > > I first tried to

[beagleboard] 802.11 Mesh Network with WiLink 8

Hi, I am trying to create a 802.11 Mesh Network using BBG-W. It seems to me that it should be possible as TI has advertised that their WiLink 8 modules are capable of this type of network. I first tried to use "sudo iw phy phy0 interface add mesh0 type mp mesh_id mymesh", but it returns

[beagleboard] Error when try to open serial port using a FT232RL converter

*Hello everyone,* *I have a Beaglebone with Debian 4.6.3 and kernel 3.8 and I require to use an usb serial converter with a FT232RL chip, I can see the converter on the Beaglebone, the problem is when I try to open the serial port I got an error like the serial cable is not connected.* *When

[beagleboard] BBB Error to Open Serial Port (FT232)

*Hello,* *I have a problem to open the serial port on my Beagle Bone. I am using a cable with a FT232 chip.* *First when the I check with the command lsusb I got this* root@beaglebone:/# lsusb Bus 001 Device 002: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial

Re: [beagleboard] does beagleboard X15 support 4k HDMI output?

Off the top of my head first thing in the morning, sounds like a PCIe add-on board project for someone. On 14 Jul 2016 07:40, "Gerald Coley" wrote: > No. 1920 x 1080 60FPS. > > Gerald > > > On Wed, Jul 13, 2016 at 4:35 PM, Yicheng Bai wrote: > >>

[beagleboard] does beagleboard X15 support 4k HDMI output?

Hi, does beagleboard X15 support 4k HDMI output? Thanks. -- 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 receiving emails from it, send an

Re: [beagleboard] does beagleboard X15 support 4k HDMI output?

No. 1920 x 1080 60FPS. Gerald On Wed, Jul 13, 2016 at 4:35 PM, Yicheng Bai wrote: > Hi, > > does beagleboard X15 support 4k HDMI output? > > Thanks. > > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are

Re: [beagleboard] Installing ARch Linux on BBB rev C. can't find boot/zImage

Correction: loaduimage=if ext4load mmc 0:2 ${loadaddr} /boot/zImage; then setenv mmcdev 0; else setenv mmcdev 1; if test $mmc0 = 1; then setenv mmcroot /dev/mmcblk1p2 rw; fi; ext4load mmc 1:2 ${loadaddr} /boot/zImage; fi *should be:* loaduimage=if ext4load mmc 0:1 ${loadaddr} /boot/zImage; then

Re: [beagleboard] Installing ARch Linux on BBB rev C. can't find boot/zImage

So . . . mmcroot=/dev/mmcblk0p2 rw *should be:* mmcroot=/dev/mmcblk0p*1* rw loadfdt=ext4load mmc ${mmcdev}:2 ${fdtaddr} /boot/dtbs/${fdtfile} *should be:* loadfdt=ext4load mmc ${mmcdev}:*1* ${fdtaddr} /boot/dtbs/${fdtfile} loaduimage=if ext4load mmc 0:2 ${loadaddr} /boot/zImage; then setenv

Re: [beagleboard] Installing ARch Linux on BBB rev C. can't find boot/zImage

By the way, ${uname_r} is defined in the second stage uEnv.txt file that comes with recent debian images. But It does not look as though the people at ARCH uses this file structure. So while these paths should be similar, they're going to be slightly different for you. But if you look at the

Re: [beagleboard] Installing ARch Linux on BBB rev C. can't find boot/zImage

Here, here is a stage one uEnv.txt file fro the latest official debian image. Note the differences in disk / partition assingment. But otherwise this uses the same layout for what I can tell as those ARCH instructions imply. william@beaglebone:~/dev$ cat /uEnv.txt ##These are needed to be

Re: [beagleboard] Installing ARch Linux on BBB rev C. can't find boot/zImage

Ok, actually looking at those instructions. They're wrong for that uEnv.txt file you have. uenvcmd=run findfdt; if test $board_name = A335BNLT; then i2c mw 0x24 1 0x3e; setenv mmcdev 1; mmc dev ${mmcdev}; if mmc rescan; then setenv mmc1 1;else setenv mmc1 0;fi;fi;setenv mmcdev 0; mmc dev

Re: [beagleboard] Installing ARch Linux on BBB rev C. can't find boot/zImage

No the arch image is on ext4 partition where the u-boot is created using: dd if=mnt/boot/MLO of=/dev/sdX count=1 seek=1 conv=notrunc bs=128k dd if=mnt/boot/u-boot.img of=/dev/sdX count=2 seek=1 conv=notrunc bs=384k This is new for me as well. Op woensdag 13 juli 2016 22:39:42 UTC+2 schreef

Re: [beagleboard] Installing ARch Linux on BBB rev C. can't find boot/zImage

Is that mount on partition 2 ? On Wed, Jul 13, 2016 at 1:35 PM, Jelle Spijker wrote: > drwxr-xr-x 2 root root 4.0K Jul 1 03:57 dtbs > -rw-r--r-- 1 root root 74K Jun 8 2015 MLO > -rw-r--r-- 1 root root 389K Jun 8 2015 u-boot.img > -rw-r--r-- 1 root root 104

Re: [beagleboard] Installing ARch Linux on BBB rev C. can't find boot/zImage

drwxr-xr-x 2 root root 4.0K Jul 1 03:57 dtbs -rw-r--r-- 1 root root 74K Jun 8 2015 MLO -rw-r--r-- 1 root root 389K Jun 8 2015 u-boot.img -rw-r--r-- 1 root root 104 Jul 13 22:03 uEnv.txt -rwxr-xr-x 1 root root 5.2M Jul 1 03:57 zImage Op woensdag 13 juli 2016 22:22:38 UTC+2 schreef

Re: [beagleboard] Installing ARch Linux on BBB rev C. can't find boot/zImage

So . . . put sdcard into another Linux machine. Then . . . sudo mount /dev/sdxx /media/rootfs ls /media/rootfs/boot What output do you get ? On Wed, Jul 13, 2016 at 1:16 PM, Jelle Spijker wrote: > Hello, > > I'm trying to install Arch on my BBB rev C. using the

[beagleboard] Installing ARch Linux on BBB rev C. can't find boot/zImage

Hello, I'm trying to install Arch on my BBB rev C. using the described method on https://archlinuxarm.org/platforms/armv7/ti/beaglebone-black but it can't find my zImage, whilst it is present in the boot folder. It hangs while the two outer LEDS are on with the following message. I also

Re: [beagleboard] Kernel change and naming convention (for the sake of uio / prussdrv)

By the way, TI's most recent kernels are purportedly supposed to use either remoteproc, or uio_pruss. I say purportedly because I have not personally experimented with that yet, but Robert made a post not long ago about this. So it sounds like right off the bat, all you need to do is load the PRU

Re: [beagleboard] Kernel change and naming convention (for the sake of uio / prussdrv)

> > 2) The "ti" version seems to be dropped starting the 4.5.0 series kernel, > so I guess remoteproc was dropped in the end with newer kernels altogether? > No. That kernel is probably straight out of mainline. Which means it hasn't had either the *bone* or *TI* patchset applied to it yet. On

Re: [beagleboard] Kernel change and naming convention (for the sake of uio / prussdrv)

> > 1) is it possible to install another kernel image, and how is this done > exactly? Unfortunately I managed to get my image on the sd-card unbootable > when installing another kernel (bone-kernel instead of ti-kernel). I guess > that uEnv.txt is not correctly updated when switching kernels.

[beagleboard] Kernel change and naming convention (for the sake of uio / prussdrv)

Ok guys, here is my first question on how to change to another kernel version. I'm using a BBG for my omni-robot project, and started opting for using the PRU's to generate accurate variable frequency PWM signals for my stepper motors (my c code was still showing the occasional delays in

[beagleboard] Re: interfacing IP camera with BBB

hey guys, i'm trying to connect an IP camera with BBB over the ethernet port then broadcast the live streaming video since my BBB is connected to an aircard and has public ip. anyone was able to do such a thing? i'm thinking of forwarding the camera port to the BBB so a person can see the live

Re: [beagleboard] BeagleBoard.org Latest Firmware Images - suggest pointing to 8.3 image rather than 8.4

On Wed, Jul 13, 2016 at 5:24 PM, Jeff Albrecht wrote: > Could you elaborate a wee bit on that syntax? By the way after booting an > 8.4 image I 'tether wifi off' per your suggestion in another thread and did > a connect entering my passphrase when prompted. It

Re: [beagleboard] BeagleBoard.org Latest Firmware Images - suggest pointing to 8.3 image rather than 8.4

Could you elaborate a wee bit on that syntax? By the way after booting an 8.4 image I 'tether wifi off' per your suggestion in another thread and did a connect entering my passphrase when prompted. It worked. I had tried this once before but didn't understand that scan wifi doesn't show the

Re: [beagleboard] jessie moved my WiFi cheese

On Wed, Jul 13, 2016 at 3:34 AM, Jeff Albrecht wrote: > Since I last brought up wifi on a BBB rev c apparently a new way has > become standard for configuring wifi. connmanctl With a couple BBB rev C > that I have run Wheezy on with Edimax USB wifi dongles

[beagleboard] UART only works after reconnecting

Hello, I try to use UART on BBB but I have a problem with UART. We use two BBB and two computers. I have two programs in Python using Pybbio library. One send data and the other receive data. Each program is on a different computer. When I run both program at the same time, nothing happens. I

Re: [beagleboard] Weird Problem using GPIOs on BBB

> > When I try to do the same using a user space C application I dont get the > expected response.I am running this app as sudo'er and I have > oscilloscope'd the timings of HIGH/LOW levels of the GPIOs and compared it > with that of the manually writing procedure of GPIOS. The waveform and the >

[beagleboard] BeagleBoard.org Latest Firmware Images - suggest pointing to 8.3 image rather than 8.4

On the BeagleBoard.Org site in the "BeagleBoard.org Latest Firmware Images" section the "Debian 8.4 2016-05-13 4GB SD LXQT" image is listed as the recommended image. I propose that the 8.3 image be listed there instead because the wifi configuration by way of the suggested configuration method

Re: [beagleboard] Connman & bone-debian-8.5-lxqt-2gb-armhf-2016-06-19-2gb.img

> > I downloaded & wrote the bone-debian-8.5-lxqt-2gb-armhf-2016-06-19-2gb.img > image to a card. > It doesn't seem to start up the ethernet connection on boot - I have to > run sudo systemctl start connman.service from the serial terminal. Here's > the full output. > I tried the 4gb lxqt as well

Re: [beagleboard] Re: PRU remoteproc Tutorial

> > > Using pru-gcc you gain GCC - free and familiar compiler. Admittedly, right > now CCS generates a bit more optimized code than pru-gcc. And CCS has > received more testing than pru-gcc. > > This is also true for the MSP430 port of gcc versus CCS' compiler. It's been this way for years, and I

[beagleboard] Re: Bagle bone boot is stopped at starting kernel

I found some of the following links helpful: https://groups.google.com/forum/#!searchin/beagleboard/nfs-uEnv|sort:date/beagleboard/X5jSWpPXegY/JxjNKU22A6kJ

[beagleboard] Re: jessie moved my WiFi cheese

8.3 image works! connmanctl> enable wifi Enabled wifi connmanctl> scan wifi Scan completed for wifi connmanctl> services ADP_EXT_Desk wifi_74da384261dd_4144505f4558545f4465736b_managed_psk ADP wifi_74da384261dd_414450_managed_psk CenturyLink5259

[beagleboard] Bagle bone boot is stopped at starting kernel

Hi , I am newbie and trying to compile kernel and using TFTP want to boot my beaglebone black . My problem is , my board gets hanged up at "starting Kernel " Log is as below . Thank you for any help . U-Boot# setenv ipaddr 192.168.1.7 U-Boot# setenv serverip 192.168.1.5 U-Boot#

[beagleboard] Re: jessie moved my WiFi cheese

I found in a thread "connman issues on latest Debian 8.4 release?" similar problems. I tried turning tethering off and connmanctl reported "Scan completed for wifi" this time, but still didn't report any access points. This

[beagleboard] Re: jessie moved my WiFi cheese

On Tuesday, July 12, 2016 at 8:34:25 PM UTC-7, Jeff Albrecht wrote: > > Since I last brought up wifi on a BBB rev c apparently a new way has > become standard for configuring wifi. connmanctl With a couple BBB rev C > that I have run Wheezy on with Edimax USB wifi dongles receiving a DHCP ip >

Re: [beagleboard] PRU remoteproc Tutorial

The PRU sends and receives messages to/from the ARM using the following functions pru_rpmsg_send and pru_rpmsg_receive. https://git.ti.com/pru-software-support-package/pru-software-support-package/blobs/bf955a05d3733ebe52d5783a1212b457b6e2f55c/lib/src/rpmsg_lib/pru_rpmsg.c#line29

[beagleboard] Weird Problem using GPIOs on BBB

I have interfaced a hardware using the 5 Gpios on BBB.I can talk to this device using GPIOs by manually (echoing 0 and 1 to the GPIOS) writing to it in the sys/class/gpio directory by first exporting the Gpios and configuring their directions and value.It works perfectly fine. But, When I try

[beagleboard] Connman & bone-debian-8.5-lxqt-2gb-armhf-2016-06-19-2gb.img

I downloaded & wrote the bone-debian-8.5-lxqt-2gb-armhf-2016-06-19-2gb.img image to a card. It doesn't seem to start up the ethernet connection on boot - I have to run sudo systemctl start connman.service from the serial terminal. Here's the full output. I tried

Re: [beagleboard] Re: PRU remoteproc Tutorial

Hi William, I have marked the release as "ready for cautious usage" merely because I seem to be the only user so far :) Once I see enough non-trivial projects using it, I will remove that wording. While it may not yet have matured into a production quality toolchain, I wouldn't call pru-gcc a