date:20150902

Re: [beagleboard] Proper way to Mux PRU pin without Cape Manager

2015-09-02 Thread jalodi . hum

Hi Charles - this will be sweet when I get past the error.

My kernel it is from RCN.
Using Kernel 3.14.51-r1 which I built from:
https://github.com/RobertCNelson/ti-linux-kernel/tree/linux-3.14.y

When I run "config-pin P9.25 pruin" I get this error:

P9_25 pinmux file not found!
Please verify your device tree file

Regards,
-J

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

[beagleboard] Re: Serial Debug output to ethernet

2015-09-02 Thread Graham

As long as your Remote PC is on the same Local Area Network...
Put "Putty" on your remote PC.
Sign onto your BBB using SSH.
--- Graham

==

On Wednesday, September 2, 2015 at 7:06:15 PM UTC-5, josiasina...@gmail.com 
wrote:
>
> Is there any way to send the Serial Debug output to a remote PC using 
> ethernet connection?
>
> So far I've been using Serial to USB so I can debug what's happening 
> during booting. But having a way to connect to the board remotely would be 
> really helpful.
>
> Anyone already did this?
>

-- 
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] Proper way to Mux PRU pin without Cape Manager

2015-09-02 Thread Charles Steinkuehler


On 9/2/2015 3:20 PM, jalodi@gmail.com wrote:


I am working with the PRU on the 3.14 series kernel.
There is no cape manager, and I want to employ the proper technique for
muxing a PRU pin.

For example, the file "am335x-bone-common-pinmux.dtsi" contains this
definition which
is the pin&mode that I want to activate:

P9_25_pruin_pin: pinmux_P9_25_pruin_pin {
   pinctrl-single,pins = <0x1ac  0x26>; }; /* Mode 6, Pull-Down,
RxActive */

How exactly would I make use of this?


If you're using RCN's kernels, the universal overlay should already be 
part of the default device tree, so you can just use the config-pin utility:


  config-pin P9.25 pruin

--
Charles Steinkuehler

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

[beagleboard] Serial Debug output to ethernet

2015-09-02 Thread josiasinaciocanada

Is there any way to send the Serial Debug output to a remote PC using 
ethernet connection?

So far I've been using Serial to USB so I can debug what's happening during 
booting. But having a way to connect to the board remotely would be really 
helpful.

Anyone already did this?

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

[beagleboard] Setup a new wireless client from your beaglebone by running a hot spot on it

2015-09-02 Thread nivwiz

cwvw 
I wrote this for my beaglebone black, but it should also run fine on other 
boards, as long as you use jessie.
Idea is simple: boot your beaglebone with a hot spot, then you connect to 
it using your phone, and get a web page from it.
in this page you define your wireless name and password and then the 
beaglebone will connect to that wireless network.
In case you want to change this, simply connect to the host spot again.

Easy deb install from deb file 

Any feedback is welcome,
Niv

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

[beagleboard] Proper way to Mux PRU pin without Cape Manager

2015-09-02 Thread jalodi . hum


I am working with the PRU on the 3.14 series kernel.
There is no cape manager, and I want to employ the proper technique for 
muxing a PRU pin.

For example, the file "am335x-bone-common-pinmux.dtsi" contains this 
definition which
is the pin&mode that I want to activate:

P9_25_pruin_pin: pinmux_P9_25_pruin_pin {
  pinctrl-single,pins = <0x1ac  0x26>; }; /* Mode 6, Pull-Down, 
RxActive */

How exactly would I make use of this?

( Guessing that I need to reference this in am335x-boneblack.dts somehow, 
 just not
experienced enough with DT to know how to do it. )

Regards,
-J

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

[beagleboard] Re: i2c-bus - A new Node.js I2C module

2015-09-02 Thread Brian Cooke

This is an odd place for a question about the Raspberry Pi :)

A guess would be that i2c-bus, which is a native addon, was installed with 
one version of Node.js but is being run with another version of Node.js. 
Reinstall i2c-bus and try again.

-- 
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] BBB OpenSuse 13.2 no video output

2015-09-02 Thread matthieu claire

I tried with *am335x-boneblack-overlay.dtb* it gives the same result as
*am335x-boneblack-emmc-overlay.dtb *

I realised those files are created when we compile the kernel 4.1.6 can it
be the root cause?



Matthieu CLAIRE
ZEPHYR AUDIO
*Ingénieur R&D / Design & Software Engineer*
http://www.zephyr-audio.com
+33 623965133

2015-09-02 17:05 GMT+02:00 matthieu claire :

> My LCD is still OFF
>
> Now I'm sure I'm loading the am335x-boneblack-emmc-overlay.dtb before
> starting the kernel (see serial log below)
>
> *UBOOT SERIAL LOG *
> ## Executing script at 8200
> this is a test
> fdtfile=dtb/am335x-boneblack-emmc-overlay.dtb
> Done
> switch to partitions #0, OK
> mmc0 is current device
> 8261808 bytes read in 541 ms (14.6 MiB/s)
> 6101876 bytes read in 399 ms (14.6 MiB/s)
> 55700 bytes read in 61 ms (891.6 KiB/s)
> Kernel image @ 0x8200 [ 0x00 - 0x7e10b0 ]
> ## Flattened Device Tree blob at 8800
>Booting using the fdt blob at 0x8800
>Using Device Tree in place at 8800, end 88010993
>
> Starting kernel ...
>
> I cheked the file size
> linux:~ # ls -l /boot/dtb/ | fgrep 55700
> -rw-r--r-- 1 root root 55700 Aug 26 09:04
> am335x-boneblack-emmc-overlay.dtb
>
> The module is OK
> [   49.781865] bone_capemgr bone_capemgr: part_number 'BB-BONE-LCD7-01',
> version '00A3'
> [   49.781909] bone_capemgr bone_capemgr: slot #4: override
> [   49.781926] bone_capemgr bone_capemgr: Using override eeprom data at
> slot 4
> [   49.781944] bone_capemgr bone_capemgr: slot #4: 'Override Board
> Name,00A3,Override Manuf,BB-BONE-LCD7-01'
> [   49.952336] bone_capemgr bone_capemgr: slot #4: dtbo
> 'BB-BONE-LCD7-01-00A3.dtbo' loaded; overlay id #0
>
> The X server starts without issue see Xorg.0.log in previous email
>
> And lightdm is running
>
> *linux:~ # ps -ef | fgrep lightdm*
> *root   646 1  0 14:47 ?00:00:00 /usr/sbin/lightdm*
> *root   674   646  0 14:47 tty7 00:00:00 /usr/bin/X :0 -seat seat0
> -auth /run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch*
> *root   781   646  0 14:47 ?00:00:00 lightdm --session-child
> 16 19*
> *lightdm791 1  0 14:47 ?00:00:00 /usr/lib/systemd/systemd
> --user*
> *lightdm792   791  0 14:47 ?00:00:00 (sd-pam)*
> *lightdm793   781  0 14:47 ?00:00:02
> /usr/sbin/lightdm-gtk-greeter*
> *lightdm800 1  0 14:47 ?00:00:00 /bin/dbus-launch
> --autolaunch 2239aafda63c4be8976a02efb8f8119e --binary-syntax
> --close-stderr*
> *lightdm801 1  0 14:47 ?00:00:00 /bin/dbus-daemon --fork
> --print-pid 5 --print-address 7 --session*
> *lightdm803 1  0 14:47 ?00:00:00
> /usr/lib/at-spi2/at-spi-bus-launcher*
> *lightdm809   803  0 14:47 ?00:00:00 /bin/dbus-daemon
> --config-file=/etc/at-spi2/accessibility.conf --nofork --print-address 3*
> *lightdm816 1  0 14:47 ?00:00:00
> /usr/lib/at-spi2/at-spi2-registryd --use-gnome-session*
> *root  1082   646  0 14:47 ?00:00:00 lightdm --session-child
> 12 19*
> *root  1655  1549 66 14:57 pts/000:00:00 grep -F --color=auto
> lightdm*
>
>
>
>
> Matthieu CLAIRE
> ZEPHYR AUDIO
> *Ingénieur R&D / Design & Software Engineer*
> http://www.zephyr-audio.com
> +33 623965133
>
> 2015-09-02 11:16 GMT+02:00 matthieu claire :
>
>> Thank you William for the link, I will try this later.
>>
>> In between I found if I load the module in the /etc/init.d/boot.local the
>> module is loaded 2-3s before X server starts
>> So now X found the device /dev/fb0 (see Xorg.0.log below)
>>
>> But unfortunately I still have NOTHING on the display, it's really
>> frustrating.
>>
>> The login manager lightdm process is running so I should see it on the
>> screen.
>> After a while the LCD backlight turns OFF, when I touch the screen it
>> turns back ON so I guess it's working.
>>
>> I'm using the fdt file am335x-boneblack-emmc-overlay.dtb (but I didn't
>> find how to check this really happeing since this parameter are loaded
>> after the auto-boot)
>> I'm loading the module BB-BONE-LCD7-01-00A3.dtbo succesfully
>>
>> So I tried to compare the Xorg.0.log between the opensuse and the debian
>> which is running without issue on the eMMc with the LCD 7" 4D-CAPE-70T
>> (wile using the same xorg.conf)
>>
>> I found several differences:
>> *On debian *
>> II) FBDEV(0): hardware:  (video memory: 750kB)
>> *while on opensuse*
>> *II) FBDEV(0): hardware:  (video memory: 2250kB)*
>>
>> --> I tried to override this parameter with the parameter *VideoRam 750*
>> in the device section of my xorg.conf but It has no impact* the log is
>> still the same*
>>
>> *On debian I have several built-in extensions*
>> [13.488] (==) RandR enabled
>> [13.490] (II) Initializing built-in extension Generic Event Extension
>> [13.490] (II) Initializing built-in extension SHAPE
>> [13.491] (II) Initializing built-in extension MIT-SHM
>> [13.491] (II) Initializing built-in extension XInputExtension
>> [13.491] (II) Ini

[beagleboard] Re: linux-4.0 on Beagleboard Rev-C D-Link DWA-160 wifi not working

2015-09-02 Thread amf

noobe mistake

failed to set these in kernel config
CONFIG_WEXT_CORE=y
CONFIG_WEXT_PROC=y
CONFIG_CFG80211=y
CONFIG_CFG80211_WEXT=y
CONFIG_MAC80211=y

both DWA-160 and DWA-121 are working

hope this helps someone else,
amf


On Tuesday, September 1, 2015 at 3:07:00 PM UTC-5, amf wrote:

> Hi all,
>
> My first post here, did some searches but came up blank.
>
> I'm trying to get D-Link DWA-160 wifi working with linux-4.0 on the old 
> Beagleboard Rev-C
> Many version back (do not recall which) this device worked.
> I have listed all I can think of that may help, if I missed something 
> please let me know.
>
> Any help will be appreciated, 
> amf
>
> D-Link
> DWA-160
> HW Ver B1
> FW Ver 2.00
> Ralink
> driver: rt2870 
> rt2800lib.ko
> RT chipset 2860, rev 0103 detected
> 07d1:3c11
>
>
> /etc/wpa_supplicant
> ctrl_interface=/var/run/wpa_supplicant
> fast_reauth=1
> ap_scan=1
> eapol_version=1
> network={
> ssid="router ssid"
> psk="passwd"
> scan_ssid=0
> proto=WPA RSN
> key_mgmt=WPA-PSK WPA-EAP
> pairwise=CCMP TKIP
> group=CCMP TKIP
> auth_alg=SHARED OPEN
> }
>
> also tried with 
> key_mgmt=NONE
> and the router encryption turned off
>
>
> /etc/networks/interfaces
> auto lo
> iface lo inet loopback
> auto wlan0
> iface wlan0 inet dhcp
>
>
> *last part of kernel booting*
> Starting network...
> [3.566223] usb 2-2.3: new high-speed USB device number 3 using 
> ehci-omap
> ip: SIOCGIFFLAGS: No such device
> ip: SIOCGIFFLAGS: No such device
> [3.726135] usb 2-2.3: New USB device found, idVendor=07d1, 
> idProduct=3c11
> [3.733428] usb 2-2.3: New USB device strings: Mfr=1, Product=2, 
> SerialNumber=3
> [3.741302] usb 2-2.3: Product: 802.11 n WLAN
> [3.745941] usb 2-2.3: Manufacturer: Ralink
> [3.750366] usb 2-2.3: SerialNumber: 1.0
> ip: can't find device 'eth0'
> ip: SIOCGIFFLAGS: No such device
>
>
> *script ran after drivers are loaded*
> wpa_supplicant -B -iwlan0 -c/etc/wpa_supplicant.conf -Dwext &&
> dhcpcd wlan0 
>
>
> *output on terminal after running script*
>
> Successfully initialized wpa_supplicant
> [   89.307525] ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading 
> firmware file 'rt2870.bin'
> [   89.334045] ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware 
> detected - version: 0.29
> [   89.920074] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
> ioctl[SIOCSIWPMKSA]: Invalid argument
> ioctl[SIOCSIWMODE]: Invalid argument
> ioctl[SIOCGIWRANGE]: Invalid argument
> ioctl[SIOCGIWMODE]: Invalid argument
> ioctl[SIOCSIWAP]: Invalid argument
> ioctl[SIOCSIWESSID]: Invalid argument
> ioctl[SIOCSIWENCODEEXT]: Invalid argument
> ioctl[SIOCSIWENCODEEXT]: Invalid argument
> ioctl[SIOCSIWENCODEEXT]: Invalid argument
> ioctl[SIOCSIWENCODEEXT]: Invalid argument
> ioctl[SIOCSIWPMKSA]: Invalid argument
> wlan0: adding address fe80::af1:9d76:7833:e833
> wlan0: waiting for carrier
> timed out
> dhcpcd exited
>
>
> *# dmesg | tail*
> [   14.738891] usbcore: registered new interface driver rtl8192cu
> [   15.126220] usb 2-2.3: reset high-speed USB device number 3 using 
> ehci-omap
> [   15.258361] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 2860, rev 
> 0103 detected
> [   15.322326] ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 0002 
> detected
> [   15.377807] ieee80211 phy0: Selected rate control algorithm 
> 'minstrel_ht'
> [   15.384948] usbcore: registered new interface driver rt2800usb
> [   16.512756] ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading 
> firmware file 'rt2870.bin'
> [   16.532989] ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware 
> detected - version: 0.29
> [   17.119445] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
> [   26.714233] random: nonblocking pool is initialized
>
>
> *# dhcpcd --version*
> dhcpcd 6.8.1
>
> *# lsmod*
> Module  Size  Used byNot tainted
> arc41719  2
> rt2800usb  15034  0
> rt2x00usb  11492  1 rt2800usb
> rt2800lib  76924  1 rt2800usb
> rt2x00lib  45930  3 rt2800usb,rt2x00usb,rt2800lib
> rtl8192cu  98537  0
> rtl_usb14724  1 rtl8192cu
> rtl8192c_common70336  1 rtl8192cu
> rtlwifi   104207  3 rtl8192cu,rtl_usb,rtl8192c_common
> mac80211  513955  6 
> rt2x00usb,rt2800lib,rt2x00lib,rtl8192cu,rtl_usb,rtlwifi
> cfg80211  428348  3 rt2x00lib,rtlwifi,mac80211
>
>
>
>

-- 
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] BBB OpenSuse 13.2 no video output

2015-09-02 Thread matthieu claire

My LCD is still OFF

Now I'm sure I'm loading the am335x-boneblack-emmc-overlay.dtb before
starting the kernel (see serial log below)

*UBOOT SERIAL LOG *
## Executing script at 8200
this is a test
fdtfile=dtb/am335x-boneblack-emmc-overlay.dtb
Done
switch to partitions #0, OK
mmc0 is current device
8261808 bytes read in 541 ms (14.6 MiB/s)
6101876 bytes read in 399 ms (14.6 MiB/s)
55700 bytes read in 61 ms (891.6 KiB/s)
Kernel image @ 0x8200 [ 0x00 - 0x7e10b0 ]
## Flattened Device Tree blob at 8800
   Booting using the fdt blob at 0x8800
   Using Device Tree in place at 8800, end 88010993

Starting kernel ...

I cheked the file size
linux:~ # ls -l /boot/dtb/ | fgrep 55700
-rw-r--r-- 1 root root 55700 Aug 26 09:04 am335x-boneblack-emmc-overlay.dtb

The module is OK
[   49.781865] bone_capemgr bone_capemgr: part_number 'BB-BONE-LCD7-01',
version '00A3'
[   49.781909] bone_capemgr bone_capemgr: slot #4: override
[   49.781926] bone_capemgr bone_capemgr: Using override eeprom data at
slot 4
[   49.781944] bone_capemgr bone_capemgr: slot #4: 'Override Board
Name,00A3,Override Manuf,BB-BONE-LCD7-01'
[   49.952336] bone_capemgr bone_capemgr: slot #4: dtbo
'BB-BONE-LCD7-01-00A3.dtbo' loaded; overlay id #0

The X server starts without issue see Xorg.0.log in previous email

And lightdm is running

*linux:~ # ps -ef | fgrep lightdm*
*root   646 1  0 14:47 ?00:00:00 /usr/sbin/lightdm*
*root   674   646  0 14:47 tty7 00:00:00 /usr/bin/X :0 -seat seat0
-auth /run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch*
*root   781   646  0 14:47 ?00:00:00 lightdm --session-child 16
19*
*lightdm791 1  0 14:47 ?00:00:00 /usr/lib/systemd/systemd
--user*
*lightdm792   791  0 14:47 ?00:00:00 (sd-pam)*
*lightdm793   781  0 14:47 ?00:00:02
/usr/sbin/lightdm-gtk-greeter*
*lightdm800 1  0 14:47 ?00:00:00 /bin/dbus-launch
--autolaunch 2239aafda63c4be8976a02efb8f8119e --binary-syntax
--close-stderr*
*lightdm801 1  0 14:47 ?00:00:00 /bin/dbus-daemon --fork
--print-pid 5 --print-address 7 --session*
*lightdm803 1  0 14:47 ?00:00:00
/usr/lib/at-spi2/at-spi-bus-launcher*
*lightdm809   803  0 14:47 ?00:00:00 /bin/dbus-daemon
--config-file=/etc/at-spi2/accessibility.conf --nofork --print-address 3*
*lightdm816 1  0 14:47 ?00:00:00
/usr/lib/at-spi2/at-spi2-registryd --use-gnome-session*
*root  1082   646  0 14:47 ?00:00:00 lightdm --session-child 12
19*
*root  1655  1549 66 14:57 pts/000:00:00 grep -F --color=auto
lightdm*




Matthieu CLAIRE
ZEPHYR AUDIO
*Ingénieur R&D / Design & Software Engineer*
http://www.zephyr-audio.com
+33 623965133

2015-09-02 11:16 GMT+02:00 matthieu claire :

> Thank you William for the link, I will try this later.
>
> In between I found if I load the module in the /etc/init.d/boot.local the
> module is loaded 2-3s before X server starts
> So now X found the device /dev/fb0 (see Xorg.0.log below)
>
> But unfortunately I still have NOTHING on the display, it's really
> frustrating.
>
> The login manager lightdm process is running so I should see it on the
> screen.
> After a while the LCD backlight turns OFF, when I touch the screen it
> turns back ON so I guess it's working.
>
> I'm using the fdt file am335x-boneblack-emmc-overlay.dtb (but I didn't
> find how to check this really happeing since this parameter are loaded
> after the auto-boot)
> I'm loading the module BB-BONE-LCD7-01-00A3.dtbo succesfully
>
> So I tried to compare the Xorg.0.log between the opensuse and the debian
> which is running without issue on the eMMc with the LCD 7" 4D-CAPE-70T
> (wile using the same xorg.conf)
>
> I found several differences:
> *On debian *
> II) FBDEV(0): hardware:  (video memory: 750kB)
> *while on opensuse*
> *II) FBDEV(0): hardware:  (video memory: 2250kB)*
>
> --> I tried to override this parameter with the parameter *VideoRam 750*
> in the device section of my xorg.conf but It has no impact* the log is
> still the same*
>
> *On debian I have several built-in extensions*
> [13.488] (==) RandR enabled
> [13.490] (II) Initializing built-in extension Generic Event Extension
> [13.490] (II) Initializing built-in extension SHAPE
> [13.491] (II) Initializing built-in extension MIT-SHM
> [13.491] (II) Initializing built-in extension XInputExtension
> [13.491] (II) Initializing built-in extension XTEST
> [13.492] (II) Initializing built-in extension BIG-REQUESTS
> [13.492] (II) Initializing built-in extension SYNC
> [13.492] (II) Initializing built-in extension XKEYBOARD
> [13.492] (II) Initializing built-in extension XC-MISC
> [13.492] (II) Initializing built-in extension SECURITY
> [13.493] (II) Initializing built-in extension XINERAMA
> [13.494] (II) Initializing built-in extension XFIXES
> [13.494] (II) Initializing built-in extension RENDER
> [13.495] (II) Initializing buil

Re: [beagleboard] booting from sd card upon power up

2015-09-02 Thread Robert Nelson

On Wed, Sep 2, 2015 at 10:03 AM, Jerry Davis  wrote:
> I have found an ubuntu image (for SDR), that I want to boot up directly from
> an sd card.
> I have scoured the internet, and frankly, there is a lot of mis-information
> out there, re this.
>
> I don't want to have to push any buttons or anything like that, as the
> beagle bone black will be in an enclosure.
>
> So, is just the mere act of putting in an sd card, make it automatically
> boot from it? Or is there more that has to be done. Prefferably, I would
> like to keep what is on the flash memory intact, so if I don't have the sd
> card inserted, it will boot up normally from the flash.
>
> And just exactly what is the boot order, while I am at it?

Okay, let's start with what's on the eMMC:

cat /etc/dogtag

Next the "SDR" image what version/etc?

What do you currently see (over the usb-serial adapter) when you
currently try to boot the SDR image.

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

[beagleboard] booting from sd card upon power up

2015-09-02 Thread Jerry Davis

I have found an ubuntu image (for SDR), that I want to boot up directly
from an sd card.
I have scoured the internet, and frankly, there is a lot of mis-information
out there, re this.

I don't want to have to push any buttons or anything like that, as the
beagle bone black will be in an enclosure.

So, is just the mere act of putting in an sd card, make it automatically
boot from it? Or is there more that has to be done. Prefferably, I would
like to keep what is on the flash memory intact, so if I don't have the sd
card inserted, it will boot up normally from the flash.

And just exactly what is the boot order, while I am at it?

Thanks,
Jerry

--
Extra Ham Operator: K7AZJ
Registered Linux User: 275424
Raspberry Pi and Arduino developer


*The most exciting phrase to hear in science - the one that heralds new
discoveries - is not "Eureka!" but "That's funny...".*- Isaac. Asimov

*I*
*f you give someone a program, you will frustrate them for a day; if you
teach them how to program, you will frustrate them for a lifetime. *-
Anonymous


*If writing good code requires very little comments, then writing really
excellent code requires no comments at all!*- Ken Thompson

-- 
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] BBB OpenSuse 13.2 no video output

2015-09-02 Thread matthieu claire

Thank you William for the link, I will try this later.

In between I found if I load the module in the /etc/init.d/boot.local the
module is loaded 2-3s before X server starts
So now X found the device /dev/fb0 (see Xorg.0.log below)

But unfortunately I still have NOTHING on the display, it's really
frustrating.

The login manager lightdm process is running so I should see it on the
screen.
After a while the LCD backlight turns OFF, when I touch the screen it turns
back ON so I guess it's working.

I'm using the fdt file am335x-boneblack-emmc-overlay.dtb (but I didn't find
how to check this really happeing since this parameter are loaded after the
auto-boot)
I'm loading the module BB-BONE-LCD7-01-00A3.dtbo succesfully

So I tried to compare the Xorg.0.log between the opensuse and the debian
which is running without issue on the eMMc with the LCD 7" 4D-CAPE-70T
(wile using the same xorg.conf)

I found several differences:
*On debian *
II) FBDEV(0): hardware:  (video memory: 750kB)
*while on opensuse*
*II) FBDEV(0): hardware:  (video memory: 2250kB)*

--> I tried to override this parameter with the parameter *VideoRam 750* in
the device section of my xorg.conf but It has no impact* the log is still
the same*

*On debian I have several built-in extensions*
[13.488] (==) RandR enabled
[13.490] (II) Initializing built-in extension Generic Event Extension
[13.490] (II) Initializing built-in extension SHAPE
[13.491] (II) Initializing built-in extension MIT-SHM
[13.491] (II) Initializing built-in extension XInputExtension
[13.491] (II) Initializing built-in extension XTEST
[13.492] (II) Initializing built-in extension BIG-REQUESTS
[13.492] (II) Initializing built-in extension SYNC
[13.492] (II) Initializing built-in extension XKEYBOARD
[13.492] (II) Initializing built-in extension XC-MISC
[13.492] (II) Initializing built-in extension SECURITY
[13.493] (II) Initializing built-in extension XINERAMA
[13.494] (II) Initializing built-in extension XFIXES
[13.494] (II) Initializing built-in extension RENDER
[13.495] (II) Initializing built-in extension RANDR
[13.495] (II) Initializing built-in extension COMPOSITE
[13.495] (II) Initializing built-in extension DAMAGE
[13.497] (II) SELinux: Disabled on system
[13.751] (II) AIGLX: Screen 0 is not DRI2 capable
*while on opensuse I have none*
*[52.716] (==) RandR enabled*
*[52.862] (II) AIGLX: Screen 0 is not DRI2 capable*

*On Debian tps65217 is identified*
(II) Using input driver 'evdev' for 'tps65217_pwr_but'
[15.134] (**) tps65217_pwr_but: always reports core events
[15.134] (**) evdev: tps65217_pwr_but: Device: "/dev/input/event0"
[15.134] (--) evdev: tps65217_pwr_but: Vendor 0 Product 0
[15.134] (--) evdev: tps65217_pwr_but: Found keys
[15.134] (II) evdev: tps65217_pwr_but: Configuring as keyboard
[15.134] (**) Option "config_info"
"udev:/sys/devices/ocp.3/44e0b000.i2c/i2c-0/0-0024/input/input0/event0"
[15.141] (II) XINPUT: Adding extended input device "tps65217_pwr_but"
(type: KEYBOARD, id 6)
*while on opensuse I have gpio_keys*
* (II) Using input driver 'evdev' for 'gpio_keys'*
*[53.895] (**) gpio_keys: always reports core events*
*[53.895] (**) evdev: gpio_keys: Device: "/dev/input/event0"*
*[53.896] (--) evdev: gpio_keys: Vendor 0x1 Product 0x1*
*[53.896] (--) evdev: gpio_keys: Found keys*
*[53.896] (II) evdev: gpio_keys: Configuring as keyboard*
*[53.896] (**) Option "config_info"
"udev:/sys/devices/platform/gpio_keys/input/input0/event0"*
*[53.896] (II) XINPUT: Adding extended input device "gpio_keys" (type:
KEYBOARD, id 6)*


*linux:~ # cat /var/log/Xorg.0.log*
*[52.436]*
*X.Org X Server 1.16.1*
*Release Date: 2014-09-21*
*[52.436] X Protocol Version 11, Revision 0*
*[52.436] Build Operating System: openSUSE SUSE LINUX*
*[52.436] Current Operating System: Linux linux.site 4.1.6 #1 SMP
PREEMPT Sun Aug 23 16:43:56 UTC 2015 armv7l*
*[52.436] Kernel command line:
root=/dev/disk/by-id/mmc-SL16G_0x28cf527e-part2 loader=uboot
disk=/dev/disk/by-id/mmc-SL16G_0x28cf527e plymouth.enable=0 console=ttyO0*
*[52.437] Build Date: 12 June 2015  07:53:26PM*
*[52.437]*
*[52.437] Current version of pixman: 0.32.6*
*[52.437]Before reporting problems, check http://wiki.x.org
*
*to make sure that you have the latest version.*
*[52.437] Markers: (--) probed, (**) from config file, (==) default
setting,*
*(++) from command line, (!!) notice, (II) informational,*
*(WW) warning, (EE) error, (NI) not implemented, (??) unknown.*
*[52.447] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Sep  2
08:09:27 2015*
*[52.462] (==) Using config file: "/etc/X11/xorg.conf"*
*[52.462] (==) Using config directory: "/etc/X11/xorg.conf.d"*
*[52.462] (==) Using system config directory
"/usr/share/X11/xorg.conf.d"*
*[52.465] (==) ServerLayout "Builtin Default Layout"*

[beagleboard] Re: Using CUPS to print pdf in BBB-Angstrom

2015-09-02 Thread Ison Thomas

I tried to install cups-filter from source. The following error shows up : 
configure: error: Required cups-config is missing. Please install CUPS 
developer packages. How to install this in Angstrom BBB

On Wednesday, 2 September 2015 16:02:52 UTC+5:30, Ison Thomas wrote:
>
> Hi,
>
> I am new to using BBB and Angstrom. What I would like to do is print a pdf 
> file from command line.
>
> I have installed 'cups' package. With this I am able to add a printer 
> using 'lpadmin' command. But when I try to print a text file or pdf file, 
> it says "Unsupported format 'text/plain' or 'application/pdf'. I might be 
> missing some dependency package or something. Kindly help to sort out the 
> issue.
>
> I have tried installing 'ghostscript' but it didn't work.
>
> When trying to install 'libcupsys2-dev' and 'cups-filter' using opkg, it 
> says 'unknown package'. 
>
> Thanks
>
> Ison Thomas
>

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

[beagleboard] MMC3 for SDIO communiction

2015-09-02 Thread Dileep D R



*dmesg log shows:[4.259093] omap_hsmmc 4781.mmc: unable to get vmmc 
regulator -517*


I have used following configuration in dts, don't know where exactly i am 
going wrong.

wl12xx_vmmc: fixedregulator@3 {
pinctrl-names = "default";
pinctrl-0 = <&wl12xx_gpio>;
compatible = "regulator-fixed";
regulator-name = "wl12xx_vmmc";
regulator-min-microvolt = <180>;
regulator-max-microvolt = <180>;
gpio = <&gpio0 27 0>;
startup-delay-us = <7>;
enable-active-high;
};

wlan_pins: pinmux_wlan_pins {
pinctrl-single,pins = <
0x28 (PIN_INPUT_PULLUP | MUX_MODE7) /* gpio0_26 WL_IRQ */
>;
};

wl12xx_gpio: pinmux_wl12xx_gpio {
pinctrl-single,pins = <
0x2c (PIN_OUTPUT_PULLUP | MUX_MODE7) /* gpio0_27 WL_EN */
>;
};

/* ODIN-W160 SDIO pins */
mmc3_pins: pinmux_mmc3_pins {
pinctrl-single,pins = <
0x3C (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_dat3 */
0x38 (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_dat2 */
0x34 (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_dat1 */
0x30 (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_dat0 */
0x8c (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_clk */
0x88 (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_cmd */
>;
};

&mmc3 {
/* these are on the crossbar and are outlined in the
xbar-event-map element */
dmas = <&edma 32 &edma 33>;
dma-names = "tx", "rx";

status = "okay";
vmmc-supply = <&wl12xx_vmmc>;
ti,non-removable;
bus-width = <4>;
cap-power-off-card;
pinctrl-names = "default";
pinctrl-0 = <&mmc3_pins>;

#address-cells = <1>;
#size-cells = <0>;
wlcore: wlcore@0 {
compatible = "ti,wl1271";
reg = <2>;
interrupt-parent = <&gpio0>;
interrupts = <26 0x4>;
ref-clock-frequency = <3840>;
};
};

&edma {
ti,edma-xbar-event-map = /bits/ 16 <1 32 2 33>;
};


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

[beagleboard] Using CUPS to print pdf in BBB-Angstrom

2015-09-02 Thread Ison Thomas

Hi,

I am new to using BBB and Angstrom. What I would like to do is print a pdf 
file from command line.

I have installed 'cups' package. With this I am able to add a printer using 
'lpadmin' command. But when I try to print a text file or pdf file, it says 
"Unsupported format 'text/plain' or 'application/pdf'. I might be missing 
some dependency package or something. Kindly help to sort out the issue.

I have tried installing 'ghostscript' but it didn't work.

When trying to install 'libcupsys2-dev' and 'cups-filter' using opkg, it 
says 'unknown package'. 

Thanks

Ison Thomas

-- 
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] Proper way to Mux PRU pin without Cape Manager

[beagleboard] Re: Serial Debug output to ethernet

Re: [beagleboard] Proper way to Mux PRU pin without Cape Manager

[beagleboard] Serial Debug output to ethernet

[beagleboard] Setup a new wireless client from your beaglebone by running a hot spot on it

[beagleboard] Proper way to Mux PRU pin without Cape Manager

[beagleboard] Re: i2c-bus - A new Node.js I2C module

Re: [beagleboard] BBB OpenSuse 13.2 no video output

[beagleboard] Re: linux-4.0 on Beagleboard Rev-C D-Link DWA-160 wifi not working

Re: [beagleboard] BBB OpenSuse 13.2 no video output

Re: [beagleboard] booting from sd card upon power up

[beagleboard] booting from sd card upon power up

Re: [beagleboard] BBB OpenSuse 13.2 no video output

[beagleboard] Re: Using CUPS to print pdf in BBB-Angstrom

[beagleboard] MMC3 for SDIO communiction

[beagleboard] Using CUPS to print pdf in BBB-Angstrom

16 matches

Site Navigation

Mail list logo

Footer information