Re: [beagleboard] SPI TFT Help

[Mark Grosen]

Glad you got it working. I was just looking at this and it seems there is a
similar issue with the default am335x-pocketbeagle.dts. cape-universal is
always enabled, or at least appears to be so from my experiments. The
PocketBeagle behavior is different from the other bones.

Mark

On Mon, Jan 15, 2018 at 5:53 PM Anthony DiGirolamo <
anthony.digirol...@gmail.com> wrote:

> Thanks for the tips Mark! I didn't know about the "dtc -I
> fs /sys/firmware/devicetree/base" command, very helpful.
>
> It looks like PB-simplegaming.dts is now in upstream bb.org-overlays
> <https://github.com/beagleboard/bb.org-overlays> with some additional
> fixes. I applied the same changes to my dts file and the screen is now
> enabled on boot! Here is the working dts:
>
>
> https://github.com/AnthonyDiGirolamo/bb.org-overlays/blob/adafruit28/src/arm/PB-SPI0-ADAFRUIT28-TFT.dts
>
>
> I think my original dts attempt was conflicting with cape-universal. The
> new fixes from jadonk@ <https://github.com/jadonk> disable it and create
> a new cape-universal with the pins needed for the LCD omitted.
>
> Thanks for the working example Jason <https://github.com/jadonk> and
> Robert <https://github.com/RobertCNelson>!
>
>
> On Sunday, January 14, 2018 at 8:20:14 PM UTC-8, Mark Grosen wrote:
>
>> Anthony,
>> I have been trying to get some similar displays working and struggling
>> with device trees. I did get an I2C SSD1331 display going and a SPI
>> ILI9340. I did notice looking at your situation that the
>> am335x-pocketbeagle-simplegaming.dts has an adafruit18 SPI display defined
>> and it uses the same gpios for dc, reset as your adafruit28 display. The
>> -16 error in dmesg is a "device busy" error code so this could be explained
>> by the adafruit18 display getting the gpios first. Look through the dmesg
>> to see if the adadfruit18 display is getting loaded. Perhaps defining
>> different gpios for your display to eliminate any possible conflicts. I
>> found running "dtc -I fs /sys/firmware/devicetree/base" on the board is
>> useful to see the total device tree after booting.
>>
>> Mark
>>
>> On Fri, Jan 12, 2018 at 11:52 PM Anthony DiGirolamo <
>> anthony.d...@gmail.com> wrote:
>>
> Hi all,
>>>
>>> I'm attempting to get a 2.8" TFT LCD
>>> https://www.adafruit.com/product/2090 working on my PocketBeagle.
>>>
>>> Using
>>> https://github.com/jadonk/bb.org-overlays/blob/PB-simplegaming/src/arm/PB-simplegaming.dts
>>> as a reference I made
>>> https://github.com/AnthonyDiGirolamo/bb.org-overlays/blob/adafruit28/src/arm/PB-SPI1-ADAFRUIT28-TFT.dts
>>>
>>> Then I updated /boot/uEnv.txt with
>>>
>>> ###Custom Cape
>>> dtb_overlay=/lib/firmware/PB-SPI1-ADAFRUIT28-TFT.dtbo
>>>
>>>
>>> and ran:
>>>
>>> cd ~/bb.org-overlays
>>> ./install.sh
>>>
>>> On reboot dmesg shows:
>>>
>>> [   37.071131] fbtft: module is from the staging directory, the quality
>>> is unknown, you have been warned.
>>> [   37.154982] fb_ili9341: module is from the staging directory, the
>>> quality is unknown, you have been warned.
>>> [   37.217569] fbtft_of_value: buswidth = 8
>>> [   37.217602] fbtft_of_value: debug = 1
>>> [   37.217611] fbtft_of_value: rotate = 0
>>> [   37.217619] fbtft_of_value: fps = 30
>>> [   37.217942] fb_ili9341 spi1.0: gpio_request_one('reset-gpios'=27)
>>> failed with -16
>>> [   37.417422] fb_ili9341: probe of spi1.0 failed with error -16
>>>
>>>
>>> And /dev/fb0 doesn't exist.
>>>
>>> I then tried:
>>>
>>> sudo rmmod fbtft_device fb_ili9341 fbtft
>>> sudo modprobe fbtft_device name=adafruit28 busnum=1 cs=1 rotate=90 gpios
>>> =dc:65,reset:27
>>>
>>> And dmesg reports:
>>>
>>> [  541.705866] fbtft: module is from the staging directory, the quality
>>> is unknown, you have been warned.
>>> [  541.723630] fbtft_device: module is from the staging directory, the
>>> quality is unknown, you have been warned.
>>> [  541.726930] spi spi1.0: ili9341 spi1.0 32000kHz 8 bits mode=0x00
>>> [  541.726961] spidev spi2.0: spidev spi2.0 24000kHz 8 bits mode=0x00
>>> [  541.726975] spidev spi2.1: spidev spi2.1 24000kHz 8 bits mode=0x00
>>> [  541.727716] fbtft_device: GPIOS used by 'adafruit28':
>>> [  541.727731] fbtft_device: 'dc' = GPIO65
>>> [  541.727738] fbtft_device: 'reset' = GPIO27
>>> [  541.727754] spi s

Re: [beagleboard] SPI TFT Help

[Mark Grosen]

Anthony,
I have been trying to get some similar displays working and struggling with
device trees. I did get an I2C SSD1331 display going and a SPI ILI9340. I
did notice looking at your situation that the
am335x-pocketbeagle-simplegaming.dts has an adafruit18 SPI display defined
and it uses the same gpios for dc, reset as your adafruit28 display. The
-16 error in dmesg is a "device busy" error code so this could be explained
by the adafruit18 display getting the gpios first. Look through the dmesg
to see if the adadfruit18 display is getting loaded. Perhaps defining
different gpios for your display to eliminate any possible conflicts. I
found running "dtc -I fs /sys/firmware/devicetree/base" on the board is
useful to see the total device tree after booting.

Mark

On Fri, Jan 12, 2018 at 11:52 PM Anthony DiGirolamo <
anthony.digirol...@gmail.com> wrote:

> Hi all,
>
> I'm attempting to get a 2.8" TFT LCD https://www.adafruit.com/product/2090
> working on my PocketBeagle.
>
> Using
> https://github.com/jadonk/bb.org-overlays/blob/PB-simplegaming/src/arm/PB-simplegaming.dts
> as a reference I made
> https://github.com/AnthonyDiGirolamo/bb.org-overlays/blob/adafruit28/src/arm/PB-SPI1-ADAFRUIT28-TFT.dts
>
> Then I updated /boot/uEnv.txt with
>
> ###Custom Cape
> dtb_overlay=/lib/firmware/PB-SPI1-ADAFRUIT28-TFT.dtbo
>
>
> and ran:
>
> cd ~/bb.org-overlays
> ./install.sh
>
> On reboot dmesg shows:
>
> [   37.071131] fbtft: module is from the staging directory, the quality is
> unknown, you have been warned.
> [   37.154982] fb_ili9341: module is from the staging directory, the
> quality is unknown, you have been warned.
> [   37.217569] fbtft_of_value: buswidth = 8
> [   37.217602] fbtft_of_value: debug = 1
> [   37.217611] fbtft_of_value: rotate = 0
> [   37.217619] fbtft_of_value: fps = 30
> [   37.217942] fb_ili9341 spi1.0: gpio_request_one('reset-gpios'=27)
> failed with -16
> [   37.417422] fb_ili9341: probe of spi1.0 failed with error -16
>
>
> And /dev/fb0 doesn't exist.
>
> I then tried:
>
> sudo rmmod fbtft_device fb_ili9341 fbtft
> sudo modprobe fbtft_device name=adafruit28 busnum=1 cs=1 rotate=90 gpios=
> dc:65,reset:27
>
> And dmesg reports:
>
> [  541.705866] fbtft: module is from the staging directory, the quality is
> unknown, you have been warned.
> [  541.723630] fbtft_device: module is from the staging directory, the
> quality is unknown, you have been warned.
> [  541.726930] spi spi1.0: ili9341 spi1.0 32000kHz 8 bits mode=0x00
> [  541.726961] spidev spi2.0: spidev spi2.0 24000kHz 8 bits mode=0x00
> [  541.726975] spidev spi2.1: spidev spi2.1 24000kHz 8 bits mode=0x00
> [  541.727716] fbtft_device: GPIOS used by 'adafruit28':
> [  541.727731] fbtft_device: 'dc' = GPIO65
> [  541.727738] fbtft_device: 'reset' = GPIO27
> [  541.727754] spi spi1.0: ili9341 spi1.0 32000kHz 8 bits mode=0x00
> [  541.727765] spidev spi2.0: spidev spi2.0 24000kHz 8 bits mode=0x00
> [  541.727776] spidev spi2.1: spidev spi2.1 24000kHz 8 bits mode=0x00
> [  541.727787] spi spi1.1: fb_ili9341 spi1.1 32000kHz 8 bits mode=0x00
> [  541.778825] fb_ili9341: module is from the staging directory, the
> quality is unknown, you have been warned.
> [  541.796831] fbtft_of_value: buswidth = 8
> [  541.796862] fbtft_of_value: debug = 1
> [  541.796871] fbtft_of_value: rotate = 0
> [  541.796879] fbtft_of_value: fps = 30
> [  541.797216] fb_ili9341 spi1.0: gpio_request_one('reset-gpios'=27)
> failed with -16
> [  541.820918] fb_ili9341: probe of spi1.0 failed with error -16
> [  541.821383] fb_ili9341 spi1.1: fbtft_request_gpios: gpio_request_one(
> 'dc'=65) failed with -16
> [  541.842127] fb_ili9341: probe of spi1.1 failed with error -16
>
> Does anyone know what I'm missing? This page
> https://github.com/notro/fbtft/wiki/BeagleBone-Black#enable-overlay
> mentions:
>
> An unfortunate sideeffect is that capemgr also adds a platform device
>> using the same DT node as the spi device:
>> $ ls -l /sys/devices/ocp.3/481a.spi/
>> total 0
>> drwxr-xr-x 3 root root0 Aug 21 19:18 0.lcd@0
>> This is not a problem for regular spi drivers, but the FBTFT drivers does
>> also support platform devices. This results in the driver probing this
>> device as well. But the probing fails because the gpio has already been
>> requested by the spi device. So, not a functional problem, but rather a
>> cosmetic one with logging of errors in the kernel log that are not actual
>> errors.
>
>
> But for me there is no /dev/fb0 and I'm not sure what to try next. For
> reference I'm running:
>
> $ uname -a
> Linux beaglebone 4.4.110-ti-r142 #1 SMP Mon Jan 8 19:06:43 UTC 2018
> armv7l GNU/Linux
>
> Thanks very much for any help!
>
> --
> 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 

Re: [beagleboard] fbdev and ssd1306

[Mark Grosen]

Thanks, David. We were on the right track. I tried something similar but
failed. I believe it's because the base dtb for the pocket has already
assigned the p2_09 and p2_11 pins to the universal pinmux. I went back to
the base dts and deleted the universal entries and setup a new i2c1_pins
mapping and used those in setting up  - success!

mark@pocket:~$ dmesg | grep fb
[1.304882] ssd1307fb 1-003c: fb0: Solomon SSD1307 framebuffer device
registered, using 256 bytes of video memory
mark@pocket:~$ fbset -i

mode "64x32"
geometry 64 32 64 32 1
timings 0 0 0 0 0 0 0
rgba 1/0,1/0,1/0,0/0
endmode

Frame buffer device information:
Name: Solomon SSD1307
Address : 0x9b637000
Size: 256
Type: PACKED PIXELS
Visual  : MONO10
XPanStep: 0
YPanStep: 0
YWrapStep   : 0
LineLength  : 8
Accelerator : No

The console now shows up at boot, but the text is reversed/mirror image. Is
there a fbdev option to remap the display? I am googling around but have
not seen anything yet ...

Mark

On Wed, Jan 10, 2018 at 7:33 PM David Lechner <da...@lechnology.com> wrote:

> Perhaps something is changing the pinmux later in boot. I'm not seeing
> anything for i2c1, but there is an overlay for i2c2.
> https://github.com/beagleboard/linux/blob/4.14/arch/arm/boot/dts/am335x-bone-pinmux-i2c2.dtsi
>
> You should be able to add this to your overlay and modify it for i2c1.
> Then the pins should get muxed before the i2c driver tries to load.
>
>
>
> On 01/09/2018 11:31 PM, Mark Grosen wrote:
>
> Thanks, David. I am not competent enough on DT yet. I see one of the I2C
> devices has a pinctrl in the device-tree but i2c1 does not. I don't
> understand why/how when I open /dev/i2c-1 from userspace that the pins seem
> to get assigned. Hopefully Robert can help.
>
> Mark
>
> On Tue, Jan 9, 2018 at 7:26 PM David Lechner <da...@lechnology.com> wrote:
>
>> Sounds like a question for RCN. I'm not up to speed on the pinctrl
>> situation on BeagleBone. I'm weird and don't use capemanager or any of the
>> usual BealgeBone stuff.
>>
>> But, I think you are right to think the problem is cause by pin muxing
>> somehow.
>>
>>
>>
>> On 01/09/2018 12:41 AM, Mark Grosen wrote:
>>
>> I moved 4.14.12-ti-r24 and now it gets past the the vbat regulator, but
>> then fails trying to write to the I2C with a bus ready timeout:
>>
>> mark@pocket:~/bb.org-overlays/src/arm$ dmesg | grep -P 'ssd|i2c'
>> [0.508117] omap_i2c 44e0b000.i2c: could not find pctldev for node
>> /ocp/l4_wkup@44c0/scm@21/pinmux@800/pinmux_i2c0_pins, deferring
>> probe
>> [0.509098] omap_i2c 4802a000.i2c: bus 1 rev0.11 at 400 kHz
>> [0.509821] omap_i2c 4819c000.i2c: bus 2 rev0.11 at 400 kHz
>> [1.945474] omap_i2c 4802a000.i2c: timeout waiting for bus ready
>> [1.945496] ssd1307fb 1-003c: Couldn't send I2C command 2.
>> [1.945554] ssd1307fb: probe of 1-003c failed with error -110
>> [2.057076] i2c /dev entries driver
>> [2.178366] input: tps65217_pwr_but as
>> /devices/platform/ocp/44e0b000.i2c/i2c-0/0-0024/tps65217-pwrbutton/input/input0
>> [2.179568] omap_i2c 44e0b000.i2c: bus 0 rev0.11 at 400 kHz
>>
>> After the boot finishes, I can use the device from userspace with no
>> problems. It seems that i2c-1 is registered before the ssd1307fb probe
>> happens. Are pins not assigned at this point?
>>
>> Mark
>>
>> On Mon, Jan 8, 2018 at 7:10 PM David Lechner <da...@lechnology.com>
>> wrote:
>>
>>> The linux driver for this is an i2c driver. So the device tree node that
>>> you added will create an i2c device in the linux kernel (i.e.
>>> /sys/bus/i2c/devices/1-003c). Then udev sees that this device matches the
>>> compatible string of the "ssd1307fb" driver (you will see this listed in
>>> `lsmod`). This driver is bound to the device and calls the drivers probe
>>> function. This is where the error message is coming from. If the probe
>>> function had completed successfully, it would have registered a new fbdev
>>> device.
>>>
>>> It looks like this error is a bug in the linux kernel that was fixed in
>>> kernel v4.11.
>>> <https://github.com/torvalds/linux/commit/cfc5b2b551d8c089079e754525839101b1b43624>
>>> <https://github.com/torvalds/linux/commit/cfc5b2b551d8c089079e754525839101b1b43624>
>>> .
>>>
>>> You can work around this by adding a fixed regulator to the device tree
>>> and adding it to your device. Or, if you are compiling your own kernel
>>> anyway, you can grab the patch 

Re: [beagleboard] fbdev and ssd1306

[Mark Grosen]

Thanks, David. I am not competent enough on DT yet. I see one of the I2C
devices has a pinctrl in the device-tree but i2c1 does not. I don't
understand why/how when I open /dev/i2c-1 from userspace that the pins seem
to get assigned. Hopefully Robert can help.

Mark

On Tue, Jan 9, 2018 at 7:26 PM David Lechner <da...@lechnology.com> wrote:

> Sounds like a question for RCN. I'm not up to speed on the pinctrl
> situation on BeagleBone. I'm weird and don't use capemanager or any of the
> usual BealgeBone stuff.
>
> But, I think you are right to think the problem is cause by pin muxing
> somehow.
>
>
>
> On 01/09/2018 12:41 AM, Mark Grosen wrote:
>
> I moved 4.14.12-ti-r24 and now it gets past the the vbat regulator, but
> then fails trying to write to the I2C with a bus ready timeout:
>
> mark@pocket:~/bb.org-overlays/src/arm$ dmesg | grep -P 'ssd|i2c'
> [0.508117] omap_i2c 44e0b000.i2c: could not find pctldev for node
> /ocp/l4_wkup@44c0/scm@21/pinmux@800/pinmux_i2c0_pins, deferring
> probe
> [0.509098] omap_i2c 4802a000.i2c: bus 1 rev0.11 at 400 kHz
> [0.509821] omap_i2c 4819c000.i2c: bus 2 rev0.11 at 400 kHz
> [1.945474] omap_i2c 4802a000.i2c: timeout waiting for bus ready
> [1.945496] ssd1307fb 1-003c: Couldn't send I2C command 2.
> [1.945554] ssd1307fb: probe of 1-003c failed with error -110
> [2.057076] i2c /dev entries driver
> [2.178366] input: tps65217_pwr_but as
> /devices/platform/ocp/44e0b000.i2c/i2c-0/0-0024/tps65217-pwrbutton/input/input0
> [2.179568] omap_i2c 44e0b000.i2c: bus 0 rev0.11 at 400 kHz
>
> After the boot finishes, I can use the device from userspace with no
> problems. It seems that i2c-1 is registered before the ssd1307fb probe
> happens. Are pins not assigned at this point?
>
> Mark
>
> On Mon, Jan 8, 2018 at 7:10 PM David Lechner <da...@lechnology.com> wrote:
>
>> The linux driver for this is an i2c driver. So the device tree node that
>> you added will create an i2c device in the linux kernel (i.e.
>> /sys/bus/i2c/devices/1-003c). Then udev sees that this device matches the
>> compatible string of the "ssd1307fb" driver (you will see this listed in
>> `lsmod`). This driver is bound to the device and calls the drivers probe
>> function. This is where the error message is coming from. If the probe
>> function had completed successfully, it would have registered a new fbdev
>> device.
>>
>> It looks like this error is a bug in the linux kernel that was fixed in
>> kernel v4.11.
>> <https://github.com/torvalds/linux/commit/cfc5b2b551d8c089079e754525839101b1b43624>
>> <https://github.com/torvalds/linux/commit/cfc5b2b551d8c089079e754525839101b1b43624>
>> .
>>
>> You can work around this by adding a fixed regulator to the device tree
>> and adding it to your device. Or, if you are compiling your own kernel
>> anyway, you can grab the patch I linked.
>>
>> On 1/8/18 8:09 PM, Mark Grosen wrote:
>>
>> mark@pocket:~$ dmesg | grep -P 'fb|ssd'
>> [2.165499] ssd1307fb 1-003c: failed to get VBAT regulator: -19
>>
>> How does fbdev "find" the ssd1306?
>>
>> On Mon, Jan 8, 2018 at 5:51 PM David Lechner <da...@lechnology.com>
>> wrote:
>>
>>> On 01/08/2018 07:27 PM, Mark Grosen wrote:
>>>
>>> On Mon, Jan 8, 2018 at 10:08 AM David Lechner <da...@lechnology.com>
>>> wrote:
>>>
>>>> On 01/07/2018 05:59 PM, Mark Grosen wrote:
>>>> > I am trying to get the kernel driver for the ssd1306 working with the
>>>> PocketBeagle USB HUB cape which has a 64x32 SSD1306 display (
>>>> https://www.tindie.com/products/microwavemont/oled-with-24-port-usb-hub-cape-for-pocketbeagle/)
>>>> I know it is physically working as I can use it via user-mode I2C. I
>>>> believe a small change is needed to support the unusual 64 pixel width of
>>>> this board. I have built and loaded a new kernel and have a .dtbo
>>>>
>>>> And what does your device tree overlay look like?
>>>>
>>>
>>> /dts-v1/;
>>> /plugin/;
>>>
>>> #include 
>>> #include 
>>> #include 
>>>
>>> / {
>>> fragment@0 {
>>> target = <>;
>>> __overlay__ {
>>> status = "okay";
>>>
>>> #address-cells = <1>;
>>> #size-cells = <0>;
>>>
>>> ssd1306: oled@3c {
>>> compatible = "solomon,ssd1306fb-i2c";
>>> reg = <0x3c>;
>>> solomon,width = <64>;
&

Re: [beagleboard] fbdev and ssd1306

[Mark Grosen]

I moved 4.14.12-ti-r24 and now it gets past the the vbat regulator, but
then fails trying to write to the I2C with a bus ready timeout:

mark@pocket:~/bb.org-overlays/src/arm$ dmesg | grep -P 'ssd|i2c'
[0.508117] omap_i2c 44e0b000.i2c: could not find pctldev for node
/ocp/l4_wkup@44c0/scm@21/pinmux@800/pinmux_i2c0_pins, deferring
probe
[0.509098] omap_i2c 4802a000.i2c: bus 1 rev0.11 at 400 kHz
[0.509821] omap_i2c 4819c000.i2c: bus 2 rev0.11 at 400 kHz
[1.945474] omap_i2c 4802a000.i2c: timeout waiting for bus ready
[1.945496] ssd1307fb 1-003c: Couldn't send I2C command 2.
[1.945554] ssd1307fb: probe of 1-003c failed with error -110
[2.057076] i2c /dev entries driver
[2.178366] input: tps65217_pwr_but as
/devices/platform/ocp/44e0b000.i2c/i2c-0/0-0024/tps65217-pwrbutton/input/input0
[2.179568] omap_i2c 44e0b000.i2c: bus 0 rev0.11 at 400 kHz

After the boot finishes, I can use the device from userspace with no
problems. It seems that i2c-1 is registered before the ssd1307fb probe
happens. Are pins not assigned at this point?

Mark

On Mon, Jan 8, 2018 at 7:10 PM David Lechner <da...@lechnology.com> wrote:

> The linux driver for this is an i2c driver. So the device tree node that
> you added will create an i2c device in the linux kernel (i.e.
> /sys/bus/i2c/devices/1-003c). Then udev sees that this device matches the
> compatible string of the "ssd1307fb" driver (you will see this listed in
> `lsmod`). This driver is bound to the device and calls the drivers probe
> function. This is where the error message is coming from. If the probe
> function had completed successfully, it would have registered a new fbdev
> device.
>
> It looks like this error is a bug in the linux kernel that was fixed in
> kernel v4.11.
> <https://github.com/torvalds/linux/commit/cfc5b2b551d8c089079e754525839101b1b43624>
> <https://github.com/torvalds/linux/commit/cfc5b2b551d8c089079e754525839101b1b43624>
> .
>
> You can work around this by adding a fixed regulator to the device tree
> and adding it to your device. Or, if you are compiling your own kernel
> anyway, you can grab the patch I linked.
>
> On 1/8/18 8:09 PM, Mark Grosen wrote:
>
> mark@pocket:~$ dmesg | grep -P 'fb|ssd'
> [2.165499] ssd1307fb 1-003c: failed to get VBAT regulator: -19
>
> How does fbdev "find" the ssd1306?
>
> On Mon, Jan 8, 2018 at 5:51 PM David Lechner <da...@lechnology.com> wrote:
>
>> On 01/08/2018 07:27 PM, Mark Grosen wrote:
>>
>> On Mon, Jan 8, 2018 at 10:08 AM David Lechner <da...@lechnology.com>
>> wrote:
>>
>>> On 01/07/2018 05:59 PM, Mark Grosen wrote:
>>> > I am trying to get the kernel driver for the ssd1306 working with the
>>> PocketBeagle USB HUB cape which has a 64x32 SSD1306 display (
>>> https://www.tindie.com/products/microwavemont/oled-with-24-port-usb-hub-cape-for-pocketbeagle/)
>>> I know it is physically working as I can use it via user-mode I2C. I
>>> believe a small change is needed to support the unusual 64 pixel width of
>>> this board. I have built and loaded a new kernel and have a .dtbo
>>>
>>> And what does your device tree overlay look like?
>>>
>>
>> /dts-v1/;
>> /plugin/;
>>
>> #include 
>> #include 
>> #include 
>>
>> / {
>> fragment@0 {
>> target = <>;
>> __overlay__ {
>> status = "okay";
>>
>> #address-cells = <1>;
>> #size-cells = <0>;
>>
>> ssd1306: oled@3c {
>> compatible = "solomon,ssd1306fb-i2c";
>> reg = <0x3c>;
>> solomon,width = <64>;
>> solomon,height = <32>;
>> solomon,page-offset = <0>;
>> };
>> };
>> };
>> };
>>
>>
>>>
>>> > loaded via u-boot with 4.4.88-ti-r128 kernel. It shows up in
>>> /proc/device-tree correctly (at least as far as I can tell - the entries
>>> match the dts values). I am missing how to get this connected to the
>>> framebuffer world - there is no /dev/fb0 showing up. I see the config
>>> options appear to be enabled (I am using the defconfig).
>>>
>>> And which options did you enable/are enabled?
>>
>>
>> mark@pocket:~$ zcat /proc/config.gz | grep CONFIG_FB | grep -v '#'
>> CONFIG_FB=y
>> CONFIG_FB_CMDLINE=y
>> CONFIG_FB_NOTIFY=y
>> CONFIG_FB_CFB_FILLRECT=y
>> CONFIG_FB_CFB_COPYAREA=y
>> CONFIG_FB_CFB_IMAGEBLIT=y
>> CONFIG_FB_SYS_FILLRECT=y
>> CONFIG_FB_SYS_COPYAREA=y
>> CONFIG_FB_SYS_IMAGEBLIT=y
>> 

Re: [beagleboard] fbdev and ssd1306

[Mark Grosen]

Thanks. That was a bit embarrassing - I saw the message in dmesg but
assumed it was benign since the /proc/device-tree entry was there. I'll
move to a later kernel and try my fix there. I appreciate your quick help!

Mark

On Mon, Jan 8, 2018 at 7:10 PM David Lechner <da...@lechnology.com> wrote:

> The linux driver for this is an i2c driver. So the device tree node that
> you added will create an i2c device in the linux kernel (i.e.
> /sys/bus/i2c/devices/1-003c). Then udev sees that this device matches the
> compatible string of the "ssd1307fb" driver (you will see this listed in
> `lsmod`). This driver is bound to the device and calls the drivers probe
> function. This is where the error message is coming from. If the probe
> function had completed successfully, it would have registered a new fbdev
> device.
>
> It looks like this error is a bug in the linux kernel that was fixed in
> kernel v4.11.
> <https://github.com/torvalds/linux/commit/cfc5b2b551d8c089079e754525839101b1b43624>
> <https://github.com/torvalds/linux/commit/cfc5b2b551d8c089079e754525839101b1b43624>
> .
>
> You can work around this by adding a fixed regulator to the device tree
> and adding it to your device. Or, if you are compiling your own kernel
> anyway, you can grab the patch I linked.
>
> On 1/8/18 8:09 PM, Mark Grosen wrote:
>
> mark@pocket:~$ dmesg | grep -P 'fb|ssd'
> [2.165499] ssd1307fb 1-003c: failed to get VBAT regulator: -19
>
> How does fbdev "find" the ssd1306?
>
> On Mon, Jan 8, 2018 at 5:51 PM David Lechner <da...@lechnology.com> wrote:
>
>> On 01/08/2018 07:27 PM, Mark Grosen wrote:
>>
>> On Mon, Jan 8, 2018 at 10:08 AM David Lechner <da...@lechnology.com>
>> wrote:
>>
>>> On 01/07/2018 05:59 PM, Mark Grosen wrote:
>>> > I am trying to get the kernel driver for the ssd1306 working with the
>>> PocketBeagle USB HUB cape which has a 64x32 SSD1306 display (
>>> https://www.tindie.com/products/microwavemont/oled-with-24-port-usb-hub-cape-for-pocketbeagle/)
>>> I know it is physically working as I can use it via user-mode I2C. I
>>> believe a small change is needed to support the unusual 64 pixel width of
>>> this board. I have built and loaded a new kernel and have a .dtbo
>>>
>>> And what does your device tree overlay look like?
>>>
>>
>> /dts-v1/;
>> /plugin/;
>>
>> #include 
>> #include 
>> #include 
>>
>> / {
>> fragment@0 {
>> target = <>;
>> __overlay__ {
>> status = "okay";
>>
>> #address-cells = <1>;
>> #size-cells = <0>;
>>
>> ssd1306: oled@3c {
>> compatible = "solomon,ssd1306fb-i2c";
>> reg = <0x3c>;
>> solomon,width = <64>;
>> solomon,height = <32>;
>> solomon,page-offset = <0>;
>> };
>> };
>> };
>> };
>>
>>
>>>
>>> > loaded via u-boot with 4.4.88-ti-r128 kernel. It shows up in
>>> /proc/device-tree correctly (at least as far as I can tell - the entries
>>> match the dts values). I am missing how to get this connected to the
>>> framebuffer world - there is no /dev/fb0 showing up. I see the config
>>> options appear to be enabled (I am using the defconfig).
>>>
>>> And which options did you enable/are enabled?
>>
>>
>> mark@pocket:~$ zcat /proc/config.gz | grep CONFIG_FB | grep -v '#'
>> CONFIG_FB=y
>> CONFIG_FB_CMDLINE=y
>> CONFIG_FB_NOTIFY=y
>> CONFIG_FB_CFB_FILLRECT=y
>> CONFIG_FB_CFB_COPYAREA=y
>> CONFIG_FB_CFB_IMAGEBLIT=y
>> CONFIG_FB_SYS_FILLRECT=y
>> CONFIG_FB_SYS_COPYAREA=y
>> CONFIG_FB_SYS_IMAGEBLIT=y
>> CONFIG_FB_SYS_FOPS=y
>> CONFIG_FB_DEFERRED_IO=y
>> CONFIG_FB_BACKLIGHT=y
>> CONFIG_FB_MODE_HELPERS=y
>> CONFIG_FB_TILEBLITTING=y
>> CONFIG_FB_SMSCUFX=m
>> CONFIG_FB_UDL=m
>> CONFIG_FB_SIMPLE=y
>> CONFIG_FB_SSD1307=y
>>
>>
>>>
>>>
>> Looks alright to me. Is there any error in `dmesg`?
>>
>>
>> --
>> 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/8d1b9f53-ab73-6bf4-92d0-ebcfb0

Re: [beagleboard] fbdev and ssd1306

[Mark Grosen]

mark@pocket:~$ dmesg | grep -P 'fb|ssd'
[2.165499] ssd1307fb 1-003c: failed to get VBAT regulator: -19

How does fbdev "find" the ssd1306?

On Mon, Jan 8, 2018 at 5:51 PM David Lechner <da...@lechnology.com> wrote:

> On 01/08/2018 07:27 PM, Mark Grosen wrote:
>
> On Mon, Jan 8, 2018 at 10:08 AM David Lechner <da...@lechnology.com>
> wrote:
>
>> On 01/07/2018 05:59 PM, Mark Grosen wrote:
>> > I am trying to get the kernel driver for the ssd1306 working with the
>> PocketBeagle USB HUB cape which has a 64x32 SSD1306 display (
>> https://www.tindie.com/products/microwavemont/oled-with-24-port-usb-hub-cape-for-pocketbeagle/)
>> I know it is physically working as I can use it via user-mode I2C. I
>> believe a small change is needed to support the unusual 64 pixel width of
>> this board. I have built and loaded a new kernel and have a .dtbo
>>
>> And what does your device tree overlay look like?
>>
>
> /dts-v1/;
> /plugin/;
>
> #include 
> #include 
> #include 
>
> / {
> fragment@0 {
> target = <>;
> __overlay__ {
> status = "okay";
>
> #address-cells = <1>;
> #size-cells = <0>;
>
> ssd1306: oled@3c {
> compatible = "solomon,ssd1306fb-i2c";
> reg = <0x3c>;
> solomon,width = <64>;
> solomon,height = <32>;
> solomon,page-offset = <0>;
> };
> };
> };
> };
>
>
>>
>> > loaded via u-boot with 4.4.88-ti-r128 kernel. It shows up in
>> /proc/device-tree correctly (at least as far as I can tell - the entries
>> match the dts values). I am missing how to get this connected to the
>> framebuffer world - there is no /dev/fb0 showing up. I see the config
>> options appear to be enabled (I am using the defconfig).
>>
>> And which options did you enable/are enabled?
>
>
> mark@pocket:~$ zcat /proc/config.gz | grep CONFIG_FB | grep -v '#'
> CONFIG_FB=y
> CONFIG_FB_CMDLINE=y
> CONFIG_FB_NOTIFY=y
> CONFIG_FB_CFB_FILLRECT=y
> CONFIG_FB_CFB_COPYAREA=y
> CONFIG_FB_CFB_IMAGEBLIT=y
> CONFIG_FB_SYS_FILLRECT=y
> CONFIG_FB_SYS_COPYAREA=y
> CONFIG_FB_SYS_IMAGEBLIT=y
> CONFIG_FB_SYS_FOPS=y
> CONFIG_FB_DEFERRED_IO=y
> CONFIG_FB_BACKLIGHT=y
> CONFIG_FB_MODE_HELPERS=y
> CONFIG_FB_TILEBLITTING=y
> CONFIG_FB_SMSCUFX=m
> CONFIG_FB_UDL=m
> CONFIG_FB_SIMPLE=y
> CONFIG_FB_SSD1307=y
>
>
>>
>>
> Looks alright to me. Is there any error in `dmesg`?
>
>
> --
> 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/8d1b9f53-ab73-6bf4-92d0-ebcfb072bb06%40lechnology.com
> <https://groups.google.com/d/msgid/beagleboard/8d1b9f53-ab73-6bf4-92d0-ebcfb072bb06%40lechnology.com?utm_medium=email_source=footer>
> .
> 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/CAL8ugEcSLFrFasGKqfX44iR-UDhzeNE9nt4u4Nfirj9oDnC20A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] fbdev and ssd1306

[Mark Grosen]

On Mon, Jan 8, 2018 at 10:08 AM David Lechner <da...@lechnology.com> wrote:

> On 01/07/2018 05:59 PM, Mark Grosen wrote:
> > I am trying to get the kernel driver for the ssd1306 working with the
> PocketBeagle USB HUB cape which has a 64x32 SSD1306 display (
> https://www.tindie.com/products/microwavemont/oled-with-24-port-usb-hub-cape-for-pocketbeagle/)
> I know it is physically working as I can use it via user-mode I2C. I
> believe a small change is needed to support the unusual 64 pixel width of
> this board. I have built and loaded a new kernel and have a .dtbo
>
> And what does your device tree overlay look like?
>

/dts-v1/;
/plugin/;

#include 
#include 
#include 

/ {
fragment@0 {
target = <>;
__overlay__ {
status = "okay";

#address-cells = <1>;
#size-cells = <0>;

ssd1306: oled@3c {
compatible = "solomon,ssd1306fb-i2c";
reg = <0x3c>;
solomon,width = <64>;
solomon,height = <32>;
solomon,page-offset = <0>;
};
};
};
};


>
> > loaded via u-boot with 4.4.88-ti-r128 kernel. It shows up in
> /proc/device-tree correctly (at least as far as I can tell - the entries
> match the dts values). I am missing how to get this connected to the
> framebuffer world - there is no /dev/fb0 showing up. I see the config
> options appear to be enabled (I am using the defconfig).
>
> And which options did you enable/are enabled?


mark@pocket:~$ zcat /proc/config.gz | grep CONFIG_FB | grep -v '#'
CONFIG_FB=y
CONFIG_FB_CMDLINE=y
CONFIG_FB_NOTIFY=y
CONFIG_FB_CFB_FILLRECT=y
CONFIG_FB_CFB_COPYAREA=y
CONFIG_FB_CFB_IMAGEBLIT=y
CONFIG_FB_SYS_FILLRECT=y
CONFIG_FB_SYS_COPYAREA=y
CONFIG_FB_SYS_IMAGEBLIT=y
CONFIG_FB_SYS_FOPS=y
CONFIG_FB_DEFERRED_IO=y
CONFIG_FB_BACKLIGHT=y
CONFIG_FB_MODE_HELPERS=y
CONFIG_FB_TILEBLITTING=y
CONFIG_FB_SMSCUFX=m
CONFIG_FB_UDL=m
CONFIG_FB_SIMPLE=y
CONFIG_FB_SSD1307=y


>
>

-- 
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/CAL8ugEcgztGeTqd%2BQvSd1YyfPZN%3DMwxVVjDECOkCgjH4i%2BQHnQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] fbdev and ssd1306

[Mark Grosen]

I am trying to get the kernel driver for the ssd1306 working with the
PocketBeagle USB HUB cape which has a 64x32 SSD1306 display (
https://www.tindie.com/products/microwavemont/oled-with-24-port-usb-hub-cape-for-pocketbeagle/)
I know it is physically working as I can use it via user-mode I2C. I
believe a small change is needed to support the unusual 64 pixel width of
this board. I have built and loaded a new kernel and have a .dtbo loaded
via u-boot with 4.4.88-ti-r128 kernel. It shows up in /proc/device-tree
correctly (at least as far as I can tell - the entries match the dts
values). I am missing how to get this connected to the framebuffer world -
there is no /dev/fb0 showing up. I see the config options appear to be
enabled (I am using the defconfig). My googling did not turn up anything
other than others stuck in a similar situation on RPi's.

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/CAL8ugEdZAp6n6Upwf0%2B%3DSV%3D%2BE35hDRPABM5Dgb21%2B6Dq3eC9GA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: ENC28J60 Click on PocketBeagle

[Mark Grosen]

Used to be you could set mac address via env ethaddr in uboot. Does this
still work or via device tree? Seems like the kernel driver would support
this:
https://elixir.free-electrons.com/linux/latest/source/drivers/net/ethernet/microchip/enc28j60.c#L1590

Mark

On Thu, Oct 19, 2017 at 8:11 AM Robert Nelson 
wrote:

> On Thu, Oct 19, 2017 at 10:05 AM, Jason Kridner 
> wrote:
> > So can we configure the MAC on the ENC? The MAC address is fetched using
> > am335x_evm.sh in /opt/scripts. Seems like it could be modified for if an
> > adapter is detected in the kernel.
>
> Yeah, that's my current thinking..
>
> > Aside, u-boot configures the on-board MII because the code was difficult
> to
> > cut out.
>
> 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/CAOCHtYhzidVYiXSkLn4uvbQhg_-P6z7P%2BWySTYb6pqPKzb5npg%40mail.gmail.com
> .
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [beagleboard] Announcing $25 PocketBeagle

[Mark Grosen]

Looks great! Any recommendations for TCP/IP connectivity, wired or wireless?

On Thu, Sep 21, 2017, 5:35 PM Jason Kridner 
wrote:

> https://beagleboard.org/pocket
>
> Trying to get a few things documented at
> https://github.com/beagleboard/pocketbeagle/wiki/FAQ, so feel free to
> start throwing out questions here, on IRC or on the github site.
>
>
> --
> 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/CA%2BT6QPmwE7Pri0_Jyx1Wp8n40rHJF_CziJj%2B0nceNkL%2B2RH24w%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [beagleboard] wifi intermittent

[Mark Grosen]

I have had better luck using the iwconfig method to disable power
management:

*sudo iwconfig wlan0 power off*

Substitute the appropriate name for wlan0 as needed.

Mark

On Fri, Dec 2, 2016 at 12:32 PM Sebastián Sáez  wrote:

Hi guys!

I'm using a BeagleBone Green Wireless.
For programming I'm using putty with ssh through a home router and from
time to time my connection closes.

I switched off the power save mode with:

echo 0 > /sys/kernel/debug/ieee80211/phy0/wlcore/sleep_auth


But nothing changes.

Any ideas?


regards,
Sebastián

-- 
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/1463e486-2738-49c3-9f0a-00f8b4fc9649%40googlegroups.com

.
For more options, visit https://groups.google.com/d/optout.

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

Re: [beagleboard] wifi works when BBGW first powered on, but not after a warm reboot

[Mark Grosen]

Yes, I have this problem, too. I have not tried figuring out a SW solution.
I just power cycle on the thankfully few times I need to reboot.

Mark

On Wed, Sep 14, 2016, 11:34 AM Stephane Charette 
wrote:

> On Saturday, September 10, 2016 at 2:09:16 PM UTC-7, Stephane Charette
> wrote:
>>
>> On Friday, September 9, 2016 at 1:15:42 PM UTC-7, RobertCNelson wrote:
>>>
>>> On Fri, Sep 9, 2016 at 2:45 PM, Stephane Charette
>>>  wrote:
>>> > When I first plug power into my BBGW, everything works great.  But if
>>> I
>>> > issue a "reboot" or "shutdown -r now" command, when the device boots
>>> back up
>>> > I have no wifi.
>>> >
>>> > Anyone else having problems with wifi not working when doing a "warm"
>>> > reboot?  Is this a known problem, or is there a known workaround?
>>>
>>> I still don't think we are properly resetting the wl18xx on startup.
>>> (in u-boot is the easiest place)
>>>
>>
>
> I tried on TI's forums to get help for this issue, but their only response
> is to contact the BBGW community here or on IRC since I'm using one of
> RCN's builds.
>
>
>1. Is anyone else seeing this problem where WIFI on BBGW doesn't work
>on warm reboots?
>2. Can someone point me to where the source/scripts are located for
>Das U-Boot used on recent BBGW builds?  Is there something like a github
>project from which the BBGW builds are generated?
>
>
> Thanks,
>
> Stéphane
>
> --
> 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/acb02ff4-408a-4797-a2ec-4406117fde35%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [beagleboard] WiFi on BBGW stopped after upgrade

[Mark Grosen]

I tried that with no joy (had to attach ftdi to get serial console). Is
there a newer kernel to try?

On Wed, Aug 10, 2016, 3:24 PM Robert Nelson <robertcnel...@gmail.com> wrote:

> Hi Mark,
>
> On Wed, Aug 10, 2016 at 5:14 PM, Mark Grosen <m...@grosen.org> wrote:
> > I had a working Debian system on the BBGW. I did an apt-get upgrade today
> > and re-booted and now the WL8 will not initialize. I saw there was a
> > firmware update in the upgrade, so maybe this is causing a problem?
> >
> > mark@markbbgw:~$ cat /etc/dogtag
> > BeagleBoard.org Debian Image 2016-06-19
> > mark@markbbgw:~$ uname -a
> > Linux markbbgw 4.4.12-ti-r31 #1 SMP Thu Jun 16 18:48:27 UTC 2016 armv7l
> > GNU/Linux
> > mark@markbbgw:~$ cat /proc/cmdline
> > console=ttyO0,115200n8 root=UUID=066b85e2-8976-4b0c-99f4-e5525a67998c ro
> > rootfstype=ext4 rootwait coherent_pool=1M quiet cape_universal=enable
> >
> > From dmesg:
> > [   27.010423] wlcore: wl18xx HW: 183x or 180x, PG 2.2 (ROM 0x11)
> > [   27.133864] wlcore: loaded
> > [   34.349928] wlcore: ERROR timeout waiting for the hardware to complete
> > initialization
> > [   38.623450] wlcore: ERROR timeout waiting for the hardware to complete
> > initialization
> > [   42.979266] wlcore: ERROR timeout waiting for the hardware to complete
> > initialization
> > [   42.998770] wlcore: ERROR firmware boot failed despite 3 retries
> > [   47.470802] wlcore: ERROR timeout waiting for the hardware to complete
> > initialization
> > [   52.035220] wlcore: ERROR timeout waiting for the hardware to complete
> > initialization
> > [   56.555735] wlcore: ERROR timeout waiting for the hardware to complete
> > initialization
> > [   56.574659] wlcore: ERROR firmware boot failed despite 3 retries
> >
> > After boot, trying an ifup:
> >
> >  linux% sudo ifup wlan0
> > [  373.798288] wlcore: ERROR ELP wakeup timeout!
> > [  375.780033] wlcore: ERROR timeout waiting for the hardware to complete
> > initialization
> > [  377.746317] wlcore: ERROR timeout waiting for the hardware to complete
> > initialization
> > [  379.724491] wlcore: ERROR timeout waiting for the hardware to complete
> > initialization
> > [  379.733485] wlcore: ERROR firmware boot failed despite 3 retries
>
> This is getting better in kernel's such as: 4.4.16-ti-r38
>
> Where the kernel will try to reset the wl18xx and try to re-load the
> firmware.
>
> But yeah, still working on this annoying bug...
>
> The easy fix is to unplug let it sit for a few seconds and power it back
> up..
>
> 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/CAOCHtYisexP3Ha-3%3DMkXX1%2BBBK%3DakEccbj0vQrS2P0fRuDRimQ%40mail.gmail.com
> .
> For more options, visit https://groups.google.com/d/optout.
>

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

[beagleboard] WiFi on BBGW stopped after upgrade

[Mark Grosen]

I had a working Debian system on the BBGW. I did an apt-get upgrade today
and re-booted and now the WL8 will not initialize. I saw there was a
firmware update in the upgrade, so maybe this is causing a problem?

mark@markbbgw:~$ cat /etc/dogtag
BeagleBoard.org Debian Image 2016-06-19
mark@markbbgw:~$ uname -a
Linux markbbgw 4.4.12-ti-r31 #1 SMP Thu Jun 16 18:48:27 UTC 2016 armv7l
GNU/Linux
mark@markbbgw:~$ cat /proc/cmdline
console=ttyO0,115200n8 root=UUID=066b85e2-8976-4b0c-99f4-e5525a67998c ro
rootfstype=ext4 rootwait coherent_pool=1M quiet cape_universal=enable

>From dmesg:
[   27.010423] wlcore: wl18xx HW: 183x or 180x, PG 2.2 (ROM 0x11)
[   27.133864] wlcore: loaded
[   34.349928] wlcore: ERROR timeout waiting for the hardware to complete
initialization
[   38.623450] wlcore: ERROR timeout waiting for the hardware to complete
initialization
[   42.979266] wlcore: ERROR timeout waiting for the hardware to complete
initialization
[   42.998770] wlcore: ERROR firmware boot failed despite 3 retries
[   47.470802] wlcore: ERROR timeout waiting for the hardware to complete
initialization
[   52.035220] wlcore: ERROR timeout waiting for the hardware to complete
initialization
[   56.555735] wlcore: ERROR timeout waiting for the hardware to complete
initialization
[   56.574659] wlcore: ERROR firmware boot failed despite 3 retries

After boot, trying an ifup:

 linux% sudo ifup wlan0
[  373.798288] wlcore: ERROR ELP wakeup timeout!
[  375.780033] wlcore: ERROR timeout waiting for the hardware to complete
initialization
[  377.746317] wlcore: ERROR timeout waiting for the hardware to complete
initialization
[  379.724491] wlcore: ERROR timeout waiting for the hardware to complete
initialization
[  379.733485] wlcore: ERROR firmware boot failed despite 3 retries

-- 
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/CAL8ugEctYWsGt7RCPNyF-RsYjY5MQi8xhv%2BW0VcPLe0hUh5J%3Dg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] BBGW console packages?

[Mark Grosen]

Sorry - I am not using Bluetooth or BLE with the BBGW. One guess based on
WiFi would be to check if there is a "power save" option for BLE. I've
noticed with WiFi that with power save "on" connections are slower and more
random.

Mark

On Fri, Jul 8, 2016 at 2:05 AM  wrote:

> Hi guys,
>
> We bought few BBGW and using them for discovering  Ibeacons, but we have
> some problems. We wrote program in NODE.js and using NOBLE. Problem is that
> bluetooth is working strange, it scaning few seconds and stops for 5-6, and
> then randomly starts and stop scaning. We tried our program with USB
> donggle BLE and it's working fine, every 1 sec we are getting Beacons(they
> have 1 sec broadcast frequency). Please can you advice what to do?
>

-- 
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/CAL8ugEchq4az1O2nEpKZVAo8OozJ-Ds5McEc6_vrF_ujpOhSKg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] BBGW console packages?

[Mark Grosen]

On Fri, Jul 1, 2016 at 1:42 PM Robert Nelson <robertcnel...@gmail.com>
wrote:

> On Fri, Jul 1, 2016 at 2:58 PM, Mark Grosen <m...@grosen.org> wrote:
> > On to Bluetooth - I see there is a bb-wl18xx-bluetooth.service in the
> > bb-wl18xx-firmware package:
> >
> https://github.com/rcn-ee/repos/blob/master/bb-wl18xx-firmware/suite/jessie/debian/bb-wl18xx-bluetooth.service
> > and systemctl shows it enabled, but it does not seem to have run. I have
> to
> > manually run bb-wl18xx-bluetooth before using bluetooth (hcitool,
> gatttool,
> > etc.) after each boot. I admit to being a noob on systemd still so maybe
> I
> > am missing something.
>
> We need to find the sweet spot for bb-wl18xx-bluetooth, it's run early
> with a delay, but still too early..
>

Oh, this is related to the infamous ST transport driver issue? No problem -
I'll just throw it in rc.local or such for now.

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/CAL8ugEc-zJw38kuA4CDVqhuDuYF88Ra33Lgow3xErO_E1paGMA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] BBGW console packages?

[Mark Grosen]

On to Bluetooth - I see there is a bb-wl18xx-bluetooth.service in the
bb-wl18xx-firmware package:
https://github.com/rcn-ee/repos/blob/master/bb-wl18xx-firmware/suite/jessie/debian/bb-wl18xx-bluetooth.service
and systemctl shows it enabled, but it does not seem to have run. I have to
manually run bb-wl18xx-bluetooth before using bluetooth (hcitool, gatttool,
etc.) after each boot. I admit to being a noob on systemd still so maybe I
am missing something.

Thanks,
Mark

On Thu, Jun 30, 2016 at 4:56 PM Robert Nelson <robertcnel...@gmail.com>
wrote:

> On Thu, Jun 30, 2016 at 6:04 PM, Mark Grosen <m...@grosen.org> wrote:
> > Ok, I cloned that and copied into /lib/firmware and now the WiFi works
> (have
> > not tried BT). So, after you fix the firmware package, I think the list
> of
> > packages needed is:
> > * wireless-tools
> > * iw
> > * wpasupplicant
> > * bb-wl18xx-firmware
> > * firmware-ti-connectivity
> > I am not using connman, etc.
>
> and "ti-wlconf", i need to add a hard dependicy to bb-wl18xx-firmware for
> that.
>
> As it's used to program, /lib/firmware/ti-connectivity/wl1271-nvs.bin
> with your wlan0 mac address
>
>
> https://github.com/rcn-ee/repos/blob/master/bb-wl18xx-firmware/suite/jessie/debian/bb-wl18xx-wlan0
>
>
> > I also changed uEnv.txt to use dtb=am335x-bonegreen-wireless.dtb - is
> this
> > required?
>
> That shouldn't be required, u-boot is patched to pick the correct dtb..
>
> 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/CAOCHtYh%3DV%2BA44gOv54KmqGiZskSC-K0qMhic2i7RuaKzzcUKDA%40mail.gmail.com
> .
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [beagleboard] BBGW console packages?

[Mark Grosen]

Ok, I cloned that and copied into /lib/firmware and now the WiFi works
(have not tried BT). So, after you fix the firmware package, I think the
list of packages needed is:
* wireless-tools
* iw
* wpasupplicant
* bb-wl18xx-firmware
* firmware-ti-connectivity
I am not using connman, etc.

I also changed uEnv.txt to use dtb=am335x-bonegreen-wireless.dtb - is this
required?

Mark


On Thu, Jun 30, 2016 at 2:58 PM Robert Nelson <robertcnel...@gmail.com>
wrote:

> On Thu, Jun 30, 2016 at 4:54 PM, Mark Grosen <m...@grosen.org> wrote:
> > Thanks, Robert. That got me the conf.bin file so that error is gone, but
> it
> > is still looking for wl18xx-fw-4.bin which does not exist. It seems like
> I
> > do need firmware-ti-connectivity otherwise there are no .bin files in
> > /lib/firmware/ti-connecivity. Is there a different firmware package?
>
> Yeah, that comes from the mainline tree, i need to update the
> firmware-ti-connectivty package..
>
>
> https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/tree/ti-connectivity
>
> 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/CAOCHtYgh%3D3unJ3jcNWV4UDw6q3SpiPdCnkZXjM2LvJKZQiJTyA%40mail.gmail.com
> .
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [beagleboard] BBGW console packages?

[Mark Grosen]

Thanks, Robert. That got me the conf.bin file so that error is gone, but it
is still looking for wl18xx-fw-4.bin which does not exist. It seems like I
do need firmware-ti-connectivity otherwise there are no .bin files in
/lib/firmware/ti-connecivity. Is there a different firmware package?

Mark

On Thu, Jun 30, 2016 at 2:32 PM Robert Nelson <robertcnel...@gmail.com>
wrote:

> Hi Mark,
>
> On Thu, Jun 30, 2016 at 4:26 PM, Mark Grosen <m...@grosen.org> wrote:
> > I got a new BB Green Wireless. I prefer the smaller console Debian image,
> > but it appears to not ship WL8 support. What packages do I need to add to
> > get the WL8 WiFi to work? WL8 Bluetooth? I tried adding the following:
> > * wireless-tools
> > * firmware-ti-connectivity
> > * ti-wlconf
> > While booting, the firmware for WL8 cannot be found:
> > [   12.330260] wl18xx_driver wl18xx.2.auto: Direct firmware load for
> > ti-connectivity/wl18xx-conf.bin failed with error -2
> > [   20.786201] wl18xx_driver wl18xx.2.auto: Direct firmware load for
> > ti-connectivity/wl18xx-fw-4.bin failed with error -2
> > There are various wl128x-fw-5*.bin files in
> /lib/firmware/ti-connectivity. I
> > thought the defaults should work without the wl18xx-conf.bin file.
> >
> > debian@beaglebone:/lib/firmware/ti-connectivity$ uname -a
> > Linux beaglebone 4.4.12-ti-r31 #1 SMP Thu Jun 16 18:48:27 UTC 2016 armv7l
> > GNU/Linux
> > debian@beaglebone:/lib/firmware/ti-connectivity$ cat /etc/dogtag
> > BeagleBoard.org Debian Image 2016-06-19
>
> bb-wl18xx-firmware
>
> details:
>
> firmware for both the wifi/bluetooth:
>
>
> https://github.com/rcn-ee/repos/tree/master/bb-wl18xx-firmware/suite/jessie/debian
>
> 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/CAOCHtYihAWVKkxY8i25ft1Yy548xA4FebSZVHk2kENTC7yHwxQ%40mail.gmail.com
> .
> For more options, visit https://groups.google.com/d/optout.
>

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

[beagleboard] BBGW console packages?

[Mark Grosen]

I got a new BB Green Wireless. I prefer the smaller console Debian image,
but it appears to not ship WL8 support. What packages do I need to add to
get the WL8 WiFi to work? WL8 Bluetooth? I tried adding the following:
* wireless-tools
* firmware-ti-connectivity
* ti-wlconf
While booting, the firmware for WL8 cannot be found:
[   12.330260] wl18xx_driver wl18xx.2.auto: Direct firmware load for
ti-connectivity/wl18xx-conf.bin failed with error -2
[   20.786201] wl18xx_driver wl18xx.2.auto: Direct firmware load for
ti-connectivity/wl18xx-fw-4.bin failed with error -2
There are various wl128x-fw-5*.bin files in /lib/firmware/ti-connectivity.
I thought the defaults should work without the wl18xx-conf.bin file.

debian@beaglebone:/lib/firmware/ti-connectivity$ uname -a
Linux beaglebone 4.4.12-ti-r31 #1 SMP Thu Jun 16 18:48:27 UTC 2016 armv7l
GNU/Linux
debian@beaglebone:/lib/firmware/ti-connectivity$ cat /etc/dogtag
BeagleBoard.org Debian Image 2016-06-19


Thanks,
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/CAL8ugEdonaG3TO%3DEZCHbyK60D4X0S1svBGDcCOJEaqtz4OCwag%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Connman and WiFi setup

[Mark Grosen]

I am new to connman, so this might be a basic question. I am trying to
setup the WL8 WiFi cape with a BBB. I am using recent console image and
kernel:

hk@wbct1:~$ uname -a
Linux wbct1 4.1.12-ti-r29 #1 SMP PREEMPT Mon Nov 9 22:46:19 UTC 2015 armv7l
GNU/Linux
hk@wbct1:~$ cat /etc/dogtag
rcn-ee.net console Debian Image 2015-11-13

With the right device tree loaded, the cape works after configuring
connman. The problem is that WiFi does not connect after a reboot. I have
to manually run "connmanctl connect wifi_blah". After that, things work
normally. I can use ifconfig up/down to change state without using
connmanctl. It's only after a (re)boot that it does not autoconnect. I have
autoconnect turned on for the AP I am using the settings file contents
below:

[wifi_blahmacaddr_6d67_managed_none]
Name=mg
SSID=6d67
Frequency=2452
Favorite=true
AutoConnect=true
Modified=2016-01-06T19:57:30.299409Z
IPv4.method=dhcp
IPv4.DHCP.LastAddress=192.168.1.104
IPv6.method=auto
IPv6.privacy=disabled
Config.file=wifi
Config.ident=service_home

Ethernet is attached and it does connect on (re)boot.

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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Anyone else interested in obtaining a mikroBUS Cape ?

[Mark Grosen]

Craig,

No problem. If you decide not to get the boards, that's fine. It was more
of a curiosity for me and just thought I would go along for the ride if you
did it. I'd be curious about your board ... :)

Mark



Mark


On Fri, Jun 6, 2014 at 2:57 PM, motortest_guy pondhockey...@gmail.com
wrote:

 Mark,
 I apologize, but I haven't ordered the boards yet.
 It's been a busy week and I was making a list of a few additional items I
 wanted, and then I started thinking about making my own version of the
 TIGAL microbus cape using KICAD since it would hone up my circuit layout
 skills and cost about the same (I have lots of ideas for capes, but need to
 put them down on circuit card).
 (There is a KICAD layout of the sensorcape that I could adapt)
So, I will do a bunch thinking this weekend and let you know.
 Craig

  --
 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.
 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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Anyone else interested in obtaining a mikroBUS Cape ?

[Mark Grosen]

Ok, I can go for 2 at this price. I can do PayPal or check or  to pay
you. I'll need to cover US shipping, too. Slow boat is fine - no rush.

Mark



Mark


On Thu, May 29, 2014 at 9:53 AM, motortest_guy pondhockey...@gmail.comwrote:

 I priced out two for me and two for you.
 Since we aren't Europe, we don't have to pay VAT, but the shipping
 (carriage)
 is pricey @ € 31,00.

 The shipping price seems fixed for 1 or more boards up to some limit I'm
 sure.
 I may also want to get a couple of 'Click' boards if the shipping doesn't
 go up.

 When I put in for a quantity of 10 boards the shipping went up to € 39,00
 for a total of  €  149,00


 Products
   # Product Unit price Quantity Net amount 1 *BeagleBone mikroBUS 
 Cape*https://www.tigal.com/product/3651
 mikroBUS Cape for BeagleBone
 € 11,00 4 € 44,00 Subtotal € 44,00 Carriage net € 31,00 Net amount € 75,00 VAT
 (20%) 0 *Total amount* *€ 75,00*


   Shopping cart  4 *BeagleBone mikroBUS 
 Cape*https://www.tigal.com/product/3651 Total
 amount: € 44,00


 On Wednesday, May 28, 2014 1:17:20 PM UTC-6, Mark Grosen wrote:

 How much is the shipping? I see the base price is ~$18 including VAT. I
 would take 2 at this price plus a reasonable shared shipping cost.

 Mark



 Mark


 On Tue, May 27, 2014 at 3:13 PM, motortest_guy pondho...@gmail.comwrote:


 https://www.tigal.com/wiki/doku.php?id=tigalcapes:bb_mikrobus_cape

 I want to get one, but the freight cost to get it across the ocean is
 double the cost of the board.
 If I order one, I might get a few more to sell to folks interested in
 the States.

 Mouser (In States) carries many if the Click boards, but doesn't carry
 the adapter cape (above).

 http://www.mouser.com/new/mikroelektronika/mikroelektronikaClick/

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

 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.
 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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Anyone else interested in obtaining a mikroBUS Cape ?

[Mark Grosen]

How much is the shipping? I see the base price is ~$18 including VAT. I
would take 2 at this price plus a reasonable shared shipping cost.

Mark



Mark


On Tue, May 27, 2014 at 3:13 PM, motortest_guy pondhockey...@gmail.comwrote:


 https://www.tigal.com/wiki/doku.php?id=tigalcapes:bb_mikrobus_cape

 I want to get one, but the freight cost to get it across the ocean is
 double the cost of the board.
 If I order one, I might get a few more to sell to folks interested in the
 States.

 Mouser (In States) carries many if the Click boards, but doesn't carry the
 adapter cape (above).

 http://www.mouser.com/new/mikroelektronika/mikroelektronikaClick/

 --
 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.
 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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Pin Mux values in DTS files

[Mark Grosen]

The TI pinmux tool is nice for this sort of thing (unfortunately only for
Windows .exe):
http://www.ti.com/tool/pinmuxtool

Mark



Mark


On Wed, May 28, 2014 at 3:25 PM, michael.du...@gmail.com wrote:

 The AM335x Technical Reference Manual is the source of all goodness, but
 the P8 and P9 PDFs here are quite useful:
 https://github.com/derekmolloy/boneDeviceTree/tree/master/docs

 You may also want to read his (Derek Molloy's) blog, e.g.

 http://derekmolloy.ie/gpios-on-the-beaglebone-black-using-device-tree-overlays/

 --
 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.
 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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: PRU FAQ 2013-05-15

[Mark Grosen]

After installing CCS with the PRU compiler, you can simply just use the
compiler as a command-line compiler (like all the other TI compilers) and
ignore the CCS IDE. The installer is only about 20MB download to start with
and then it downloads the rest as needed. It's a quick install on Linux
(YMMV on Windows).

http://processors.wiki.ti.com/index.php/Download_CCS

Mark



Mark


On Wed, May 7, 2014 at 9:51 AM, William Hermans yyrk...@gmail.com wrote:

 For me personally, it is not just preferable, it is a  requirement.  As I
 refuse to use CCS.


 On Wed, May 7, 2014 at 8:37 AM, brian larochelle 
 larochelle.br...@gmail.com wrote:


 On Wednesday, May 7, 2014 10:44:19 AM UTC-4, Jason Kridner wrote:

 It is a slightly updated version from the one I've been providing in
 beta. I've been waiting for a response to my request for a direct
 download, rather than needing to download all of CCS, before I posted
 something. Seems the cat is out of the bag!

 Very cool, thanks Jason.  Hopefully you get a response to the direct
 download request, that would be preferable over all of CCS.

  --
 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.
 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.
 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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: PRU FAQ 2013-05-15

[Mark Grosen]

Well, install it, copy the PRU directory somewhere else and rm -rf the CCS
directory - no more JRE. There is no dependency on the CCS IDE from the
compilers.

Mark



Mark


On Wed, May 7, 2014 at 1:04 PM, William Hermans yyrk...@gmail.com wrote:

 Mark, it is not CCS specifically that I have a problem with. I have a very
 strong aversion to having JRE on any of my Windows machines. So, if the
 tool is not made available as a separate native windows ( or perhaps *NIX )
 binary, I probably wont even give it a second look.



 On Wed, May 7, 2014 at 11:09 AM, Mark Grosen m...@grosen.org wrote:

 After installing CCS with the PRU compiler, you can simply just use the
 compiler as a command-line compiler (like all the other TI compilers) and
 ignore the CCS IDE. The installer is only about 20MB download to start with
 and then it downloads the rest as needed. It's a quick install on Linux
 (YMMV on Windows).

 http://processors.wiki.ti.com/index.php/Download_CCS

 Mark



 Mark


 On Wed, May 7, 2014 at 9:51 AM, William Hermans yyrk...@gmail.comwrote:

 For me personally, it is not just preferable, it is a  requirement.  As
 I refuse to use CCS.


 On Wed, May 7, 2014 at 8:37 AM, brian larochelle 
 larochelle.br...@gmail.com wrote:


 On Wednesday, May 7, 2014 10:44:19 AM UTC-4, Jason Kridner wrote:

 It is a slightly updated version from the one I've been providing in
 beta. I've been waiting for a response to my request for a direct
 download, rather than needing to download all of CCS, before I posted
 something. Seems the cat is out of the bag!

 Very cool, thanks Jason.  Hopefully you get a response to the direct
 download request, that would be preferable over all of CCS.

  --
 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.
 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.
 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.
 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.
 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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] how to add a simple kernel module with customized kernel

[Mark Grosen]

What kind of kernel did you build? My stock kernel is Thumb2 so modinfo
shows:

vermagic:   3.8.13-bone41 SMP mod_unload modversions ARMv7 thumb2 p2v8

If your kernel is Thumb2, then your module needs to be Thumb2, also.

mark@p3d:/lib/modules/3.8.13-bone41/kernel/drivers% zcat /proc/config.gz |
grep -i thumb
CONFIG_ARM_THUMB=y
CONFIG_ARM_THUMBEE=y
CONFIG_THUMB2_KERNEL=y
CONFIG_THUMB2_AVOID_R_ARM_THM_JUMP11=y
CONFIG_XZ_DEC_ARMTHUMB=y

Mark



Mark


On Sun, Mar 23, 2014 at 10:05 PM, siva kumar boopathisivaku...@gmail.comwrote:


 hai all,

   i followed this link to compile a kernel  for bbb

 http://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-BasicRequirements
 i try to mount my kernel using sd card, after a series of bugs finally i
 can able to boot my kernel using the precompiled ubuntu rootfs which was
 given in the above link.
 but when i tried to add a hello world module into my bbb . i got the
 following error
 i googled it all the possible ways but none of them helped me .

 *ubuntu@arm:/opt$ sudo insmod hello.ko *
 *Error: could not insert module hello.ko: Invalid module format*
 *ubuntu@arm:/opt$ *

 when i execute  modinfo command from the bbb. i got the following log
 information

 ubuntu@arm:/opt$ modinfo hello.ko
 filename:   /opt/hello.ko
 description:A Simple Hello World module
 author:  sivakumar
 license:GPL
 srcversion: F545620F75762B1AAE668ED
 depends:
 vermagic:   3.8.13 SMP mod_unload modversions ARMv7 p2v8

 help me how to insert the module into my beagelobne black kernel.

 regards
 siva




  --
 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.
 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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Ethernet interface failure

[Mark Grosen]

Which kernel are you using? I've been running a BBB on Ethernet 24x7 using
the Debian distro plus the 3.13 kernel with no networking issues for
several weeks.

Mark


Mark


On Fri, Mar 14, 2014 at 9:12 AM, atomik...@gmail.com wrote:

 This is not an isolated instance. We have SEVERAL Beagles 10+ all bought
 at different times, and all showing the same issue. This is not one
 specific Beagle that needs to be RMA'd


 On Friday, March 14, 2014 11:33:48 AM UTC-4, Gerald wrote:

 So if the board never works again, have you sent it in for repair via an
 RMA?

 Gerald



 On Fri, Mar 14, 2014 at 10:28 AM, atom...@gmail.com wrote:

 The BeagleBone Black ethernet interface will fail after a few hours of
 operation. As an example, we did a fresh install of both Debian and Ubuntu
 on two Beagles (Newest updates for the Arm OS), connected them to the
 network and sure enough the next morning, both of the interfaces had
 failed. Several people have apparently noticed this issue, but I can't find
 any suggestions on possible fixes. It appears to potentially be a hardware
 or Kernel issue. Has anyone out there had any experience with this and
 discovered a fix?

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

 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.
 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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] debian: test images (2014-01-29) (resend with correct topic..)

[Mark Grosen]

On Wed, Jan 29, 2014 at 1:25 PM, Robert Nelson robertcnel...@gmail.comwrote:

 Lets keep this going, round 4...

 First, for tracking please report all bugs to:
 http://bugs.elinux.org/projects/debian-image-releases

 Fixes:
 3.8.13-bone37 - 3.8.13-bone39
 * rs485 support from Micka
 * dir-changeable propery for gpio-of-helper from Charles
 * cape-bone-proto from me *(new default pinmux)

 New Packages:
 python-pip, python-setuptools, python2.7-dev


Thanks, it's working fine on my BBB using the setup_sdcard.sh approach. I'm
also using the latest 3.13 kernel:

Linux markbbb 3.13.0-bone5 #1 SMP Sat Jan 25 01:06:55 UTC 2014 armv7l
GNU/Linux

The only issue I noticed was several 404 errors from the bone101 website.

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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [beagleboard] debian: test images (2014-01-22)

[Mark Grosen]

On Fri, Jan 24, 2014 at 7:33 AM, Robert Nelson robertcnel...@gmail.comwrote:

  I made a new SD card using setup_card.sh and it boots fine.
 
  Verified new groups in both default debian and new user accounts. Ran
 Python
  script to drive i2c LED matrix as non-root user.

 Sweet! That's what we wanted..


Forgot to mention that the PATH additions were correct, too. Thanks.



  There are no /dev/spidev entries with this release:

 yeah you need to load the spidev cape..  I'm pretty sure the below
 will take care of the user permissions (spi group) for any /dev/spidev


I upgraded to 3.13 kernel and things are good there, too. I do get 2
spidev
devices with group spi and 660 permissions with this kernel and dtbs.

Mark



 debian@beaglebone:~$ cat /etc/udev/rules.d/50-spi.rules
 KERNEL==spidev*, GROUP=spi, MODE=0660

 
  mark@markbbb:~% uname -a
  Linux markbbb 3.8.13-bone37 #1 SMP Thu Jan 23 00:56:41 UTC 2014 armv7l
  GNU/Linux
  mark@markbbb:~% cat /proc/cmdline
  console=ttyO0,115200n8 root=/dev/mmcblk0p2 ro rootfstype=ext4 rootwait
  fixrtc ip= quiet init=/lib/systemd/systemd
  mark@markbbb:~% cat /etc/dogtag
  BeagleBoard.org BeagleBone Debian Image 2014-01-22
 

 Thanks!

 Regards,

 --
 Robert Nelson
 http://www.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.
 For more options, visit https://groups.google.com/groups/opt_out.


-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [beagleboard] Re: debian: test images (2014-01-16)

[Mark Grosen]

On Mon, Jan 20, 2014 at 12:43 PM, Robert Nelson robertcnel...@gmail.comwrote:

 On Sun, Jan 19, 2014 at 12:01 AM, Mark Grosen m...@grosen.org wrote:
  * Add /sbin and /usr/sbin to the default PATH

 Are you thinking system-wide or just the first user?

 As i'm looking at /etc/profile

 if [ `id -u` -eq 0 ]; then
   PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
 else
   PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
 fi
 export PATH

 Thinking of using sed to change...

 from:
 PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
 to:

 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/usr/games


I would make it system-wide. Given this is for embedded systems, I think
any user is going to want access to the if* and iw* commands as well as
i2c utilities (IMHO)


  * Enable the EXTRA_GROUPS options in /etc/adduser.conf and add i2c to the
  EXTRA_GROUPS

 Sounds good, added:

 https://github.com/beagleboard/image-builder/commit/47a74f654dddcf21e5327c76216b6a8bb6dfbcec


Thanks!

On a related note, it would be convenient if the spidev devices were in the
same
or similar group.


  * Add a way to identify the build version (or tell me how). I see
  /etc/os-release but it does not have a RCN build identifier in it

 I can't really touch /etc/os-release, as any stable update might blow
 that away...

 But i set it up similar to Angstrom:

 debian@beaglebone:~$ cat /etc/dogtag
 BeagleBoard.org BeagleBone Debian Image 2014-01-16


Ooops, missed that one in my grep'ing around - just what I was looking for.
Thanks.

Mark



 Regards,

 --
 Robert Nelson
 http://www.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.
 For more options, visit https://groups.google.com/groups/opt_out.


-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [beagleboard] Re: debian: test images (2014-01-16)

[Mark Grosen]

Robert,

I tried this new build on a BBB with good success. I used the
setup_sdcard.sh approach on an 8GB SD card. WiFi works with a cheapo
Rosewill USB dongle:

[   15.015308] rtl8192cu: Loading firmware rtlwifi/rtl8192cufw.bin
[   15.015468] usbcore: registered new interface driver rtl8192cu

I am using the 3.13 kernel:

Linux markbbb 3.13.0-rc8-bone4 #1 SMP Tue Jan 14 16:22:05 UTC 2014 armv7l
GNU/Linux

I have an I2C 8x8 LED matrix scrolling continuously, so i2c is good.

Running headless so no report on HDMI.

A couple small requests/suggestions:

* Add /sbin and /usr/sbin to the default PATH
* Enable the EXTRA_GROUPS options in /etc/adduser.conf and add i2c to the
EXTRA_GROUPS
* Add a way to identify the build version (or tell me how). I see
/etc/os-release but it does not have a RCN build identifier in it

Thanks much for your work on this.

Mark


On Thu, Jan 16, 2014 at 1:43 PM, Robert Nelson robertcnel...@gmail.comwrote:

 On Thu, Jan 16, 2014 at 3:42 PM, Robert Nelson robertcnel...@gmail.com
 wrote:
  Thanks for everyone who tested 2014-01-10... So here we go, round two...
 
  First, for tracking please report all bugs to:
  http://bugs.elinux.org/projects/debian-image-releases
 
  Fixes:
  3.8.13-bone35 - 3.8.13-bone36
  * uvc camera backport
 
 https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=8ca5d2d8e58df7235b77ed435e63c484e123fede
  * config sync with last Angstrom, missing a few modules, thumb2 enabled..
 
  lxde: autostart of screensaver disabled (pegged cpu to 100%)
  /opt/scripts/ now a git repo, easier to pull in board tweaks for
  bootup scripts..
  * including a kernel update script under
 /opt/scripts/tools/update_kernel.sh
  Chromium updated to 32.0.1700.76 with webrtc enabled.
  4gb image, dropped from 3750Mb to 3700Mb, should work with more 4GB
 cards.
  /var/lib/cloud9/node_modules/bonescript/ nodejs dependicy now installed
 
  Know Issues:
  wicd: can only handle eth0 or wlan0, not both at the same time..
 
  Questions? Should we switch to connman?
 
  To test:
  apt-get remove wicd-* --purge
  apt-get install connman
  (no good gui with connman)
 
  Does your cape work?
 
  Does your wifi adapter work? Are we missing it's firmware?
 
  So go forward and test the first beta release. There are 3 files on
  the web server, depending on what you want to do. Using the same
  standard procedure found here:
  http://elinux.org/Beagleboard:Updating_The_Software
 
  http://rcn-ee.net/deb/testing/2014-01-16/
 
  7cda65ef9971d8d770a84c00b8863c1e
  BBB-eMMC-flasher-debian-7.3-2014-01-16-2gb.img.xz
  c84011db191151986d14fe73e43f5f4d  bone-debian-7.3-2014-01-16-4gb.img.xz
  05ed49c8fe4555081f83f5be61b2b75b  debian-7.3-lxde-armhf-2014-01-16.tar.xz
 
  An eMMC flasher which can be installed to any 2GB or greater microSD
  card. [BBB-eMMC-flasher-debian-7.3-2014-01-16-2gb.img.xz]
 
 
 http://rcn-ee.net/deb/testing/2014-01-16/BBB-eMMC-flasher-debian-7.3-2014-01-16-2gb.img.xz
 
  It takes about 10-15 Minutes to dd microSD (2GB), 15 minutes to flash
  eMMC (look for full 4 LED's)
 
  4GB standalone image that can be flashed to any 4GB or greater.
  [bone-debian-7.3-2014-01-16-4gb.img.xz]
 
 
 http://rcn-ee.net/deb/testing/2014-01-16/bone-debian-7.3-2014-01-16-4gb.img.xz
 
  It takes about 20-30 Minutes to dd microSD (4GB)
 
  Finally one of my classic setup_sdcard.sh.
  [debian-7.3-console-armhf-2014-01-16.tar.xz]
 
 
 http://rcn-ee.net/deb/testing/2014-01-16/debian-7.3-console-armhf-2014-01-16.tar.xz

 Doh! cough


 http://rcn-ee.net/deb/testing/2014-01-16/debian-7.3-lxde-armhf-2014-01-16.tar.xz

 I'll get this form letter correct one of these weeks...

 Regards,

 --
 Robert Nelson
 http://www.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.
 For more options, visit https://groups.google.com/groups/opt_out.


-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.