[beagleboard] Re: SPI Overlay not changing states BBB 4.1.15-ti-r43 Debian Image 2015-11-12

I've been using spi2 quite extensively in python: from spidev import SpiDev as SPI and it works fine for me. > ls /dev/spi* /dev/spidev1.0 /dev/spidev1.1 > > sudo cat $SLOTS 0: PF -1 1: PF -1 2: PF -1 3: PF -1 4: P-O-L- 0 Override Board Name,00A0,Override

[beagleboard] IVerilog: just for info

I've been meaning to check out iverilog written by Stephen Williams for quite some time. I finally got around to it and thought why not install to the BBB in anticipation of the X15 that should be available soon. I did a git install from git clone git://github.com/steveicarus/ivtest.git The only

[beagleboard] Re: bone_capemgr.* - no such file or directory (Debian 8.2 2015-11-12)

Robert, after many many hours I was able to get almost everything working (well enough) in Debian 8.2; most of the details are described at: https://groups.google.com/forum/#!category-topic/beagleboard/beaglebone-black/E2VG4uAb31o On Tuesday, January 19, 2016 at 6:54:41 PM UTC-5, Robert Hurd

[beagleboard] Debian 4.1.x (Jessie) Device Driver Update: Summary mostly working

Summary, mostly working with some gotchas; this posting is just help others doing a change to 4.1.x, if not, please just ignore. 1) I2C works but it appears the addresses have changed: sudo i2cdetect -y -r 2 shows I2C at address 2 2) Adafruit_BBIO.ADC: needs fixes from

[beagleboard] I2C Buses Changed in 4.1.x

Under 3.8.13: > uname -r 3.8.13-bone77 > sudo i2cdetect -l i2c-0 i2c OMAP I2C adapter I2C adapter i2c-1 i2c OMAP I2C adapter I2C adapter > Under 4.1.115: > uname -r 4.1.15-bone17 > sudo i2cdetect -l i2c-0 i2c OMAP I2C adapter

[beagleboard] Re: BBB don't boot sometimes

I have also seen this occur on the order of 1/20 boots using 5V power jack. I'm guessing it could be due to a 'glitch' in the power supply, or possibly to noise entering some of the GPIO pins that effect boot. It looks to me that in these cases, the BBB does boot, but just doesn't turn on LED's

[beagleboard] Dongle WiFi Compatibility (Just for Info)

Just tested a few TP-Link USB WiFi dongles: summary TL-WN722N and TL-WN823N work, TL-WN821N has problems; it comes up without errors, but when being listed, reports being down even though it is up and working; see below. This is just for info; note the driver is rtl8192cu which I suspect is the

Re: [beagleboard] Re: Made a new systemd service, where is my output going?

a post that is nearly a year old ? On > Christmas of all days . . . > > Merry Christmas, and go sit down and relax with the family . . . > > On Fri, Dec 25, 2015 at 3:30 PM, Bit Pusher <ken.w@gmail.com > > wrote: > >> The output of stderr error ca

[beagleboard] Upgrade Best Practices?

I'm in the process of upgrading to a new image/kernel, and have many questions regarding best practices. My goal is to stay relatively current while spending most of my time on developing my application, not on doing upgrades; my success to date has been dismal. Over the past few weeks I have

[beagleboard] Re: Made a new systemd service, where is my output going?

The output of stderr error can be found using "sudo systemctl status SERVICE_NAME.service"; I'm not sure where stdout is going (perhaps /dev/null?). Irrespective, when doing systemd development, I always "tee" both stdout and stderr into a log file under my home directory. By using tee, I see

[beagleboard] Re: Using the BBB as a standalone wireless server

Getting over my head, but did wireshark show the arp request going to the IP address of the wlan device on the BBB? Also, check the address of the BBB when configured for login using ip > ip addr list dev wlan2 #(you are probably wlan0 or wlan1) 3: wlan2: mtu

Re: [beagleboard] Set priority of network interfaces wlan0 rather than eth0

William, the link you recommended uses /etc/network/interfaces for the setup; doesn't that require having NetworkManager enabled whereas I think Jessie is currently using connman and comes without NetworkManager installed? (this is a question, not a statement) Felipe, which network manager are

[beagleboard] Wireless Managager on Debian Wheezy

It appears Connman is being used to manage the network on Debian Wheezy. Does this mean /etc/network/interfaces is no longer being used? The only configuration file I have found for connman is /var/lib/connman/settings which has: [WiFi] Enable=false Tethering=false Can someone explain how to

[beagleboard] Recommended Image

I'm starting to update from an outdated image and to be clean am planning on starting from scratch with a newly flashed image. On http://beagleboard.org/latest-images there are two possible Debian images from Nov. 12'th, Wheezy 7.9 and Jessie 8.2. It is not clear which image I should use. I'm

Re: [beagleboard] SPI Issues

to a non-Dropbox directory and currently trying again (each try is almost an hour). Moral: even the simplest upgrade will break your programs; plan on stopping everything for at least 1-5 days. On Wednesday, September 23, 2015 at 9:14:59 PM UTC-4, Bit Pusher wrote: > > Please ignore f

Re: [beagleboard] SPI Issues

to block waiting for the edge. Overall Summary: I2C fine, GPIO fine but sparse documentation, SPI works but very flaky and can't use spi1 without wasting pins of spi0 On Monday, September 21, 2015 at 4:29:47 PM UTC-4, RobertCNelson wrote: > > On Mon, Sep 21, 2015 at 3:14 PM, Bit Pusher

Re: [beagleboard] SPI Issues

Please ignore for now, found headers by changing precise to wheezy (actually I added your repository back into /etc/apt/sources.list and then did an apt-get but I think it's equivalent). Next step is to get uio_pruss.ko. On Wednesday, September 23, 2015 at 8:56:41 PM UTC-4, Bit Pusher wrote

Re: [beagleboard] SPI Issues

what the correct address should be? It seems upgrades just never go right for me. On Monday, September 21, 2015 at 4:29:47 PM UTC-4, RobertCNelson wrote: > > On Mon, Sep 21, 2015 at 3:14 PM, Bit Pusher <ken.w@gmail.com > > wrote: > > I have been working with prog

[beagleboard] SPI Issues

I have been working with programming the BBB's SPI interface in python, and have become aware of a large number of issues others may be interested in; if planning on using the SPI interface, I hope this can save others some time. This is ongoing, so some of these issues may not be real in that

Re: [beagleboard] SPI Issues

k_Debian martin@beaglew's password: Last login: Mon Sep 21 12:07:13 2015 from granite10 > uname -a Linux BBB3 3.8.13-bone70 #1 SMP Fri Jan 23 02:15:42 UTC 2015 armv7l GNU/Linux On Monday, September 21, 2015 at 4:29:47 PM UTC-4, RobertCNelson wrote: > > On Mon, Sep 21, 2015 at 3:

[beagleboard] Boot Freezes with a single P8-P9 connection; reproduced on two boards

I have found a reproducible boot freeze (on two boards); could someone else possibly check; it's very easy to try. No connections besides power plug and one (or two) wires from header P8 to P9 Scenario 1: connect P8-43 to P9-30, plug in power, only power light comes on and BBB does not boot up

[beagleboard] Re: PRUSS under Debian beta

We have been using the PRUSS's extensively on bone70; with mostly success, but every so often, memory gets corrupted, and we have to reboot. This behavior is aperiodic and we have not been able to track it down yet (the PRUSS's can write anywhere in memory - they could be a significant security

[beagleboard] Re: PRUSS extRAM vs ddrMem; are they different memories or both part of the 500Mbytes DDRL3?

faster with a wireless connection compared to USB or a WiFi connection. On Monday, March 16, 2015 at 12:18:29 PM UTC-4, Bit Pusher wrote: I am trying to figure out memory mappings in the PRU, and especially ddrMem vs extRAM, and although there is information here and there, I have yet to find

[beagleboard] PRUSS extRAM vs ddrMem; are they different memories or both part of the 500Mbytes DDRL3?

I am trying to figure out memory mappings in the PRU, and especially ddrMem vs extRAM, and although there is information here and there, I have yet to find a cohesive explanation. I have found a few things to share, and perhaps someone more knowledgeable can help fill in some unanswered

[beagleboard] Re: MVIW Instruction on PRU

Eventually tracked it down to not having -V3 flags in pasm compile comand (they were missing from Makefile originally copied from TI examples). On Wednesday, February 18, 2015 at 5:08:08 PM UTC-5, Bit Pusher wrote: I'm planning on reading the PRU IO inputs a large number of consecutive times

[beagleboard] Re: PRUSS extRAM vs ddrMem; are they different memories or both part of the 500Mbytes DDRL3?

was big enough, it would be an option for sending data quickly to user space. On Monday, March 16, 2015 at 12:18:29 PM UTC-4, Bit Pusher wrote: I am trying to figure out memory mappings in the PRU, and especially ddrMem vs extRAM, and although there is information here and there, I have yet

[beagleboard] Initiating PRU Single-Stepping Using Prudebug?

I am running an example similar to PRU_PRUtoPRU_Interrupt from TI's pru support package, and have download and installed prudebug (the suggested alternative from LinuxCNC configs/pru-examples/README

Re: [beagleboard] MVIW Instruction on PRU

not. In the meantime, I will read the example you suggest.Thanks again. -Bit_Pusher On Thursday, February 19, 2015 at 3:40:03 PM UTC-5, Charles Steinkuehler wrote: On 2/18/2015 4:08 PM, Bit Pusher wrote: I'm planning on reading the PRU IO inputs a large number of consecutive times and move them

[beagleboard] MVIW Instruction on PRU

I'm planning on reading the PRU IO inputs a large number of consecutive times and move them (eventually) to DDR space. As part of my code, I tried one instruction like: MVIW *r0.w0++, r31.w0 which from section 5.3.4.2.3 Move Register File Indirect (MVIx) of the PRU reference manual seems correct

Re: [beagleboard] Pruss Question Re PRU_memAcc_DDR_sharedRAM.p

: On 2/16/2015 2:39 PM, Bit Pusher wrote: Thanks Charles this helps, I didn't realize a single address location is used to modify two constants. I'm slowly working my way through the documentation, but there's a lot of it without many examples I've found to date and the examples supplied

Re: [beagleboard] Pruss Question Re PRU_memAcc_DDR_sharedRAM.p

cause problems) On Monday, February 16, 2015 at 3:22:50 PM UTC-5, Charles Steinkuehler wrote: On 2/16/2015 12:37 PM, Bit Pusher wrote: I am having difficulty understanding a short snippet of code from the PRU_memAcc_DDR_sharedRAM.p example. The code is: // Configure the programmable

[beagleboard] Pruss Question Re PRU_memAcc_DDR_sharedRAM.p

I am having difficulty understanding a short snippet of code from the PRU_memAcc_DDR_sharedRAM.p example. The code is: // Configure the programmable pointer register for PRU0 by setting c31_pointer[15:0] // field to 0x0010. This will make C31 point to 0x80001000 (DDR memory). MOV

Re: [beagleboard] Could BB-BONELT-BT-00A0.dtbo have an error?

fixed or is it still present? Thanks again. -Ken On 14-03-12 12:37 PM, Robert Nelson wrote: On Wed, Mar 12, 2014 at 11:24 AM, Bit Pusher ken.w@gmail.comjavascript: wrote: BBB Ubuntu 3.8.13-bone28 cross compiled from Robert Nelson's source bone28 that's like from 6 months ago

Re: [beagleboard] Could BB-BONELT-BT-00A0.dtbo have an error?

Thanks Robert, this is very useful information that I did not know. On Wednesday, March 12, 2014 5:09:56 PM UTC-4, RobertCNelson wrote: On Wed, Mar 12, 2014 at 4:05 PM, Bit Pusher ken.w@gmail.comjavascript: wrote: Thanks John, this worked. I also tried modifying /lib/firmware/cape

Re: [beagleboard] Could BB-BONELT-BT-00A0.dtbo have an error?

wrote: On Wed, Mar 12, 2014 at 4:09 PM, Robert Nelson robert...@gmail.comjavascript: wrote: On Wed, Mar 12, 2014 at 4:05 PM, Bit Pusher ken.w@gmail.comjavascript: wrote: Thanks John, this worked. I also tried modifying /lib/firmware/cape-boneblack-hdmi-00A0.dts to remove

[beagleboard] Re: Struggling to find detailed information on how to make capes for the BBB

{ to something like: test_mycape:mycape { -Bit Pusher On Sunday, May 26, 2013 1:53:01 PM UTC-4, woss...@gmail.com wrote: I'd like to find a good and detailed source of information on how to create a well-integrated BBB Cape design. I have put together a bare-bones

[beagleboard] How Difficult is it to Compile and Run Robert Nelson's Ubuntu 13.04, V3.12.x branch?

Not! Just for info, especially for newbies (which I am regarding linux kernels). I went through the process of downloading and compiling Robert Nelson's Ubuntu 13.04 (v3.12.x branch (better usb and ethernet)), and it was very seamless and straightforward with no glitches. What a nice piece of

Re: [beagleboard] Re: Deleting Device Tree Overlays

/__init__.py, line 123 raise CodecRegistryError,\ ^ SyntaxError: invalid syntax Aborted (core dumped) I'm guessing I'm doing something stupid? Thanks. Bit_Pusher On Monday, December 9, 2013 11:19:20 AM UTC-5, Jeremy L wrote: On 12/09/2013 08:11 AM, Bit Pusher wrote

Re: [beagleboard] Re: Deleting Device Tree Overlays

Jeremy, please ignore; sudo apt-get install git-all did the trick. On Tuesday, December 10, 2013 4:15:18 PM UTC-5, Bit Pusher wrote: Jeremy, thank you; any chance you can field one more (probably not too intelligent) question as I'm only starting on git? git clone git://github.com/adafruit

[beagleboard] Re: Deleting Device Tree Overlays

help; with my limited knowledge re device trees, this is not something I would have been able to solve on my own. Bit Pusher On Friday, December 6, 2013 2:50:39 PM UTC-5, Zachary Thorson wrote: Odd, dmesg has no errors, but there is definitely a conflict between the two. Someone can correct

Re: [beagleboard] Re: Deleting Device Tree Overlays

Thanks John, appreciated. Bit Pusher On Tuesday, December 3, 2013 11:45:23 PM UTC-5, John Syne wrote: From: Bit Pusher ken.w@gmail.com javascript: Reply-To: beagl...@googlegroups.com javascript: Date: Tuesday, December 3, 2013 at 6:39 PM To: beagl...@googlegroups.com javascript

[beagleboard] Re: Deleting Device Tree Overlays

$PINS, I can see the expected pin change to 6. If I setup the AD first in python, I do not see any changes in the $PINS, and if I then try to load my overlay and check the pins, they are still the same as just after boot. Bit Pusher /lib/firmware\ cat BB-BONE-PRU-00A0.dts /* * pru dts file BB-BONE

[beagleboard] Re: Deleting Device Tree Overlays

on and off). I'm guessing things are not quite as expected. Also, could someone point me to the file in kernel source that loads overlays? Thanks. Bit Pusher On Tuesday, December 3, 2013 12:16:34 PM UTC-5, Zachary Thorson wrote: Correct me if I am wrong, but it appears that you simply want to use ADC

[beagleboard] Re: Deleting Device Tree Overlays

the same as before. By the way, my kernel is Linux ubuntu-armhf 3.8.13-bone28 On Monday, December 2, 2013 4:10:07 PM UTC-5, btr...@gmail.com wrote: if you actually run echo -9 $SLOTS as the root user do you still have this issue? On Sunday, December 1, 2013 7:42:06 PM UTC-6, Bit Pusher wrote

[beagleboard] Deleting Device Tree Overlays

the Adafruit_BBBIO.ADC does not have cleanup function. This behaviour does not seem correct to me. I also tried removing the overlay that set up the PRU output pins, and that did seem to work correctly. Any ideas? Thanks. Bit Pusher -- For more options, visit http://beagleboard.org/discuss --- You

[beagleboard] Re: Failure loading device tree overlay into BBB Ubuntu, seems to be loading incorrect *.tbo file?

BB-BONE-PRU $SLOTS pin 12 (44e10830) 0006 pinctrl-single and all is well. Any suggestions on how to load the overlay and have the output come up low? Thanks. On Wednesday, October 23, 2013 2:38:27 PM UTC-4, Bit Pusher wrote: Update, recompiled with different name, and then overlay load

Re: [beagleboard] Re: How to open ports on compiled ubuntu-13.04-console-armhf-2013-07-22.tar.xz

Robert, I got the downloaded image version working fine; the trouble was trying to access a compiled version working; I am still unsuccessful with this, and have given up on it for now, and am just working with the image version for now; I wll come back to it later, but currently have no idea

[beagleboard] Failure loading device tree overlay into BBB Ubuntu, seems to be loading incorrect *.tbo file?

bone_capemgr.9: failed to load firmware 'cape-bone-pru-00A0.dtbo' /lib/firmware\ any ideas? Thanks. Bit Pusher /lib/firmware\ cat BB-BONE-PRU-00A0.dts /* * pru dts file BB-BONE-PRU-00A0.dts */ /dts-v1/; /plugin/; / { compatible = ti,beaglebone, ti,beaglebone-black; /* identification

[beagleboard] Re: How to open ports on compiled ubuntu-13.04-console-armhf-2013-07-22.tar.xz

Thanks George, I actually do want to boot the operating system on the SD card which has two partitions made according to instructions at http://eewiki.net/display/linuxonarm/BeagleBone+Black. The operating system I installed on the SD card is ubuntu-13.04-console-armhf-2013-07-22.tar.xz. The

[beagleboard] Two's Complement Arithmetic

Has anyone used the PRU for signal processing with two's complement arithmetic? And a related question, are there any ideas on how to best implement sign extension? Thanks Bit Pusher -- For more options, visit http://beagleboard.org/discuss --- You received this message because you

[beagleboard] How to open ports on compiled ubuntu-13.04-console-armhf-2013-07-22.tar.xz

card that was made using ubuntu-raring-13.04-armhf-3.8.13-bone20.img.xz I need to figure out how torun compiled kernel so I can work at using the A/D driver from Zubair Lutfullah. Any suggestion or help is appreciated. Thanks Bit Pusher -- For more options, visit http://beagleboard.org

Re: [beagleboard] Re: How to enable PRU on the BeagleBoard BeagleBone Black?

Thanks Jacek, this is very helpful; is there any chance you canalso point me to a link re: Make sure that you loaded overlay enabling PRU and that the PRU driver is loaded? Thanks again. Bit Pusher On Tuesday, October 1, 2013 6:45:16 PM UTC-4, Jacek Radzikowski wrote: On Tue, Oct 1, 2013