[beagleboard] Re: 4G dongle keeps debouncing

[Tarmo]

On Thursday, October 29, 2020 at 1:16:13 AM UTC+2 atiqu...@gmail.com wrote:

> I have a 4G dongle which keep on denouncing between two interfaces
>

How do you supply power to the 4G dongle? It's not connected directly to 
the Beagle's USB port, is it?

--
Kind regards,
Tarmo

-- 
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/e2b9e165-96c2-456d-b221-77f529ebf7b5n%40googlegroups.com.

Re: [beagleboard] Re: 4G dongle keeps debouncing

[Atique Rehman]

I tried both ways, direct connection with beaglebone and using a powered
usb hub.

On Thu, Oct 29, 2020, 6:47 PM Tarmo  wrote:

> On Thursday, October 29, 2020 at 1:16:13 AM UTC+2 atiqu...@gmail.com
> wrote:
>
>> I have a 4G dongle which keep on denouncing between two interfaces
>>
>
> How do you supply power to the 4G dongle? It's not connected directly to
> the Beagle's USB port, is it?
>
> --
> Kind regards,
> Tarmo
>
> --
> 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/e2b9e165-96c2-456d-b221-77f529ebf7b5n%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/CAOzcuAh4AWk4M0fx%2BwsPT0reuw5XrVMFgNPegJeBuyZH53m4QQ%40mail.gmail.com.

[beagleboard] Adding a SPI-based SD card reader

[Mark A. Yoder]

I have a 2.4" TFT LCD display that also has a SPI-based SD card reader on 
it.  I'd like to interface it to my BeagleBone Black.  I see there's a 
Pocket Beagle device tree[1] for a SPI-based micro sd on a click board.  

Could this project be as easy as editing this dt to change it to the BBB's 
SPI bus?  What am I missing?

--Mark

[1] 
https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/PB-SPI0-MICROSD-CLICK.dts

-- 
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/b3806a43-92a6-4c84-a75a-695920999404n%40googlegroups.com.

[beagleboard] Logging Data in Google Sheets

[Mark A. Yoder]

I just updated my instructions for how to log data on the Bone to Google 
Sheets.

Enjoy.

https://elinux.org/EBC_Exercise_37_Logging_to_Sheets

--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/bb711e75-975b-439a-9dbe-b509b6648197n%40googlegroups.com.

[beagleboard] Re: 4G dongle keeps debouncing

[amf]

don't know about this dongle, but a quick google, this device seems to have 
several modes of operation. your log shows it changing pid which implies it 
is changing modes. see the following link, they seemed to have had the same 
issue and have posted a possible solution. 

https://gist.github.com/jfstenuit/13becfe728046074f5aaa0cb7f899ab9

On Wednesday, October 28, 2020 at 6:16:13 PM UTC-5 atiqu...@gmail.com wrote:

>
> HI All,
> I have a 4G dongle which keep on denouncing between two interfaces
> Kernel version "3.8.13-bone80" (Sorry we are stuck with this)
> here is dmesg for the dongle behavior:
> [ 1764.764123] usb 1-1.1: Product: HUAWEI_MOBILE
> [ 1764.764133] usb 1-1.1: Manufacturer: HUAWEI_MOBILE
> [ 1764.764573] usb 1-1.1: usb_probe_device
> [ 1764.764589] usb 1-1.1: configuration #1 chosen from 1 choice
> [ 1764.815748] usb 1-1.1: adding 1-1.1:1.0 (config #1, interface 0)
> [ 1764.816114] cdc_ether 1-1.1:1.0: usb_probe_interface
> [ 1764.816185] cdc_ether 1-1.1:1.0: usb_probe_interface - got id
> [ 1764.842656] cdc_ether 1-1.1:1.0 eth1: register 'cdc_ether' at 
> usb-musb-hdrc.1.auto-1.1, CDC Ethernet Device, 00:1e:10:1f:00:00
> [ 1764.842806] usb 1-1.1: adding 1-1.1:1.1 (config #1, interface 1)
> [ 1764.843398] hub 1-1:1.0: state 7 ports 4 chg  evt 0002
> [ 1767.309575] hub 1-1:1.0: state 7 ports 4 chg  evt 0002
> [ 1767.309715] hub 1-1:1.0: port 1, status 0100, change 0001, 12 Mb/s
> [ 1767.309734] usb 1-1.1: USB disconnect, device number 95
> [ 1767.309745] usb 1-1.1: unregistering device
> [ 1767.309757] usb 1-1.1: unregistering interface 1-1.1:1.0
> [ 1767.309972] cdc_ether 1-1.1:1.0 eth1: unregister 'cdc_ether' 
> usb-musb-hdrc.1.auto-1.1, CDC Ethernet Device
> [ 1767.316709] usb 1-1.1: unregistering interface 1-1.1:1.1
> [ 1767.317000] usb 1-1.1: usb_disable_device nuking all URBs
> [ 1767.535142] hub 1-1:1.0: debounce: port 1: total 200ms stable 100ms 
> status 0x101
> [ 1767.601538] usb 1-1.1: new high-speed USB device number 96 using 
> musb-hdrc
> [ 1767.615236] hub 1-1:1.0: port 1 not reset yet, waiting 10ms
> [ 1767.695706] usb 1-1.1: default language 0x0409
> [ 1767.695919] usb 1-1.1: udev 96, busnum 1, minor = 95
> [ 1767.695933] usb 1-1.1: New USB device found, idVendor=12d1, 
> idProduct=1f01
> [ 1767.695945] usb 1-1.1: New USB device strings: Mfr=1, Product=2, 
> SerialNumber=3
> [ 1767.695955] usb 1-1.1: Product: HUAWEI_MOBILE
> [ 1767.695964] usb 1-1.1: Manufacturer: HUAWEI_MOBILE
> [ 1767.695973] usb 1-1.1: SerialNumber: 0123456789ABCDEF
> [ 1767.696417] usb 1-1.1: usb_probe_device
> [ 1767.696434] usb 1-1.1: configuration #1 chosen from 1 choice
> [ 1767.696943] usb 1-1.1: adding 1-1.1:1.0 (config #1, interface 0)
> [ 1767.697360] usb-storage 1-1.1:1.0: usb_probe_interface
> [ 1767.697387] usb-storage 1-1.1:1.0: usb_probe_interface - got id
> [ 1767.700483] scsi418 : usb-storage 1-1.1:1.0
> [ 1767.701194] hub 1-1:1.0: state 7 ports 4 chg  evt 0002
> [ 1768.368244] usb-storage 1-1.1:1.0: disconnect by usbfs
> [ 1768.589625] hub 1-1:1.0: state 7 ports 4 chg  evt 0002
> [ 1768.589777] hub 1-1:1.0: port 1, status 0101, change 0001, 12 Mb/s
> [ 1768.589863] usb 1-1.1: USB disconnect, device number 96
> [ 1768.589875] usb 1-1.1: unregistering device
> [ 1768.589887] usb 1-1.1: unregistering interface 1-1.1:1.0
> [ 1768.590231] usb 1-1.1: usb_disable_device nuking all URBs
> [ 1768.699418] hub 1-1:1.0: debounce: port 1: total 100ms stable 100ms 
> status 0x101
> [ 1768.765758] usb 1-1.1: new high-speed USB device number 97 using 
> musb-hdrc
> [ 1768.779445] hub 1-1:1.0: port 1 not reset yet, waiting 10ms
> [ 1768.859861] usb 1-1.1: skipped 1 descriptor after configuration
> [ 1768.859886] usb 1-1.1: skipped 3 descriptors after interface
> [ 1768.859995] usb 1-1.1: default language 0x0409
> [ 1768.860170] usb 1-1.1: udev 97, busnum 1, minor = 96
> [ 1768.860184] usb 1-1.1: New USB device found, idVendor=12d1, 
> idProduct=14db
> [ 1768.860196] usb 1-1.1: New USB device strings: Mfr=1, Product=2, 
> SerialNumber=0
> [ 1768.860206] usb 1-1.1: Product: HUAWEI_MOBILE
> [ 1768.860215] usb 1-1.1: Manufacturer: HUAWEI_MOBILE
> [ 1768.860673] usb 1-1.1: usb_probe_device
> [ 1768.860692] usb 1-1.1: configuration #1 chosen from 1 choice
> [ 1768.912011] usb 1-1.1: adding 1-1.1:1.0 (config #1, interface 0)
> [ 1768.912540] cdc_ether 1-1.1:1.0: usb_probe_interface
> [ 1768.912557] cdc_ether 1-1.1:1.0: usb_probe_interface - got id
> [ 1768.939763] cdc_ether 1-1.1:1.0 eth1: register 'cdc_ether' at 
> usb-musb-hdrc.1.auto-1.1, CDC Ethernet Device, 00:1e:10:1f:00:00
> [ 1768.939972] usb 1-1.1: adding 1-1.1:1.1 (config #1, interface 1)
> [ 1768.940562] hub 1-1:1.0: state 7 ports 4 chg  evt 0002
>
> This keep on repeating forever.
> Any help is appreciated
>

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

[beagleboard] I2C 8 bit address?

[Paul Beam]

Does the Beaglebone support 8 bit I2c addresses?  I'm using a TI bq28z610 
which has I2C address 0xAA, but I cannot access it via i2ctools.  I can 
connect a TI I2C interface to my Windows PC and access the part, and the 
Beaglebone can communicate with other devices on the same bus, I'm pretty 
sure the component is attached properly, but no joy in trying to access 
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/c6794d4c-cc50-453d-b52d-d61cc548573an%40googlegroups.com.

[beagleboard] Interfacing a 16x2 char HD44780 LCD display

[Mark A. Yoder]

I've just recently discovered I have access to lots of 16x2 LCD displays.

I see there are many examples of interfacing it to a Linux machine, but 
most are via user space.  I'm looking for kernel space examples.  *modinfo 
hd44780* shows a driver is there, but how do I use it.  

Is there a device tree for the hd44780 for a parallel interface?

--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/691add1c-90ad-4702-a2de-c8ec7ce4f9bcn%40googlegroups.com.

[beagleboard] Re: I2C 8 bit address?

[Dennis Lee Bieber]

On Thu, 29 Oct 2020 10:23:39 -0700 (PDT), in
gmane.comp.hardware.beagleboard.user Paul Beam
 wrote:

>Does the Beaglebone support 8 bit I2c addresses?  I'm using a TI bq28z610 

Which Beaglebone?

>which has I2C address 0xAA, but I cannot access it via i2ctools.  I can 

Per the BBB TRM (TI SPRUH73P) 
"""
21.1.1 I2C Features
The general features of the I2C controller are:
• Compliant with Philips I2C specification version 2.1
• Supports standard mode (up to 100K bits/s) and fast mode (up to 400K
bits/s).
• Multimaster transmitter/slave receiver mode
• Multimaster receiver/slave transmitter mode
• Combined master transmit/receive and receive/transmit modes
• 7-bit and 10-bit device addressing modes
• Built-in 32-byte FIFO for buffered read or writes in each module
• Programmable clock generation
• Two DMA channels, one interrupt line
"""

BB-AI TRM
"""
The multimaster HS I2C controllers have the following features:
• Compliant with Philips I2C specification version 2.1
• Supports a standard mode (up to 100 kbps) and fast mode (up to 400 kbps)
• Supports HS mode for transfer up to 3.4 Mbps (only for I2C3, I2C4 and
I2C5)
• 7-bit and 10-bit device addressing modes
• General call
• Start/Restart/Stop
• Multimaster transmitter/slave receiver mode
• Multimaster receiver/slave transmitter mode
• Combined master transmit/receive and receive/transmit mode
• Built-in FIFOs (16 bytes) for buffered read or write
• Module enable/disable capability
• Programmable multislave channel (responds to four separate addresses)
"""

Per
https://www.totalphase.com/support/articles/200349176-7-bit-8-bit-and-10-bit-I2C-Slave-Addressing#8bit
8-bit addressing is not a proper I2C addressing mode.

Your xAA is probably address x55 with read/write bit 0 (write)



-- 
Dennis L Bieber

-- 
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/o54mpf9itc7hbrl24v98h17cucfkvmjpn1%404ax.com.

[beagleboard] Re: Interfacing a 16x2 char HD44780 LCD display

[Dennis Lee Bieber]

On Thu, 29 Oct 2020 11:39:54 -0700 (PDT), in
gmane.comp.hardware.beagleboard.user "Mark A. Yoder"
 wrote:

>
>Is there a device tree for the hd44780 for a parallel interface?
>
I suspect the true parallel interface has become somewhat deprecated --
most later displays using that protocol have incorporated a sub-board that
does serial<>parallel (I2C or SPI, maybe even plain UART).

One problem is that the parallel mode supports TWO configurations:
8-bit parallel and 4-bit parallel. When you add in the other control
signals, you can easily consume 11 GPIOs (in 8-bit mode; 7 GPIOs in 4-bit).

Since the Beagle doesn't seem to expose a parallel load for GPIOs
(unlike the Arduino AVR and BASIC Stamp which expose PORTx registers), that
leads to 4/8 slow, single-bit, loads. cf:
https://groups.google.com/forum/#!topic/beagleboard/WZxfbaHipWA

Using a PRU might be feasible for this (though where the GPIOs are
exposed may not be contiguous to the bits in the PRU GPIO register).


-- 
Dennis L Bieber

-- 
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/nq4mpfd3cqd8k4kb9gfb7rsvbj9hehldss%404ax.com.

Re: [beagleboard] Re: I2C 8 bit address?

[Paul Beam]

Thanks.  This part is totally confusing me.  It is supposed to be an
"upgrade" of a part I have been using.  I guess my time is better spent
getting the TI driver to work instead of accessing the registers directly,
which is what I had been doing.

On Thu, Oct 29, 2020 at 3:08 PM Dennis Lee Bieber 
wrote:

> On Thu, 29 Oct 2020 10:23:39 -0700 (PDT), in
> gmane.comp.hardware.beagleboard.user Paul Beam
>  wrote:
>
> >Does the Beaglebone support 8 bit I2c addresses?  I'm using a TI bq28z610
>
> Which Beaglebone?
>
> >which has I2C address 0xAA, but I cannot access it via i2ctools.  I can
>
> Per the BBB TRM (TI SPRUH73P)
> """
> 21.1.1 I2C Features
> The general features of the I2C controller are:
> • Compliant with Philips I2C specification version 2.1
> • Supports standard mode (up to 100K bits/s) and fast mode (up to 400K
> bits/s).
> • Multimaster transmitter/slave receiver mode
> • Multimaster receiver/slave transmitter mode
> • Combined master transmit/receive and receive/transmit modes
> • 7-bit and 10-bit device addressing modes
> • Built-in 32-byte FIFO for buffered read or writes in each module
> • Programmable clock generation
> • Two DMA channels, one interrupt line
> """
>
> BB-AI TRM
> """
> The multimaster HS I2C controllers have the following features:
> • Compliant with Philips I2C specification version 2.1
> • Supports a standard mode (up to 100 kbps) and fast mode (up to 400 kbps)
> • Supports HS mode for transfer up to 3.4 Mbps (only for I2C3, I2C4 and
> I2C5)
> • 7-bit and 10-bit device addressing modes
> • General call
> • Start/Restart/Stop
> • Multimaster transmitter/slave receiver mode
> • Multimaster receiver/slave transmitter mode
> • Combined master transmit/receive and receive/transmit mode
> • Built-in FIFOs (16 bytes) for buffered read or write
> • Module enable/disable capability
> • Programmable multislave channel (responds to four separate addresses)
> """
>
> Per
>
> https://www.totalphase.com/support/articles/200349176-7-bit-8-bit-and-10-bit-I2C-Slave-Addressing#8bit
> 8-bit
> 
> addressing is not a proper I2C addressing mode.
>
> Your xAA is probably address x55 with read/write bit 0 (write)
>
>
>
> --
> Dennis L Bieber
>
> --
> 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/o54mpf9itc7hbrl24v98h17cucfkvmjpn1%404ax.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/CAA_M65N4%3DdHgSbVaOT%3D_Kfd7t_rr2PJNLjK2WNK8Jm6VnUfNnA%40mail.gmail.com.

Re: [beagleboard] Re: I2C 8 bit address?

[H. Nikolaus Schaller]

It is much simpler than you think. Look into the bq chip technical reference 
manual:

the BQ28Z610 uses a series of 2-byte standard I2C commands with a 7-bit 
device address of 0x55 (8 bits = 0xAA to write and 0xAB to read).

You just have to know that Linux uses 7-bit addresses.

I.e. use i2cget with 0x55.
Or use i2cdetect to find out on which address the chip is really responding.


> Am 29.10.2020 um 20:33 schrieb Paul Beam :
> 
> Thanks.  This part is totally confusing me.  It is supposed to be an 
> "upgrade" of a part I have been using.  I guess my time is better spent 
> getting the TI driver to work instead of accessing the registers directly, 
> which is what I had been doing.
> 
> On Thu, Oct 29, 2020 at 3:08 PM Dennis Lee Bieber  
> wrote:
> On Thu, 29 Oct 2020 10:23:39 -0700 (PDT), in
> gmane.comp.hardware.beagleboard.user Paul Beam
>  wrote:
> 
> >Does the Beaglebone support 8 bit I2c addresses?  I'm using a TI bq28z610 
> 
> Which Beaglebone?
> 
> >which has I2C address 0xAA, but I cannot access it via i2ctools.  I can 
> 
> Per the BBB TRM (TI SPRUH73P) 
> """
> 21.1.1 I2C Features
> The general features of the I2C controller are:
> • Compliant with Philips I2C specification version 2.1
> • Supports standard mode (up to 100K bits/s) and fast mode (up to 400K
> bits/s).
> • Multimaster transmitter/slave receiver mode
> • Multimaster receiver/slave transmitter mode
> • Combined master transmit/receive and receive/transmit modes
> • 7-bit and 10-bit device addressing modes
> • Built-in 32-byte FIFO for buffered read or writes in each module
> • Programmable clock generation
> • Two DMA channels, one interrupt line
> """
> 
> BB-AI TRM
> """
> The multimaster HS I2C controllers have the following features:
> • Compliant with Philips I2C specification version 2.1
> • Supports a standard mode (up to 100 kbps) and fast mode (up to 400 kbps)
> • Supports HS mode for transfer up to 3.4 Mbps (only for I2C3, I2C4 and
> I2C5)
> • 7-bit and 10-bit device addressing modes
> • General call
> • Start/Restart/Stop
> • Multimaster transmitter/slave receiver mode
> • Multimaster receiver/slave transmitter mode
> • Combined master transmit/receive and receive/transmit mode
> • Built-in FIFOs (16 bytes) for buffered read or write
> • Module enable/disable capability
> • Programmable multislave channel (responds to four separate addresses)
> """
> 

vvv here is the important info

> Per
> https://www.totalphase.com/support/articles/200349176-7-bit-8-bit-and-10-bit-I2C-Slave-Addressing#8bit
> 8-bit addressing is not a proper I2C addressing mode.
> 
> Your xAA is probably address x55 with read/write bit 0 (write)

^^^ here is the important info

> 
> 
> 
> -- 
> Dennis L Bieber
> 
> -- 
> 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/o54mpf9itc7hbrl24v98h17cucfkvmjpn1%404ax.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/CAA_M65N4%3DdHgSbVaOT%3D_Kfd7t_rr2PJNLjK2WNK8Jm6VnUfNnA%40mail.gmail.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/5D52C99D-C165-4242-9A74-402BF2B3A3B4%40goldelico.com.

Re: [beagleboard] Interfacing a 16x2 char HD44780 LCD display

[Robert Nelson]

On Thu, Oct 29, 2020 at 1:40 PM Mark A. Yoder  wrote:
>
> I've just recently discovered I have access to lots of 16x2 LCD displays.
>
> I see there are many examples of interfacing it to a Linux machine, but most 
> are via user space.  I'm looking for kernel space examples.  modinfo hd44780 
> shows a driver is there, but how do I use it.
>
> Is there a device tree for the hd44780 for a parallel interface?

There is a relatively new driver for this, i just don't know of anyone
who's worked out a device tree for it..

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/auxdisplay/hd44780.c

Here is one example i found, just need to list the gpio's..

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm/boot/dts/armada-370-netgear-rn104.dts?h=v5.10-rc1#n146

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/CAOCHtYjQ07y1WZjVd4HEZHm3XJKATv6MyeCTG%2BxNAf_gUC-VbA%40mail.gmail.com.

Re: [beagleboard] Re: Disable Power Button IRQ from TPS65217 on BBBW?

[Joe Glandorf]

Thanks, Robert.  Unfortunately, commenting out either line in uEnv.txt, 
`#enable_uboot_overlays=1` or 
`#enable_uboot_cape_universal=1`
the TPS65217 IRQ still exists:  
$ cat /proc/interrupts | grep 65217
 60:  0  INTC   7 Level tps65217-irq
 62:  0  tps65217   0 Edge  vbus
 63:  0  tps65217   2 Edge  tps65217_pwr_but
And, PWM no longer works using the Python scripts, even after restoring the 
original dtb files.

Is this the appropriate information source for building the kernel?  
- 
https://www.digikey.com/eewiki/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-LinuxKernel
  
We're currently using this lxqt image for the BBBW:  
- 
https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Debian_Buster_LXQt_Snapshot
  

Joe

On Wednesday, October 28, 2020 at 1:44:11 PM UTC-4 RobertCNelson wrote:

> You can disable teh cape universal redirect with disabling this line
> in /boot/uEnv.txt
>
> enable_uboot_overlays=1
>
> You can also just not build with the tps65218-pwrbutton driver:
>
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/input/misc/tps65218-pwrbutton.c
>
> 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/2b95f0ea-c707-4298-82dc-c833f3e0ec9en%40googlegroups.com.

[beagleboard] Is BeagleBone_Black_Extracting_eMMC_contents method not working anymore? (2020-Q3)

[Fausto Gutierrez]

Is BeagleBone_Black_Extracting_eMMC_contents method not working anymore? 
(2020-Q3)

I've been using this procedure 
https://elinux.org/BeagleBone_Black_Extracting_eMMC_contents with no 
problem for years, using both BBB or BBB Industrial indistinctly.

However, nowadays (I mean with last BBB I bought (2020-Q3)), it does not 
work anymore (no backup-creation nor backup-restoration).

I have no clue why it happens (maybe some breaking changes in BBB hardware 
or BBB booting procedure. I don't know).

Any help will be appreciated. Thanks.

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

[beagleboard] Is BeagleBone_Black_Extracting_eMMC_contents method not working anymore? (2020-Q3)

[faustogut]

I've been using this procedure 
https://elinux.org/BeagleBone_Black_Extracting_eMMC_contents with no 
problem for years, using both BBB or BBB Industrial indistinctly.

However, nowadays (I mean with last BBB I bought (2020-Q3)), it does not 
work anymore (no backup-creation nor backup-restoration).

I have no clue why it happens (maybe some breaking changes in BBB hardware 
or BBB booting procedure. I don't know).

Any help will be appreciated. Thanks.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/161e8108-457c-48c8-bd72-7c5a503d84ado%40googlegroups.com.

[beagleboard] Wrong image version on Beaglebone's latest-images

[maciej . kubaszczyk]

Hi. I wanted to install Debian for 1st time on BeagleBone Black Wireless 
and selected Stretch IoT Debian 9.9 2019-08-03 4GB SD IoT 

 
from https://beagleboard.org/latest-images . Unfortunately, after 1st use 
of "sudo apt-get update" I noticed that repositories for Jessy are checked. 
After that I checked "cat /etc/os-release" and it confirmed that it is 
Jessy installed. So I would like to inform website administrators that 
something is wrong :) Could someone follow this information to right people 
and ask them to put answer under this post?

-- 
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/c7180667-c112-4a5a-9bbc-beeba3dcf141o%40googlegroups.com.

Re: [beagleboard] Wrong image version on Beaglebone's latest-images

[Robert Nelson]

On Thu, Oct 29, 2020 at 5:37 PM  wrote:
>
> Hi. I wanted to install Debian for 1st time on BeagleBone Black Wireless and 
> selected Stretch IoT Debian 9.9 2019-08-03 4GB SD IoT from 
> https://beagleboard.org/latest-images . Unfortunately, after 1st use of "sudo 
> apt-get update" I noticed that repositories for Jessy are checked. After that 
> I checked "cat /etc/os-release" and it confirmed that it is Jessy installed. 
> So I would like to inform website administrators that something is wrong :) 
> Could someone follow this information to right people and ask them to put 
> answer under this post?

This happens when you have a really really old version of Debian
installed on the eMMC, either hold down the boot button before you
provide power, or remove the MLO/u-boot.img files in the fat partition
of your eMMC.

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/CAOCHtYjYTNKm2hEzUWk_aFKxyZ%2Bq86%2B1JCaC5-m-BSSVP0wtVw%40mail.gmail.com.

Re: [beagleboard] Re: Disable Power Button IRQ from TPS65217 on BBBW?

[Robert Nelson]

On Thu, Oct 29, 2020 at 5:37 PM Joe Glandorf  wrote:
>
> Thanks, Robert.  Unfortunately, commenting out either line in uEnv.txt,
> `#enable_uboot_overlays=1` or
> `#enable_uboot_cape_universal=1`
> the TPS65217 IRQ still exists:
> $ cat /proc/interrupts | grep 65217
>  60:  0  INTC   7 Level tps65217-irq
>  62:  0  tps65217   0 Edge  vbus
>  63:  0  tps65217   2 Edge  tps65217_pwr_but
> And, PWM no longer works using the Python scripts, even after restoring the 
> original dtb files.

Correct, you'd have to enable pwm..

User cross posted here:

https://forum.digikey.com/t/disable-power-button-irq-from-tps65217-on-bbbw/9803/2

With the dtb hack to make tps65217_pwr_but disappear..

>
> Is this the appropriate information source for building the kernel?
> - 
> https://www.digikey.com/eewiki/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-LinuxKernel
> We're currently using this lxqt image for the BBBW:
> - 
> https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Debian_Buster_LXQt_Snapshot

Correct

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/CAOCHtYiR1jFAS%3DwD3QVn9kV9tX0PTfT9%2BYLotgsE%2B%2BAS-_yJ2g%40mail.gmail.com.

Re: [beagleboard] Re: 4G dongle keeps debouncing

[Atique Rehman]

That link is not very helpful for me.

On Fri, Oct 30, 2020 at 3:44 AM amf  wrote:

> don't know about this dongle, but a quick google, this device seems to
> have several modes of operation. your log shows it changing pid which
> implies it is changing modes. see the following link, they seemed to have
> had the same issue and have posted a possible solution.
>
> https://gist.github.com/jfstenuit/13becfe728046074f5aaa0cb7f899ab9
>
> On Wednesday, October 28, 2020 at 6:16:13 PM UTC-5 atiqu...@gmail.com
> wrote:
>
>>
>> HI All,
>> I have a 4G dongle which keep on denouncing between two interfaces
>> Kernel version "3.8.13-bone80" (Sorry we are stuck with this)
>> here is dmesg for the dongle behavior:
>> [ 1764.764123] usb 1-1.1: Product: HUAWEI_MOBILE
>> [ 1764.764133] usb 1-1.1: Manufacturer: HUAWEI_MOBILE
>> [ 1764.764573] usb 1-1.1: usb_probe_device
>> [ 1764.764589] usb 1-1.1: configuration #1 chosen from 1 choice
>> [ 1764.815748] usb 1-1.1: adding 1-1.1:1.0 (config #1, interface 0)
>> [ 1764.816114] cdc_ether 1-1.1:1.0: usb_probe_interface
>> [ 1764.816185] cdc_ether 1-1.1:1.0: usb_probe_interface - got id
>> [ 1764.842656] cdc_ether 1-1.1:1.0 eth1: register 'cdc_ether' at
>> usb-musb-hdrc.1.auto-1.1, CDC Ethernet Device, 00:1e:10:1f:00:00
>> [ 1764.842806] usb 1-1.1: adding 1-1.1:1.1 (config #1, interface 1)
>> [ 1764.843398] hub 1-1:1.0: state 7 ports 4 chg  evt 0002
>> [ 1767.309575] hub 1-1:1.0: state 7 ports 4 chg  evt 0002
>> [ 1767.309715] hub 1-1:1.0: port 1, status 0100, change 0001, 12 Mb/s
>> [ 1767.309734] usb 1-1.1: USB disconnect, device number 95
>> [ 1767.309745] usb 1-1.1: unregistering device
>> [ 1767.309757] usb 1-1.1: unregistering interface 1-1.1:1.0
>> [ 1767.309972] cdc_ether 1-1.1:1.0 eth1: unregister 'cdc_ether'
>> usb-musb-hdrc.1.auto-1.1, CDC Ethernet Device
>> [ 1767.316709] usb 1-1.1: unregistering interface 1-1.1:1.1
>> [ 1767.317000] usb 1-1.1: usb_disable_device nuking all URBs
>> [ 1767.535142] hub 1-1:1.0: debounce: port 1: total 200ms stable 100ms
>> status 0x101
>> [ 1767.601538] usb 1-1.1: new high-speed USB device number 96 using
>> musb-hdrc
>> [ 1767.615236] hub 1-1:1.0: port 1 not reset yet, waiting 10ms
>> [ 1767.695706] usb 1-1.1: default language 0x0409
>> [ 1767.695919] usb 1-1.1: udev 96, busnum 1, minor = 95
>> [ 1767.695933] usb 1-1.1: New USB device found, idVendor=12d1,
>> idProduct=1f01
>> [ 1767.695945] usb 1-1.1: New USB device strings: Mfr=1, Product=2,
>> SerialNumber=3
>> [ 1767.695955] usb 1-1.1: Product: HUAWEI_MOBILE
>> [ 1767.695964] usb 1-1.1: Manufacturer: HUAWEI_MOBILE
>> [ 1767.695973] usb 1-1.1: SerialNumber: 0123456789ABCDEF
>> [ 1767.696417] usb 1-1.1: usb_probe_device
>> [ 1767.696434] usb 1-1.1: configuration #1 chosen from 1 choice
>> [ 1767.696943] usb 1-1.1: adding 1-1.1:1.0 (config #1, interface 0)
>> [ 1767.697360] usb-storage 1-1.1:1.0: usb_probe_interface
>> [ 1767.697387] usb-storage 1-1.1:1.0: usb_probe_interface - got id
>> [ 1767.700483] scsi418 : usb-storage 1-1.1:1.0
>> [ 1767.701194] hub 1-1:1.0: state 7 ports 4 chg  evt 0002
>> [ 1768.368244] usb-storage 1-1.1:1.0: disconnect by usbfs
>> [ 1768.589625] hub 1-1:1.0: state 7 ports 4 chg  evt 0002
>> [ 1768.589777] hub 1-1:1.0: port 1, status 0101, change 0001, 12 Mb/s
>> [ 1768.589863] usb 1-1.1: USB disconnect, device number 96
>> [ 1768.589875] usb 1-1.1: unregistering device
>> [ 1768.589887] usb 1-1.1: unregistering interface 1-1.1:1.0
>> [ 1768.590231] usb 1-1.1: usb_disable_device nuking all URBs
>> [ 1768.699418] hub 1-1:1.0: debounce: port 1: total 100ms stable 100ms
>> status 0x101
>> [ 1768.765758] usb 1-1.1: new high-speed USB device number 97 using
>> musb-hdrc
>> [ 1768.779445] hub 1-1:1.0: port 1 not reset yet, waiting 10ms
>> [ 1768.859861] usb 1-1.1: skipped 1 descriptor after configuration
>> [ 1768.859886] usb 1-1.1: skipped 3 descriptors after interface
>> [ 1768.859995] usb 1-1.1: default language 0x0409
>> [ 1768.860170] usb 1-1.1: udev 97, busnum 1, minor = 96
>> [ 1768.860184] usb 1-1.1: New USB device found, idVendor=12d1,
>> idProduct=14db
>> [ 1768.860196] usb 1-1.1: New USB device strings: Mfr=1, Product=2,
>> SerialNumber=0
>> [ 1768.860206] usb 1-1.1: Product: HUAWEI_MOBILE
>> [ 1768.860215] usb 1-1.1: Manufacturer: HUAWEI_MOBILE
>> [ 1768.860673] usb 1-1.1: usb_probe_device
>> [ 1768.860692] usb 1-1.1: configuration #1 chosen from 1 choice
>> [ 1768.912011] usb 1-1.1: adding 1-1.1:1.0 (config #1, interface 0)
>> [ 1768.912540] cdc_ether 1-1.1:1.0: usb_probe_interface
>> [ 1768.912557] cdc_ether 1-1.1:1.0: usb_probe_interface - got id
>> [ 1768.939763] cdc_ether 1-1.1:1.0 eth1: register 'cdc_ether' at
>> usb-musb-hdrc.1.auto-1.1, CDC Ethernet Device, 00:1e:10:1f:00:00
>> [ 1768.939972] usb 1-1.1: adding 1-1.1:1.1 (config #1, interface 1)
>> [ 1768.940562] hub 1-1:1.0: state 7 ports 4 chg  evt 0002
>>
>> This keep on repeating forever.
>> Any help is appreciated
>>
> --
> For more options, visit http://beagleboard.org/dis

Re: [beagleboard] Beagle bone black setup with Intel Real sense camera

[Vinicius Juvinski]

Hi,

I don't know but you have several problems on it. First, the RealSense 
require USB 3 - without that you have several limitations on having data.
Another one is I tried to compile realsense libraries for beagle but I 
couldn't - requires a lot of memory for that.

Em segunda-feira, 19 de outubro de 2020 às 16:22:25 UTC-3, 
jonn...@gmail.com escreveu:

> I personally have no experience with the RealSense camera, but I am 
> interested in this combo as well.
>
> I would suspect the best place to start would be the github location:
>
> https://github.com/IntelRealSense/librealsense/blob/master/doc/installation.md
>
> There was a post by someone who was setting this up with a BeagleBone so 
> you could try to track them down:
> https://github.com/IntelRealSense/librealsense/issues/3394
>
> This looks like a good resource for info.
> https://support.intelrealsense.com/hc/en-us/community/topics
>
> Good luck.
>
> Cheers,
>
> Jon
>
>
> On Mon, Oct 19, 2020 at 5:18 AM Megha Bhirade  wrote:
>
>> Hi,
>>
>> I am using Beagle bone black in Linux Ubuntu platform and i want to use 
>> Real sense camera for my application.
>>
>> Please anybody suggest me how to setup the Beagle bone black with Real 
>> sense Depth and tracking camera??
>>
>> Please suggest me any related link for step by step setup...
>>
>> -- 
>> 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/4340e28c-4bb9-4995-95bc-bd2baa009f80o%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/2017667b-1742-495f-b49b-9875d5482c07n%40googlegroups.com.

Re: [beagleboard] Re: 4G dongle keeps debouncing

[jonnymo]

Have you created a udev rule for this device on the BB?
This seems to indicate it keeps creating a new device.

[ 1768.860170] usb 1-1.1: udev 97, busnum 1, minor = 96
[ 1768.860184] usb 1-1.1: New USB device found, idVendor=12d1,
idProduct=14db
[ 1768.860196] usb 1-1.1: New USB device strings: Mfr=1, Product=2,
SerialNumber=0
[ 1768.860206] usb 1-1.1: Product: HUAWEI_MOBILE
[ 1768.860215] usb 1-1.1: Manufacturer: HUAWEI_MOBILE

Ex:
https://wiki.debian.org/udev
https://linuxconfig.org/tutorial-on-how-to-write-basic-udev-rules-in-linux

Did the device come with a driver that is supported on the kernel you are
running?

What USB hub are you using?  I found that not all work the same on the BB.
At the bottom of this link is a list of Hubs that are known to work.
https://elinux.org/Beagleboard:BeagleBone_Black_Accessories

I've had good luck with the Belkin F4U041 7-port hub:
https://www.belkin.com/us/p/P-F4U041/

Cheers,

Jon

Jon

On Thu, Oct 29, 2020 at 4:13 PM Atique Rehman  wrote:

> That link is not very helpful for me.
>
> On Fri, Oct 30, 2020 at 3:44 AM amf  wrote:
>
>> don't know about this dongle, but a quick google, this device seems to
>> have several modes of operation. your log shows it changing pid which
>> implies it is changing modes. see the following link, they seemed to have
>> had the same issue and have posted a possible solution.
>>
>> https://gist.github.com/jfstenuit/13becfe728046074f5aaa0cb7f899ab9
>>
>> On Wednesday, October 28, 2020 at 6:16:13 PM UTC-5 atiqu...@gmail.com
>> wrote:
>>
>>>
>>> HI All,
>>> I have a 4G dongle which keep on denouncing between two interfaces
>>> Kernel version "3.8.13-bone80" (Sorry we are stuck with this)
>>> here is dmesg for the dongle behavior:
>>> [ 1764.764123] usb 1-1.1: Product: HUAWEI_MOBILE
>>> [ 1764.764133] usb 1-1.1: Manufacturer: HUAWEI_MOBILE
>>> [ 1764.764573] usb 1-1.1: usb_probe_device
>>> [ 1764.764589] usb 1-1.1: configuration #1 chosen from 1 choice
>>> [ 1764.815748] usb 1-1.1: adding 1-1.1:1.0 (config #1, interface 0)
>>> [ 1764.816114] cdc_ether 1-1.1:1.0: usb_probe_interface
>>> [ 1764.816185] cdc_ether 1-1.1:1.0: usb_probe_interface - got id
>>> [ 1764.842656] cdc_ether 1-1.1:1.0 eth1: register 'cdc_ether' at
>>> usb-musb-hdrc.1.auto-1.1, CDC Ethernet Device, 00:1e:10:1f:00:00
>>> [ 1764.842806] usb 1-1.1: adding 1-1.1:1.1 (config #1, interface 1)
>>> [ 1764.843398] hub 1-1:1.0: state 7 ports 4 chg  evt 0002
>>> [ 1767.309575] hub 1-1:1.0: state 7 ports 4 chg  evt 0002
>>> [ 1767.309715] hub 1-1:1.0: port 1, status 0100, change 0001, 12 Mb/s
>>> [ 1767.309734] usb 1-1.1: USB disconnect, device number 95
>>> [ 1767.309745] usb 1-1.1: unregistering device
>>> [ 1767.309757] usb 1-1.1: unregistering interface 1-1.1:1.0
>>> [ 1767.309972] cdc_ether 1-1.1:1.0 eth1: unregister 'cdc_ether'
>>> usb-musb-hdrc.1.auto-1.1, CDC Ethernet Device
>>> [ 1767.316709] usb 1-1.1: unregistering interface 1-1.1:1.1
>>> [ 1767.317000] usb 1-1.1: usb_disable_device nuking all URBs
>>> [ 1767.535142] hub 1-1:1.0: debounce: port 1: total 200ms stable 100ms
>>> status 0x101
>>> [ 1767.601538] usb 1-1.1: new high-speed USB device number 96 using
>>> musb-hdrc
>>> [ 1767.615236] hub 1-1:1.0: port 1 not reset yet, waiting 10ms
>>> [ 1767.695706] usb 1-1.1: default language 0x0409
>>> [ 1767.695919] usb 1-1.1: udev 96, busnum 1, minor = 95
>>> [ 1767.695933] usb 1-1.1: New USB device found, idVendor=12d1,
>>> idProduct=1f01
>>> [ 1767.695945] usb 1-1.1: New USB device strings: Mfr=1, Product=2,
>>> SerialNumber=3
>>> [ 1767.695955] usb 1-1.1: Product: HUAWEI_MOBILE
>>> [ 1767.695964] usb 1-1.1: Manufacturer: HUAWEI_MOBILE
>>> [ 1767.695973] usb 1-1.1: SerialNumber: 0123456789ABCDEF
>>> [ 1767.696417] usb 1-1.1: usb_probe_device
>>> [ 1767.696434] usb 1-1.1: configuration #1 chosen from 1 choice
>>> [ 1767.696943] usb 1-1.1: adding 1-1.1:1.0 (config #1, interface 0)
>>> [ 1767.697360] usb-storage 1-1.1:1.0: usb_probe_interface
>>> [ 1767.697387] usb-storage 1-1.1:1.0: usb_probe_interface - got id
>>> [ 1767.700483] scsi418 : usb-storage 1-1.1:1.0
>>> [ 1767.701194] hub 1-1:1.0: state 7 ports 4 chg  evt 0002
>>> [ 1768.368244] usb-storage 1-1.1:1.0: disconnect by usbfs
>>> [ 1768.589625] hub 1-1:1.0: state 7 ports 4 chg  evt 0002
>>> [ 1768.589777] hub 1-1:1.0: port 1, status 0101, change 0001, 12 Mb/s
>>> [ 1768.589863] usb 1-1.1: USB disconnect, device number 96
>>> [ 1768.589875] usb 1-1.1: unregistering device
>>> [ 1768.589887] usb 1-1.1: unregistering interface 1-1.1:1.0
>>> [ 1768.590231] usb 1-1.1: usb_disable_device nuking all URBs
>>> [ 1768.699418] hub 1-1:1.0: debounce: port 1: total 100ms stable 100ms
>>> status 0x101
>>> [ 1768.765758] usb 1-1.1: new high-speed USB device number 97 using
>>> musb-hdrc
>>> [ 1768.779445] hub 1-1:1.0: port 1 not reset yet, waiting 10ms
>>> [ 1768.859861] usb 1-1.1: skipped 1 descriptor after configuration
>>> [ 1768.859886] usb 1-1.1: skipped 3 descriptors after interface
>>> [ 1768.859995] usb 1-1.1

Re: [beagleboard] Beagle bone black setup with Intel Real sense camera

[jonnymo]

Perhaps you need to cross compile the Libraries for the BB on a physical
Debian or Ubuntu host or a VM.  Have you tried this?

Cheers,

Jon

On Thu, Oct 29, 2020 at 5:37 PM Vinicius Juvinski <
vinicius.juvin...@gmail.com> wrote:

> Hi,
>
> I don't know but you have several problems on it. First, the RealSense
> require USB 3 - without that you have several limitations on having data.
> Another one is I tried to compile realsense libraries for beagle but I
> couldn't - requires a lot of memory for that.
>
> Em segunda-feira, 19 de outubro de 2020 às 16:22:25 UTC-3,
> jonn...@gmail.com escreveu:
>
>> I personally have no experience with the RealSense camera, but I am
>> interested in this combo as well.
>>
>> I would suspect the best place to start would be the github location:
>>
>> https://github.com/IntelRealSense/librealsense/blob/master/doc/installation.md
>>
>> There was a post by someone who was setting this up with a BeagleBone so
>> you could try to track them down:
>> https://github.com/IntelRealSense/librealsense/issues/3394
>>
>> This looks like a good resource for info.
>> https://support.intelrealsense.com/hc/en-us/community/topics
>>
>> Good luck.
>>
>> Cheers,
>>
>> Jon
>>
>>
>> On Mon, Oct 19, 2020 at 5:18 AM Megha Bhirade 
>> wrote:
>>
>>> Hi,
>>>
>>> I am using Beagle bone black in Linux Ubuntu platform and i want to use
>>> Real sense camera for my application.
>>>
>>> Please anybody suggest me how to setup the Beagle bone black with Real
>>> sense Depth and tracking camera??
>>>
>>> Please suggest me any related link for step by step setup...
>>>
>>> --
>>> 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/4340e28c-4bb9-4995-95bc-bd2baa009f80o%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/2017667b-1742-495f-b49b-9875d5482c07n%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/CAG99bkrmnPeD9gGsJOZT6%2BcBQ7UhqE-yK51gKQtL0TSM5Ly%2Bsg%40mail.gmail.com.

Re: [beagleboard] Beagle bone black setup with Intel Real sense camera

[Vinicius Juvinski]

Hi

Yes, and this made me discover the problems with usb.
What camera are you thinking in use ?

Sent from my iPhone


> Em 29 de out de 2020, à(s) 21:53, jonnymo  escreveu:
> 
> 
> Perhaps you need to cross compile the Libraries for the BB on a physical 
> Debian or Ubuntu host or a VM.  Have you tried this?
> 
> Cheers,
> 
> Jon
> 
>> On Thu, Oct 29, 2020 at 5:37 PM Vinicius Juvinski 
>>  wrote:
>> Hi,
>> 
>> I don't know but you have several problems on it. First, the RealSense 
>> require USB 3 - without that you have several limitations on having data.
>> Another one is I tried to compile realsense libraries for beagle but I 
>> couldn't - requires a lot of memory for that.
>> 
>>> Em segunda-feira, 19 de outubro de 2020 às 16:22:25 UTC-3, 
>>> jonn...@gmail.com escreveu:
>>> I personally have no experience with the RealSense camera, but I am 
>>> interested in this combo as well.
>>> 
>>> I would suspect the best place to start would be the github location:
>>> https://github.com/IntelRealSense/librealsense/blob/master/doc/installation.md
>>> 
>>> There was a post by someone who was setting this up with a BeagleBone so 
>>> you could try to track them down:
>>> https://github.com/IntelRealSense/librealsense/issues/3394
>>> 
>>> This looks like a good resource for info.
>>> https://support.intelrealsense.com/hc/en-us/community/topics
>>> 
>>> Good luck.
>>> 
>>> Cheers,
>>> 
>>> Jon
>>> 
>>> 
 On Mon, Oct 19, 2020 at 5:18 AM Megha Bhirade  wrote:
 Hi,
 
 I am using Beagle bone black in Linux Ubuntu platform and i want to use 
 Real sense camera for my application.
 
 Please anybody suggest me how to setup the Beagle bone black with Real 
 sense Depth and tracking camera??
 
 Please suggest me any related link for step by step setup...
>>> 
 -- 
 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/4340e28c-4bb9-4995-95bc-bd2baa009f80o%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/2017667b-1742-495f-b49b-9875d5482c07n%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/CAG99bkrmnPeD9gGsJOZT6%2BcBQ7UhqE-yK51gKQtL0TSM5Ly%2Bsg%40mail.gmail.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/5679206B-86D9-41AE-AE7B-29F90A4C698C%40gmail.com.

Re: [beagleboard] Beagle bone black setup with Intel Real sense camera

[jonnymo]

I'm not the OP but was looking at a 415 or 435.
According to the following doc, there appears to be USB 2.0 support with a
particular FW version:
https://www.intel.com/content/dam/support/us/en/documents/emerging-technologies/intel-realsense-technology/RealSense-D400-Series-Spec-Update.pdf

I suppose a cable or hub to convert to USB 2.0 would be needed.

However, they do show a RealSense connected to a RasPi, even an A.
https://www.intelrealsense.com/usb2-support-for-intel-realsense-technology/

Jon

On Thu, Oct 29, 2020 at 6:43 PM Vinicius Juvinski <
vinicius.juvin...@gmail.com> wrote:

> Hi
>
> Yes, and this made me discover the problems with usb.
> What camera are you thinking in use ?
>
> Sent from my iPhone
>
>
> Em 29 de out de 2020, à(s) 21:53, jonnymo  escreveu:
>
> 
> Perhaps you need to cross compile the Libraries for the BB on a physical
> Debian or Ubuntu host or a VM.  Have you tried this?
>
> Cheers,
>
> Jon
>
> On Thu, Oct 29, 2020 at 5:37 PM Vinicius Juvinski <
> vinicius.juvin...@gmail.com> wrote:
>
>> Hi,
>>
>> I don't know but you have several problems on it. First, the RealSense
>> require USB 3 - without that you have several limitations on having data.
>> Another one is I tried to compile realsense libraries for beagle but I
>> couldn't - requires a lot of memory for that.
>>
>> Em segunda-feira, 19 de outubro de 2020 às 16:22:25 UTC-3,
>> jonn...@gmail.com escreveu:
>>
>>> I personally have no experience with the RealSense camera, but I am
>>> interested in this combo as well.
>>>
>>> I would suspect the best place to start would be the github location:
>>>
>>> https://github.com/IntelRealSense/librealsense/blob/master/doc/installation.md
>>>
>>> There was a post by someone who was setting this up with a BeagleBone so
>>> you could try to track them down:
>>> https://github.com/IntelRealSense/librealsense/issues/3394
>>>
>>> This looks like a good resource for info.
>>> https://support.intelrealsense.com/hc/en-us/community/topics
>>>
>>> Good luck.
>>>
>>> Cheers,
>>>
>>> Jon
>>>
>>>
>>> On Mon, Oct 19, 2020 at 5:18 AM Megha Bhirade 
>>> wrote:
>>>
 Hi,

 I am using Beagle bone black in Linux Ubuntu platform and i want to use
 Real sense camera for my application.

 Please anybody suggest me how to setup the Beagle bone black with Real
 sense Depth and tracking camera??

 Please suggest me any related link for step by step setup...

 --
 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/4340e28c-4bb9-4995-95bc-bd2baa009f80o%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/2017667b-1742-495f-b49b-9875d5482c07n%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/CAG99bkrmnPeD9gGsJOZT6%2BcBQ7UhqE-yK51gKQtL0TSM5Ly%2Bsg%40mail.gmail.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/5679206B-86D9-41AE-AE7B-29F90A4C698C%40gmail.com
> 
> .
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Grou

[beagleboard] UART Registers program ---reg

[Santosh Maddi]

Hello Every one i have newly purchased beaglebone black... can anyone 
send me UART program using UART registers(ARM335)...to establish a serial 
communication between two systems.

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/ad1447ca-31a7-4b29-b271-8817138319bcn%40googlegroups.com.