Re: [beagleboard] cpufreq-info only 800MHz but I need 1GHz

2019-06-19 Thread activewholefoods 
I ran sudo dd if=/dev/zero of=/dev/mmcblk1 bs=1M count=100 

Now my BBB will not boot. What do I do?

Thanks,
Blair

On Wednesday, September 19, 2018 at 9:55:19 AM UTC-4, RobertCNelson wrote:
>
> On Wed, Sep 19, 2018 at 8:47 AM > wrote: 
> > 
> > Hi Robert. 
> > 
> > I'm wondering if you could help...  I have a BBBW that I can't get to 
> run at 1000MHz.  I tried updating the eeprom as suggested but no 
> difference.  Hardware still listed as max 800MHz. 
> > 
> > Here is output of version.sh 
> > git:/opt/scripts/:[73593ebe3b7d3cc381eeb502d45ccb33a6ec5e78] 
> > eeprom:[A335BNLTBWA5BBWG*] 
> > model:[TI_AM335x_BeagleBone_Black_Wireless] 
> > dogtag:[BeagleBoard.org Debian Image 2018-08-30] 
> > bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot 
> 2018.03-2-gac9cce7c6a]:[location: dd MBR] 
> > bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 
> 2017.01-6-g55e748eda0]:[location: dd MBR] 
>
> The really old version of U-Boot in the eMMC is blocking proper 
> construction of the Black Wireless device tree, thus breaking the cpu 
> node. 
>
> Just run: 
>
> sudo dd if=/dev/zero of=/dev/mmcblk1 bs=1M count=100 
>
> and reboot.. 
>
> 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/4d8ce632-c79a-4c2b-be26-9cf65d849e1a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: BBB wireless eMMC flash problem

2019-06-19 Thread Robert Nelson 
On Wed, Jun 19, 2019 at 5:13 PM Jeff Albrecht
 wrote:
>
> On Wednesday, June 19, 2019 at 9:59:07 AM UTC-7, Dennis Lee Bieber wrote:
>>
>> On Tue, 18 Jun 2019 20:22:20 -0700 (PDT), Jeff Albrecht
>>  declaimed the
>> following:
>>
>>
>> >!==> Error: [/dev/mmcblk1] does not exist
>> >writing to [/dev/mmcblk1] failed...
>>
>> Off hand -- I'd say the eMMC is dead...
>
>
> I wonder if I can find a through hole replacement? ;-)
>
> I do have a hot air rework station though...Has anyone ever successfully done 
> a field repair of eMMC?

Before you go do that, give this latest image a shot:

https://rcn-ee.net/rootfs/bb.org/testing/2019-06-16/buster-iot/bone-eMMC-flasher-debian-buster-iot-armhf-2019-06-16-4gb.img.xz

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/CAOCHtYi1AHVD%2BVimbxM1Kuea3e%3D41YBmBGzUz8%3D_TG3YOfVnxw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: BBB wireless eMMC flash problem

2019-06-19 Thread Jeff Albrecht 
On Wednesday, June 19, 2019 at 9:59:07 AM UTC-7, Dennis Lee Bieber wrote:
>
> On Tue, 18 Jun 2019 20:22:20 -0700 (PDT), Jeff Albrecht 
> > declaimed the 
> following: 
>
>
> >!==> Error: [/dev/mmcblk1] does not exist 
> >writing to [/dev/mmcblk1] failed... 
>
> Off hand -- I'd say the eMMC is dead... 


I wonder if I can find a through hole replacement? ;-) 

I do have a hot air rework station though...Has anyone ever successfully 
done a field repair of eMMC?

 - Jeff 

-- 
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/5fc851f7-3a37-42b7-a436-dbb88c2715b9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Getting Started with Beagle Board Blue

2019-06-19 Thread Scott Harding 
Hi all,
I'm new to Beagle and am trying to get started. I went to the 
https://beagleboard.org/blue and watching a video called "Getting Started". 
It mentions a web link on https://beagleboard.org/blue called "Getting 
Started" but I don't see the link. I also went to FAQ and it says go to  
http://192.168.8.1:3000 but this says "
This site can’t be reached

*192.168.8.1* took too long to respond."


Are there any other getting started tips?

thank you,

Scott

-- 
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/c1045444-d413-4ad1-81f9-f3ed30e72ccc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Bluetooth Connectivity Issues

2019-06-19 Thread Aravind Reddy 
Hello all ,

Got my new BBBW yesterday and I just went over an article of setting up 
beagle box wireless and i am successfully able to enable wifi and ping.. 
now trying to enable Bluetooth but i encounter the following issues, any 
help will be greatly appreciated.
Here are the steps i followed :
[bluetooth]# scan on
Discovery started
[CHG] Controller 6C:C3:74:E7:89:DA Discovering: yes
[NEW] Device 53:93:6D:6D:12:AF 53-93-6D-6D-12-AF
[NEW] Device D0:81:7A:8A:F4:C4 Aravind Reddy’s iPhone

[bluetooth]# pair D0:81:7A:8A:F4:C4
Attempting to pair with D0:81:7A:8A:F4:C4
[CHG] Device D0:81:7A:8A:F4:C4 Connected: yes
Request confirmation
[agent] Confirm passkey 018547 (yes/no): yes
[CHG] Device D0:81:7A:8A:F4:C4 Modalias: bluetooth:v004Cp7005d0C30
[CHG] Device D0:81:7A:8A:F4:C4 UUIDs: -deca-fade-deca-deafdecacafe
[CHG] Device D0:81:7A:8A:F4:C4 UUIDs: 1000--1000-8000-00805f9b34fb
[CHG] Device D0:81:7A:8A:F4:C4 UUIDs: 110a--1000-8000-00805f9b34fb
[CHG] Device D0:81:7A:8A:F4:C4 UUIDs: 110c--1000-8000-00805f9b34fb
[CHG] Device D0:81:7A:8A:F4:C4 UUIDs: 110e--1000-8000-00805f9b34fb
[CHG] Device D0:81:7A:8A:F4:C4 UUIDs: 1116--1000-8000-00805f9b34fb
[CHG] Device D0:81:7A:8A:F4:C4 UUIDs: 111f--1000-8000-00805f9b34fb
[CHG] Device D0:81:7A:8A:F4:C4 UUIDs: 112f--1000-8000-00805f9b34fb
[CHG] Device D0:81:7A:8A:F4:C4 UUIDs: 1132--1000-8000-00805f9b34fb
[CHG] Device D0:81:7A:8A:F4:C4 UUIDs: 1200--1000-8000-00805f9b34fb
[CHG] Device D0:81:7A:8A:F4:C4 UUIDs: 02030302-1d19-415f-86f2-22a2106a0a77
[CHG] Device D0:81:7A:8A:F4:C4 ServicesResolved: yes
[CHG] Device D0:81:7A:8A:F4:C4 Paired: yes
Pairing successful
[CHG] Device D0:81:7A:8A:F4:C4 ServicesResolved: no
[CHG] Device D0:81:7A:8A:F4:C4 Connected: no
[bluetooth]# pair D0:81:7A:8A:F4:C4
Attempting to pair with D0:81:7A:8A:F4:C4
Failed to pair: org.bluez.Error.AlreadyExists
[bluetooth]# connect D0:81:7A:8A:F4:C4
Attempting to connect to D0:81:7A:8A:F4:C4
*Failed to connect: org.bluez.Error.Failed *

Adding to the above, it holds the connection for a second when i try to 
connect to my mobile device.
[CHG] Device D0:81:7A:8A:F4:C4 Connected: yes
[Aravind Reddy’s iPhone]# 

and reverts back to 
[CHG] Device D0:81:7A:8A:F4:C4 Connected: yes
[CHG] Device D0:81:7A:8A:F4:C4 Connected: no
[CHG] Device D0:81:7A:8A:F4:C4 Connected: yes
[CHG] Device D0:81:7A:8A:F4:C4 Connected: no
[CHG] Device D0:81:7A:8A:F4:C4 Connected: yes
[CHG] Device D0:81:7A:8A:F4:C4 Connected: no
[bluetooth]#

Thanks 
Aravind

-- 
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/0dd2c612-4044-4424-ac38-82c30f3897d3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: BBB wireless eMMC flash problem

2019-06-19 Thread Jeff Albrecht 
On Tuesday, June 18, 2019 at 8:22:20 PM UTC-7, Jeff Albrecht wrote:
>
> Seems my BBB wireless quit booting from eMMC. I fired up bone-debian-9.5-
> iot-armhf-2018-10-07-4gb.img from SD card and set uEnv.txt to flash. Fail 
> :-(
>
> The following appears to be the offending part of the log. Here is the entire 
> log  on my pastebin as captured by 
> TeraTerm.
>
> Is there anything to try to initialize / format / recover for flashing the 
> emmc?
>
>
In this thread 
 
@RobertCNelson suggests to try old image. Here is the log from that 
unsuccessful attempt; 

U-Boot SPL 2014.04-00014-g47880f5 (Apr 22 2014 - 13:23:54)
reading args
spl_load_image_fat_os: error reading image args, err - -1
reading u-boot.img
reading u-boot.img




U-Boot 2014.04-00014-g47880f5 (Apr 22 2014 - 13:23:54)


I2C:   ready
DRAM:  512 MiB
NAND:  0 MiB
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
*** Warning - readenv() failed, using default environment


Net:not set. Validating first E-fuse MAC
Could not get PHY for cpsw: addr 0
cpsw, usb_ether
Hit any key to stop autoboot:  0
gpio: pin 53 (gpio 53) value is 1
mmc0 is current device
gpio: pin 54 (gpio 54) value is 1
SD/MMC found on device 0
reading uEnv.txt
1672 bytes read in 5 ms (326.2 KiB/s)
gpio: pin 55 (gpio 55) value is 1
Loaded environment from uEnv.txt
Importing environment from mmc ...
Checking if uenvcmd is set ...
gpio: pin 56 (gpio 56) value is 1
Running uenvcmd ...
reading zImage
4103240 bytes read in 227 ms (17.2 MiB/s)
reading initrd.img
2957458 bytes read in 166 ms (17 MiB/s)
reading /dtbs/am335x-boneblack.dtb
25926 bytes read in 9 ms (2.7 MiB/s)
Kernel image @ 0x8200 [ 0x00 - 0x3e9c48 ]
## Flattened Device Tree blob at 8800
   Booting using the fdt blob at 0x8800
   Using Device Tree in place at 8800, end 88009545


Starting kernel ...


Uncompressing Linux... done, booting the kernel.
[0.378382] omap2_mbox_probe: platform not supported
[0.532986] tps65217-bl tps65217-bl: no platform data provided
[0.596730] bone-capemgr bone_capemgr.9: slot #0: No cape found
[0.633839] bone-capemgr bone_capemgr.9: slot #1: No cape found
[0.670947] bone-capemgr bone_capemgr.9: slot #2: No cape found
[0.708056] bone-capemgr bone_capemgr.9: slot #3: No cape found
[0.722735] bone-capemgr bone_capemgr.9: slot #6: BB-BONELT-HDMIN 
conflict P8.45 (#5:BB-BONELT-HDMI)
[0.732349] bone-capemgr bone_capemgr.9: slot #6: Failed verification
[0.739097] bone-capemgr bone_capemgr.9: loader: failed to load slot-6 BB
-BONELT-HDMIN:00A0 (prio 2)
[0.756676] omap_hsmmc mmc.5: of_parse_phandle_with_args of 'reset' 
failed
[0.819666] pinctrl-single 44e10800.pinmux: pin 44e10854 already 
requested by 44e10800.pinmux; cannot claim for gpio-leds.8
[0.831347] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.8) status -
22
[0.838647] pinctrl-single 44e10800.pinmux: could not request pin 21 on 
device pinctrl-single
[1.042656] Unhandled fault: external abort on non-linefetch (0x1008) at 
0xe089c000
[1.050780] Internal error: : 1008 [#1] SMP THUMB2
[1.055850] Modules linked in:
[1.059092] CPU: 0Not tainted  (3.8.13-bone50 #1)
[1.064436] PC is at cpsw_probe+0x348/0x960
[1.068858] LR is at ioremap_page_range+0x95/0xf8
[1.073827] pc : []lr : []psr: a033
[1.073827] sp : df071e18  ip :   fp : df0d3400
[1.085950] r10: c081de48  r9 : de28d000  r8 : de28d590
[1.091457] r7 : de28d000  r6 : de28d540  r5 :   r4 : e089c000
[1.098334] r3 : 8000  r2 :   r1 : e089d000  r0 : e089c000
[1.105226] Flags: NzCv  IRQs on  FIQs on  Mode SVC_32  ISA Thumb  
Segment kernel
[1.113114] Control: 50c5387d  Table: 9e284019  DAC: 0015
[1.119181] Process swapper/0 (pid: 1, stack limit = 0xdf070240)
[1.125518] Stack: (0xdf071e18 to 0xdf072000)
[1.130118] 1e00:   
 c00b5629
[1.138754] 1e20: c086b9b8 c086b9b8 de28d540 de28d298 df0d3410 de5fc8c8 
 df071e90
[1.147395] 1e40: df071e90 c00fdd53    c086b9b8 
de5fc8c8 de5f9ec0
[1.156038] 1e60: de5fc8c8 c00fdc8f de5fc8c8  df071e90 de5fc948 
df0d5d48 c00fe507
[1.164673] 1e80: df0494b8 c00492af  df0d3444 0020 0008 
df0d3410 c09189ec
[1.173305] 1ea0: df0d3410 c088aa58  c0800925 0100 c081de48 
 c02c6e19
[1.181935] 1ec0: c02c6e09 c02c62bb  df0d3410 c088aa58 df0d3444 
 c02c641b
[1.190559] 1ee0: c088aa58 c02c63d1  c02c53ef df049478 df0ce600 
c088aa58 c087fe90
[1.199196] 1f00: de5f9ec0 c02c5daf c072dc7c c088aa58 c088aa58 df07 
c08ab580 
[1.207829] 1f20: c0800925 c02c671d  c080b080 df07 c08ab580 
 c0800925
[1.216463] 1f40: 0100 c000867f 0007 0007 c0863b18 c080b07c 
c080b080 0007
[1.227702]

Re: [beagleboard] Breakout Board for Beagle Board X15

2019-06-19 Thread Daniel Block 
Yes.  Glad you can use the board.  I have attached the EagleCAD library for
the Hirose connector that I made.  This library has two other parts for a
different board I was working on at the time, so ignore those.

Dan

On Tue, Jun 18, 2019 at 9:23 PM Calvin Slater 
wrote:

> Wow Dan!
>
> This is perfect. I was looking for something like this.
>
> Did you create the Hirose header footprints yourself? They are very nice.
>
> Calvin
>
>
>
> On Wed, 12 Jun 2019 at 09:18, Daniel Block  wrote:
>
>> I thought I would post this to the BB x15 group in case some else would
>> find this board helpful.  I created this board in EagleCAD 7.  It breaks
>> out most of the PINs of the 4 expansion connectors of the BBx15.  Hopefully
>> the schematic is documented enough that you can solder up the board
>> yourself.  If you want to use the board to just break out the expansion
>> connectors you do not need to solder any of the chips except for the  7
>> SN74CBTD16211DL chips that are level converters that would allow 5V
>> signals.
>>
>> Dan
>>
>> --
>> 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/37a0a372-58db-4fb0-8c0b-c15b9e66bb36%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/CAN%2BNdyi13jbYrXbtNNmu7S284cXowxaaczVUsVxCsZ_wX9gctQ%40mail.gmail.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/CAMTPGNZsM9cW2GDAUuzEKWPYKzVrKque3G%2BzO-N0goS3YYDz%2BA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


custom7.lbr
Description: Binary data

Re: [beagleboard] How use SGX / PowerVR on BBB in 2019 ?

2019-06-19 Thread labbe . mat 
Hi Everyone,

I want to test whether 2D acceleration makes QtWebEngine (Chromium) 
reactive enough on the BBB.
I tried Rémi's procedure, and I can run the OGLES2 demos and kmscube. 
However, when I try to use a QWebEngineView in a Qt application, I get a 
segmentation fault (other Qt apps are fine).

I checked with ldd that my app is linked with libgbm2 and not libgbm1, so 
that does not seem to be the problem.

Has anyone tried QtWebEngine with this setup? Could it be that the debian 
package for QtWebEngine is incompatible?

Best regards,
Mathieu

Le jeudi 2 mai 2019 15:05:28 UTC+2, devm...@gmail.com a écrit :
>
> Hi Bora,
>
> Thank you very much for your feedback. I am very happy to know that my 
> article was able to help you!
>
> Best regards,
> Rémi
>
> Le mercredi 1 mai 2019 03:07:08 UTC+2, Bora a écrit :
>>
>> Hey Remi,
>>
>> I believe you solved this issue since you already posted this article in 
>> the wiki:
>>
>> https://elinux.org/BeagleBoneBlack/SGX_%2B_Qt_EGLFS_%2B_Weston
>>
>> I used your article to enable EGLFS support for Qt on my BeagleBone 
>> Black. Many thanks for the clear and detailed article!
>>
>> Best regards
>> Bora
>>
>> On Thursday, March 28, 2019 at 7:47:49 PM UTC+1, devm...@gmail.com wrote:
>>>
>>> So kernel "overlays" are broken, upgrade your version of u-boot and

 add this define in /boot/uEnv.txt

 sudo /opt/scripts/tools/developers/update_bootloader.sh

 enable_uboot_overlays=1
 uboot_overlay_addr4=/lib/firmware/CAPE-LVDS-1024-00A0.dtbo
 disable_uboot_overlay_video=1

 Then reboot and run:

 sudo /opt/scripts/tools/version.sh

 to see if everything is happy..


>>> Ok perfect, that work very fine! Thanks
>>>
>>>
>>> That is strange, i never had libgbm-dev installed and got kmscube to 
 work..
>>>
>>> When I execute 'autogen.sh', the script notice me to get libgbm-dev:
>>>
>>> git clone git://git.ti.com/glsdk/kmscube.git
>>>
>>> cd kmscube/
>>>
>>> ./autogen.sh
>>> ...
>>> checking for DRM... yes
>>> checking for GBM... no
>>> configure: error: Package requirements (gbm) were not met:
>>>
>>> No package 'gbm' found
>>>
>>> Consider adjusting the PKG_CONFIG_PATH environment variable if you
>>> installed software in a non-standard prefix.
>>>
>>> Alternatively, you may set the environment variables GBM_CFLAGS
>>> and GBM_LIBS to avoid the need to call pkg-config.
>>> See the pkg-config man page for more details.
>>>
>>>
>>>  
>>> But it's very strange, because if I do just: apt remove libgbm1 --purge
>>> I can execute normaly kmscube but I have a black screen.
>>> root@beaglebone ~ # ll /usr/lib/libgb*
>>> lrwxrwxrwx 1 root root   15 Mar 26 18:40 /usr/lib/libgbm.so -> 
>>> libgbm.so.2.0.0
>>> lrwxrwxrwx 1 root root   15 Mar 26 18:40 /usr/lib/libgbm.so.2 -> 
>>> libgbm.so.2.0.0
>>> -rw-r--r-- 1 root root 9.5K Mar 26 18:40 /usr/lib/libgbm.so.2.0.0
>>> root@beaglebone ~ # whereis kmscube
>>> kmscube: /usr/bin/kmscube
>>> root@beaglebone ~ # ldd /usr/bin/kmscube
>>> linux-vdso.so.1 (0xbeff6000)
>>> libm.so.6 => /lib/arm-linux-gnueabihf/libm.so.6 (0xb6f27000)
>>> libdrm.so.2 => /usr/lib/arm-linux-gnueabihf/libdrm.so.2 
>>> (0xb6f0b000)
>>> libgbm.so.2 => /usr/lib/libgbm.so.2 (0xb6ef8000)
>>> libdl.so.2 => /lib/arm-linux-gnueabihf/libdl.so.2 (0xb6ee5000)
>>> libEGL.so.1 => /usr/lib/libEGL.so.1 (0xb6ed3000)
>>> libIMGegl.so.1 => /usr/lib/libIMGegl.so.1 (0xb6eae000)
>>> libdrm_omap.so.1 => 
>>> /usr/lib/arm-linux-gnueabihf/libdrm_omap.so.1 (0xb6e9b000)
>>> libGLESv2.so.2 => /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2 
>>> (0xb6e7d000)
>>> libsrv_um.so.1 => /usr/lib/libsrv_um.so.1 (0xb6e46000)
>>> libc.so.6 => /lib/arm-linux-gnueabihf/libc.so.6 (0xb6d58000)
>>> /lib/ld-linux-armhf.so.3 (0xb6fc3000)
>>> libudev.so.1 => /lib/arm-linux-gnueabihf/libudev.so.1 
>>> (0xb6d41000)
>>> libwayland-server.so.0 => 
>>> /usr/lib/arm-linux-gnueabihf/libwayland-server.so.0 (0xb6d26000)
>>> libffi.so.6 => /usr/lib/arm-linux-gnueabihf/libffi.so.6 
>>> (0xb6d1)
>>> libdbm.so.1 => /usr/lib/libdbm.so.1 (0xb6cfe000)
>>> libpthread.so.0 => /lib/arm-linux-gnueabihf/libpthread.so.0 
>>> (0xb6cda000)
>>> libGLdispatch.so.0 => 
>>> /usr/lib/arm-linux-gnueabihf/libGLdispatch.so.0 (0xb6c5c000)
>>> librt.so.1 => /lib/arm-linux-gnueabihf/librt.so.1 (0xb6c46000)
>>> libgcc_s.so.1 => /lib/arm-linux-gnueabihf/libgcc_s.so.1 
>>> (0xb6c1d000)
>>> After the command "apt autoremove", the kmscube is displayed correctly 
>>> on the screen!
>>>
>>>  
>>>
>>> Unfortunately, if we use we ti-sgx-common-ddk-um package's, we will have 
 conflicts with libegl1-mesa-dev and libgles2-mesa-dev packages and the 
 libgbm1 package will be reinstall... 
>>>
>>> Ah crap, so the reason i split those files into a 2nd common package
 was to fix that possibility..

 Fixed with:

[beagleboard] AM3352: RTL8188 USB WiFi device

2019-06-19 Thread 'Sivaraj Arigovindan' via BeagleBoard 


root@beaglebone:~# [ 93.905101] usb 2-1.5: new high-speed USB device number 
4 using musb-hdrc
[ 94.026761] usb 2-1.5: New USB device found, idVendor=0bda, idProduct=8179
[ 94.034025] usb 2-1.5: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[ 94.041757] usb 2-1.5: Product: 802.11n NIC
[ 94.046186] usb 2-1.5: Manufacturer: Realtek
[ 94.066132] Chip Version Info: 
CHIP_8188E_Normal_Chip_TSMC_D_CUT_1T1R_RomVer(0)
[ 95.220556] r8188eu 2-1.5:1.0: Direct firmware load for 
rtlwifi/rtl8188eufw.bin failed with error -2
[ 95.230293] r8188eu 2-1.5:1.0: Falling back to user helper
[ 95.257900] r8188eu 2-1.5:1.0: Firmware rtlwifi/rtl8188eufw.bin not 
available
[ 95.265566] MAC Address = 40:a5:ef:d6:1a:4c
[ 95.323135] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 95.362117] usb 2-1.5: USB disconnect, device number 4
[ 95.370587] R8188EU: ERROR indicate disassoc



root@beaglebone:~# 
root@beaglebone:~#

-- 
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/523a56e7-16fe-4d73-8f43-e78073b36613%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] uEnv.txt not taken into account on debian + 4.19-ti-rt

2019-06-19 Thread Igor Jędrzejczak 
Hi,

I've installed debian + kernal 4.19-ti-rt on my BBB according to this 
instruction: 
https://www.digikey.com/eewiki/display/linuxonarm/BeagleBone+Black

After I finally started the system I'm trying now to change pins roles to 
start using PRU. When I change /boot/uEnv.txt file to enable overlays and 
select which one to use, it doesn't seem to work at all - after reboot 
pins' roles remain default, no PRU pins enabled. What am I doing wrong?

/opt/scripts/tools/version.sh
git:/opt/scripts/:[15198b3b7ff40ef517a305eeb7cd20e57f18d37a]
eeprom:[A335BNLTEIA05115BBBK0079]
model:[TI_AM335x_BeagleBone_Black]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2019.04-dirty]:[location: 
dd MBR]
kernel:[4.19.31-ti-rt-r19]
uboot_overlay_options:[enable_uboot_overlays=1]
uboot_overlay_options:[disable_uboot_overlay_video=1]
uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-19
-TI-00A0.dtbo]
pkg check: to individually upgrade run: [sudo apt install --only-upgrade 
]
pkg:[bb-cape-overlays]:[4.4.20190610.0-0rcnee0~stretch+20190610]
WARNING:pkg:[bb-wl18xx-firmware]:[NOT_INSTALLED]
pkg:[kmod]:[23-2rcnee1~stretch+20171005]
WARNING:pkg:[librobotcontrol]:[NOT_INSTALLED]
pkg:[firmware-ti-connectivity]:[20180825+dfsg-1rcnee1~stretch+20181217]
groups:[debian : debian adm kmem dialout cdrom floppy audio dip video 
plugdev users systemd-journal i2c netdev gpio pwm eqep bluetooth admin spi 
tisdk weston-launch xenomai cloud9ide]
cmdline:[console=ttyO0,115200n8 root=UUID=702af096-c19d-4ce1-ac79-
0ad255340345 ro rootfstype=ext4 rootwait]
dmesg | grep remote
[2.715739] remoteproc remoteproc0: wkup_m3 is available
[2.717172] remoteproc remoteproc1: 4a334000.pru is available
[2.717809] remoteproc remoteproc2: 4a338000.pru is available
[3.051770] remoteproc remoteproc0: powering up wkup_m3
[3.109595] remoteproc remoteproc0: Booting fw image am335x-pm-firmware.
elf, size 217168
[3.122818] remoteproc remoteproc0: remote processor wkup_m3 is now up
dmesg | grep pru
[2.717172] remoteproc remoteproc1: 4a334000.pru is available
[2.717362] pru-rproc 4a334000.pru: PRU rproc node pru@4a334000 probed 
successfully
[2.717809] remoteproc remoteproc2: 4a338000.pru is available
[2.718000] pru-rproc 4a338000.pru: PRU rproc node pru@4a338000 probed 
successfully
dmesg | grep pinctrl-single
[1.229997] pinctrl-single 44e10800.pinmux: 142 pins, size 568
dmesg | grep gpio-of-helper
[1.232540] gpio-of-helper ocp:cape-universal: ready
lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
END


/boot/uEnv.txt
uname_r=4.19.31-ti-rt-r19
uuid=702af096-c19d-4ce1-ac79-0ad255340345


enable_uboot_overlays=1


disable_uboot_overlay_video=1


uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-19-TI-00A0.dtbo


Cheers


-- 
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/3bcbbc1d-811d-49e3-a778-6d2164ba8f83%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Tuning the watchdog timer - correct place?

2019-06-19 Thread Hugh Frater 
Yep, I did verify that. You need to use the child_process.execSync()
function to call the tuning binary from Node.js because you must wait for
the tuning to complete before opening the watchdog device from within your
Node.js application. I know, using synchronous functions inside an
asynchronous environment like Node.js is bad practice, blah blah blah - It
works, it's good enough for me.

Verification of the timeout change is done by looking at the timeout and
timeleft entries in:

/sys/devices/platform/ocp/44e35000.wdt/watchdog/watchdog0

For example, on first boot:

debian@beaglebone:/sys/devices/platform/ocp/44e35000.wdt/watchdog/watchdog0$
cat timeout
60

Then I start my Node.js application that in turn calls the watchdog tuning
binary then sets up a 1 second write to the watchdog device:

debian@beaglebone:/sys/devices/platform/ocp/44e35000.wdt/watchdog/watchdog0$
cat timeout
5

debian@beaglebone:/sys/devices/platform/ocp/44e35000.wdt/watchdog/watchdog0$
cat timeleft
4

If I Ctrl-C my Node.js application (simulating a lockup/it crashes etc)
then I can watch the timeout value count down and the system reboots.

I hope that helps...



On Tue, 18 Jun 2019 at 17:40, 'Mark Lazarewicz' via BeagleBoard <
beagleboard@googlegroups.com> wrote:

> Did you verify the time out changed?
> If so how?
>
>
> Sent from Yahoo Mail on Android
> 
>
> On Tue, Jun 18, 2019 at 7:55 AM, Hugh Frater
>  wrote:
> Update: The kernel watchdog driver support tuning the timout through ioctl
> calls. A quick and dirty bit of C code:
>
>
> int main()
> {
> int fd = open("/dev/watchdog", O_WRONLY);
> int timeout = 5;
> ioctl(fd, WDIOC_SETTIMEOUT, );
> printf("Setting timeout to %d seconds\n", timeout);
> close(fd);
> return 0;
> }
>
> Will tune the watchdog. I use node.js' child_process to call the above
> code (when compiled, obviously), if my node.js app crashes then the BBB
> will reboot. Perfect
>
> On Monday, 3 June 2019 13:07:49 UTC+1, Hugh Frater wrote:
>
> Where does one go to tune the watchdog timer? Is it a
> kernel-recompilation-required thing, or can it be done through uBoot?
>
> Or should I just use my PRU code to tune the watchdog control register
> when it boots? This would be the easiest option for me, if someone can
> point me at the correct area if the AM335XTRM? I had a look in there and
> couldn't find the correct registers.
>
> I'd like it to run about 10 seconds if possible for my application.
>
> --
> 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/ab8ea583-ab9a-4017-a89f-6bd8127eaf47%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 a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/ovGQSAXqwBE/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/952566089.2906417.1560876023480%40mail.yahoo.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/CAPm6wa11-z9GOguf%3DdddpFob1PsVZAi4U%2BMcmv80gQ-W6duydg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.