[beagleboard] Unhandled fault: external abort on non-linefetch (0x1028)

[JAY KOTHARI]

Hello,
  I am trying to access i2c_controller for AM335x sitara processor.When 
I am reading I2C_REVNB_HI register with ioread() I am getting a crash with 
show below error?

Unhandled fault: external abort on non-linefetch (0x1028)

What might be reason for such crash?

-- 
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] CAN-CAPE TT3201 CAN/CANBUS on BeagleBone Black Redux

[Andrew P. Lentvorski]

Anyway ... tl;dr I can verify that 2 of the 3 CANBUS interfaces on the 
TT3201 work.  The third looks like it should work, but I didn't verify it.

For those who would like to actually use the thing, here's the notes I was 
taking as I was going along in case I need to repeat this:


Dealing with CANBUS on the TT3201 with BeagleBone Black:

1) Start from 

Angstrom Distribution (BeagleBone, BeagleBone Black - 4GB SD) 2013-06-20 
https://s3.amazonaws.com/angstrom/demo/beaglebone/Angstrom-Cloud9-IDE-GNOME-eglibc-ipk-v2012.12-beaglebone-2013.06.20.img.xz


2)  Expanded partition to 16GB--I did everything from a uSD card rather 
than eMMC which seems to sidestep some collisions and timing problems with 
certain things that people reported on different groups.


3) opkg update 
4) opkg upgrade

(This dance required a couple of rounds and I had to shut down services on 
port 80 to get around an error)

Lather/rinse/repeat 3&4 until it converges.


5) Upgrade the kernel TowerTech's 3.8.13+ custom thing that you have to get 
directly from them

Really guys?  You don't just have a public link/repository in this day and 
age?  Sigh.  They did provide it within 24 hours, so "yay" for a vendor who 
actually responds to their support email address.

5b) Reboot



6) The default can utilities appear to be broken (or maybe I just don't 
understand them--wouldn't be the first time ).  You need to compile 
up a new set of can-utils from here: 
https://gitorious.org/linux-can/can-utils

Standard "./autogen.sh" "./configure" "make" dance applies as for anything 
afflicted with the autotools curse.



7) Connect can0 to can1--Connect Pin 8 to Pin 6 and Pin 7 to Pin 5.

Pinout data in the TT3201 "user manual" does appear to be correct.  I 
verified some stuff on my scope, but can2 exhibits different behavior from 
can0 and can1.  Not surprising since the first two seem to come from the 
MCP2515 chips and the other is directly from the SoC.

CAN0 -> IC4 -> Pin 7 and Pin 8 on connector
CAN1 -> IC5 -> Pin 5 and Pin 6 on connector
CAN2 -> IC6 -> Odd behavior that I still haven't worked out


8) Push the 3 switches on S1 away from the edge of the board

This seems to connect the 120Ohm terminating resistors for the interfaces.


9) Configure can buses

root@beaglebone:~# ip link set can0 type can bitrate 125000
root@beaglebone:~# ip link set can1 type can bitrate 125000
root@beaglebone:~# ip link set can0 up 
root@beaglebone:~# ip link set can1 up

CAUTION: My scope shows the TX line as being 15.8us from rising 
edge-to-rising edge.  That's exactly 1/2 of 125000 (as it should be since 
that's 2 *bits*), but it confused me until I thought about it for a bit. 
 So if you are interfacing to a different CAN system, make sure that you 
agree on what "bitrate" actually means.


10) Run cansend and candump in two different windows/sessions/whatever

root@beaglebone:~# cd linux-can-can-utils/
root@beaglebone:~/linux-can-can-utils# ./candump can1
  can1  1F334455   [8]  11 22 33 44 55 66 77 88

root@beaglebone:~# cd linux-can-can-utils/
root@beaglebone:~/linux-can-can-utils# ./cansend can0 
1F334455#1122334455667788


11) Resist urge to crumple up into a gibbering heap in the corner


As always, your mileage may vary.  Offer not valid anywhere.  You're on 
your own--cope.  Be careful out there.  Go pound sand.  Etc.


Anybody want to tackle doing this in straight Debian (TowerTech sends you a 
repo link)?  I'll buy you a beer.  Maybe even two.  Possibly a six pack.

Please?  Pretty please?  Don't make me do this 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.

[beagleboard] Beginning Operations on BBB, Android or Linux? Debugging and building Graphics applications

[madyn]

Note: the tags are a trifle misleading, but the best I can do.

I've got a BBB, Rev C.  I've considerable experience in programming 
embedded C on an XMEGA under FreeRTOS, so programming is not necessarily a 
problem.

However, I'm going back and forth about how to start (and this includes the 
basic environment) for the BBB.

The ultimate application would be instrument monitoring screens for custom 
I2C instruments (oscilloscope and logic analyzers), displayed on an LCD 
display with a resistive touchscreen.  The BBB has more RAM and can run 
programs out of RAM memory (does not have a Harvard architecture).

I'm using windows 8.1, not Linux, although I do have a laptop running 
Ubuntu 14 which I could use if needed.

I've considered bonescript and javascript, but at first glance, it may not 
be complex enough or capable enough to write drivers for I2C.  I'm also not 
sure about the graphics aspect, since a logic analyzer would need 
considerable graphics support (as does a scope).  The advantage of these 
seems to be that they are well supported.

I've considered the Debian Linux image as shipped.  Programming in C or C++ 
is not a problem, and it looks as if it works well at accessing the I2C 
devices. However, I've tried TI's Code Composer Studio, and find that the 
examples don't compile properly because the paths are not valid in windows 
8.1 (apparently, lots of "file not found, fatal error", for the includes.  
With multiple platforms and processors, CCS is not that friendly.  Nor is 
using Android on CCS.  Not sure what graphics tools are available for 
making a GUI program.

Android Image.  I have the circuitco image, which boots, but does not 
connect to the laptop over USB.  I can (probably) work thorugh the JNI 
aspect if I need that to get to the I2C drivers working, but haven't yet.  
Since Java has a built in GUI creator (drag and drop, I'm familiar with 
Lazarus Pascal, Delphi, and Visual studio, although I don't like visual 
studio at all), that solves the GUI problems.  Using Android studio, latest 
version.

However, under android, even setting Developer options/usb debugging does 
not even produce an undefined device on the direct USB cable connection to 
the PC (windows 8.1).   Trying to edit the android usb configuration .ini 
file (instructions at TI's android development platform) produces a file 
that windows says has been tampered with, and refuses to install.  The 
basic driver file (before modification) installs just fine.

SO:  Questions abound:
1) which application framework would be best to do what I need to do.  No 
problem doing Java if needed, no problem with C, C++ if needed...
2) Is there a specific problem with windows 8.1 and debugging (and changing 
.ini files) that I don't know the solution to (hopefully yes)
3) which platform is best at hardware access.  I need to be able to 
read/write I2C with binary strings to be able to communicate to the 
hardware and boards.  Those are already designed, so the protocol won't 
change, and I2C specifies only the first one or two bytes anyway.
4) I've read tons of web pages, and right now, I'd like to avoid Linux if 
possible, but if necessary, then I guess I need to.  Right now I'm trying 
to make it all work under windows 8.1 just to keep the development on the 
same system.  

These are a lot of questions, but I'm looking for a decent place (and 
direction) to start.  And no, the TI "blink the LED" application does not 
work (won't compile due to path problems, even with a default installation).

Thanks for any help.

Harvey

-- 
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: BBBAndroid with USB Bluetooth Adapter Support

[Keith Conger]

Oh ok I see. I'll give it a try.

Thanks,
Keith

On Tue, Feb 17, 2015 at 3:18 PM, Andrew Henderson  wrote:
> On Tue, 17 Feb 2015, Keith Conger wrote:
>
>> I did hand patch epoll_create1() into bionic.  The above was a logcat,
>> how do I get the errno value?
>
>
> Immediately after any failed POSIX call, the errno global variable (an
> integer) is set.  Just include the errno.h header in the file making the
> failed call to get access to the errno variable.  You can see how the logcat
> message is being generated in that same file (usually via a system() call to
> "logcat" or a C++ stream to LOG(INFO) or whatever.
>
> Andrew



-- 
Keith Conger
keith DOT conger AT gmail DOT com
http://thecongers.org

-- 
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: BBBAndroid with USB Bluetooth Adapter Support

[Andrew Henderson]

On Tue, 17 Feb 2015, Keith Conger wrote:


I did hand patch epoll_create1() into bionic.  The above was a logcat,
how do I get the errno value?


Immediately after any failed POSIX call, the errno global variable (an 
integer) is set.  Just include the errno.h header in the file making the 
failed call to get access to the errno variable.  You can see how the 
logcat message is being generated in that same file (usually via a 
system() call to "logcat" or a C++ stream to LOG(INFO) or whatever.


Andrew

Re: [beagleboard] Re: BBBAndroid with USB Bluetooth Adapter Support

[Keith Conger]

Hi Andrew,

I did hand patch epoll_create1() into bionic.  The above was a logcat,
how do I get the errno value?

Thanks,
Keith

On Tue, Feb 17, 2015 at 2:48 PM, Andrew Henderson  wrote:
> On Tuesday, February 17, 2015 at 4:20:42 PM UTC-5, Keith Conger wrote:
>
>>
>> D/bluetoothd( 1072):
>> external/bluetooth/bluez/android/ipc.c:cmd_connect_cb()
>>
>> E/bluetoothd( 1072): IPC: command socket connect failed
>
> OK, this is the place to start.  A socket isn't being created properly.
> That means that either the permissions aren't correct or the call used to
> create/interact with the socket is not supported.  The Bionic libc
> replacement does not implement a number of Linux kernel system calls because
> those system calls are not used under Android.  For example, shared memory
> or message queue syscalls aren't implemented because all IPC should be
> routed through Binder.  My guess is that you are running into something like
> this (section 1.2):
>
> http://forum.xda-developers.com/showthread.php?t=2640723
>
> The epoll_create1 syscall is not implemented by default in Bionic, so making
> an epoll_create1() call in Bionic results in an immediate failure.  Try
> dumping out logcat info at that error point with the errno value after the
> failed function call in cmd_connect_cb().  I bet that it is calling a Bionic
> function that doesn't generate the appropriate syscall to the kernel.
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/X4HYHv9cC-0/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.



-- 
Keith Conger
keith DOT conger AT gmail DOT com
http://thecongers.org

-- 
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: BBBAndroid with USB Bluetooth Adapter Support

[Andrew Henderson]

On Tuesday, February 17, 2015 at 4:20:42 PM UTC-5, Keith Conger wrote:
 

> D/bluetoothd( 1072): 
> external/bluetooth/bluez/android/ipc.c:cmd_connect_cb() 
>
> E/bluetoothd( 1072): IPC: command socket connect failed
>
OK, this is the place to start.  A socket isn't being created properly. 
 That means that either the permissions aren't correct or the call used to 
create/interact with the socket is not supported.  The Bionic libc 
replacement does not implement a number of Linux kernel system calls 
because those system calls are not used under Android.  For example, shared 
memory or message queue syscalls aren't implemented because all IPC should 
be routed through Binder.  My guess is that you are running into something 
like this (section 1.2):

http://forum.xda-developers.com/showthread.php?t=2640723

The epoll_create1 syscall is not implemented by default in Bionic, so 
making an epoll_create1() call in Bionic results in an immediate failure. 
 Try dumping out logcat info at that error point with the errno value after 
the failed function call in cmd_connect_cb().  I bet that it is calling a 
Bionic function that doesn't generate the appropriate syscall to the kernel.

-- 
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: BBBAndroid with USB Bluetooth Adapter Support

[Keith Conger]

I think I'm getting close with integrating android-bluez.  I have 
bluetoothd 'seeing' my adapter however dies at connecting to IPC.  I've 
posed the question to the bluez list.

Here is a logcat with debugging enabled.  I've googled the errors and have 
had no luck. 

I/bluetoothd( 1072): Bluetooth daemon 5.28

D/bluetoothd( 1072): 
external/bluetooth/bluez/android/main.c:set_capabilities() Caps: eff: 
0x3400, perm: 0x3400, inh: 0x0

D/bluetoothd( 1072): 
external/bluetooth/bluez/android/bluetooth.c:bt_bluetooth_start() index -1

I/bluetoothd( 1072): Starting SDP server

D/bluetoothd( 1072): external/bluetooth/bluez/android/main.c:main() 
Entering main loop

I/bluetoothd( 1072): mgmt_if: [0x] command 0x0001

I/bluetoothd( 1072): mgmt_if: < 01 00 ff ff 00 00  
  ..??..  

I/bluetoothd( 1072): mgmt_if: > 01 00 ff ff 06 00 01 00 00 01 07 00
  ..??

I/bluetoothd( 1072): mgmt_if: [0x] command 0x0001 complete: 0x00

D/bluetoothd( 1072): 
external/bluetooth/bluez/android/bluetooth.c:read_version_complete() 

I/bluetoothd( 1072): Bluetooth management interface 1.7 initialized

I/bluetoothd( 1072): Kernel connection control will be used

I/bluetoothd( 1072): mgmt_if: [0x] command 0x0003

I/bluetoothd( 1072): mgmt_if: < 03 00 ff ff 00 00  
  ..??..  

I/bluetoothd( 1072): mgmt_if: > 01 00 ff ff 07 00 03 00 00 01 00 00 00 
  ..??.   

I/bluetoothd( 1072): mgmt_if: [0x] command 0x0003 complete: 0x00

D/bluetoothd( 1072): 
external/bluetooth/bluez/android/bluetooth.c:read_index_list_complete() 

D/bluetoothd( 1072): 
external/bluetooth/bluez/android/bluetooth.c:read_index_list_complete() 
Number of controllers: 1

I/bluetoothd( 1072): mgmt_if: [0x] command 0x0004

I/bluetoothd( 1072): mgmt_if: < 04 00 00 00 00 00  
  ..  

I/bluetoothd( 1072): mgmt_if: > 01 00 00 00 1b 01 04 00 00 e9 36 36 e7 18 
00 03  .?66?...

I/bluetoothd( 1072): mgmt_if:   0f 00 bf 10 00 00 90 00 00 00 00 00 00 42 
43 4d  ..?..BCM

I/bluetoothd( 1072): mgmt_if:   32 30 34 35 42 33 00 00 00 00 00 00 00 00 
00 00  2045B3..

I/bluetoothd( 1072): mgmt_if:   00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00  

I/bluetoothd( 1072): mgmt_if:   00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00  

I/bluetoothd( 1072): mgmt_if:   00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00  

I/bluetoothd( 1072): mgmt_if:   00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00  

I/bluetoothd( 1072): mgmt_if:   00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00  

I/bluetoothd( 1072): mgmt_if:   00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00  

I/bluetoothd( 1072): mgmt_if:   00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00  

I/bluetoothd( 1072): mgmt_if:   00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00  

I/bluetoothd( 1072): mgmt_if:   00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00  

I/bluetoothd( 1072): mgmt_if:   00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00  

I/bluetoothd( 1072): mgmt_if:   00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00  

I/bluetoothd( 1072): mgmt_if:   00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00  

I/bluetoothd( 1072): mgmt_if:   00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00  

I/bluetoothd( 1072): mgmt_if:   00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00  

I/bluetoothd( 1072): mgmt_if:   00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00  

I/bluetoothd( 1072): mgmt_if:   00 
  .   

I/bluetoothd( 1072): mgmt_if: [0x] command 0x0004 complete: 0x00

D/bluetoothd( 1072): 
external/bluetooth/bluez/android/bluetooth.c:read_info_complete() 

D/bluetoothd( 1072): 
external/bluetooth/bluez/src/sdpd-service.c:register_device_id() Adding 
device id record for 0002:1d6b:0247:051c

D/bluetoothd( 1072): 
external/bluetooth/bluez/src/sdpd-service.c:add_record_to_server() Adding 
record with handle 0x10001

D/bluetoothd( 1072): 
external/bluetooth/bluez/src/sdpd-service.c:add_record_to_server() Record 
pattern UUID 1002--1000-8000-00805f9

D/bluetoothd( 1072): 
external/bluetooth/bluez/src/sdpd-service.c:add_record_to_server() Record 
pattern UUID 113a--1000-8000-00805f9

D/bluetoothd( 1072): 
external/bluetooth/bluez/src/sdpd-service.c:add_record_to_server() Record 
pattern UUID 113b--1000-8000-00805f9

D/bluetoothd( 1072): 
external/bluetooth/bluez/android/bluetooth.c:load_ltks() ltks 0

D/bluetoothd( 1072): 
external/bluetooth/bluez/android/bluetooth.c:load_irks() irks 0

D/bluetoothd( 1072): 
external/bluetooth/bluez/android/bluetooth.c:load_link_keys() keys 0 

I/bluetoothd( 1072): mgmt_if: [0x] command 0x000e

I/bluetoothd(

Re: [beagleboard] Re: Enable LCD4 adding .dts to Kernel source v3.1x ?

[Cedric Malitte]

Hi,

I'm not very familiar with the cape manager, but you should get a look 
at http://www.embest-tech.com/community/index.php?topic=2845.0

I am using kernels 3.1x that do not have the cape manager, so I play with 
the dts files and rebuild a kernel each time.

I told you about the BB-View because your LCD seems to be using 24bits.
If you hookup your lcd the same way the BB-View is done, you should be able 
to get something.

Can't help more than that.


Le mardi 17 février 2015 14:33:53 UTC-5, Rahul Mahajan a écrit :
>
> HI Cedric, 
>
> Thanks for your prompt reply. 
> I am using 3.8.13-bone68 kernel.but i am not understand how to enable 
> the bb-view dts in the config files as a starting point. 
> That file not having with me. 
> Please tell me how to proceed 
>
> thanks 
>
> On Mon, Feb 16, 2015 at 11:07 PM, Cedric Malitte 
> > wrote: 
> > Hi, 
> > 
> > you should look at this 
> > 
> http://www.element14.com/community/servlet/JiveServlet/previewBody/65082-102-5-294046/BB%20VIEW%20User%20Manual%20V3.pdf
>  
> > 
> > This is also a 24bit rgb lcd panel. 
> > 
> > If you want to enable your panel in linux, it will depend on your kernel 
> > version. 
> > If you have the 3.8.13, the one that came on the BBB , you will just 
> have to 
> > enalbe the bb-view dts in the config files as a starting point. 
> > 
> > For other kernels, I think bb-view is enabled at some point, but I'm not 
> > using those displays. 
> > I use the 4D systems cape displays because they are 16 bits, so it saves 
> me 
> > a few pins on the BBB. 
> > 
> > Regards. 
> > 
> > 
> > 2015-02-16 7:40 GMT-05:00 >: 
> > 
> >> Hi Cedric, 
> >> 
> >> can you tell me how your applying patch i am new to device tree. 
> >> can you tell me i am using this LCD paneel 
> >> 
> >> 
> http://www.aliexpress.com/store/product/4-3-inch-40PIN-TFT-LCD-Screen-with-Touch-Panel-OTA5180A-Drive-IC-480-272-RGB/224898_1899445212.html
>  
> >> but its not working as per this i changes in .dts file 
> >> but LCD is not working. 
> >> 
> >> Please give me details. 
> >> 
> >> thanks 
> >> 
> >> On Saturday, August 2, 2014 at 12:20:24 PM UTC+5:30, Cedric Malitte 
> wrote: 
> >>> 
> >>> Hi, 
> >>> 
> >>> I compiled the 3.13 and 3.15 kernel using Robert tools, and I saw this 
> >>> hoping to get LCD4 cape support: 
> >>> http://www.spinics.net/lists/linux-omap/msg109735.html 
> >>> 
> >>> I applied the patch against the kernel tree, but nothing happened at 
> boot 
> >>> after a rebuild, I mean screen stayed black. 
> >>> 
> >>> A quick look in the kernel tree dirs and the 
> am335x-bone-display-cape.dts 
> >>> has not been compiled. 
> >>> So I tried to ass it to Makefile, rebuild and got a fatal error from 
> DTC. 
> >>> 
> >>> I'm not very used to DT, so if someone could have a look at this file 
> and 
> >>> tell me what can be wrong, I'll try to rebuild it. 
> >>> 
> >>> /* 
> >>>  * Copyright (C) 2014 Texas Instruments Incorporated - 
> http://www.ti.com/ 
> >>>  * 
> >>>  * This program is free software; you can redistribute it and/or 
> modify 
> >>>  * it under the terms of the GNU General Public License version 2 as 
> >>>  * published by the Free Software Foundation. 
> >>>  * 
> >>>  * This DTS adds supports for display capes using LCD interface for 
> >>> display 
> >>>  * and GPIO or PWM interface for backlight controls. 
> >>>  */ 
> >>> &am33xx_pinmux { 
> >>> bbcape_backlight_pins: bbcape_backlight_pins { 
> >>> pinctrl-single,pins = < 
> >>> 0x48  (PIN_OUTPUT | MUX_MODE7) /* gpmc_a[2].GPIO1[18] (backlight 
> control) 
> >>> */ 
> >>> >; 
> >>> }; 
> >>> bbcape_lcd_pins: bbcape_lcd_pins { 
> >>> pinctrl-single,pins = < 
> >>> 0xa0 (PIN_OUTPUT | MUX_MODE0) /* lcd_data0.lcd_data0 */ 
> >>> 0xa4 (PIN_OUTPUT | MUX_MODE0) /* lcd_data1.lcd_data1 */ 
> >>> 0xa8 (PIN_OUTPUT | MUX_MODE0) /* lcd_data2.lcd_data2 */ 
> >>> 0xac (PIN_OUTPUT | MUX_MODE0) /* lcd_data3.lcd_data3 */ 
> >>> 0xb0 (PIN_OUTPUT | MUX_MODE0) /* lcd_data4.lcd_data4 */ 
> >>> 0xb4 (PIN_OUTPUT | MUX_MODE0) /* lcd_data5.lcd_data5 */ 
> >>> 0xb8 (PIN_OUTPUT | MUX_MODE0) /* lcd_data6.lcd_data6 */ 
> >>> 0xbc (PIN_OUTPUT | MUX_MODE0) /* lcd_data7.lcd_data7 */ 
> >>> 0xc0 (PIN_OUTPUT | MUX_MODE0) /* lcd_data8.lcd_data8 */ 
> >>> 0xc4 (PIN_OUTPUT | MUX_MODE0) /* lcd_data9.lcd_data9 */ 
> >>> 0xc8 (PIN_OUTPUT | MUX_MODE0) /* lcd_data10.lcd_data10 */ 
> >>> 0xcc (PIN_OUTPUT | MUX_MODE0) /* lcd_data11.lcd_data11 */ 
> >>> 0xd0 (PIN_OUTPUT | MUX_MODE0) /* lcd_data12.lcd_data12 */ 
> >>> 0xd4 (PIN_OUTPUT | MUX_MODE0) /* lcd_data13.lcd_data13 */ 
> >>> 0xd8 (PIN_OUTPUT | MUX_MODE0) /* lcd_data14.lcd_data14 */ 
> >>> 0xdc (PIN_OUTPUT | MUX_MODE0) /* lcd_data15.lcd_data15 */ 
> >>> 0xe0 (PIN_OUTPUT | MUX_MODE0) /* lcd_vsync.lcd_vsync */ 
> >>> 0xe4 (PIN_OUTPUT | MUX_MODE0) /* lcd_hsync.lcd_hsync */ 
> >>> 0xe8 (PIN_OUTPUT | MUX_MODE0) /* lcd_pclk.lcd_pclk */ 
> >>> 0xec (PIN_OUTPUT | MUX_MODE0) /* lcd_ac_bias_en.lcd_ac_bias_en 
> (lcd_en) 
> >>> */ 
> >>> 0x1a4 (PIN_OUTPUT_PULLUP | MUX_MODE7) /* mcasp0_fsr

Re: [beagleboard] Re: Cant flash Jessie to BBB

[Graham Haddock]

Most of the Debian distributions will totally fill the 2 GB eMMC.  I
suspect that is your problem.
You will either need to find a distribution that can load and run in 2 GB,
or get a FAST uSD card
that is larger than 2 GB and load the Debian distribution and run from the
card instead.

--- Graham

==

On Tue, Feb 17, 2015 at 9:18 AM,  wrote:

> I believe I have a BBB with 2 gigabyte eMMC. Problem is that I just cant
> seem to manage to get the images Chipsee provided with their expansion
> (their LCD cape) to work with the ralink usb wifi adapter (UWN100). Thatś
> why I'm trying to make it work with an other distribution :(
>
>
> On Monday, February 16, 2015 at 8:59:51 PM UTC+1, Graham wrote:
>>
>> Hi Auke:
>>
>> What kind (revision, size memory) of Beaglebone Black?
>> Which version of Jessie? (Date and name?)
>> What size SD-Card?
>> What speed of SD card?
>>
>> If the card is big enough, and the memory on the BBB is large enough, then
>> you should be able to install the ".img" on the card using
>> Win32DiskImager and
>> have it install on the BBB just fine. Time will be 10 minutes for a fast
>> SD card, and
>> perhaps 30 minutes for a slow card.
>>
>> --- Graham
>>
>> ==
>>
>>
>> On Monday, February 16, 2015 at 7:39:12 AM UTC-6, auk...@gmail.com wrote:
>>>
>>> Hello!
>>>
>>> I can't manage to flash Jessie to my BBB.  I tried to install Jessie
>>> (Debian version; still in testing fase). But when I try to flash Jessie the
>>> leds light up in the following pattern USR0 -> USR1 -> USR2 -> USR3 -> USR0
>>> and so on. I left it on for about an hour and still saw no difference. Do I
>>> have to wait longer, or is it maybe my fault for using windows to create
>>> the bootable SD-card and it should work with Linux?
>>>
>>> The reason I'm trying to flash it, is because I can't get the Ralink
>>> UWN100 to work with the debian image Chipsee provided (I'm using their 7
>>> inch lcd screen), and I've heard that it's supported in Jessie.
>>>
>>> I really really would appreciate any help!
>>>
>>> Thanks in advance,
>>>
>>> Auke
>>>
>>  --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/zkN55PjhoTw/unsubscribe.
> To unsubscribe from this group and all its topics, 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] Enabling debugfs for ATH9k on BBB running Debian 3.19:Compile new Kernel vs Backports

[Marco Steger]

Hi Robert,
thank you - I will try To compile the kernel tomorrow.

Backports: https://backports.wiki.kernel.org/index.php/Documentation

I'm not sure if it is also part of the Debian backport repo. It's mainly
about wireles: 80211, Bluetooth, ...

Thanks again and besteht regards,
Marco
Am 17.02.2015 18:42 schrieb "Robert Nelson" :

> On Tue, Feb 17, 2015 at 11:39 AM, Marco Steger 
> wrote:
> > Dear Robert,
> > thanks for your help - again! :)
> >
> >>Yeap, all the patches are in the tag...  The default config is:
> >> rcn-ee_defconfig
> > This is great! Makes things much easier!
> >
> >> make ARCH=arm  LOCALVERSION=- CROSS_COMPILE=
> > KBUILD_DEBARCH=armhf deb-pkg
> >
> > I'm not really sure here: Does this mean that the compiling will be done
> on
> > the BBB or crosscompile on another PC? But I will need to install a
> > toolchain for that rigth? This one: 'gcc-arm-linux-gnueabi'?
>
> If on the "BBB" just use: CROSS_COMPILE=
>
> If on an x86, use: CROSS_COMPILE=/path/to/bin/gcc
>
> > I also tried to comple my backports (directly on the BBB). Therefore, I
> used
> > KLIB and KLIB_BUILD to point to the kernel source. But this didn't worked
> > for me. But maybe also a problem with missing tools / toolchain. Has
> anyone
> > expiriences with backports on BBB?
>
> debian backport repo?
>
> 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 a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/WFlb_7dzwi0/unsubscribe.
> To unsubscribe from this group and all its topics, 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: Enable LCD4 adding .dts to Kernel source v3.1x ?

[Rahul Mahajan]

HI Cedric,

Thanks for your prompt reply.
I am using 3.8.13-bone68 kernel.but i am not understand how to enable
the bb-view dts in the config files as a starting point.
That file not having with me.
Please tell me how to proceed

thanks

On Mon, Feb 16, 2015 at 11:07 PM, Cedric Malitte
 wrote:
> Hi,
>
> you should look at this
> http://www.element14.com/community/servlet/JiveServlet/previewBody/65082-102-5-294046/BB%20VIEW%20User%20Manual%20V3.pdf
>
> This is also a 24bit rgb lcd panel.
>
> If you want to enable your panel in linux, it will depend on your kernel
> version.
> If you have the 3.8.13, the one that came on the BBB , you will just have to
> enalbe the bb-view dts in the config files as a starting point.
>
> For other kernels, I think bb-view is enabled at some point, but I'm not
> using those displays.
> I use the 4D systems cape displays because they are 16 bits, so it saves me
> a few pins on the BBB.
>
> Regards.
>
>
> 2015-02-16 7:40 GMT-05:00 :
>
>> Hi Cedric,
>>
>> can you tell me how your applying patch i am new to device tree.
>> can you tell me i am using this LCD paneel
>>
>> http://www.aliexpress.com/store/product/4-3-inch-40PIN-TFT-LCD-Screen-with-Touch-Panel-OTA5180A-Drive-IC-480-272-RGB/224898_1899445212.html
>> but its not working as per this i changes in .dts file
>> but LCD is not working.
>>
>> Please give me details.
>>
>> thanks
>>
>> On Saturday, August 2, 2014 at 12:20:24 PM UTC+5:30, Cedric Malitte wrote:
>>>
>>> Hi,
>>>
>>> I compiled the 3.13 and 3.15 kernel using Robert tools, and I saw this
>>> hoping to get LCD4 cape support:
>>> http://www.spinics.net/lists/linux-omap/msg109735.html
>>>
>>> I applied the patch against the kernel tree, but nothing happened at boot
>>> after a rebuild, I mean screen stayed black.
>>>
>>> A quick look in the kernel tree dirs and the am335x-bone-display-cape.dts
>>> has not been compiled.
>>> So I tried to ass it to Makefile, rebuild and got a fatal error from DTC.
>>>
>>> I'm not very used to DT, so if someone could have a look at this file and
>>> tell me what can be wrong, I'll try to rebuild it.
>>>
>>> /*
>>>  * Copyright (C) 2014 Texas Instruments Incorporated - http://www.ti.com/
>>>  *
>>>  * This program is free software; you can redistribute it and/or modify
>>>  * it under the terms of the GNU General Public License version 2 as
>>>  * published by the Free Software Foundation.
>>>  *
>>>  * This DTS adds supports for display capes using LCD interface for
>>> display
>>>  * and GPIO or PWM interface for backlight controls.
>>>  */
>>> &am33xx_pinmux {
>>> bbcape_backlight_pins: bbcape_backlight_pins {
>>> pinctrl-single,pins = <
>>> 0x48  (PIN_OUTPUT | MUX_MODE7) /* gpmc_a[2].GPIO1[18] (backlight control)
>>> */
>>> >;
>>> };
>>> bbcape_lcd_pins: bbcape_lcd_pins {
>>> pinctrl-single,pins = <
>>> 0xa0 (PIN_OUTPUT | MUX_MODE0) /* lcd_data0.lcd_data0 */
>>> 0xa4 (PIN_OUTPUT | MUX_MODE0) /* lcd_data1.lcd_data1 */
>>> 0xa8 (PIN_OUTPUT | MUX_MODE0) /* lcd_data2.lcd_data2 */
>>> 0xac (PIN_OUTPUT | MUX_MODE0) /* lcd_data3.lcd_data3 */
>>> 0xb0 (PIN_OUTPUT | MUX_MODE0) /* lcd_data4.lcd_data4 */
>>> 0xb4 (PIN_OUTPUT | MUX_MODE0) /* lcd_data5.lcd_data5 */
>>> 0xb8 (PIN_OUTPUT | MUX_MODE0) /* lcd_data6.lcd_data6 */
>>> 0xbc (PIN_OUTPUT | MUX_MODE0) /* lcd_data7.lcd_data7 */
>>> 0xc0 (PIN_OUTPUT | MUX_MODE0) /* lcd_data8.lcd_data8 */
>>> 0xc4 (PIN_OUTPUT | MUX_MODE0) /* lcd_data9.lcd_data9 */
>>> 0xc8 (PIN_OUTPUT | MUX_MODE0) /* lcd_data10.lcd_data10 */
>>> 0xcc (PIN_OUTPUT | MUX_MODE0) /* lcd_data11.lcd_data11 */
>>> 0xd0 (PIN_OUTPUT | MUX_MODE0) /* lcd_data12.lcd_data12 */
>>> 0xd4 (PIN_OUTPUT | MUX_MODE0) /* lcd_data13.lcd_data13 */
>>> 0xd8 (PIN_OUTPUT | MUX_MODE0) /* lcd_data14.lcd_data14 */
>>> 0xdc (PIN_OUTPUT | MUX_MODE0) /* lcd_data15.lcd_data15 */
>>> 0xe0 (PIN_OUTPUT | MUX_MODE0) /* lcd_vsync.lcd_vsync */
>>> 0xe4 (PIN_OUTPUT | MUX_MODE0) /* lcd_hsync.lcd_hsync */
>>> 0xe8 (PIN_OUTPUT | MUX_MODE0) /* lcd_pclk.lcd_pclk */
>>> 0xec (PIN_OUTPUT | MUX_MODE0) /* lcd_ac_bias_en.lcd_ac_bias_en (lcd_en)
>>> */
>>> 0x1a4 (PIN_OUTPUT_PULLUP | MUX_MODE7) /* mcasp0_fsr.gpio3[19] (lcd_disen)
>>> */
>>> >;
>>> };
>>> bbcape_touchscreen_pins: bbcape_touchscreen_pins {
>>> pinctrl-single,pins = <
>>> 0x184 (PIN_INPUT_PULLDOWN | MUX_MODE7) /* uart1_txd.gpio0[15] (enter) */
>>> 0x40  (PIN_INPUT_PULLDOWN | MUX_MODE7) /* gpmc_a0.gpio1[16] (left) */
>>> 0x44  (PIN_INPUT_PULLDOWN | MUX_MODE7) /* gpmc_a1.gpio1[17] (right) */
>>> 0x4c  (PIN_INPUT_PULLDOWN | MUX_MODE7) /* gpmc_a3.gpio1[19] (up) */
>>> 0x198 (PIN_INPUT_PULLDOWN | MUX_MODE7) /* mcasp0_axr0.gpio3[16] (down) */
>>> >;
>>> };
>>> };
>>>
>>> / {
>>> backlight {
>>> status = "okay";
>>> compatible = "gpio-backlight";
>>> pinctrl-names = "default";
>>> pinctrl-0 = <&bbcape_backlight_pins>;
>>> gpios = <&gpio1 18 GPIO_ACTIVE_HIGH>;
>>> default-on;
>>> };
>>> panel {
>>> status = "okay";
>>> compatible = "ti,tilcdc,panel";
>>> pinctrl-names = "default";
>>> pinctrl-0 = <&bbcape_lcd_pins>;
>>> pa

[beagleboard] BBB not working well with Mac Yosemite

[vincent . kc . chow]

Hi, I got a new bbb, and want to test under mac yosemite. I've got the 
drivers installed, but sometimes my mac just freeze and force me to reboot, 
anyone share the same experience?

The cable is working well on Windows 7.

I read someone said the usb driver is working perfectly well on Maverick 
and Yosemite. Could anyone advise how could I use the board smoothly on Mac 
Yosemite please? Thanks a lot!!

-- 
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: Enable LCD4 adding .dts to Kernel source v3.1x ?

[mahajanrahulc . 28]

HI Cedric,

Thanks for your prompt reply.
I am not using BB-view cape i only used 
4.3 inch 40PIN TFT LCD Screen with Touch Panel OTA5180A Drive IC 480*272 
RGB interface.I am using 3.8.13-bone68 kernel.but i am not understand how 
to enable the bb-view dts in the config files as a starting point.
That file not having with me.
Please tell me how to proceed

thanks


On Saturday, August 2, 2014 at 12:20:24 PM UTC+5:30, Cedric Malitte wrote:
>
> Hi,
>
> I compiled the 3.13 and 3.15 kernel using Robert tools, and I saw this 
> hoping to get LCD4 cape support: 
> http://www.spinics.net/lists/linux-omap/msg109735.html
>
> I applied the patch against the kernel tree, but nothing happened at boot 
> after a rebuild, I mean screen stayed black.
>
> A quick look in the kernel tree dirs and the am335x-bone-display-cape.dts 
> has not been compiled.
> So I tried to ass it to Makefile, rebuild and got a fatal error from DTC.
>
> I'm not very used to DT, so if someone could have a look at this file and 
> tell me what can be wrong, I'll try to rebuild it.
>
> /*
>  * Copyright (C) 2014 Texas Instruments Incorporated - http://www.ti.com/
>  *
>  * This program is free software; you can redistribute it and/or modify
>  * it under the terms of the GNU General Public License version 2 as
>  * published by the Free Software Foundation.
>  *
>  * This DTS adds supports for display capes using LCD interface for display
>  * and GPIO or PWM interface for backlight controls.
>  */
> &am33xx_pinmux {
> bbcape_backlight_pins: bbcape_backlight_pins {
> pinctrl-single,pins = <
> 0x48  (PIN_OUTPUT | MUX_MODE7) /* gpmc_a[2].GPIO1[18] (backlight control) 
> */
> >;
> };
> bbcape_lcd_pins: bbcape_lcd_pins {
> pinctrl-single,pins = <
> 0xa0 (PIN_OUTPUT | MUX_MODE0) /* lcd_data0.lcd_data0 */
> 0xa4 (PIN_OUTPUT | MUX_MODE0) /* lcd_data1.lcd_data1 */
> 0xa8 (PIN_OUTPUT | MUX_MODE0) /* lcd_data2.lcd_data2 */
> 0xac (PIN_OUTPUT | MUX_MODE0) /* lcd_data3.lcd_data3 */
> 0xb0 (PIN_OUTPUT | MUX_MODE0) /* lcd_data4.lcd_data4 */
> 0xb4 (PIN_OUTPUT | MUX_MODE0) /* lcd_data5.lcd_data5 */
> 0xb8 (PIN_OUTPUT | MUX_MODE0) /* lcd_data6.lcd_data6 */
> 0xbc (PIN_OUTPUT | MUX_MODE0) /* lcd_data7.lcd_data7 */
> 0xc0 (PIN_OUTPUT | MUX_MODE0) /* lcd_data8.lcd_data8 */
> 0xc4 (PIN_OUTPUT | MUX_MODE0) /* lcd_data9.lcd_data9 */
> 0xc8 (PIN_OUTPUT | MUX_MODE0) /* lcd_data10.lcd_data10 */
> 0xcc (PIN_OUTPUT | MUX_MODE0) /* lcd_data11.lcd_data11 */
> 0xd0 (PIN_OUTPUT | MUX_MODE0) /* lcd_data12.lcd_data12 */
> 0xd4 (PIN_OUTPUT | MUX_MODE0) /* lcd_data13.lcd_data13 */
> 0xd8 (PIN_OUTPUT | MUX_MODE0) /* lcd_data14.lcd_data14 */
> 0xdc (PIN_OUTPUT | MUX_MODE0) /* lcd_data15.lcd_data15 */
> 0xe0 (PIN_OUTPUT | MUX_MODE0) /* lcd_vsync.lcd_vsync */
> 0xe4 (PIN_OUTPUT | MUX_MODE0) /* lcd_hsync.lcd_hsync */
> 0xe8 (PIN_OUTPUT | MUX_MODE0) /* lcd_pclk.lcd_pclk */
> 0xec (PIN_OUTPUT | MUX_MODE0) /* lcd_ac_bias_en.lcd_ac_bias_en (lcd_en) */
> 0x1a4 (PIN_OUTPUT_PULLUP | MUX_MODE7) /* mcasp0_fsr.gpio3[19] (lcd_disen) 
> */
> >;
> };
> bbcape_touchscreen_pins: bbcape_touchscreen_pins {
> pinctrl-single,pins = <
> 0x184 (PIN_INPUT_PULLDOWN | MUX_MODE7) /* uart1_txd.gpio0[15] (enter) */
> 0x40  (PIN_INPUT_PULLDOWN | MUX_MODE7) /* gpmc_a0.gpio1[16] (left) */
> 0x44  (PIN_INPUT_PULLDOWN | MUX_MODE7) /* gpmc_a1.gpio1[17] (right) */
> 0x4c  (PIN_INPUT_PULLDOWN | MUX_MODE7) /* gpmc_a3.gpio1[19] (up) */
> 0x198 (PIN_INPUT_PULLDOWN | MUX_MODE7) /* mcasp0_axr0.gpio3[16] (down) */
> >;
> };
> };
>
> / {
> backlight {
> status = "okay";
> compatible = "gpio-backlight";
> pinctrl-names = "default";
> pinctrl-0 = <&bbcape_backlight_pins>;
> gpios = <&gpio1 18 GPIO_ACTIVE_HIGH>;
> default-on;
> };
> panel {
> status = "okay";
> compatible = "ti,tilcdc,panel";
> pinctrl-names = "default";
> pinctrl-0 = <&bbcape_lcd_pins>;
> panel-info {
> ac-bias   = <255>;
> ac-bias-intrpt= <0>;
> dma-burst-sz  = <16>;
> bpp   = <16>;
> fdd   = <0x80>;
> sync-edge = <0>;
> sync-ctrl = <1>;
> raster-order  = <0>;
> fifo-th   = <0>;
> };
> display-timings {
> native-mode = <&timing0>;
> /* www.newhavendisplay.com/app_notes/OTA5180A.pdf */
> timing0: 480x272 {
> clock-frequency = <920>;
> hactive = <480>;
> vactive = <272>;
> hfront-porch = <8>;
> hback-porch = <47>;
> hsync-len = <41>;
> vback-porch = <2>;
> vfront-porch = <3>;
> vsync-len = <10>;
> hsync-active = <0>;
> vsync-active = <0>;
> de-active = <1>;
> pixelclk-active = <0>;
> };
> };
> };
> }; 
>
>
> Thanks 
>
> Cedric. 
>

-- 
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: Cant flash Jessie to BBB

[auke989]

I believe I have a BBB with 2 gigabyte eMMC. Problem is that I just cant 
seem to manage to get the images Chipsee provided with their expansion 
(their LCD cape) to work with the ralink usb wifi adapter (UWN100). Thatś 
why I'm trying to make it work with an other distribution :(

On Monday, February 16, 2015 at 8:59:51 PM UTC+1, Graham wrote:
>
> Hi Auke:
>
> What kind (revision, size memory) of Beaglebone Black?
> Which version of Jessie? (Date and name?)
> What size SD-Card?
> What speed of SD card?
>
> If the card is big enough, and the memory on the BBB is large enough, then
> you should be able to install the ".img" on the card using Win32DiskImager 
> and
> have it install on the BBB just fine. Time will be 10 minutes for a fast 
> SD card, and
> perhaps 30 minutes for a slow card.
>
> --- Graham
>
> ==
>
>
> On Monday, February 16, 2015 at 7:39:12 AM UTC-6, auk...@gmail.com wrote:
>>
>> Hello!
>>
>> I can't manage to flash Jessie to my BBB.  I tried to install Jessie 
>> (Debian version; still in testing fase). But when I try to flash Jessie the 
>> leds light up in the following pattern USR0 -> USR1 -> USR2 -> USR3 -> USR0 
>> and so on. I left it on for about an hour and still saw no difference. Do I 
>> have to wait longer, or is it maybe my fault for using windows to create 
>> the bootable SD-card and it should work with Linux?
>>
>> The reason I'm trying to flash it, is because I can't get the Ralink 
>> UWN100 to work with the debian image Chipsee provided (I'm using their 7 
>> inch lcd screen), and I've heard that it's supported in Jessie.
>>
>> I really really would appreciate any help!
>>
>> Thanks in advance,
>>
>> Auke
>>
>

-- 
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] Can't make UART work with Python and AdaFruitBBB

[palaniyappan r]

Thank you sir... I have WiFi dongle used to my computer.Can I used same
wifi usb dongle for BBB? Because of I tried But It did not connect. How to
connect WIFI usb for my BBB?



*--regards,*


*palaniyappan.R*

On Tue, Feb 17, 2015 at 5:19 PM, Cláudio B  wrote:

> @palaniyappan
>
> You can if you use the same protocol developed in BBB.
>
>
>
> 2015-02-14 8:14 GMT-02:00 :
>
>> I have GPRS modem for PIC microcontroller. Can I used  same gprs modem
>> for BBB?
>>
>>
>> --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to a topic in the
>> Google Groups "BeagleBoard" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/beagleboard/-I_to80m9_Y/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> beagleboard+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Cláudio B.
> Desenvolvimento de Software
> Logmatch Produtos Eletrônicos LTDA
>
> 31 3476-8540
>
> clau...@logmatch.com.br
>
> Solução de qualidade para o controle de ponto em sua empresa.
> Mensis  - Belo Horizonte
> 
>
>  --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/-I_to80m9_Y/unsubscribe.
> To unsubscribe from this group and all its topics, 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.

[beagleboard] Re: Unable to Connect to BBB via USB from OSX Yosemite

[Vincent Chow]

I found some folks said the usb driver is not working well on Mac Maverick
and Yosemite, is it?

the cable is working fine on Windows 7.

On Sat, Feb 14, 2015 at 10:27 PM, SimGQ  wrote:

> One factor that plays a huge part in connecting to the BBB is the quality
> of the USB lead.
>
> We had issues when using longer leads, which seemed to be physically
> thinner than those supplied with the boards. Once the shorter fatter leads
> were used connections tended to be more consistent.
>



-- 
Cheers,
Vincent

-- 
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] Beaglebone Black Ethernet Phy Not Detected on Boot.

[bkozak]

Hi Alex,

In my test, like John Zhang, I also had my BBB sending a ping after boot to 
confirm that Ethernet was working. In my experience the "Phy 0 not found" log 
message will occur even when the Ethernet seems to work normally.

Regards,
Bill

-- 
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] Enabling debugfs for ATH9k on BBB running Debian 3.19:Compile new Kernel vs Backports

[Robert Nelson]

On Tue, Feb 17, 2015 at 11:39 AM, Marco Steger  wrote:
> Dear Robert,
> thanks for your help - again! :)
>
>>Yeap, all the patches are in the tag...  The default config is:
>> rcn-ee_defconfig
> This is great! Makes things much easier!
>
>> make ARCH=arm  LOCALVERSION=- CROSS_COMPILE=
> KBUILD_DEBARCH=armhf deb-pkg
>
> I'm not really sure here: Does this mean that the compiling will be done on
> the BBB or crosscompile on another PC? But I will need to install a
> toolchain for that rigth? This one: 'gcc-arm-linux-gnueabi'?

If on the "BBB" just use: CROSS_COMPILE=

If on an x86, use: CROSS_COMPILE=/path/to/bin/gcc

> I also tried to comple my backports (directly on the BBB). Therefore, I used
> KLIB and KLIB_BUILD to point to the kernel source. But this didn't worked
> for me. But maybe also a problem with missing tools / toolchain. Has anyone
> expiriences with backports on BBB?

debian backport repo?

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/d/optout.

Re: [beagleboard] Enabling debugfs for ATH9k on BBB running Debian 3.19:Compile new Kernel vs Backports

[Marco Steger]

Dear Robert,
thanks for your help - again! :)

>Yeap, all the patches are in the tag...  The default config is:
rcn-ee_defconfig
This is great! Makes things much easier!

> make ARCH=arm  LOCALVERSION=- CROSS_COMPILE=
KBUILD_DEBARCH=armhf deb-pkg

I'm not really sure here: Does this mean that the compiling will be done on
the BBB or crosscompile on another PC? But I will need to install a
toolchain for that rigth? This one: 'gcc-arm-linux-gnueabi'?

I also tried to comple my backports (directly on the BBB). Therefore, I
used KLIB and KLIB_BUILD to point to the kernel source. But this didn't
worked for me. But maybe also a problem with missing tools / toolchain. Has
anyone expiriences with backports on BBB?

Thanks for all your help!!! Really great!!!
Best regards,
Marco







2015-02-17 16:21 GMT+01:00 Robert Nelson :

> On Tue, Feb 17, 2015 at 9:10 AM, Marco Steger 
> wrote:
> > Hi,
> >
> > so I just can use this source without any patches or something like that?
>
> Yeap, all the patches are in the tag...  The default config is:
> rcn-ee_defconfig
>
> >
> > I will just try to use:
> >
> > 1.) make menuconfig
> > 2.) make
> > 3.) make install
> >
> > is this right?
>
> However, make install won't install the files in the correct place..
>
> make ARCH=arm  LOCALVERSION=- CROSS_COMPILE=
> KBUILD_DEBARCH=armhf deb-pkg
>
> Then install the *.deb
>
> 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 a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/WFlb_7dzwi0/unsubscribe.
> To unsubscribe from this group and all its topics, 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.

[beagleboard] Re: On power-up, PWRONRSTn (PORZ) becomes de-asserted while WARMRSTn stays asserted (low).

[ulrichd]

RESOLVED - Found error in the BOM - inverted part was placed on board.



On Tuesday, February 17, 2015 at 10:19:04 AM UTC-5, ulrichd wrote:

>
>- 
>
>Symptom:
>- 
>
>
>- 
>   
>   On power-up, PWRONRSTn (B15 – PORZ) – pin 2 of U16 
>   becomes de-asserted while WARMRSTn  (A10 – NRESET_INOUT) stays 
>   asserted (low).  
>   
>
>- 
>
>
>- 
>
>
>- 
>
>Below is a summary of the current situation and test executed. Any 
>feedback is greatly appreciated. 
>- 
>
>
>- 
>
>Same symptoms on 5 circuit boards. New design – based on BeagleBone 
>Black.
>- 
>
>24mHz oscillator is oscillating
>- 
>
>32Khz oscillator is not oscillating
>- 
>
>Measured resistance to ground on WARMRSTn  (A10 – NRESET_INOUT)  using 
>DVM – about 15K ohms – no short.
>- 
>
>Removed C35 based on Paul’s recommendation  – no effect
>- 
>
>Removed R9 based on Biser’s recommendation – no effect
>- 
>
>Checked all voltages and all align with datasheet 
>- 
>   
>   3.3V operation for I/O
>   - 
>   
>VDD_MPU is set for OPP_100 – is there something else that needs to 
>   be setup?
>   - 
>
>Found a note in the BeagleBone notes – revision A6 – referencing AND 
>gate. This is not in our design since it is not shown in schematic. Could 
>this be a factor?
>
>  
>
>  
>
> A6
>  
> 1. Moved the enable for the VDD_3V3B regulator to VDD_3V3A rail. Change 
> was made to reduce the delay between the ramp up of the 3.3V rails.
>
> 2. Added a AND gate to the SYS_RESETn circuitry. There is a small chance 
> that on power up the nRESETOUT signal on the processor may go high, 
> causing the SYS_RESETn signal to go HI before it should. This change 
> reenforces the reset with the PORZn reset signal.
> 3. Added optional zero ohm resistor to tie GND_OSC0 to system ground.
>
>
>   
>
>  
>
> 7/25/2013
>  
>  
>
>  
>
> GC
>  
>  
>

-- 
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] Enabling debugfs for ATH9k on BBB running Debian 3.19:Compile new Kernel vs Backports

[Robert Nelson]

On Tue, Feb 17, 2015 at 9:10 AM, Marco Steger  wrote:
> Hi,
>
> so I just can use this source without any patches or something like that?

Yeap, all the patches are in the tag...  The default config is: rcn-ee_defconfig

>
> I will just try to use:
>
> 1.) make menuconfig
> 2.) make
> 3.) make install
>
> is this right?

However, make install won't install the files in the correct place..

make ARCH=arm  LOCALVERSION=- CROSS_COMPILE=
KBUILD_DEBARCH=armhf deb-pkg

Then install the *.deb

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/d/optout.

Re: [beagleboard] Enabling debugfs for ATH9k on BBB running Debian 3.19:Compile new Kernel vs Backports

[Marco Steger]

Hi,

so I just can use this source without any patches or something like that?

I will just try to use:

1.) make menuconfig
2.) make
3.) make install

is this right?

Best regards and thanks for your help,
Marco

2015-02-17 15:08 GMT+01:00 Robert Nelson :

> On Tue, Feb 17, 2015 at 7:37 AM, Marco Steger 
> wrote:
> > Dear all,
> >
> > I'm currently working on a IEEE802.11s WSN using 5 BBBs and a TP-Link
> stick.
> > To evaluate the wireless link I need to get more information on the
> wireless
> > link. Therefore, I want to enable the debugfs option of the ATH9k driver
> > module (because just enabling the debug mode using 'modprobe ath9k_htc
> > debug=0x' didn't work for me).
> >
> > I think I will have to recompile the ath9k module and some related
> modules.
> > As far as I understand all what I need for that is part of the backports
> > project [1]. I have already used this on Android for another purpose and
> > everything worked fine. BUT, I will need the kernel source for the
> compiling
> > process! Where to get the source? (I used Roberts update_kernel.sh
> script to
> > upgrade my kernel to 3.19)
> >
> > Another possibility would be to compile a kernel and using make
> menuconfig
> > to configure the modules. But therefore I would also need the kernel
> source.
> > I really want to use Robert Nelsons version because I will also need to
> use
> > DTBs for CAN.
> >
> > Can anyone help me out here? What would be better/easier?
>
> There's a repo here:
> https://github.com/RobertCNelson/linux-stable-rcn-ee
>
> Each release (uname -r) is tagged so:
>
> git clone https://github.com/RobertCNelson/linux-stable-rcn-ee
> cd ./linux-stable-rcn-ee
> git checkout `uname -r` -b tmp
>
> 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 a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/WFlb_7dzwi0/unsubscribe.
> To unsubscribe from this group and all its topics, 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.

[beagleboard] Re: Static IP on eth0

[Enric Climent]

El dimarts, 17 febrer de 2015 4:44:33 UTC+1, Brian Anderson va escriure:
>
> Enric,
>
> I think your problem may be related to ConnMan.  ConnMan is a network 
> manager that is installed on the Jessie test images.  It manages your 
> network connections, including eth.  Any settings you have in 
> /etc/network/interfaces is overriden by ConnMan, and thus this is why you 
> see a DHCP assigned address rather than the static address configured in 
> /etc/network/interfaces when you reboot.
>
> You can disable ConnMan (not recommended), tell ConnMan to not manage eth0 
> on your behalf and manage things yourself (again, not recommended), or use 
> ConnMan to setup a static IP address.  Using ConnMan to setup a static IP 
> address will be "persistent", that is it will survive reboots.  This is 
> pretty simple:
>
> First, determine the "service" name of your ethernet:
>
> *connmanctl services*
>
> Using the appropriate ethernet service, tell connman to setup a static IP 
> address for that service:
>
> su*do connmanctl config  --ipv4 manual   
>  --nameservers *
>
> You will need to pick an IP address compatible with your network and 
> router.
>
> For example:
>
> $ connmanctl services
> *AO Wiredethernet_d05fb8ed4f78_cable
> $ sudo connmanctl config ethernet_d05fb8ed4f78_cable --ipv4 manual 
> 10.0.1.100 255.255.255.0 10.0.1.1 --nameservers 8.8.8.8
>
> You should then see the new address using the "ip" command:
>
> $ ip addr show dev eth0
> 2: eth0:  mtu 1500 qdisc 
> pfifo_fast state UP group default qlen 1000
> link/ether d0:5f:b8:ed:4f:78 brd ff:ff:ff:ff:ff:ff
> inet 10.0.1.100/24 brd 10.0.1.255 scope global eth0
>valid_lft forever preferred_lft forever
> inet6 fe80::d25f:b8ff:feed:4f78/64 scope link 
>valid_lft forever preferred_lft forever
>
> You should now also be able to "ping" an address such as "google.com".
>
> You can revert back to a DHCP configuration simply as follows:
>
> $ sudo connmanctl config ethernet_d05fb8ed4f78_cable --ipv4 dhcp
>
> It would be best if you have a FTDI serial cable so you can see what is 
> going on at the console in case something goes wrong.  Actually, it would 
> be best to issues these commands from the console rather than ssh'ing.
>
> Hope this helps
>
> ba
>

Ok thanks i try it. For now i get static ip writing simple script and save 
it at /etc/init.d :
#!bash
/etc/init.d/networking restart

after:
# update-rc.d fixnet defaults

And now i get static ip when reboot bbb.
So i try understant how connman works and will edit configuration for 
static ip at eth0.
Thanks a lot bro ;)

-- 
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] Enabling debugfs for ATH9k on BBB running Debian 3.19:Compile new Kernel vs Backports

[Robert Nelson]

On Tue, Feb 17, 2015 at 7:37 AM, Marco Steger  wrote:
> Dear all,
>
> I'm currently working on a IEEE802.11s WSN using 5 BBBs and a TP-Link stick.
> To evaluate the wireless link I need to get more information on the wireless
> link. Therefore, I want to enable the debugfs option of the ATH9k driver
> module (because just enabling the debug mode using 'modprobe ath9k_htc
> debug=0x' didn't work for me).
>
> I think I will have to recompile the ath9k module and some related modules.
> As far as I understand all what I need for that is part of the backports
> project [1]. I have already used this on Android for another purpose and
> everything worked fine. BUT, I will need the kernel source for the compiling
> process! Where to get the source? (I used Roberts update_kernel.sh script to
> upgrade my kernel to 3.19)
>
> Another possibility would be to compile a kernel and using make menuconfig
> to configure the modules. But therefore I would also need the kernel source.
> I really want to use Robert Nelsons version because I will also need to use
> DTBs for CAN.
>
> Can anyone help me out here? What would be better/easier?

There's a repo here:
https://github.com/RobertCNelson/linux-stable-rcn-ee

Each release (uname -r) is tagged so:

git clone https://github.com/RobertCNelson/linux-stable-rcn-ee
cd ./linux-stable-rcn-ee
git checkout `uname -r` -b tmp

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/d/optout.

[beagleboard] Enabling debugfs for ATH9k on BBB running Debian 3.19:Compile new Kernel vs Backports

[Marco Steger]

Dear all,

I'm currently working on a IEEE802.11s WSN using 5 BBBs and a TP-Link 
stick. To evaluate the wireless link I need to get more information on the 
wireless link. Therefore, I want to enable the debugfs option of the ATH9k 
driver module (because just enabling the debug mode using 'modprobe 
ath9k_htc debug=0x' didn't work for me).

I think I will have to recompile the ath9k module and some related modules. 
As far as I understand all what I need for that is part of the backports 
project [1]. I have already used this on Android for another purpose and 
everything worked fine. BUT, I will need the kernel source for the 
compiling process! Where to get the source? (I used Roberts 
update_kernel.sh script to upgrade my kernel to 3.19)

Another possibility would be to compile a kernel and using make menuconfig 
to configure the modules. But therefore I would also need the kernel 
source. I really want to use Robert Nelsons version because I will also 
need to use DTBs for CAN. 

Can anyone help me out here? What would be better/easier? 

Thanks a lot in advance and best regards,
Marco

[1] https://www.kernel.org/pub/linux/kernel/projects/backports/

-- 
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] Can't make UART work with Python and AdaFruitBBB

[Cláudio B]

@palaniyappan

You can if you use the same protocol developed in BBB.



2015-02-14 8:14 GMT-02:00 :

> I have GPRS modem for PIC microcontroller. Can I used  same gprs modem for
> BBB?
>
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/-I_to80m9_Y/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Cláudio B.
Desenvolvimento de Software
Logmatch Produtos Eletrônicos LTDA

31 3476-8540

clau...@logmatch.com.br

Solução de qualidade para o controle de ponto em sua empresa.
Mensis  - Belo Horizonte


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