Re: [beagleboard] C compiler

[John Syne]

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 hello.c
MBPR:~ john $ ls -la hello
-rwxr-xr-x  1 john  staff  8432 Mar 25 22:17 hello


As you can see, 022 is turning off “group" write and “other" write permissions. 
So normally, touch would provide 0666, but when umask is 022, permission is 
anded with the inverse of umask, which provides 0644. So gcc would create a 
file with 0777 if umask was 000.

Regards,
John




> On Mar 25, 2016, at 5:30 PM, Mike  wrote:
> 
> 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 Hermans > > wrote:
>> 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 
>> that "issue", because it wont.
>> 
>> I do recall at some point perhaps not too long ago that changing file 
>> permissions to executable was required. But now days this does not seem to 
>> be the case . . . I've always in the last several years use ./executable 
>> until I put the executable into my local path . . .
>> 
>> On Fri, Mar 25, 2016 at 2:19 PM, Mike < 
>> bellyac...@gmail.com 
>> > wrote:
>> 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 actually know what they're talking 
>>> about, and have been on this list a lot longer than you.
>> Maybe we need to learn what ./ does...  It has absolutely nothing to do with 
>> a files permissions or whether it's executable or not.  It's use is 
>> regarding the lack of the current directory "." in one's PATH variable.  
>> Umask is (largely) what controls what permissions a file is created with.
>> 
>> mike@pride-n-joy:~/test.d$  ls -al
>> total 12
>> drwxr-xr-x  2 mike mike 4096 Mar 25 17:07 .
>> drwxr-xr-x 37 mike mike 4096 Mar 25 16:46 ..
>> -rw-r--r--  1 mike mike   78 Mar 25 16:47 hello.c
>> mike@pride-n-joy:~/test.d$  umask
>> 0022
>> mike@pride-n-joy:~/test.d$  gcc -Wall 
>> -o hello hello.c 
>> mike@pride-n-joy:~/test.d$  ls -l
>> total 12
>> -rwxr-xr-x 1 mike mike 6696 Mar 25 17:08 hello
>> -rw-r--r-- 1 mike mike   78 Mar 25 16:47 hello.c
>> mike@pride-n-joy:~/test.d$  hello
>> bash: hello: command not found
>> mike@pride-n-joy:~/test.d$  ./hello 
>> Hello, world!
>> mike@pride-n-joy:~/test.d$  umask 0137
>> mike@pride-n-joy:~/test.d$  gcc -Wall 
>> -o hello hello.c 
>> mike@pride-n-joy:~/test.d$  ls -l
>> total 12
>> -rw-r- 1 mike mike 6696 Mar 25 17:09 hello
>> -rw-r--r-- 1 mike mike   78 Mar 25 16:47 hello.c
>> mike@pride-n-joy:~/test.d$  hello
>> bash: hello: command not found
>> mike@pride-n-joy:~/test.d$  ./hello
>> bash: ./hello: Permission denied
>> mike@pride-n-joy:~/test.d$  ls -l
>> total 12
>> -rw-r- 1 mike mike 6696 Mar 25 17:09 hello
>> -rw-r--r-- 1 mike mike   78 Mar 25 16:47 hello.c
>> mike@pride-n-joy:~/test.d$  chmod 0750 
>> hello
>> mike@pride-n-joy:~/test.d$  ls -l
>> total 12
>> -rwxr-x--- 1 mike mike 6696 Mar 25 17:09 hello
>> -rw-r--r-- 1 mike mike   78 Mar 25 16:47 hello.c
>> mike@pride-n-joy:~/test.d$  ./hello 
>> Hello, world!
>> mike@pride-n-joy:~/test.d$  umask 022
>> mike@pride-n-joy:~/test.d$  umask
>> 0022
>> mike@pride-n-joy:~/test.d$ 
>> 
>> Mike 
>>> 
>>> On Fri, Mar 25, 2016 at 8:53 AM, Dieter Wirz < 
>>> didi.w...@gmail.com 
>>> > wrote:
>>> On Fri, Mar 25, 

Re: [beagleboard] Re: C compiler

[William Hermans]

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 . . .anyone care to take a stab at what
the most common executable name will be for test applications ?

Could I have checked for "test" as an existing executable ? Yes, certainly,
but would I in any right state of mind even think that I should check ? No,
probably not . . . So yes, I could probably be a better user and look
before I leap, but why in hell would an default *anything* named test exist
on any Linux system ? Guess we'll either have to ask the maintainer(s) of
bash and ask them wtf they were thinking, or just move on . . .

On Fri, Mar 25, 2016 at 7:01 PM, Mike  wrote:

> 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 
> wrote:
>
>> 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 william 5047 Mar 25 18:31 test
>> william@beaglebone:~/ramfs$ umask 022
>> william@beaglebone:~/ramfs$ test
>> william@beaglebone:~/ramfs$ umask 0137
>> william@beaglebone:~/ramfs$ test
>> william@beaglebone:~/ramfs$ ./test
>> hello world !
>> william@beaglebone:~/ramfs$ chmod u+x test
>> william@beaglebone:~/ramfs$ test
>> william@beaglebone:~/ramfs$ umask 022
>> william@beaglebone:~/ramfs$ test
>> william@beaglebone:~/ramfs$ sudo test
>> sudo: test: command not found
>> william@beaglebone:~/ramfs$ umask 0137
>> william@beaglebone:~/ramfs$ sudo test
>> sudo: test: command not found
>> william@beaglebone:~/ramfs$ export PATH=$PATH:/home/william/ramfs/
>> william@beaglebone:~/ramfs$ test
>> william@beaglebone:~/ramfs$ echo $PATH
>>
>> /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/home/william/ramfs/
>>
>> At this point I decided that the executable "test" is a bad choice for
>> some reason unknown to me.
>>
>>
>> william@beaglebone:~/ramfs$ mv test.c hello.c
>> william@beaglebone:~/ramfs$ rm test
>> william@beaglebone:~/ramfs$ ls -al
>> total 8
>> drwxrwxrwt 2 rootroot  60 Mar 25 18:36 .
>> drwxr-xr-x 4 william william 4096 Jan  3 16:16 ..
>> -rw-r--r-- 1 william william   74 Mar 25 18:26 hello.c
>> william@beaglebone:~/ramfs$ gcc hello.c -o hello
>> william@beaglebone:~/ramfs$ hello
>> -bash: /home/william/ramfs/hello: Permission denied
>> william@beaglebone:~/ramfs$ chmod +x hello
>> william@beaglebone:~/ramfs$ hello
>> -bash: /home/william/ramfs/hello: Permission denied
>> william@beaglebone:~/ramfs$ sudo hello
>> sudo: hello: command not found
>> william@beaglebone:~/ramfs$ ./hello
>> -bash: ./hello: Permission denied
>> william@beaglebone:~/ramfs$ chmod u+x hello
>> william@beaglebone:~/ramfs$ sudo hello
>> sudo: hello: command not found
>>
>> oops forgot about umask .  .
>>
>> william@beaglebone:~/ramfs$ umask 022
>> william@beaglebone:~/ramfs$ sudo hello
>> sudo: hello: command not found
>>
>> d'oh, of course this wont work . . . the executable is not in roots path.
>>
>> william@beaglebone:~/ramfs$ hello
>> hello world !
>> william@beaglebone:~/ramfs$ ./hello
>> hello world !
>> william@beaglebone:~/ramfs$
>>
>> So yes, really weird the executable "test" is not working correctly on
>> this system, and yes, I ran which test, and in fact . . .
>>
> Your not getting the usage of umask at all.  It doesn't change permissions
> on an existing file..
>
> I'd suggest man umask...
>
> Mike
>
> --
> 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 an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: C compiler

[Mike]

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 > wrote:


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 william 5047 Mar 25 18:31 test
william@beaglebone:~/ramfs$ umask 022
william@beaglebone:~/ramfs$ test
william@beaglebone:~/ramfs$ umask 0137
william@beaglebone:~/ramfs$ test
william@beaglebone:~/ramfs$ ./test
hello world !
william@beaglebone:~/ramfs$ chmod u+x test
william@beaglebone:~/ramfs$ test
william@beaglebone:~/ramfs$ umask 022
william@beaglebone:~/ramfs$ test
william@beaglebone:~/ramfs$ sudo test
sudo: test: command not found
william@beaglebone:~/ramfs$ umask 0137
william@beaglebone:~/ramfs$ sudo test
sudo: test: command not found
william@beaglebone:~/ramfs$ export PATH=$PATH:/home/william/ramfs/
william@beaglebone:~/ramfs$ test
william@beaglebone:~/ramfs$ echo $PATH

/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/home/william/ramfs/

At this point I decided that the executable "test" is a bad choice
for some reason unknown to me.


william@beaglebone:~/ramfs$ mv test.c hello.c
william@beaglebone:~/ramfs$ rm test
william@beaglebone:~/ramfs$ ls -al
total 8
drwxrwxrwt 2 rootroot  60 Mar 25 18:36 .
drwxr-xr-x 4 william william 4096 Jan  3 16:16 ..
-rw-r--r-- 1 william william   74 Mar 25 18:26 hello.c
william@beaglebone:~/ramfs$ gcc hello.c -o hello
william@beaglebone:~/ramfs$ hello
-bash: /home/william/ramfs/hello: Permission denied
william@beaglebone:~/ramfs$ chmod +x hello
william@beaglebone:~/ramfs$ hello
-bash: /home/william/ramfs/hello: Permission denied
william@beaglebone:~/ramfs$ sudo hello
sudo: hello: command not found
william@beaglebone:~/ramfs$ ./hello
-bash: ./hello: Permission denied
william@beaglebone:~/ramfs$ chmod u+x hello
william@beaglebone:~/ramfs$ sudo hello
sudo: hello: command not found

oops forgot about umask .  .

william@beaglebone:~/ramfs$ umask 022
william@beaglebone:~/ramfs$ sudo hello
sudo: hello: command not found

d'oh, of course this wont work . . . the executable is not in
roots path.

william@beaglebone:~/ramfs$ hello
hello world !
william@beaglebone:~/ramfs$ ./hello
hello world !
william@beaglebone:~/ramfs$

So yes, really weird the executable "test" is not working
correctly on this system, and yes, I ran which test, and in fact . . .

Your not getting the usage of umask at all.  It doesn't change 
permissions on an existing file..


I'd suggest man umask...

Mike

--
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 an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Load overlay at boot

[Greg]

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 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 an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: C compiler

[Mike]

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
test is a shell builtin
root@ticktock:/dev# type -a test
test is a shell builtin
test is /usr/bin/test
root@ticktock:/dev#

Mike

--
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 an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: C compiler

[William Hermans]

>
> *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 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. '/usr/bin/test' is often a real program for
> shells that don't have builtin 'test'. Which you just
> overwrote.
>
>
> > william@beaglebone:~/ti$ test
> > william@beaglebone:~/ti$ cd ..
> > william@beaglebone:~$ test
> > william@beaglebone:~$ sudo test
> > 32.540001
> >
> > So, it's a permissions issue. . .
>
> Nope. shell builtin aliasing.
>
> This thread has so much bad advice in it.
>
> Regards,
> Peter Hurley
>
> --
> 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 an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: C compiler

[Peter Hurley]

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. '/usr/bin/test' is often a real program for
shells that don't have builtin 'test'. Which you just
overwrote.


> william@beaglebone:~/ti$ test
> william@beaglebone:~/ti$ cd ..
> william@beaglebone:~$ test
> william@beaglebone:~$ sudo test
> 32.540001
> 
> So, it's a permissions issue. . .

Nope. shell builtin aliasing.

This thread has so much bad advice in it.

Regards,
Peter Hurley

-- 
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 an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: C compiler

[William Hermans]

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:

> 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 william 5047 Mar 25 18:31 test
> william@beaglebone:~/ramfs$ umask 022
> william@beaglebone:~/ramfs$ test
> william@beaglebone:~/ramfs$ umask 0137
> william@beaglebone:~/ramfs$ test
> william@beaglebone:~/ramfs$ ./test
> hello world !
> william@beaglebone:~/ramfs$ chmod u+x test
> william@beaglebone:~/ramfs$ test
> william@beaglebone:~/ramfs$ umask 022
> william@beaglebone:~/ramfs$ test
> william@beaglebone:~/ramfs$ sudo test
> sudo: test: command not found
> william@beaglebone:~/ramfs$ umask 0137
> william@beaglebone:~/ramfs$ sudo test
> sudo: test: command not found
> william@beaglebone:~/ramfs$ export PATH=$PATH:/home/william/ramfs/
> william@beaglebone:~/ramfs$ test
> william@beaglebone:~/ramfs$ echo $PATH
>
> /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/home/william/ramfs/
>
> At this point I decided that the executable "test" is a bad choice for
> some reason unknown to me.
>
>
> william@beaglebone:~/ramfs$ mv test.c hello.c
> william@beaglebone:~/ramfs$ rm test
> william@beaglebone:~/ramfs$ ls -al
> total 8
> drwxrwxrwt 2 rootroot  60 Mar 25 18:36 .
> drwxr-xr-x 4 william william 4096 Jan  3 16:16 ..
> -rw-r--r-- 1 william william   74 Mar 25 18:26 hello.c
> william@beaglebone:~/ramfs$ gcc hello.c -o hello
> william@beaglebone:~/ramfs$ hello
> -bash: /home/william/ramfs/hello: Permission denied
> william@beaglebone:~/ramfs$ chmod +x hello
> william@beaglebone:~/ramfs$ hello
> -bash: /home/william/ramfs/hello: Permission denied
> william@beaglebone:~/ramfs$ sudo hello
> sudo: hello: command not found
> william@beaglebone:~/ramfs$ ./hello
> -bash: ./hello: Permission denied
> william@beaglebone:~/ramfs$ chmod u+x hello
> william@beaglebone:~/ramfs$ sudo hello
> sudo: hello: command not found
>
> oops forgot about umask .  .
>
> william@beaglebone:~/ramfs$ umask 022
> william@beaglebone:~/ramfs$ sudo hello
> sudo: hello: command not found
>
> d'oh, of course this wont work . . . the executable is not in roots path.
>
> william@beaglebone:~/ramfs$ hello
> hello world !
> william@beaglebone:~/ramfs$ ./hello
> hello world !
> william@beaglebone:~/ramfs$
>
> So yes, really weird the executable "test" is not working correctly on
> this system, and yes, I ran which test, and in fact . . .
>
>
> On Fri, Mar 25, 2016 at 6:30 PM, Mike  wrote:
>
>> 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 this problem before, and it creates all sorts
>> of strange behavior. So, I'll write a simple hello world executable
>> locally, in tmpfs . . .
>>
>> Adding symlinks and NFS with a different UID will certainly skew the
>> results!
>>
>> Umask *does* have an effect, it determines what permissions a file gets
>> created with, regardless of how you create it.
>>
>>
>> Mike
>>
>> On Fri, Mar 25, 2016 at 6:17 PM, William Hermans 
>> wrote:
>>
>>> umask has no effect on the current situation. None, period, zip.
>>>
>>> On Fri, Mar 25, 2016 at 6:16 PM, Mike < 
>>> bellyac...@gmail.com> 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
 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:~$ sudo test
 32.540001

 So, it's a permissions issue. . .

 Exactly, yet you haven't show any of the file permissions in your above
 foray.

 Again I'll say it umask is largely what controls how permissions are
 set when files are created.  This is basic *nix 101...


 Mike


 On Fri, Mar 25, 2016 at 5:41 PM, William Hermans < 
 yyrk...@gmail.com> wrote:

> *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.
>

Re: [beagleboard] Re: C compiler

[William Hermans]

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 william 5047 Mar 25 18:31 test
william@beaglebone:~/ramfs$ umask 022
william@beaglebone:~/ramfs$ test
william@beaglebone:~/ramfs$ umask 0137
william@beaglebone:~/ramfs$ test
william@beaglebone:~/ramfs$ ./test
hello world !
william@beaglebone:~/ramfs$ chmod u+x test
william@beaglebone:~/ramfs$ test
william@beaglebone:~/ramfs$ umask 022
william@beaglebone:~/ramfs$ test
william@beaglebone:~/ramfs$ sudo test
sudo: test: command not found
william@beaglebone:~/ramfs$ umask 0137
william@beaglebone:~/ramfs$ sudo test
sudo: test: command not found
william@beaglebone:~/ramfs$ export PATH=$PATH:/home/william/ramfs/
william@beaglebone:~/ramfs$ test
william@beaglebone:~/ramfs$ echo $PATH
/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/home/william/ramfs/

At this point I decided that the executable "test" is a bad choice for some
reason unknown to me.


william@beaglebone:~/ramfs$ mv test.c hello.c
william@beaglebone:~/ramfs$ rm test
william@beaglebone:~/ramfs$ ls -al
total 8
drwxrwxrwt 2 rootroot  60 Mar 25 18:36 .
drwxr-xr-x 4 william william 4096 Jan  3 16:16 ..
-rw-r--r-- 1 william william   74 Mar 25 18:26 hello.c
william@beaglebone:~/ramfs$ gcc hello.c -o hello
william@beaglebone:~/ramfs$ hello
-bash: /home/william/ramfs/hello: Permission denied
william@beaglebone:~/ramfs$ chmod +x hello
william@beaglebone:~/ramfs$ hello
-bash: /home/william/ramfs/hello: Permission denied
william@beaglebone:~/ramfs$ sudo hello
sudo: hello: command not found
william@beaglebone:~/ramfs$ ./hello
-bash: ./hello: Permission denied
william@beaglebone:~/ramfs$ chmod u+x hello
william@beaglebone:~/ramfs$ sudo hello
sudo: hello: command not found

oops forgot about umask .  .

william@beaglebone:~/ramfs$ umask 022
william@beaglebone:~/ramfs$ sudo hello
sudo: hello: command not found

d'oh, of course this wont work . . . the executable is not in roots path.

william@beaglebone:~/ramfs$ hello
hello world !
william@beaglebone:~/ramfs$ ./hello
hello world !
william@beaglebone:~/ramfs$

So yes, really weird the executable "test" is not working correctly on this
system, and yes, I ran which test, and in fact . . .


On Fri, Mar 25, 2016 at 6:30 PM, Mike  wrote:

> 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 this problem before, and it creates all sorts
> of strange behavior. So, I'll write a simple hello world executable
> locally, in tmpfs . . .
>
> Adding symlinks and NFS with a different UID will certainly skew the
> results!
>
> Umask *does* have an effect, it determines what permissions a file gets
> created with, regardless of how you create it.
>
>
> Mike
>
> On Fri, Mar 25, 2016 at 6:17 PM, William Hermans 
> wrote:
>
>> umask has no effect on the current situation. None, period, zip.
>>
>> On Fri, Mar 25, 2016 at 6:16 PM, Mike < 
>> bellyac...@gmail.com> 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
>>> 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:~$ sudo test
>>> 32.540001
>>>
>>> So, it's a permissions issue. . .
>>>
>>> Exactly, yet you haven't show any of the file permissions in your above
>>> foray.
>>>
>>> Again I'll say it umask is largely what controls how permissions are set
>>> when files are created.  This is basic *nix 101...
>>>
>>>
>>> Mike
>>>
>>>
>>> On Fri, Mar 25, 2016 at 5:41 PM, William Hermans < 
>>> yyrk...@gmail.com> wrote:
>>>
 *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 < 
 bellyac...@gmail.com> wrote:

> 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 Hermans < 

Re: [beagleboard] Re: C compiler

[Mike]

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 this problem before, and 
it creates all sorts of strange behavior. So, I'll write a simple 
hello world executable locally, in tmpfs . . .


Adding symlinks and NFS with a different UID will certainly skew the 
results!


Umask *does* have an effect, it determines what permissions a file gets 
created with, regardless of how you create it.


Mike
On Fri, Mar 25, 2016 at 6:17 PM, William Hermans > wrote:


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
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:~$ sudo test
32.540001

So, it's a permissions issue. . .

Exactly, yet you haven't show any of the file permissions in
your above foray.

Again I'll say it umask is largely what controls how
permissions are set when files are created. This is basic *nix
101...


Mike


On Fri, Mar 25, 2016 at 5:41 PM, William Hermans
> wrote:

/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
> wrote:

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 Hermans
> wrote:

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 that "issue", because it wont.

I do recall at some point perhaps not too long
ago that changing file permissions to executable
was required. But now days this does not seem to
be the case . . . I've always in the last
several years use ./executable until I put the
executable into my local path . . .

On Fri, Mar 25, 2016 at 2:19 PM, Mike
> wrote:

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
actually know what they're talking about,
and have been on this list a lot longer
than you.

Maybe we need to learn what ./ does...  It
has absolutely nothing to do with a files
permissions or whether it's executable or
not.  It's use is regarding the lack of the
current directory "." in one's PATH
variable. Umask is (largely) what controls
what permissions a file is created with.

mike@pride-n-joy:~/test.d$
 ls -al
 

Re: [beagleboard] Re: C compiler

[William Hermans]

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 strange behavior. So, I'll write a simple hello world executable
locally, in tmpfs . . .

On Fri, Mar 25, 2016 at 6:17 PM, William Hermans  wrote:

> 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
>> 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:~$ sudo test
>> 32.540001
>>
>> So, it's a permissions issue. . .
>>
>> Exactly, yet you haven't show any of the file permissions in your above
>> foray.
>>
>> Again I'll say it umask is largely what controls how permissions are set
>> when files are created.  This is basic *nix 101...
>>
>>
>> Mike
>>
>>
>> On Fri, Mar 25, 2016 at 5:41 PM, William Hermans 
>> wrote:
>>
>>> *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 < 
>>> bellyac...@gmail.com> wrote:
>>>
 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 Hermans < 
 yyrk...@gmail.com> wrote:

> 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 that "issue", because it wont.
>
> I do recall at some point perhaps not too long ago that changing file
> permissions to executable was required. But now days this does not seem to
> be the case . . . I've always in the last several years use ./executable
> until I put the executable into my local path . . .
>
> On Fri, Mar 25, 2016 at 2:19 PM, Mike < 
> bellyac...@gmail.com> wrote:
>
>> 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 actually know what they're
>> talking about, and have been on this list a lot longer than you.
>>
>> Maybe we need to learn what ./ does...  It has absolutely nothing to
>> do with a files permissions or whether it's executable or not.  It's use 
>> is
>> regarding the lack of the current directory "." in one's PATH variable.
>> Umask is (largely) what controls what permissions a file is created with.
>>
>> mike@pride-n-joy:~/test.d$ ls -al
>> total 12
>> drwxr-xr-x  2 mike mike 4096 Mar 25 17:07 .
>> drwxr-xr-x 37 mike mike 4096 Mar 25 16:46 ..
>> -rw-r--r--  1 mike mike   78 Mar 25 16:47 hello.c
>> mike@pride-n-joy:~/test.d$ umask
>> 0022
>> mike@pride-n-joy:~/test.d$ gcc -Wall
>> -o hello hello.c
>> mike@pride-n-joy:~/test.d$ ls -l
>> total 12
>> -rwxr-xr-x 1 mike mike 6696 Mar 25 17:08 hello
>> -rw-r--r-- 1 mike mike   78 Mar 25 16:47 hello.c
>> mike@pride-n-joy:~/test.d$ hello
>> bash: hello: command not found
>> mike@pride-n-joy:~/test.d$ ./hello
>> Hello, world!
>> mike@pride-n-joy:~/test.d$ umask 0137
>> mike@pride-n-joy:~/test.d$ gcc -Wall
>> -o hello hello.c
>> mike@pride-n-joy:~/test.d$ ls -l
>> total 12
>> -rw-r- 1 mike mike 6696 Mar 25 17:09 hello
>> -rw-r--r-- 1 mike mike   78 Mar 25 16:47 hello.c
>> mike@pride-n-joy:~/test.d$ hello
>> 

Re: [beagleboard] Re: C compiler

[William Hermans]

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
> 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:~$ sudo test
> 32.540001
>
> So, it's a permissions issue. . .
>
> Exactly, yet you haven't show any of the file permissions in your above
> foray.
>
> Again I'll say it umask is largely what controls how permissions are set
> when files are created.  This is basic *nix 101...
>
>
> Mike
>
>
> On Fri, Mar 25, 2016 at 5:41 PM, William Hermans 
> wrote:
>
>> *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 < 
>> bellyac...@gmail.com> wrote:
>>
>>> 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 Hermans < 
>>> yyrk...@gmail.com> wrote:
>>>
 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 that "issue", because it wont.

 I do recall at some point perhaps not too long ago that changing file
 permissions to executable was required. But now days this does not seem to
 be the case . . . I've always in the last several years use ./executable
 until I put the executable into my local path . . .

 On Fri, Mar 25, 2016 at 2:19 PM, Mike < 
 bellyac...@gmail.com> wrote:

> 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 actually know what they're
> talking about, and have been on this list a lot longer than you.
>
> Maybe we need to learn what ./ does...  It has absolutely nothing to
> do with a files permissions or whether it's executable or not.  It's use 
> is
> regarding the lack of the current directory "." in one's PATH variable.
> Umask is (largely) what controls what permissions a file is created with.
>
> mike@pride-n-joy:~/test.d$ ls -al
> total 12
> drwxr-xr-x  2 mike mike 4096 Mar 25 17:07 .
> drwxr-xr-x 37 mike mike 4096 Mar 25 16:46 ..
> -rw-r--r--  1 mike mike   78 Mar 25 16:47 hello.c
> mike@pride-n-joy:~/test.d$ umask
> 0022
> mike@pride-n-joy:~/test.d$ gcc -Wall -o
> hello hello.c
> mike@pride-n-joy:~/test.d$ ls -l
> total 12
> -rwxr-xr-x 1 mike mike 6696 Mar 25 17:08 hello
> -rw-r--r-- 1 mike mike   78 Mar 25 16:47 hello.c
> mike@pride-n-joy:~/test.d$ hello
> bash: hello: command not found
> mike@pride-n-joy:~/test.d$ ./hello
> Hello, world!
> mike@pride-n-joy:~/test.d$ umask 0137
> mike@pride-n-joy:~/test.d$ gcc -Wall -o
> hello hello.c
> mike@pride-n-joy:~/test.d$ ls -l
> total 12
> -rw-r- 1 mike mike 6696 Mar 25 17:09 hello
> -rw-r--r-- 1 mike mike   78 Mar 25 16:47 hello.c
> mike@pride-n-joy:~/test.d$ hello
> bash: hello: command not found
> mike@pride-n-joy:~/test.d$ ./hello
> bash: ./hello: Permission denied
> mike@pride-n-joy:~/test.d$ ls -l
> total 12
> -rw-r- 1 mike mike 6696 Mar 25 17:09 hello
> -rw-r--r-- 1 mike mike   78 Mar 25 16:47 hello.c
> mike@pride-n-joy:~/test.d$ chmod 0750
> hello
> mike@pride-n-joy:~/test.d$ ls -l
> total 12
> -rwxr-x--- 1 mike mike 6696 Mar 25 17:09 hello
> -rw-r--r-- 1 mike mike   78 

Re: [beagleboard] Re: C compiler

[Mike]

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 ..
william@beaglebone:~$ test
william@beaglebone:~$ sudo test
32.540001

So, it's a permissions issue. . .
Exactly, yet you haven't show any of the file permissions in your above 
foray.


Again I'll say it umask is largely what controls how permissions are set 
when files are created.  This is basic *nix 101...


Mike


On Fri, Mar 25, 2016 at 5:41 PM, William Hermans > wrote:


/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 > wrote:

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 Hermans
> wrote:

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 that "issue", because it wont.

I do recall at some point perhaps not too long ago that
changing file permissions to executable was required. But
now days this does not seem to be the case . . . I've
always in the last several years use ./executable until I
put the executable into my local path . . .

On Fri, Mar 25, 2016 at 2:19 PM, Mike
> wrote:

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 actually know
what they're talking about, and have been on this
list a lot longer than you.

Maybe we need to learn what ./ does... It has
absolutely nothing to do with a files permissions or
whether it's executable or not.  It's use is
regarding the lack of the current directory "." in
one's PATH variable.  Umask is (largely) what
controls what permissions a file is created with.

mike@pride-n-joy:~/test.d$
 ls -al
total 12
drwxr-xr-x  2 mike mike 4096 Mar 25 17:07 .
drwxr-xr-x 37 mike mike 4096 Mar 25 16:46 ..
-rw-r--r--  1 mike mike   78 Mar 25 16:47 hello.c
mike@pride-n-joy:~/test.d$
 umask
0022
mike@pride-n-joy:~/test.d$
 gcc -Wall -o
hello hello.c
mike@pride-n-joy:~/test.d$
 ls -l
total 12
-rwxr-xr-x 1 mike mike 6696 Mar 25 17:08 hello
-rw-r--r-- 1 mike mike 78 Mar 25 16:47 hello.c
mike@pride-n-joy:~/test.d$
 hello
bash: hello: command not found
mike@pride-n-joy:~/test.d$
 ./hello
Hello, world!
mike@pride-n-joy:~/test.d$
 umask 0137
mike@pride-n-joy:~/test.d$
 gcc -Wall -o
hello hello.c
mike@pride-n-joy:~/test.d$
 ls -l
total 12
-rw-r- 1 mike mike 6696 Mar 25 17:09 hello
-rw-r--r-- 1 mike mike 78 Mar 25 16:47 hello.c
mike@pride-n-joy:~/test.d$

Re: [beagleboard] Re: C compiler

[William Hermans]

>
> *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:

>
> 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$ test
> > william@beaglebone:~/ti$ cd ..
> > william@beaglebone:~$ test
> > william@beaglebone:~$ sudo test
> > 32.540001
> >
> > So, it's a permissions issue. . .
>
> chmod +x test
>
> Regards,
>
> --
> 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 an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: C compiler

[Robert Nelson]

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$ test
> william@beaglebone:~/ti$ cd ..
> william@beaglebone:~$ test
> william@beaglebone:~$ sudo test
> 32.540001
>
> So, it's a permissions issue. . .

chmod +x test

Regards,

-- 
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 an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: C compiler

[William Hermans]

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:~$ sudo test
32.540001

So, it's a permissions issue. . .

On Fri, Mar 25, 2016 at 5:41 PM, William Hermans  wrote:

> *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  wrote:
>
>> 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 Hermans 
>> wrote:
>>
>>> 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 that "issue", because it wont.
>>>
>>> I do recall at some point perhaps not too long ago that changing file
>>> permissions to executable was required. But now days this does not seem to
>>> be the case . . . I've always in the last several years use ./executable
>>> until I put the executable into my local path . . .
>>>
>>> On Fri, Mar 25, 2016 at 2:19 PM, Mike < 
>>> bellyac...@gmail.com> wrote:
>>>
 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 actually know what they're talking
 about, and have been on this list a lot longer than you.

 Maybe we need to learn what ./ does...  It has absolutely nothing to do
 with a files permissions or whether it's executable or not.  It's use is
 regarding the lack of the current directory "." in one's PATH variable.
 Umask is (largely) what controls what permissions a file is created with.

 mike@pride-n-joy:~/test.d$ ls -al
 total 12
 drwxr-xr-x  2 mike mike 4096 Mar 25 17:07 .
 drwxr-xr-x 37 mike mike 4096 Mar 25 16:46 ..
 -rw-r--r--  1 mike mike   78 Mar 25 16:47 hello.c
 mike@pride-n-joy:~/test.d$ umask
 0022
 mike@pride-n-joy:~/test.d$ gcc -Wall -o hello hello.c
 mike@pride-n-joy:~/test.d$ ls -l
 total 12
 -rwxr-xr-x 1 mike mike 6696 Mar 25 17:08 hello
 -rw-r--r-- 1 mike mike   78 Mar 25 16:47 hello.c
 mike@pride-n-joy:~/test.d$ hello
 bash: hello: command not found
 mike@pride-n-joy:~/test.d$ ./hello
 Hello, world!
 mike@pride-n-joy:~/test.d$ umask 0137
 mike@pride-n-joy:~/test.d$ gcc -Wall -o hello hello.c
 mike@pride-n-joy:~/test.d$ ls -l
 total 12
 -rw-r- 1 mike mike 6696 Mar 25 17:09 hello
 -rw-r--r-- 1 mike mike   78 Mar 25 16:47 hello.c
 mike@pride-n-joy:~/test.d$ hello
 bash: hello: command not found
 mike@pride-n-joy:~/test.d$ ./hello
 bash: ./hello: Permission denied
 mike@pride-n-joy:~/test.d$ ls -l
 total 12
 -rw-r- 1 mike mike 6696 Mar 25 17:09 hello
 -rw-r--r-- 1 mike mike   78 Mar 25 16:47 hello.c
 mike@pride-n-joy:~/test.d$ chmod 0750 hello
 mike@pride-n-joy:~/test.d$ ls -l
 total 12
 -rwxr-x--- 1 mike mike 6696 Mar 25 17:09 hello
 -rw-r--r-- 1 mike mike   78 Mar 25 16:47 hello.c
 mike@pride-n-joy:~/test.d$ ./hello
 Hello, world!
 mike@pride-n-joy:~/test.d$ umask 022
 mike@pride-n-joy:~/test.d$ umask
 0022
 mike@pride-n-joy:~/test.d$

 Mike


 On Fri, Mar 25, 2016 at 8:53 AM, Dieter Wirz < 
 didi.w...@gmail.com> wrote:

> On Fri, Mar 25, 2016 at 3:57 PM, Graham Haddock <
> gra...@flexradio.com> 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; }'
> >> hello.c
> $ cat hello.c
> #include 
> int main (void) {  printf ("Hello, world!\n");   return 0; }
> $ gcc -Wall -o hello hello.c
> $ ./hello
> Hello, world!
> $ ls -l
> total 12
> -rwxrwxr-x 1 dw dw 7332 Mar 25 16:32 hello
> -rw-rw-r-- 1 dw dw   

Re: [beagleboard] Re: C compiler

[William Hermans]

>
> *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  wrote:

> 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 Hermans 
> wrote:
>
>> 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 that "issue", because it wont.
>>
>> I do recall at some point perhaps not too long ago that changing file
>> permissions to executable was required. But now days this does not seem to
>> be the case . . . I've always in the last several years use ./executable
>> until I put the executable into my local path . . .
>>
>> On Fri, Mar 25, 2016 at 2:19 PM, Mike < 
>> bellyac...@gmail.com> wrote:
>>
>>> 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 actually know what they're talking
>>> about, and have been on this list a lot longer than you.
>>>
>>> Maybe we need to learn what ./ does...  It has absolutely nothing to do
>>> with a files permissions or whether it's executable or not.  It's use is
>>> regarding the lack of the current directory "." in one's PATH variable.
>>> Umask is (largely) what controls what permissions a file is created with.
>>>
>>> mike@pride-n-joy:~/test.d$ ls -al
>>> total 12
>>> drwxr-xr-x  2 mike mike 4096 Mar 25 17:07 .
>>> drwxr-xr-x 37 mike mike 4096 Mar 25 16:46 ..
>>> -rw-r--r--  1 mike mike   78 Mar 25 16:47 hello.c
>>> mike@pride-n-joy:~/test.d$ umask
>>> 0022
>>> mike@pride-n-joy:~/test.d$ gcc -Wall -o hello hello.c
>>> mike@pride-n-joy:~/test.d$ ls -l
>>> total 12
>>> -rwxr-xr-x 1 mike mike 6696 Mar 25 17:08 hello
>>> -rw-r--r-- 1 mike mike   78 Mar 25 16:47 hello.c
>>> mike@pride-n-joy:~/test.d$ hello
>>> bash: hello: command not found
>>> mike@pride-n-joy:~/test.d$ ./hello
>>> Hello, world!
>>> mike@pride-n-joy:~/test.d$ umask 0137
>>> mike@pride-n-joy:~/test.d$ gcc -Wall -o hello hello.c
>>> mike@pride-n-joy:~/test.d$ ls -l
>>> total 12
>>> -rw-r- 1 mike mike 6696 Mar 25 17:09 hello
>>> -rw-r--r-- 1 mike mike   78 Mar 25 16:47 hello.c
>>> mike@pride-n-joy:~/test.d$ hello
>>> bash: hello: command not found
>>> mike@pride-n-joy:~/test.d$ ./hello
>>> bash: ./hello: Permission denied
>>> mike@pride-n-joy:~/test.d$ ls -l
>>> total 12
>>> -rw-r- 1 mike mike 6696 Mar 25 17:09 hello
>>> -rw-r--r-- 1 mike mike   78 Mar 25 16:47 hello.c
>>> mike@pride-n-joy:~/test.d$ chmod 0750 hello
>>> mike@pride-n-joy:~/test.d$ ls -l
>>> total 12
>>> -rwxr-x--- 1 mike mike 6696 Mar 25 17:09 hello
>>> -rw-r--r-- 1 mike mike   78 Mar 25 16:47 hello.c
>>> mike@pride-n-joy:~/test.d$ ./hello
>>> Hello, world!
>>> mike@pride-n-joy:~/test.d$ umask 022
>>> mike@pride-n-joy:~/test.d$ umask
>>> 0022
>>> mike@pride-n-joy:~/test.d$
>>>
>>> Mike
>>>
>>>
>>> On Fri, Mar 25, 2016 at 8:53 AM, Dieter Wirz < 
>>> didi.w...@gmail.com> wrote:
>>>
 On Fri, Mar 25, 2016 at 3:57 PM, Graham Haddock <
 gra...@flexradio.com> 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; }'
 >> hello.c
 $ cat hello.c
 #include 
 int main (void) {  printf ("Hello, world!\n");   return 0; }
 $ gcc -Wall -o hello hello.c
 $ ./hello
 Hello, world!
 $ ls -l
 total 12
 -rwxrwxr-x 1 dw dw 7332 Mar 25 16:32 hello
 -rw-rw-r-- 1 dw dw   80 Mar 25 16:31 hello.c
 $

 No chmod needed, no myprogram.o there, why the sudo

>>>
>>> --
>>> 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
>>> an email to 
>>> beagleboard+unsubscr...@googlegroups.com.
>>> For more options, visit 

Re: [beagleboard] Re: C compiler

[Mike]

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 Hermans > wrote:


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 that "issue", because it wont.

I do recall at some point perhaps not too long ago that changing
file permissions to executable was required. But now days this
does not seem to be the case . . . I've always in the last several
years use ./executable until I put the executable into my local
path . . .

On Fri, Mar 25, 2016 at 2:19 PM, Mike > wrote:

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 actually know what
they're talking about, and have been on this list a lot
longer than you.

Maybe we need to learn what ./ does... It has absolutely
nothing to do with a files permissions or whether it's
executable or not. It's use is regarding the lack of the
current directory "." in one's PATH variable.  Umask is
(largely) what controls what permissions a file is created with.

mike@pride-n-joy:~/test.d$
 ls -al
total 12
drwxr-xr-x  2 mike mike 4096 Mar 25 17:07 .
drwxr-xr-x 37 mike mike 4096 Mar 25 16:46 ..
-rw-r--r--  1 mike mike   78 Mar 25 16:47 hello.c
mike@pride-n-joy:~/test.d$
 umask
0022
mike@pride-n-joy:~/test.d$
 gcc -Wall -o hello hello.c
mike@pride-n-joy:~/test.d$
 ls -l
total 12
-rwxr-xr-x 1 mike mike 6696 Mar 25 17:08 hello
-rw-r--r-- 1 mike mike   78 Mar 25 16:47 hello.c
mike@pride-n-joy:~/test.d$
 hello
bash: hello: command not found
mike@pride-n-joy:~/test.d$
 ./hello
Hello, world!
mike@pride-n-joy:~/test.d$
 umask 0137
mike@pride-n-joy:~/test.d$
 gcc -Wall -o hello hello.c
mike@pride-n-joy:~/test.d$
 ls -l
total 12
-rw-r- 1 mike mike 6696 Mar 25 17:09 hello
-rw-r--r-- 1 mike mike   78 Mar 25 16:47 hello.c
mike@pride-n-joy:~/test.d$
 hello
bash: hello: command not found
mike@pride-n-joy:~/test.d$
 ./hello
bash: ./hello: Permission denied
mike@pride-n-joy:~/test.d$
 ls -l
total 12
-rw-r- 1 mike mike 6696 Mar 25 17:09 hello
-rw-r--r-- 1 mike mike   78 Mar 25 16:47 hello.c
mike@pride-n-joy:~/test.d$
 chmod 0750 hello
mike@pride-n-joy:~/test.d$
 ls -l
total 12
-rwxr-x--- 1 mike mike 6696 Mar 25 17:09 hello
-rw-r--r-- 1 mike mike   78 Mar 25 16:47 hello.c
mike@pride-n-joy:~/test.d$
 ./hello
Hello, world!
mike@pride-n-joy:~/test.d$
 umask 022
mike@pride-n-joy:~/test.d$
 umask
0022
mike@pride-n-joy:~/test.d$ 

Mike


On Fri, Mar 25, 2016 at 8:53 AM, 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
$ echo 'int main (void) {  printf ("Hello, world!\n"); 
 return 0; }' 

Re: [beagleboard] Re: C compiler

[William Hermans]

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
> 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 that "issue", because it wont.
>
> I do recall at some point perhaps not too long ago that changing file
> permissions to executable was required. But now days this does not seem to
> be the case . . . I've always in the last several years use ./executable
> until I put the executable into my local path . . .
>
> On Fri, Mar 25, 2016 at 2:19 PM, Mike  wrote:
>
>> 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 actually know what they're talking
>> about, and have been on this list a lot longer than you.
>>
>> Maybe we need to learn what ./ does...  It has absolutely nothing to do
>> with a files permissions or whether it's executable or not.  It's use is
>> regarding the lack of the current directory "." in one's PATH variable.
>> Umask is (largely) what controls what permissions a file is created with.
>>
>> mike@pride-n-joy:~/test.d$ ls -al
>> total 12
>> drwxr-xr-x  2 mike mike 4096 Mar 25 17:07 .
>> drwxr-xr-x 37 mike mike 4096 Mar 25 16:46 ..
>> -rw-r--r--  1 mike mike   78 Mar 25 16:47 hello.c
>> mike@pride-n-joy:~/test.d$ umask
>> 0022
>> mike@pride-n-joy:~/test.d$ gcc -Wall -o hello hello.c
>> mike@pride-n-joy:~/test.d$ ls -l
>> total 12
>> -rwxr-xr-x 1 mike mike 6696 Mar 25 17:08 hello
>> -rw-r--r-- 1 mike mike   78 Mar 25 16:47 hello.c
>> mike@pride-n-joy:~/test.d$ hello
>> bash: hello: command not found
>> mike@pride-n-joy:~/test.d$ ./hello
>> Hello, world!
>> mike@pride-n-joy:~/test.d$ umask 0137
>> mike@pride-n-joy:~/test.d$ gcc -Wall -o hello hello.c
>> mike@pride-n-joy:~/test.d$ ls -l
>> total 12
>> -rw-r- 1 mike mike 6696 Mar 25 17:09 hello
>> -rw-r--r-- 1 mike mike   78 Mar 25 16:47 hello.c
>> mike@pride-n-joy:~/test.d$ hello
>> bash: hello: command not found
>> mike@pride-n-joy:~/test.d$ ./hello
>> bash: ./hello: Permission denied
>> mike@pride-n-joy:~/test.d$ ls -l
>> total 12
>> -rw-r- 1 mike mike 6696 Mar 25 17:09 hello
>> -rw-r--r-- 1 mike mike   78 Mar 25 16:47 hello.c
>> mike@pride-n-joy:~/test.d$ chmod 0750 hello
>> mike@pride-n-joy:~/test.d$ ls -l
>> total 12
>> -rwxr-x--- 1 mike mike 6696 Mar 25 17:09 hello
>> -rw-r--r-- 1 mike mike   78 Mar 25 16:47 hello.c
>> mike@pride-n-joy:~/test.d$ ./hello
>> Hello, world!
>> mike@pride-n-joy:~/test.d$ umask 022
>> mike@pride-n-joy:~/test.d$ umask
>> 0022
>> mike@pride-n-joy:~/test.d$
>>
>> Mike
>>
>>
>> On Fri, Mar 25, 2016 at 8:53 AM, 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
>>> $ echo 'int main (void) {  printf ("Hello, world!\n");   return 0; }' >>
>>> hello.c
>>> $ cat hello.c
>>> #include 
>>> int main (void) {  printf ("Hello, world!\n");   return 0; }
>>> $ gcc -Wall -o hello hello.c
>>> $ ./hello
>>> Hello, world!
>>> $ ls -l
>>> total 12
>>> -rwxrwxr-x 1 dw dw 7332 Mar 25 16:32 hello
>>> -rw-rw-r-- 1 dw dw   80 Mar 25 16:31 hello.c
>>> $
>>>
>>> No chmod needed, no myprogram.o there, why the sudo
>>>
>>
>> --
>> 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 an
>> email to beagleboard+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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 an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: C compiler

[William Hermans]

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 that "issue", because it wont.

I do recall at some point perhaps not too long ago that changing file
permissions to executable was required. But now days this does not seem to
be the case . . . I've always in the last several years use ./executable
until I put the executable into my local path . . .

On Fri, Mar 25, 2016 at 2:19 PM, Mike  wrote:

> 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 actually know what they're talking
> about, and have been on this list a lot longer than you.
>
> Maybe we need to learn what ./ does...  It has absolutely nothing to do
> with a files permissions or whether it's executable or not.  It's use is
> regarding the lack of the current directory "." in one's PATH variable.
> Umask is (largely) what controls what permissions a file is created with.
>
> mike@pride-n-joy:~/test.d$ ls -al
> total 12
> drwxr-xr-x  2 mike mike 4096 Mar 25 17:07 .
> drwxr-xr-x 37 mike mike 4096 Mar 25 16:46 ..
> -rw-r--r--  1 mike mike   78 Mar 25 16:47 hello.c
> mike@pride-n-joy:~/test.d$ umask
> 0022
> mike@pride-n-joy:~/test.d$ gcc -Wall -o hello hello.c
> mike@pride-n-joy:~/test.d$ ls -l
> total 12
> -rwxr-xr-x 1 mike mike 6696 Mar 25 17:08 hello
> -rw-r--r-- 1 mike mike   78 Mar 25 16:47 hello.c
> mike@pride-n-joy:~/test.d$ hello
> bash: hello: command not found
> mike@pride-n-joy:~/test.d$ ./hello
> Hello, world!
> mike@pride-n-joy:~/test.d$ umask 0137
> mike@pride-n-joy:~/test.d$ gcc -Wall -o hello hello.c
> mike@pride-n-joy:~/test.d$ ls -l
> total 12
> -rw-r- 1 mike mike 6696 Mar 25 17:09 hello
> -rw-r--r-- 1 mike mike   78 Mar 25 16:47 hello.c
> mike@pride-n-joy:~/test.d$ hello
> bash: hello: command not found
> mike@pride-n-joy:~/test.d$ ./hello
> bash: ./hello: Permission denied
> mike@pride-n-joy:~/test.d$ ls -l
> total 12
> -rw-r- 1 mike mike 6696 Mar 25 17:09 hello
> -rw-r--r-- 1 mike mike   78 Mar 25 16:47 hello.c
> mike@pride-n-joy:~/test.d$ chmod 0750 hello
> mike@pride-n-joy:~/test.d$ ls -l
> total 12
> -rwxr-x--- 1 mike mike 6696 Mar 25 17:09 hello
> -rw-r--r-- 1 mike mike   78 Mar 25 16:47 hello.c
> mike@pride-n-joy:~/test.d$ ./hello
> Hello, world!
> mike@pride-n-joy:~/test.d$ umask 022
> mike@pride-n-joy:~/test.d$ umask
> 0022
> mike@pride-n-joy:~/test.d$
>
> Mike
>
>
> On Fri, Mar 25, 2016 at 8:53 AM, 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
>> $ echo 'int main (void) {  printf ("Hello, world!\n");   return 0; }' >>
>> hello.c
>> $ cat hello.c
>> #include 
>> int main (void) {  printf ("Hello, world!\n");   return 0; }
>> $ gcc -Wall -o hello hello.c
>> $ ./hello
>> Hello, world!
>> $ ls -l
>> total 12
>> -rwxrwxr-x 1 dw dw 7332 Mar 25 16:32 hello
>> -rw-rw-r-- 1 dw dw   80 Mar 25 16:31 hello.c
>> $
>>
>> No chmod needed, no myprogram.o there, why the sudo
>>
>
> --
> 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 an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Moez Essid]

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 an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Robert Nelson]

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/;
>
> /{
>
>   compatible = "ti,beaglebone", "ti,beaglebone-black";
>   part-number = "BBB-DS3231";
>   version = "00A0";
>
>   fragment@0 {
> target = <>;
>
> __overlay__ {
>   pinctrl-0 = <_pins>;
>
>   clock-frequency = <10>;
>   status = "okay";
>
>   rtc: rtc@68 {
> compatible = "dallas,ds1307";
> #address-cells = <1>;
> #size-cells = <0>;
> reg = <0x68>;
>   };
> };
>   };
> };
>
> I have compiled it and put the .dtbo in /lib/firmware:
>
> # ls -l /lib/firmware/DS3231-00A0.dtbo
> -rw-r--r-- 1 root root 699 Feb 22 21:35 /lib/firmware/DS3231-00A0.dtbo
> #
>
> Interactively it works:
>
> # echo DS3231 > /sys/devices/platform/bone_capemgr/slots
>
> produces:
>
> [ 4082.171481] bone_capemgr bone_capemgr: part_number 'DS3231', version
'N/A'
> [ 4082.178999] bone_capemgr bone_capemgr: slot #4: override
> [ 4082.184502] bone_capemgr bone_capemgr: Using override eeprom data at
slot 4
> [ 4082.191512] bone_capemgr bone_capemgr: slot #4: 'Override Board
Name,00A0,Override Manuf,DS3231'
> [ 4082.216295] rtc-ds1307 2-0068: rtc core: registered ds1307 as rtc1
> [ 4082.222530] rtc-ds1307 2-0068: 56 bytes nvram
> [ 4082.237260] bone_capemgr bone_capemgr: slot #4: dtbo
'DS3231-00A0.dtbo' loaded; overlay id #0
>
> and
>
> # cat /sys/devices/platform/bone_capemgr/slots
>  0: PF  -1
>  1: PF  -1
>  2: PF  -1
>  3: PF  -1
>  4: P-O-L-   0 Override Board Name,00A0,Override Manuf,DS3231
> #
>
> So I ask to have it enabled at boot:
>
> # cat /boot/uEnv.txt
> optargs=coherent_pool=1M bone_capemgr.enable_partno=BBB-DS3231
> #
>
> and I get this in dmesg:
>
> # dmesg | grep bone
> [0.00] Kernel command line: console=ttyO0,115200n8
coherent_pool=1M bone_capemgr.enable_partno=BBB-DS3231
root=PARTUUID=0e4f7ccd-01 rw rootwait fixrtc
> [4.950284] bone_capemgr bone_capemgr: Baseboard:
'A335BNLT,00C0,3214BBBK9247'
> [4.957585] bone_capemgr bone_capemgr:
compatible-baseboard=ti,beaglebone-black - #slots=4
> [5.023585] bone_capemgr bone_capemgr: slot #0: No cape found
> [5.083600] bone_capemgr bone_capemgr: slot #1: No cape found
> [5.143596] bone_capemgr bone_capemgr: slot #2: No cape found
> [5.203580] bone_capemgr bone_capemgr: slot #3: No cape found
> [5.209370] bone_capemgr bone_capemgr: enabled_partno PARTNO
'BBB-DS3231' VER 'N/A' PR '0'
> [5.217685] bone_capemgr bone_capemgr: slot #4: override
> [5.223023] bone_capemgr bone_capemgr: Using override eeprom data at
slot 4
> [5.230034] bone_capemgr bone_capemgr: slot #4: 'Override Board
Name,00A0,Override Manuf,BBB-DS3231'
> [5.239545] bone_capemgr bone_capemgr: initialized OK.
> [6.259420] bone_capemgr bone_capemgr: loader: failed to load slot-4
BBB-DS3231:00A0 (prio 0)
> #
>
> Is this a case of /lib/firmware not being available yet?  I see people
with Debian fiddling with initramfs in similar situations...?

Correct, if you use an initramfs, you must copy the dtbo objects into it.

https://github.com/beagleboard/bb.org-overlays/blob/master/tools/dtbo

Regards,

-- 
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 an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[David Good]

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 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/;
>
> /{
>
>   compatible = "ti,beaglebone", "ti,beaglebone-black";
>   part-number = "BBB-DS3231";
>   version = "00A0";
>
>   fragment@0 {
> target = <>;
>
> __overlay__ {
>   pinctrl-0 = <_pins>;
>
>   clock-frequency = <10>;
>   status = "okay";
>
>   rtc: rtc@68 {
> compatible = "dallas,ds1307";
> #address-cells = <1>;
> #size-cells = <0>;
> reg = <0x68>;
>   };
> };
>   };
> };
>
> I have compiled it and put the .dtbo in /lib/firmware:
>
> # ls -l /lib/firmware/DS3231-00A0.dtbo
> -rw-r--r-- 1 root root 699 Feb 22 21:35 /lib/firmware/DS3231-00A0.dtbo
> #
>
> Interactively it works:
>
> # echo DS3231 > /sys/devices/platform/bone_capemgr/slots
>
> produces:
>
> [ 4082.171481] bone_capemgr bone_capemgr: part_number 'DS3231', version
> 'N/A'
> [ 4082.178999] bone_capemgr bone_capemgr: slot #4: override
> [ 4082.184502] bone_capemgr bone_capemgr: Using override eeprom data at
> slot 4
> [ 4082.191512] bone_capemgr bone_capemgr: slot #4: 'Override Board
> Name,00A0,Override Manuf,DS3231'
> [ 4082.216295] rtc-ds1307 2-0068: rtc core: registered ds1307 as rtc1
> [ 4082.222530] rtc-ds1307 2-0068: 56 bytes nvram
> [ 4082.237260] bone_capemgr bone_capemgr: slot #4: dtbo 'DS3231-00A0.dtbo'
> loaded; overlay id #0
>
> and
>
> # cat /sys/devices/platform/bone_capemgr/slots
>  0: PF  -1
>  1: PF  -1
>  2: PF  -1
>  3: PF  -1
>  4: P-O-L-   0 Override Board Name,00A0,Override Manuf,DS3231
> #
>
> So I ask to have it enabled at boot:
>
> # cat /boot/uEnv.txt
> optargs=coherent_pool=1M bone_capemgr.enable_partno=BBB-DS3231
> #
>
> and I get this in dmesg:
>
> # dmesg | grep bone
> [0.00] Kernel command line: console=ttyO0,115200n8
> coherent_pool=1M bone_capemgr.enable_partno=BBB-DS3231
> root=PARTUUID=0e4f7ccd-01 rw rootwait fixrtc
> [4.950284] bone_capemgr bone_capemgr: Baseboard:
> 'A335BNLT,00C0,3214BBBK9247'
> [4.957585] bone_capemgr bone_capemgr:
> compatible-baseboard=ti,beaglebone-black - #slots=4
> [5.023585] bone_capemgr bone_capemgr: slot #0: No cape found
> [5.083600] bone_capemgr bone_capemgr: slot #1: No cape found
> [5.143596] bone_capemgr bone_capemgr: slot #2: No cape found
> [5.203580] bone_capemgr bone_capemgr: slot #3: No cape found
> [5.209370] bone_capemgr bone_capemgr: enabled_partno PARTNO
> 'BBB-DS3231' VER 'N/A' PR '0'
> [5.217685] bone_capemgr bone_capemgr: slot #4: override
> [5.223023] bone_capemgr bone_capemgr: Using override eeprom data at
> slot 4
> [5.230034] bone_capemgr bone_capemgr: slot #4: 'Override Board
> Name,00A0,Override Manuf,BBB-DS3231'
> [5.239545] bone_capemgr bone_capemgr: initialized OK.
> [6.259420] bone_capemgr bone_capemgr: loader: failed to load slot-4
> BBB-DS3231:00A0 (prio 0)
> #
>
> Is this a case of /lib/firmware not being available yet?  I see people
> with Debian fiddling with initramfs in similar situations...?
>
>
> --
> 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 an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Axe]

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";
  version = "00A0";

  fragment@0 {
target = <>;

__overlay__ {
  pinctrl-0 = <_pins>;

  clock-frequency = <10>;
  status = "okay";

  rtc: rtc@68 {
compatible = "dallas,ds1307";
#address-cells = <1>;
#size-cells = <0>;
reg = <0x68>;
  };
};
  };
};

I have compiled it and put the .dtbo in /lib/firmware:

# ls -l /lib/firmware/DS3231-00A0.dtbo 
-rw-r--r-- 1 root root 699 Feb 22 21:35 /lib/firmware/DS3231-00A0.dtbo
# 

Interactively it works:

# echo DS3231 > /sys/devices/platform/bone_capemgr/slots

produces:

[ 4082.171481] bone_capemgr bone_capemgr: part_number 'DS3231', version 
'N/A'
[ 4082.178999] bone_capemgr bone_capemgr: slot #4: override
[ 4082.184502] bone_capemgr bone_capemgr: Using override eeprom data at 
slot 4
[ 4082.191512] bone_capemgr bone_capemgr: slot #4: 'Override Board 
Name,00A0,Override Manuf,DS3231'
[ 4082.216295] rtc-ds1307 2-0068: rtc core: registered ds1307 as rtc1
[ 4082.222530] rtc-ds1307 2-0068: 56 bytes nvram
[ 4082.237260] bone_capemgr bone_capemgr: slot #4: dtbo 'DS3231-00A0.dtbo' 
loaded; overlay id #0

and

# cat /sys/devices/platform/bone_capemgr/slots
 0: PF  -1 
 1: PF  -1 
 2: PF  -1 
 3: PF  -1 
 4: P-O-L-   0 Override Board Name,00A0,Override Manuf,DS3231
# 

So I ask to have it enabled at boot:

# cat /boot/uEnv.txt 
optargs=coherent_pool=1M bone_capemgr.enable_partno=BBB-DS3231
# 

and I get this in dmesg:

# dmesg | grep bone
[0.00] Kernel command line: console=ttyO0,115200n8 coherent_pool=1M 
bone_capemgr.enable_partno=BBB-DS3231 root=PARTUUID=0e4f7ccd-01 rw rootwait 
fixrtc
[4.950284] bone_capemgr bone_capemgr: Baseboard: 
'A335BNLT,00C0,3214BBBK9247'
[4.957585] bone_capemgr bone_capemgr: 
compatible-baseboard=ti,beaglebone-black - #slots=4
[5.023585] bone_capemgr bone_capemgr: slot #0: No cape found
[5.083600] bone_capemgr bone_capemgr: slot #1: No cape found
[5.143596] bone_capemgr bone_capemgr: slot #2: No cape found
[5.203580] bone_capemgr bone_capemgr: slot #3: No cape found
[5.209370] bone_capemgr bone_capemgr: enabled_partno PARTNO 
'BBB-DS3231' VER 'N/A' PR '0'
[5.217685] bone_capemgr bone_capemgr: slot #4: override
[5.223023] bone_capemgr bone_capemgr: Using override eeprom data at 
slot 4
[5.230034] bone_capemgr bone_capemgr: slot #4: 'Override Board 
Name,00A0,Override Manuf,BBB-DS3231'
[5.239545] bone_capemgr bone_capemgr: initialized OK.
[6.259420] bone_capemgr bone_capemgr: loader: failed to load slot-4 
BBB-DS3231:00A0 (prio 0)
#

Is this a case of /lib/firmware not being available yet?  I see people with 
Debian fiddling with initramfs in similar situations...?


-- 
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 an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: C compiler

[Mike]

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 actually know what they're 
talking about, and have been on this list a lot longer than you.
Maybe we need to learn what ./ does...  It has absolutely nothing to do 
with a files permissions or whether it's executable or not.  It's use is 
regarding the lack of the current directory "." in one's PATH variable.  
Umask is (largely) what controls what permissions a file is created with.


mike@pride-n-joy:~/test.d$ ls -al
total 12
drwxr-xr-x  2 mike mike 4096 Mar 25 17:07 .
drwxr-xr-x 37 mike mike 4096 Mar 25 16:46 ..
-rw-r--r--  1 mike mike   78 Mar 25 16:47 hello.c
mike@pride-n-joy:~/test.d$ umask
0022
mike@pride-n-joy:~/test.d$ gcc -Wall -o hello hello.c
mike@pride-n-joy:~/test.d$ ls -l
total 12
-rwxr-xr-x 1 mike mike 6696 Mar 25 17:08 hello
-rw-r--r-- 1 mike mike   78 Mar 25 16:47 hello.c
mike@pride-n-joy:~/test.d$ hello
bash: hello: command not found
mike@pride-n-joy:~/test.d$ ./hello
Hello, world!
mike@pride-n-joy:~/test.d$ umask 0137
mike@pride-n-joy:~/test.d$ gcc -Wall -o hello hello.c
mike@pride-n-joy:~/test.d$ ls -l
total 12
-rw-r- 1 mike mike 6696 Mar 25 17:09 hello
-rw-r--r-- 1 mike mike   78 Mar 25 16:47 hello.c
mike@pride-n-joy:~/test.d$ hello
bash: hello: command not found
mike@pride-n-joy:~/test.d$ ./hello
bash: ./hello: Permission denied
mike@pride-n-joy:~/test.d$ ls -l
total 12
-rw-r- 1 mike mike 6696 Mar 25 17:09 hello
-rw-r--r-- 1 mike mike   78 Mar 25 16:47 hello.c
mike@pride-n-joy:~/test.d$ chmod 0750 hello
mike@pride-n-joy:~/test.d$ ls -l
total 12
-rwxr-x--- 1 mike mike 6696 Mar 25 17:09 hello
-rw-r--r-- 1 mike mike   78 Mar 25 16:47 hello.c
mike@pride-n-joy:~/test.d$ ./hello
Hello, world!
mike@pride-n-joy:~/test.d$ umask 022
mike@pride-n-joy:~/test.d$ umask
0022
mike@pride-n-joy:~/test.d$

Mike


On Fri, Mar 25, 2016 at 8:53 AM, 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
$ echo 'int main (void) {  printf ("Hello, world!\n");  return 0;
}' >> hello.c
$ cat hello.c
#include 
int main (void) {  printf ("Hello, world!\n");   return 0; }
$ gcc -Wall -o hello hello.c
$ ./hello
Hello, world!
$ ls -l
total 12
-rwxrwxr-x 1 dw dw 7332 Mar 25 16:32 hello
-rw-rw-r-- 1 dw dw   80 Mar 25 16:31 hello.c
$

No chmod needed, no myprogram.o there, why the sudo



--
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 an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] LCD 4D 7" problem

[Moez Essid]

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.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: PRU

[John Tobias]

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 required for the Make file in the examples to
> compile correctly.
> I've got most of the examples working and it is amazingly easy once you
> limit the problem to the essentials.
>
> Once you get past the provided examples and try to do something new, that
> is a new level of problems.
>
> Regards,
> Greg
>
>
>
Hi Greg,

Thanks for the info. I'll check it later too.

Regards,

John

> --
> 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 an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: C compiler

[William Hermans]

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 been on this list a lot longer than you.

On Fri, Mar 25, 2016 at 8:53 AM, 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
> $ echo 'int main (void) {  printf ("Hello, world!\n");   return 0; }' >>
> hello.c
> $ cat hello.c
> #include 
> int main (void) {  printf ("Hello, world!\n");   return 0; }
> $ gcc -Wall -o hello hello.c
> $ ./hello
> Hello, world!
> $ ls -l
> total 12
> -rwxrwxr-x 1 dw dw 7332 Mar 25 16:32 hello
> -rw-rw-r-- 1 dw dw   80 Mar 25 16:31 hello.c
> $
>
> No chmod needed, no myprogram.o there, why the sudo
>
> --
> 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 an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[William Hermans]

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 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 wrong with you device tree file, but I'm
> not that good with pinmuxing in dts file so . . . I can not say one way or
> another. You seem to be using the correct kernel though for using the uio
> PRU driver. *bone*
>
> On Fri, Mar 25, 2016 at 9:46 AM, Sylwester 
> wrote:
>
>>
>> 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 beaglebone 4.1.20-bone-rt-r20 #1 Sat Mar 19 06:28:47 UTC 2016
>> armv7l GNU/Linux
>>
>>
>> 1. Beagle Bone Black with latest Image (Debian 8.3) running from SD-Card
>> 2. eMMC and HDMI Disabled via* dtb=am335x-boneblack-overlay.dtb* in
>> /boot/uEnv.txt on SD
>> 3. The bb.org-overlays set up and Installed.
>> 4. Set up DTS file to initialize PRUSS and Pin P9_27 in Mode 5, as Output
>> for PRU
>> DTS File here:
>> https://github.com/DatanoiseTV/BBB-PRU/blob/master/overlay/DatanoiseTV-001.dts
>> 0x1a4 0xd was previously 0x1a4 0x5, but this didn't work as well.
>>
>> What are the current problems?
>> ==
>> 1. The directory tree in /sys/class/uio is empty, software loading
>> firmware into PRU
>> exits with SEGFAULT:
>>
>> open("/dev/uio0", O_RDWR|O_SYNC)= -1 ENOENT (No such file or
>> directory)
>>
>> open("/sys/class/uio/uio0/maps/map0/addr", O_RDONLY) = -1 ENOENT (No such
>> file or directory)
>>
>> --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0xd00} ---
>>
>> +++ killed by SIGSEGV +++
>>
>> Segmentation fault
>>
>>
>> 2. GPIO direction and state apparently not initialized correcty.
>>
>>
>>
>> --
>> 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 an
>> email to beagleboard+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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 an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[William Hermans]

>
> *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 wrong with you device tree file, but I'm
not that good with pinmuxing in dts file so . . . I can not say one way or
another. You seem to be using the correct kernel though for using the uio
PRU driver. *bone*

On Fri, Mar 25, 2016 at 9:46 AM, Sylwester 
wrote:

>
> 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 beaglebone 4.1.20-bone-rt-r20 #1 Sat Mar 19 06:28:47 UTC 2016 armv7l
> GNU/Linux
>
>
> 1. Beagle Bone Black with latest Image (Debian 8.3) running from SD-Card
> 2. eMMC and HDMI Disabled via* dtb=am335x-boneblack-overlay.dtb* in
> /boot/uEnv.txt on SD
> 3. The bb.org-overlays set up and Installed.
> 4. Set up DTS file to initialize PRUSS and Pin P9_27 in Mode 5, as Output
> for PRU
> DTS File here:
> https://github.com/DatanoiseTV/BBB-PRU/blob/master/overlay/DatanoiseTV-001.dts
> 0x1a4 0xd was previously 0x1a4 0x5, but this didn't work as well.
>
> What are the current problems?
> ==
> 1. The directory tree in /sys/class/uio is empty, software loading
> firmware into PRU
> exits with SEGFAULT:
>
> open("/dev/uio0", O_RDWR|O_SYNC)= -1 ENOENT (No such file or
> directory)
>
> open("/sys/class/uio/uio0/maps/map0/addr", O_RDONLY) = -1 ENOENT (No such
> file or directory)
>
> --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0xd00} ---
>
> +++ killed by SIGSEGV +++
>
> Segmentation fault
>
>
> 2. GPIO direction and state apparently not initialized correcty.
>
>
>
> --
> 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 an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] HDMI RGB communitation

[Tomáš Polišenský]

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 blanking initialized and 
properly set that display but without good results.
Display is showing some mess which is reacting to changes in framebuffer:







My question is, if it is even compatible or does hdmi IO using totally some 
different protocol then standard parallel rgb? 

Is there some other way how to easily force linux to output data on that 
bus? I'm initializing lcd from user-space by spi, all i need is just some 
regular 16bit data on rgb bus. 

-- 
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 an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: PRU

[Greg]

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 examples working and it is amazingly easy once you 
limit the problem to the essentials.

Once you get past the provided examples and try to do something new, that 
is a new level of problems.

Regards,
Greg


-- 
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 an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] PRU

[John Tobias]

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 (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 4.1.15-ti-rt-r43. Below are the version of my tools that I
> am using.
>
> What error messages are you getting?
>
>
> PRU_CGT=/home/jtobias/ti/ccsv6/tools/compiler/ti-cgt-pru_2.1.2
> ARM_CGT=/home/jtobias/ti/ccsv6/tools/compiler/ti-cgt-arm_5.2.5
> SW_DIR=/home/jtobias/ti/AM335X_StarterWare_02_00_01_01
>
>
> Regards,
>
> John
>
> On Wed, Mar 23, 2016 at 8:37 PM, John Syne  wrote:
>
>> http://processors.wiki.ti.com/index.php/Mklib#Invoking_mklib_manually
>>
>> Regards,
>> John
>>
>>
>>
>>
>> On Mar 23, 2016, at 5:55 PM, John Tobias 
>> wrote:
>>
>> Hi John,
>>
>> I have the PRU Add on which is pru-icss-4.0.1. Then, I tried the latest
>> example from the git you provided.
>> I have some compilation error (please see the attached log.txt)
>>
>> Regards,
>>
>> John
>>
>>
>> On Wed, Mar 23, 2016 at 4:37 PM, John Syne  wrote:
>>
>>> Or you can use the latest examples from here:
>>>
>>>
>>> https://git.ti.com/pru-software-support-package/pru-software-support-package
>>>
>>> Regards,
>>> John
>>>
>>>
>>>
>>>
>>> On Mar 23, 2016, at 1:54 PM, John Tobias 
>>> wrote:
>>>
>>> Hello Guys,
>>>
>>> I am using debian image version 8.3 that I downloaded @
>>> http://beagleboard.org/latest-images (4.1.15-ti-rt-r43). Also, I
>>> downloaded the TI SDK for AM335x (
>>> http://software-dl.ti.com/processor-sw/esd/PROCESSOR-SDK-LINUX-AM335X/latest/index_FDS.html
>>> ).
>>>
>>> I compiled the sample program for PRU (toggle_led.out) and copy it over
>>> in /lib/firmware/am335x-pru0-fw, but it did not work.
>>>
>>> Then, I found Robert Nelson's binary and it works fine.
>>>
>>>
>>> https://github.com/RobertCNelson/boot-scripts/commit/20a16f79be80886a1e030d197573b5950f98626d#diff-a0ab1dbc32ef29215c473f3b8979ad32
>>>
>>>
>>> Any idea?.
>>>
>>> Regards,
>>>
>>> John
>>>
>>> --
>>> 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
>>> an email to beagleboard+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>>
>>>
>>> --
>>> 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
>>> an email to beagleboard+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>> --
>> 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 an
>> email to beagleboard+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>> 
>>
>>
>>
>> --
>> 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 an
>> email to beagleboard+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> --
> 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 an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> 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 an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] PRU

[John Syne]

> 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.
> 
> None of them and are loading successfully. I am using debian version 8.3 
> running kernel 4.1.15-ti-rt-r43. Below are the version of my tools that I am 
> using.
What error messages are you getting?
> 
> PRU_CGT=/home/jtobias/ti/ccsv6/tools/compiler/ti-cgt-pru_2.1.2
> ARM_CGT=/home/jtobias/ti/ccsv6/tools/compiler/ti-cgt-arm_5.2.5
> SW_DIR=/home/jtobias/ti/AM335X_StarterWare_02_00_01_01
> 
> 
> Regards,
> 
> John
> 
> On Wed, Mar 23, 2016 at 8:37 PM, John Syne  > wrote:
> http://processors.wiki.ti.com/index.php/Mklib#Invoking_mklib_manually 
> 
> 
> Regards,
> John
> 
> 
> 
> 
>> On Mar 23, 2016, at 5:55 PM, John Tobias > > wrote:
>> 
>> Hi John,
>> 
>> I have the PRU Add on which is pru-icss-4.0.1. Then, I tried the latest 
>> example from the git you provided.
>> I have some compilation error (please see the attached log.txt)
>> 
>> Regards,
>> 
>> John
>> 
>> 
>> On Wed, Mar 23, 2016 at 4:37 PM, John Syne > > wrote:
>> Or you can use the latest examples from here:
>> 
>> https://git.ti.com/pru-software-support-package/pru-software-support-package 
>> 
>> 
>> Regards,
>> John
>> 
>> 
>> 
>> 
>>> On Mar 23, 2016, at 1:54 PM, John Tobias >> > wrote:
>>> 
>>> Hello Guys,
>>> 
>>> I am using debian image version 8.3 that I downloaded @ 
>>> http://beagleboard.org/latest-images  
>>> (4.1.15-ti-rt-r43). Also, I downloaded the TI SDK for AM335x 
>>> (http://software-dl.ti.com/processor-sw/esd/PROCESSOR-SDK-LINUX-AM335X/latest/index_FDS.html
>>>  
>>> ).
>>> 
>>> I compiled the sample program for PRU (toggle_led.out) and copy it over in 
>>> /lib/firmware/am335x-pru0-fw, but it did not work.
>>> 
>>> Then, I found Robert Nelson's binary and it works fine.
>>> 
>>> https://github.com/RobertCNelson/boot-scripts/commit/20a16f79be80886a1e030d197573b5950f98626d#diff-a0ab1dbc32ef29215c473f3b8979ad32
>>>  
>>> 
>>> 
>>> 
>>> Any idea?.
>>> 
>>> Regards,
>>> 
>>> John
>>> 
>>> -- 
>>> 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 an 
>>> email to beagleboard+unsubscr...@googlegroups.com 
>>> .
>>> For more options, visit https://groups.google.com/d/optout 
>>> .
>> 
>> 
>> -- 
>> 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 an 
>> email to beagleboard+unsubscr...@googlegroups.com 
>> .
>> For more options, visit https://groups.google.com/d/optout 
>> .
>> 
>> 
>> -- 
>> 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 an 
>> email to beagleboard+unsubscr...@googlegroups.com 
>> .
>> For more options, visit https://groups.google.com/d/optout 
>> .
>> 
> 
> 
> -- 
> 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 an 
> email to beagleboard+unsubscr...@googlegroups.com 
> .
> For more options, visit https://groups.google.com/d/optout 
> .
> 
> 
> -- 
> For more options, visit http://beagleboard.org/discuss 
> 
> --- 
> You received this message 

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

[Le Costaouec Vincent]

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 pinctrl-single 
pin 101 (44e10994.0) 0027 pinctrl-single 
pin 102 (44e10998.0) 0027 pinctrl-single 
pin 103 (44e1099c.0) 0027 pinctrl-single 
This mean that the pins are not correctly configure, in fact they should be 
configure at 0x33 0x33 0x13 and 0x13, isn't it ?
And since I started configuring caps and pinmux it is the only time It 
doesn't correspond with the dts.

# dmesg | grep bone
[0.00] Linux version 4.1.18-bone20 (lecostaouec@mppdev) (gcc 
version 4.9.3 20150413 (prerelease) (Linaro GCC 4.9-2015.05) ) #4 Fri Mar 
18 15:16:19 CET 2016
[0.00] Kernel command line: console=ttyO0,115200n8 
bone_capemgr.enable_partno=BB-SPIDEV1 root=/dev/mmcblk0p1 ro 
rootfstype=ext4 rootwait
[3.998684] usb usb1: Manufacturer: Linux 4.1.18-bone20 musb-hcd
[4.349285] bone_capemgr bone_capemgr: Baseboard: 
'A335BNLT,00C0,4414BBBK9699'
[4.356616] bone_capemgr bone_capemgr: 
compatible-baseboard=ti,beaglebone-black - #slots=4
[4.422658] bone_capemgr bone_capemgr: slot #0: No cape found
[4.482655] bone_capemgr bone_capemgr: slot #1: No cape found
[4.542654] bone_capemgr bone_capemgr: slot #2: No cape found
[4.602654] bone_capemgr bone_capemgr: slot #3: No cape found
[4.608439] bone_capemgr bone_capemgr: enabled_partno PARTNO 
'BB-SPIDEV1' VER 'N/A' PR '0'
[4.616751] bone_capemgr bone_capemgr: slot #4: override
[4.622088] bone_capemgr bone_capemgr: Using override eeprom data at 
slot 4
[4.629091] bone_capemgr bone_capemgr: slot #4: 'Override Board 
Name,00A0,Override Manuf,BB-SPIDEV1'
[4.638497] bone_capemgr bone_capemgr: initialized OK.
[4.645406] bone_capemgr bone_capemgr: slot #4: dtbo 
'BB-SPIDEV1-00A0.dtbo' loaded; overlay id #0

# cat /proc/cmdline 
console=ttyO0,115200n8 bone_capemgr.enable_partno=BB-SPIDEV1 
root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait


The other issue could be that we are not using exatly the same version of 
the kernel 
# uname -ar
Linux beagle01 4.1.18-bone20 #4 Fri Mar 18 15:16:19 CET 2016 armv7l 
GNU/Linux

Or I'm I wrong and 4.1.18-ti-r55 is the same as 4.1.18-bone20 ?
Thanks for your time


Le vendredi 25 mars 2016 16:49:55 UTC+1, RobertCNelson a écrit :
>
> 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 dmesg. 
>
> Yeah, double check your wires, it works as-is... 
>
> root@beaglebone:~# ./spidev_test -D /dev/spidev2.1 
> spi mode: 0 
> bits per word: 8 
> max speed: 50 Hz (500 KHz) 
>
> FF FF FF FF FF FF 
> 40 00 00 00 00 95 
> FF FF FF FF FF FF 
> FF FF FF FF FF FF 
> FF FF FF FF FF FF 
> DE AD BE EF BA AD 
> F0 0D 
> root@beaglebone:~# ./spidev_test -D /dev/spidev2.0 
> spi mode: 0 
> bits per word: 8 
> max speed: 50 Hz (500 KHz) 
>
> FF FF FF FF FF FF 
> 40 00 00 00 00 95 
> FF FF FF FF FF FF 
> FF FF FF FF FF FF 
> FF FF FF FF FF FF 
> DE AD BE EF BA AD 
> F0 0D 
>
> root@beaglebone:~# cat /proc/cmdline 
> console=tty0 console=ttyO0,115200n8 
> bone_capemgr.enable_partno=BB-SPIDEV1 root=/dev/mmcblk0p1 
> rootfstype=ext4 rootwait coherent_pool=1M quiet cape_universal=enable 
> root@beaglebone:~# uname -r 
> 4.1.18-ti-r55 
>
> root@beaglebone:~# dmesg | grep bone 
> [0.00] Kernel command line: console=tty0 
> console=ttyO0,115200n8 bone_capemgr.enable_partno=BB-SPIDEV1 
> root=/dev/mmcblk0p1 rootfstype=ext4 rootwait coherent_pool=1M quiet 
> cape_universal=enable 
> [3.426727] bone_capemgr bone_capemgr: Baseboard: 'A335BNLT, 
> ,BBG115096609' 
> [3.426755] bone_capemgr bone_capemgr: 
> compatible-baseboard=ti,beaglebone-black - #slots=4 
> [3.477193] bone_capemgr bone_capemgr: slot #0: No cape found 
> [3.537209] bone_capemgr bone_capemgr: slot #1: No cape found 
> [3.597174] bone_capemgr bone_capemgr: slot #2: No cape found 
> [3.657179] bone_capemgr bone_capemgr: slot #3: No cape found 
> [3.662979] bone_capemgr bone_capemgr: enabled_partno PARTNO 
> 'BB-SPIDEV1' VER 'N/A' PR '0' 
> [3.662991] bone_capemgr bone_capemgr: slot #4: override 
> [3.663006] bone_capemgr bone_capemgr: Using override eeprom data at 
> slot 4 
> [3.663021] bone_capemgr bone_capemgr: slot #4: 'Override Board 
> Name,00A0,Override Manuf,BB-SPIDEV1' 
> [3.663322] bone_capemgr bone_capemgr: initialized OK. 
> [3.671575] bone_capemgr bone_capemgr: slot #4: dtbo 
> 'BB-SPIDEV1-00A0.dtbo' loaded; overlay id #0 
> [   11.231817] LUN: removable file: 
> /var/cache/doc-beaglebone-getting-started/beaglebone-getting-started-2015-12-04.img

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

[Sylwester]

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 beaglebone 4.1.20-bone-rt-r20 #1 Sat Mar 19 06:28:47 UTC 2016 armv7l 
GNU/Linux


1. Beagle Bone Black with latest Image (Debian 8.3) running from SD-Card
2. eMMC and HDMI Disabled via* dtb=am335x-boneblack-overlay.dtb* in 
/boot/uEnv.txt on SD
3. The bb.org-overlays set up and Installed.
4. Set up DTS file to initialize PRUSS and Pin P9_27 in Mode 5, as Output 
for PRU
DTS File 
here: 
https://github.com/DatanoiseTV/BBB-PRU/blob/master/overlay/DatanoiseTV-001.dts
0x1a4 0xd was previously 0x1a4 0x5, but this didn't work as well.

What are the current problems?
==
1. The directory tree in /sys/class/uio is empty, software loading firmware 
into PRU
exits with SEGFAULT:

open("/dev/uio0", O_RDWR|O_SYNC)= -1 ENOENT (No such file or 
directory)

open("/sys/class/uio/uio0/maps/map0/addr", O_RDONLY) = -1 ENOENT (No such 
file or directory)

--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0xd00} ---

+++ killed by SIGSEGV +++

Segmentation fault


2. GPIO direction and state apparently not initialized correcty.



-- 
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 an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: C compiler

[Dieter Wirz]

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; }' >> hello.c
$ cat hello.c
#include 
int main (void) {  printf ("Hello, world!\n");   return 0; }
$ gcc -Wall -o hello hello.c
$ ./hello
Hello, world!
$ ls -l
total 12
-rwxrwxr-x 1 dw dw 7332 Mar 25 16:32 hello
-rw-rw-r-- 1 dw dw   80 Mar 25 16:31 hello.c
$

No chmod needed, no myprogram.o there, why the sudo

-- 
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 an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Robert Nelson]

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 dmesg.

Yeah, double check your wires, it works as-is...

root@beaglebone:~# ./spidev_test -D /dev/spidev2.1
spi mode: 0
bits per word: 8
max speed: 50 Hz (500 KHz)

FF FF FF FF FF FF
40 00 00 00 00 95
FF FF FF FF FF FF
FF FF FF FF FF FF
FF FF FF FF FF FF
DE AD BE EF BA AD
F0 0D
root@beaglebone:~# ./spidev_test -D /dev/spidev2.0
spi mode: 0
bits per word: 8
max speed: 50 Hz (500 KHz)

FF FF FF FF FF FF
40 00 00 00 00 95
FF FF FF FF FF FF
FF FF FF FF FF FF
FF FF FF FF FF FF
DE AD BE EF BA AD
F0 0D

root@beaglebone:~# cat /proc/cmdline
console=tty0 console=ttyO0,115200n8
bone_capemgr.enable_partno=BB-SPIDEV1 root=/dev/mmcblk0p1
rootfstype=ext4 rootwait coherent_pool=1M quiet cape_universal=enable
root@beaglebone:~# uname -r
4.1.18-ti-r55

root@beaglebone:~# dmesg | grep bone
[0.00] Kernel command line: console=tty0
console=ttyO0,115200n8 bone_capemgr.enable_partno=BB-SPIDEV1
root=/dev/mmcblk0p1 rootfstype=ext4 rootwait coherent_pool=1M quiet
cape_universal=enable
[3.426727] bone_capemgr bone_capemgr: Baseboard: 'A335BNLT, ,BBG115096609'
[3.426755] bone_capemgr bone_capemgr:
compatible-baseboard=ti,beaglebone-black - #slots=4
[3.477193] bone_capemgr bone_capemgr: slot #0: No cape found
[3.537209] bone_capemgr bone_capemgr: slot #1: No cape found
[3.597174] bone_capemgr bone_capemgr: slot #2: No cape found
[3.657179] bone_capemgr bone_capemgr: slot #3: No cape found
[3.662979] bone_capemgr bone_capemgr: enabled_partno PARTNO
'BB-SPIDEV1' VER 'N/A' PR '0'
[3.662991] bone_capemgr bone_capemgr: slot #4: override
[3.663006] bone_capemgr bone_capemgr: Using override eeprom data at slot 4
[3.663021] bone_capemgr bone_capemgr: slot #4: 'Override Board
Name,00A0,Override Manuf,BB-SPIDEV1'
[3.663322] bone_capemgr bone_capemgr: initialized OK.
[3.671575] bone_capemgr bone_capemgr: slot #4: dtbo
'BB-SPIDEV1-00A0.dtbo' loaded; overlay id #0
[   11.231817] LUN: removable file:
/var/cache/doc-beaglebone-getting-started/beaglebone-getting-started-2015-12-04.img

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

-- 
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 an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] PRU

[John Tobias]

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 4.1.15-ti-rt-r43. Below are the version of my tools that I
am using.

PRU_CGT=/home/jtobias/ti/ccsv6/tools/compiler/ti-cgt-pru_2.1.2
ARM_CGT=/home/jtobias/ti/ccsv6/tools/compiler/ti-cgt-arm_5.2.5
SW_DIR=/home/jtobias/ti/AM335X_StarterWare_02_00_01_01


Regards,

John

On Wed, Mar 23, 2016 at 8:37 PM, John Syne  wrote:

> http://processors.wiki.ti.com/index.php/Mklib#Invoking_mklib_manually
>
> Regards,
> John
>
>
>
>
> On Mar 23, 2016, at 5:55 PM, John Tobias  wrote:
>
> Hi John,
>
> I have the PRU Add on which is pru-icss-4.0.1. Then, I tried the latest
> example from the git you provided.
> I have some compilation error (please see the attached log.txt)
>
> Regards,
>
> John
>
>
> On Wed, Mar 23, 2016 at 4:37 PM, John Syne  wrote:
>
>> Or you can use the latest examples from here:
>>
>>
>> https://git.ti.com/pru-software-support-package/pru-software-support-package
>>
>> Regards,
>> John
>>
>>
>>
>>
>> On Mar 23, 2016, at 1:54 PM, John Tobias 
>> wrote:
>>
>> Hello Guys,
>>
>> I am using debian image version 8.3 that I downloaded @
>> http://beagleboard.org/latest-images (4.1.15-ti-rt-r43). Also, I
>> downloaded the TI SDK for AM335x (
>> http://software-dl.ti.com/processor-sw/esd/PROCESSOR-SDK-LINUX-AM335X/latest/index_FDS.html
>> ).
>>
>> I compiled the sample program for PRU (toggle_led.out) and copy it over
>> in /lib/firmware/am335x-pru0-fw, but it did not work.
>>
>> Then, I found Robert Nelson's binary and it works fine.
>>
>>
>> https://github.com/RobertCNelson/boot-scripts/commit/20a16f79be80886a1e030d197573b5950f98626d#diff-a0ab1dbc32ef29215c473f3b8979ad32
>>
>>
>> Any idea?.
>>
>> Regards,
>>
>> John
>>
>> --
>> 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 an
>> email to beagleboard+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>>
>> --
>> 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 an
>> email to beagleboard+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> --
> 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 an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
> 
>
>
> --
> 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 an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Le Costaouec Vincent]

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 host ethernet address
[   18.837256] using host ethernet address: D0:39:72:31:1D:3B
[   18.842633] using self ethernet address: D0:39:72:31:1D:30
[   18.886570] usb0: HOST MAC d0:39:72:31:1d:3b
[   18.909174] usb0: MAC d0:39:72:31:1d:30
[   18.921832] using random self ethernet address
[   18.926391] using random host ethernet address
[   18.983303] g_ether gadget: Ethernet Gadget, version: Memorial Day 2008
[   18.990066] g_ether gadget: g_ether ready
root@beagle01:~/labs/exploringBB/chp08/spi/spidev_test# dmesg | grep SPI
[0.00] Kernel command line: console=ttyO0,115200n8 bone_capemgr.
enable_partno=BB-SPIDEV1 root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait
[4.608333] bone_capemgr bone_capemgr: enabled_partno PARTNO 'BB-SPIDEV1' 
VER 'N/A' PR '0'
[4.628986] bone_capemgr bone_capemgr: slot #4: 'Override Board 
Name,00A0,Override Manuf,BB-SPIDEV1'
[4.645313] bone_capemgr bone_capemgr: slot #4: dtbo 
'BB-SPIDEV1-00A0.dtbo' loaded; overlay id #0



Le vendredi 25 mars 2016 15:36:22 UTC+1, RobertCNelson a écrit :
>
> 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 (spi1_d0) and P9_30 
> (spi_d1) 
> > And I'm trying to use the derek molloy program : 
> > 
> https://github.com/derekmolloy/exploringBB/tree/master/chp08/spi/spidev_test 
> > 
> > ./spidev_test -D /dev/spidev2.1 
> > 
> > and also 
> > 
> > ./spidev_test -D /dev/spidev2.0 
> > 
> > However I'm alway having the answer : 
> > spi mode: 0 
> > bits per word: 8 
> > max speed: 50 Hz (500 KHz) 
> > 
> > 00 00 00 00 00 00 
> > 00 00 00 00 00 00 
> > 00 00 00 00 00 00 
> > 00 00 00 00 00 00 
> > 00 00 00 00 00 00 
> > 00 00 00 00 00 00 
> > 00 00 
> > 
> > And I'm supposed to received 
> > bits per word: 8 
> > max speed: 50 Hz (500 KHz) 
> > 
> > FF FF FF FF FF FF 
> > 40 00 00 00 00 95 
> > FF FF FF FF FF FF 
> > FF FF FF FF FF FF 
> > FF FF FF FF FF FF 
> > DE AD BE EF BA AD 
> > F0 0D 
> > I received this when I do that with SPI0 and connected P9_18(spi0_d0) 
> and 
> > P9_21(spi0_d1) 
> > 
> > So I still don't get where did the problem come. 
>
> Compare your cape dts with: 
>
>
> https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/BB-SPIDEV1-00A0.dts
>  
>
> Regards, 
>
> -- 
> Robert Nelson 
> https://rcn-ee.com/ 
>

-- 
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 an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: C compiler

[Graham Haddock]

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 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 Black.
>>
>> --- Graham
>>
>> ==
>>
>> On Friday, March 25, 2016 at 7:33:35 AM UTC-5, c...@isbd.net wrote:
>>>
>>> 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 ??
>>> >
>>> Create your code in a file called, say, myprogram.c.
>>>
>>> Then:-
>>>
>>> gcc -o myprogram myprogram.c
>>>
>>> This will create a compiled program called myprogram which you can
>>> execute by typing its name at the command prompt.  For C++ you can do
>>> the same using g++ instead of gcc.
>>>
>>> For more complex programs and libraries it gets more involved.
>>>
>>> --
>>> Chris Green
>>> ·
>>>
>>> --
>> 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 an
>> email to beagleboard+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Developing next generation wireless audio
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/Q6Ed3hfRQag/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: C compiler

[Seppo Nikkilä]

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 familiar with the basics of Linux, if you
> are
> working on a Linux platform like the BeagleBone Black.
>
> --- Graham
>
> ==
>
> On Friday, March 25, 2016 at 7:33:35 AM UTC-5, c...@isbd.net wrote:
>>
>> 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 ??
>> >
>> Create your code in a file called, say, myprogram.c.
>>
>> Then:-
>>
>> gcc -o myprogram myprogram.c
>>
>> This will create a compiled program called myprogram which you can
>> execute by typing its name at the command prompt.  For C++ you can do
>> the same using g++ instead of gcc.
>>
>> For more complex programs and libraries it gets more involved.
>>
>> --
>> Chris Green
>> ·
>>
>> --
> 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 an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Developing next generation wireless audio

-- 
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 an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Robert Nelson]

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 (spi1_d0) and P9_30 (spi_d1)
> And I'm trying to use the derek molloy program :
> https://github.com/derekmolloy/exploringBB/tree/master/chp08/spi/spidev_test
>
> ./spidev_test -D /dev/spidev2.1
>
> and also
>
> ./spidev_test -D /dev/spidev2.0
>
> However I'm alway having the answer :
> spi mode: 0
> bits per word: 8
> max speed: 50 Hz (500 KHz)
>
> 00 00 00 00 00 00
> 00 00 00 00 00 00
> 00 00 00 00 00 00
> 00 00 00 00 00 00
> 00 00 00 00 00 00
> 00 00 00 00 00 00
> 00 00
>
> And I'm supposed to received
> bits per word: 8
> max speed: 50 Hz (500 KHz)
>
> FF FF FF FF FF FF
> 40 00 00 00 00 95
> FF FF FF FF FF FF
> FF FF FF FF FF FF
> FF FF FF FF FF FF
> DE AD BE EF BA AD
> F0 0D
> I received this when I do that with SPI0 and connected P9_18(spi0_d0) and
> P9_21(spi0_d1)
>
> So I still don't get where did the problem come.

Compare your cape dts with:

https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/BB-SPIDEV1-00A0.dts

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

-- 
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 an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Le Costaouec Vincent]

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 : 
https://github.com/derekmolloy/exploringBB/tree/master/chp08/spi/spidev_test

./spidev_test -D /dev/spidev2.1

and also 

./spidev_test -D /dev/spidev2.0

However I'm alway having the answer : 
spi mode: 0
bits per word: 8
max speed: 50 Hz (500 KHz)

00 00 00 00 00 00 
00 00 00 00 00 00 
00 00 00 00 00 00 
00 00 00 00 00 00 
00 00 00 00 00 00 
00 00 00 00 00 00 
00 00 

And I'm supposed to received
bits per word: 8
max speed: 50 Hz (500 KHz)

FF FF FF FF FF FF 
40 00 00 00 00 95 
FF FF FF FF FF FF 
FF FF FF FF FF FF 
FF FF FF FF FF FF 
DE AD BE EF BA AD 
F0 0D 
I received this when I do that with SPI0 and connected P9_18(spi0_d0) and 
P9_21(spi0_d1)

So I still don't get where did the problem come.





Le vendredi 25 mars 2016 15:09:08 UTC+1, RobertCNelson a écrit :
>
> 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 
> > GNU/Linux 
> > 
> > 
> > # lsb_release -da 
> > Distributor ID:Debian 
> > Description:Debian GNU/Linux 8.3 (jessie) 
> > Release:8.3 
> > Codename:jessie 
> > 
> > # cat $SLOTS 
> >  0: PF  -1 
> >  1: PF  -1 
> >  2: PF  -1 
> >  3: PF  -1 
> >  4: P-O-L-   0 Override Board Name,00A0,Override Manuf,BB-SPIDEV1 
> > 
> > # cat $PINS | grep '990\|998\|994\|99c\|97c' 
> > pin 95 (44e1097c.0) 0033 pinctrl-single 
> > pin 100 (44e10990.0) 0027 pinctrl-single 
> > pin 101 (44e10994.0) 0027 pinctrl-single 
> > pin 102 (44e10998.0) 0027 pinctrl-single 
> > pin 103 (44e1099c.0) 0027 pinctrl-single 
>
> ignore that.. 
>
>
> > # cat /boot/uEnv.txt 
> > uname_r=4.1.18-bone20 
> > dtb=am335x-boneblack-overlay.dtb 
> > 
> cape_disable=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN,BB-BONE-EMMC-2G
>  
>
> > cape_enable=bone_capemgr.enable_partno=BB-SPIDEV1 
>
> remove 
> "cape_disable=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN,BB-BONE-EMMC-2G"
>  
>
> it's not used with "4.1.x".. 
>
> > 
> > # dmesg |grep SPI 
> > [0.00] Kernel command line: console=ttyO0,115200n8 
> > capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN,BB-BONE-EMMC-2G 
> > bone_capemgr.enable_partno=BB-SPIDEV1 root=/dev/mmcblk0p1 ro 
> rootfstype=ext4 
> > rootwait 
> > [4.618372] bone_capemgr bone_capemgr: enabled_partno PARTNO 
> 'BB-SPIDEV1' 
> > VER 'N/A' PR '0' 
> > [4.639023] bone_capemgr bone_capemgr: slot #4: 'Override Board 
> > Name,00A0,Override Manuf,BB-SPIDEV1' 
> > [4.655351] bone_capemgr bone_capemgr: slot #4: dtbo 
> > 'BB-SPIDEV1-00A0.dtbo' loaded; overlay id #0 
> > 
> > # ls -la /dev/spi* 
> > crw-rw 1 root spi 153, 0 Mar 25 14:17 /dev/spidev2.0 
> > crw-rw 1 root spi 153, 1 Mar 25 14:17 /dev/spidev2.1 
>
> it's loaded, have you actually wired something up to it and tested? 
>
> Regards, 
>
> -- 
> Robert Nelson 
> https://rcn-ee.com/ 
>

-- 
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 an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: C compiler

[Graham]

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 Black.

--- Graham

==

On Friday, March 25, 2016 at 7:33:35 AM UTC-5, c...@isbd.net wrote:
>
> 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 ?? 
> > 
> Create your code in a file called, say, myprogram.c. 
>
> Then:- 
>
> gcc -o myprogram myprogram.c 
>
> This will create a compiled program called myprogram which you can 
> execute by typing its name at the command prompt.  For C++ you can do 
> the same using g++ instead of gcc. 
>
> For more complex programs and libraries it gets more involved. 
>
> -- 
> Chris Green 
> · 
>
>

-- 
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 an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Robert Nelson]

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
> GNU/Linux
>
>
> # lsb_release -da
> Distributor ID:Debian
> Description:Debian GNU/Linux 8.3 (jessie)
> Release:8.3
> Codename:jessie
>
> # cat $SLOTS
>  0: PF  -1
>  1: PF  -1
>  2: PF  -1
>  3: PF  -1
>  4: P-O-L-   0 Override Board Name,00A0,Override Manuf,BB-SPIDEV1
>
> # cat $PINS | grep '990\|998\|994\|99c\|97c'
> pin 95 (44e1097c.0) 0033 pinctrl-single
> pin 100 (44e10990.0) 0027 pinctrl-single
> pin 101 (44e10994.0) 0027 pinctrl-single
> pin 102 (44e10998.0) 0027 pinctrl-single
> pin 103 (44e1099c.0) 0027 pinctrl-single

ignore that..


> # cat /boot/uEnv.txt
> uname_r=4.1.18-bone20
> dtb=am335x-boneblack-overlay.dtb
> cape_disable=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN,BB-BONE-EMMC-2G
> cape_enable=bone_capemgr.enable_partno=BB-SPIDEV1

remove 
"cape_disable=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN,BB-BONE-EMMC-2G"
it's not used with "4.1.x"..

>
> # dmesg |grep SPI
> [0.00] Kernel command line: console=ttyO0,115200n8
> capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN,BB-BONE-EMMC-2G
> bone_capemgr.enable_partno=BB-SPIDEV1 root=/dev/mmcblk0p1 ro rootfstype=ext4
> rootwait
> [4.618372] bone_capemgr bone_capemgr: enabled_partno PARTNO 'BB-SPIDEV1'
> VER 'N/A' PR '0'
> [4.639023] bone_capemgr bone_capemgr: slot #4: 'Override Board
> Name,00A0,Override Manuf,BB-SPIDEV1'
> [4.655351] bone_capemgr bone_capemgr: slot #4: dtbo
> 'BB-SPIDEV1-00A0.dtbo' loaded; overlay id #0
>
> # ls -la /dev/spi*
> crw-rw 1 root spi 153, 0 Mar 25 14:17 /dev/spidev2.0
> crw-rw 1 root spi 153, 1 Mar 25 14:17 /dev/spidev2.1

it's loaded, have you actually wired something up to it and tested?

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

-- 
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 an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Le Costaouec Vincent]

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)
Release:8.3
Codename:jessie

# cat $SLOTS
 0: PF  -1 
 1: PF  -1 
 2: PF  -1 
 3: PF  -1 
 4: P-O-L-   0 Override Board Name,00A0,Override Manuf,BB-SPIDEV1

# cat $PINS | grep '990\|998\|994\|99c\|97c'
pin 95 (44e1097c.0) 0033 pinctrl-single 
pin 100 (44e10990.0) 0027 pinctrl-single 
pin 101 (44e10994.0) 0027 pinctrl-single 
pin 102 (44e10998.0) 0027 pinctrl-single 
pin 103 (44e1099c.0) 0027 pinctrl-single 


# cat /boot/uEnv.txt 
uname_r=4.1.18-bone20
dtb=am335x-boneblack-overlay.dtb
cape_disable=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN,BB-BONE-
EMMC-2G
cape_enable=bone_capemgr.enable_partno=BB-SPIDEV1

# dmesg |grep SPI
[0.00] Kernel command line: console=ttyO0,115200n8 capemgr.
disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN,BB-BONE-EMMC-2G bone_capemgr.
enable_partno=BB-SPIDEV1 root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait
[4.618372] bone_capemgr bone_capemgr: enabled_partno PARTNO 'BB-SPIDEV1' 
VER 'N/A' PR '0'
[4.639023] bone_capemgr bone_capemgr: slot #4: 'Override Board 
Name,00A0,Override Manuf,BB-SPIDEV1'
[4.655351] bone_capemgr bone_capemgr: slot #4: dtbo 
'BB-SPIDEV1-00A0.dtbo' loaded; overlay id #0

# ls -la /dev/spi*
crw-rw 1 root spi 153, 0 Mar 25 14:17 /dev/spidev2.0
crw-rw 1 root spi 153, 1 Mar 25 14:17 /dev/spidev2.1

# dmesg |grep cape
[0.00] Kernel command line: console=ttyO0,115200n8 capemgr.
disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN,BB-BONE-EMMC-2G bone_capemgr.
enable_partno=BB-SPIDEV1 root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait
[4.359224] bone_capemgr bone_capemgr: Baseboard: 
'A335BNLT,00C0,4414BBBK9699'
[4.366514] bone_capemgr bone_capemgr: compatible-baseboard=ti,beaglebone
-black - #slots=4
[4.432592] bone_capemgr bone_capemgr: slot #0: No cape found
[4.492588] bone_capemgr bone_capemgr: slot #1: No cape found
[4.552588] bone_capemgr bone_capemgr: slot #2: No cape found
[4.612588] bone_capemgr bone_capemgr: slot #3: No cape found
[4.618372] bone_capemgr bone_capemgr: enabled_partno PARTNO 'BB-SPIDEV1' 
VER 'N/A' PR '0'
[4.626683] bone_capemgr bone_capemgr: slot #4: override
[4.632019] bone_capemgr bone_capemgr: Using override eeprom data at 
slot 4
[4.639023] bone_capemgr bone_capemgr: slot #4: 'Override Board 
Name,00A0,Override Manuf,BB-SPIDEV1'
[4.648433] bone_capemgr bone_capemgr: initialized OK.
[4.655351] bone_capemgr bone_capemgr: slot #4: dtbo 
'BB-SPIDEV1-00A0.dtbo' loaded; overlay id #0

In addition, I'm not currently using the eMMC. 
So, I don't really understand what I'm doing wrong. 
It looks like for me that it is an issue with the HDMI audio (mcasp), but I 
don't see what I can do.
Is it because of the kernel version? Or is it something else?
If someone have any suggestions.

Thanks by advance
Regards
Vincent







Le vendredi 24 juillet 2015 04:49:09 UTC+2, thom...@googlemail.com a écrit :
>
> Update: setting "dtb=am335x-boneblack-emmc-overlay.dtb" in /boot/Env.txt 
> solved the issue after updating to the  "4.1.2-ti-r4" kernel image. Thanks 
> for the help!
>
> On Wednesday, July 22, 2015 at 11:33:48 AM UTC-7, RobertCNelson wrote:
>>
>> On Wed, Jul 22, 2015 at 11:20 AM,   wrote: 
>> > after uncommenting the line: 
>> > #dtb=am335x-boneblack-overlay.dtb 
>> > 
>> > ...my beaglebone has trouble loading the kernel and drops to a shell. 
>>  i've 
>> > managed to record the debug output from uart0: 
>> > 
>> > Starting kernel ... 
>> > 
>> > [0.000453] WARNING: Your 'console=ttyO0' has been replaced by 
>> 'ttyS0' 
>> > [0.000463] This ensures that you still see kernel messages. Please 
>> > [0.000471] update your kernel commandline. 
>> > [3.554658] omap_voltage_late_init: Voltage driver support not added 
>> > [3.676455] bone_capemgr bone_capemgr: slot #0: No cape found 
>> > [3.736442] bone_capemgr bone_capemgr: slot #1: No cape found 
>> > [3.796440] bone_capemgr bone_capemgr: slot #2: No cape found 
>> > [3.856434] bone_capemgr bone_capemgr: slot #3: No cape found 
>> > Loading, please wait... 
>> > Gave up waiting for root device.  Common problems: 
>> >  - Boot args (cat /proc/cmdline) 
>> >- Check rootdelay= (did the system wait long enough?) 
>> >- Check root= (did the system wait for the right device?) 
>> >  - Missing modules (cat /proc/modules; ls /dev) 
>> > ALERT!  /dev/disk/by-uuid/4ccbfb5c-9e82-4bed-aa38-a0d7a10e2404 does not 
>> > exist.  Dropping to a shell! 
>> > (initramfs) cat /proc/cmdline 
>> > console=ttyO0,115200n8 
>> bone_capemgr.enable_partno=BB-I2C1,BB-CAN1,BB-SPIDEV1 
>> > root=UUID=4ccbfb5c-9e82-4bed-aa38-a0d7a10e2404 ro 

[beagleboard] Re: C compiler

[cl]

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 ??
> 
Create your code in a file called, say, myprogram.c.

Then:-

gcc -o myprogram myprogram.c

This will create a compiled program called myprogram which you can
execute by typing its name at the command prompt.  For C++ you can do
the same using g++ instead of gcc.

For more complex programs and libraries it gets more involved.

-- 
Chris Green
·

-- 
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 an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Load overlay at boot

[dorica]

>
> 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 difference 
> between them (audio), but I cant find where it says it has to load the 
> cape-universaln.
> It is, somehow, speciffied in am335x_evm.sh? if so, can it be changed? 
> I have tried to make a custom overlay, setting P9_14 as output, but I 
> cannot put it in slots, because is in conflict with the loaded cape. I can 
> modify the source file for cape-universaln, compile and repalce the dtbo, 
> but I dont like the idea so much, so now I am stuck at wondering where are 
> those overlays loaded, and how can i avoid conflicts. 
>
 

> Putting it to /etc/default/capemgr makes slots showing that my overlay has 
> been loaded (also in dmesg), but it has replaced the cape-universaln, and 
> all the gpios in sys/class/gpio are gone (they are not defined in my 
> overlay) and replaced with gpiochip0, 32, 64 and 96.
>
I dont want to change all the pins, I just want to make P9_14 an output, at 
boot, so I can use it without setting it every time (and wihout root). How 
can I do that.
Also,echo it to export say permission denied (as root). 
Thank you

-- 
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 an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: overlays load at boot

[dorica]

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 in 
> /boot/uEnv.txt is says it has to load cape-universal. I know the difference 
> between them (audio), but I cant find where it says it has to load the 
> cape-universaln.
> It is, somehow, speciffied in am335x_evm.sh? if so, can it be changed? 
> I have tried to make a custom overlay, setting P9_14 as output, but I 
> cannot put it in slots, because is in conflict with the loaded cape. I can 
> modify the source file for cape-universaln, compile and repalce the dtbo, 
> but I dont like the idea so much, so now I am stuck at wondering where are 
> those overlays loaded, and how can i avoid conflicts. 
>
 

> Putting it to /etc/default/capemgr makes slots showing that my overlay has 
> been loaded (also in dmesg), but it has replaced the cape-universaln, and 
> all the gpios in sys/class/gpio are gone (they are not defined in my 
> overlay) and replaced with gpiochip0, 32, 64 and 96.
>
I dont want to change all the pins, I just want to make P9_14 an output, at 
boot, so I can use it without setting it every time (and wihout root). How 
can I do that.
Also,echo it to export say permission denied (as root). 

> Thank you
>

-- 
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 an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] overlays load at boot

[dorica]

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 difference 
between them (audio), but I cant find where it says it has to load the 
cape-universaln.
It is, somehow, speciffied in am335x_evm.sh? if so, can it be changed? 
I have tried to make a custom overlay, setting P9_14 as output, but I 
cannot put it in slots, because is in conflict with the loaded cape. I can 
modify the source file for cape-universaln, compile and repalce the dtbo, 
but I dont like the idea so much, so now I am stuck at wondering where are 
those overlays loaded, and how can i avoid conflicts. Putting it to 
/etc/default/capemgr, maybe might help?
Thank you

-- 
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 an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] C compiler

[Wadi Ben Rhouma]

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 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
> >
> >
> > --
> > 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 an
> > email to beagleboard+unsubscr...@googlegroups.com.
> > For more options, visit https://groups.google.com/d/optout.
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/Q6Ed3hfRQag/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
*Wadi Ben Rhouma*
*Vice Président ENET'COM Junior Entreprise*

*Tél : +216 53 56 61 70*
*E-mail : wadi.benrhoum...@gamil.com *
*Facebook : https://www.facebook.com/wadi.benrhouma
*
*Skype : benrhoumawadi*

*--Dream as if you'll live forever; Live as if you'll die today.--*

-- 
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 an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] C compiler

[Wadi Ben Rhouma]

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 
> 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
> >
> >
> > --
> > 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 an
> > email to beagleboard+unsubscr...@googlegroups.com.
> > For more options, visit https://groups.google.com/d/optout.
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/Q6Ed3hfRQag/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
*Wadi Ben Rhouma*
*Vice Président ENET'COM Junior Entreprise*

*Tél : +216 53 56 61 70*
*E-mail : wadi.benrhoum...@gamil.com *
*Facebook : https://www.facebook.com/wadi.benrhouma
*
*Skype : benrhoumawadi*

*--Dream as if you'll live forever; Live as if you'll die today.--*

-- 
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 an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] C compiler

[Dieter Wirz]

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
>
>
> --
> 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 an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
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 an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] C compiler

[Brainiac]

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 are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.