Re: [beagleboard] Re: Trouble enabling SPI1 hardware with debian 4.4.9

2016-09-26 Thread William Wendin
Hi Danny,

No, I did not get spi2 working (SPI1_ pins on P9 header) with all the 
other pins enabled.   I gave up for now.   Wasn't sure what to try next... 
  Maybe I don't understand William Hermans' instructions.

On Monday, September 26, 2016 at 6:33:17 AM UTC-7, Danny B wrote:
>
> Was there any luck on getting this to work?
>
> On Wednesday, August 24, 2016 at 12:44:19 PM UTC-4, William Wendin wrote:
>>
>> I have tried these steps:
>> * altering cape-universaln-00A0.dts by uncommenting every spi2 lines in 
>> there (I called it universalbbb-00A0.dts).  Created new dtbo.  Copied it to 
>> /lib/firmware
>> * Changed uEnv.txt to "cmdline=coherent_pool=1M quiet 
>> cape_universal=disable"Trying to load universalbbb in uEnv.txt DOES NOT 
>> work.
>> * root@beaglebone:/# echo 'universalbbb' 
>> > /sys/devices/platform/bone_capemgr/slots
>> * I see in dmesg that above fails to config debian pins 100, 101, 103
>>
>> I tried some other things after above steps to see if I can fix it at 
>> runtime:
>> * config-pin manually to spi:
>> root@beaglebone:/# config-pin P9.29 spi
>> bash: /sys/devices/platform/ocp/ocp*P9_29_pinmux/state: No such file or 
>> directory
>> Cannot write pinmux file: /sys/devices/platform/ocp/ocp*P9_29_pinmux/state
>> * add cape overlay BB-SPIDEV1
>> root@beaglebone:/# echo 'BB-SPIDEV1' > 
>> /sys/devices/platform/bone_capemgr/slots
>> bash: echo: write error: File exists
>>
>> I'm going to have to give up for now as I spent whole day yesterday on 
>> this.   Need to move on to other stuff but will return.
>>
>>
>> On Saturday, August 20, 2016 at 4:09:55 PM UTC-7, William Hermans wrote:
>>>
>>> You'll need to put all your pin mux into one file. I'd probably test 
>>> with universal io, to see if you can get it working that way first, and 
>>> then perhaps you'll have to put that, or all pin mux into the board file.
>>>
>>> On Sat, Aug 20, 2016 at 3:29 PM, William Wendin  
>>> wrote:
>>>
 Made a mistake in original post.   Should read:

 What I've tried:
 * I've tried adding BB-SPIDEV1 via uEnv.txt.   SPI1 now works.   
  However, that wipes out the availability of I2C, PWMs, etc which I don't 
 know how to repair
 * I've seen that folks say that the only way to add SPIDEV1 overlay is 
 via /etc/rc.local (echo 'BB-SPIDEV1' > 
 /sys/devices/platform/bone_capemgr/slots). But that didn't work at all 
 for me (SPI1 not enabled AND it wipes out availability of I2C, PWMs etc).


 On Saturday, August 20, 2016 at 2:42:12 PM UTC-7, William Wendin wrote:
>
> Background Info:
> 1) We are using BeagleBone Black to power our robot, using it since 
> November.  
> 2) We use ADC, I2C1, I2C2, SPI0, 5 PWMs, and almost every available 
> GPIO.  We have all these working using overlays, or config-pin, whichever 
> is needed.   All is good.
> 3) Up until now I have not had to alter the default kernel or 
> uEnv.txt.*
> 4) Upgraded to 4.4.9 a month or two ago.I am up-to-date with all 
> "apt-get update" and "apt-get upgrade".
> 5) /boot/uEnv.txt is attached.
> 6) root@beaglebone:/home/debian# uname -a
>Linux beaglebone 4.4.9-ti-r25 #1 SMP Thu May 5 23:08:13 UTC 
> 2016 armv7l GNU/Linux
>
> The problem: Now we need SPI1 (yes, we need two SPI busses). I 
> want to use all the IOs listed above  (see #2).
>
> I think the best way is to use the default universal cape that comes 
> with 4.4.9 (see above where I use it for all my IOs with little effort), 
> but enable SPI1 instead of MCASP.
>
> What I've tried:
> * I've seen that folks say that the only way to add SPIDEV1 overlay is 
> via /etc/rc.local (echo 'BB-SPIDEV1' > 
> /sys/devices/platform/bone_capemgr/slots).However, that then wipes 
> out 
> the availability of I2C, PWMs, etc.
> * I've also tried adding BB-SPIDEV1 via uEnv.txt but that didn't work 
> at all.
>
> I've spent a few days trying various combination and can't find it.   
> Looked at source code too to try and see what is up, but didn't figure it 
> out yet.
>
> I guess my idea of the "best way" is heading down the wrong path.   
>
> Questions:
> * Do I have to make a whole new universal custom cape?
> * Follow on question: Anybody have a way to turn on everything I use 
> (see #2 above) and SPIDEV1 too?
>
 -- 
 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.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/beagleboard/353acaa9-0512-4099-a171-2b5cc0e2216c%40googlegroups.com
  
 

Re: [beagleboard] Debugging with CCs V6.2 / TI XDS100v2 USB failed becuase of Address 0x80000000

2016-09-26 Thread Ashkan Golestani
John,
Thanks for quick reply .Using the BBB is too complicated than I expected . 
Thanks again for info . I'll post to this chain if I had more issue with 
those packages!

Regards 
Ash 

On Monday, September 26, 2016 at 12:33:51 PM UTC-7, john3909 wrote:

> If you are trying to do bare bone development, then Starterware has a 
> custom MLO, u-boot and GEL files necessary to configure DDR memory. Clearly 
> the BBB DDR hasn’t been configured and that is why you are getting this 
> error.
>
> Regards,
> John
>
>
>
>
> On Sep 26, 2016, at 12:04 PM, Ashkan Golestani  > wrote:
>
> Folks,
> I am new with BBB but I have enough experience with CCS and ARM and other 
> processors .
> I have created the project with C++ ,GNU Compiler and Linker also is 
> attached to my project . 
> Here is my problem :
>
> M3_wakeupSS: File Loader: Verification failed: Values at address 
> 0x8000 do not match Please verify target memory and memory map. (Note: 
> I can uncheck the fast verification, But that is not the right solution )
>
> M3_wakeupSS: GEL: File: ...\workspace_v6_2\RSM_1\Debug\RSM_1.out: a data 
> verification error occurred, file load failed.
>
> I don't see any option on project properties for BBB setting to select the 
> start debugging address. 
> By the way if it is not 0x8000  ! what is the number ?
>
> Thanks in advance 
> Ashkan Golestani
>
> -- 
> 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 .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/beagleboard/31da8342-4de5-4f70-81a3-c38f9592695c%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/676be37b-b9a6-4e6a-937d-93ca20cd1e1e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [beagleboard] bone-debian-8.6-console-armhf-2016-09-25-2gb Permission denied

2016-09-26 Thread Robert Nelson
On Mon, Sep 26, 2016 at 3:29 PM, Robert Nelson  wrote:
> On Mon, Sep 26, 2016 at 2:34 PM, toni incog  wrote:
>> Hi,
>>
>> FYI. I could not login as user debian from this freshly bmapped sd booted
>> image, root is possible.
>>
>> Long story short:
>>
>> root@beaglebone:/lib/arm-linux-gnueabihf# ls -sla /
>> total 92
>>  4 drwx-- 21  110  114  4096 Sep 25 21:06 .
>>  4 drwx-- 21  110  114  4096 Sep 25 21:06 ..
>>  4 -rw-r--r--  1 root root40 Sep 26  2016 ID.txt
>>
>> 110 114?
>>
>> chown root:root /
>> chmod 755  /
>>
>> et voila, login user debian possible
>
> Yeah, i'm seeing this too, on the non *.img...
>
> Last week we had a debootstrap upgrade 1.0.81 -> 1.0.83, i bet that broke it..
>
> Testing now...

Yeah, regression in debootstrap 1.0.83... 1.0.82 works here, triggered
a full rebuild..

Regards,

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

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYhW7P16-LUkDfQfPC0GgERNHeGdrd4VoP8etQ6mi5_tFg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [beagleboard] bone-debian-8.6-console-armhf-2016-09-25-2gb Permission denied

2016-09-26 Thread Robert Nelson
On Mon, Sep 26, 2016 at 2:34 PM, toni incog  wrote:
> Hi,
>
> FYI. I could not login as user debian from this freshly bmapped sd booted
> image, root is possible.
>
> Long story short:
>
> root@beaglebone:/lib/arm-linux-gnueabihf# ls -sla /
> total 92
>  4 drwx-- 21  110  114  4096 Sep 25 21:06 .
>  4 drwx-- 21  110  114  4096 Sep 25 21:06 ..
>  4 -rw-r--r--  1 root root40 Sep 26  2016 ID.txt
>
> 110 114?
>
> chown root:root /
> chmod 755  /
>
> et voila, login user debian possible

Yeah, i'm seeing this too, on the non *.img...

Last week we had a debootstrap upgrade 1.0.81 -> 1.0.83, i bet that broke it..

Testing now...

Regards,

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

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYi2yrZS%2B%2B3oU55eCMmUsFk3%2BbjEPSTBaH53kMn2WMt%3DxQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [beagleboard] Debugging with CCs V6.2 / TI XDS100v2 USB failed becuase of Address 0x80000000

2016-09-26 Thread John Syne
If you are trying to do bare bone development, then Starterware has a custom 
MLO, u-boot and GEL files necessary to configure DDR memory. Clearly the BBB 
DDR hasn’t been configured and that is why you are getting this error.

Regards,
John




> On Sep 26, 2016, at 12:04 PM, Ashkan Golestani  wrote:
> 
> Folks,
> I am new with BBB but I have enough experience with CCS and ARM and other 
> processors .
> I have created the project with C++ ,GNU Compiler and Linker also is attached 
> to my project .
> Here is my problem :
> M3_wakeupSS: File Loader: Verification failed: Values at address 0x8000 
> do not match Please verify target memory and memory map. (Note: I can uncheck 
> the fast verification, But that is not the right solution )
> 
> M3_wakeupSS: GEL: File: ...\workspace_v6_2\RSM_1\Debug\RSM_1.out: a data 
> verification error occurred, file load failed.
> 
> 
> I don't see any option on project properties for BBB setting to select the 
> start debugging address.
> By the way if it is not 0x8000  ! what is the number ?
> 
> Thanks in advance
> Ashkan Golestani
> 
> -- 
> 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 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/beagleboard/31da8342-4de5-4f70-81a3-c38f9592695c%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/604694BF-DC2D-4689-8713-C8E40B294940%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


[beagleboard] bone-debian-8.6-console-armhf-2016-09-25-2gb Permission denied

2016-09-26 Thread toni incog
Hi,

FYI. I could not login as user debian from this freshly bmapped sd booted 
image, root is possible.

Long story short:

root@beaglebone:/lib/arm-linux-gnueabihf# ls -sla /
total 92
 4 drwx-- 21  110  114  4096 Sep 25 21:06 .
 4 drwx-- 21  110  114  4096 Sep 25 21:06 ..
 4 -rw-r--r--  1 root root40 Sep 26  2016 ID.txt

110 114?

chown root:root /
chmod 755  /   

et voila, login user debian possible

--
Toni

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/d0303204-08fb-47e2-8d22-154e57101f79%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [beagleboard] SGX on 4.4.*-ti-rt kernel

2016-09-26 Thread Robert Nelson
On Mon, Sep 26, 2016 at 10:50 AM,   wrote:
> Hi,
>
> I try for the first time to enable SGX feauture on BBB using the kernel
> version 4.4.* to experiment and try to use it with weston.
> I use jessie debian image (rcn) updated to kernel 4.4.16-ti-rt-r38
> After the update, I install also sgx module:
> $ apt-get install ti-sgx-ti335x-modules-4.4.16-ti-rt-r38
>
> In this package there are:
> pvrsrvkm.ko
> bc_example.ko
>
> I don't know if I need also omaplfb.ko.that I find in documentation.
> Is there in any package? What packages I need to install for this kernel
> version?

So, you just need the userspace bits:

git clone -b ti-img-sgx/1.14.3699939
git://git.ti.com/graphics/omap5-sgx-ddk-um-linux.git --depth=1

cd omap5-sgx-ddk-um-linux/

sudo su
export DISCIMAGE=/
export TARGET_PRODUCT=ti335x
make install
exit

#fix: libgbm.so.2
sudo ln -s /usr/lib/arm-linux-gnueabihf/libgbm.so.1
/usr/lib/arm-linux-gnueabihf/libgbm.so.2

sudo mkdir -p /lib/modules/4.4.11-00332-gce54280-dirty/extra/
sudo ln -s /lib/modules/`uname -r`/extra/ti335x/pvrsrvkm.ko
/lib/modules/4.4.11-00332-gce54280-dirty/extra/pvrsrvkm.ko

debian@beaglebone:~$ sudo /usr/bin/pvrsrvctl --start
PVR:(Error): OpenServices: PVRDRMOpenRender failed [0, ]
PVR:(Error): PVRSRVInitSrvConnect: PVRSRVConnect failed [0, ]
PVR:(Error): SrvInit: PVRSRVInitSrvConnect failed (4) [0, ]
/usr/bin/pvrsrvctl: SrvInit failed (already initialized?)
(err=PVRSRV_ERROR_INIT_FAILURE)

Yeah, that's as far as i got... TI even got that far in our jessie image too...

Regards,


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

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYjqyxcWb5YuFQO875U_n1daaXLTjdTG9M%3DeyDu83%2BNwkA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


[beagleboard] Debugging with CCs V6.2 / TI XDS100v2 USB failed becuase of Address 0x80000000

2016-09-26 Thread Ashkan Golestani
Folks,
I am new with BBB but I have enough experience with CCS and ARM and other 
processors .
I have created the project with C++ ,GNU Compiler and Linker also is 
attached to my project . 
Here is my problem :

M3_wakeupSS: File Loader: Verification failed: Values at address 0x8000 
do not match Please verify target memory and memory map. (Note: I can 
uncheck the fast verification, But that is not the right solution )

M3_wakeupSS: GEL: File: ...\workspace_v6_2\RSM_1\Debug\RSM_1.out: a data 
verification error occurred, file load failed.

I don't see any option on project properties for BBB setting to select the 
start debugging address. 
By the way if it is not 0x8000  ! what is the number ?

Thanks in advance 
Ashkan Golestani

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/31da8342-4de5-4f70-81a3-c38f9592695c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[beagleboard] SGX on 4.4.*-ti-rt kernel

2016-09-26 Thread matteo . facchinetti
Hi,

I try for the first time to enable SGX feauture on BBB using the kernel 
version 4.4.* to experiment and try to use it with weston.
I use jessie debian image (rcn) updated to kernel 4.4.16-ti-rt-r38
After the update, I install also sgx module:
$ apt-get install ti-sgx-ti335x-modules-4.4.16-ti-rt-r38

In this package there are:
pvrsrvkm.ko
bc_example.ko

I don't know if I need also omaplfb.ko.that I find in documentation.
Is there in any package? What packages I need to install for this kernel 
version?

Regards,
Matteo

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/80233f5e-9d1b-400f-ba7b-5a2aaf5ba2a6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [beagleboard] Re: Trouble enabling SPI1 hardware with debian 4.4.9

2016-09-26 Thread Danny B
Was there any luck on getting this to work?

On Wednesday, August 24, 2016 at 12:44:19 PM UTC-4, William Wendin wrote:
>
> I have tried these steps:
> * altering cape-universaln-00A0.dts by uncommenting every spi2 lines in 
> there (I called it universalbbb-00A0.dts).  Created new dtbo.  Copied it to 
> /lib/firmware
> * Changed uEnv.txt to "cmdline=coherent_pool=1M quiet 
> cape_universal=disable"Trying to load universalbbb in uEnv.txt DOES NOT 
> work.
> * root@beaglebone:/# echo 'universalbbb' 
> > /sys/devices/platform/bone_capemgr/slots
> * I see in dmesg that above fails to config debian pins 100, 101, 103
>
> I tried some other things after above steps to see if I can fix it at 
> runtime:
> * config-pin manually to spi:
> root@beaglebone:/# config-pin P9.29 spi
> bash: /sys/devices/platform/ocp/ocp*P9_29_pinmux/state: No such file or 
> directory
> Cannot write pinmux file: /sys/devices/platform/ocp/ocp*P9_29_pinmux/state
> * add cape overlay BB-SPIDEV1
> root@beaglebone:/# echo 'BB-SPIDEV1' > 
> /sys/devices/platform/bone_capemgr/slots
> bash: echo: write error: File exists
>
> I'm going to have to give up for now as I spent whole day yesterday on 
> this.   Need to move on to other stuff but will return.
>
>
> On Saturday, August 20, 2016 at 4:09:55 PM UTC-7, William Hermans wrote:
>>
>> You'll need to put all your pin mux into one file. I'd probably test with 
>> universal io, to see if you can get it working that way first, and then 
>> perhaps you'll have to put that, or all pin mux into the board file.
>>
>> On Sat, Aug 20, 2016 at 3:29 PM, William Wendin  wrote:
>>
>>> Made a mistake in original post.   Should read:
>>>
>>> What I've tried:
>>> * I've tried adding BB-SPIDEV1 via uEnv.txt.   SPI1 now works.   
>>>  However, that wipes out the availability of I2C, PWMs, etc which I don't 
>>> know how to repair
>>> * I've seen that folks say that the only way to add SPIDEV1 overlay is 
>>> via /etc/rc.local (echo 'BB-SPIDEV1' > 
>>> /sys/devices/platform/bone_capemgr/slots). But that didn't work at all 
>>> for me (SPI1 not enabled AND it wipes out availability of I2C, PWMs etc).
>>>
>>>
>>> On Saturday, August 20, 2016 at 2:42:12 PM UTC-7, William Wendin wrote:

 Background Info:
 1) We are using BeagleBone Black to power our robot, using it since 
 November.  
 2) We use ADC, I2C1, I2C2, SPI0, 5 PWMs, and almost every available 
 GPIO.  We have all these working using overlays, or config-pin, whichever 
 is needed.   All is good.
 3) Up until now I have not had to alter the default kernel or uEnv.txt.*
 4) Upgraded to 4.4.9 a month or two ago.I am up-to-date with all 
 "apt-get update" and "apt-get upgrade".
 5) /boot/uEnv.txt is attached.
 6) root@beaglebone:/home/debian# uname -a
Linux beaglebone 4.4.9-ti-r25 #1 SMP Thu May 5 23:08:13 UTC 
 2016 armv7l GNU/Linux

 The problem: Now we need SPI1 (yes, we need two SPI busses). I want 
 to use all the IOs listed above  (see #2).

 I think the best way is to use the default universal cape that comes 
 with 4.4.9 (see above where I use it for all my IOs with little effort), 
 but enable SPI1 instead of MCASP.

 What I've tried:
 * I've seen that folks say that the only way to add SPIDEV1 overlay is 
 via /etc/rc.local (echo 'BB-SPIDEV1' > 
 /sys/devices/platform/bone_capemgr/slots).However, that then wipes out 
 the availability of I2C, PWMs, etc.
 * I've also tried adding BB-SPIDEV1 via uEnv.txt but that didn't work 
 at all.

 I've spent a few days trying various combination and can't find it.   
 Looked at source code too to try and see what is up, but didn't figure it 
 out yet.

 I guess my idea of the "best way" is heading down the wrong path.   

 Questions:
 * Do I have to make a whole new universal custom cape?
 * Follow on question: Anybody have a way to turn on everything I use 
 (see #2 above) and SPIDEV1 too?

>>> -- 
>>> 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.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/beagleboard/353acaa9-0512-4099-a171-2b5cc0e2216c%40googlegroups.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 

[beagleboard] Re: Cape issue

2016-09-26 Thread 'Barry Day' via BeagleBoard
First thing I would do is loop back tests on both ends so I know for 
certain what is working and what is not. 

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/1f31f1bc-4392-4b4b-9c94-f661254f5829%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[beagleboard] Re: Anyone using 4D System's 7in LCD cape?

2016-09-26 Thread 'Barry Day' via BeagleBoard
max brightness is 100 so for half brightness:
$ sudo echo 50 > /sys/class/backlight/backlight.11/brightness

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/fc6fd5dc-812f-4c37-b20f-7e33ab4c7631%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[beagleboard] Re: an initial success; beagle bone black + 7" LCD touchscreen cape a very nice/awesome combo

2016-09-26 Thread 'Barry Day' via BeagleBoard
I have the same cape mounted to a stand I made using the plastic tongue 
from tongue and groove chipboard. Very nifty but the power led is way too 
bright. 

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/ce1da3d2-0533-4082-98a5-2ffe1d75ab91%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.