Re: [beagleboard] Re: BBB, Debian, Chipsee display: Tkinter gives error

It looks like you need to set the DISPLAY environment variable so that tkinter knows which display to use. Is X11 installed on the BBB? On my linux machine, when I try echo $DISPLAY, I get ":0.0" without the quotes. What happens if you run that command? You might check out some of the info on

Re: [beagleboard] Re: C compiler

On Fri, Mar 25, 2016 at 9:03 PM, William Hermans wrote: > william@beaglebone:~/ti$ gcc test.c -o test > william@beaglebone:~/ti$ test > That's because it's the wrong test. type 'which test' and it'll probably say /usr/bin/test. If you don't specify the path, it's using the

[beagleboard] Re: BBB, Debian, Chipsee display: Tkinter gives error

Harke: Another in the Learned Group, I think it was Steve Plant but I can't find the post, suggested connecting a keyboard and mouse to the BBB and running the Python program with 'sudo python your_python_program'. That worked great for me. I never would have thought of it. My code is a GUI

Re: [beagleboard] Re: C compiler

@Richard Cook First thing one needs to understand. Just because the hardware is a beaglebone, does not mean it needs anything special in regards to toolchain's. As long as the tools have an ABI compatible binary, we're fine. The ABI it's self we do not really need to worry about. It's already in

Re: [beagleboard] Re: C compiler

To Richard Cook: My personal recommendation is Derek Molloy's: Exploring BeagleBone: Tools and Techniques for Building with Embedded Linux by Derek Molloy for John Wiley & Sons, 2014 -- ISBN 9781118935125 Book WebSite: includes errata, discussion http://exploringbeaglebone.com/ Source Code:

[beagleboard] Re: Using PRU on 4.1.20-bone-rt-r20 - Failed attemps

Hi Silwester! What happens when you load the kernel module manually (sudo modprobe uio_pruss)? Does it create the interrupts (ls -l /dev/uio*)? If not, do you get any messages in dmesg? BR -- For more options, visit http://beagleboard.org/discuss --- You received this message because you

[beagleboard] Re: C compiler

William Hermans wrote: > [-- text/plain, encoding 7bit, charset: UTF-8, 52 lines --] > > No chmod needed *IF* you precede the command with a dot slash "./". So when > you run a regular Linux command do you have to type this dot slash ? No > because chmod +x is run on the

[beagleboard] Re: C compiler

Dieter Wirz wrote: > On Fri, Mar 25, 2016 at 3:57 PM, Graham Haddock > wrote: > > Yes. > > sudo chmod 755 myprogram > > or > > sudo chmod 755 myprogram.o > > > Graham, please do not tell fairy tails on this list! > > $ echo '#include ' > hello.c > $

[beagleboard] Re: C compiler

Not to belabor the point but I am in about the same situation as Brainiac. Is there a cookbook guide to compiling, linking, and running C programs on beaglebone? It seems that most BB folks are comfortable with linux toolchain but many people come to this board with little linux knowledge, eg.

[beagleboard] Plz. Chack this Code For DHT11 with BBB code .......

Hello friends, I'm compilited this code for interface BBB with DHT11(temperature-humidity sensor) this code is compiled and run successfully but OUTPUT is *0'c temperature - 0% humidity Plz *, find error this code...

Re: [beagleboard] C compiler

You do not have to. I've been trying to tell you all that umask is already set by default. Screwing around with umask passed that is a recipe for disaster. Unless you know exactly what you're doing, and then you do not need to listen to me. Again, it was a terrible idea to even bring up umask, as

Re: [beagleboard] C compiler

Strange. I’m not sure there is a way to not use umask. With umask=022, the purpose is to set the default permission for newly created files or directories, so only the owner has write permissions. How is that a security flaw? I guess you can always make umask=000, but then you are enabling

Re: [beagleboard] C compiler

I think it should be pretty clear, and if this is not abundantly clear to new users. **DO NOT USE umask* *Period. good bye, the end. One should leave the default settings and instead work with the system as intended. Instead of creating a serious potential security hole. On Fri, Mar 25, 2016 at

Re: [beagleboard] How to get SPI1 working with 4.1 Kernel when mcasp is preventing the pins to be configured correctly

Hello I had a similar issue as noted here : https://groups.google.com/forum/#!topic/beagleboard/gOynYr8fgns I found I could not mux the pins by loading the overlay from the command line *BUT* it did work when I loaded the overlay via boot/uEnv.txt I still don't know why !!! On Friday, 25