[beagleboard] Build Kernel 3.8.13-bone79

Hello, I want to build kernel 3.8 for my BeagleBone Black and I don't know what should I do next. After a google search I have done next steps: - installed cross compiler on Ubuntu 16.04: sudo apt-get install gcc-arm-linux-gnueabi - download U-Boot, make and install the U-Boot tools: wget ftp:

[beagleboard] USB host is not detected

I know is a problem that I have on BeagleCore, not BeagleBone, but since the boards are kind of similar, I would be very thankful to anyone who can help me. I'm using a Debian Wheezy 7.11 image (https://beagleboard.org/latest-images) with Kernel 3.13.11-bone12. The problem is the board is not

[beagleboard] Can't connect on Wifi

Hello, I want to use my beaglebone as access point, and I want to connect with my PC. I'm in a point where I see the network on my PC, but I can't connect. Next are some details about the config I done after a google research: Configured network interface */etc/network/interfaces* auto wlx5cf37

[beagleboard] BBB CAN cape - how to enable CAN interface

Hello, I want to use BBB with a CAN cape to parse some messages received on CAN bus. For beginning, I want to see the CAN messages in a terminal with can-utils package. I use the last image available at this time: Debian 9.2 2017-10-10 4GB SD IoT

[beagleboard] Re: BBB CAN cape - how to enable CAN interface

I return with a remark. The CAN cape was detected after installing bb.org-overlays. So candump and cansend commands can be used as expected. The problem I had before was regarding to another LCD cape that is attached to beaglebone. For what dmesg output returns, seem to be a pin conflict betwee

[beagleboard] UART1 pin conflict, when using LCD and CAN capes

Hello, The scope of my project is to get CAN messages from CAN bus and display some information on an LCD. The HW components used: - BeagleBone Black - CAN cape https://www.waveshare.com/rs485-can-cape.htm - LCD cape gen4-4DCAPE-43T http://www.4dsystems.com.au/product/gen4_4DCAPE/ SW: Debian 9.2

Re: [beagleboard] UART1 pin conflict, when using LCD and CAN capes

Thank you, Can I change the pin map for P9.26 to use another pin? Or maybe change the CAN interface to another UART? joi, 26 octombrie 2017, 14:37:51 UTC+3, RobertCNelson a scris: > > > > On Oct 26, 2017 1:34 AM, "William" > > wrote: > > Hello, > &g

Re: [beagleboard] UART1 pin conflict, when using LCD and CAN capes

update-initramfs -uk 4.4.91-ti-r133 I also tried to enable from /boot/uEnv.txt: cape_enable=bone_capemgr.enable_partno=BB-CAN1 Can you please tell me what I am doing wrong? joi, 26 octombrie 2017, 15:20:42 UTC+3, RobertCNelson a scris: > > On Thu, Oct 26, 2017 at 7:13 AM, William >

Re: [beagleboard] Unable to get WiFi working on BBBW using the latest Debian image

Hello, this is what I have done, no result for now: *1. *Flashed BBBW with last image Debian 9.2 2017-10-10 4GB SD IoT *2. *Grounded TP1 *3.* dd if=/opt/scripts/device/bone/bbbw-eeprom.dump *4. * of=/sys/

Re: [beagleboard] Unable to get WiFi working on BBBW using the latest Debian image

I am using a *BB wireless *from element14. luni, 20 noiembrie 2017, 12:39:15 UTC+2, Reshmi Chandran a scris: > > are you using beagle bone black or beagle bone black wireless .wireless > works only on beaglebone wireless > > -- For more options, visit http://beagleboard.org/discuss --- You re

Re: [beagleboard] Unable to get WiFi working on BBBW using the latest Debian image

Added enable_uboot_overlays=1 disable_uboot_overlay_video=1 to /boot/uEnv.txt Now it does not boot, leds for BT, WL and USR0 stay on. beaglebone login: [ 64.841141] Error: Driver 'ecap' is already registered, aborting... [ 65.139009] Error: Driver 'ecap' is already registered, aborting...

Re: [beagleboard] Unable to get WiFi working on BBBW using the latest Debian image

n Nov 20, 2017 7:10 AM, "William" > > wrote: > > Added > enable_uboot_overlays=1 > disable_uboot_overlay_video=1 > to /boot/uEnv.txt > > Now it does not boot, leds for BT, WL and USR0 stay on. > beaglebone login: [ 64.841141] Error: Driver 'ecap' is alr

Re: [beagleboard] Unable to get WiFi working on BBBW using the latest Debian image

BB is completely freeze with those leds on. Tried to re-flash, same issue. I am not able to run any script. -- 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

Re: [beagleboard] Unable to get WiFi working on BBBW using the latest Debian image

CLcBGAs/s1600/bbbw.jpg> marți, 21 noiembrie 2017, 17:05:18 UTC+2, RobertCNelson a scris: > > On Tue, Nov 21, 2017 at 8:16 AM, William > > wrote: > > BB is completely freeze with those leds on. > > Tried to re-flash, same issue. > > I am not able to run any script. &g

Re: [beagleboard] Unable to get WiFi working on BBBW using the latest Debian image

I always use a 5V power supply. Got the image, flashed SD with Etcher, flashed the BBBW. Same result as before: it runs until "*beaglebone login:", *then freezes. bbbw.jpg

Re: [beagleboard] Unable to get WiFi working on BBBW using the latest Debian image

I always use a 5V power supply. Got the image, flashed SD with Etcher, flashed the BBBW. Same result as before: it runs until "beaglebone login:", then freezes. bbbw.jpg

Re: [beagleboard] Unable to get WiFi working on BBBW using the latest Debian image

I have only a 5V TTL serial cable, used only for receiving debug messages on PC (I don't want to burn something connecting the TX and V since voltage is different). For a normal SSH connection I use the mini USB cable and here is the problem. Since now I used with no problem BBB rev C and BBB i

Re: [beagleboard] Unable to get WiFi working on BBBW using the latest Debian image

I have only a 5V TTL serial cable, used only for receiving debug messages on PC (I don't want to burn something connecting the TX and V since voltage is different). For a normal SSH connection I use the mini USB cable and here is the problem. Since now I used with no problem BBB rev C and BBB i

Re: [beagleboard] Lightest distro for BBB

Asking a question of this sort will only, or even can only result in a zealot war. The question you should be asking yourself is which distro *you* prefer. After answering that question for yourself, common sense should step in. P.S. -Linux is Linux. On Sat, Sep 21, 2013 at 10:01 PM, Wasabi Fan

Re: [beagleboard] Power Supply Issues

We're using modified sine here. Granted I personally power my bbb via USB 3.0 from a laptop. So perhaps some extra filtering on the input cable into the laptop. However this modified sine system is the same system evilwulfie is on as well. I only power via USB as an easy means to avoid the short br

Re: [beagleboard] Re: Beaglebone Black ... What a Bull Shit !!!

It is obvious, at least to me this person did not even try very hard, and I can not help wondering if this person even really owns a BBB. My experiences have been the complete reverse what this person has said. I also can not help but wonder if this person is smart enough to know what a pin confli

Re: [beagleboard] Apple full numeric [Aluminium] keyboard and internal hub does not work

Hi Sushant Khanna, I have read about similar issues with all sorts of devices, and as far as I can tell the type of hub used can be a big factor in this situation. First, if you have not tried checking if each device works by its self on the USB host port ( individually ) I would do so now. So, I

Re: [beagleboard] Re: How can I improve processing time on BB?

^^^ Fifthly - Look into using the two PRU's to help offload some tasks. Also look into using using specific external hardware to offload even more from the CPU. Could also be that your routines need some tightening up. Have you done any cycle counting on your code ? Checked the generated ASM ?

Re: [beagleboard] BBB all leds on when connected a microSD

Sorry Gerald, but just to be sure it is clear. Case matters so "uEnv.txt" . . . Hate to be nickpicking, but in this case it does matter :/ On Fri, Sep 27, 2013 at 4:38 PM, Gerald Coley wrote: > You must add a uenv.txt file as indicated in the link I sent to th eSD > card. > > Gerald > > > > On F

Re: [beagleboard] BBB all leds on when connected a microSD

*nod* fair enough. On Fri, Sep 27, 2013 at 5:12 PM, Gerald Coley wrote: > Sure. Not an issue. All they have to do is read the link I sent and my > typing skills would not matter. > > Gerald > > > > On Fri, Sep 27, 2013 at 7:10 PM, William Hermans wrote: > >> Sor

Re: [beagleboard] Unreliable boot behavior

Also, from what has been said on these groups here. Having a power supply with a good rise time will help some too. I have experienced what you have as well. Granted, now while in project development stage, I boot almost exclusively from a local tftp / NFS share. Later, I expect to have a decent p

Re: [beagleboard] BBB all leds on when connected a microSD

I didn't follow the document :-( >> >> Now is booting! >> >> Next step install debian! >> >> regards >> >> >> On Saturday, 28 September 2013 01:17:58 UTC+1, Gerald wrote: >> >>> I did go to the link and make sur

Re: [beagleboard] Cross compiled binary won't run

> Specifically https://launchpad.net/linaro-toolchain-binaries/trunk/2013.09/+download/gcc-linaro-arm-linux-gnueabihf-4.8-2013.09_linux.tar.xz Wrong ABI. gnueabi should be the compiler you're after not gnueabihf. On Mon, Sep 30, 2013 at 9:41 AM, Tux Leonard wrote: > ldd doesn't show up in the

Re: [beagleboard] No activity lights, only power and ethernet light, what should I do?

unplug everything from the board while you're flashing it. e.g. dont leave your ethernet cable plugged in during. On Mon, Sep 30, 2013 at 6:53 AM, Gerald Coley wrote: > Five minutes is not necessary. Only about 10 seconds is required. Sounds > like the SD card was not created properly or the SD

Re: [beagleboard] Cross compiled binary won't run

f was for. > > On Monday, September 30, 2013 7:14:22 PM UTC+2, William Hermans wrote: >> >> > Specifically https://launchpad.net/linaro-** >> toolchain-binaries/trunk/2013.**09/+download/gcc-linaro-arm-** >> linux-gnueabihf-4.8-2013.09_**linux.tar.xz<https://l

Re: [beagleboard] [Issue] Debian Wheezy - No Sound, At All

Not only that, but what does lsmod have to say ? Is there a driver installed for it already ? On Mon, Sep 30, 2013 at 2:48 PM, Robert Nelson wrote: > On Mon, Sep 30, 2013 at 4:08 PM, Illutian Kade > wrote: > > I freakin' give up. > > > > I've spent the last TEN HOURS trying to get sound off thi

Re: [beagleboard] Remote debugging thru SSH

The problem with python in some situations is that it will use more CPU cycles, and can be horrendously slow compared to many native alternatives. Just a for example and very rough ( going from memory here . . .) C/C++ for one benchmark I looked at was around 7-8 seconds. ADA2005 roughly 12, nodejs

Re: [beagleboard] TFTP setup for the Beaglebone Black

This wont work with Angstrom Ubuntu or Fedora . . .but here ya go http://www.embeddedhobbyist.com/debian-tips/beaglebone-black/beaglebone-black-network-boot/ On Wed, Oct 2, 2013 at 8:02 AM, wrote: > How can I setup TFTP server for the Beaglebone Black? > > -- > For more options, visit http://b

Re: [beagleboard] Re: TFTP setup for the Beaglebone Black

I mean, I know of at least one person who has tested this on Debian, ARCH, Busybox( custom ) and all three of those worked. Ubuntu, Fedora, and Angstrom all ***did not work***. I am personally only interested in Debian at this moment. So this is all the testing I have done. I have been hearing th

Re: [beagleboard] putty black screen

This means you're unable to connect via puTTY to the Beaglebone. Now, there are several reasons why this can be, and you're going to have to figure that out on your own. Google should be a good source of information for this. On Sun, Mar 21, 2021 at 3:55 PM Meric wrote: > hi guys i have a issue

Re: [beagleboard] Which USB to TTL cable should I buy from here?

I've been using a prolific 2303hx for about a year now. https://www.amazon.com/Armorview-PL2303HX-RS232-Module-Converter/dp/B008AGDTA4 They're fairly inexpensive, and they seem to be supported very well. It works great on Linux, or Windows, but I prefer to use it on Windows because Linux cmdline t

Re: [beagleboard] Which USB to TTL cable should I buy from here?

r. On Sat, Aug 13, 2016 at 10:45 AM, William Hermans wrote: > I've been using a prolific 2303hx for about a year now. > https://www.amazon.com/Armorview-PL2303HX-RS232- > Module-Converter/dp/B008AGDTA4 > > They're fairly inexpensive, and they seem to be supported very

Re: [beagleboard] Beagle Board Black - cannot connect with Win10 over Putty

You need to remove that bridge, and use internet connection sharing. On Mon, Aug 15, 2016 at 3:28 AM, lamprechtmarkus1 via BeagleBoard < beagleboard@googlegroups.com> wrote: > Hey all, > > I have a BBB(Beagle Bone Black) and here is what I did: > > First I flashed this firmware onto my board: >

Re: [beagleboard] UARTS in kernel 4.4: no /dev/ttO* ?

william@beaglebone:~$ dmesg |grep tty [0.00] Kernel command line: console=tty0 console=ttyO0,115200n8 root=/dev/mmcblk0p1 rootfstype=ext4 rootwait ipv6.disable=1 [0.002187] console [tty0] enabled [0.002223] WARNING: Your 'console=ttyO0' has been replaced

Re: [beagleboard] UARTS in kernel 4.4: no /dev/ttO* ?

william@beaglebone:~$ ls /sys/devices/platform/ocp/ 4030.ocmcram 4803.spi4806.mmc 4831.rng 5350.aes 40302000.ocmcram_nocache 48038000.mcasp 480c8000.mailbox 4900.edma 5600.sgx 44e07000.gpio 4803c000.mcasp 480ca000.spinlock 4980

Re: [beagleboard] UARTS in kernel 4.4: no /dev/ttO* ?

william@beaglebone:~$ apt-cache search setserial setserial - controls configuration of serial ports william@beaglebone:~$ sudo apt-get install setserial . . . The following NEW packages will be installed: setserial 0 upgraded, 1 newly installed, 0 to remove and 13 not upgraded. Need to get 49.9

Re: [beagleboard] UARTS in kernel 4.4: no /dev/ttO* ?

http://bfy.tw/7Hr5 Anyhow, consider this horse beaten to death. On Thu, Aug 18, 2016 at 4:42 PM, William Hermans wrote: > william@beaglebone:~$ apt-cache search setserial > setserial - controls configuration of serial ports > william@beaglebone:~$ sudo apt-get install setserial >

Re: [beagleboard] Right way to get the gpio values from the device tree in the device driver for BeagleboneBlack

http://linux.die.net/man/3/strerror On Thu, Aug 18, 2016 at 9:03 PM, Jane wrote: > Hello, > > This topic is not solely related to beagleboneBlack , still posting on > this group . > > With reference to the example below what is the correct way to get the > gpio values from the device tree : > >

Re: [beagleboard] Re: Microchip mcp2515, can over spi, not working. Wrong device tree overlay?

> > 1. Haha! It does? Must have missed it when I looked on the pinmap. > 2. Tried to disable universal cape, makes no difference. > > Anyways. I still want to get it to work. Have spent so much time on it, > and I would hate to just let it go. Even though I probably won't use it. I > also need to g

Re: [beagleboard] Re: Microchip mcp2515, can over spi, not working. Wrong device tree overlay?

8:58 AM, William Hermans wrote: > 1. Haha! It does? Must have missed it when I looked on the pinmap. >> 2. Tried to disable universal cape, makes no difference. >> >> Anyways. I still want to get it to work. Have spent so much time on it, >> and I would hate to just l

Re: [beagleboard] BBB TPS65217 RTC

> > Does the BBB use the TPS65217 RTC to keep system time while powered, but > not synchronized to any NTP server? > No, the beaglebone uses the tsp65217c "real-time clock" to bring up the power rails on the beaglebone in the correct order, and all the other interresting power things. Such as char

Re: [beagleboard] Re: Microchip mcp2515, can over spi, not working. Wrong device tree overlay?

4 debian images. The only thing you may have to do is download via wget config-pin, chmod +x it then move it to the appropriate /bin directory. Then you just: $ sudo config-pin PX.XX spi etc, etc. On Fri, Aug 19, 2016 at 9:01 AM, William Hermans wrote: > https://github.com/msperl/mcp251

Re: [beagleboard] BBB TPS65217 RTC

$ ls /sys/devices/platform/ocp/44e3e000.rtc/rtc rtc0 On Fri, Aug 19, 2016 at 1:25 PM, wrote: > On Friday, August 19, 2016 at 3:55:34 PM UTC-4, Wulf Man wrote: >> >> That part is a power management IC not a RTC there is a built in RTC in >> the processor that will not keep >> time when powered d

Re: [beagleboard] BBB TPS65217 RTC

By the way, you can use /dev/rtc0 just like any other real-time clock. Search the internet for "linux how to use real-time clock" On Fri, Aug 19, 2016 at 9:29 PM, William Hermans wrote: > $ ls /sys/devices/platform/ocp/44e3e000.rtc/rtc > rtc0 > > > On Fri, Aug 19

Re: [beagleboard] BBB TPS65217 RTC

That does not mean you can not set time on it, set time in apps from it, etc. On Sat, Aug 20, 2016 at 12:13 AM, Micka wrote: > Rtc0 is already used by default... > > Le sam. 20 août 2016 06:30, William Hermans a écrit : > >> By the way, you can use /dev/rtc0 just like any oth

[beagleboard] Trouble enabling SPI1 hardware with debian 4.4.9

Background Info: 1) We are using BeagleBone Black to power our robot, using it since November. 2) We use ADC, I2C1, I2C2, SPI0, 5 PWMs, and almost every available GPIO. We have all these working using overlays, or config-pin, whichever is needed. All is good. 3) Up until now I have not had

[beagleboard] Re: Trouble enabling SPI1 hardware with debian 4.4.9

On Saturday, August 20, 2016 at 2:42:12 PM UTC-7, William Wendin wrote: > > Background Info: > 1) We are using BeagleBone Black to power our robot, using it since > November. > 2) We use ADC, I2C1, I2C2, SPI0, 5 PWMs, and almost every available GPIO. > We have all t

[beagleboard] Re: Trouble enabling SPI1 hardware with debian 4.4.9

add SPIDEV1 overlay is via /etc/rc.local (echo 'BB-SPIDEV1' > /sys/devices/platform/bone_capemgr/slots). But that didn't work at all for me (SPI1 not enabled AND it wipes out availability of I2C, PWMs etc). On Saturday, August 20, 2016 at 2:42:12 PM UTC-7, William Wendin w

Re: [beagleboard] Re: Trouble enabling SPI1 hardware with debian 4.4.9

You'll need to put all your pin mux into one file. I'd probably test with universal io, to see if you can get it working that way first, and then perhaps you'll have to put that, or all pin mux into the board file. On Sat, Aug 20, 2016 at 3:29 PM, William Wendin wrote: >

Re: [beagleboard] BBB TPS65217 RTC

Well actualy, it may be in the datasheet. For the am335x processor. On Mon, Aug 22, 2016 at 9:29 AM, William Hermans wrote: > that's probably in the TRM. > > On Mon, Aug 22, 2016 at 7:24 AM, wrote: > >> On Saturday, August 20, 2016 at 12:31:01 AM UTC-4, William Herman

Re: [beagleboard] BBB TPS65217 RTC

that's probably in the TRM. On Mon, Aug 22, 2016 at 7:24 AM, wrote: > On Saturday, August 20, 2016 at 12:31:01 AM UTC-4, William Hermans wrote: >> >> By the way, you can use /dev/rtc0 just like any other real-time clock. >> Search the internet for "l

Re: [beagleboard] Re: PRU C Project - from device tree to program execution

Use git . . . On Sun, Aug 21, 2016 at 10:31 PM, wrote: > "apt-get am335x-pru-package" gives me "Unable to locate package" on > Ubuntu 14.04. Has this package disappeared between 2014 and 2016 or do I > need to do something else to get it? > > Thanks, > Ken > > On Monday, December 1, 2014 at 8:57

Re: [beagleboard] Re: Monodevelop running terminal commands

I'd probably consider using groups. Like I briefly discuss here: https://github.com/wphermans/Bonejs/blob/master/documentation/permissions.md However. sudo can be very specific with commands. So for instance if you wanted a regular user to be able to use apt-get update, and no other apt commands.

Re: [beagleboard] Re: Monodevelop running terminal commands

Heres a quick simple example of command specific sudo usage. http://www.atrixnet.com/allow-an-unprivileged-user-to-run-a-certain-command-with-sudo/ On Mon, Aug 22, 2016 at 11:17 AM, William Hermans wrote: > I'd probably consider using groups. Like I briefly discuss here: > https:/

Re: [beagleboard] USB Connection kills laptops WIFI

This, which I'm assuming if your wifi adapter ? wlo1 Link encap:Ethernet HWaddr 2c:33:7a:80:90:79 *inet addr:10.67.66.49 Bcast:10.67.79.255 Mask:255.255.240.0* inet6 addr: fe80::5bed:8318:765b:bc41/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:

Re: [beagleboard] USB Connection kills laptops WIFI

Yeah additionally, your broadcast address is wrong for the address range you're in. So it seems like Ubuntu 16.04 has a major screw loose somewhere. Perhaps it's time for you to file a bug report ? On Tue, Aug 23, 2016 at 6:26 PM, William Hermans wrote: > This, which I'm ass

Re: [beagleboard] Re: Trouble enabling SPI1 hardware with debian 4.4.9

/sys/devices/platform/bone_capemgr/slots bash: echo: write error: File exists I'm going to have to give up for now as I spent whole day yesterday on this. Need to move on to other stuff but will return. On Saturday, August 20, 2016 at 4:09:55 PM UTC-7, William Hermans wrote: > > Yo

Re: [beagleboard] nodejs beaglebone black can't use serialport module

Serial is actually really easy to do in Nodejs: https://github.com/wphermans/Bonejs/blob/master/examples/serial-read-example.js https://github.com/wphermans/Bonejs/blob/master/examples/serial-write-example.js On Wed, Aug 24, 2016 at 7:30 AM, Robert Nelson wrote: > > > On Wed, Aug 24, 2016 at 9:

Re: [beagleboard] 4.1 or 4.4 kernel for best stability and feature support on BBB

Alexander, Are you just loading the rootfs and kernel from USB ? If this is the case you should not need a custom first or second stage bootloader. Granted I have not done this myself since 3.8.x kernels, but It should just work, Unless uboot has changed in this regard. Don't see why it should ha

Re: [beagleboard] 4.1 or 4.4 kernel for best stability and feature support on BBB

el versions. And if that > fails, I'll switch to a new image per Robert's suggestion. > > Thanks, > Alex > > On Thursday, August 25, 2016 at 8:41:58 PM UTC-4, William Hermans wrote: >> >> Alexander, >> >> Are you just loading the rootfs and kernel fro

Re: [beagleboard] Can't upgrade my Beaglebone Black's kernel from 3.8 to 4.* version

> > Thanks for your answer, Robert. I checked option, but I don't have a > microSD card right now. Is there a way to install images without using an > SD card or SD card is the only option? > No, not really. Well actually you *could* "boot" off USB, but this should really be done with the bootload

Re: [beagleboard] BBB battery charging

Page 41 of the datasheet, looks like registers 3-6. Although I have not read in details what the function of those registers are. This should be fixable through custom software, but I'd have to read in greater detail to understand what must be done, and what should be checked for before manually se

Re: [beagleboard] BBB battery charging

uot;twiddle" the register bits. I would have to experiment with this myself to confirm that anything I think may be possible. Actually *is* possible. On Fri, Sep 2, 2016 at 3:52 PM, William Hermans wrote: > Page 41 of the datasheet, looks like registers 3-6. Although I have not >

Re: [beagleboard] BBB battery charging

interestingly: *william@beaglebone:~$ cat* /sys/bus/i2c/drivers/tps65217/0-0024/tps65217-charger/power/runtime_enabled disabled So is it possible to change this to "enabled" ? If so what are the consequences ? On Fri, Sep 2, 2016 at 7:04 PM, William Hermans wrote: > So I did some

Re: [beagleboard] Re: Welcome the Fall 2014 Beagle Class to the group

You're serious, with a name like that ? On Sun, Sep 4, 2016 at 1:32 AM, Bill Mar wrote: > Do you mean Fall 2016 ? > > On Fri, Sep 2, 2016 at 9:24 PM, David Mehl wrote: > >> I think this is the right place... >> >> -- >> For more options, visit http://beagleboard.org/discuss >> --- >> You recei

Re: [beagleboard] BBB battery charging

.c?v=4.4 > The low-level driver you have looked at is used by this. > > Cheers > Christoph > > On Sat, Sep 3, 2016 at 4:04 AM, William Hermans wrote: > > So I did some searching on this because I am interested in this as well. > I > > figured that the PMIC driver i

Re: [beagleboard] BBG - Soft poweroff does not work

$ sudo apt-get install acpid Give that a whirl, it should fix your issue. You changed images didnt you ? from LXDE image to one of the command line images. Right ? On Mon, Sep 5, 2016 at 7:08 AM, Steven Hirsch wrote: > Title says it. After updating to Debian 8.4 I find that the power button >

Re: [beagleboard] BBG - Soft poweroff does not work

If by chance that does not work for you. Use the latest image. Jessie 8.5 I believe. It works, or at least works for me, with the beaglebone black or beaglebone green. On Mon, Sep 5, 2016 at 8:49 AM, William Hermans wrote: > $ sudo apt-get install acpid > > Give that a whirl, it should

Re: [beagleboard] analogRead in bonescript fails on first attempt after reboot

Yeah it sound like bonescript, or the newer refactored version may not correctly handle the "file does not exist" exception correctly. As it currently sits. Ideally, in code you would check that the file you're about to use exists, and if it does not then you load the appropriate device tree file,

Re: [beagleboard] analogRead in bonescript fails on first attempt after reboot

w I do not have the time. . . On Mon, Sep 5, 2016 at 2:03 PM, William Hermans wrote: > Yeah it sound like bonescript, or the newer refactored version may not > correctly handle the "file does not exist" exception correctly. As it > currently sits. > > Ideally, in code y

Re: [beagleboard] Trying to run the ADC from the PRU

The only thing I can think of is that you're not enabling the ADC control register. Below is a code snippet from another post. //Init ADC CTRL register MOV r2, 0x44E0D040 MOV r3, 0x0005 SBBO r3, r2, 0, 4 >From this post: https://groups.google.com/forum/#!msg/beagleboard/0a4tszlq2y

[beagleboard] gpio1_16 and gpio2_0 issues on beaglebone green.

So as the subject says we're having issues with gpio1_16 and gpio2_0 being tied together through r161. We've removed r161 on one beaglebone green, then export gpio48(gpio1_16) through sysfs, set the direction to 'in', in an attempt to read input to an externally connected sensor. This does not

Re: [beagleboard] gpio1_16 and gpio2_0 issues on beaglebone green.

at 1:51 PM, William Hermans wrote: > So as the subject says we're having issues with gpio1_16 and gpio2_0 being > tied together through r161. We've removed r161 on one beaglebone green, > then export gpio48(gpio1_16) through sysfs, set the direction to 'in', in >

Re: [beagleboard] gpio1_16 and gpio2_0 issues on beaglebone green.

without universal io, config pin, or any of that. On Wed, Sep 7, 2016 at 2:00 PM, William Hermans wrote: > Additionally, using: > > $ sudo config-pin overlay univ-all > $ sudo config-pin P9.15 hi / low > > Seems to work fine on the BBG too. However the idea is to use P9.15 as >

Re: [beagleboard] Re: Header files for non PRU peripherals

On Wed, Sep 7, 2016 at 2:28 PM, Charles Steinkuehler < char...@steinkuehler.net> wrote: > > IMHO it works best if you setup the GPIO banks with Linux, then use > the PRU to twiddle the output bits using the set and clear registers > in the GPIO bank. That way you don't have to worry about any sor

Re: [beagleboard] gpio1_16 and gpio2_0 issues on beaglebone green.

BONE_P9_13 (PIN_OUTPUT_PULLDOWN | MUX_MODE6) /* gpmc_wpn.uart4_txd_mux2 */ BONE_P9_15 (PIN_INPUT | MUX_MODE7) /* gpmc_a0.gpio1[16] */ *0x088 (PIN_INPUT | MUX_MODE7) /* gpmc_csn3.gpio2[0] */* >; }; That should be the culprit, but do I realy

Re: [beagleboard] gpio1_16 and gpio2_0 issues on beaglebone green.

in *debian@beaglebone:~$* sudo sh -c "echo 'out' > /sys/class/gpio/gpio51/direction" *debian@beaglebone:~$* cat /sys/class/gpio/gpio51/direction out *debian@beaglebone:~$* sudo sh -c "echo '1' > /sys/class/gpio/gpio51/value" *debian@beaglebone:~$* sudo s

Re: [beagleboard] gpio1_16 and gpio2_0 issues on beaglebone green.

/config-pin overlay univ-all Loading univ-all overlay *debian@beaglebone:~$* sudo ./config-pin P9.16 hi *debian@beaglebone:~$* cat /sys/class/gpio/gpio48/value 0 *debian@beaglebone:~$* sudo ./config-pin P9.16 low *debian@beaglebone:~$* cat /sys/class/gpio/gpio48/value 1 So, Robert, Charles, anyone ? What

Re: [beagleboard] Is there a way to decrease the interval between bytes during an SPI transfer?

Hi Dave, Does changing the clock frequency have an impact on latency between bytes ? I've read that spidev should be able to handle 48Mhz. But if increasing the clock frequency does not help, or gives diminishing returns. You may be bumping up against the limitation of running such an application

Re: [beagleboard] gpio1_16 and gpio2_0 issues on beaglebone green.

at /sys/class/gpio/gpio48/value 1 So, I'm not experiencing an "off by 1" issue. But for some reason gpio1_16 *only* works if a universal IO overlay that deals with gpio1_16 appropriately - *somehow*. I'm not sure what I'm missing. Is this a software bug of some sort ?

Re: [beagleboard] Re: Header files for non PRU peripherals

On Wed, Sep 7, 2016 at 5:39 PM, Charles Steinkuehler < char...@steinkuehler.net> wrote: > On 9/7/2016 5:18 PM, William Hermans wrote: > > > > I agree with Charles with one exception. I personally prefer to use > DATAOUT > > directly instead of using SETDATAOUT /

Re: [beagleboard] gpio1_16 and gpio2_0 issues on beaglebone green.

So, booting and loading am335x-bonegreen-overlay.dtb on a beaglebone green will render the board unbootable. On Wed, Sep 7, 2016 at 5:24 PM, William Hermans wrote: > Just for clarity > > *debian@beaglebone:~$* sudo sh -c "echo '1' > > /sys/class/gpio/gpio51/value

Re: [beagleboard] gpio1_16 and gpio2_0 issues on beaglebone green.

Let me rephrase that. The board seems to boot and come up, but I was unable to ssh into the board. For whatever reason. Did not care to look why. On Wed, Sep 7, 2016 at 6:08 PM, William Hermans wrote: > So, booting and loading am335x-bonegreen-overlay.dtb on a beaglebone green > will rend

Re: [beagleboard] gpio1_16 and gpio2_0 issues on beaglebone green.

Sep 7, 2016 at 6:09 PM, William Hermans wrote: > Let me rephrase that. The board seems to boot and come up, but I was > unable to ssh into the board. For whatever reason. Did not care to look why. > > On Wed, Sep 7, 2016 at 6:08 PM, William Hermans wrote: > >> So, booting an

Re: [beagleboard] Re: Header files for non PRU peripherals

On Thu, Sep 8, 2016 at 6:36 AM, Charles Steinkuehler < char...@steinkuehler.net> wrote: > On 9/7/2016 7:50 PM, William Hermans wrote: > > > > SETDATAOUT -> |= BITx > > CLEARDATAOUT -> &=(~BITx) > > > > I gues I'll have to reread the TRM again.

Re: [beagleboard] gpio1_16 and gpio2_0 issues on beaglebone green.

ay file in order for this 1 pin to be usable ? On Wed, Sep 7, 2016 at 8:35 PM, William Hermans wrote: > So, I still do not know what exactly the problem *is*. So for those of you > who need to use this pin, I guess you, and everyone else who is using a 4.x > kernel will have to load a device

Re: [beagleboard] analogRead in bonescript fails on first attempt after reboot

own message!) > > I'll look into following your suggestion. I'm not too savvy on device > trees, so it'll be a learning experience. > > > On Monday, September 5, 2016 at 5:08:10 PM UTC-4, William Hermans wrote: >> >> What i mean by the above is that the

Re: [beagleboard] Re: Header files for non PRU peripherals

effect, a blocking write, then read, but it turned out to be very fast. Anyway, I think this is similar how I would approach what's being discussed here. On Thu, Sep 8, 2016 at 1:38 PM, Charles Steinkuehler < char...@steinkuehler.net> wrote: > On 9/8/2016 1:40 PM, William Hermans

Re: [beagleboard] Re: Header files for non PRU peripherals

ut the way I read the TRM. TO me it seems that the SETDATA(direction) registers actually write to DATAOUT. did I read that wrong ? On Thu, Sep 8, 2016 at 1:51 PM, Charles Steinkuehler < char...@steinkuehler.net> wrote: > On 9/8/2016 3:35 PM, Charles Steinkuehler wrote: > > On 9/8/2016

Re: [beagleboard] Re: Header files for non PRU peripherals

(GPIO_CLEARDATAOUT) address. Ok thats confusing . . .but I guess I read this and understood the opposite of what it's saying ? e.g. I was thinking DATAOUT would be fast ? On Thu, Sep 8, 2016 at 1:56 PM, William Hermans wrote: > Oh...while we're on the subject, there's one more signifi

Re: [beagleboard] pinmux broken on hdmi pins in 4.4-ti kernel but working in 4.4-bone kernel

Sure, the work around is don't use those kernels. william@beaglebone:~$ uname -r 4.4.14-ti-r34 william@beaglebone:~$ ls /sys/class/gpio export gpiochip0 gpiochip32 gpiochip64 gpiochip96 unexport william@beaglebone:~$ sudo sh -c "echo '115' > /sys/class/gpio/expo

Re: [beagleboard] pinmux broken on hdmi pins in 4.4-ti kernel but working in 4.4-bone kernel

asted ? I do not know . . . On Sat, Sep 10, 2016 at 3:00 PM, Jason Kridner wrote: > Is this a reason we can't get it working in both? > > On Sep 10, 2016, at 2:11 PM, William Hermans wrote: > > Sure, the work around is don't use those kernels. > > william@beaglebone

Re: [beagleboard] pinmux broken on hdmi pins in 4.4-ti kernel but working in 4.4-bone kernel

2016 at 8:45 PM, William Hermans wrote: > Is this a reason we can't get it working in both? >> > > Are you speaking to me Jason ? > > If so I'm not sure what the problem the OP is having. But I can say that > "we" do not need to to any extra pin mux

Re: [beagleboard] Re: High speed encoder input capability of BBB?

There is an eCAP module in the processor that *perhaps* could be controlled via a PRU . . . but I have limited knowledge of that peripheral module, and no hands on . . . On Sat, Sep 10, 2016 at 6:25 PM, Dennis Lee Bieber wrote: > On Sat, 10 Sep 2016 15:04:23 -0700 (PDT), beezerlm > declaimed th

Re: [beagleboard] pinmux broken on hdmi pins in 4.4-ti kernel but working in 4.4-bone kernel

ey'll always read '0' whether that pin is pulled high, or low - externally. On Sat, Sep 10, 2016 at 8:55 PM, William Hermans wrote: > Oh, and right. I'm still not clear on if SPI can be muxed outside of the > given board overlay file. While at the same time, it seems

  1   2   3   4   5   6   7   8   9   10   >