Re: [beagleboard] C compiler

Hi Mike, The way I think about this is umask turns off permission, which means that the execute permission is provided by gcc. For example: MBPR:~ john$ umask 0022 MBPR:~ john $ touch test MBPR:~ john $ ls -la test -rw-r--r-- 1 john staff 0 Mar 25 22:15 test MBPR:~ john $ gcc -Wall -o hello

Re: [beagleboard] Re: C compiler

lol . . . way off the point by now. But since we're way off point I will make my disappointment known. First, Linux is purportedly know as the developers OS by developers, yes ? So with that in mind it's probably a good assumption that many people are going to be developing software on it. So . .

Re: [beagleboard] Re: C compiler

On 03/25/2016 09:44 PM, William Hermans wrote: ooops forgot to add this. william@beaglebone:~/ramfs$ which test william@beaglebone:~/ramfs$ sudo su root@beaglebone:/home/william/ramfs# which test root@beaglebone:/home/william/ramfs# exit exit* * On Fri, Mar 25, 2016 at 6:42 PM, William Hermans

[beagleboard] Re: Load overlay at boot

https://github.com/cdsteinkuehler/beaglebone-universal-io See the help for config-pin. You can create a file and run config-pin with -f option using your .profile. I can't tell you how to get this done outside of root, however, I believe it is possible. -- For more options, visit

Re: [beagleboard] Re: C compiler

On 03/25/2016 09:51 PM, William Hermans wrote: /Careful. '/usr/bin/test' is often a real program for/ /shells that don't have builtin 'test'. Which you just/ /overwrote./ I had no idea . . . good thing this is a test image - heh. Thanks Peter :) root@ticktock:/dev# type test

Re: [beagleboard] Re: C compiler

> > *Careful. '/usr/bin/test' is often a real program for* > * shells that don't have builtin 'test'. Which you just* > * overwrote.* > I had no idea . . . good thing this is a test image - heh. Thanks Peter :) On Fri, Mar 25, 2016 at 6:49 PM, Peter Hurley wrote: > On

Re: [beagleboard] Re: C compiler

On 03/25/2016 06:03 PM, William Hermans wrote: > william@beaglebone:~/ti$ gcc test.c -o test > william@beaglebone:~/ti$ test 'test' is a bash builtin > william@beaglebone:~/ti$ ./test > 32.540001 > > william@beaglebone:~/ti$ sudo ln -s /home/william/ti/test /usr/bin/test Careful.

Re: [beagleboard] Re: C compiler

ooops forgot to add this. william@beaglebone:~/ramfs$ which test william@beaglebone:~/ramfs$ sudo su root@beaglebone:/home/william/ramfs# which test root@beaglebone:/home/william/ramfs# exit exit On Fri, Mar 25, 2016 at 6:42 PM, William Hermans wrote: >

Re: [beagleboard] Re: C compiler

william@beaglebone:~/ramfs$ cat test.c #include int main() { printf("hello world !\n"); return 0; } william@beaglebone:~/ramfs$ gcc test.c -o test william@beaglebone:~/ramfs$ la -al test -bash: la: command not found william@beaglebone:~/ramfs$ ls -al test -rwxr-xr-x 1 william

Re: [beagleboard] Re: C compiler

On 03/25/2016 09:22 PM, William Hermans wrote: So be a little bit clearer for you folks that are wondering what's going on. ~/ti for william on this system is the mount point for an NFS share. Both machines have user william, but it is possible that the UID for each is different. I've run into

Re: [beagleboard] Re: C compiler

So be a little bit clearer for you folks that are wondering what's going on. ~/ti for william on this system is the mount point for an NFS share. Both machines have user william, but it is possible that the UID for each is different. I've run into this problem before, and it creates all sorts of

Re: [beagleboard] Re: C compiler

umask has no effect on the current situation. None, period, zip. On Fri, Mar 25, 2016 at 6:16 PM, Mike wrote: > On 03/25/2016 09:03 PM, William Hermans wrote: > > william@beaglebone:~/ti$ gcc test.c -o test > william@beaglebone:~/ti$ test > william@beaglebone:~/ti$ ./test

Re: [beagleboard] Re: C compiler

On 03/25/2016 09:03 PM, William Hermans wrote: william@beaglebone:~/ti$ gcc test.c -o test william@beaglebone:~/ti$ test william@beaglebone:~/ti$ ./test 32.540001 william@beaglebone:~/ti$ sudo ln -s /home/william/ti/test /usr/bin/test william@beaglebone:~/ti$ test william@beaglebone:~/ti$ cd ..

Re: [beagleboard] Re: C compiler

> > *chmod +x test* > > *Regards,* > Yeah, thats what I thought too, but it doesn't work. I suspect in my case the symbolic link is getting in the way. But thats not the only issues thats going on. Looking into it On Fri, Mar 25, 2016 at 6:10 PM, Robert Nelson wrote: >

Re: [beagleboard] Re: C compiler

On Mar 25, 2016 8:03 PM, "William Hermans" wrote: > > william@beaglebone:~/ti$ gcc test.c -o test > william@beaglebone:~/ti$ test > william@beaglebone:~/ti$ ./test > 32.540001 > > william@beaglebone:~/ti$ sudo ln -s /home/william/ti/test /usr/bin/test > william@beaglebone:~/ti$

Re: [beagleboard] Re: C compiler

william@beaglebone:~/ti$ gcc test.c -o test william@beaglebone:~/ti$ test william@beaglebone:~/ti$ ./test 32.540001 william@beaglebone:~/ti$ sudo ln -s /home/william/ti/test /usr/bin/test william@beaglebone:~/ti$ test william@beaglebone:~/ti$ cd .. william@beaglebone:~$ test william@beaglebone:~$

Re: [beagleboard] Re: C compiler

> > *Nothing at all to do with gcc, reread what I already posted...* Your system, and mine behave nothing alike. For instance if I attempt to run an executable without using dot slash prefixed. The executable will simple fail silently. On Fri, Mar 25, 2016 at 5:30 PM, Mike

Re: [beagleboard] Re: C compiler

On 03/25/2016 08:11 PM, William Hermans wrote: Im guessing that perhaps gcc's -o option now days enables the executable bit on the output file ? I haven't looked into that however. Nothing at all to do with gcc, reread what I already posted... Mike On Fri, Mar 25, 2016 at 5:08 PM, William

Re: [beagleboard] Re: C compiler

Im guessing that perhaps gcc's -o option now days enables the executable bit on the output file ? I haven't looked into that however. On Fri, Mar 25, 2016 at 5:08 PM, William Hermans wrote: > No, Mike is absolutely correct. dot's meaning in this context is current >

Re: [beagleboard] Re: C compiler

No, Mike is absolutely correct. dot's meaning in this context is current directory, and slash is just a path modifier / separator. Putting the file in ones $PATH would solve the "problem" of having to use dot slash I've know this forever, I do not know why I was thinking that chmod +x would solve

Re: [beagleboard] Re: 4D Systems 4DCAPE-70T, no display

any idea when it work perfectly but i hear a noise ?? please help -- 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 receiving emails from it, send

Re: [beagleboard] Arch linux and issues loading device tree overlay at boot via uEnv.txt

On Mar 25, 2016 4:42 PM, "Axe" wrote: > > > Like many, I'm having issues with loading device tree overlays at boot. > > # uname -a > Linux spa.turrim 4.4.4-1-ARCH #1 Sat Mar 5 18:30:09 MST 2016 armv7l GNU/Linux > # > > I have DS3231.dts: > > /dts-v1/; > /plugin/; > > /{ > >

Re: [beagleboard] Arch linux and issues loading device tree overlay at boot via uEnv.txt

Or does it have something to do with the external RTC specifically? I made a cape that had an RTC which loads correctly at boot time using kernel 3.8 something, so maybe it's a kernel problem. Can you check if another cape loads automatically on boot correctly? --David On Fri, Mar 25, 2016 at

[beagleboard] Arch linux and issues loading device tree overlay at boot via uEnv.txt

Like many, I'm having issues with loading device tree overlays at boot. # uname -a Linux spa.turrim 4.4.4-1-ARCH #1 Sat Mar 5 18:30:09 MST 2016 armv7l GNU/Linux # I have DS3231.dts: /dts-v1/; /plugin/; /{ compatible = "ti,beaglebone", "ti,beaglebone-black"; part-number = "BBB-DS3231";

Re: [beagleboard] Re: C compiler

On 03/25/2016 02:03 PM, William Hermans wrote: 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 executable at some point . . . So be nice to fellow group users who

[beagleboard] LCD 4D 7" problem

HI evry one , i am install angestrom in my bbblack, and when i put it in LCD 4D 7" cape , it work but i hear a bad his . help please -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group.

Re: [beagleboard] Re: PRU

On Fri, Mar 25, 2016 at 10:40 AM, Greg wrote: > If you are trying to compile the examples on the Beaglebone (no > cross-compile), you don't need the TI SDK. > The pru compiler and libraries are provided in the Debian 8.3 distribution. > > There is a slight change

Re: [beagleboard] Re: C compiler

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 executable at some point . . . So be nice to fellow group users who actually know what they're talking about, and have

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

Which Linux image is this ? IS this a Wheezy, or Jesse ? On Fri, Mar 25, 2016 at 10:58 AM, William Hermans wrote: > *1. The directory tree in /sys/class/uio is empty, software loading >> firmware into PRU* >> > *exits with SEGFAULT:* > > > That is the real hint. The uio pru

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

> > *1. The directory tree in /sys/class/uio is empty, software loading > firmware into PRU* > *exits with SEGFAULT:* That is the real hint. The uio pru driver module is not loaded. So any attempts to use said files or directory structure is going to fail . . . I'd have to say that something is

[beagleboard] HDMI RGB communitation

Hello, I'm trying to just tryout display with ILI9806E without too much experience around linux drivers so i wanted to just connect it on parallel 16bit rgb bus while HDMI is active and be "snoofing" that communication with that display. I forced proper resolution and CVT with reduced

[beagleboard] Re: PRU

If you are trying to compile the examples on the Beaglebone (no cross-compile), you don't need the TI SDK. The pru compiler and libraries are provided in the Debian 8.3 distribution. There is a slight change required for the Make file in the examples to compile correctly. I've got most of the

Re: [beagleboard] PRU

Hi John, I was getting "rproc_boot failed" Regards, John On Fri, Mar 25, 2016 at 10:22 AM, John Syne wrote: > > On Mar 25, 2016, at 8:35 AM, John Tobias wrote: > > Hi John, > > I were able to compile the missing library. I compiled the programs

Re: [beagleboard] PRU

> On Mar 25, 2016, at 8:35 AM, John Tobias wrote: > > Hi John, > > I were able to compile the missing library. I compiled the programs (git tags > v4.0.0, v4.0.1 and v4.0.2) then copied the toggle_led.out fie into > /lib/firmware and named it to am335x-pru0-fw. > >

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

I'm confused because I recheck the wired configuration. I also tried on a second beagleboneblack with the same configuration. So I'm lost. For me it still look like that the problem came from the pin mux. In fact # cat $PINS | grep '990\|998\|994\|99c' pin 100 (44e10990.0) 0027

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

What am I trying to achieve? 1. Toggle P9_27 via PRU as an "hello world" example. 2. Get uio_pruss up and running, making /sys/class/uio/ not empty anymore 3. Getting "exploringBB/chp13/signalTest" working. What is my current setup? = Linux

Re: [beagleboard] Re: C compiler

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 $ echo 'int main (void) { printf ("Hello, world!\n"); return 0;

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

On Fri, Mar 25, 2016 at 10:01 AM, Le Costaouec Vincent wrote: > I tried directly by copying and past this one, and I had still the same > answer. In addition I have tried to monitor the different signal on the > scope, nothing. > Moreover, nothing new appears on the

Re: [beagleboard] PRU

Hi John, I were able to compile the missing library. I compiled the programs (git tags v4.0.0, v4.0.1 and v4.0.2) then copied the toggle_led.out fie into /lib/firmware and named it to am335x-pru0-fw. None of them and are loading successfully. I am using debian version 8.3 running kernel

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

I tried directly by copying and past this one, and I had still the same answer. In addition I have tried to monitor the different signal on the scope, nothing. Moreover, nothing new appears on the dmesg. # dmesg |tail [ 18.828229] using random self ethernet address [ 18.832790] using random

Re: [beagleboard] Re: C compiler

Yes. sudo chmod 755 myprogram or sudo chmod 755 myprogram.o --- Graham On Fri, Mar 25, 2016 at 9:50 AM, Seppo Nikkilä < seppo.nikk...@innovativeideas.fi> wrote: > myprogram.o > > On Fri, Mar 25, 2016 at 3:27 PM, Graham wrote: > >> And after you create the file for the

Re: [beagleboard] Re: C compiler

myprogram.o On Fri, Mar 25, 2016 at 3:27 PM, Graham wrote: > And after you create the file for the first time, you will need to change > its permissions > so that it is executable. > use an incantation like: > sudo chmod 755 myprogram.c > > You will really need to become

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

On Fri, Mar 25, 2016 at 9:29 AM, Le Costaouec Vincent wrote: > Thank for this quick answer, > > So I have remove the line > cape_disable=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN,BB-BONE-EMMC-2G > > In addition yes I have connected the PIN P9_29

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

Thank for this quick answer, So I have remove the line cape_disable=capemgr.disable_ partno=BB-BONELT-HDMI,BB-BONELT-HDMIN,BB-BONE-EMMC-2G In addition yes I have connected the PIN P9_29 (spi1_d0) and P9_30 (spi_d1) And I'm trying to use the derek molloy program :

[beagleboard] Re: C compiler

And after you create the file for the first time, you will need to change its permissions so that it is executable. use an incantation like: sudo chmod 755 myprogram.c You will really need to become familiar with the basics of Linux, if you are working on a Linux platform like the BeagleBone

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

On Fri, Mar 25, 2016 at 9:03 AM, Le Costaouec Vincent wrote: > Hello, > > I' m currently facing the same issue with the SPI1. However, even with your > solution, it is not working. > > # uname -ra > Linux beagle01 4.1.18-bone20 #4 Fri Mar 18 15:16:19 CET 2016 armv7l

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

Hello, I' m currently facing the same issue with the SPI1. However, even with your solution, it is not working. # uname -ra Linux beagle01 4.1.18-bone20 #4 Fri Mar 18 15:16:19 CET 2016 armv7l GNU/Linux # lsb_release -da Distributor ID:Debian Description:Debian GNU/Linux 8.3 (jessie)

[beagleboard] Re: C compiler

Wadi Ben Rhouma wrote: > [-- text/plain, encoding quoted-printable, charset: UTF-8, 66 lines --] > > thx ,sorry i have another question, i'm not failiar with LINUX , so can u > help me with this , how can i write a C code on the terminal and excute it > on my BBB ?? >

[beagleboard] Load overlay at boot

> > Hello, > I've got a new BeagleBone black, rev. C, and i flashed it with Debian 8.3. > It works fine, but looking around I noticed it loads the cape-universaln > overlay (I looked in sys/devices/platform/bone_capemgr/slots), but in > /boot/uEnv.txt is says it has to load cape-universal. I

[beagleboard] Re: overlays load at boot

On Friday, March 25, 2016 at 1:07:22 PM UTC+2, dorica wrote: > > Hello, > I've got a new BeagleBone black, rev. C, and i flashed it with Debian 8.3. > It works fine, but looking around I noticed it loads the cape-universaln > overlay (I looked in sys/devices/platform/bone_capemgr/slots), but

[beagleboard] overlays load at boot

Hello, I've got a new BeagleBone black, rev. C, and i flashed it with Debian 8.3. It works fine, but looking around I noticed it loads the cape-universaln overlay (I looked in sys/devices/platform/bone_capemgr/slots), but in /boot/uEnv.txt is says it has to load cape-universal. I know the

Re: [beagleboard] C compiler

thx ,sorry i have another question, i'm not familiar with LINUX , so can u help me with this , how can i write a C code on the terminal and excute it on my BBB ?? what command i have to use??? 2016-03-25 11:55 GMT+01:00 Dieter Wirz : > gcc > > On Fri, Mar 25, 2016 at 11:40

Re: [beagleboard] C compiler

thx ,sorry i have another question, i'm not failiar with LINUX , so can u help me with this , how can i write a C code on the terminal and excute it on my BBB ?? 2016-03-25 11:55 GMT+01:00 Dieter Wirz : > gcc > > On Fri, Mar 25, 2016 at 11:40 AM, Brainiac

Re: [beagleboard] C compiler

gcc On Fri, Mar 25, 2016 at 11:40 AM, Brainiac wrote: > hi eeveryone, > > does the BeageleBone Black have a C compiler ? > > i want to controle a step by step motor using BBB with C language , and i'm > wondering if the BBB has an integrated C compiler > > > -- >

[beagleboard] C compiler

hi eeveryone, does the BeageleBone Black have a C compiler ? i want to controle a step by step motor using BBB with C language , and i'm wondering if the BBB has an integrated C compiler -- For more options, visit http://beagleboard.org/discuss --- You received this message because you