[beagleboard] github beagleboard/linux

2018-10-04 Thread Enoch 
Hi Robert Nelson & Friends,

I have a local Linux kernel repository that tracks 
g...@github.com:beagleboard/linux.git
Each time this repository gets updated my git-pull creates numerous 
unmerged files to resolve by hand.
No other git project that I track (including linux-stable) behaves the same.
Can this be avoided?

Thanks, Enoch.

 

-- 
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/4154f609-dd57-4a37-b902-c96b23f6e5bf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] BeagleBoneBlack wireless — does the wifi module need to be power cycled to reset after suspend?

2018-10-04 Thread matthew . redding 


I'm trying to configure the beaglebone black [wireless version - 
4.9.82-ti-r102 #1 SMP PREEMPT] -- running debian 9.3 stretch.

So, I can successfully cause the device to sleep and wake with this command:

/usr/sbin/rtcwake -m mem -u -t $(date +%s -d "20 minutes")

However, the AP run from the BBB wireless does not restart.

I would like to use crontab to then restart the BBB access point, which I 
think I have to do via connmanctl.

Unfortunately, I've not been able to get this to happen. What I am seeing 
is that the wifi module on the BBB wifi appears to require a power cycle or 
a physical reset before the wifi will re-establish properly after a suspend 
and then wake. The following command will not give errors, but it won't 
actually get the AP up and running again:

/usr/bin/connmanctl disable wifi;/usr/bin/connmanctl enable 
wifi;/usr/bin/connmanctl tether wifi "BeagleBone-thing" "Password"

Is this a limitation of the wifi module on this board? Is there a way to 
initiate a reset of the module without powering down the BBB?

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/1919de60-b8e5-4948-a35b-a6148310d4c3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Adafruit i2c install issue

2018-10-04 Thread Graham Haddock 
did you install smbus?
It is a prerequisite.
--- Graham

On Thu, Oct 4, 2018 at 10:34 AM Dennis Lee Bieber 
wrote:

> On Wed, 3 Oct 2018 20:15:04 -0700 (PDT), Chris Bohler
>  declaimed the
> following:
>
> >
> >When attempt to execute Adafruit_BBIO.I2C as I2C:
> >   "Adafruit_BBIO.I2C deprecated. Replace with Adafruit_GPIO.I2C"
> >
>
> Note the message says "deprecated", not that it is no longer
> usable.
>
>
> >  File
> >"/usr/local/lib/python2.7/dist-packages/Adafruit_GPIO-1.0.3-py2.7.egg/Adafruit_GPIO/I2C.py",
>
> >line 98, in __init__
> >import Adafruit_PureIO.smbus
> >ImportError: No module named Adafruit_PureIO.smbus
> >
>
> Looking at the source code for I2C
>
> """
> def __init__(self, address, busnum, i2c_interface=None):
> """Create an instance of the I2C device at the specified address on
> the
> specified I2C bus number."""
> self._address = address
> if i2c_interface is None:
> # Use pure python I2C interface if none is specified.
> import Adafruit_PureIO.smbus
> self._bus = Adafruit_PureIO.smbus.SMBus(busnum)
> else:
> # Otherwise use the provided class to create an smbus
> interface.
> self._bus = i2c_interface(busnum)
> """
>
> you can bypass Adafruit_PureIO by providing your own interface object. I
> have not looked deeper into what such an object would be.
>
> >This from simple python code:
> >
> >import Adafruit_GPIO.I2C as I2C
> >import Adafruit_BBIO.GPIO as GPIO
>
> I suspect if you are using Adafruit_GPIO you should also use
>
> import Adafruit_GPIO.GPIO as GPIO
>
> (that, itself, imports Adafruit_BBIO)
>
>
>
> --
> Wulfraed Dennis Lee Bieber AF6VN
> wlfr...@ix.netcom.comHTTP://wlfraed.home.netcom.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/gtbcrd585viblrvujp5e3ntgo6nq0pjkgl%404ax.com
> .
> For more options, visit https://groups.google.com/d/optout.
>

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

[beagleboard] Checking McASP I2S behavior on PocketBeagle?

2018-10-04 Thread mzwtjp 
Hello.
I am following the below post and trying to play audio on PCM5102A I2S 
board, connected to PocketBeagle header.

https://e2e.ti.com/support/processors/f/791/t/458085?Suggestion-for-improving-the-Sitara-Linux-Audio-DAC-Example

I am using the official Debian image (with PCM5102A driver eneabled).

So far (according to dmesg output) the drivers are initialized and newly 
created ALSA output device can be seen.

>[ 1.553224] asoc-simple-card sound: ASoC: binding 
davinci-mcasp.0-pcm5102a-hifi
>[ 1.662191] asoc-simple-card sound: pcm5102a-hifi 48038000.mcasp mapping ok
>[ 1.76] asoc-simple-card sound: ASoC: no DMI vendor name!

>[ 1.697221] ALSA device list:
>[ 1.697236] #0: I2S slave playback

The problem is, trying 'aplay', but no sound on I2S device.

The header pins are listed as follows in dtb.

0x190 0x8 /* P1.36 mcasp0_aclkx */
0x194 0x8 /* P1.33 mcasp0_fsx */
0x198 0x8 /* P2.32 mcasp0_axr0 */

I examined the pins with osilloscope, but I think there is no signal there.
(Looks like P1.36 left open, P1.33, P2.32 pulled down to GND without 
signal?)

I think there are at least two points I should look into next, but I am not 
sure how to.

1) mcasp0 driver is it working?
2) pinmux functioning so that I am seeing mcasp pins on P1.36/P1.33/P2.34 
physical pins?

Sorry I am new to pinmuxing.
Maybe looking into some debugfs files I can be sure my pinmux definitions 
are working as expected?

FYI. Here are lines containing mcasp from debugfs:

/sys/kernel/debug/pinctrl/pinctrl_handles:

>device: 48038000.mcasp current state: default
> state: default
> type: MUX_GROUP controller pinctrl-single group: mcasp0_pins (313) 
function: mcasp0_pins (313)

/sys/kernel/debug/pinctrl/pinctrl-maps

>device 48038000.mcasp
>state default
>type MUX_GROUP (2)
>controlling device 44e10800.pinmux
>group mcasp0_pins
>function mcasp0_pins

/sys/kernel/debug/pinctrl/44e10800.pinmux/pingroups:

>group: mcasp0_pins
>pin 100 (PIN100)
>pin 101 (PIN101)
>pin 102 (PIN102)

/sys/kernel/debug/pinctrl/44e10800.pinmux/pinmux-functions:

>function: mcasp0_pins, groups = [ mcasp0_pins ]

/sys/kernel/debug/pinctrl/44e10800.pinmux/pinmux-pins:

>pin 100 (PIN100): 48038000.mcasp (GPIO UNCLAIMED) function mcasp0_pins 
group mcasp0_pins
>pin 101 (PIN101): 48038000.mcasp (GPIO UNCLAIMED) function mcasp0_pins 
group mcasp0_pins
>pin 102 (PIN102): 48038000.mcasp (GPIO UNCLAIMED) function mcasp0_pins 
group mcasp0_pins

-- 
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/ed9d1070-475b-4e7a-b5c8-901662acc40d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Checking McASP I2S behavior on PocketBeagle?

2018-10-04 Thread mzwtjp 
Hello.
I am following the below post and trying to play audio on PCM5102A I2S 
board, connected to PocketBeagle header.

https://e2e.ti.com/support/processors/f/791/t/458085?Suggestion-for-improving-the-Sitara-Linux-Audio-DAC-Example

I am using the official Debian image (with PCM5102A driver eneabled).

So far (according to dmesg output) the drivers are initialized and newly 
created ALSA output device can be seen.

>[ 1.553224] asoc-simple-card sound: ASoC: binding 
davinci-mcasp.0-pcm5102a-hifi
>[ 1.662191] asoc-simple-card sound: pcm5102a-hifi 48038000.mcasp mapping ok
>[ 1.76] asoc-simple-card sound: ASoC: no DMI vendor name!

>[ 1.697221] ALSA device list:
>[ 1.697236] #0: I2S slave playback

The problem is, trying 'aplay', but no sound on I2S device.

The header pins are listed as follows in dtb.

0x190 0x8 /* P1.36 mcasp0_aclkx */
0x194 0x8 /* P1.33 mcasp0_fsx */
0x198 0x8 /* P2.32 mcasp0_axr0 */

I examined the pins with osilloscope, but I think there is no signal there.
(Looks like P1.36 left open, P1.33, P2.32 pulled down to GND without 
signal?)

I think there are at least two points I should look into next, but I am not 
sure how to.

1) mcasp0 driver is it working?
2) pinmux functioning so that I am seeing mcasp pins on P1.36/P1.33/P2.34 
physical pins?

Sorry I am new to pinmuxing.
Maybe looking into some debugfs files I can be sure my pinmux definitions 
are working as expected?

FYI. Here are lines containing mcasp from debugfs:

/sys/kernel/debug/pinctrl/pinctrl_handles:

>device: 48038000.mcasp current state: default
> state: default
> type: MUX_GROUP controller pinctrl-single group: mcasp0_pins (313) 
function: mcasp0_pins (313)

/sys/kernel/debug/pinctrl/pinctrl-maps

>device 48038000.mcasp
>state default
>type MUX_GROUP (2)
>controlling device 44e10800.pinmux
>group mcasp0_pins
>function mcasp0_pins

/sys/kernel/debug/pinctrl/44e10800.pinmux/pingroups:

>group: mcasp0_pins
>pin 100 (PIN100)
>pin 101 (PIN101)
>pin 102 (PIN102)

/sys/kernel/debug/pinctrl/44e10800.pinmux/pinmux-functions:

>function: mcasp0_pins, groups = [ mcasp0_pins ]

/sys/kernel/debug/pinctrl/44e10800.pinmux/pinmux-pins:

>pin 100 (PIN100): 48038000.mcasp (GPIO UNCLAIMED) function mcasp0_pins 
group mcasp0_pins
>pin 101 (PIN101): 48038000.mcasp (GPIO UNCLAIMED) function mcasp0_pins 
group mcasp0_pins
>pin 102 (PIN102): 48038000.mcasp (GPIO UNCLAIMED) function mcasp0_pins 
group mcasp0_pins

-- 
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/0d6f5674-57ae-448a-9cd4-8bb8327e0ab3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Beaglebone Blue

2018-10-04 Thread TJF 
Matlab and Simulink is an issue.

Beaglebone hardware is fine for such a task, when executing the cortoller 
loop in real-time at the PRUSS. Ie. one PRUSS for IO (using libpruio 
) and the other to evaluate LIDAR data and 
compute track and motor outputs. Since the ARM software is not involved in 
the controller, it can be a slow application. Ie. written in Python or 
Matlab, just to load and start the firmware on PRUSS and then monitor the 
current system state.

Regards

-- 
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/4dc8b802-e7b4-454c-9b02-42af1e64a22f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.