Re: [beagleboard] Re: Is memory spec in dts shipped with BBB A6A Angstrom 3.8.13 wrong?

[ags]

Not necessarily an issue. Originally I was wondering if only half of 
available physical memory was being made available. Still, I'd like to 
understand why the device tree bindings indicate 256 MB memory, yet it 
appears that the full 512 MB are available.


On Thursday, April 24, 2014 7:23:51 AM UTC-7, RobertCNelson wrote:
>
> On Thu, Apr 24, 2014 at 9:13 AM, ags > 
> wrote: 
> >> Any suggestions on where to look next to figure out what's going on 
> here? 
> >> Seems that either something other than the device tree in file 
> >> "/boot/am335x-boneblack.dts" is being read at boot, or there is 
> something 
> >> else that is overriding later on, or a boot parameter... or the memory 
> >> specification in the reg property doesn't work as I expect it to. 
>
> So... What issue are you having with it?  Other then the dts file 
> showing 256Mb and linux showing 512Mb available? 
>
> u-boot initializes the memory, the kernel just uses what's available. 
>
> Regards, 
>
> -- 
> Robert Nelson 
> http://www.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] Compile Error on AM335x_PRU_BeagleBone examples - vfp mismatch

[stuie_norris via BeagleBoard]

Hi Forum,

I am attempting to learn to use the PRU on the BBB.  I have ubuntu-armhf 
3.8.13-bone30 kernel with gcc-armhf 3.8.13-bone30 compiler installed.

I am following the instructions from ECE497 BeagleBone PRU at
http://elinux.org/ECE497_BeagleBone_PRU#Building_and_Running_the_GPIO_PWM_PRU_Example

However, when I try to compile the example I get an error message about 
VFP.  My system is reported as "soft".

ubuntu@ubuntu-armhf:~$ gcc -print-multi-lib
.;
sf;@mfloat-abi=soft

What is the problem and what should I do to resolve it?

Thanks

Stuart

ubuntu@ubuntu-armhf:~$ git clone 
git://github.com/millerap/AM335x_PRU_BeagleBoneCloning into 
'AM335x_PRU_BeagleBone'...
remote: Reusing existing pack: 111, done.
remote: Total 111 (delta 0), reused 0 (delta 0)
Receiving objects: 100% (111/111), 248.41 KiB | 131.00 KiB/s, done.
Resolving deltas: 100% (34/34), done.
Checking connectivity... done

ubuntu@ubuntu-armhf:~$ cd AM335x_PRU_BeagleBone/GPIO_PWM_PRU/interface
ubuntu@ubuntu-armhf:~/AM335x_PRU_BeagleBone/GPIO_PWM_PRU/interface$ export 
CROSS_COMPILE=""
ubuntu@ubuntu-armhf:~/AM335x_PRU_BeagleBone/GPIO_PWM_PRU/interface$ make
gcc -I. -Wall -I../include   -c -g -O0 -D__DEBUG -o debug/prussdrv.o 
prussdrv.c
ar rc ../lib/libprussdrvd.a debug/prussdrv.o

ubuntu@ubuntu-armhf:~/AM335x_PRU_BeagleBone/GPIO_PWM_PRU/interface$ cd 
../utils/pasm_source
ubuntu@ubuntu-armhf:~/AM335x_PRU_BeagleBone/GPIO_PWM_PRU/utils/pasm_source$./linuxbuild

ubuntu@ubuntu-armhf:~/AM335x_PRU_BeagleBone/GPIO_PWM_PRU/utils/pasm_source$cd 
../../
ubuntu@ubuntu-armhf:~/AM335x_PRU_BeagleBone/GPIO_PWM_PRU$ make 
CROSS_COMPILE=""

gcc -Wall -I./include -D__DEBUG -O2 -mtune=cortex-a8 -march=armv7-a -o 
bin/blinker obj/blinker.o -L./lib -lprussdrv -lpthread
/usr/bin/ld: error: bin/blinker uses VFP register arguments, obj/blinker.o 
does not
/usr/bin/ld: failed to merge target specific data of file obj/blinker.o
/usr/bin/ld: error: bin/blinker uses VFP register arguments, 
./lib/libprussdrv.a(prussdrv.o) does not
/usr/bin/ld: failed to merge target specific data of file 
./lib/libprussdrv.a(prussdrv.o)
collect2: error: ld returned 1 exit status
make: *** [bin/blinker] Error 1

-- 
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] What is the default root password for 3.8.13-bone47 installation

[William Hermans]

Hmmm, wow, I guess in this day and age google + "how to secure my debian
system" is just too much trouble for the instant gratification crowd.



On Fri, Apr 25, 2014 at 4:44 PM, Robert Nelson wrote:

>
> On Apr 25, 2014 6:36 PM, "William Hermans"  wrote:
> >
> > @Robert
> >
> > What ?! Granted I did not use the prerolled image, but I am using the
> same basic( bare ) image passwd was "root"
>
> Just changed it, bunch of noobs complained when their default setup got
> owned as it was internet facing.
>
> >
> >
> > On Fri, Apr 25, 2014 at 4:33 PM, Robert Nelson 
> wrote:
> >>
> >>
> >> On Apr 25, 2014 6:28 PM, "Mike"  wrote:
> >> >
> >> > I also checked the ssh login script and allowrootlogin is set to
> 'yes'.
> >> >
> >> >
> >> > On Friday, April 25, 2014 4:26:12 PM UTC-7, Mike wrote:
> >> >>
> >> >>
> >> >> Neither  nor "root" nor <> work. I get "authentication
> failure."
> >> >>
> >> >>> It's setup as 'blank' to match the old Angstrom releases.
> >>
> >> Oh wait 4-18. Read the notes, only user debian is setup. Root is
> disabled on those images now.
> >>
> >> >>>
> >> >>> >
> >> >>> > --
> >> >>> > 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...@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] What is the default root password for 3.8.13-bone47 installation

[Robert Nelson]

On Apr 25, 2014 6:36 PM, "William Hermans"  wrote:
>
> @Robert
>
> What ?! Granted I did not use the prerolled image, but I am using the
same basic( bare ) image passwd was "root"

Just changed it, bunch of noobs complained when their default setup got
owned as it was internet facing.

>
>
> On Fri, Apr 25, 2014 at 4:33 PM, Robert Nelson 
wrote:
>>
>>
>> On Apr 25, 2014 6:28 PM, "Mike"  wrote:
>> >
>> > I also checked the ssh login script and allowrootlogin is set to 'yes'.
>> >
>> >
>> > On Friday, April 25, 2014 4:26:12 PM UTC-7, Mike wrote:
>> >>
>> >>
>> >> Neither  nor "root" nor <> work. I get "authentication
failure."
>> >>
>> >>> It's setup as 'blank' to match the old Angstrom releases.
>>
>> Oh wait 4-18. Read the notes, only user debian is setup. Root is
disabled on those images now.
>>
>> >>>
>> >>> >
>> >>> > --
>> >>> > 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...@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] What is the default root password for 3.8.13-bone47 installation

[Robert Nelson]

On Apr 25, 2014 6:35 PM, "Mike"  wrote:
>
>
> Thanks for that Robert - I guess I'll trash it then and go to something I
can use.

Sudo su
Passwd -l xyz

Takes 5 seconds to enable.

>
>
> On Friday, April 25, 2014 4:33:01 PM UTC-7, RobertCNelson wrote:
>>
>>
>>
>> Oh wait 4-18. Read the notes, only user debian is setup. Root is
disabled on those images now.
>>
>>
> --
> 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] What is the default root password for 3.8.13-bone47 installation

[William Hermans]

@Robert

What ?! Granted I did not use the prerolled image, but I am using the same
basic( bare ) image passwd was "root"


On Fri, Apr 25, 2014 at 4:33 PM, Robert Nelson wrote:

>
> On Apr 25, 2014 6:28 PM, "Mike"  wrote:
> >
> > I also checked the ssh login script and allowrootlogin is set to 'yes'.
> >
> >
> > On Friday, April 25, 2014 4:26:12 PM UTC-7, Mike wrote:
> >>
> >>
> >> Neither  nor "root" nor <> work. I get "authentication failure."
> >>
> >>> It's setup as 'blank' to match the old Angstrom releases.
>
> Oh wait 4-18. Read the notes, only user debian is setup. Root is disabled
> on those images now.
>
> >>>
> >>> >
> >>> > --
> >>> > 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...@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] What is the default root password for 3.8.13-bone47 installation

[Mike]

Thanks for that Robert - I guess I'll trash it then and go to something I 
can use.

On Friday, April 25, 2014 4:33:01 PM UTC-7, RobertCNelson wrote:
>
>
>
> Oh wait 4-18. Read the notes, only user debian is setup. Root is disabled 
> on those images now.
>
>
>  

-- 
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] What is the default root password for 3.8.13-bone47 installation

[William Hermans]

So, logging in as normal user "debian" then issuing su followed by "root"
or blank does not work ?


On Fri, Apr 25, 2014 at 4:28 PM, Mike  wrote:

> I also checked the ssh login script and allowrootlogin is set to 'yes'.
>
>
> On Friday, April 25, 2014 4:26:12 PM UTC-7, Mike wrote:
>>
>>
>> Neither  nor "root" nor <> work. I get "authentication failure."
>>
>> It's setup as 'blank' to match the old Angstrom releases.
>>>
>>> >
>>> > --
>>> > 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...@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] What is the default root password for 3.8.13-bone47 installation

[Robert Nelson]

On Apr 25, 2014 6:28 PM, "Mike"  wrote:
>
> I also checked the ssh login script and allowrootlogin is set to 'yes'.
>
>
> On Friday, April 25, 2014 4:26:12 PM UTC-7, Mike wrote:
>>
>>
>> Neither  nor "root" nor <> work. I get "authentication failure."
>>
>>> It's setup as 'blank' to match the old Angstrom releases.

Oh wait 4-18. Read the notes, only user debian is setup. Root is disabled
on those images now.

>>>
>>> >
>>> > --
>>> > 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...@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] What is the default root password for 3.8.13-bone47 installation

[Mike]

The instructions said to login as debian/temppwd and that works but it's 
useless.

On Friday, April 25, 2014 4:21:00 PM UTC-7, William Hermans wrote:
>
> *root : root*
>
> You should really read the instructions that came with the image.
>
>

-- 
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] What is the default root password for 3.8.13-bone47 installation

[Mike]

I also checked the ssh login script and allowrootlogin is set to 'yes'.

On Friday, April 25, 2014 4:26:12 PM UTC-7, Mike wrote:
>
>
> Neither  nor "root" nor <> work. I get "authentication failure."
>
> It's setup as 'blank' to match the old Angstrom releases.
>>
>> >
>> > -- 
>> > 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...@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] What is the default root password for 3.8.13-bone47 installation

[Mike]

Neither  nor "root" nor <> work. I get "authentication failure."

It's setup as 'blank' to match the old Angstrom releases.
>
> >
> > -- 
> > 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...@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] What is the default root password for 3.8.13-bone47 installation

[Robert Nelson]

On Apr 25, 2014 6:15 PM, "Mike"  wrote:
>
> I feel almost stupid asking this, but I just installed
BBB-eMMC-flasher-debian-7.4-2014-04-18-2gb.img.xz
> and I cannot use either debug console nor SSH to do any useful work
because it will not let me be root.
> I cannot use sudo for same reason - what is the superuser password in
this release?
> Thanks.

It's setup as 'blank' to match the old Angstrom releases.

>
> --
> 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] What is the default root password for 3.8.13-bone47 installation

[William Hermans]

*root : root*

You should really read the instructions that came with the image.


On Fri, Apr 25, 2014 at 4:14 PM, Mike  wrote:

> I feel almost stupid asking this, but I just installed
> BBB-eMMC-flasher-debian-7.4-2014-04-18-2gb.img.xz
> and I cannot use either debug console nor SSH to do any useful work
> because it will not let me be root.
> I cannot use sudo for same reason - what is the superuser password in this
> release?
> Thanks.
>
> --
> 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] What is the default root password for 3.8.13-bone47 installation

[Mike]

I feel almost stupid asking this, but I just installed 
BBB-eMMC-flasher-debian-7.4-2014-04-18-2gb.img.xz
and I cannot use either debug console nor SSH to do any useful work because 
it will not let me be root.
I cannot use sudo for same reason - what is the superuser password in this 
release?
Thanks.

-- 
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] BeagleBone Black RevB with Debian 2014-04-14 SD image -- networking issues

[William Hermans]

hmmm, I do not think my laptop screen has been tested for having coke spit
at it either . . .


On Fri, Apr 25, 2014 at 11:21 AM, Robert P. J. Day wrote:

> On Fri, 25 Apr 2014, Gerald Coley wrote:
>
> > It has been tested for robustness. Just not tested for you.
> > Gerald
>
>   Test nazi. No testing for *you*.
>
> rday
>
> --
>
> 
> Robert P. J. Day Ottawa, Ontario, CANADA
> http://crashcourse.ca
>
> Twitter:   http://twitter.com/rpjday
> LinkedIn:   http://ca.linkedin.com/in/rpjday
> 
>
> --
> 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] Device Overlay to Switch off USR0-3 LEDS

[stuie_norris]

Hi Cody,

Well spotted the typo with the lablels, but it still does not work.  The 
dts file I now am using is

/dts-v1/;
/plugin/;
/
{
compatible = "ti,beaglebone", "ti,beaglebone-black";
part-number = "BBB-LEDS-00A0";
version = "00A0";
fragment@0
{
target = <&ocp>;
__overlay__
{
 gpio-leds {
compatible = "gpio-leds";
pinctrl-names = "default";
pinctrl-0 = <&userled_pins>;

led0 {
label = "beaglebone:green:usr0";
gpios = <&gpio2 21 0>;
linux,default-trigger = "none";
default-state = "off";
};

led1 {
label = "beaglebone:green:usr1";
gpios = <&gpio2 22 0>;
linux,default-trigger = "none";
default-state = "off";
};

led2 {
label = "beaglebone:green:usr2";
gpios = <&gpio2 23 0>;
linux,default-trigger = "none";
default-state = "off";
};

led3 {
label = "beaglebone:green:usr3";
gpios = <&gpio2 24 0>;
default-state = "off";
linux,default-trigger = "none";
};
};

};
};
};

Thanks

Stuart

-- 
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] Problems modifying device tree (3.14 kernel)

[Charles Steinkuehler]

On 4/25/2014 4:26 PM, kip...@ualberta.ca wrote:
> If not, advice on getting the kernel 
> to load my own dtb file would still be great.

The kernel doesn't load your device tree.  The kernel just uses the
device tree loaded into memory by the boot loader.  If you're using the
recent Debian images, you need to edit the line that looks like this:

loadfdt=load mmc ${mmcdev}:${mmcpart} ${fdtaddr} /dtbs/${fdtfile}

The ${fdtfile} is the filename of the device tree u-boot will load and
pass to the kernel.  This isn't generally set in the uEnv.txt file,
which means you're using the default value (which is set by some script
stuff that happens behind the scenes in the default uBoot configuration,
not all of which is overridden by the uEnv.txt file).

Anyway, just adjust things so that when the uenvcmd= line is run*, you
have the proper device tree loaded.

[*]
uenvcmd runs loadfiles
loadfiles runs loadfdt
loadfdt loads the device tree file from /dtbs/${fdtfile}

...so the easiest thing to do is probably just change ${fdtfile} to the
name of your device tree.

-- 
Charles Steinkuehler
char...@steinkuehler.net

-- 
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] Problems modifying device tree (3.14 kernel)

[kipper]

I got the kernel build process to build my dtb file, but n now it looks 
like the kernel isn't loading it. I'm not super familiar with how the 
kernel actually figures out which dtb files to use, so I just threw my dtb 
in the boot directory in my root file system, but inspection of 
/proc/device-tre/e makes it pretty clear that it hasn't loaded.

As an experiment, rather than making my own dtb file, I simply threw my 
code into the am335x-bone-common.dtsi device tree, built that and replaced 
the existing one so that it would be loaded automatically. I know this is a 
petty stupid way to change the device tree, but I thought it would be fine 
for a quick test. The LCD still isn't working, but the interesting thing is 
that the additions (pinmux and ocp config for LCD)  to the dtsi file do 
appear in /proc/device-tree/ and its sub-directories. When I compare 
/proc/device-tree/ with these modifications on the 3.14 kernel and 
/proc/device-tree/ with the 3.8 kernel and the corresponding device tree 
overlay, they look pretty identical. By this I mean that all the 
directories/files generated by the device tree overlay match up with the 
configuration of my modified device tree. This makes me think that the 
device tree has loaded properly, but the LCD driver still doesn't seem to 
be configured. 

Here's the contents of the file I modified.  I 
know it's pretty extensive, but if anyone could help me figure out why this 
wouldn't work it would be appreciated. If not, advice on getting the kernel 
to load my own dtb file would still be great.

Thanks,


On Thursday, April 24, 2014 6:35:13 PM UTC-6, john3909 wrote:
>
>
> From: >
> Reply-To: >
> Date: Thursday, April 24, 2014 at 3:48 PM
> To: >
> Subject: Re: [beagleboard] Problems modifying device tree (3.14 kernel)
>
> Thanks for the help guys, but I'm still a little confused on how exactly 
> the build script knows which dtb files to generate. I'm using Robert C 
> Nelson's build 
> scripts and 
> I've modified one of them to skip the kernel and just build the dtbs. The 
> firmware/Makefile that my kernel source has doesn't mention anything about 
> dts or dtb files, so I'm not really sure how I would modify that file in 
> order to build an additional dtb file. The terminal echoes each dtb file it 
> packages, and this list matches the dtb files specified in 
> arch/arm/boot/dts/Makefile so I'm guessing that's what it's using to figure 
> out which dtbs to build/package. Would I modify this file? This makefile 
> only specifies dtb files with no information on the corresponding dts 
> files, so I tried adding a line for my dts file in a similar manner (i.e. I 
> added myBlob.dts to arch/arm/boot/dts/ and then added a myBlob.dtb line to 
> the Makefile) but this doesn't work.
>
> Sorry for needing so much hand-holding through this but I'm really having 
> a tough time wrapping my head around how exactly all this stuff works. 
>
> In firmware/Makefile, you will see capes with the dtbo extension. The 
> makefile runs device tree compiler (dtc) with the source of dts and output 
> of dtbo.  You just need to add your DTS file name, but use the dtbo 
> extension. 
>
> Regards,
> John
>
>
>
> On Thursday, April 24, 2014 3:31:55 PM UTC-6, Charles Steinkuehler wrote:
>>
>> On 4/24/2014 4:25 PM, John Syn wrote: 
>> > 
>> >> I built the kernel I'm using from source, so it wouldn't be too 
>> challenging to 
>> >> rebuild it with my file included. If the kernel needs to compile dts 
>> files 
>> >> during its build, does it need to be told to look for my new file? I 
>> haven't 
>> >> included any board-specific information in the file (aside from the 
>> #include) 
>> >> so I'd assume that the kernel can't figure this out on its own while 
>> it's 
>> >> building. My initial frantic googling hasn't given me a location of 
>> this 
>> >> configuration, so do you (or anyone, really) know where you specify 
>> the device 
>> >> tree files to build? 
>> > 
>> > Add you DTS file to firmware/Makefile 
>>
>> Note that unless you're trying to build the device tree into the kernel 
>> itself (which isn't done on the BeagleBone), building the dtb files is 
>> pretty much completely separate from building the kernel. 
>>
>> So to experiment, you can just run builds local to the firmware 
>> directory, although I'd recommend getting your dts tweaks committed to a 
>> clone of the kernel source/build-scripts (whichever you're using).  That 
>> should make it easier to track progress of all the folks frantically 
>> working on improving ARM device-tree support!  :) 
>>
>> -- 
>> Charles Steinkuehler 
>> cha...@steinkuehler.net
>>
> -- 
> 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 beagleboa

Re: [beagleboard] Fwd: Help for generation Image BeagleBone Black

[vanessa . borba]

Contents of uEnv.txt:

bootargs=console=ttyO0,115200n8 root=/dev/mmcblk0p2 rw rootfstype=ext4 
rootwait
uenvcmd=mmc dev ${mmcdev};load mmc ${mmcdev} ${loadaddr} uImage;load mmc 
${mmcdev} ${fdtaddr} am335x-boneblack.dtb;bootm ${loadaddr} - ${fdtaddr}

-- 
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] Fwd: Help for generation Image BeagleBone Black

[Cody Lacey]

what are the contents of uEnv.txt?


On Fri, Apr 25, 2014 at 2:04 PM,  wrote:

> Hello,
> I created the directories on PC. Modules compiled and installed modules
> and headers as indicated. I ran the command sudo chown-R root.root / media
> / rootfs_ / lib / firmware, copied to other directories for User Group and
> were the root and not the user of my machine. However follow with the same
> problem.
>
> Below I am putting as was the partitions on the SD card.
>
> Boot:
>
> *vanessa@vanessa-VirtualBox:~$ ls -lsa /media/boot/*
> *total 4760*
> *   1 drwx-- 2 vanessa vanessa 512 Dez 31  1969 .*
> *   4 drwxr-xr-x 7 rootroot   4096 Abr 25 15:46 ..*
> *  25 -rw-r--r-- 1 vanessa vanessa   24968 Abr 25 14:59
> am335x-boneblack.dtb*
> * 102 -rw-r--r-- 1 vanessa vanessa  103812 Abr 25 14:59 MLO*
> * 354 -rw-r--r-- 1 vanessa vanessa  362136 Abr 25 14:59 u-boot.img*
> *   1 -rw-r--r-- 1 vanessa vanessa 226 Abr 25 14:59 uEnv.txt*
> *4275 -rw-r--r-- 1 vanessa vanessa 4376808 Abr 25 14:59 uImage*
> *vanessa@vanessa-VirtualBox:~$ ls -lsa /media/rootfs_/*
> *total 84*
> * 4 drwxrwxr-x 18 root root  4096 Abr 25 15:24 .*
> * 4 drwxr-xr-x  7 root root  4096 Abr 25 15:46 ..*
> * 4 drwxrwxr-x  2 root root  4096 Abr 25 14:07 bin*
> * 4 drwxr-xr-x  3 root root  4096 Abr 25 14:09 dev*
> * 4 drwxr-xr-x  5 root root  4096 Dez 31  1999 etc*
> * 4 drwxrwxr-x  4 root root  4096 Abr 25 14:09 home*
> * 4 drwxrwxr-x  4 root root  4096 Abr 25 15:28 lib*
> * 0 lrwxrwxrwx  1 root root 3 Abr 25 13:59 lib32 -> lib*
> * 0 lrwxrwxrwx  1 root root11 Abr 25 14:07 linuxrc -> bin/busybox*
> *16 drwx--  2 root root 16384 Abr 25 14:58 lost+found*
> * 4 drwxrwxr-x  2 root root  4096 Ago 30  2013 media*
> * 4 drwxrwxr-x  2 root root  4096 Ago 30  2013 mnt*
> * 4 drwxrwxr-x  2 root root  4096 Ago 30  2013 opt*
> * 4 drwxrwxr-x  2 root root  4096 Ago 30  2013 proc*
> * 4 drwx--  2 root root  4096 Ago 30  2013 root*
> * 0 lrwxrwxrwx  1 root root 3 Ago 30  2013 run -> tmp*
> * 4 drwxrwxr-x  2 root root  4096 Abr 25 14:07 sbin*
> * 4 drwxrwxr-x  2 root root  4096 Ago 30  2013 sys*
> * 4 drwxrwxrwt  3 root root  4096 Dez 31  1999 tmp*
> * 4 drwxrwxr-x  7 root root  4096 Abr 25 15:07 usr*
> * 4 drwxrwxr-x  4 root root  4096 Abr 25 14:09 var*
> *vanessa@vanessa-VirtualBox:~$ ls -lsa /media/rootfs_/lib*
> *total 2604*
> *   4 drwxrwxr-x  4 root root4096 Abr 25 15:28 .*
> *   4 drwxrwxr-x 18 root root4096 Abr 25 15:24 ..*
> *   4 drwxrwxr-x  7 root root4096 Abr 25 14:53 firmware*
> * 132 -rwxr-xr-x  1 root root  134316 Abr 25 14:07 ld-2.17.so
> *
> *   0 lrwxrwxrwx  1 root root  10 Abr 25 14:01 ld-linux.so.3 ->
> ld-2.17.so *
> *1228 -rwxr-xr-x  1 root root 1254532 Abr 25 14:07 libc-2.17.so
> *
> *  40 -rwxr-xr-x  1 root root   38480 Abr 25 14:07 libcrypt-2.17.so
> *
> *   0 lrwxrwxrwx  1 root root  16 Abr 25 14:01 libcrypt.so.1 ->
> libcrypt-2.17.so *
> *   0 lrwxrwxrwx  1 root root  12 Abr 25 14:01 libc.so.6 ->
> libc-2.17.so *
> *  20 -rwxr-xr-x  1 root root   18008 Abr 25 14:07 libdl-2.17.so
> *
> *   0 lrwxrwxrwx  1 root root  13 Abr 25 14:01 libdl.so.2 ->
> libdl-2.17.so *
> * 132 -rwxr-xr-x  1 root root  133660 Abr 25 14:07 libgcc_s.so.1*
> * 620 -rwxr-xr-x  1 root root  632404 Abr 25 14:07 libm-2.17.so
> *
> *   0 lrwxrwxrwx  1 root root  12 Abr 25 14:01 libm.so.6 ->
> libm-2.17.so *
> *  80 -rwxr-xr-x  1 root root   79808 Abr 25 14:07 libnsl-2.17.so
> *
> *   0 lrwxrwxrwx  1 root root  14 Abr 25 14:01 libnsl.so.1 ->
> libnsl-2.17.so *
> *  28 -rwxr-xr-x  1 root root   26224 Abr 25 14:07 libnss_dns-2.17.so
> *
> *   0 lrwxrwxrwx  1 root root  18 Abr 25 14:01 libnss_dns.so.2 ->
> libnss_dns-2.17.so *
> *  52 -rwxr-xr-x  1 root root   51124 Abr 25 14:07 libnss_files-2.17.so
> *
> *   0 lrwxrwxrwx  1 root root  20 Abr 25 14:01 libnss_files.so.2 ->
> libnss_files-2.17.so *
> * 128 -rwxr-xr-x  1 root root  127839 Abr 25 14:07 libpthread-2.17.so
> *
> *   0 lrwxrwxrwx  1 root root  18 Abr 25 14:01 libpthread.so.0 ->
> libpthread-2.17.so *
> *  84 -rwxr-xr-x  1 root root   83820 Abr 25 14:07 libresolv-2.17.so
> *
> *   0 lrwxrwxrwx  1 root root  17 Abr 25 14:01 libresolv.so.2 ->
> libresolv-2.17.so *
> *  28 -rwxr-xr-x  1 root root   26528 Abr 25 14:07 librt-2.17.so
> *
> *   0 lrwxrwxrwx  1 root root  13 Abr 25 14:01 librt.so.1 ->
> librt-2.17.so *
> *  16 -rwxr-xr-x  1 root root   13944 Abr 25 14:07 libutil-2.17.so
> *
> *   0

Re: [beagleboard] Fwd: Help for generation Image BeagleBone Black

[vanessa . borba]

Hello, 
I created the directories on PC. Modules compiled and installed modules and 
headers as indicated. I ran the command sudo chown-R root.root / media / 
rootfs_ / lib / firmware, copied to other directories for User Group and 
were the root and not the user of my machine. However follow with the same 
problem. 

Below I am putting as was the partitions on the SD card. 

Boot:

*vanessa@vanessa-VirtualBox:~$ ls -lsa /media/boot/*
*total 4760*
*   1 drwx-- 2 vanessa vanessa 512 Dez 31  1969 .*
*   4 drwxr-xr-x 7 rootroot   4096 Abr 25 15:46 ..*
*  25 -rw-r--r-- 1 vanessa vanessa   24968 Abr 25 14:59 
am335x-boneblack.dtb*
* 102 -rw-r--r-- 1 vanessa vanessa  103812 Abr 25 14:59 MLO*
* 354 -rw-r--r-- 1 vanessa vanessa  362136 Abr 25 14:59 u-boot.img*
*   1 -rw-r--r-- 1 vanessa vanessa 226 Abr 25 14:59 uEnv.txt*
*4275 -rw-r--r-- 1 vanessa vanessa 4376808 Abr 25 14:59 uImage*
*vanessa@vanessa-VirtualBox:~$ ls -lsa /media/rootfs_/*
*total 84*
* 4 drwxrwxr-x 18 root root  4096 Abr 25 15:24 .*
* 4 drwxr-xr-x  7 root root  4096 Abr 25 15:46 ..*
* 4 drwxrwxr-x  2 root root  4096 Abr 25 14:07 bin*
* 4 drwxr-xr-x  3 root root  4096 Abr 25 14:09 dev*
* 4 drwxr-xr-x  5 root root  4096 Dez 31  1999 etc*
* 4 drwxrwxr-x  4 root root  4096 Abr 25 14:09 home*
* 4 drwxrwxr-x  4 root root  4096 Abr 25 15:28 lib*
* 0 lrwxrwxrwx  1 root root 3 Abr 25 13:59 lib32 -> lib*
* 0 lrwxrwxrwx  1 root root11 Abr 25 14:07 linuxrc -> bin/busybox*
*16 drwx--  2 root root 16384 Abr 25 14:58 lost+found*
* 4 drwxrwxr-x  2 root root  4096 Ago 30  2013 media*
* 4 drwxrwxr-x  2 root root  4096 Ago 30  2013 mnt*
* 4 drwxrwxr-x  2 root root  4096 Ago 30  2013 opt*
* 4 drwxrwxr-x  2 root root  4096 Ago 30  2013 proc*
* 4 drwx--  2 root root  4096 Ago 30  2013 root*
* 0 lrwxrwxrwx  1 root root 3 Ago 30  2013 run -> tmp*
* 4 drwxrwxr-x  2 root root  4096 Abr 25 14:07 sbin*
* 4 drwxrwxr-x  2 root root  4096 Ago 30  2013 sys*
* 4 drwxrwxrwt  3 root root  4096 Dez 31  1999 tmp*
* 4 drwxrwxr-x  7 root root  4096 Abr 25 15:07 usr*
* 4 drwxrwxr-x  4 root root  4096 Abr 25 14:09 var*
*vanessa@vanessa-VirtualBox:~$ ls -lsa /media/rootfs_/lib*
*total 2604*
*   4 drwxrwxr-x  4 root root4096 Abr 25 15:28 .*
*   4 drwxrwxr-x 18 root root4096 Abr 25 15:24 ..*
*   4 drwxrwxr-x  7 root root4096 Abr 25 14:53 firmware*
* 132 -rwxr-xr-x  1 root root  134316 Abr 25 14:07 ld-2.17.so*
*   0 lrwxrwxrwx  1 root root  10 Abr 25 14:01 ld-linux.so.3 -> 
ld-2.17.so*
*1228 -rwxr-xr-x  1 root root 1254532 Abr 25 14:07 libc-2.17.so*
*  40 -rwxr-xr-x  1 root root   38480 Abr 25 14:07 libcrypt-2.17.so*
*   0 lrwxrwxrwx  1 root root  16 Abr 25 14:01 libcrypt.so.1 -> 
libcrypt-2.17.so*
*   0 lrwxrwxrwx  1 root root  12 Abr 25 14:01 libc.so.6 -> 
libc-2.17.so*
*  20 -rwxr-xr-x  1 root root   18008 Abr 25 14:07 libdl-2.17.so*
*   0 lrwxrwxrwx  1 root root  13 Abr 25 14:01 libdl.so.2 -> 
libdl-2.17.so*
* 132 -rwxr-xr-x  1 root root  133660 Abr 25 14:07 libgcc_s.so.1*
* 620 -rwxr-xr-x  1 root root  632404 Abr 25 14:07 libm-2.17.so*
*   0 lrwxrwxrwx  1 root root  12 Abr 25 14:01 libm.so.6 -> 
libm-2.17.so*
*  80 -rwxr-xr-x  1 root root   79808 Abr 25 14:07 libnsl-2.17.so*
*   0 lrwxrwxrwx  1 root root  14 Abr 25 14:01 libnsl.so.1 -> 
libnsl-2.17.so*
*  28 -rwxr-xr-x  1 root root   26224 Abr 25 14:07 libnss_dns-2.17.so*
*   0 lrwxrwxrwx  1 root root  18 Abr 25 14:01 libnss_dns.so.2 -> 
libnss_dns-2.17.so*
*  52 -rwxr-xr-x  1 root root   51124 Abr 25 14:07 libnss_files-2.17.so*
*   0 lrwxrwxrwx  1 root root  20 Abr 25 14:01 libnss_files.so.2 -> 
libnss_files-2.17.so*
* 128 -rwxr-xr-x  1 root root  127839 Abr 25 14:07 libpthread-2.17.so*
*   0 lrwxrwxrwx  1 root root  18 Abr 25 14:01 libpthread.so.0 -> 
libpthread-2.17.so*
*  84 -rwxr-xr-x  1 root root   83820 Abr 25 14:07 libresolv-2.17.so*
*   0 lrwxrwxrwx  1 root root  17 Abr 25 14:01 libresolv.so.2 -> 
libresolv-2.17.so*
*  28 -rwxr-xr-x  1 root root   26528 Abr 25 14:07 librt-2.17.so*
*   0 lrwxrwxrwx  1 root root  13 Abr 25 14:01 librt.so.1 -> 
librt-2.17.so*
*  16 -rwxr-xr-x  1 root root   13944 Abr 25 14:07 libutil-2.17.so*
*   0 lrwxrwxrwx  1 root root  15 Abr 25 14:01 libutil.so.1 -> 
libutil-2.17.so*
*   4 drwxrwxr-x  3 root root4096 Abr 25 14:52 modules*
*vanessa@vanessa-VirtualBox:~$ ls -lsa /media/rootfs_/lib/modules/*
*total 12*
*4 drwxrwxr-x 3 root root 4096 Abr 25 14:52 .*
*4 drwxrwxr-x 4 root root 4096 Abr 25 15:28 ..*
*4 drwxrwxr-x 3 root root 4096 Abr 25 14:53 3.8.13-00744-gfc59ffd*
*vanessa@vanessa-VirtualBox:~$ ls -lsa 
/media/rootfs_/lib/modules/3.8.13-00744-gfc59ffd/*
*total 1104*
*  4 drwxrwxr-x 3 root root   4096 Abr 25 14:53 .*
*  4 drwxrwxr-x 3 root root   4096 Abr 25 14:52 ..*
*  0 lrwxrwxrwx 1 root root 32 Abr 25 14:52 build -> 
/home/vanessa/pBBB/kernel/kernel*
*  4 drwxrwxr-x 9 root root   4096 Abr 25 14:53 kernel*
*288 -rw-rw-r-- 1 root root 291012 Abr 25 14:53 modules.alias*
*296 -rw-rw-r-- 1 root 

Re: [beagleboard] BeagleBone Black RevB with Debian 2014-04-14 SD image -- networking issues

[Robert P. J. Day]

On Fri, 25 Apr 2014, Gerald Coley wrote:

> It has been tested for robustness. Just not tested for you.
> Gerald

  Test nazi. No testing for *you*.

rday

-- 


Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter:   http://twitter.com/rpjday
LinkedIn:   http://ca.linkedin.com/in/rpjday


-- 
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] BeagleBone Black RevB with Debian 2014-04-14 SD image -- networking issues

[Gerald Coley]

It has been tested for robustness. Just not tested for you.

Gerald



On Fri, Apr 25, 2014 at 11:31 AM, treedeegraphics  wrote:

>
>
> Thanks very much. That is precisely what is happening.  I'll work around
> it for now.  ;-)
>   ((Strange though))
>
> I find depending on the moon phase sometimes on board Ethernet (ETH0)
> works but then USB Ethernet (ETH1) fails and vice-verse.
> Any who, it is what it is!
>
> Has Beagleboard Black been electrically tested yet for robustness?   :-))
>   ((it's a Redundant question, don't answer that))
>
>
>
>
> On Wednesday, 16 April 2014 09:17:20 UTC-4, RobertCNelson wrote:
>
>> On Tue, Apr 15, 2014 at 9:10 PM, treedeegraphics
>>  wrote:
>> > Hi
>> >
>> > I am wondering if anyone has experienced similar issues 
>> >
>> > I have a Beaglebone Black Rev B.
>> >
>> > I have flashed the Debian  2014-04-14  image that is posted onto an SD
>> card
>> > and I boot it up ok,
>> > but I have been having difficulties trying to get various networking to
>> > work.
>> >
>> > 1.  Using the on board ethernet does not work.  It pretends to
>> configure ok
>> > but it does not send packets out.
>> > Using dmesg I see the following issues after issuing an ifup eth0:
>> > [  325.013469] net eth0: initializing cpsw version 1.12 (0)
>> > [  325.016077] libphy: PHY 4a101000.mdio:00 not found
>> > [  325.021246] net eth0: phy 4a101000.mdio:00 not found on slave 0
>> > [  325.027593] libphy: PHY 4a101000.mdio:01 not found
>> > [  325.032737] net eth0: phy 4a101000.mdio:01 not found on slave 1
>> > [  325.046467] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
>> >
>> > This looks like the onboard ethernet PHY is not properly supported in
>> this
>> > image ??
>>
>> http://bugs.elinux.org/issues/67
>>
>> It's an odd situation, seems to only occur on some boards when the
>> microSD's is being used.  As the phy is coming up on the wrong
>> address, however the driver is hardcoded to one address so it never
>> connects up properly.
>>
>> You can confirm this situation by using the 'flasher', and only boot
>> with the eMMC, I don't have a working software fix yet.
>>
>> > 2.  If I try using my EDIMAX (rtl8192cu)  usb WIFI dongle it sort of
>> works
>> > but seems very unstable.
>> > I also tried using a 2A power supply but it seemed worse than powering
>> it
>> > from the computer USB.
>>
>> I have a shoe box full of rtl8192's.. They are crap..
>>
>> > How stable is this Debian  2014-04-14   image and what should be my
>> > expectations at this point for various devices working ?
>> >
>> > Which Ethernet or Wifi works in a stable manner under Debian
>>  2014-04-14  ?
>>
>> Regards,
>>
>> --
>> Robert Nelson
>> http://www.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.
>

-- 
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: HDMI support for chalkboard electronics 10"

[greggschroeder]

What resolution are you wanting to display?  Or I should ask, what 
resolution are you currently viewing it in?


On Thursday, July 25, 2013 4:04:12 PM UTC-7, raps...@gmail.com wrote:
>
>
> So I have plugged in and been able to pull EDID information for the 
> Chalkboard Electronics 10" display.
>
> Screen 0: minimum 320 x 200, current 1280 x 800, maximum 2048 x 2048
> HDMI-0 connected 1280x800+0+0 (0x41) normal (normal left inverted right x 
> axis y axis) 217mm x 136mm
> Identifier: 0x40
> Timestamp:  1798433513
> Subpixel:   unknown
> Gamma:  1.0:1.0:1.0
> Brightness: 1.0
> Clones:
> CRTC:   0
> CRTCs:  0
> Transform:  1.00 0.00 0.00
> 0.00 1.00 0.00
> 0.00 0.00 1.00
>filter: 
> EDID:
> 000030e44503
> 0015010490160e7802e887965a559528
> 2251550001010101010101010101
> 0101010101014c1d00ec502018304030
> 5700d988001b1612008050201630
> 30204700d988001b00fe0043
> 3347524e803130315758310a
> 4132a801010a2020009a
>   1280x800 (0x41)   75.0MHz +HSync -VSync *current +preferred
> h: width  1280 start 1344 end 1392 total 1516 skew0 clock   
> 49.5KHz
> v: height  800 start  805 end  812 total  824   clock   
> 60.0Hz
>   1280x800 (0x42)   46.3MHz +HSync -VSync
> h: width  1280 start 1328 end 1360 total 1408 skew0 clock   
> 32.9KHz
> v: height  800 start  804 end  811 total  822   clock   
> 40.0Hz
>
>
> Also from /sys/class/drm/card0/card0-HDMI-A-1/edid
>
> parse-edid: parse-edid version 2.0.0
> parse-edid: EDID checksum passed.
>
> # EDID version 1 revision 4
> Section "Monitor"
> # Block type: 2:0 3:fe
> # Block type: 2:0 3:0
> Identifier "LGD:4503"
> VendorName "LGD"
> ModelName "LGD:4503"
> # Block type: 2:0 3:fe
> # Block type: 2:0 3:0
> # DPMS capabilities: Active off:no  Suspend:no  Standby:no
>
> Mode "1280x800"# vfreq 60.039Hz, hfreq 49.472kHz
> DotClock75.00
> HTimings1280 1344 1392 1516
> VTimings800 805 812 824
> Flags"-HSync" "+VSync"
> EndMode
> Mode "1280x800"# vfreq 40.004Hz, hfreq 32.884kHz
> DotClock46.30
> HTimings1280 1328 1360 1408
> VTimings800 804 811 822
> Flags"-HSync" "+VSync"
> EndMode
> # Block type: 2:0 3:fe
> # Block type: 2:0 3:0
> EndSection
>
> The LCD only supports one resolution and it isn't in the support 
> resolution list. Could I have this support added to the DRM driver?
>
> Also from the kernel logs I am getting:
> [ 3351.400053] [drm:drm_ioctl], pid=254, cmd=0xc01864b1, nr=0xb1, dev 
> 0xe200, auth=1
> [ 3351.400356] [drm:drm_ioctl], ret = -38
> [ 3361.221450] [drm:output_poll_execute], [CONNECTOR:5:HDMI-A-1] status 
> updated from 1 to 1
> [ 3371.252258] [drm:output_poll_execute], [CONNECTOR:5:HDMI-A-1] status 
> updated from 1 to 1
> [ 3381.283534] [drm:output_poll_execute], [CONNECTOR:5:HDMI-A-1] status 
> updated from 1 to 1
> [ 3391.314771] [drm:output_poll_execute], [CONNECTOR:5:HDMI-A-1] status 
> updated from 1 to 1
> [ 3401.346046] [drm:output_poll_execute], [CONNECTOR:5:HDMI-A-1] status 
> updated from 1 to 1
>
> repeated.

-- 
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: Cape Device Tree Overlay fails to load during boot?

[William Hermans]

I think sudo -S  might work too, but have not tested this myself
yet.


On Fri, Apr 25, 2014 at 4:51 AM, Charles Steinkuehler <
char...@steinkuehler.net> wrote:

> On 4/25/2014 5:37 AM, Andreas Tauböck wrote:
> >
> > and I get a permission denied when i want to add it manually with:
> >
> > ubuntu@arm:/sys/devices/bone_capemgr.9$ sudo echo TT3201:001 >slots
> > -bash: slots: Permission denied
>
> The redirect happens before the sudo, try:
>
> sudo su -c "echo TT3201:001 > slots"
>
> --
> Charles Steinkuehler
> char...@steinkuehler.net
>
> --
> 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: I would like to execute a program automatically,when power supply at ON.

[William Hermans]

NOTE this method knows nothing about when your board has power applied.
This service*will* however start every time Debian is booted up. Even from
a soft boot / restart.


On Fri, Apr 25, 2014 at 10:02 AM, William Hermans  wrote:

> If you're using Debian Wheezy, the instructions below are taken from my
> blog and work. More information here:
> https://wiki.debian.org/LSBInitScripts
>
> Create some file, and edit it accordingly. In my case *test*
>  *touch /etc/init.d/test && nano /etc/init.d/test *
>
> And in the file we put . . .
>  *#! /bin/sh *
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> *### BEGIN INIT INFO # Provides: test # Required-Start: $all #
> Required-Stop: $all # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 #
> Short-Description: Short script description # Description: Longer script
> description. ### END INIT INFO case “$1″ in start) /sbin/route add default
> gw 192.168.0.1 dev eth0 /usr/sbin/ntpdate pool.ntp.org
>  ;; stop) #no-op ;; *) #no-op ;; esac*
>
> *exit 0 *
>
> Then we must make the file executable, so we issue the command:
>  *chmod +x /etc/init.d/test *
>
> Followed by the new method of installing the service. Do note the first
> command tests the file, and the second command actually installs the file
> as a service.
>
> *insserv -n /etc/init.d/test insserv /etc/init.d/test *
>
>
>
> On Thu, Apr 24, 2014 at 11:05 PM, Uonsong Ly wrote:
>
>> Hello Anthony, it looks like that this method only works if I boot up and
>> ssh to the BBB OS. Do you know of a method that would allow a program to
>> execute once there is power through the BBB (with 5V port not the USB)?
>>
>> I have been trying to figure this out for a while now. I would really
>> appreciate it if you can provide me with some suggestions on this matter.
>> Thanks in advance,
>>
>> Uonsong
>>
>> On Thursday, April 24, 2014 6:01:36 AM UTC-6, cove...@gmail.com wrote:
>>>
>>> Hi,
>>>
>>> You can put myScript.sh into the /etc/profile.d directory and your
>>> script will be executed on startup.
>>>
>>> Obviously there's several ways to do this, but that's cheap and cheerful.
>>>
>>> Regards,
>>>
>>> Anthony
>>>
>>>
>>>
>>> On Thursday, 24 April 2014 07:07:32 UTC+1, kenji maehara wrote:

 Hi,

 I made TCP client program for Beaglebone Black on Angstrom Linux.
 I would like to execute a program automatically,when power supply at ON
 for connection to server.



 I put the execute file here.
 /home/a.out


 I made a file called myScript.sh on this pass.
  /etc/init.d/myScript.sh

 It is contents of file myScript.sh
 #!/bin/bash
 /home/a.out


 I executed the following command for file myScript.sh.
  chmod u=+rwx myScript.sh


 Next, in /etc/rc5.d folder、I executed the command.
  ln -s ../init.d/myScript.sh S99myScript


 I thought that it can start in this automatically,

  but I can't.


 I refer to these contents.
 https://groups.google.com/forum/#!topic/beagleboard/6GmHGPgnY84


 Would you tell me any your advice thing or solution?


 thanks.



  --
>> 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: I would like to execute a program automatically,when power supply at ON.

[William Hermans]

If you're using Debian Wheezy, the instructions below are taken from my
blog and work. More information here: https://wiki.debian.org/LSBInitScripts

Create some file, and edit it accordingly. In my case *test*
 *touch /etc/init.d/test && nano /etc/init.d/test *

And in the file we put . . .
 *#! /bin/sh *





















*### BEGIN INIT INFO # Provides: test # Required-Start: $all #
Required-Stop: $all # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 #
Short-Description: Short script description # Description: Longer script
description. ### END INIT INFO case “$1″ in start) /sbin/route add default
gw 192.168.0.1 dev eth0 /usr/sbin/ntpdate pool.ntp.org
 ;; stop) #no-op ;; *) #no-op ;; esac*

*exit 0 *

Then we must make the file executable, so we issue the command:
 *chmod +x /etc/init.d/test *

Followed by the new method of installing the service. Do note the first
command tests the file, and the second command actually installs the file
as a service.

*insserv -n /etc/init.d/test insserv /etc/init.d/test *



On Thu, Apr 24, 2014 at 11:05 PM, Uonsong Ly  wrote:

> Hello Anthony, it looks like that this method only works if I boot up and
> ssh to the BBB OS. Do you know of a method that would allow a program to
> execute once there is power through the BBB (with 5V port not the USB)?
>
> I have been trying to figure this out for a while now. I would really
> appreciate it if you can provide me with some suggestions on this matter.
> Thanks in advance,
>
> Uonsong
>
> On Thursday, April 24, 2014 6:01:36 AM UTC-6, cove...@gmail.com wrote:
>>
>> Hi,
>>
>> You can put myScript.sh into the /etc/profile.d directory and your script
>> will be executed on startup.
>>
>> Obviously there's several ways to do this, but that's cheap and cheerful.
>>
>> Regards,
>>
>> Anthony
>>
>>
>>
>> On Thursday, 24 April 2014 07:07:32 UTC+1, kenji maehara wrote:
>>>
>>> Hi,
>>>
>>> I made TCP client program for Beaglebone Black on Angstrom Linux.
>>> I would like to execute a program automatically,when power supply at ON
>>> for connection to server.
>>>
>>>
>>>
>>> I put the execute file here.
>>> /home/a.out
>>>
>>>
>>> I made a file called myScript.sh on this pass.
>>> /etc/init.d/myScript.sh
>>>
>>> It is contents of file myScript.sh
>>> #!/bin/bash
>>> /home/a.out
>>>
>>>
>>> I executed the following command for file myScript.sh.
>>> chmod u=+rwx myScript.sh
>>>
>>>
>>> Next, in /etc/rc5.d folder、I executed the command.
>>> ln -s ../init.d/myScript.sh S99myScript
>>>
>>>
>>> I thought that it can start in this automatically,
>>>
>>>  but I can't.
>>>
>>>
>>> I refer to these contents.
>>> https://groups.google.com/forum/#!topic/beagleboard/6GmHGPgnY84
>>>
>>>
>>> Would you tell me any your advice thing or solution?
>>>
>>>
>>> thanks.
>>>
>>>
>>>
>>>  --
> 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] Re: i2c help needed

[treedeegraphics]

Thanks.  I'm not sure what strangeness was going on but then it started 
working.  ;-)



On Friday, 25 April 2014 10:56:34 UTC-4, Akhil wrote:
>
> Try with just the i2c bus number or without the /dev/ like:
> i2cdetect -F 0
> i2cdetect -F i2c-0
>
> On Friday, April 25, 2014 6:38:10 AM UTC+2, treedeegraphics wrote:
>>
>> Hi:
>>
>> I have a custom i2c device  (one that looks like memory, you can do reads 
>> and writes to it) connected to my BeagleBone Black.
>>
>> According to the online docs, I have the device connected to:  i2c2: 
>> 0x4819_C000
>>
>> However when I do an i2cdetect -l  I only see:
>> # i2cdetect -l
>> i2c-0   i2c OMAP I2C adapterI2C 
>> adapter
>> i2c-1   i2c OMAP I2C adapterI2C 
>> adapter
>>
>> # i2cdetect -F /dev/i2c-1
>> Error: I2C bus name doesn't match any bus present!
>>
>> # i2cdetect -F /dev/i2c-0
>> Error: I2C bus name doesn't match any bus present!
>>
>> I don't see to be able to see anything on any i2c buses in the system.
>> The hardware seems to be correctly connected.
>>
>> Is there some configuration thing I need to do to get i2c working 
>> properly on my BeagleBone Black ?
>>
>> I am using the Debian image on my uSD card to boot:  
>>   bone-debian-7.4-2014-03-27-2gb.img.xz   (Wheezy stable)
>>   (KERNEL: BeagleBone/BeagleBone Black: v3.8.13-bone47 kernel)
>>
>> I seem to be befuddled as I think some junk should show up on i2cdetect 
>> or i2cdump but I get nothing.
>> Help ? Ideas ?
>>
>> Thanks in Advanced.
>>
>>
>>

-- 
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] BeagleBone Black RevB with Debian 2014-04-14 SD image -- networking issues

[treedeegraphics]

Thanks very much. That is precisely what is happening.  I'll work around it 
for now.  ;-)
  ((Strange though))

I find depending on the moon phase sometimes on board Ethernet (ETH0) works 
but then USB Ethernet (ETH1) fails and vice-verse.
Any who, it is what it is!

Has Beagleboard Black been electrically tested yet for robustness?   :-))
  ((it's a Redundant question, don't answer that))



On Wednesday, 16 April 2014 09:17:20 UTC-4, RobertCNelson wrote:
>
> On Tue, Apr 15, 2014 at 9:10 PM, treedeegraphics 
> > wrote: 
> > Hi 
> > 
> > I am wondering if anyone has experienced similar issues  
> > 
> > I have a Beaglebone Black Rev B. 
> > 
> > I have flashed the Debian  2014-04-14  image that is posted onto an SD 
> card 
> > and I boot it up ok, 
> > but I have been having difficulties trying to get various networking to 
> > work. 
> > 
> > 1.  Using the on board ethernet does not work.  It pretends to configure 
> ok 
> > but it does not send packets out. 
> > Using dmesg I see the following issues after issuing an ifup eth0: 
> > [  325.013469] net eth0: initializing cpsw version 1.12 (0) 
> > [  325.016077] libphy: PHY 4a101000.mdio:00 not found 
> > [  325.021246] net eth0: phy 4a101000.mdio:00 not found on slave 0 
> > [  325.027593] libphy: PHY 4a101000.mdio:01 not found 
> > [  325.032737] net eth0: phy 4a101000.mdio:01 not found on slave 1 
> > [  325.046467] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready 
> > 
> > This looks like the onboard ethernet PHY is not properly supported in 
> this 
> > image ?? 
>
> http://bugs.elinux.org/issues/67 
>
> It's an odd situation, seems to only occur on some boards when the 
> microSD's is being used.  As the phy is coming up on the wrong 
> address, however the driver is hardcoded to one address so it never 
> connects up properly. 
>
> You can confirm this situation by using the 'flasher', and only boot 
> with the eMMC, I don't have a working software fix yet. 
>
> > 2.  If I try using my EDIMAX (rtl8192cu)  usb WIFI dongle it sort of 
> works 
> > but seems very unstable. 
> > I also tried using a 2A power supply but it seemed worse than powering 
> it 
> > from the computer USB. 
>
> I have a shoe box full of rtl8192's.. They are crap.. 
>
> > How stable is this Debian  2014-04-14   image and what should be my 
> > expectations at this point for various devices working ? 
> > 
> > Which Ethernet or Wifi works in a stable manner under Debian  2014-04-14 
>  ? 
>
> Regards, 
>
> -- 
> Robert Nelson 
> http://www.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: Here is the BeagleBone Debian (beta) image you want to test

[vitor de miranda henrique]

Hello Everyone,

I'm having problems with the latest debian build (2014-04-23) and the WIFI 
dongle Edimax EW-7811Un.

I follow this link 
(https://groups.google.com/forum/#!topic/beaglebone/Q92uD9F1us8) to set up 
the dongle, can connect to wifi, but the connection is faulty, works for 
couple of minutes and than just stops.

Raspiberry Pi works great with the same adapter, where can i find a better 
drive for this dongle? what is the best dongle to use with this Debian 
images?

Thank you,

Vitor Henrique


-- 
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: BBB can't shutdown

[deepak karki]

sudo shutdown 0

On Wednesday, 23 April 2014 19:18:57 UTC+5:30, kie42...@gmail.com wrote:
>
> My BBB can't shutdown. What can I do ?
>

-- 
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] LEDscape and adafruit NEOpixel LEDs on BBB

[Ian Woloschin]

Sorry, one minor correction.

The dtb file should be in one of the following places:

/boot
/boot/uboot/dtbs

If you're using the latest Debian image then it's the second.  I believe 
Angstrom uses the first.  It looks like the Yona-Appletree LEDscape readme 
has been just been updated to reflect this.

-Ian

On Friday, April 25, 2014 11:12:10 AM UTC-4, Ian Woloschin wrote:
>
> I've been using a LEDscape fork that I think will better allow me to use 
> Python to write the bulk of my program, and then LEDscape to do the 
> Neopixel control.
>
> https://github.com/Yona-Appletree/LEDscape
>
> Everything works, except that you should check the uEnv.txt file in /boot 
> or possible /boot/uboot to make sure you've put the *.dtb file in the 
> correct place to be read.  Different distros do different things, so it's 
> hard to say exactly what you're looking for here.
>
> Unfortunately, USPS is late, so I won't have my Neopixel Stick before I 
> leave this evening, so I won't be putting any time into this over the 
> weekend, but I do expect to pick this back up early next week.
>
> -Ian
>
> On Friday, April 25, 2014 8:07:55 AM UTC-4, Yoder, Mark A wrote:
>>
>>  Ian:
>>  What instructions were you following?
>>
>>  --Mark
>>
>> Sent from my iPad
>>
>> On Apr 25, 2014, at 7:21 AM, "Ian Woloschin"  wrote:
>>
>>   I'm an idiot.  I blindly followed instructions that were likely for 
>> Angstrom, and put the dtb file in the wrong place, /boot instead of 
>> /boot/uboot/dtbs.  Now that the dtb file is being read I've got everything 
>> showing up properly, which is great because I've got my first NeoPixel 
>> stick arriving in the mail today.  Unfortunately I'll be out of town this 
>> weekend, but I've got a 4 hour train ride back Monday morning so I may try 
>> to get some stuff working on the train. 
>>  
>> On Friday, April 25, 2014 7:05:58 AM UTC-4, Ian Woloschin wrote: 
>>>
>>> I'm looking into the same thing and running into the same problems of no 
>>> simple tutorials.  At this point I'm having issues getting the PRU to even 
>>> be enabled, and I'm not really sure why.
>>>
>>> On Tuesday, April 22, 2014 12:59:09 PM UTC-4, Mark A. Yoder wrote: 

 David: 
   Thanks for the pointer, however I had already Google'd around and 
 picked the LEDscape as the most promising. Since I haven't uncovered any 
 'getting started' guides for it I guess I'll just dive in a figure it out 
 for myself.

  --Mark

 On Monday, April 21, 2014 1:48:15 PM UTC-4, dwfunk4475 wrote: 
>
> http://lmgtfy.com/?q=beaglebone+black+ws2812
>
>  
>  Plenty of tutorials . . .  adapt to whatever pin(s) you wish to use 
> on our BBB
>
>  
>  
>  
>  -david
>
>
> On Mon, Apr 21, 2014 at 11:00 AM, Mark A. Yoder 
> wrote:
>
>> Hi Beagle'ers: 
>>   I have a string adafruit NEOpixel LEDs[1] that I want to drive with 
>> the BBB.  LEDscape[2] looks like a good way to drive the LEDs via the 
>> PRUs.
>>
>>  I'm not sure how to get started.  Has anyone used this software to 
>> drive the LEDs?  What should I wire where?
>>
>>  --Mark
>>
>>  [1] http://www.adafruit.com/products/1376 
>> [2] https://github.com/osresearch/LEDscape 
>>  
>
>  
>  
> -- 
>> 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/WvwfBq26kEk/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> beagleboard...@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] LEDscape and adafruit NEOpixel LEDs on BBB

[Ian Woloschin]

I've been using a LEDscape fork that I think will better allow me to use 
Python to write the bulk of my program, and then LEDscape to do the 
Neopixel control.

https://github.com/Yona-Appletree/LEDscape

Everything works, except that you should check the uEnv.txt file in /boot 
or possible /boot/uboot to make sure you've put the *.dtb file in the 
correct place to be read.  Different distros do different things, so it's 
hard to say exactly what you're looking for here.

Unfortunately, USPS is late, so I won't have my Neopixel Stick before I 
leave this evening, so I won't be putting any time into this over the 
weekend, but I do expect to pick this back up early next week.

-Ian

On Friday, April 25, 2014 8:07:55 AM UTC-4, Yoder, Mark A wrote:
>
>  Ian:
>  What instructions were you following?
>
>  --Mark
>
> Sent from my iPad
>
> On Apr 25, 2014, at 7:21 AM, "Ian Woloschin" 
> > 
> wrote:
>
>   I'm an idiot.  I blindly followed instructions that were likely for 
> Angstrom, and put the dtb file in the wrong place, /boot instead of 
> /boot/uboot/dtbs.  Now that the dtb file is being read I've got everything 
> showing up properly, which is great because I've got my first NeoPixel 
> stick arriving in the mail today.  Unfortunately I'll be out of town this 
> weekend, but I've got a 4 hour train ride back Monday morning so I may try 
> to get some stuff working on the train. 
>  
> On Friday, April 25, 2014 7:05:58 AM UTC-4, Ian Woloschin wrote: 
>>
>> I'm looking into the same thing and running into the same problems of no 
>> simple tutorials.  At this point I'm having issues getting the PRU to even 
>> be enabled, and I'm not really sure why.
>>
>> On Tuesday, April 22, 2014 12:59:09 PM UTC-4, Mark A. Yoder wrote: 
>>>
>>> David: 
>>>   Thanks for the pointer, however I had already Google'd around and 
>>> picked the LEDscape as the most promising. Since I haven't uncovered any 
>>> 'getting started' guides for it I guess I'll just dive in a figure it out 
>>> for myself.
>>>
>>>  --Mark
>>>
>>> On Monday, April 21, 2014 1:48:15 PM UTC-4, dwfunk4475 wrote: 

 http://lmgtfy.com/?q=beaglebone+black+ws2812

  
  Plenty of tutorials . . .  adapt to whatever pin(s) you wish to use 
 on our BBB

  
  
  
  -david


 On Mon, Apr 21, 2014 at 11:00 AM, Mark A. Yoder wrote:

> Hi Beagle'ers: 
>   I have a string adafruit NEOpixel LEDs[1] that I want to drive with 
> the BBB.  LEDscape[2] looks like a good way to drive the LEDs via the 
> PRUs.
>
>  I'm not sure how to get started.  Has anyone used this software to 
> drive the LEDs?  What should I wire where?
>
>  --Mark
>
>  [1] http://www.adafruit.com/products/1376 
> [2] https://github.com/osresearch/LEDscape 
>  

  
  
 -- 
> 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/WvwfBq26kEk/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> beagleboard...@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] Re: i2c help needed

[Akhil]

Try with just the i2c bus number or without the /dev/ like:
i2cdetect -F 0
i2cdetect -F i2c-0

On Friday, April 25, 2014 6:38:10 AM UTC+2, treedeegraphics wrote:
>
> Hi:
>
> I have a custom i2c device  (one that looks like memory, you can do reads 
> and writes to it) connected to my BeagleBone Black.
>
> According to the online docs, I have the device connected to:  i2c2: 
> 0x4819_C000
>
> However when I do an i2cdetect -l  I only see:
> # i2cdetect -l
> i2c-0   i2c OMAP I2C adapterI2C adapter
> i2c-1   i2c OMAP I2C adapterI2C adapter
>
> # i2cdetect -F /dev/i2c-1
> Error: I2C bus name doesn't match any bus present!
>
> # i2cdetect -F /dev/i2c-0
> Error: I2C bus name doesn't match any bus present!
>
> I don't see to be able to see anything on any i2c buses in the system.
> The hardware seems to be correctly connected.
>
> Is there some configuration thing I need to do to get i2c working properly 
> on my BeagleBone Black ?
>
> I am using the Debian image on my uSD card to boot:  
>   bone-debian-7.4-2014-03-27-2gb.img.xz   (Wheezy stable)
>   (KERNEL: BeagleBone/BeagleBone Black: v3.8.13-bone47 kernel)
>
> I seem to be befuddled as I think some junk should show up on i2cdetect or 
> i2cdump but I get nothing.
> Help ? Ideas ?
>
> Thanks in Advanced.
>
>
>

-- 
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] BBB can't shutdown

[William Pretty Security]

Tell us what you did (exactly)

 

http://www.packtpub.com/building-a-home-security-system-with-beaglebone/book

 

From: beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com] On 
Behalf Of kie4280...@gmail.com
Sent: Friday, April 25, 2014 9:44 AM
To: beagleboard@googlegroups.com
Subject: Re: [beagleboard] BBB can't shutdown

 

Still didn't work !

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



No virus found in this message.
Checked by AVG - www.avg.com
Version: 2014.0.4570 / Virus Database: 3920/7393 - Release Date: 04/25/14

-- 
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] Device Overlay to Switch off USR0-3 LEDS

[Cody Lacey]

Try labeling them exactly as they are labled here
https://github.com/beagleboard/linux/blob/3.8/arch/arm/boot/dts/am335x-bone-common.dtsi#L63-L95

  gpio-leds {
compatible = "gpio-leds";
pinctrl-names = "default";
pinctrl-0 = <&userled_pins>;

led0 {
label = "beaglebone:green:usr0";
gpios = <&gpio2 21 0>;
linux,default-trigger = "heartbeat";
default-state = "off";
};

led1 {
label = "beaglebone:green:usr1";
gpios = <&gpio2 22 0>;
linux,default-trigger = "mmc0";
default-state = "off";
};

led2 {
label = "beaglebone:green:usr2";
gpios = <&gpio2 23 0>;
linux,default-trigger = "cpu0";
default-state = "off";
};

led3 {
label = "beaglebone:green:usr3";
gpios = <&gpio2 24 0>;
default-state = "off";
linux,default-trigger = "mmc1";
};
};



On Fri, Apr 25, 2014 at 7:12 AM,  wrote:

> Hi Forum,
>
> I am attempting to create a device overaly to turn off the USR0-3 on
> Ubuntu 13.10 (Linux ubuntu-armhf 3.8.13-bone30)  on my Beagle Bone Black
> A5C.
>
> I have performed the following process - but the USR0-3 LEDs continue to
> flash.  I expected all of them to turn off and have trigger state of
> "[none]"
>
> The DTS (BBB-LEDS-00A0.dts) file I have created is as follows
>
> /dts-v1/;
> /plugin/;
> /
> {
>  compatible = "ti,beaglebone", "ti,beaglebone-black";
>  part-number = "BBB-LEDS-00A0";
>  version = "00A0";
>  fragment@0
>   {
>  target = <&ocp>;
>  __overlay__
>  {
>  gpio-leds {
>  compatible = "gpio-leds";
>  pinctrl-names = "default";
>  pinctrl-0 = <&userled_pins>;
>  led0 {
>  label = "beaglebone:green:usr0";
>  gpios = <&gpio2 0x15 0x0>;
>  linux,default-trigger = "none";
>  default-state = "off";
>  };
>  led1 {
>  label = "beaglebone:green:usr0";
>  gpios = <&gpio2 0x16 0x0>;
>  linux,default-trigger = "none";
>  default-state = "off";
>  };
>  led2 {
>  label = "beaglebone:green:usr0";
>  gpios = <&gpio2 0x17 0x0>;
>  linux,default-trigger = "none";
>  default-state = "off";
>  };
>  led3 {
>  label = "beaglebone:green:usr0";
>  gpios = <&gpio2 0x18 0x0>;
>  linux,default-trigger = "none";
>  default-state = "off";
>  };
>  };
>  };
>};
> };
>
> I have the latest dtc with the patches from Robert Nelson ( wget -c
> https://raw.github.com/RobertCNelson/tools/master/pkgs/dtc.sh)
>
> I compile the DTS file using
>
> dtc -O dtb -o BBB-LEDS-00A0.dtbo -b 0 -@ BBB-LEDS-00A0.dts
> Copy the generated dtbo file to /lib/firmware
>
> sudo cp BBB-LEDS-00A0.dtbo /lib/firmware/
> Load the device tree overlay using
>
> sudo sh -c "echo BBB-LEDS > /sys/devices/bone_capemgr.9/slots"
> I see the slots that the "cape" is loaded
> 0: 54:PF---
>  1: 55:PF---
>  2: 56:PF---
>  3: 57:PF---
>  4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G
>  5: ff:P-O-L Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI
>  8: ff:P-O-L Override Board Name,00A0,Override Manuf,BBB-LEDS
> From dmesg all seems okay as well
> [20729.329645] bone-capemgr bone_capemgr.9: part_number 'BBB-LEDS',
> version 'N/A'
> [20729.329832] bone-capemgr bone_capemgr.9: slot #8: generic override
> [20729.329882] bone-capemgr bone_capemgr.9: bone: Using override eeprom
> data at slot 8
> [20729.329933] bone-capemgr bone_capemgr.9: slot #8: 'Override Board
> Name,00A0,Override Manuf,BBB-LEDS'
> [20729.330218] bone-capemgr bone_capemgr.9: slot #8: Requesting part
> number/version based 'BBB-LEDS-00A0.dtbo
> [20729.330273] bone-capemgr bone_capemgr.9: slot #8: Requesting firmware
> 'BBB-LEDS-00A0.dtbo' for board-name 'Override Board Name', version '00A0'
> [20729.333640] bone-capemgr bone_capemgr.9: slot #8: dtbo
> 'BBB-LEDS-00A0.dtbo' loaded; converting to live tree
> [20729.334146] bone-capemgr bone_capemgr.9: slot #8: #1 overlays
> [20729.334750] bone-capemgr bone_capemgr.9: slot #8: Applied #1 overlays.
> Could someone point me as towards what I h

Re: [beagleboard] Re: Wrong execution time

[Cody Lacey]

You may also want to post this to the TI e2e forum.


On Fri, Apr 25, 2014 at 5:16 AM,  wrote:

> Hi,
>
> I have a similar problem with my Beaglebone and Starterware. To check out
> the performance of Starterware and Beaglebone I do the following in my
> main-Function:
>
> while(1)
> {
>GPIOPinWrite(GPIO_INSTANCE_ADDRESS,28, GPIO_PIN_HIGH);
>
> *   for*(i=0; i<35000; i++)
>{
>x = *sqrt*(3.141592654);
>}
>
> *   GPIOPinWrite*(GPIO_INSTANCE_ADDRESS, 28, GPIO_PIN_LOW);
>
> *   for*(i=0; i<35000; i++)
>{
>x = *sqrt*(3.141592654);
>}
> }
>
> As you can see I toggle a pin and in between I do sqrt(pi) 35000 times.
> Using an oscilloscope I measure the period /frequency on that pin.
>
> At first I got: T = 18 s 
>
> Then I found this post and  enabled Cache and MMU like in the example:
>  \\StarterWare\examples\evmskAM335x\uart_edma\uartEcho_edma.c
>
> After that i measured: T = 500 ms  / f = 2 Hz
>
> This is still quite slow! I run a program with the same functionality
> using the Linux Distribution Angström on the beaglebone, there I measured a
> period of T = 1.1 ms  / f = 1 kHz .
>
> So what is going on with the Starterware being so slow? Do I have to
> enable the Cache / MMU differently or can't I go faster with Starterware???
> I read a few posts so far where people wrote that they solved this speed
> problem by enabling the cache and mmu but it still is fu* slow : ) why
> ??? help me 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.
>

-- 
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: Disable BB-BONELT-HDMI using uEnv

[Cody Lacey]

Try this, the capemgr= may be causing a problem

optargs=quiet capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN



On Fri, Apr 25, 2014 at 7:58 AM, Tristan Phillips
wrote:

> Interestingly this issue seems to have disappeared in the latest build of
> ubuntu for BBB.  Happy days.
>
>
> On Friday, 25 April 2014 12:21:14 UTC+1, Tristan Phillips wrote:
>>
>> I'm rather confused.  I cannot seem to disable BB-BONELT-HDMI using the
>> uEnv capemgr.disable_partno optargs arg.
>>
>> My uEnv.txt line looks like this: optargs=capemgr=capemgr.
>> disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN
>>
>> but:
>>
>> root@StockBBB:~#* cat /sys/devices/bone_capemgr.9/slots*
>>
>>  1: 55:PF---
>>
>>  2: 56:PF---
>>
>>  3: 57:PF---
>>
>>  4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G
>>
>>  5: ff:P-O-*L* Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI
>>
>> Yet I can see the uEnv was read:
>>
>> root@StockBBB:~# *cat /proc/cmdline *
>>
>> console=ttyO0,115200n8
>> *capemgr=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN*root=UUID=458951f9-fd96-459c-b1a3-6f2300e0fa58
>> ro rootfstype=ext4 rootwait fixrtc ip=
>>
>> Does anybody have any ideas?
>>
>> As a side question, the firmware for things like the BB-BONE-AUD-01 are
>> apparently compiled into the kernel now.  How could I force the dtbo to be
>> loaded from a file?
>>
>> Thanks in advance for any help.
>>
>> Tris
>>
>  --
> 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] BBB can't shutdown

[kie4280ann]

Still didn't work !

-- 
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: Disable BB-BONELT-HDMI using uEnv

[Tristan Phillips]

Interestingly this issue seems to have disappeared in the latest build of 
ubuntu for BBB.  Happy days.

On Friday, 25 April 2014 12:21:14 UTC+1, Tristan Phillips wrote:
>
> I'm rather confused.  I cannot seem to disable BB-BONELT-HDMI using the 
> uEnv capemgr.disable_partno optargs arg.
>
> My uEnv.txt line looks like this: 
> optargs=capemgr=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN
>
> but:
>
> root@StockBBB:~#* cat /sys/devices/bone_capemgr.9/slots*
>
>  1: 55:PF---
>
>  2: 56:PF--- 
>
>  3: 57:PF--- 
>
>  4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G
>
>  5: ff:P-O-*L* Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI
>
> Yet I can see the uEnv was read:
>
> root@StockBBB:~# *cat /proc/cmdline *
>
> console=ttyO0,115200n8 
> *capemgr=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN*root=UUID=458951f9-fd96-459c-b1a3-6f2300e0fa58
>  ro rootfstype=ext4 rootwait 
> fixrtc ip=
>
> Does anybody have any ideas?
>
> As a side question, the firmware for things like the BB-BONE-AUD-01 are 
> apparently compiled into the kernel now.  How could I force the dtbo to be 
> loaded from a file?
>
> Thanks in advance for any help.
>
> Tris
>

-- 
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] Starterware slower than Linux

[Charles Steinkuehler]

On 4/25/2014 4:52 AM, thomas5...@gmx.de wrote:
> So I also integrated the functions MMUConfigEnable() and 
> CacheEnable(CACHE_ALL) into my program. It kind of worked, my new results 
> for Starterware:
> 
> T = 500 ms
>  
> But still !!! 500 times slower than on Linux.
>  
>  
> Did anyone make similar experiences or do you have a clue what could be 
> wrong with Starterware? In the past i only did programming on simple 
> Microcontrollers, so I don't really know how to handle all this cache and 
> MMU stuff.

Is the starterware tool chain using the FPU?

-- 
Charles Steinkuehler
char...@steinkuehler.net

-- 
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] Starterware slower than Linux

[thomas5288]

Hi there,
 
I am testing the performance of the beaglebone in combination with the 
no-OS Starterware from TexasInstruments and with the Linux Distribution 
Angström. 
 
My test program, which I wrote for both for Starterware and Linux, does the 
following: I configure GPIO_1_28 as an output pin and in an endless loop I 
do...
1. set the pin HIGH
2. for(i=0; i<35000; i++)
   { x = sqrt(3.141592654); }
3. set the pin LOW
4. for(i=0; i<35000; i++)
   { x = sqrt(3.141592654); }
 
Then I used  an oscilloscope top measure the period time / frequency of the 
output. My first results:
 
using Linux, the period is  T = 1,1 ms  (with a Jitter of about 
70 us)
using Starterware, the period is T = 18 s  
 
Wondering why Starterware is so amazing slow, I started googling and found 
the following post in a TI forum: 
http://e2e.ti.com/support/embedded/starterware/f/790/t/208033.aspx
The guys on that forum manged to speed up Starterware by enabling Cache and 
MMU like in the example \\StarterWare\examples\evmskAM335x\uart\uartEcho.c 
So I also integrated the functions MMUConfigEnable() and 
CacheEnable(CACHE_ALL) into my program. It kind of worked, my new results 
for Starterware:

T = 500 ms
 
But still !!! 500 times slower than on Linux.
 
 
Did anyone make similar experiences or do you have a clue what could be 
wrong with Starterware? In the past i only did programming on simple 
Microcontrollers, so I don't really know how to handle all this cache and 
MMU stuff.

-- 
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: Wrong execution time

[thomas5288]

Hi,

I have a similar problem with my Beaglebone and Starterware. To check out 
the performance of Starterware and Beaglebone I do the following in my 
main-Function:

while(1)
{
   GPIOPinWrite(GPIO_INSTANCE_ADDRESS,28, GPIO_PIN_HIGH);

*   for*(i=0; i<35000; i++)
   {
   x = *sqrt*(3.141592654);
   }

*   GPIOPinWrite*(GPIO_INSTANCE_ADDRESS, 28, GPIO_PIN_LOW);

*   for*(i=0; i<35000; i++)
   {
   x = *sqrt*(3.141592654);
   }
}

As you can see I toggle a pin and in between I do sqrt(pi) 35000 times. 
Using an oscilloscope I measure the period /frequency on that pin.

At first I got: T = 18 s 

Then I found this post and  enabled Cache and MMU like in the example: 
 \\StarterWare\examples\evmskAM335x\uart_edma\uartEcho_edma.c 

After that i measured: T = 500 ms  / f = 2 Hz

This is still quite slow! I run a program with the same functionality using 
the Linux Distribution Angström on the beaglebone, there I measured a 
period of T = 1.1 ms  / f = 1 kHz .

So what is going on with the Starterware being so slow? Do I have to enable 
the Cache / MMU differently or can't I go faster with Starterware??? I read 
a few posts so far where people wrote that they solved this speed problem 
by enabling the cache and mmu but it still is fu* slow : ) why ??? help 
me 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] LEDscape and adafruit NEOpixel LEDs on BBB

[Yoder, Mark A]

Ian:
 What instructions were you following?

--Mark

Sent from my iPad

On Apr 25, 2014, at 7:21 AM, "Ian Woloschin" 
mailto:iwolosc...@gmail.com>> wrote:

I'm an idiot.  I blindly followed instructions that were likely for Angstrom, 
and put the dtb file in the wrong place, /boot instead of /boot/uboot/dtbs.  
Now that the dtb file is being read I've got everything showing up properly, 
which is great because I've got my first NeoPixel stick arriving in the mail 
today.  Unfortunately I'll be out of town this weekend, but I've got a 4 hour 
train ride back Monday morning so I may try to get some stuff working on the 
train.

On Friday, April 25, 2014 7:05:58 AM UTC-4, Ian Woloschin wrote:
I'm looking into the same thing and running into the same problems of no simple 
tutorials.  At this point I'm having issues getting the PRU to even be enabled, 
and I'm not really sure why.

On Tuesday, April 22, 2014 12:59:09 PM UTC-4, Mark A. Yoder wrote:
David:
  Thanks for the pointer, however I had already Google'd around and picked the 
LEDscape as the most promising. Since I haven't uncovered any 'getting started' 
guides for it I guess I'll just dive in a figure it out for myself.

--Mark

On Monday, April 21, 2014 1:48:15 PM UTC-4, dwfunk4475 wrote:
http://lmgtfy.com/?q=beaglebone+black+ws2812


Plenty of tutorials . . .  adapt to whatever pin(s) you wish to use on our BBB




-david


On Mon, Apr 21, 2014 at 11:00 AM, Mark A. Yoder  wrote:
Hi Beagle'ers:
  I have a string adafruit NEOpixel LEDs[1] that I want to drive with the BBB.  
LEDscape[2] looks like a good way to drive the LEDs via the PRUs.

I'm not sure how to get started.  Has anyone used this software to drive the 
LEDs?  What should I wire where?

--Mark

[1] http://www.adafruit.com/products/1376
[2] https://github.com/osresearch/LEDscape




--
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/WvwfBq26kEk/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.

[beagleboard] Re: I would like to execute a program automatically,when power supply at ON.

[Uonsong Ly]

Hello Anthony, it looks like that this method only works if I boot up and 
ssh to the BBB OS. Do you know of a method that would allow a program to 
execute once there is power through the BBB (with 5V port not the USB)?

I have been trying to figure this out for a while now. I would really 
appreciate it if you can provide me with some suggestions on this matter. 
Thanks in advance,

Uonsong  

On Thursday, April 24, 2014 6:01:36 AM UTC-6, cove...@gmail.com wrote:
>
> Hi,
>
> You can put myScript.sh into the /etc/profile.d directory and your script 
> will be executed on startup.
>
> Obviously there's several ways to do this, but that's cheap and cheerful.
>
> Regards,
>
> Anthony
>
>
>
> On Thursday, 24 April 2014 07:07:32 UTC+1, kenji maehara wrote:
>>
>> Hi,
>>
>> I made TCP client program for Beaglebone Black on Angstrom Linux.
>> I would like to execute a program automatically,when power supply at ON 
>> for connection to server.
>>
>>
>>
>> I put the execute file here.
>> /home/a.out
>>
>>
>> I made a file called myScript.sh on this pass.
>> /etc/init.d/myScript.sh
>>
>> It is contents of file myScript.sh
>> #!/bin/bash
>> /home/a.out
>>
>>
>> I executed the following command for file myScript.sh.
>> chmod u=+rwx myScript.sh
>>
>>
>> Next, in /etc/rc5.d folder、I executed the command.
>> ln -s ../init.d/myScript.sh S99myScript
>>
>>
>> I thought that it can start in this automatically,
>>
>>  but I can't.
>>
>>
>> I refer to these contents.
>> https://groups.google.com/forum/#!topic/beagleboard/6GmHGPgnY84
>>
>>
>> Would you tell me any your advice thing or solution?
>>
>>
>> thanks.
>>
>>
>>
>>

-- 
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] BeagleBoneBlack toy DJ table? Needs to mix and warp two music tracks.

[paul . sisneros]

I have a project idea that I'm still in the early stages of. My background 
is in PLC programming and microcontrollers, mostly for automation, so I've 
done some graphics and signal control, but not much with audio other than 
playing a sound.

My son is a toddler, and he loves instruments and music toys, and he loves 
this thing at the children's museum that lets him mix beats. So I was 
thinking it would be a lot of fun to make him a DJ table, it would have two 
turn tables that could detect when they were pushed or pulled, and a 
selector for the type of tune each controlled (hip hop, funk, disco, club 
techno ect). I can easily handle the input and control, but I have only a 
vague idea where to start with the audio mixing. I understand the BBB needs 
a USB audio device to play sound, and that's fine. The hard part is that it 
would have to mix the two tracks and warp them. Perhaps there is some open 
source Linux software that is already most of the way? I could pre-edit the 
beat tracks to get them in the same time and in the right format, but it 
would still have to be able to warp their speed in real time. It would also 
be cool if there were buttons for samples to mix in. The main thing that 
makes this different from a real DJ table is that the track selection 
doesn't have to be editable on the fly, and it would automatically make the 
samples and audio tracks settle on the same clock beat.

Any suggestions. I'm open to suggestions on other controllers that could do 
this as well, but I think the BBB could, and I already have one. I could 
use an entire PC to do it, but that doesn't seem as cool or efficient.

Thanks!

-- 
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] Device Overlay to Switch off USR0-3 LEDS

[stuie_norris]

Hi Forum,
 
I am attempting to create a device overaly to turn off the USR0-3 on Ubuntu 
13.10 (Linux ubuntu-armhf 3.8.13-bone30)  on my Beagle Bone Black A5C.
 
I have performed the following process - but the USR0-3 LEDs continue to 
flash.  I expected all of them to turn off and have trigger state of 
"[none]"
 
The DTS (BBB-LEDS-00A0.dts) file I have created is as follows
 
/dts-v1/;
/plugin/;
/
{
 compatible = "ti,beaglebone", "ti,beaglebone-black";
 part-number = "BBB-LEDS-00A0";
 version = "00A0";
 fragment@0
  {
 target = <&ocp>;
 __overlay__
 {
 gpio-leds {
 compatible = "gpio-leds";
 pinctrl-names = "default";
 pinctrl-0 = <&userled_pins>;
 led0 {
 label = "beaglebone:green:usr0";
 gpios = <&gpio2 0x15 0x0>;
 linux,default-trigger = "none";
 default-state = "off";
 };
 led1 {
 label = "beaglebone:green:usr0";
 gpios = <&gpio2 0x16 0x0>;
 linux,default-trigger = "none";
 default-state = "off";
 };
 led2 {
 label = "beaglebone:green:usr0";
 gpios = <&gpio2 0x17 0x0>;
 linux,default-trigger = "none";
 default-state = "off";
 };
 led3 {
 label = "beaglebone:green:usr0";
 gpios = <&gpio2 0x18 0x0>;
 linux,default-trigger = "none";
 default-state = "off";
 };
 };
 };
   };
};
 
I have the latest dtc with the patches from Robert Nelson ( wget -c 
https://raw.github.com/RobertCNelson/tools/master/pkgs/dtc.sh)
 
I compile the DTS file using 
 
dtc -O dtb -o BBB-LEDS-00A0.dtbo -b 0 -@ BBB-LEDS-00A0.dts
Copy the generated dtbo file to /lib/firmware
 
sudo cp BBB-LEDS-00A0.dtbo /lib/firmware/
Load the device tree overlay using
 
sudo sh -c "echo BBB-LEDS > /sys/devices/bone_capemgr.9/slots"
I see the slots that the "cape" is loaded
0: 54:PF---
 1: 55:PF---
 2: 56:PF---
 3: 57:PF---
 4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G
 5: ff:P-O-L Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI
 8: ff:P-O-L Override Board Name,00A0,Override Manuf,BBB-LEDS
>From dmesg all seems okay as well
[20729.329645] bone-capemgr bone_capemgr.9: part_number 'BBB-LEDS', version 
'N/A'
[20729.329832] bone-capemgr bone_capemgr.9: slot #8: generic override
[20729.329882] bone-capemgr bone_capemgr.9: bone: Using override eeprom 
data at slot 8
[20729.329933] bone-capemgr bone_capemgr.9: slot #8: 'Override Board 
Name,00A0,Override Manuf,BBB-LEDS'
[20729.330218] bone-capemgr bone_capemgr.9: slot #8: Requesting part 
number/version based 'BBB-LEDS-00A0.dtbo
[20729.330273] bone-capemgr bone_capemgr.9: slot #8: Requesting firmware 
'BBB-LEDS-00A0.dtbo' for board-name 'Override Board Name', version '00A0'
[20729.333640] bone-capemgr bone_capemgr.9: slot #8: dtbo 
'BBB-LEDS-00A0.dtbo' loaded; converting to live tree
[20729.334146] bone-capemgr bone_capemgr.9: slot #8: #1 overlays
[20729.334750] bone-capemgr bone_capemgr.9: slot #8: Applied #1 overlays.
Could someone point me as towards what I have done wrong?  
 
Thanks
 
Stuart
 

-- 
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] ti ezsdk v07.00 for BBB

[Maxim Podbereznyy]

Hey guys!

Who already tried SITARA-EZSDK v07.00 at BBB? Is it worth a try?

-- 
LinkedIn - http://www.linkedin.com/in/maximpodbereznyy
Company - http://www.linkedin.com/company/mentorel
Facebook - https://www.facebook.com/mentorel.company

-- 
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: Cape Device Tree Overlay fails to load during boot?

[Charles Steinkuehler]

On 4/25/2014 5:37 AM, Andreas Tauböck wrote:
> 
> and I get a permission denied when i want to add it manually with:
> 
> ubuntu@arm:/sys/devices/bone_capemgr.9$ sudo echo TT3201:001 >slots
> -bash: slots: Permission denied

The redirect happens before the sudo, try:

sudo su -c "echo TT3201:001 > slots"

-- 
Charles Steinkuehler
char...@steinkuehler.net

-- 
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] LEDscape and adafruit NEOpixel LEDs on BBB

[Ian Woloschin]

I'm an idiot.  I blindly followed instructions that were likely for 
Angstrom, and put the dtb file in the wrong place, /boot instead of 
/boot/uboot/dtbs.  Now that the dtb file is being read I've got everything 
showing up properly, which is great because I've got my first NeoPixel 
stick arriving in the mail today.  Unfortunately I'll be out of town this 
weekend, but I've got a 4 hour train ride back Monday morning so I may try 
to get some stuff working on the train.

On Friday, April 25, 2014 7:05:58 AM UTC-4, Ian Woloschin wrote:
>
> I'm looking into the same thing and running into the same problems of no 
> simple tutorials.  At this point I'm having issues getting the PRU to even 
> be enabled, and I'm not really sure why.
>
> On Tuesday, April 22, 2014 12:59:09 PM UTC-4, Mark A. Yoder wrote:
>>
>> David:
>>   Thanks for the pointer, however I had already Google'd around and 
>> picked the LEDscape as the most promising. Since I haven't uncovered any 
>> 'getting started' guides for it I guess I'll just dive in a figure it out 
>> for myself.
>>
>> --Mark
>>
>> On Monday, April 21, 2014 1:48:15 PM UTC-4, dwfunk4475 wrote:
>>>
>>> http://lmgtfy.com/?q=beaglebone+black+ws2812
>>>
>>>
>>> Plenty of tutorials . . .  adapt to whatever pin(s) you wish to use on 
>>> our BBB
>>>
>>>
>>>
>>>
>>> -david
>>>
>>>
>>> On Mon, Apr 21, 2014 at 11:00 AM, Mark A. Yoder wrote:
>>>
 Hi Beagle'ers:
   I have a string adafruit NEOpixel LEDs[1] that I want to drive with 
 the BBB.  LEDscape[2] looks like a good way to drive the LEDs via the PRUs.

 I'm not sure how to get started.  Has anyone used this software to 
 drive the LEDs?  What should I wire where?

 --Mark

 [1] http://www.adafruit.com/products/1376 
 [2] https://github.com/osresearch/LEDscape 

>>>
>>>
>>>
>>>

-- 
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] Disable BB-BONELT-HDMI using uEnv

[Tristan Phillips]

 

I'm rather confused.  I cannot seem to disable BB-BONELT-HDMI using the 
uEnv capemgr.disable_partno optargs arg.

My uEnv.txt line looks like this: 
optargs=capemgr=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN

but:

root@StockBBB:~#* cat /sys/devices/bone_capemgr.9/slots*

 1: 55:PF---

 2: 56:PF--- 

 3: 57:PF--- 

 4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G

 5: ff:P-O-*L* Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI

Yet I can see the uEnv was read:

root@StockBBB:~# *cat /proc/cmdline *

console=ttyO0,115200n8 
*capemgr=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN*root=UUID=458951f9-fd96-459c-b1a3-6f2300e0fa58
 ro rootfstype=ext4 rootwait 
fixrtc ip=

Does anybody have any ideas?

As a side question, the firmware for things like the BB-BONE-AUD-01 are 
apparently compiled into the kernel now.  How could I force the dtbo to be 
loaded from a file?

Thanks in advance for any help.

Tris

-- 
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] LEDscape and adafruit NEOpixel LEDs on BBB

[Ian Woloschin]

I'm looking into the same thing and running into the same problems of no 
simple tutorials.  At this point I'm having issues getting the PRU to even 
be enabled, and I'm not really sure why.

On Tuesday, April 22, 2014 12:59:09 PM UTC-4, Mark A. Yoder wrote:
>
> David:
>   Thanks for the pointer, however I had already Google'd around and picked 
> the LEDscape as the most promising. Since I haven't uncovered any 'getting 
> started' guides for it I guess I'll just dive in a figure it out for myself.
>
> --Mark
>
> On Monday, April 21, 2014 1:48:15 PM UTC-4, dwfunk4475 wrote:
>>
>> http://lmgtfy.com/?q=beaglebone+black+ws2812
>>
>>
>> Plenty of tutorials . . .  adapt to whatever pin(s) you wish to use on 
>> our BBB
>>
>>
>>
>>
>> -david
>>
>>
>> On Mon, Apr 21, 2014 at 11:00 AM, Mark A. Yoder wrote:
>>
>>> Hi Beagle'ers:
>>>   I have a string adafruit NEOpixel LEDs[1] that I want to drive with 
>>> the BBB.  LEDscape[2] looks like a good way to drive the LEDs via the PRUs.
>>>
>>> I'm not sure how to get started.  Has anyone used this software to drive 
>>> the LEDs?  What should I wire where?
>>>
>>> --Mark
>>>
>>> [1] http://www.adafruit.com/products/1376 
>>> [2] https://github.com/osresearch/LEDscape 
>>>
>>
>>
>>
>>

-- 
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: Cape Device Tree Overlay fails to load during boot?

[Andreas Tauböck]

Hy,

I´m having a very similar problem. I am using the current version of ubuntu 
for BBB (Ubuntu 14.04 LTS (GNU/Linux 3.8.13-bone47 armv7l)) and tried to a 
device tree overlay with this guide for the exact same cape: 
http://the8thlayerof.net/2013/10/28/canbus-beagle-bone-black-as-a-canbus-data-logger-part-2/

However the dmesg output says the loading fails:

[2.011897] bone-capemgr bone_capemgr.9: loader: before slot-3 
TT3201-001:05 (prio 0)
[2.020116] bone-capemgr bone_capemgr.9: loader: check slot-3 
TT3201-001:05 (prio 0)
[2.042227] bone-capemgr bone_capemgr.9: loader: after slot-3 
TT3201-001:05 (prio 0)
[2.062825] bone-capemgr bone_capemgr.9: slot #3: Requesting part 
number/version based 'TT3201-001-05.dtbo
[2.093253] bone-capemgr bone_capemgr.9: slot #3: Requesting firmware 
'TT3201-001-05.dtbo' for board-name 'TT3201 CAN Bus Cape', version '05'
[2.901230] bone-capemgr bone_capemgr.9: failed to load firmware 
'TT3201-001-05.dtbo'
[2.909494] bone-capemgr bone_capemgr.9: loader: failed to load slot-3 
TT3201-001:05 (prio 0)

and I get a permission denied when i want to add it manually with:

ubuntu@arm:/sys/devices/bone_capemgr.9$ sudo echo TT3201:001 >slots
-bash: slots: Permission denied

There are plenty of people having this problem but i could not find a good 
solution yet as it should not happen in newer releases anymore.

I appreciate any help???

Am Freitag, 15. November 2013 11:50:05 UTC+1 schrieb Jesper We:
>
> OK, I have read this 
> threadtwice
>  now, and I still fail to see any real solution in between the 
> discussion of various patches. 
>
> There is a lot of discussion in that thread about custom kernels, but my 
> BB Black has the latest Angstrom eMMC flasher version with everything as 
> default.
>
> I have made a Cape PCB with an RTC and 4 serial ports for UART1,2,4,5. The 
> Cape has an EEPROM at i2c address 0x54 (Slot #0) with the proper part 
> number and revision.
> I have disabled the loading of all HDMI overlay features in uEnv.txt.
>
> On exactly the same board I can swap out my Cape for the Circuitco RS232 
> cape which I have a couple of. It has the .dto files already in 
> /lib/firmware in the distro.
> That DTO loads fine during boot, with the same priority (0) as my cape.
> So it's not an issue of the eMMC not being ready.
>
> However, the Circuitco Rs232 Capes are loaded earlier in the boot process 
> than the point at which my cape fails. Since my DTO is just a merge of the 
> original RS232 UARTs DTOs from the distro, I cannot understand why...
>
> So my questions are:
> - Why is the failure to load my cape coming much later in the boot process 
> than the Circuitco cape's success?
> - Is there any way to know why the boot time loading fails, when the cape 
> loads fine manually?
>
> See below fore some transcripts. The source for my DTO is enclosed.
>
> /jesper
>
>
> root@beaglebone:~# ls -l /lib/firmware/CP*
> -rw-r--r-- 1 root root 1969 Nov 14 19:15 /lib/firmware/CP-CLOUDSAFE-
> 00A0.dtbo
> -rwxr-xr-x 1 root root 2117 Nov 14 19:13 /lib/firmware/CP-CLOUDSAFE-
> 00A0.dts
>
> Loading the DTO manually works fine:
>
> root@beaglebone:/lib/firmware# echo CP-CLOUDSAFE 
> >/sys/devices/bone_capemgr.8/slots
> root@beaglebone:/lib/firmware# dmesg
> 
> [  200.937688] bone-capemgr bone_capemgr.8: part_number 
> 'CP-CLOUDSAFE',version 
> 'N/A'
> [  200.937766] bone-capemgr bone_capemgr.8: slot #7: generic override
> [  200.937786] bone-capemgr bone_capemgr.8: bone: Using override eeprom 
> data at slot 7
> [  200.937803] bone-capemgr bone_capemgr.8: slot #7: 'Override Board 
> Name,00A0,Override Manuf,CP-CLOUDSAFE'
> [  200.937896] bone-capemgr bone_capemgr.8: slot #7: Requesting part 
> number/version based 'CP-CLOUDSAFE-00A0.dtbo
> [  200.937915] bone-capemgr bone_capemgr.8: slot #7: Requesting firmware 
> 'CP-CLOUDSAFE-00A0.dtbo' for board-name 'Override Board Name', version 
> '00A0'
> [  200.947556] bone-capemgr bone_capemgr.8: slot #7: dtbo 
> 'CP-CLOUDSAFE-00A0.dtbo' loaded; converting to live tree
> [  200.947984] bone-capemgr bone_capemgr.8: slot #7: #5 overlays
> [  200.954890] 48022000.serial: ttyO1 at MMIO 0x48022000 (irq = 89) is a 
> OMAP UART1
> [  200.958878] 48024000.serial: ttyO2 at MMIO 0x48024000 (irq = 90) is a 
> OMAP UART2
> [  200.964739] 481a8000.serial: ttyO4 at MMIO 0x481a8000 (irq = 61) is a 
> OMAP UART4
> [  200.970604] 481aa000.serial: ttyO5 at MMIO 0x481aa000 (irq = 62) is a 
> OMAP UART5
> [  200.974945] bone-capemgr bone_capemgr.8: slot #7: Applied #5 overlays.
> 
> root@beaglebone:~# cat /sys/devices/bone_capemgr.8/slots
>  1: 55:PF--- 
>  2: 56:PF--- 
>  3: 57:PF--- 
>  4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G
>  5: ff:P-O-- Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI
>  6: ff:P-O-- Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN
>  7: ff:P-O-L Override Board Name,00A0,Override Manuf,CP