Re: [beagleboard] Re: ds18b20 with BBGW

On Sat, Dec 3, 2016 at 10:52 AM, Sebastián Sáez wrote: > Again, thanks Williams... that was it. > > I commented everything about P9.22 in ./bb.org-overlays/src/arm/ > univ-bbgw-00A0.dts > Then build and install with your instruccions :) > > Which is an elegant way to mount the

Re: [beagleboard] Re: ds18b20 with BBGW

On Fri, Dec 2, 2016 at 8:10 PM, Dennis Lee Bieber wrote: > Is that safe? I'd think the 5V would influence the swing of the > data > line, and I thought the BBB is supposed to only have 3.3V on the inputs. > You know, it ran over night no problems, the sensor still

Re: [beagleboard] Re: ds18b20 with BBGW

, William Hermans <yyrk...@gmail.com> wrote: > By the way, for informational purposes. The board file I'm loading( > am335x-boneblack-emmc-overlay.dtb ) for my BBB should also work with > BBG's too. At least I've used it with several Greens, and have had zero > problems with i

Re: [beagleboard] Re: ds18b20 with BBGW

ent boards . . . On Fri, Dec 2, 2016 at 6:33 PM, William Hermans <yyrk...@gmail.com> wrote: > > On Fri, Dec 2, 2016 at 2:37 PM, acheesehead <acheeseh...@gmail.com> wrote: > >> Thanks William. I'll try out your instructions on Mon. >> > > One thing I did n

Re: [beagleboard] Re: ds18b20 with BBGW

On Fri, Dec 2, 2016 at 2:37 PM, acheesehead wrote: > Thanks William. I'll try out your instructions on Mon. > One thing I did not mention last night was that I did all this one a beaglebone black running . . . william@beaglebone:~$ cat /etc/dogtag BeagleBoard.org Debian

Re: [beagleboard] Re: ds18b20 with BBGW

Note the "mode7" column to the far right. On Thu, Dec 1, 2016 at 10:51 PM, William Hermans <yyrk...@gmail.com> wrote: > Ah forgot the screenshot . . . > > On Thu, Dec 1, 2016 at 10:50 PM, William Hermans <yyrk...@gmail.com> > wrote: > >> >> On Th

Re: [beagleboard] Re: ds18b20 with BBGW

On Thu, Dec 1, 2016 at 10:39 PM, acheesehead wrote: > In all of the examples that I have seen, the P9.x -> GPIO bank.port > translates to GPIO (bank +1).port between lines in the overlay script. > That's incorrect if I understand what you're trying to say. the P8/P9

Re: [beagleboard] Re: ds18b20 with BBGW

I should probably note that when I connected everything up. I had the beaglebone powered down, and completely disconnected from everything. On Thu, Dec 1, 2016 at 10:28 PM, William Hermans <yyrk...@gmail.com> wrote: > *1-wire workflow:* > > *Hardware setup:* > > Everything

Re: [beagleboard] Re: ds18b20 with BBGW

*1-wire workflow:* *Hardware setup:* Everything is directly connected via jumper wires, with no additional components. DS18B20 PIN1 connected to Beaglebone P9.1 (ground) DS18B20 PIN2 connected to Beaglebone P9.22 (1-wire data) DS18B20 PIN3 connected to Beaglebone P9.5 (Vdd 5v) Remove any

Re: [beagleboard] Re: ds18b20 with BBGW

it a test. I'll even write, or more correctly modify the existing 1-wire dtb i linked to earlier to match your exact needs. As it just so happens I have to get 1-wire working myself. As I'm in the process of designing my own 1-wire slave devices. On Thu, Dec 1, 2016 at 8:47 PM, William Her

Re: [beagleboard] Re: ds18b20 with BBGW

On Thu, Dec 1, 2016 at 10:57 AM, Sebastián Sáez wrote: > Hi Dennis, > > I attach my circuit. It's connected to P9_22 with a pullup 4.7K resistor. > Now I'm trying with BBGW-blank-debian-8.5-seeed-iot-armhf-2016-06-19-4gb > > I try with this module from this tutorial >

Re: [beagleboard] Re: Beaglebone Black and RS485 Cape Interface

On Thu, Dec 1, 2016 at 5:06 AM, Bouni wrote: > Hi, > > thanks for your answers! > > I've searched the web yesterday in the evening for quite a long time and > stumbled up on this page: > > http://inspire.logicsupply.com/2014/09/beaglebone-rs-485- > communication.html > > If I got

Re: [beagleboard] Re: Beaglebone Black and RS485 Cape Interface

On Wed, Nov 30, 2016 at 1:21 PM, Bouni wrote: > Hi, > > indeed i want to go for Modbus TCP, but unfortunately my ventilation > system has only Modbus RTU. The BB will act as a Gateway between Modbus TCP > and Serial Modbus RTU. > Does your ventilation system output Modbus over

Re: [beagleboard] Re: Beaglebone Black and RS485 Cape Interface

On Wed, Nov 30, 2016 at 11:45 AM, Bouni wrote: > Hi, > > I have almost the same situation. I have a Beaglebone Green and the > Waveshare RS485 CAN CAPE mentioned in the first post. > In the near future I want to use RS485 to build a Modbus TCP to Modbus RTU > Gateway to

Re: [beagleboard] API for configure USB port of beaglebone green wireless board

On Tue, Nov 29, 2016 at 4:59 AM, Gourav wrote: > Hello, > > I currently using BeagleBone Green Wireless board for transferring the > data from host PC to BeagleBone Board using USB. But I unable to find API > for USB for this Board.Please help me to know from where I

Re: [beagleboard] 5.2 Volt / 1A switching adapter as power supply. Safe to use with Beagle Bone Black?

Should also be aware that the given plug with that power supply *could* potentially be reversed polarity. In which case it'll fry your beaglebone. On Tue, Nov 29, 2016 at 12:34 PM, evilwulfie wrote: > from the PMIC data sheet > > Absolute Maximum Ratings > Supply voltage

Re: [beagleboard] Help designing-in fast ADC (e.g. Analog Devices AD7761) for sonar.

Perhaps you should be thinking of using an external dedicated processor for your application ? Something that has decent on die ADCs. Something like the TI C2000 line ? There are many dev kits here which include but are not limited to just the C2000 products:

Re: [beagleboard] Re: Beaglebone Black can't get USB audio to work

On Wed, Nov 23, 2016 at 9:00 AM, Jim S wrote: > Thanks! I take it that is done on the BBB itself? (rather than cross > compiled) Any issue with doing this over ssh? (particularly the selecting > of kernel configuration boxes) > > I saw in another thread > >

Re: [beagleboard] Re: Beaglebone Black PRU Troubles

up not having to mess around with > any custom device trees. Hopefully that information helps someone else > struggling with the same thing I was. > > On Sunday, November 20, 2016 at 7:25:06 PM UTC-5, William Hermans wrote: >> >> On Sun, Nov 20, 2016 at 4:31 PM, Zach B <

Re: [beagleboard] Re: Beaglebone Black PRU Troubles

On Sun, Nov 20, 2016 at 4:31 PM, Zach B wrote: > Thanks for the information Greg. > > Robert & everyone, > I was digging into that link you sent about which universal overlay gets > loaded at boot. I have tried modifying my uEnv.txt file to enable different > overlays but i

Re: [beagleboard] Re: nodejs, v4.x/v6.x transition

On Wed, Nov 16, 2016 at 1:21 PM, Robert Nelson wrote: > On Wed, Nov 16, 2016 at 11:18 AM, mtn_beagle > wrote: > > > > > >> Just to note what is on the Nodered.org site: > > > > > > Note: Node.js 7.x is under active development and is not

Re: [beagleboard] Re: [beagle-alpha] nodejs, v4.x/v6.x transition

On Wed, Nov 16, 2016 at 8:28 AM, Robert Nelson <robertcnel...@gmail.com> wrote: > On Wed, Nov 16, 2016 at 6:00 AM, William Hermans <yyrk...@gmail.com> > wrote: > > I think it may be wise to at least provide build instructions for 4.x. In > > case somet

Re: [beagleboard] Re: [beagle-alpha] nodejs, v4.x/v6.x transition

I think it may be wise to at least provide build instructions for 4.x. In case something someone needs in addition to the packages you provide are reasonably guaranteed to be usable. If not by one version but by another. Anyway I can provide build instructions for 4.2.6( from source ). It's

Re: [beagleboard] Announcement: Debian 8.6 released for all boards

On Wed, Nov 16, 2016 at 4:35 AM, Jason Kridner wrote: > BeagleBone Black Wireless. Doesn't have the hub or Grove connectors of the > SeeedStudio BeagleBone Green Wireless, but is mechanically and electrically > compatible with BeagleBone Black outside of swapping

Re: [beagleboard] tpa81(sensor temperatur)

So, i2c_bus=3,100 probably won't work for your case. You'll probably have replace "3" to reflect the proper I2C bus you're using. But in case you're using a bus thats already in use ( 0, or 2 ), I'd probably not try the above. On Tue, Nov 15, 2016 at 10:45 PM, William Hermans <yyrk

Re: [beagleboard] tpa81(sensor temperatur)

http://permalink.gmane.org/gmane.linux.distributions.gumstix.general/60029 > The signals on the bus are the same as shown in my previous posted picture. > The error is as follows: > error I2C_RDWR errno=121(Remote I/O error) Generally, that means that the remote didn't respond properly

Re: [beagleboard] Announcement: Debian 8.6 released for all boards

Can't say I'm interested in the BBGW _at_all_. But I do think the BBG is pretty nice. On Tue, Nov 15, 2016 at 10:30 PM, Robert Nelson <robertcnel...@gmail.com> wrote: > On Nov 15, 2016 11:28 PM, "William Hermans" <yyrk...@gmail.com> wrote: > > > > Jason,

Re: [beagleboard] Announcement: Debian 8.6 released for all boards

Jason, What's the compelling reason for those of us who already have well established images to shift to this one ? Honestly, I can't see one. Besides . . . apt-get upgrade . . . On Mon, Nov 14, 2016 at 1:54 PM, Jason Kridner wrote: > Thanks to Robert and the rest of the

Re: [beagleboard] nodejs, v4.x/v6.x transition

4.6.2 is easy to build from source Robert. It just takes a little bit of time to compile directly on a beaglebone is all. 2-3 hours, is all. On Tue, Nov 15, 2016 at 8:16 PM, Robert Nelson wrote: > Hey Everyone, > > Over the weekend, there was a few requests to bump our

Re: [beagleboard] PMIC does not charge battery

ge is probably damaged and should not be charged. > > I don't know how the PMIC decides the charge profile, though, so I don't > know what it might be doing. > > > On Nov 13, 2016, at 14:05 , William Hermans <yyrk...@gmail.com> wrote: > > > > We've been observing that th

[beagleboard] PMIC does not charge battery

We've been observing that the PMIC does not charge a battery that is below a certain voltage threshold. So obviously, when a battery is at or around 0v it will not charge that battery. As well as when the battery is at around 1v the PMIC still will not charge. I was wondering if this is normal

Re: [beagleboard] Re: Use eQEP on 4.4.23-ti-r51 kernel

It's a simple read. Learn how to read a file in Python, and your problem will be solved. On Sun, Nov 13, 2016 at 12:50 PM, Dennis Lee Bieber wrote: > On Sun, 13 Nov 2016 10:44:05 -0800 (PST), Theodosis Ntegiannakis > declaimed the > following: >

Re: [beagleboard] BBG cannot connect via ethernet

not have other means to connect to the beaglebone, to change some configuration files. Like a serial debug cable, have g_serial setup and running properly, or booting from an sdcard, then mounting the eMMC long enough to edit files. On Fri, Nov 11, 2016 at 6:16 PM, William Hermans <yyrk...@gmail.

Re: [beagleboard] BBG cannot connect via ethernet

So . . . # Ethernet/RNDIS gadget (g_ether) # ... or on host side, usbnet and random hwaddr iface usb0 inet static address 192.168.7.2 netmask 255.255.255.252 network 192.168.7.0 gateway 192.168.7.1 This is what a stock system should be setup as for USB ethernet.

Re: [beagleboard] Re: Beaglebone Black PRU Troubles

On Fri, Nov 11, 2016 at 12:45 PM, Robert Nelson wrote: > >> univ-emmc is the userspace overlay we automatically load on bootup > >> > >> open /boot/uEnv.txt > >> > >> you'll notice a cape_universal=enable > >> > >> remove that and reboot > >> > >> Regards, > >> > > > >

Re: [beagleboard] Re: Beaglebone Black PRU Troubles

Hi Zach, So, first of all. Yes removing the line , commenting it out in uEnv.txt will keep from loading the overlay at boot. As for removing it from the initramfs, I would assume if you reversed the process. e.g. remove the line from uEnv.txt. then remove the file from /lib/firmware, that the

Re: [beagleboard] Re: Beaglebone Black PRU Troubles

On Fri, Nov 11, 2016 at 12:26 PM, Robert Nelson wrote: > On Fri, Nov 11, 2016 at 12:53 PM, Zach B wrote: > > wow that is incredible useful, I didn't even realize that is what dmesg > did. > > Here is the output I got: > > [ 2117.571792] bone_capemgr

Re: [beagleboard] Do I really need a USB-to-FTDI cable to see the U-boot prompt? Will it not work on micro-HDMI?

You do not have to buy a FTDI cable. It could be any decent cable, that does not necessarily cost as much as FTDI. For example my buddy and I ordered a couple of PL2303HX cables off ebay for like $5-6 usd shipped. My point here is that you could just simply pay $2-$3 out of your pocket, and just

Re: [beagleboard] Embedded C - Function Declaration

this feature, but it depends on which std as to which options you have, On Thu, Nov 10, 2016 at 1:46 AM, William Hermans <yyrk...@gmail.com> wrote: > *#1 Your code as is won't compile. Period.* > william@beaglebone:~$ pru-gcc -o main main.c > main.c:10:13: error: redefinition of 'tu

Re: [beagleboard] Embedded C - Function Declaration

*#1 Your code as is won't compile. Period.* william@beaglebone:~$ pru-gcc -o main main.c main.c:10:13: error: redefinition of 'turnOn' static void turnOn(){ ^~ main.c:5:13: note: previous definition of 'turnOn' was here static void turnOn(){ ^~ *#2 If you use

Re: [beagleboard] Re: Beaglebone Black PRU Troubles

On Tue, Nov 8, 2016 at 11:08 AM, Greg wrote: > I think I know exactly what is wrong. You need to activate the Remoteproc > PRU framework. This is no longer active by default. > Robert Nelson's script which is available via Github repository will fix > the problem. > >

Re: [beagleboard] Re: Surefire PRU Example

> > Then here: http://beaglebone.cameon.net/home/pin-muxing says a couple of > my assumptions were wrong. 0x25h seems correct. Blah, I got it wrong again. Seems 0xD was correct. But anyway, you have the means to do what you need. Just make sure you read the second link correctly. I got it wrong

Re: [beagleboard] Re: Surefire PRU Example

case a value of 0xD would be sufficient. For the mux mode( if you do not need a pull up or pull down) Assuming my assumption is correct . . . On Mon, Nov 7, 2016 at 7:04 PM, William Hermans <yyrk...@gmail.com> wrote: > So if my assumption that the left most bit of the first nibble

Re: [beagleboard] Re: Surefire PRU Example

gt; current state? > > Neil > > On Monday, November 7, 2016 at 6:05:53 PM UTC-7, William Hermans wrote: >> >> It's also described here: https://groups.google.com/foru >> m/#!searchin/beagleboard/Robert$20Nelson$20remoteproc|sort: >> date/beagleboard/LOaTgWH7T

Re: [beagleboard] Re: Surefire PRU Example

On Mon, Nov 7, 2016 at 5:39 PM, Greg wrote: > I didn't adjust anything in the device tree. I never had to do that > before to successfully run the Remoteproc examples. The only thing I have > ever had to tweak is the pull-up/down resistors in the pads. > > When I run

Re: [beagleboard] Re: Surefire PRU Example

software.ca> > wrote: > >> Look up in this thread to Robert's post I believe both are disabled. You >> have to choose one and enable it. >> >> On Monday, November 7, 2016 at 5:52:59 PM UTC-7, William Hermans wrote: >>> >>> >>> On Mon, Nov 7, 2016

Re: [beagleboard] Re: Surefire PRU Example

ieve both are disabled. You > have to choose one and enable it. > > On Monday, November 7, 2016 at 5:52:59 PM UTC-7, William Hermans wrote: >> >> >> On Mon, Nov 7, 2016 at 5:39 PM, Greg <soapy...@comcast.net> wrote: >> >>> I didn't adjust anythi

Re: [beagleboard] Re: Surefire PRU Example

On Mon, Nov 7, 2016 at 5:07 PM, Greg wrote: > I'm also using 4.4.27-ti-r62. In particular, the IOT distribution. > > I'm seeing strange behavior attempting to run Remoteproc. It's like the > PRUs are missing from the device tree. I think. > > I'm comparing a working

Re: [beagleboard] Use PWM and UART at the same time

On Mon, Nov 7, 2016 at 3:56 PM, Theodosis Ntegiannakis < tntegianna...@gmail.com> wrote: > I tried twice to implement my own overlay but I gave up because I had a > significant lack of knowledge at this point. > > Finally i used cape-universala (in which pwm works fine) and enabled uart2 > and

Re: [beagleboard] Re: Surefire PRU Example

Ah, I think I see. Perhaps the left most bit is to indicate input( 0 ) or output( 1 ). On Mon, Nov 7, 2016 at 2:32 PM, William Hermans <yyrk...@gmail.com> wrote: > I'm not sure what the first one i trying to do other than put the pin in > GPIO mux mode. > > The second seems to

Re: [beagleboard] Re: Surefire PRU Example

I'm not sure what the first one i trying to do other than put the pin in GPIO mux mode. The second seems to be the correct one. I'd have to look up what 0x20 is ( probably pull up or down ) but mux mode 5, and 6 is generally PRU mux mode. DO also keep in mind mode 5, and 6, one mode is input,

Re: [beagleboard] Use PWM and UART at the same time

On Mon, Nov 7, 2016 at 2:18 PM, Charles Steinkuehler < char...@steinkuehler.net> wrote: > On 11/7/2016 2:38 PM, Theodosis Ntegiannakis wrote: > > > > On Monday, November 7, 2016 at 3:29:07 PM UTC+2, Charles Steinkuehler > wrote: > > > > You have to set the pins to the proper pinmux values for

Re: [beagleboard] Use PWM and UART at the same time

On Mon, Nov 7, 2016 at 1:39 PM, Theodosis Ntegiannakis < tntegianna...@gmail.com> wrote: > > > On Monday, November 7, 2016 at 9:19:58 PM UTC+2, William Hermans wrote: >> >> > and with sudo sh -c "echo 'BB-UART2' > /sys/devices/platform/bone_cap >>&

Re: [beagleboard] Use PWM and UART at the same time

So if this continues to be a problem for you. Once you unload a cape, you should instead just reboot. This is not ideal, but it's what we have right now . . . On Mon, Nov 7, 2016 at 2:18 PM, William Hermans <yyrk...@gmail.com> wrote: > > > On Mon, Nov 7, 2016 at 1:39 PM, Theodos

Re: [beagleboard] WakeUp GPIO features is missing

william@beaglebone:~$ ls /sys/class/gpio/gpio3 active_low device direction *edge* power subsystem uevent value Set the "edge" file to "rising", "falling:, or "both". You can then perform a blocking read on the value file. Using poll(), select(), etc. This is about as close as it gets for

Re: [beagleboard] Use PWM and UART at the same time

> > > and with sudo sh -c "echo 'BB-UART2' > /sys/devices/platform/bone_ > capemgr/slots" > > i get sh: echo: I/O-error > > This generally means the cape couldn't be loaded. You can sometimes > find more detail at the end of dmesg output, but failures when trying > to load capes are usually

Re: [beagleboard] Re: Trying to build tlv430

Paul, Have you copied the exact error message you're getting on the cmd line and pasted it to us yet ? If so, I'm not seeing it . . . On Fri, Nov 4, 2016 at 11:14 AM, wrote: > Helps also if I get the right sh in the tools directory... I meant > rebuild.sh. It's

Re: [beagleboard] BBB: schizophrenic MMC names

On Thu, Nov 3, 2016 at 2:19 PM, Robert Nelson wrote: > CONFIG_DEBUG_INFO is now disabled... The dbg symbols, while smaller > then they use to be, still just ended up taking up too much server > space. ;) > > heheh, excellent. That worked out good then ;) -- For more

Re: [beagleboard] BBB: schizophrenic MMC names

On Thu, Nov 3, 2016 at 9:19 AM, Gary Thomas wrote: > On 2016-11-03 15:22, Robert Nelson wrote: > >> On Thu, Nov 3, 2016 at 9:18 AM, Gary Thomas wrote: >> >>> On 2016-11-03 15:11, Robert Nelson wrote: >>> > Thanks, I'll investigate these changes.

[beagleboard] Re: [beagle-alpha] v4.9.x-ti now open for testing...

should have something for this in the next couple of week or so. > > > > Heavy rework, and I’d probably have to touch base with Beaglelogic > > at all for a new PRU driver (continuation of the old one in 3.8). > > > > If anyone is interested drop me an email but pleas

Re: [beagleboard] Re: Dallas 1-Wire BeagleBone Black

in this group and 100 > views of the eLinux page. > > --Mark > > On Thursday, October 27, 2016 at 10:38:58 AM UTC-4, Jason Kridner wrote: >> >> >> >> On Oct 26, 2016, at 3:20 PM, William Hermans <yyr...@gmail.com> wrote: >> >> HI Mar

Re: [beagleboard] Beaglebone Green and PRU "Programmable Real-Time Unit" Interface to ADC using RemoteProc and RPMsg

Jason, Well, my point was that it would be nice to have a list of required files for a PRU / remoteproc project. Something that describes the minimal required files, and what each file purpose is. On Thu, Oct 27, 2016 at 7:54 AM, Jason Kridner wrote: >

Re: [beagleboard] Beaglebone Green and PRU "Programmable Real-Time Unit" Interface to ADC using RemoteProc and RPMsg

Looks good ! You know I just realized something that no one is doing that might be helpful to others when first attempting a project using remoteproc. An explanation of what the various files are for. For example AM335x_PRU.cmd looks to be some sort of configuration file, perhaps for the PRU's .

Re: [beagleboard] No MLO-file on newer BBG's?

On Wed, Oct 26, 2016 at 2:57 PM, Jason Kridner wrote: > > > On Tue, Oct 25, 2016 at 1:09 PM Robert Nelson > wrote: > >> On Tue, Oct 25, 2016 at 3:04 PM, Paul Plankton >> wrote: >> > That's cool! I use an own,

Re: [beagleboard] Re: Dallas 1-Wire BeagleBone Black

HI Mark, So here: http://elinux.org/EBC_Exercise_31_Dallas_1-Wire#Reading_the_DS12B20 Shouldn't The *t=24437* is the temperature in C times 1000. Warm up the probe and see > what happens to the temp. > > Be: The *t=24437* is the temperature in C times .001. Warm up the probe and see > what

Re: [beagleboard] Re: LED won't go off (Chapter 6 exercise)

s.. > > mz > > On Monday, October 24, 2016 at 7:32:59 PM UTC-6, William Hermans wrote: >> >> I'd check /sys/class/gpio/gpio49/direction . . . >> >> william@beaglebone:~$ cat /sys/class/gpio//gpio49/direction >> in >> >> Make sure its "out

Re: [beagleboard] Re: LED won't go off (Chapter 6 exercise)

, Oct 24, 2016 at 6:32 PM, William Hermans <yyrk...@gmail.com> wrote: > I'd check /sys/class/gpio/gpio49/direction . . . > > william@beaglebone:~$ cat /sys/class/gpio//gpio49/direction > in > > Make sure its "out" > > After that, I'd start by disconne

Re: [beagleboard] Re: LED won't go off (Chapter 6 exercise)

I'd check /sys/class/gpio/gpio49/direction . . . william@beaglebone:~$ cat /sys/class/gpio//gpio49/direction in Make sure its "out" After that, I'd start by disconnecting P9.23 from the circuit, then check with a volt meter that the pin isn't somehow damaged. P9.1 and P9.2 are both ground on

Re: [beagleboard] Re: LED won't go off (Chapter 6 exercise)

Ok, first I'm not an EE, so if I make a statement that's obviously wrong from that perspective. . . Anyway . . . I have a custom cape with several LED's on it here. Connected to a Beagelbone green. LED is on: william@beaglebone:~$ cat /sys/class/gpio/gpio110/value 1 LED goes off:

Re: [beagleboard] Re: LED won't go off (Chapter 6 exercise)

Removing the gpio pin from the sysfs entries probably won't help. So why don't you be verbose with us, and tell us everything you've done, including setup, Linux image date, and kernel used. On Mon, Oct 24, 2016 at 12:06 PM, mzimmers wrote: > Oops...forgot the pic: > > >

Re: [beagleboard] BBBlue student robot project

Id, double check and document everything when trying ot setup the serial debug port on the Beaglebone blue. Which to me going form pictures on the internet. Just seems to be *another* beaglebone, but with a blue PCB. In other words. It appears to be very similar to if not exactly the same as a

Re: [beagleboard] Re: eth0 mysteriously stops working

So, I'm still getting "Write failed: broken pipe" using ssh from my debian support system to the beaglebone. This is not a timeout issue at all. As in the ssh session I'm running nload which constantly displays eth0 bandwidth usage. On Thu, Oct 20, 2016 at 10:16 PM, William Her

[beagleboard] Re: eth0 mysteriously stops working

:41:44 PM UTC-7, William Hermans wrote: > > I had a board a few days ago that just stopped working as far as ssh went. > So, I checked the LEDs on my GbE switch, and the lights were not lit. > Checking further, I found that the LEDs on the beaglebone were also not lit. > >

Re: [beagleboard] Re: eth0 mysteriously stops working

Ok,I had to modify my workflow, but I do believe I got the changes put into place. Not sure why Robert's way was not working, but I'm used to thinking outside the box, or looking at multiple ways to achieve the same results . . . You board file name, and kernel version will depend on which

Re: [beagleboard] Changing SPI0 Clock Rate

On Thu, Oct 20, 2016 at 8:56 PM, George Rung wrote: > > I am able to get *SPI0 *working on the BeagleBone Black by using only > *config-pin* commands: > > config-pin P9_17 spi > config-pin P9_18 spi > config-pin P9_21 spi > config-pin P9_22 spi > > Then writing to

Re: [beagleboard] Re: eth0 mysteriously stops working

So after decompiling the two files and comparing with diff, then piping to a file . . . the diff file is literally 2186 lines in length . . . wtf ? On Thu, Oct 20, 2016 at 5:25 PM, William Hermans <yyrk...@gmail.com> wrote: > So, at this point I think I'll have to decompile both bo

Re: [beagleboard] How can i install Virtualbox on my Beaglebone black ? i am using beaglebone 7.9 wheezy version.

First, you're going to need the right software architecture, but as you've already seen. I seriously doubt you're going to find an armhf ABI compatible binary. Then, even if you did find a compatible armhf binary, assuming virtualbox could, or would run off such minimal resources. It would be so

Re: [beagleboard] Re: eth0 mysteriously stops working

So, at this point I think I'll have to decompile both board files, and then run diff to see what's different. On Wed, Oct 19, 2016 at 10:16 PM, William Hermans <yyrk...@gmail.com> wrote: > Overlay, meaning board file. > > On Wed, Oct 19, 2016 at 10:15 PM, William Hermans <

Re: [beagleboard] Re: eth0 mysteriously stops working

Overlay, meaning board file. On Wed, Oct 19, 2016 at 10:15 PM, William Hermans <yyrk...@gmail.com> wrote: > Yeah I'm locked in a boot loop ending here: > > Starting kernel ... > > [3.341689] CPUidle arm: CPU 0 failed to init idle CPU ops > [3.347892] omap_hs

Re: [beagleboard] Re: eth0 mysteriously stops working

. Which is the same overlay file I was loading previous to rebuilding. On Wed, Oct 19, 2016 at 11:27 AM, William Hermans <yyrk...@gmail.com> wrote: > Thanks again Robert, > > So I'll have to download the overlay board file repo, edit, and then > install but hummm. B

Re: [beagleboard] BBBlue student robot project

or /dev/ttyACM0. It depends on which serial to USB device you're using. Here, I use a PL2303hx based serial to USB cable, and that shows up as /dev/ttyUSB0. On Wed, Oct 19, 2016 at 8:08 PM, William Hermans <yyrk...@gmail.com> wrote: > > > On Wed, Oct 19, 2016 at 4:55 PM, Alvin K

Re: [beagleboard] Time beween pulses

Oh, and right. For all intents and purpose concerning application performance. cout with C++ and printf() in C would roughly be the same. On Wed, Oct 19, 2016 at 8:48 PM, William Hermans <yyrk...@gmail.com> wrote: > Additionally, I'm not really sure if the above description I gave will

Re: [beagleboard] Time beween pulses

such an application. *UNLESS* you were to pipe the output of that application to a file. LIke: ./foo > somefile.txt On Wed, Oct 19, 2016 at 8:31 PM, William Hermans <yyrk...@gmail.com> wrote: > > > On Wed, Oct 19, 2016 at 4:50 PM, Arthur Caio <arth...@gmail.com> wrote: > >

Re: [beagleboard] Time beween pulses

On Wed, Oct 19, 2016 at 4:50 PM, Arthur Caio wrote: > Hello you all! > > I need to calculate hot much time it takes for an input to go from LOW to > HIGH and then to LOW again. Basically, I want to know the period of a > square wave generated by the LM555 timer. > > I am using

Re: [beagleboard] BBBlue student robot project

On Wed, Oct 19, 2016 at 4:55 PM, Alvin Koontz wrote: > Hi, I am one of the students who was given the BBBlue to interface with > the robot, We have the latest image on an SD card in the BBBlue, on boot > the leds appear to go through the normal boot routine. However we are

Re: [beagleboard] Re: eth0 mysteriously stops working

get the chance. SO others can test, and potentially fix the same issue if needed. On Wed, Oct 19, 2016 at 11:15 AM, Robert Nelson <robertcnel...@gmail.com> wrote: > On Wed, Oct 19, 2016 at 1:09 PM, William Hermans <yyrk...@gmail.com> > wrote: > > Thanks Robert, > > &g

Re: [beagleboard] Re: eth0 mysteriously stops working

I would think both, but honestly don't know . . . On Wed, Oct 19, 2016 at 11:09 AM, William Hermans <yyrk...@gmail.com> wrote: > Thanks Robert, > > I'll check that out, So when you sasy "remove the sleeps". I just delete > "sleep" from pinctrl-names = &q

Re: [beagleboard] Re: eth0 mysteriously stops working

robertcnel...@gmail.com> wrote: > On Wed, Oct 19, 2016 at 12:54 PM, William Hermans <yyrk...@gmail.com> > wrote: > > > > > > On Wed, Oct 19, 2016 at 3:24 AM, Graham <gra...@flex-radio.com> wrote: > >> > >> I have two BBG units that

Re: [beagleboard] Re: eth0 mysteriously stops working

On Wed, Oct 19, 2016 at 3:24 AM, Graham wrote: > I have two BBG units that I use as headless servers, with only access > through Ethernet. Both have been running without reboot for multiple > months without any issues. I think that I mentioned that I did have a BBB > do

Re: [beagleboard] kernel tools/iio

https://kernelnewbies.org/IIO_tasks These tasks are for you to get familiar with the IIO subsystem. You do not > need to claim these via the Outreachy tasks page. *For IIO related > questions you can join #linux-iio IRC channel (server irc.oftc.net > ). * > Please email your

[beagleboard] eth0 mysteriously stops working

I had a board a few days ago that just stopped working as far as ssh went. So, I checked the LEDs on my GbE switch, and the lights were not lit. Checking further, I found that the LEDs on the beaglebone were also not lit. So I disconnected the ethernet jack on both ends and reseated. Nothing.

Re: [beagleboard] Installing SGX drivers - omaplfb & pvrsrvkm not loaded

> > On a secondary remark, why is TI seemingly making it so hard for people to > develop applications targeting their processors, using community tools? The > easy answer is evidently to promote vendor tools, but in the end they still > end up selling chips even though people don't buy the

Re: [beagleboard] Re: Missing ports and componants, need clarification and info to turn on.

On Sat, Oct 15, 2016 at 12:37 PM, Gerald Coley wrote: > > What I would do with this board to use it and power it, is use the power jack holes. Whether or not anyone else could do > this, I cannot say. Then again, what I would do is only speculation on my part because I

Re: [beagleboard] bone_capemgr bone_capemgr: loader: failed to load slot-4 (prio 0)

one of the scripts can also deal with this. Here: https://github.com/rcn-ee/repos/blob/master/bb-bb- customizations/suite/jessie/debian/dtbo bb-customizations deb package On Sat, Oct 15, 2016 at 11:24 AM, William Hermans <yyrk...@gmail.com> wrote: > > So, it turns out you *do* ha

Fwd: [beagleboard] bone_capemgr bone_capemgr: loader: failed to load slot-4 (prio 0)

So, it turns out you *do* have to modify the initramfs image, in order to load a custom overlay file at boot. The hook for /etc/default/capemgr does not seem to be in place for the image I'm using. Which is fine since this is just an init script anyhow, which I feel is the wrong way to do this.

Re: [beagleboard] Re: Missing ports and componants, need clarification and info to turn on.

> > With the R-Pi's it is back to power the unit from the GPIO because it is > not regulated from there and one can blow out the board. > I wouldn't say it's bad per se. Assuming 'back' was meant to be 'bad' I'd say that it would be bad to apply unregulated power through the expansion header. I

Re: [beagleboard] Re: Missing ports and componants, need clarification and info to turn on.

Hi Gerald, I think he is asking if the board can be powered via the P9 header. Or is this not possible either ? Like insinuated in the image below. http://zewaren.net/site/sites/default/files/imagepicker/1/bbb_can_pinout.jpg On Sat, Oct 15, 2016 at 11:04 AM, Gerald Coley

Re: [beagleboard] Re: Copy a device tree file in /sys/firmware

device tree overlays go into /lib/firmware On Sat, Oct 15, 2016 at 8:14 AM, Dennis Lee Bieber wrote: > On Sat, 15 Oct 2016 01:53:34 -0700 (PDT), Sebastien Capel > declaimed the > following: > > >Hello, > >I'm following a tutorial to learn to

Re: [beagleboard] Android for Beagle

Hello Chris, Looks good ! I was going to ask how this differs from Andrew H's Android on Beaglebone, but after glancing at your page it seems obvious to me. I think what would be beneficial to all is an explanation how Android differs from say Debian. In the context of how the hardware

Re: [beagleboard] ARM->PRU->ARM interrupts for data transfer from ARM->PRU

ri, Oct 14, 2016 at 8:48 AM, William Hermans <yyrk...@gmail.com> wrote: > awesome! Thank you! Do you know where I can find a good example of using >> shared memory? I am wondering if I might be better off using shared memory >> instead. Does shared memory work both ways

<    2   3   4   5   6   7   8   9   10   11   >