Re: [beagleboard] cloud9 remove root access Debian 8

On Friday, July 21, 2017 at 4:47:12 PM UTC-7, RobertCNelson wrote: > > On Fri, Jul 21, 2017 at 6:39 PM, Sebastián Sáez > wrote: > > Hi, > > > > In Debian stretch, cloud9 is no longer root > > > > Is it possible to remove root access to cloud 9 for Debian 8? > > Yes, just a few changes requ

Re: [beagleboard] Re: Beaglebone as a USB router (Share ethernet connection over USB)

> > > > Thanks for the suggestions. I'll have a look at the suggested logging and see if that provides any clues. In terms of the PC side, I am using Windows 10. Everything looks like it is ready to receive internet, but internet is never detected. Looking here: https://wiki.archlinux.org/i

[beagleboard] Beaglebone as USB Router (Shares internet via USB to computer)

I have found a lot of posts for Sharing the main computer's internet with the Beaglebone, but I was actually considering the reverse. The beaglebone is connected to a Windows Laptop. The Beaglebone has internet access via ethernet cable / wifi. The laptop does not. How would one go about sharing

Re: [beagleboard] Using a device table overlay to disable the onboard RTC on the beaglebone black

On Tue, Feb 20, 2018 at 7:28 PM, Robert Nelson wrote: > On Tue, Feb 20, 2018 at 6:54 PM, ferdster wrote: >> Can't boot back after step 5. I am running from eMMC, if that makes a >> difference. >> >> U-Boot SPL 2018.03-rc2-2-ged1e504391 (Feb 16 2018 - 15:02:58 -0600) >> Trying to boot from MMC

[beagleboard] Re: Using ROS (rosserial) on PocketBeagle

I assume you want to stream data from the PocketBeagle to another PocketBeagle which comes from / goes to ROS. So why don't you create a rospy node on the side that contains ROS? You can, for example, use pickle to serialize Python objects, or maybe protobuf, json or bson. It really depends on

[beagleboard] Re: Getting EQEP2 to work on the PocketBeagle

Hi, Answering myself: upgrading to bone-debian-9.3-iot-armhf-2018-01-28-4gb.img, with kernel 4.9.78-ti-r94 improves the situation. The pins can be configured with config-pin but sysfs entries for the eqep do not appear, I assume that is a bug? The overlays I created earlier now work though, s

Re: [beagleboard] Using a device table overlay to disable the onboard RTC on the beaglebone black

On Wed, Feb 21, 2018 at 9:30 AM, Robert Nelson wrote: > On Tue, Feb 20, 2018 at 7:28 PM, Robert Nelson > wrote: >> On Tue, Feb 20, 2018 at 6:54 PM, ferdster wrote: >>> Can't boot back after step 5. I am running from eMMC, if that makes a >>> difference. >>> >>> U-Boot SPL 2018.03-rc2-2-ged1

Re: [beagleboard] Using a device table overlay to disable the onboard RTC on the beaglebone black

Now it won't boot after upgrading the kernel in step 2 (still running off eMMC): Loading, please wait... starting version 232 [3.031626] usb 1-1: new high-speed USB device number 2 using musb-hdrc [3.193198] usb 1-1: New USB device found, idVendor=05e3, idProduct=0610 [3.200011] usb 1-

Re: [beagleboard] Using a device table overlay to disable the onboard RTC on the beaglebone black

On Wed, Feb 21, 2018 at 10:26 AM, ferdster wrote: > Now it won't boot after upgrading the kernel in step 2 (still running off > eMMC): > Loading, please wait... > starting version 232 > [3.031626] usb 1-1: new high-speed USB device number 2 using musb-hdrc > [3.193198] usb 1-1: New USB dev

[beagleboard] Re: TinyDRM ST7735 with BeagleBone?

On 02/20/2018 10:19 PM, Drew Fustini wrote: On Sat, Feb 17, 2018 at 7:06 PM, David Lechner wrote: Hi Drew, I haven't used it with a BeagleBone. Creating a device tree overlay should be easy though. If you want to use the backlight, you need to create a node at the root level like this:

Re: [beagleboard] Using a device table overlay to disable the onboard RTC on the beaglebone black

BTW, this is on a SeeedStudio Green Wireless. loading /boot/vmlinuz-4.16.0-rc2-bone3 ... 10183168 bytes read in 659 ms (14.7 MiB/s) uboot_overlays: [uboot_base_dtb=am335x-boneblack-uboot-univ.dtb] ... uboot_overlays: Switching too: dtb=am335x-boneblack-uboot-univ.dtb ... loading /boot/dtbs/4.16.0-r

Re: [beagleboard] Using a device table overlay to disable the onboard RTC on the beaglebone black

This is just before running the update_kernel script: loading /boot/vmlinuz-4.9.78-ti-r94 ... 9960536 bytes read in 646 ms (14.7 MiB/s) uboot_overlays: [uboot_base_dtb=am335x-boneblack-uboot-univ.dtb] ... uboot_overlays: [uboot_base_dtb=am335x-boneblack-uboot.dtb] ... uboot_overlays: Switching too:

[beagleboard] SPI1

Has anybody managed to get /dev/spidev1.0 working on the latest release ? I been trying to get a spi display working and i can see data going to the display I can see the CS go low and i can see clocks but i do not see data from the display. Just trying to read status registers here. so I decide

Re: [beagleboard] Using a device table overlay to disable the onboard RTC on the beaglebone black

On Wed, Feb 21, 2018 at 11:44 AM, ferdster wrote: > This is just before running the update_kernel script: > loading /boot/vmlinuz-4.9.78-ti-r94 ... > 9960536 bytes read in 646 ms (14.7 MiB/s) > uboot_overlays: [uboot_base_dtb=am335x-boneblack-uboot-univ.dtb] ... > uboot_overlays: [uboot_base_dtb=a

Re: [beagleboard] Using a device table overlay to disable the onboard RTC on the beaglebone black

On Wed, Feb 21, 2018 at 11:32 AM, ferdster wrote: > BTW, this is on a SeeedStudio Green Wireless. > loading /boot/vmlinuz-4.16.0-rc2-bone3 ... > 10183168 bytes read in 659 ms (14.7 MiB/s) > uboot_overlays: [uboot_base_dtb=am335x-boneblack-uboot-univ.dtb] ... > uboot_overlays: Switching too: dtb=am

[beagleboard] Re: Beaglebone as a USB router (Share ethernet connection over USB)

Ah that is very helpful indeed. I didn't really consider such a basic setting wouldn't be included but then I guess that is really not what the USB connection is designed for. I have managed to get this to work with almost your suggestion. Instead of using Google's or my ISP DNS I instead just

[beagleboard] Re: TinyDRM ST7735 with BeagleBone?

On 02/21/2018 01:18 PM, Drew Fustini wrote: On Wed, Feb 21, 2018 at 11:01 AM, David Lechner wrote: Are you sure your phandles are correct here? They don't match the comments. Should it be <&gpio1 16 0> instead? + reset-gpios = <&gpio1 16 0>; /* reset:60 P9.12 GPI

Re: [beagleboard] Re: TinyDRM ST7735 with BeagleBone?

those mappings are correct GPIO1_28 P9-12 U18  = mapping /sys/class/gpio60 GPIO1_16 P9-15 R13  = mapping /sys/class/gpio48 On 2/21/2018 12:18 PM, Drew Fustini wrote: > On Wed, Feb 21, 2018 at 11:01 AM, David Lechner wrote: >> Are you sure your phandles are correct here? They don't match the com

[beagleboard] Re: TinyDRM ST7735 with BeagleBone?

On Wed, Feb 21, 2018 at 11:01 AM, David Lechner wrote: > Are you sure your phandles are correct here? They don't match the comments. > Should it be <&gpio1 16 0> instead? > >> + reset-gpios = <&gpio1 16 0>; /* >> reset:60 P9.12 GPIO1_28 */ > > > And then <&gpio1 28 0>

Re: [beagleboard] Using a device table overlay to disable the onboard RTC on the beaglebone black

I am using 'Debian 9.3 2018-01-28 4GB SD IoT' from here: https://beagleboard.org/latest-images (first one on top) I just started completely from scratch with the above base image, running from eMMC (uncommented 'init-eMMC-flasher-v3.sh' from /boot/uEnv.txt). The only thing I did was run connmanc

Re: [beagleboard] Using a device table overlay to disable the onboard RTC on the beaglebone black

On Wed, Feb 21, 2018 at 3:17 PM, ferdster wrote: > I am using 'Debian 9.3 2018-01-28 4GB SD IoT' from here: > https://beagleboard.org/latest-images (first one on top) > > I just started completely from scratch with the above base image, running > from eMMC (uncommented 'init-eMMC-flasher-v3.sh' fr

Re: [beagleboard] Using a device table overlay to disable the onboard RTC on the beaglebone black

Yes, that seems to work to add the PCF8523 RTC, but there are some other issues. -no more wifi (SoftAp0 or wlan0). 'ifconfig -a' only shows lo, usb0, and usb1. -'config-pin' still does not work. For example: config-pin P9_24 uart config-pin P9_26 uart Thanks. -- For more options, visit

Re: [beagleboard] Using a device table overlay to disable the onboard RTC on the beaglebone black

On Wed, Feb 21, 2018 at 3:36 PM, ferdster wrote: > Yes, that seems to work to add the PCF8523 RTC, but there are some other > issues. Cool > -no more wifi (SoftAp0 or wlan0). 'ifconfig -a' only shows lo, usb0, and > usb1. Okay, so it's just my board here.. I'll debug some more, it's the 'overla

Re: [beagleboard] Using a device table overlay to disable the onboard RTC on the beaglebone black

> > Only gpio's are implemented > Could you clarify that because the following don't work either: config-pin P9_14 gpio config-pin P9_42 gpio Thanks. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups

Re: [beagleboard] Using a device table overlay to disable the onboard RTC on the beaglebone black

On Wed, Feb 21, 2018 at 4:01 PM, ferdster wrote: >> Only gpio's are implemented > > > Could you clarify that because the following don't work either: > config-pin P9_14 gpio > config-pin P9_42 gpio sudo apt update ; sudo apt upgrade there's an upgraded bb-cape-overlay package Those two

Re: [beagleboard] Using a device table overlay to disable the onboard RTC on the beaglebone black

On Wed, Feb 21, 2018 at 3:42 PM, Robert Nelson wrote: > On Wed, Feb 21, 2018 at 3:36 PM, ferdster wrote: >> Yes, that seems to work to add the PCF8523 RTC, but there are some other >> issues. > > Cool > >> -no more wifi (SoftAp0 or wlan0). 'ifconfig -a' only shows lo, usb0, and >> usb1. > > Okay,

Re: [beagleboard] Using a device table overlay to disable the onboard RTC on the beaglebone black

> > sudo apt update ; sudo apt upgrade > > there's an upgraded bb-cape-overlay package > After digging out a USB-to-Ethernet dongle for internet access, I did the upgrade and those pins now work. Thanks. -- For more options, visit http://beagleboard.org/discuss --- You received this message

Re: [beagleboard] Using a device table overlay to disable the onboard RTC on the beaglebone black

On Wed, Feb 21, 2018 at 4:38 PM, ferdster wrote: >> sudo apt update ; sudo apt upgrade >> >> there's an upgraded bb-cape-overlay package > > After digging out a USB-to-Ethernet dongle for internet access, I did the > upgrade and those pins now work. Yeah, this is going to work for the BBGW at the

[beagleboard] Re: Powering Beaglebone black through VDD_5V

I'm having power issues booting a BBBW, where did you solder in the capacitor? On Monday, March 23, 2015 at 1:46:00 PM UTC-4, Karl Walter wrote: > > > > On Monday, December 23, 2013 at 12:30:32 PM UTC-8, José Luis Redrejo wrote: >> >> I've made a power supply to power my BBB, but whenever I conn

Re: [beagleboard] Using a device table overlay to disable the onboard RTC on the beaglebone black

On Wed, Feb 21, 2018 at 5:01 PM, Robert Nelson wrote: > On Wed, Feb 21, 2018 at 4:38 PM, ferdster wrote: >>> sudo apt update ; sudo apt upgrade >>> >>> there's an upgraded bb-cape-overlay package >> >> After digging out a USB-to-Ethernet dongle for internet access, I did the >> upgrade and those

[beagleboard] Can someone help me understand

I am looking for some one to answer a few questions I have about what I need to build my own. -- 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

Re: [beagleboard] Re: Powering Beaglebone black through VDD_5V

Hello, Just put the capacitor between 5v and ground anywhere. --Karl www.waltech.com On Wed, Feb 21, 2018 at 9:37 AM, wrote: > I'm having power issues booting a BBBW, where did you solder in the > capacitor? > > On Monday, March 23, 2015 at 1:46:00 PM UTC-4, Karl Walter wrote: >> >> >> >> On

Re: [beagleboard] Can someone help me understand

On 22/02/18 07:24, jflamini...@gmail.com wrote: > I am looking for some one to answer a few questions I have about what I need > to build my own. … your own… *what*? :-) -- Stuart Longland (aka Redhatter, VK4MSL) I haven't lost my mind... ...it's backed up on a tape somewhere. -- For more

[beagleboard] Where do I find PWM device address mappings?

Hi all, I'm trying to use the PWM outputs on my beaglebone and have a question about working out which pwmchip device a pin maps to. After figuring out the steps to get the PWM overlays working with u-boot (as most tutorials are still referring to cape manager), I was struggling with getting a

Re: [beagleboard] Where do I find PWM device address mappings?

On Wed, Feb 21, 2018 at 7:44 PM, James Fitzsimons wrote: > Hi all, > > I'm trying to use the PWM outputs on my beaglebone and have a question about > working out which pwmchip device a pin maps to. > > After figuring out the steps to get the PWM overlays working with u-boot (as > most tutorials ar

Re: [beagleboard] Where do I find PWM device address mappings?

Hi Robert, Thanks so much for your speedy response! Just to confirm then - I understand from the comment at the top of that file "#PWM's change on every bootup:" that my C++ driver code is going to have to list the contents of each of the epwmss device directories (e.g. /sys/devices/platform/ocp/

Re: [beagleboard] Where do I find PWM device address mappings?

On Wed, Feb 21, 2018 at 8:19 PM, James Fitzsimons wrote: > Hi Robert, > > Thanks so much for your speedy response! > > Just to confirm then - I understand from the comment at the top of that file > "#PWM's change on every bootup:" that my C++ driver code is going to have to > list the contents of

[beagleboard] tft driver

How would one know if if a particular driver is already build in the bone kernel fb_ra8875.c https://git.kernel.org/cgit/linux/kernel/git/gregkh/staging.git/tree/drivers/s

[beagleboard] PWM documentation and/logic for kernel 4.9.XX

Hi, I am using C blacklib to handle some i2c and spi devices. Also I have few PWM's P9_14 and 16 let's say. I learned the hard way that P9_14 and P9_16 are to befound in '48302200'. For P9_14 for example /sys/devices/platform/ocp/48302000.epwmss/48302200.pwm/pwm/pwmchipX which is a l

[beagleboard] Re: TinyDRM ST7735 with BeagleBone?

Thanks! I had DC and Reset swapped in the overlay file. I've fixed and the display is now working! The console is displayed after bootup and libdrm modetest is able to display color bars OK. Here is the updated dts: https://gist.github.com/pdp7/aee5664598059c9b9a9020f107957f80 Thanks, Drew On