Re: [beagleboard] No I2S signals from the BeagleBone Black

[Yiling Cao]

can you send us the audio part of schematics?

have you modified kernel? 2018-oct-5 says kernel not modified.

On Wed, Aug 14, 2019 at 12:16 AM  wrote:

>
> I am unable to get the I2S signals from the beaglebone. Below are the
> things I did.
>
>1. I first disabled the HDMI audio as described here
>.
>2. I am using the P9.31 (SCLK), P9.28 (Data0) and P9.29(FSX/WS).
>Running sudo /opt/scripts/tools/version.sh gives the following.
>
> debian@beaglebone:/boot$ sudo /opt/scripts/tools/version.sh
> [sudo] password for debian:
> git:/opt/scripts/:[1aa73453b2c980b75e31e83dab7dd8b6696f10c7]
> eeprom:[A335BNLT00C02315BBBK4ACD]
> model:[TI_AM335x_BeagleBone_Black]
> dogtag:[BeagleBoard.org Debian Image 2018-10-07]
> bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 
> 2018.09-2-g0b54a51eee]:[location: dd MBR]
> kernel:[4.14.71-ti-r80]
> nodejs:[v6.14.4]
> uboot_overlay_options:[enable_uboot_overlays=1]
> uboot_overlay_options:[uboot_overlay_addr0=/lib/firmware/BB-BONE-AUDI-02.dtbo]
> uboot_overlay_options:[disable_uboot_overlay_audio=1]
> uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-14-TI-00A0.dtbo]
> uboot_overlay_options:[enable_uboot_cape_universal=1]
> pkg check: to individually upgrade run: [sudo apt install --only-upgrade 
> ]
> pkg:[bb-cape-overlays]:[4.4.20180928.0-0rcnee0~stretch+20180928]
> pkg:[bb-wl18xx-firmware]:[1.20180517-0rcnee0~stretch+20180517]
> pkg:[kmod]:[23-2rcnee1~stretch+20171005]
> pkg:[librobotcontrol]:[1.0.3-git20181005.0-0rcnee0~stretch+20181005]
> pkg:[firmware-ti-connectivity]:[20170823-1rcnee1~stretch+20180328]
> groups:[debian : debian adm kmem dialout cdrom floppy audio dip video plugdev 
> users systemd-journal i2c bluetooth netdev cloud9ide gpio pwm eqep admin spi 
> tisdk weston-launch xenomai]
> cmdline:[console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 
> root=/dev/mmcblk1p1 ro rootfstype=ext4 rootwait coherent_pool=1M 
> net.ifnames=0 quiet]
> dmesg | grep pinctrl-single
> [1.107553] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 
> 568
> dmesg | grep gpio-of-helper
> [1.119437] gpio-of-helper ocp:cape-universal: ready
> END
>
>
>1. Running perl /opt/scripts/device/bone/show-pins.pl gives the
>following.
>
> debian@beaglebone:/boot$ perl /opt/scripts/device/bone/show-pins.pl
> P8.25 / eMMC d00  U7 fast rx  up  1 mmc 1 d0 
> mmc@481d8000 (pinmux_emmc_pins)
> P8.24 / eMMC d11  V7 fast rx  up  1 mmc 1 d1 
> mmc@481d8000 (pinmux_emmc_pins)
> P8.05 / eMMC d22  R8 fast rx  up  1 mmc 1 d2 
> mmc@481d8000 (pinmux_emmc_pins)
> P8.06 / eMMC d33  T8 fast rx  up  1 mmc 1 d3 
> mmc@481d8000 (pinmux_emmc_pins)
> P8.23 / eMMC d44  U8 fast rx  up  1 mmc 1 d4 
> mmc@481d8000 (pinmux_emmc_pins)
> P8.22 / eMMC d55  V8 fast rx  up  1 mmc 1 d5 
> mmc@481d8000 (pinmux_emmc_pins)
> P8.03 / eMMC d66  R9 fast rx  up  1 mmc 1 d6 
> mmc@481d8000 (pinmux_emmc_pins)
> P8.04 / eMMC d77  T9 fast rx  up  1 mmc 1 d7 
> mmc@481d8000 (pinmux_emmc_pins)
> P8.19  8 U10 fast rx down 7 gpio 0.22
> ocp/P8_19_pinmux (pinmux_P8_19_default_pin)
> P8.13  9 T10 fast rx down 7 gpio 0.23
> ocp/P8_13_pinmux (pinmux_P8_13_default_pin)
> P8.14 10 T11 fast rx down 7 gpio 0.26
> ocp/P8_14_pinmux (pinmux_P8_14_default_pin)
> P8.17 11 U12 fast rx down 7 gpio 0.27
> ocp/P8_17_pinmux (pinmux_P8_17_default_pin)
> P8.12 12 T12 fast rx down 7 gpio 1.12
> ocp/P8_12_pinmux (pinmux_P8_12_default_pin)
> P8.11 13 R12 fast rx down 7 gpio 1.13
> ocp/P8_11_pinmux (pinmux_P8_11_default_pin)
> P8.16 14 V13 fast rx down 7 gpio 1.14
> ocp/P8_16_pinmux (pinmux_P8_16_default_pin)
> P8.15 15 U13 fast rx down 7 gpio 1.15
> ocp/P8_15_pinmux (pinmux_P8_15_default_pin)
> P9.15 16 R13 fast rx down 7 gpio 1.16
> ocp/P9_15_pinmux (pinmux_P9_15_default_pin)
> P9.23 17 V14 fast rx down 7 gpio 1.17
> ocp/P9_23_pinmux (pinmux_P9_23_default_pin)
> P9.14 18 U14 fast rx down 7 gpio 1.18
> ocp/P9_14_pinmux (pinmux_P9_14_default_pin)
> P9.16 19 T14 fast rx down 7 gpio 1.19
> ocp/P9_16_pinmux (pinmux_P9_16_default_pin)
> P9.11 28 T17 fast rx down 7 gpio 0.30
> ocp/P9_11_pinmux (pinmux_P9_11_default_pin)
> P9.13 29 U17 fast rx down 7 gpio 0.31
> ocp/P9_13_pinmux (pinmux_P9_13_default_pin)
> P9.12  

[beagleboard] Re: follow-up on mjpg streamer video manipulation on BLUE

[Daniyal Ansari]

On Thu, Aug 1, 2019 at 5:09 PM Daniyal Ansari 
wrote:

> It works!
> Thank you.
>
> https://gist.github.com/ansarid/b820026d2fd169fe729e8e8b651eba67
>
> On Thu, Aug 1, 2019 at 4:25 PM Daniyal Ansari 
> wrote:
>
>> Testing that now.
>> Also added beagleboard@googlegroups.com
>>
>> On Thu, Aug 1, 2019 at 3:54 PM Jason Kridner  wrote:
>>
>>> It is in the package feeds now, but not installed by default.
>>>
>>> sudo apt update
>>> sudo apt install mjpg-streamer-opencv-python
>>>
>>> Would be awesome if we had beagleboard@googlegroups.com in copy. Do you
>>> mind if I just forward this thread?
>>>
>>> On Thu, Aug 1, 2019 at 3:38 PM David Malawey  wrote:
>>>
 Hi Jason,

 I'm writing the lab together with Daniyal to instruct students on using
 openCV to process video stream in realtime.   We need to be able to view
 our images in realtime after performing a filter, etc. using openCV.
 Daniyal is helping me put this tutorial together, and we believe you
 planned to make an update to the base image for the Blue to enable this.

 I think we are waiting on an OpenCV module to be added to the
 preinstalled mjpg-streamer before we can produce a live output of modified
 images.  Is this something you can add on your end and is it feasible to
 implement by next week?  My time is getting compressed to finish lab
 instructions for the fall, so I will decide this week if I should keep this
 lab or remove it from the lessons.

 Cheers,

 David Malawey, MS ME
 ETID Technical Lab Coordinator
 mala...@tamu.edu

>>>
>>>
>>> --
>>> https://beagleboard.org/about
>>>
>>

-- 
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/CAK6ueFnXNcRBb02q3tgQ0zg%3DE_oTNexXmcTfDptknPjvH8KMew%40mail.gmail.com.

Re: [beagleboard] name resolution failed BBB wireless

[Jim F]

I think you messed up in step 1.

/etc/resolv.conf should contain at least one line in the form :

nameserver 8.8.8.8

In order to separate the different components for debugging, recommend you
try ping 8.8.8.8 and see if that works, first.

J



On Tue, Aug 13, 2019, 11:42 AM anish kumar  wrote:

> I am trying to setup my beaglebone black wireless for accessing my
> pc(windows-7) internet using usb-ethernet. Below is the steps i have
> performed
> 1.) add dns server in file edit /etc/network/interfaces
>  dns-nameservers 8.8.8.8
> 2.) add default gateway [i have to do this every time beaglebone is
> reset/restarted or power cycled]
>  sudo route add default gateway 192.168.7.1
> 3.) on pc side, the linux-rndis has following settings;
>  ipv4 - 192.168.7.1
>   sub  - 255.255.255.0
>   dns  - 8.8.8.8
> 4.) update date and time
>
> Now, when trying to ping www.google.com i get *"temporary failure in name
> resolution"*
>
> I am using bone-debian-9.5-lxqt-armhf-2018-10-07-4gb.img.xz
>
>
> --
> 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/ed4abdf1-ab24-4fc9-9efb-d05e09cabd54%40googlegroups.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/CAGS%2B2h_rZGECp8qgZBCN0DeLqPcC7LiXnqV4sQAgnZSZcY%3D8LQ%40mail.gmail.com.

[beagleboard] Re: follow-up on mjpg streamer video manipulation on BLUE

[Daniyal Ansari]

Testing that now.
Also added beagleboard@googlegroups.com

On Thu, Aug 1, 2019 at 3:54 PM Jason Kridner  wrote:

> It is in the package feeds now, but not installed by default.
>
> sudo apt update
> sudo apt install mjpg-streamer-opencv-python
>
> Would be awesome if we had beagleboard@googlegroups.com in copy. Do you
> mind if I just forward this thread?
>
> On Thu, Aug 1, 2019 at 3:38 PM David Malawey  wrote:
>
>> Hi Jason,
>>
>> I'm writing the lab together with Daniyal to instruct students on using
>> openCV to process video stream in realtime.   We need to be able to view
>> our images in realtime after performing a filter, etc. using openCV.
>> Daniyal is helping me put this tutorial together, and we believe you
>> planned to make an update to the base image for the Blue to enable this.
>>
>> I think we are waiting on an OpenCV module to be added to the
>> preinstalled mjpg-streamer before we can produce a live output of modified
>> images.  Is this something you can add on your end and is it feasible to
>> implement by next week?  My time is getting compressed to finish lab
>> instructions for the fall, so I will decide this week if I should keep this
>> lab or remove it from the lessons.
>>
>> Cheers,
>>
>> David Malawey, MS ME
>> ETID Technical Lab Coordinator
>> mala...@tamu.edu
>>
>
>
> --
> https://beagleboard.org/about
>

-- 
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/CAK6ueF%3DZv-Jq53gZX_XKUt5Y%2BSAYEiHbn%2Ba3oG_e8nkpWysbJQ%40mail.gmail.com.

[beagleboard] CANBus Cape availability

[thenbomr]

Hi All.

Does anyone know of a source for the CANbuscape described in the BeagleBone 
support website, allegedly built by Beagleboard Toys?
https://elinux.org/CAN_Bus_Cape_RevA
What I really want is the isolation provided by the transceiver, and any 
other BBB compatible board that has the same or equivalent chip would be 
adequate to me. There are a smallish number of CANbus capes for the BBB 
(actually BBG, in my case; I assume there is no compatibility issue), and 
all of the ones I've seen offer little or no isolation from the CAN bus. 
There is the design at 

https://www.thomas-wedemeyer.de/beaglebone-canbus-python.html

which has an isolating transceiver. HAs anyone used that design to build up 
a cape in real hardware? Any available for sale?

   ---   rod.

-- 
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/2497b9b3-c64d-42d6-9386-fe3076b24121%40googlegroups.com.

[beagleboard] I can't ping to default gateway over usb connection

[Jin Tak Lee]

My BBB is connected to my Windows 10 Host pc over usb.
It is currently not pinging to default gw 192.168.7.1 even after I typed 
'route add default gw 192.168.7.1'.
Here is my connection setting over usb.

usb0: flags=4163  mtu 1500
inet 192.168.7.2  netmask 255.255.255.252  broadcast 192.168.7.3
inet6 fe80::76e1:82ff:fe8d:c9a9  prefixlen 64  scopeid 0x20
ether 74:e1:82:8d:c9:a9  txqueuelen 1000  (Ethernet)
RX packets 4093  bytes 471965 (460.9 KiB)
RX errors 0  dropped 6  overruns 0  frame 0
TX packets 3354  bytes 506179 (494.3 KiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Can anyone explain why ping doesn'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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/fffaf264-8c4f-452c-a764-ea04fc846a5a%40googlegroups.com.

[beagleboard] I'm having a trouble in setting the

[takitaki228]

My BBB is connected to my Windows 10 host PC via USB port.
I'm currently trying to direct the IP address from my Beagle board through 
my PC by adding default gateway '192.168.7.1'. Thus I typed a command 
'route add default gw 192.168.7.1'
The problem is that I still can't ping to '8.8.8.8'. Here is my network 
setting on usb0

usb0: flags=4163  mtu 1500
inet 192.168.7.2  netmask 255.255.255.252  broadcast 192.168.7.3
inet6 fe80::76e1:82ff:fe8d:c9a9  prefixlen 64  scopeid 0x20
ether 74:e1:82:8d:c9:a9  txqueuelen 1000  (Ethernet)
RX packets 809  bytes 144139 (140.7 KiB)
RX errors 0  dropped 4  overruns 0  frame 0
TX packets 416  bytes 104988 (102.5 KiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


Can broadcast be considered as gateway here? If it is, shouldn't it be 
changed to '192.168.7.1' after I added the default gateway?

-- 
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/bb7516ea-452e-4006-827a-097e24c310b3%40googlegroups.com.

[beagleboard] Re: Beagle Blue Boo Boo - Attached the battery the wrong way

[mnccouk via BeagleBoard]

Further to my previous post bought the MOSFET from digikey, installed it 
today and it now works fine. I'm pretty certain in my case though that I 
didn't connect the battery the wrong way round. Anyway, thanks to this 
group it's now back working again.
Here's the new installed component

[image: 2019-07-31-202742.jpg]
  

On Friday, 28 April 2017 20:55:34 UTC+1, Mark A. Yoder wrote:
>
> My son attached an S2 battery to a Blue yesterday and got a spark.  He 
> thinks he had the plug oriented correctly.  He re plugged it in again and 
> attached the Blue to a 12V supply.  The Blue fired up and the battery 
> charged.  Once charged we removed the 12V and the Blue died.  The Blue 
> reboots when the 12V supply is restored, but won't run on the battery 
> alone.  It looks like we melted part of the regulator.  Notice the 8 pin 
> device in the top center of the picture.
>
>
>
> 
>
>
> I'm assuming the part can be replaced.  Does anyone know what part it is?
>
>
> --Mark
>
>
>
>

-- 
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/4c32138f-47bf-434c-9be8-d00a1878aeca%40googlegroups.com.

[beagleboard] No I2S signals from the BeagleBone Black

[vinaydivakar1990]

I am unable to get the I2S signals from the beaglebone. Below are the 
things I did.

   1. I first disabled the HDMI audio as described here 
   .
   2. I am using the P9.31 (SCLK), P9.28 (Data0) and P9.29(FSX/WS). Running 
   sudo /opt/scripts/tools/version.sh gives the following.

debian@beaglebone:/boot$ sudo /opt/scripts/tools/version.sh
[sudo] password for debian: 
git:/opt/scripts/:[1aa73453b2c980b75e31e83dab7dd8b6696f10c7]
eeprom:[A335BNLT00C02315BBBK4ACD]
model:[TI_AM335x_BeagleBone_Black]
dogtag:[BeagleBoard.org Debian Image 2018-10-07]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 
2018.09-2-g0b54a51eee]:[location: dd MBR]
kernel:[4.14.71-ti-r80]
nodejs:[v6.14.4]
uboot_overlay_options:[enable_uboot_overlays=1]
uboot_overlay_options:[uboot_overlay_addr0=/lib/firmware/BB-BONE-AUDI-02.dtbo]
uboot_overlay_options:[disable_uboot_overlay_audio=1]
uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-14-TI-00A0.dtbo]
uboot_overlay_options:[enable_uboot_cape_universal=1]
pkg check: to individually upgrade run: [sudo apt install --only-upgrade ]
pkg:[bb-cape-overlays]:[4.4.20180928.0-0rcnee0~stretch+20180928]
pkg:[bb-wl18xx-firmware]:[1.20180517-0rcnee0~stretch+20180517]
pkg:[kmod]:[23-2rcnee1~stretch+20171005]
pkg:[librobotcontrol]:[1.0.3-git20181005.0-0rcnee0~stretch+20181005]
pkg:[firmware-ti-connectivity]:[20170823-1rcnee1~stretch+20180328]
groups:[debian : debian adm kmem dialout cdrom floppy audio dip video plugdev 
users systemd-journal i2c bluetooth netdev cloud9ide gpio pwm eqep admin spi 
tisdk weston-launch xenomai]
cmdline:[console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 
root=/dev/mmcblk1p1 ro rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 
quiet]
dmesg | grep pinctrl-single
[1.107553] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568
dmesg | grep gpio-of-helper
[1.119437] gpio-of-helper ocp:cape-universal: ready
END


   1. Running perl /opt/scripts/device/bone/show-pins.pl gives the 
   following.

debian@beaglebone:/boot$ perl /opt/scripts/device/bone/show-pins.pl
P8.25 / eMMC d00  U7 fast rx  up  1 mmc 1 d0 
mmc@481d8000 (pinmux_emmc_pins)
P8.24 / eMMC d11  V7 fast rx  up  1 mmc 1 d1 
mmc@481d8000 (pinmux_emmc_pins)
P8.05 / eMMC d22  R8 fast rx  up  1 mmc 1 d2 
mmc@481d8000 (pinmux_emmc_pins)
P8.06 / eMMC d33  T8 fast rx  up  1 mmc 1 d3 
mmc@481d8000 (pinmux_emmc_pins)
P8.23 / eMMC d44  U8 fast rx  up  1 mmc 1 d4 
mmc@481d8000 (pinmux_emmc_pins)
P8.22 / eMMC d55  V8 fast rx  up  1 mmc 1 d5 
mmc@481d8000 (pinmux_emmc_pins)
P8.03 / eMMC d66  R9 fast rx  up  1 mmc 1 d6 
mmc@481d8000 (pinmux_emmc_pins)
P8.04 / eMMC d77  T9 fast rx  up  1 mmc 1 d7 
mmc@481d8000 (pinmux_emmc_pins)
P8.19  8 U10 fast rx down 7 gpio 0.22
ocp/P8_19_pinmux (pinmux_P8_19_default_pin)
P8.13  9 T10 fast rx down 7 gpio 0.23
ocp/P8_13_pinmux (pinmux_P8_13_default_pin)
P8.14 10 T11 fast rx down 7 gpio 0.26
ocp/P8_14_pinmux (pinmux_P8_14_default_pin)
P8.17 11 U12 fast rx down 7 gpio 0.27
ocp/P8_17_pinmux (pinmux_P8_17_default_pin)
P8.12 12 T12 fast rx down 7 gpio 1.12
ocp/P8_12_pinmux (pinmux_P8_12_default_pin)
P8.11 13 R12 fast rx down 7 gpio 1.13
ocp/P8_11_pinmux (pinmux_P8_11_default_pin)
P8.16 14 V13 fast rx down 7 gpio 1.14
ocp/P8_16_pinmux (pinmux_P8_16_default_pin)
P8.15 15 U13 fast rx down 7 gpio 1.15
ocp/P8_15_pinmux (pinmux_P8_15_default_pin)
P9.15 16 R13 fast rx down 7 gpio 1.16
ocp/P9_15_pinmux (pinmux_P9_15_default_pin)
P9.23 17 V14 fast rx down 7 gpio 1.17
ocp/P9_23_pinmux (pinmux_P9_23_default_pin)
P9.14 18 U14 fast rx down 7 gpio 1.18
ocp/P9_14_pinmux (pinmux_P9_14_default_pin)
P9.16 19 T14 fast rx down 7 gpio 1.19
ocp/P9_16_pinmux (pinmux_P9_16_default_pin)
P9.11 28 T17 fast rx down 7 gpio 0.30
ocp/P9_11_pinmux (pinmux_P9_11_default_pin)
P9.13 29 U17 fast rx down 7 gpio 0.31
ocp/P9_13_pinmux (pinmux_P9_13_default_pin)
P9.12 30 U18 fast rx down 7 gpio 1.28
ocp/P9_12_pinmux (pinmux_P9_12_default_pin)
P8.26 31  V6 fast rx down 7 gpio 1.29
ocp/P8_26_pinmux (pinmux_P8_26_default_pin)
P8.21 / eMMC clk  32  U9 fast rx  up  2 mmc 1 clk
mmc@481d8000 (pinmux_emmc_pins)
P8.20 / eMMC 

[beagleboard] Question about I2C Bus Recovery

[harrisoncbsteel]

Hello all,

I have a quick question about the I2C bus on the Beaglebone Black. 

I have built a system with a number of I2C slaves, but sometimes (rarely, 
once in 50,000 communications or less) they seem to hang and hold the bus 
in a fixed state. The I2C standard in theory has a fix for this (toggling 
the CLK 9 times 
), which 
forces the slave to release the bus.

Is this fix implemented for the Beaglebone Black? I figured it might be 
only in recent Linux kernels, and hence I am upgrading my system to Debian 
10/Linux 4.19 (previously it was the default Debian 8). However, I saw on a 
Raspberry Pi forum (here 
) that bus 
recovery functionality might be chip-specific, and so I worry that this may 
functionality may not exist for the AM335X. If not, how might I go about 
implementing it?

Thank you in advance for any assistance.

-- 
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/4b787e78-c63c-436e-880e-bd78f7bfa681%40googlegroups.com.

[beagleboard] Re: follow-up on mjpg streamer video manipulation on BLUE

[Daniyal Ansari]

It works!
Thank you.

https://gist.github.com/ansarid/b820026d2fd169fe729e8e8b651eba67

On Thu, Aug 1, 2019 at 4:25 PM Daniyal Ansari 
wrote:

> Testing that now.
> Also added beagleboard@googlegroups.com
>
> On Thu, Aug 1, 2019 at 3:54 PM Jason Kridner  wrote:
>
>> It is in the package feeds now, but not installed by default.
>>
>> sudo apt update
>> sudo apt install mjpg-streamer-opencv-python
>>
>> Would be awesome if we had beagleboard@googlegroups.com in copy. Do you
>> mind if I just forward this thread?
>>
>> On Thu, Aug 1, 2019 at 3:38 PM David Malawey  wrote:
>>
>>> Hi Jason,
>>>
>>> I'm writing the lab together with Daniyal to instruct students on using
>>> openCV to process video stream in realtime.   We need to be able to view
>>> our images in realtime after performing a filter, etc. using openCV.
>>> Daniyal is helping me put this tutorial together, and we believe you
>>> planned to make an update to the base image for the Blue to enable this.
>>>
>>> I think we are waiting on an OpenCV module to be added to the
>>> preinstalled mjpg-streamer before we can produce a live output of modified
>>> images.  Is this something you can add on your end and is it feasible to
>>> implement by next week?  My time is getting compressed to finish lab
>>> instructions for the fall, so I will decide this week if I should keep this
>>> lab or remove it from the lessons.
>>>
>>> Cheers,
>>>
>>> David Malawey, MS ME
>>> ETID Technical Lab Coordinator
>>> mala...@tamu.edu
>>>
>>
>>
>> --
>> https://beagleboard.org/about
>>
>

-- 
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/CAK6ueF%3DFCsvGtVLkJ8rX4MtPuzMBRa093EfDmdhzjr0tpus6Tw%40mail.gmail.com.

Re: [beagleboard] (usability) apt upgrade, install instructions, and machinekit images

[shabaz]

>
> Thanks!

Google groups took a while to push this question onto the mail-group, 
out-of-order (it was the first question I posted).
Thanks again for your help.

Incidentally, the pre-built Xenomai kernel that you mentioned is running 
nicely, I'm a newcomer to it but was able to write a simple program to show 
its improvement during toggling of GPIO output pin, where the jitter can be 
easily measured on a 'scope.
(Not a real-life scenario of course, since PRU would be used where the 
jitter needed to be reduced to ~ zero). But nice to see Linux on the BBB 
can have such low jitter for user-space linux apps too.
I'll write that up soon.

-- 
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/64e2b5d1-9bd8-4d1e-9b29-d225487c70b5%40googlegroups.com.

[beagleboard] Re: PWM in beagle bone black

[lbarros]

Hi Megha,

I recomend you to use adafruit python library to check your uEnv.tx 
configuration and pin choice. It is a very easy to use lib and helped me a 
lot to test GPIO stuff.

Here is a link to a simple 
tutorial:https://learn.adafruit.com/setting-up-io-python-library-on-beaglebone-black/pwm

Em sexta-feira, 2 de agosto de 2019 01:07:38 UTC-3, Megha Bhirade escreveu:
>
>
> Hi,
>
> I got why that error is coming . already i used those pins to UART , so i 
> can't use that pins again to PWM.
>
> i am using P9.14 for pwm, but still also it is not working for me..
>
> i am feeling something i need to add in to uEnv.txt, but i am not getting 
> ..
>
> please suggest me??
>

-- 
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/6829d8fc-54ae-448a-b8e4-996d80d7335f%40googlegroups.com.

[beagleboard] Interrupt from PRU to ARM

[geyer . christian97]

Hello Everybody,

I've got a problem which I can not solve through tutorials and other stuff. 
Therefore I am asking you all:

Has anybody an example on how to run an Interrupt from PRU to ARM by using 
remoteproc and the 4.14 kernel?

The problem I face is the whole Init sequence for interrupt checking on the 
ARM, as it is completely new to me, and I only found examples using 
polling, but I need a "actual" interrupt.

I'm looking forward to get answers.

Regards
Chris

-- 
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/1fe20813-118c-4aa8-bd61-dbe58dadc0d5%40googlegroups.com.

[beagleboard] What's the best way of sending positional data to BeagleBone Blue from a connected Windows desktop?

[rrajan]

Hello,
I am currently working on a project to control a motor from a Windows 7 
Desktop. So far I've been able to write a program with librobotcontrol to 
move a connected DC motor a specified amount: at the moment I can control 
the motor by SSHing into the BeagleBone and running a simple command line 
program from there. I would like to eventually be able to control the motor 
by launching a program with a UI on the desktop, but I am struggling to 
find a way to do it. Using ROS seemed promising, but I was struggling with 
sending messages with rosserial_windows from windows to the beagle, so I 
was wondering if there was an easier way.

Thanks,
rrajan 

-- 
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/a68db0e0-99e8-4452-8c2a-1db5984fde1d%40googlegroups.com.

[beagleboard] BLE on BBBW

[agathe]

Hello, this is my first post so tell me if I'm in the wrong forum. I want 
to purchase a BBB wireless that I can connect to via an application on my 
phone so to transfer data from my BBBW to my phone using Bluetooth Low 
Energy and I wanted to check first if what I wanted to do was possible and 
if there were explanation on how to do it. However I couldn't find any 
tutorial to do so, even just the connection part. There are tutorial to use 
Bluetooth LE on a BBB (not wireless) or another to use Bluetooth RFCOMM 
with a BBBW but no tutorial to use BLE on BBBW. Did anyone by any chance 
find a tutorial that I missed or know how to do it ?
Thank you in advance !

-- 
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/51adee92-5ead-4960-8195-f050d828e7df%40googlegroups.com.

[beagleboard] Testing MCP41010

[Frederico Alves de Oliveira Silva]

Hello,

I am trying to test a digipot MCP41010 on a BeagleBone Black and I can't 
make it work.

I made the connections between BeagleBone and the digipot MCP41010 as below:

PORT |  CS0 |
DO |DI |SCLK
SPI0   |  
   
P9_17 |  
P9_21 |  
P9_18 |  
P9_22

I used the code below , from this page: 
https://adafruit-beaglebone-io-python.readthedocs.io/en/latest/SPI.html, to 
test the output of the BeagleBone:

*import Adafruit_BBIO.SPI as SPI

from Adafruit_BBIO.SPI import SPI
# spi = SPI(bus, device) #/dev/spidev.

# /dev/spidev0.0
spi = SPI(0, 0)
print(spi.xfer2([32, 11, 110, 22, 220]))
spi.close()*

The output should be: *32, 11, 110, 22, 220*; but, it is: *255, 255, 255, 255, 
255*.

Can anybody help me, please?
Thanks for the attention

-- 
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/e76db12a-e6e6-4faa-aab5-3f6895ccae04%40googlegroups.com.

[beagleboard] BeagleBone Black booting from SD card.

[digvijaykhambe007]

Hi,
 
   I want to flash the SD card for booting the beaglebone black. I 
am using bone-debian-9.5-lxqt-armhf-2018-10-07-4gb.img image and 
balenaEtcher-1.5.52-x64.AppImage  for flashing the SD card. But i am 
getting the rootfs partition only, there is no boot partition(MLO and 
uboot). So how can i get boot partition??  What is the process of flashing 
the SD card using image mentioned above.

Regrads,
Digvijay

-- 
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/b111e93f-c1ae-4f1f-89c7-e2f14d612dd8%40googlegroups.com.

[beagleboard] Beaglebone Black Kernel Module

[geyer . christian97]

Hello Online community,

I am facing a problem, which I need assistence for. I want to write a 
Kernel Module to my Beaglebone Black, and the Makefile is not working, 
because the default path /lib/modules/$(shell uname -r)/build does not 
exist on the Kernel (4.14.71-ti-r80) I am using.

I would like to know which file path is the correct one. I also want to 
know if it is even possible to compile a Kernelmodule right on the 
Beaglebone Black, or it has to be done by crosscompiling.

Regards

Chris

-- 
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/6ae5c5a9-068b-4e20-b661-3348761258ac%40googlegroups.com.

[beagleboard] BBBW not detetcted by PC

[Agathe LG]

Hello,
I just started working on a BBBW. I tried to connect it to my pc with an 
usb cable, the led usr0 is blinking in a heartbeat rate like it's supposed 
to but I'm supposed to see it appeared as a external drive and nothing is 
there. I tried on another computer with different cables and I nether see 
it. I tried installing the driver bone_D64 but nothing changed. It also 
doesn't appear in the wifi networks.
If you have any idea of what I did wrong, I would be really grateful for 
your help !

PS : I am working on windows 10

-- 
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/4c90f267-bf42-4cc5-8d42-a892cf9f0a80%40googlegroups.com.

[beagleboard] Using digital potentiometer MCP41010 with BeagleBone Black

[Frederico Alves de Oliveira Silva]

Hello guys,

I am using a BeagleBone Black with an digital potentiometer MCP41010.

I did the connections between the two devices and run the code in python 
below:

import Adafruit_BBIO.SPI as SPI
from Adafruit_BBIO.SPI import SPI# spi = SPI(bus, device) 
#/dev/spidev.
# /dev/spidev0.0spi = SPI(0, 0)print(spi.xfer2([127]))spi.close()
The output of the code should be: 127
But I only get: 255

Can anyone help me?

-- 
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/399406fc-1139-429d-bac8-f12e5b0bf17e%40googlegroups.com.

[beagleboard] DDR capacity

[DMotlagh]

What is the maximum DDR for this chip or AM5718?  The datasheet indicates 
2GB, is this the max?

-- 
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/98c494c6-b11c-44a2-887b-ba1491200326%40googlegroups.com.

[beagleboard] Re: CANBus Cape availability

[Jason Kridner]

On Tuesday, August 13, 2019 at 12:16:10 PM UTC-4, thenbomr wrote:
>
> Hi All.
>
> Does anyone know of a source for the CANbuscape described in the 
> BeagleBone support website, allegedly built by Beagleboard Toys?
> https://elinux.org/CAN_Bus_Cape_RevA 
> 
> What I really want is the isolation provided by the transceiver, and any 
> other BBB compatible board that has the same or equivalent chip would be 
> adequate to me. There are a smallish number of CANbus capes for the BBB 
> (actually BBG, in my case; I assume there is no compatibility issue), and 
> all of the ones I've seen offer little or no isolation from the CAN bus. 
> There is the design at 
>
> https://www.thomas-wedemeyer.de/beaglebone-canbus-python.html
>
> which has an isolating transceiver. HAs anyone used that design to build 
> up a cape in real hardware? Any available for sale?
>
>---   rod.
>

BeagleBoard.org BeagleBone Comms Cape (https://beagleboard.org/capes#comms) has 
a CAN XCVR on it.

-- 
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/d28c2421-1a20-479b-9c52-f3e2d9f96040%40googlegroups.com.

[beagleboard] name resolution failed BBB wireless

[anish kumar]

I am trying to setup my beaglebone black wireless for accessing my 
pc(windows-7) internet using usb-ethernet. Below is the steps i have 
performed
1.) add dns server in file edit /etc/network/interfaces
 dns-nameservers 8.8.8.8
2.) add default gateway [i have to do this every time beaglebone is 
reset/restarted or power cycled]
 sudo route add default gateway 192.168.7.1
3.) on pc side, the linux-rndis has following settings;
 ipv4 - 192.168.7.1
  sub  - 255.255.255.0
  dns  - 8.8.8.8
4.) update date and time

Now, when trying to ping www.google.com i get *"temporary failure in name 
resolution"*

I am using bone-debian-9.5-lxqt-armhf-2018-10-07-4gb.img.xz


-- 
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/ed4abdf1-ab24-4fc9-9efb-d05e09cabd54%40googlegroups.com.

Re: [beagleboard] (usability) apt upgrade, install instructions, and machinekit images

[Robert Nelson]

On Tue, Aug 13, 2019 at 10:07 AM shabaz  wrote:
>
>
> Hi!
>
> I've got a few usability issues to report.
>
> (a) apt upgrade
> I installed the latest Debian image on my BBB-Wireless, and then typed apt 
> update followed by apt-upgrade.
> Partway through the upgrade, it prompted me if I had a robotics cape. I 
> didn't so I selected No (the default option).
> However, it then prompted me if I wished a librobotcontrol service to run on 
> boot. That made me think I may have
> accidentally selected Yes for the robotics cape. Is there any alternative way 
> to do this, rather than in an apt upgrade?

https://github.com/StrawsonDesign/librobotcontrol/issues

>
> (b) install instructions
> It may be just me, but I find the user instructions a little hard to follow 
> (I always have found then hard to follow, for many years).
> I appreciate this is because they need to cater for many scenarios and many 
> images, and the changes over the years.
> I've written some instructions in a blog format, if you wish to link to, or 
> copy these on the BeagleBoard.org website, in entirety or in part,
> or edited or not, then please feel free to use them.
> The instructions are here:
> https://www.element14.com/community/community/designcenter/single-board-computers/blog/2019/08/11/getting-started-with-beaglebone-black
> I'm sure mine will not be to everyones taste either, but a link to them could 
> help some people since it complements the official instructions
> which of course by nature are more 'formal' than a blog format.

No reason to use 7-zip, etcher.io can write the compressed image as-is..

> (c) machinekit image location
> I'm really struggling to find a link to pre-built machinekit images. Several 
> websites suggest they should be at
> https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#BBW.2FBBB_.28All_Revs.29_Machinekit

Click that link again...

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/CAOCHtYidmPYh9%2BKjgf19g-i8wGr%2BCKA%2BZwexSSg_X1YRGcCA0A%40mail.gmail.com.

[beagleboard] LCD touch screen cape not working

[Amine Amiri]

hi i have a beaglebone black board that have debian installed

but i cant connect the touch screen to it

it lights up then closes without showing a thing, but the beaglebone works 
fine with the micro Hdmi

and when i tried an android image on it it works just when the micro hdmi 
is connected

well , it the screen works but i cant touch anything

is there like drivers needed or anything ?

-- 
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/ec7528c3-e4ee-4202-b6f6-6df64b839d7d%40googlegroups.com.

[beagleboard] Beaglebone Black driver troubles

[Jan Coetzer]

Hi 

I am trying to get a Beaglebone Black working on a Windows 8.1 machine. ( I 
managed to get it working on a Windows 10.1 machine at work.)

I googled the problem and all that I find is the signing of the driver 
issue. I did follow the procedure to install unsigned drivers on both 
machines.

In my device manager I see the 'Linux USB Ethernet/RNDIS Gadget' under 
Network Adapters on my machine but with an explanation mark. The status 
is*:This 
device cannot start. (Code 10) {Operation Failed} The requested operation 
was unsuccessful.*

Any advice will be appreciated.

Thanks in advance


-- 
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/f9312906-451c-4664-8783-8608c204dc79%40googlegroups.com.

[beagleboard] (usability) apt upgrade, install instructions, and machinekit images

[shabaz]

Hi!

I've got a few usability issues to report.

(a) apt upgrade
I installed the latest Debian image on my BBB-Wireless, and then typed apt 
update followed by apt-upgrade.
Partway through the upgrade, it prompted me if I had a robotics cape. I 
didn't so I selected No (the default option).
However, it then prompted me if I wished a librobotcontrol service to run 
on boot. That made me think I may have 
accidentally selected Yes for the robotics cape. Is there any alternative 
way to do this, rather than in an apt upgrade?

(b) install instructions
It may be just me, but I find the user instructions a little hard to follow 
(I always have found then hard to follow, for many years). 
I appreciate this is because they need to cater for many scenarios and many 
images, and the changes over the years.
I've written some instructions in a blog format, if you wish to link to, or 
copy these on the BeagleBoard.org website, in entirety or in part,
or edited or not, then please feel free to use them.
The instructions are here: 
https://www.element14.com/community/community/designcenter/single-board-computers/blog/2019/08/11/getting-started-with-beaglebone-black
I'm sure mine will not be to everyones taste either, but a link to them 
could help some people since it complements the official instructions
which of course by nature are more 'formal' than a blog format. 

(c) machinekit image location
I'm really struggling to find a link to pre-built machinekit images. 
Several websites suggest they should be at 
https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#BBW.2FBBB_.28All_Revs.29_Machinekit

and similar links, but there isn't anything there (at least not that I can 
find by typing Ctrl-F and searching for the text "Machinekit".
Where are the machinekit images located?

Many thanks,

Shabaz.

-- 
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/942b99c8-8964-4958-8cb2-ca194764ef6d%40googlegroups.com.

[beagleboard] Documentation for peripherals in /sys/class

[anish kumar]

Hi,

Is there any official documentation that describes various configuration 
parameters with examples for peripherals in */sys/class/**


-- 
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/06599b2c-a2b9-48a2-91ad-9381ed477957%40googlegroups.com.

Re: [beagleboard] Re: Pocket Beagle power question

[benoit . rapidel]

Hi,

Could this be related to random reboots on BBB ?

See this thread for more details: 
https://groups.google.com/forum/#!msg/beagleboard/RMOTnQBgIo8/q5vzpFPLlhgJ

We found out the issue / causes are still present on a 4.1 kernel.

Le samedi 10 août 2019 04:53:23 UTC+2, Robert Heller a écrit :
>
> At Fri, 9 Aug 2019 21:14:50 -0500 beagl...@googlegroups.com  
> wrote: 
>
> > 
> > 
> > As I said, P1-Pin-1 and the microUSB connector power are two different 
> > inputs to two different power supplies.  Having power on both of them is 
> > not a problem, and in fact, will prevent the problem of instability I 
> was 
> > concerned about. 
> > 
> > So, no problem powering both. 
> > 
> > The concern with the random crashes is just that, it could take three 
> days, 
> > or could happen in the first hour. 
> > I would power the unit from both pins, if it is doing something at all 
> > important. 
> > 
> > Of course, my crashing experience is from 18 months ago, and there have 
> > been a lot of software releases since then. 
>
> So you believe it was some sort of software issue, rather than a hardware 
> design problem? 
>
> > 
> > I would encourage you to run some endurance tests on your board, before 
> > putting it in service. 
>
> OK, I can do that at some point. 
>
> > 
> > --- Graham 
> > 
> > == 
> > 
> > On Fri, Aug 9, 2019 at 8:34 PM Robert Heller  > wrote: 
> > 
> > > At Fri, 9 Aug 2019 16:23:26 -0700 (PDT) beagl...@googlegroups.com 
>  
> > > wrote: 
> > > 
> > > > 
> > > > 
> > > > 
> > > > Robert: 
> > > > 
> > > > It has been a while, almost a year since I did any testing with the 
> > > > PocketBeagle. 
> > > > But I don't think anything has changed relative to my comments 
> below. 
> > > > Maybe someone can correct me if I am wrong, and some things have 
> been 
> > > fixed. 
> > > > 
> > > > P1-Pin-1 is Vin, and is equivalent to the Barrel Jack input on the 
> > > > Beaglebone Black, it 
> > > > is a separate power supply input, and is isolated from the microUSB 
> > > > connector power. 
> > > > 
> > > > P1-Pin-7 is hardwired to the +5 pin on the microUSB connector, USB 
> Port 
> > > 0. 
> > > > It is not clear from the schematic, but is visible if you view the 
> PCB 
> > > > board plots. 
> > > > Or check it with an Ohmmeter. 
> > > > 
> > > > I found that the PocketBeagle, when powered exclusively by P1-Pin-1 
> > > would 
> > > > randomly 
> > > > crash about once every 24 hours of operation, without any apparent 
> > > reason, 
> > > > or 
> > > > any clue in the logs. I hope that this has been fixed, but I have 
> seen 
> > > > other reports 
> > > > since I initially reported it, and nothing since that reported a 
> fix. 
> > > 
> > > Well, I am not expecting an application that would run 24/7.  I am 
> working 
> > > on 
> > > model RR control circuits.  It does not sound like this should be an 
> > > immediate 
> > > problem. 
> > > 
> > > 
> > > > 
> > > > The only workaround I found was to power P1-Pin-1 and P1-Pin-7 in 
> > > parallel, 
> > > > in which case 
> > > > it does not crash, but now there is no isolation between USB +5V and 
> > > your 
> > > > independent 
> > > > PB power supply, and, as you are concerned about, all kinds of 
> > > cross-feed 
> > > > and back 
> > > > powering can occur. 
> > > 
> > > That does not sound like a really good idea. 
> > > 
> > > Question: if the board was powered from P1-Pin-1 *and* the USB will 
> there 
> > > be 
> > > problems?  Right now, that is my main concern.  Jacking in the USB 
> (for 
> > > file 
> > > transfer mostly, since I can use the serial console for debugging) 
> while 
> > > the 
> > > board is being powered via P1-Pin-1 is something I'd like to be able 
> to 
> > > do, 
> > > but don't want to fry anything. 
> > > 
> > > > 
> > > > I suggest you read the email thread "PocketBeagles are Unstable" 
> started 
> > > > 11/24/2017 
> > > 
> > > Will have a look. 
> > > 
> > > 
> > 
>
> -- 
> Robert Heller -- 978-544-6933 
> Deepwoods Software-- Custom Software Services 
> http://www.deepsoft.com/  -- Linux Administration Services 
> hel...@deepsoft.com-- Webhosting Services 
>   
>

-- 
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/a8473b3c-9234-43b2-bf8a-a3f2e2471d68%40googlegroups.com.