Re: [beagleboard] Re: BUS ERROR modprobe uio_pruss extram_pool_sz=0x800000

5 > > > >; > }; > > }; > }; > > //Allowed us to have the differents uio > fragment@1{ > target = <&pruss>; > __overlay__{ > status = "okay"; > pinctrl-nam

Re: [beagleboard] Which way BBBW or BBGW

rease over time. The cost will come down. On Mon, Dec 12, 2016 at 12:39 PM, Ross Morrison wrote: > On Mon, 12 Dec 2016 12:29:37 -0700 > William Hermans wrote: > > > The beaglebone black wireless seems to have HDMI, where the beaglebone > > green's do not. > >

Re: [beagleboard] Which way BBBW or BBGW

Well, that, and the beaglebone black wireless also does not have the two grove connectors. Which personally I found no use for. On Mon, Dec 12, 2016 at 12:29 PM, William Hermans wrote: > The beaglebone black wireless seems to have HDMI, where the beaglebone > green's do not. > &g

Re: [beagleboard] Which way BBBW or BBGW

The beaglebone black wireless seems to have HDMI, where the beaglebone green's do not. On Mon, Dec 12, 2016 at 12:14 PM, Ross Morrison wrote: > Now that the BBBW is out (in stock), my question is: Which one, the BBBW > or the BBGW board for a project? This project will be small volume > this yea

Re: [beagleboard] Re: BUS ERROR modprobe uio_pruss extram_pool_sz=0x800000

I suspect that you need to make these changes in the overlay file you use to initially configure the PRU's. On Mon, Dec 12, 2016 at 9:39 AM, TJF wrote: > Hi malkowki! > > Sorry, I cannot really help. Just some info: The same commands work well > for me on several kernel versions (3.8, 4.1 and 4.

Re: [beagleboard] Ony one parition on boot.

I use a combination of an NFS share, and a samba share. So . . . Linux server == NFS share to BBB, and Samba share to Windows workstation. What this nets me is the ability to edit files from Windows directly on the BBB. Or more correctly on the Linux server, which also hosts a share to the BBB.

Re: [beagleboard] Ony one parition on boot.

There is no FAT partition in the images since . . . over a year now. On Thu, Dec 8, 2016 at 4:56 AM, DragosP wrote: > > Hi, > > I run Debin beaglebone 4.4.36-ti-r72 on Beaglebone Black Rev C. > > I want to mount the FAT partition I see in Windows, to /media/folder_name > in BBB. > > Sending "lsb

Re: [beagleboard] PRU UART Debian 8.6

Anyway, sorry if that "stings" but hey, it's pretty much the truth. People have lives of their own and contribute what they can, when they can. But I would assume most people are pretty busy doing stuff for people who actually pay them. A lot of the time. On Tue, Dec 6, 2016 at 10

Re: [beagleboard] PRU UART Debian 8.6

Did you expect someone to do all the work for you ? But yes, I've experienced the same thing. So "free" as in beer, open sourced software. You get what you pay for. If you need something more, then it's up to you to do that for yourself. Or pay someone else to do it for you. On Tue, Dec 6, 2016 at

Re: [beagleboard] Re: ds18b20 with BBGW

Nope, actually that persons overlay file is wrong. So yeah I don;t know time to learn Linux and start troubleshooting your problems ;) On Mon, Dec 5, 2016 at 8:47 PM, William Hermans wrote: > Actually the last bit probably wont work because: > > william@beaglebone:~$ ls /sys/devices

Re: [beagleboard] Re: ds18b20 with BBGW

y one gpio bank. On Mon, Dec 5, 2016 at 8:28 PM, William Hermans wrote: > On Mon, Dec 5, 2016 at 7:30 PM, acheesehead wrote: > >> Tried your workflow today without success. Everything is OK up to the >> lsmod | grep w1 step. I only get the w1_gpio entry. I am not a Linux kernel &g

Re: [beagleboard] Re: ds18b20 with BBGW

On Mon, Dec 5, 2016 at 7:30 PM, acheesehead wrote: > Tried your workflow today without success. Everything is OK up to the > lsmod | grep w1 step. I only get the w1_gpio entry. I am not a Linux kernel > expert, so I don't know how to troubleshoot why the other entries aren't > showing up. > > I d

Re: [beagleboard] Re: ds18b20 with BBGW

/sys/bus/w1/devices/28-0647ddf6/w1_slave 19 01 4b 46 7f ff 07 10 eb : crc=eb YES 19 01 4b 46 7f ff 07 10 eb t=17562 Anyway, dead horse . . . point made? On Mon, Dec 5, 2016 at 6:41 PM, William Hermans wrote: > I repeated this process for P8.14, and it works fine. This is just to let >

Re: [beagleboard] Re: ds18b20 with BBGW

IO_ACTIVE_HIGH>; --- > gpios = <&gpio1 28 GPIO_ACTIVE_HIGH>; On Sat, Dec 3, 2016 at 3:11 PM, William Hermans wrote: > @ Sebastian > > Ah I forgot to mention loading capes from /boot/uEnv.txt. So . . . > > *william@beaglebone:~$* cat /boot/uE

Re: [beagleboard] Re: ds18b20 with BBGW

@ Sebastian Ah I forgot to mention loading capes from /boot/uEnv.txt. So . . . *william@beaglebone:~$* cat /boot/uEnv.txt |grep cape #cmdline=coherent_pool=1M quiet cape_universal=enable video=HDMI-A-1:1024x768@60e #cape_disable=capemgr.disable_partno= #cape_enable=capemgr.enable_partno= #cape_di

Re: [beagleboard] clone image

st an sdcard or multiples, in order to pull that off. So having an emmc flasher image of some sort is probably the quickest and least expensive way to go. Then you just put the sdcard into a board, and boot -> flash to emmc. Then move on to the next system. On Sat, Dec 3, 2016 at 2:29 PM, Will

Re: [beagleboard] clone image

Robert uses rsync I think for his cloning image( emmc flasher images ). But I think the best, easiest, and most consistent way to clone an image would be to use dd. This has the benefit of creating a bit for bit exact copy of the image in question. However, one downside to using dd is that if you'

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 w1 overlay automati

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 working fine. I was how

Re: [beagleboard] Re: ds18b20 with BBGW

2016 at 6:37 PM, William Hermans 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

Re: [beagleboard] Re: ds18b20 with BBGW

of 40-50 different boards . . . On Fri, Dec 2, 2016 at 6:33 PM, William Hermans wrote: > > 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 al

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 Image 2016-10-30 william

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 wrote: > Ah forgot the screenshot . . . > > On Thu, Dec 1, 2016 at 10:50 PM, William Hermans > wrote: > >> >> On Thu, Dec 1, 2016 at 10:39 PM, acheesehead >>

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 header values for the pins ha

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 wrote: > *1-wire workflow:* > > *Hardware setup:* > > Everything is directly connected v

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 cur

Re: [beagleboard] Re: ds18b20 with BBGW

or 5v, and a data pin to give 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

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 it right, I can

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 RS485, or is there

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 communicate with a central

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 get API for > writing a progr

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 (with respect to PGND)

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: http://www.ti.com/lsds/ti/tools-softwa

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 > > https://groups.google.com/forum/emb

Re: [beagleboard] Re: Beaglebone Black PRU Troubles

ded 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 wr

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 cant' seem to get conf

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 recommended for > a > > stable base. Many 3rd party node p

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

On Wed, Nov 16, 2016 at 8:28 AM, Robert Nelson wrote: > On Wed, Nov 16, 2016 at 6:00 AM, William Hermans > wrote: > > 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 > > a

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 actua

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 Ethernet for WiFi and > miniUSB f

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

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 (i.e.

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 wrote: > On Nov 15, 2016 11:28 PM, "William Hermans" wrote: > > > > Jason, > > > > What's the com

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 BeagleBoard.org communi

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 version of nodejs. > > So

Re: [beagleboard] PMIC does not charge battery

ly 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 wrote: > > > > We've been observing that the PMIC does not c

[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: > > > > >Now my only problem is how to read positio

Re: [beagleboard] BBG cannot connect via ethernet

o 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 wrote:

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. So

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, > >> > > > > What does that actually do

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 scri

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 bone_capemgr: part_number 'PRU-GPIO-BLINK', >

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 b

Re: [beagleboard] Embedded C - Function Declaration

to work around 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 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 &

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 the

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. > > I have been working on det

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

, 2016 at 7:08 PM, William Hermans wrote: > Additionally, I have no idea what 0x20h is meant to do. I'm assuming it's > either for pull up or pull down enable, but I have not checked the > documentation. I would think you could do away with the pullup / pulldown, > for an output.

Re: [beagleboard] Re: Surefire PRU Example

Can someone > please post a working PRU Pin P9.27 dts config with confirmation out put > like below? > > I am trying to build one that uses the *compatible = "bone-pinmux-helper"* > target atm to see if that makes a difference. syntax errors.... > > Neil >

Re: [beagleboard] Re: Surefire PRU Example

to do. In which 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 wrote: > So if my assumption that the left most bit of the first nibble is meant to > b

Re: [beagleboard] Re: Surefire PRU Example

l > > 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/LOaTgWH7Tpo/T0eote3TAQAJ in John's f

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 lsmod, I am seeing normal R

Re: [beagleboard] Re: Surefire PRU Example

p 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 at 5:39 PM, Greg wrote: >>>

Re: [beagleboard] Re: Surefire PRU Example

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 wrote: >> >>> I didn't adjust anything in the device tree. I never had to do that >&

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 board built with 4.4.12-ti-

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 uar

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 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 be the correct one.

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, whie

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 wrote: > > > On Mon, Nov 7, 2016 at 1:39 PM, Theodosis Ntegiannakis

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 in

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 pretty

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 been a long day > > > On Thur

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 options, visit http://beagl

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. > > Based on the comment "first v

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

t; > > 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 please be patient. > > I’m super busy right now. > > I be

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

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 wrote: >> >> HI Mark, >> >> So here: http://elinux.org/EBC_

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: > http://processors.wiki.ti.com/index.php/Li

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, customised MLO file - is there a way to put >> it >> > into MBR too? It has a size of

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 happ

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

hecked > the resistor, and it's the correct "size" (220 ohm). > > I remember reading in the book that the BBB is a little "fussy" about > things getting connected an disconnected. Is it good practice to do a > shutdown before I start moving wires around for te

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

ircuit. On Mon, Oct 24, 2016 at 6:32 PM, William Hermans 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 disconnecting

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 tha

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: william@beagleb

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 beag

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, Wi

[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. > > So

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 boar

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 */dev/spidev1.0 *causes data 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 wrote: > So, at this point I think I'll have to decompile both board files, and > then

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 s

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 wrote: > Overlay, meaning board file. > > On Wed, Oct 19, 2016 at 10:15 PM, William Hermans > wrote: > >

Re: [beagleboard] Re: eth0 mysteriously stops working

Overlay, meaning board file. On Wed, Oct 19, 2016 at 10:15 PM, William Hermans 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_hsmmc 4806.mmc: unable

Re: [beagleboard] Re: eth0 mysteriously stops working

mmc-overlay.dtb. Which is the same overlay file I was loading previous to rebuilding. On Wed, Oct 19, 2016 at 11:27 AM, William Hermans wrote: > Thanks again Robert, > > So I'll have to download the overlay board file repo, edit, and then > install but hummm. Been a while I ne

Re: [beagleboard] BBBlue student robot project

yUSB0 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 wrote: > > > On Wed, Oct 19, 2016 at 4:55 PM, Alvin Koontz > wrote

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