[beagleboard] Re: Will we lose access to BBB pins when LCD cape is connected?

[Terry Storm]

There are a bunch of options you can use, such as prototyping capes etc to 
get at the signals. The BBB is the first part in the stack of capes, and 
the LCD cape is designed to be the last cape in the stack. So if you want 
to access the extra pins, you need to get at them between the two.

The 7" from 4D Systems and the 7" from CircuitCo both allow you to access 
the extra pins.

If you want to use the 4", then have a look at something like 
this: http://tigal.com/product/2413

Lots of other options too. Sandwich that in between your BBB and your LCD 
Cape and access the pins that way.

Terry.

On Tuesday, 21 January 2014 18:10:56 UTC+13, Aswin wrote:
>
> Hi,
>
> I am searching for an LCD cape for Beaglebone Black and came across this 
> product: https://www.sparkfun.com/products/12085
>
> From the images provided on that page, it seems we lose physical access to 
> BBB GPIO pins once the two are connected together; LCD cape's male 
> connector mates with all the pins on BBB. If true, how do we make 
> connection with other peripherals in the system? For example, a 
> microcontroller.
>
> Please suggest an LCD cape where this issue doesn't come up.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[beagleboard] Re: problem booting android 4.2.2 on baglebone

[Vishveshwar]

On Monday, January 27, 2014 10:26:41 PM UTC+5:30, Mihir Jariwala wrote:
>
> I recently started working on baglebone. I followed the steps on 
>
>
> http://processors.wiki.ti.com/index.php/TI-Android-JB-4.2.2-DevKit-4.1.1_UserGuide
> &
>
> http://processors.wiki.ti.com/index.php/BeagleBone-Android-DevKit_Guide#Hardware_setup
>
> After establishing serial communication the window starts "" as 
> recommended. As instructed I insert the bootable sdmmc card into the 
> beaglebone. Android starts booting and in the end the log stops... snippet 
> of the log is as below. Now i dont know what i have to do. Please provide 
> some support regarding it. I am using ubantu 11.10 using VMware on windows7 
> 64bit
>
> log..
>
> root@android:/ # [3.365753] android_work: sent uevent 
> USB_STATE=CONNECTED
> [3.371520] android_work: sent uevent USB_STATE=DISCONNECTED   
>
> [3.379119] Disabling lock debugging due to kernel taint   
>
> [3.435455] android_work: sent uevent USB_STATE=CONNECTED   
>   
> [3.784362] warning: `rild' uses 32-bit capabilities (legacy support in 
> use)  
> [3.845520] android_work: sent uevent USB_STATE=DISCONNECTED   
>
> [3.890869] android_work: did not send uevent (0 0   (null))   
>
> [3.955291] android_work: sent uevent USB_STATE=CONNECTED   
>   
> [4.109863] android_work: sent uevent USB_STATE=DISCONNECTED   
>
> [4.141540] android_work: sent uevent USB_STATE=CONNECTED   
>   
> [4.147369] android_work: sent uevent USB_STATE=DISCONNECTED   
>
> [4.211578] android_work: sent uevent USB_STATE=CONNECTED   
>   
> [4.377655]  gadget: high-speed config #1: android 
>
> [4.397521] android_work: sent uevent USB_STATE=CONFIGURED 
>
> [   20.203216] request_suspend_state: wakeup (3->0) at 20170814787 
> (2000-01-01 00:23:56.3389)
> [   21.057922] net eth0: CPSW phy found : id is : 0x7c0f1 
>
> [   21.064208] PHY 0:01 not found 
>
> [   21.076110] ADDRCONF(NETDEV_UP): eth0: link is not ready   
>
> [   21.768341] acc_open   
>
> [   21.773101] acc_release 
>   
> [   25.053070] PHY: 0:00 - Link is Up - 100/Full   
>   
> [   25.069183] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready   
>   
> [   33.759277] init: sys_prop: permission denied uid:1003 
>  name:service.bootanim.exit  
>

Congratulations! Android booted up. If you did not attach a LCD cape, 
that's all you get.. a working console with shell prompt.
The shell prompt got lost in the kernel boot messages, but it is there. 
Press Enter key again and you should see it.

-Vishveshwar 

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[beagleboard] Re: Can't get BeagleSNES to work on BBB

[Scott Paul]

I'll keep an eye out for the update.  In the meantime, I bought a second, 
different controller and everything works now.  Connecting the controller 
has been a little spotty compared to the other one that the start and 
select buttons don't work on, but it works.  I cycled the power a couple 
times, plugged and unplugged it and it eventually worked.  Once it did work 
it seemed more consistently connected after a power cycle.  The other 
remote didn't have that issue.  Oh well.  It works.

I've only tried a few games quickly, but I like it.  For anyone else 
ordering through Amazon...

This is where I ordered the one that 
worked: 
http://www.amazon.com/gp/product/B0058FN036/ref=oh_details_o02_s00_i00?ie=UTF8&psc=1
Sold by *Hitgaming Video Games 
*

This is where I ordered the one that caused me 
problems: 
http://www.amazon.com/gp/product/B0034ZOAO0/ref=oh_details_o03_s00_i00?ie=UTF8&psc=1
Sold by *Hitgaming Video Games 
*

Good luck getting the right one :)

Anyways, thanks Andrew.  I also got the Android 4.2.2 running on the BBB. 
 Good work on that too!  That also worked after I tried imaging the disk 
from the Ubuntu machine.


On Sunday, January 26, 2014 4:02:54 PM UTC-5, Andrew Henderson wrote:
>
> Yes.  The front-end GUI does not look at that configuration file for 
> button mapping.  That is the configuration file for the SNES9X emulator. 
>  Part of my work for v0.5 is to pull button mappings from that file.  v0.5 
> should give you the following:
>
> - An additional VFAT partition that houses the config files, ROMs, and 
> images.  This way, you can pop the microSD card into your non-Linux PC and 
> add ROMs, edit files, etc.
> - XML for the games.cfg.  This is using the Expat XML parsing library. 
>  This will eliminate most of the common problems, I hope, like the config 
> file having to be just-so or DOS end-of-line characters messing things up, 
> etc.
> - Key mapping from the SNES9X emulator's config file so that you can do a 
> custom key mappings.
>
> I am a PhD student, and I've been working on a papers over the past few 
> months, so I haven't been working on BeagleSNES development as much as I 
> would like.  I'm still working on it, though, and I'll be getting a release 
> out as soon as I can.  Trust me, I don't want to answer mail after mail for 
> support when I can release a new version that addresses these issues 
> directly!
>
> Andrew
>  
>
> On Sunday, January 26, 2014 3:13:18 PM UTC-5, Scott Paul wrote:
>>
>> Hi Andrew.  Is there a short explanation for why I can't quickly edit the 
>> "*snes9x.conf.BBB*" file and change the lines 
>>
>>
>> *J00:B8 = Joypad1 SelectJ00:B9 = Joypad1 Start*
>>
>> to something like 
>>
>>
>> *J00:B6 = Joypad1 SelectJ00:B7 = Joypad1 Start*
>>
>> to effectively test different button mappings? I tried editing them and 
>> popping the card back in the BBB but it doesn't seem to do anything.  Does 
>> modifying that conf file require a rebuild to take effect?  
>>
>> When do you hope to release the v0.5?
>>
>>
>> On Friday, January 3, 2014 9:22:19 AM UTC-5, Andrew Henderson wrote:
>>>
>>> Hey Scott.  I have been away for the holidays and won't be back to my 
>>> office with my equipment until the start of next week.  You have everything 
>>> set up correctly, it seems.  The games.cfg looks OK, in any case.  The 
>>> problem is that the button numbers for the start and select are hardcoded 
>>> in the front-end GUI.  I have a better button mapping scheme on my dev list 
>>> for v0.5 of BeagleSNES, but I can't work on it and get another release out 
>>> until I am able to get back to my equipment.  The short answer is that you 
>>> will require a code change and recompile to get it working for your 
>>> particular controller.
>>>
>>> I have a big laundry list of things that I have been working on that I 
>>> want to get out for v0.5, and a few of the items have been delaying me in 
>>> getting the release out.  I may just have to bite the bullet and expedite 
>>> the more urgent items because a large number of people have received new 
>>> BBBs for the holidays and have been filling my inbox with all sorts of 
>>> issues regarding gamepads and button mappings.
>>>
>>> Good work on getting everything working as well as you have so far.  I 
>>> should write a book on how to develop the BBB into a standalone appliance 
>>> based on all of the feedback and reports that I have received from everyone 
>>> over the last six months...
>>>
>>> Andrew
>>>
>>>
>>> On Wednesday, January 1, 2014 6:23:41 PM UTC-5, Scott Paul wrote:

 So close...

 I had an old PC sitting around collecting dust so I formatted that to 
 Ubuntu 12.04.  I re-did everything from that machine.  Before I started, 
 when I plugged in the SD card that I had

[beagleboard] Heads up: Device tree files compiled with wrong address references?

[David M.]

>
> I ran into this last week when configuring an I2C RTC device, and I have 
> not seen this mentioned in the group.


Angstrom for the BBB, at least the most recent version, has a selection of 
device tree files, both in source and precompiled form.  I used them as a 
basis for my own Beagleboard NTPD device tree.  I've found an ambiguous 
address reference that tripped me up.

Consider this segment of a device tree for an I2C RTC device, such as the 
Dallas DS1307, or the DS3231 (packaged as the Chronodot, which I have).  
I've omitted most of it for clarity:


> fragment@1 {
> target = <&i2c2>;
>
> __overlay__ {
> /* shut up DTC warnings */
> #address-cells = <1>;
> #size-cells = <0>;
>
> /* DS1307 RTC module */
> rtc@68 {
> compatible = "dallas,ds1307";
> reg = <0x68>;
> };
> };
> }
>
 Note the rtc@68 address.  This is ambiguous.  The real address of this 
device is 0x68 in hex.  The DTC parser must interpret numeric values in a 
default decimal radix, unless it has a hex digit already in it;  another 
device I have is addressed as 3C, which is represented correctly.

My RTC was not being detected by the kernel.  The fix is simple:  always 
insert the 0x prefix for all addresses (represented in most databooks in 
hex);  the corrected reference is rtc@0x68.  My Chronodot was since 
detected by the kernel with no fuss.

I've "decompiled" the original binary device tree file 
(BB-BONE-RTC-00A0.dtbo) and it matches the source (BB-BONE-RTC-00A0.dts) as 
far as the address reference is concerned.

I believe this would affect all I2C devices represented in the device 
tree.  I haven't had the chance to scan the other device tree files.  I am 
running this on a Beaglebone White, but I have both species of Beaglebone 
(white and black) and they both are running the latest Angstrom so this 
problem appears to still exist.

I've attached a corrected version of the BB-BONE-RTC-00A0.dts file.

Regards,

Dave M.


-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
/*
* Copyright (C) 2013 Matt Ranostay 
*
* 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.
*/
/dts-v1/;
/plugin/;

/*
 * Pin assignments
 *
 * Module Connector
 * SCL -> P9.19
 * SDA <- P9.20
 * SQW/PPS <- P9.15
 *
 */

/ {
compatible = "ti,beaglebone", "ti,beaglebone-black";
part-number = "BB-BONE-RTC-01";
version = "00A0";

/* state the resources this cape uses */
exclusive-use =
/* the pin header uses */
"P9.15";/*gpio1_16 */


fragment@0 {
target = <&am33xx_pinmux>;
__overlay__ {
pps_pins: pinmux_pps_pins {
pinctrl-single,pins = <
0x040   0x27/* gpmc_a0.gpio1_16, 
INPUT | PULLDIS | MODE7 */
>;
};
};
};


fragment@1 {
target = <&i2c2>;

__overlay__ {
/* shut up DTC warnings */
#address-cells = <1>;
#size-cells = <0>;

/* DS1307 RTC module */
rtc@0x68 {
compatible = "dallas,ds1307";
reg = <0x68>;
};
};
};

fragment@2 {
target = <&ocp>;
__overlay__ {
pps {
compatible = "pps-gpio";
status = "okay";
pinctrl-names = "default";
pinctrl-0 = <&pps_pins>;

gpios = <&gpio2 16 0>;
assert-falling-edge;
};
};
};
};

Re: [beagleboard] machinekit on BBB - how to force enabled HDMI hardware from cmdline

[doog]

I had looked at it and overlooked what was the problem but you asking and 
my copy/paste made me realize I'd cat'ed it onto the capemgr.disable 
mesg with a comma instead of separating it. It now works. Thanks for slap 
in the back of the head.

Doug

On Tuesday, January 28, 2014 5:29:22 PM UTC-8, Charles Steinkuehler wrote:
>
> On 1/28/2014 6:57 PM, doog wrote: 
> > I'm getting going with LinuxCNC Machinekit on BBB but my first hiccup is 
> > that I can't get HDMI hardware enabled. I have an HDMI-DVI cable and for 
> > whatever reason the hardware has to be told to turn on. With Angstrom I 
> > pass "video=HDMI-A-1:e" on optargs in uEnv.txt but default Debian in 
> > Machinekit doesn't do it. 
> > 
> > is there something I can do to force it on/enabled from the command 
> line? 
> >  I've tried shelling in with ssh -X then doing xrandr :0.0 --output 
> HDMI1 
> > --auto but it didn't work. 
> > I'm checking /sys/class/drm/card0-HDMI-A-1/enabled and when booting 
> > Angstrom without a display connected it states "enabled" as it should. 
> > Booting Machinekit it states "disabled". 
>
> First, are you sure the option is being passed to the kernel?  What does 
> "cat /proc/cmdline" return? 
>
> Second, have you tried the 'e' flag while also specifying a resolution? 
>  Try something like: 
>
> kms_force_mode=video=HDMI-A-1:1024x768@60e 
>
> ...in /boot/uboot/uEnv.txt. 
>
> -- 
> Charles Steinkuehler 
> cha...@steinkuehler.net  
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [beagleboard] machinekit on BBB - how to force enabled HDMI hardware from cmdline

[Charles Steinkuehler]

On 1/28/2014 6:57 PM, doog wrote:
> I'm getting going with LinuxCNC Machinekit on BBB but my first hiccup is 
> that I can't get HDMI hardware enabled. I have an HDMI-DVI cable and for 
> whatever reason the hardware has to be told to turn on. With Angstrom I 
> pass "video=HDMI-A-1:e" on optargs in uEnv.txt but default Debian in 
> Machinekit doesn't do it.
> 
> is there something I can do to force it on/enabled from the command line? 
>  I've tried shelling in with ssh -X then doing xrandr :0.0 --output HDMI1 
> --auto but it didn't work.
> I'm checking /sys/class/drm/card0-HDMI-A-1/enabled and when booting 
> Angstrom without a display connected it states "enabled" as it should. 
> Booting Machinekit it states "disabled".

First, are you sure the option is being passed to the kernel?  What does
"cat /proc/cmdline" return?

Second, have you tried the 'e' flag while also specifying a resolution?
 Try something like:

kms_force_mode=video=HDMI-A-1:1024x768@60e

...in /boot/uboot/uEnv.txt.

-- 
Charles Steinkuehler
char...@steinkuehler.net

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[beagleboard] machinekit on BBB - how to force enabled HDMI hardware from cmdline

[doog]

I'm getting going with LinuxCNC Machinekit on BBB but my first hiccup is 
that I can't get HDMI hardware enabled. I have an HDMI-DVI cable and for 
whatever reason the hardware has to be told to turn on. With Angstrom I 
pass "video=HDMI-A-1:e" on optargs in uEnv.txt but default Debian in 
Machinekit doesn't do it.

is there something I can do to force it on/enabled from the command line? 
 I've tried shelling in with ssh -X then doing xrandr :0.0 --output HDMI1 
--auto but it didn't work.
I'm checking /sys/class/drm/card0-HDMI-A-1/enabled and when booting 
Angstrom without a display connected it states "enabled" as it should. 
Booting Machinekit it states "disabled".

any ideas?  Thanks.

Doug

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [beagleboard] Power Requirements for Beaglebone black and LCD Display(4DCAPE-43)

[Mahendra Gunawardena]

I was able to power the 4 inch 4Dsystem display with a USB cable. I guess
the 4D system 4inch LCD display requires less current.
Thanks


On Wed, Jan 15, 2014 at 2:58 PM, Mahendra Gunawardena <
mahengunaward...@gmail.com> wrote:

> Thanks for the feed back
>
>
> On Wed, Jan 15, 2014 at 12:47 PM, Philip Polstra wrote:
>
>> No chance USB will work.  Get 2A adapter.
>> On Jan 15, 2014 11:41 AM, "Mahendra Gunawardena" <
>> mahengunaward...@gmail.com> wrote:
>>
>>> Hello all,
>>>
>>> Does anyone have any idea of power requirements for BBB & 4 inch LCD
>>> display (4DCAPE-43) combination?
>>>
>>> Note: I recently purchased a BBB and the display is on its way.
>>>
>>>1. Can the USB power both BBB and 4 inch LCD Display?
>>>2. If the 5V supply is need what is minimum require current? A good
>>>guess is sufficient.
>>>
>>> Base on little research in TPS65217C USB and AC lines are connect to
>>> SYS.
>>>
>>> Your thought is appreciated.
>>>
>>> --
>>> For more options, visit http://beagleboard.org/discuss
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "BeagleBoard" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to beagleboard+unsubscr...@googlegroups.com.
>>>
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>
>>  --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to a topic in the
>> Google Groups "BeagleBoard" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/beagleboard/lA-oDIiI4Bk/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/groups/opt_out.
>>
>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [beagleboard] Beaglebone Black backordered everywhere

[Brandon I]

At arrow, I just asked, and they have an old A53 datasheet up, so the guy 
told me it was a rev A5B. Are the arrow boards A6A?

On Monday, January 27, 2014 4:38:26 PM UTC-8, smith.wi...@gmail.com wrote:
>
> On Monday, January 27, 2014 2:18:04 PM UTC-5, Gerald wrote:
>>
>> Arrow is showing 500 boards in stock. We have people buying boards to go 
>> into products, something we cannot plan for. When will that be fixed? I 
>> have no idea. We cannot plan for something we don't know about. 
>>
>>
> Thank you!  I've had them backorderd at both Digikey and Newark for weeks 
> now.  Arrow have already shipped my order.  They still have 436 in stock.
>
>  
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[beagleboard] USB Label printer trouble with beaglebone black.

[kevin_woolbright]

I got a USB label Printer working with ubuntu but can't get it to work with 
a stock beaglebone black.  I have loaded CUPS and have a .PPD file but no 
luck.  Can't seem to figure out how to add a new printer.
 
Can any one please point me in the right direction?
 
Thank you for your time.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [beagleboard] BeagleBone Black P8 & P9 physical location on board

[r . butts]

Perfect!
 
Thanks Guys!

On Tuesday, January 28, 2014 3:16:04 PM UTC-5, Charles Steinkuehler wrote:

> On 1/28/2014 2:06 PM, r.b...@mykoolride.com  wrote: 
> > I'm using the BeagleBone Black as the backbone of a graphical display 
> > exercise equipment design.  I'm designing an interface board to 
> interface 
> > with the peripherals of my design; the lcd display, exercise 
> equipment... 
> >   
> > I'd like to make my interface board plug directly into the P8 and P9 
> > connectors much like the ready-made breadboard found here: 
> > http://elinux.org/CircuitCo:BeagleBone_Breadboard#Hardware_Files 
> >   
> > My problem is that I can not find the relative location of those 
> connectors 
> > on the board.  Does anyone know of such a drawing or the location of the 
> P8 
> > and P9 connectors? 
>
> It's in the system reference manual (SRM): 
>
> http://beagleboard.org/hardware/design 
>
> See Chapter 7 "Cape Board Support", specifically section 7.6.1 "Standard 
> Cape Size". 
>
> You can also find libraries for common design tools like Eagle and KiCad 
> with PCB layouts (board outline and connectors) already done for you. 
>
> -- 
> Charles Steinkuehler 
> cha...@steinkuehler.net  
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [beagleboard] BeagleBone Black P8 & P9 physical location on board

[Eric Fort]

both the sparkfun and adafruit libraries for eagle have a beaglebone
cape as part in the library.  due to issues of orientation I find the
sparkfun library part easier to use in the free version of eagle but
that's just preference.

Eric

On Tue, Jan 28, 2014 at 12:16 PM, Charles Steinkuehler
 wrote:
> On 1/28/2014 2:06 PM, r.bu...@mykoolride.com wrote:
>> I'm using the BeagleBone Black as the backbone of a graphical display
>> exercise equipment design.  I'm designing an interface board to interface
>> with the peripherals of my design; the lcd display, exercise equipment...
>>
>> I'd like to make my interface board plug directly into the P8 and P9
>> connectors much like the ready-made breadboard found here:
>> http://elinux.org/CircuitCo:BeagleBone_Breadboard#Hardware_Files
>>
>> My problem is that I can not find the relative location of those connectors
>> on the board.  Does anyone know of such a drawing or the location of the P8
>> and P9 connectors?
>
> It's in the system reference manual (SRM):
>
> http://beagleboard.org/hardware/design
>
> See Chapter 7 "Cape Board Support", specifically section 7.6.1 "Standard
> Cape Size".
>
> You can also find libraries for common design tools like Eagle and KiCad
> with PCB layouts (board outline and connectors) already done for you.
>
> --
> Charles Steinkuehler
> char...@steinkuehler.net
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups 
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [beagleboard] Automotive Cape

[marcmltd]

We are in the final process of layout and looking to get the first versions 
manufactured in the next 4 weeks.
The initial run will be low volume as we are using it for developing our 
product.  If there is enough interest then we would produce in volume.
 
We have been trying to find a way to get the information out on twitter but 
as we are a startup we have a very small following.
 
If anyone fancies tweeting us or re-tweeting us we are @aSanCloud 
 
There are going to be regular updates with the progress of the board and 
some pictures when we get the boards manufactured/assembled.

On Tuesday, January 28, 2014 4:00:45 PM UTC, Mickae1 wrote:

> By curiousity, when are you planning to release this cap ? :p
>
>
> On Tue, Jan 28, 2014 at 4:28 PM, > wrote:
>
>> Hi Eric,
>> Yes adding the compass as well could easily be done as we are already 
>> using the MPU-6050 and it is a compatible replacement.
>>
>> The mini-PCI-e is the socket that a 3G/LTE card can be attached to, the 
>> interface to the beagle is USB and has the SIM interface as well to make 
>> things easy
>> A GPS 3v3 LNA booster is also planned to allow the use of GPS antennas 
>> with LNA.
>>
>> Having the mini-PCIe enables the use of any card the user chooses.  We 
>> have used SierraWireless and Huawei modules for the 3G uplink.
>>
>> Marc
>>
>> On Monday, January 27, 2014 7:42:08 PM UTC, Eric wrote: 
>>>
>>> adding compass functionality would add very little to the cost and be 
>>> quite useful.  It's the difference between usung an invensense 
>>> MPU-6050 6 axis or an MPU-9150 9 axis sensor.  an altimeter would be 
>>> nice as well.  I'd be interested in just how you intend to provide 
>>> mini-PCI-e on the bone but I don't see how it's needed for 3G-LTE or 
>>> GPS interfacing to the bone.  most of those modules are serially 
>>> controlled and where sound comes into play the bone has i2s and audio 
>>> serial port abilities that can either drive a dac/listen to an adc or 
>>> even speak directly to some modules over asp/i2s. 
>>>
>>> Eric 
>>>
>>> On Mon, Jan 27, 2014 at 9:37 AM,   wrote: 
>>> > Hello, 
>>> > I am part of a startup that has developed a system that is used to 
>>> analyse 
>>> > vehicles in they way they are driven and also track the journeys. 
>>> > 
>>> > We are producing a cape to use for development of our next version and 
>>> > thinking  about offering it for sale to the open source community. 
>>>  The 
>>> > basics of the interface are: 
>>> > CAN 
>>> > ODBII via SN1110 OBD to UART Interpreter 
>>> > Mini-PCIe for 3G-LTE/GPS card 
>>> > 6 axis accel and gyro 
>>> > RTC 
>>> > USB expansion for WiFi dongle (possibly supporting 802.11p) 
>>> > Bi directional GPIO for vehicle signals (Ignition in GPIO_0 wakeup 
>>> domain) 
>>> > 
>>> > And maybe some more. 
>>> > 
>>> > Are there any requests/requirements that you think might be of benefit 
>>> to 
>>> > make the cape more usable ? 
>>> > 
>>> > Any feedback appreciated. 
>>> > 
>>> > Kind Regards 
>>> > Marc 
>>> > 
>>> > -- 
>>> > For more options, visit http://beagleboard.org/discuss 
>>> > --- 
>>> > You received this message because you are subscribed to the Google 
>>> Groups 
>>> > "BeagleBoard" group. 
>>> > To unsubscribe from this group and stop receiving emails from it, send 
>>> an 
>>> > email to beagleboard...@googlegroups.com. 
>>> > For more options, visit https://groups.google.com/groups/opt_out. 
>>>
>> -- 
>> For more options, visit http://beagleboard.org/discuss
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to beagleboard...@googlegroups.com .
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [beagleboard] BeagleBone Black P8 & P9 physical location on board

[Charles Steinkuehler]

On 1/28/2014 2:06 PM, r.bu...@mykoolride.com wrote:
> I'm using the BeagleBone Black as the backbone of a graphical display 
> exercise equipment design.  I'm designing an interface board to interface 
> with the peripherals of my design; the lcd display, exercise equipment...
>  
> I'd like to make my interface board plug directly into the P8 and P9 
> connectors much like the ready-made breadboard found here:
> http://elinux.org/CircuitCo:BeagleBone_Breadboard#Hardware_Files
>  
> My problem is that I can not find the relative location of those connectors 
> on the board.  Does anyone know of such a drawing or the location of the P8 
> and P9 connectors?

It's in the system reference manual (SRM):

http://beagleboard.org/hardware/design

See Chapter 7 "Cape Board Support", specifically section 7.6.1 "Standard
Cape Size".

You can also find libraries for common design tools like Eagle and KiCad
with PCB layouts (board outline and connectors) already done for you.

-- 
Charles Steinkuehler
char...@steinkuehler.net

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[beagleboard] Re: BBB Ubuntu HDMI Red and Blue Inverted in X Window

[sstuart . vigil]

Worked great, thanks!

On Saturday, January 25, 2014 9:06:25 AM UTC-8, mich...@o2.pl wrote:
>
> Switch to 16 bit color wating for the rock solid fix.: add 
> /etc/X11/xorg.conf
>
>  Section "Screen"
>  Identifier"Default Screen"
>  Monitor"Configured Monitor"
>  Device"Configured Video Device"
>  DefaultDepth16
>  SubSection "Display"
>  Modes"1280x1024" "1280x960" "1152x864" "1024x768" "832x624" 
> "800x600" "720x400" "640x480"
>  EndSubSection
>  EndSection
>
>
>
>
>
> W dniu środa, 15 stycznia 2014 23:39:01 UTC+1 użytkownik 
> sstuar...@gmail.com napisał:
>>
>> Hi,
>>
>> I've got a BBB running Ubuntu 13.04 on the eMMC connected to an HDMI 
>> monitor where I want to display a webpage hosted on the BBB. I'm do this by 
>> starting an X Server and then launching a broswer:
>>
>> >xinit &
>> >DISPLAY=:0 chromium-browser
>>
>> The page is displayed, but anything that should be blue is red, and 
>> everything red is blue. Green stays the same. If I use a terminal on the 
>> HDMI display by plugging a keyboard into the BBB the colours appear as they 
>> should, but I can't get anything in X to look right.
>>
>> I've tried Ubuntu 13.10 on another BBB and it had the same problem. I 
>> also tried the default Angstrom image and the desktop looked normal on 
>> that. I've tried all the supported resolutions for this monitor that I got 
>> from "xrandr -q" and they all had the same issues. I also tried another 
>> model monitor with the same issue. I tried Firefox as well and had the same 
>> issue.
>>
>> parse-edid output:
>> Section "Monitor"
>> # Block type: 2:0 3:fd
>> # Block type: 2:0 3:fc
>> Identifier "HP 23tm"
>> VendorName "HWP"
>> ModelName "HP 23tm"
>> # Block type: 2:0 3:fd
>> HorizSync 24-94
>> VertRefresh 50-76
>> # Max dot clock (video bandwidth) 170 MHz
>> # Block type: 2:0 3:fc
>> # Block type: 2:0 3:ff
>> # DPMS capabilities: Active off:yes  Suspend:yes  Standby:yes
>>
>> Mode"1920x1080" # vfreq 60.000Hz, hfreq 67.500kHz
>> DotClock148.50
>> HTimings1920 2008 2052 2200
>> VTimings1080 1084 1089 1125
>> Flags   "+HSync" "+VSync"
>> EndMode
>> # Block type: 2:0 3:fd
>> # Block type: 2:0 3:fc
>> # Block type: 2:0 3:ff
>> EndSection
>>
>> fbset output:
>> mode "1280x720"
>> geometry 1280 720 1280 720 16
>> timings 0 0 0 0 0 0 0
>> accel true
>> rgba 5/11,6/5,5/0,0/0
>> endmode
>>
>> Seems this has happened to 
>> others:https://groups.google.com/forum/?fromgroups=#!searchin/beagleboard/bbb$20colors/beagleboard/l3VogAknB5Q/PBCHhZHzLeoJ
>>
>> Any ideas on how to fix this, or suggestions on how to display a webpage 
>> on the HDMI without using X Windows?
>>
>> Thanks,
>>
>> Sean
>>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [beagleboard] BeagleBone Black P8 & P9 physical location on board

[Gerald Coley]

Look in the System Reference Manual. Section 8.7.

http://www.elinux.org/Beagleboard:BeagleBoneBlack#LATEST_PRODUCTION_FILES_.28A6A.29


Gerald



On Tue, Jan 28, 2014 at 2:06 PM,  wrote:

> I'm using the BeagleBone Black as the backbone of a graphical display
> exercise equipment design.  I'm designing an interface board to interface
> with the peripherals of my design; the lcd display, exercise equipment...
>
> I'd like to make my interface board plug directly into the P8 and P9
> connectors much like the ready-made breadboard found here:
> http://elinux.org/CircuitCo:BeagleBone_Breadboard#Hardware_Files
>
> My problem is that I can not find the relative location of those
> connectors on the board.  Does anyone know of such a drawing or the
> location of the P8 and P9 connectors?
>
> Thanks!
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[beagleboard] BeagleBone Black P8 & P9 physical location on board

[r . butts]

I'm using the BeagleBone Black as the backbone of a graphical display 
exercise equipment design.  I'm designing an interface board to interface 
with the peripherals of my design; the lcd display, exercise equipment...
 
I'd like to make my interface board plug directly into the P8 and P9 
connectors much like the ready-made breadboard found here:
http://elinux.org/CircuitCo:BeagleBone_Breadboard#Hardware_Files
 
My problem is that I can not find the relative location of those connectors 
on the board.  Does anyone know of such a drawing or the location of the P8 
and P9 connectors?
 
Thanks!

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [beagleboard] Re: SPI input is always 0 with BeagleBoneBlack Anstrom images

[Andrew Wagner]

Hello Sam,

We never did get SPI working though the device file in Angstrom and ended
up just bitbanging the same pins as GPIO.  Our bitbanged clock signal is
wack, but the spi slave we're reading from doesn't seem to mind.  Unless
someone has submitted some changes to the spi driver in between what I was
using and the most recent kernel, I'd recommend you just try bitbanging.

You might try changing the direction of the clock pin to be the opposite of
what it should; I think we were at least able to get a clock out, but
couldn't read the data correctly.

I recently spent some time trying out bare metal, but I didn't even manage
to get an LED to blink with TI starterware (BBB is not officially supported
yet).

Just today I was able to boot into the most recent ubuntu 12.04 image from
armhf; I had some stupid hardware problems where the hdmi plug was too big
and I could either connect to a monitor or a keyboard but not both :)  I
will probably not want to mess with the BBB we're bitbanging SPI on again,
but if I do, I'll let you know.

Cheers,
Andrew


On Tue, Jan 28, 2014 at 8:19 AM,  wrote:

> Have you had any luck getting the spi0 clock working on the BBB (rev A6)
> using Ubuntu (3.8.13-bone30) ? I've done all the following
> 1) Added "capemgr.enable_partno=BB-SPIDEV0" to uEnv.txt in boot/uboot .
> This is the right uEnv.txt file as its in the FAT boot portion.
> 2) checking with "cat /sys/devices/bone_capemgr.9/slots"  I see the SPIDEV
> override
> 3) checking "ls -al /dev/spi*" I get the expected "/dev/spidev1.0 and
> /dev/spidev1.0" files
> 4) I added Adafruit_BB library and the CS pin (P9_17) can be toggled from
> here
> 5) Shorting pins 21 and 18 I can see data transfer so internally the spi
> clock works as expected.
>
> However connected SPI_CLK(P9_22) to a logic analyzer I see no clock
> signal! I am certain the logic analyzer is ok since with hdmi enabled I can
> see clock signals on pins 25 and 31. I don't know why I am not getting a
> clock signal for SPI0. I just get the clock 'low'. The same thing happens
> when I disable hdmi and enable spidev1 instead; I get no clock signal on
> SPI1 clock  (pin 31).
>
> Any suggestions on what I may be missing?
>
> Le mardi 1 octobre 2013 10:55:57 UTC-5, lper...@fiu.edu a écrit :
>
>> Rafael, Would you mind posting you DTS file??? I have been trying to make
>> the SPI clocl work, but I haven't had any luck!
>>
>> Thank you,
>>
>> Laura
>>
>> El lunes, 16 de septiembre de 2013 07:28:18 UTC-4, Rafael Fiebig-Bindner
>> escribió:
>>>
>>> Just for clearence: Deactivate Pullup/-down is only needed at clock.
>>> Am Montag, 16. September 2013 11:22:43 UTC+2 schrieb Andrew Wagner:
>>>
 Hi Arlen,

 The coverage for setup up a device overlay tree here is pretty good:

 http://learn.adafruit.com/introduction-to-the-
 beaglebone-black-device-tree/overview

 With that and glancing at some other samples, we were able to get
 writing to work.  We did not get reading working in time for our
 deadline, and resorted to bitbanging from userspace code.   I have not
 had a chance to try Rafael's advice (clock as input, deactivate pull
 up / pull down).

 Cheers,
 Andrew

>>>  --
> 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/NADsTC5Ro-I/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/groups/opt_out.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [beagleboard] Re: Volumio - Audiophile Music Player on Beaglebone Black

[vkarmarkar]

Can you please clarify how to modify uEnv.txt so that the HDMI port 
(including music) does not "blank" after 10 minutes?

On Tuesday, December 31, 2013 10:04:52 PM UTC-5, Gerald wrote:
>
> It would need to go out the HDMI port. HDMI has and audio 
> channel embedded in it.
>
> Gerald
>
>
>
> On Tue, Dec 31, 2013 at 6:46 PM, James Yeo 
> > wrote:
>
>> I'm a bit unclear - the BBB doesn't have an audio jack, so does this 
>> stream the audio, or...? Sorry if I'm being dense.
>>
>>
>> On Sunday, December 15, 2013 7:38:47 PM UTC-6, Michelangelo Guarise wrote:
>>
>>> Hi Beagleboard folks!!!
>>> I'm really glad to announce that Volumio  has been 
>>> released!
>>>
>>> Volumio is the porting of the RaspyFi distro, which you may have seen on 
>>> Raspberry Pi. But what does Volumio??
>>>
>>> Volumio will turn your BeagleBone Black into an headless music player. 
>>> Just connect the tiny Beagle to your home Network and to a DAC. You will 
>>> then be able to control the music playback with your phone, tablet or PC. 
>>> Wirelessly! 
>>>
>>> Volumio has 2 main goals: to sound amazingly good and to be easy and 
>>> confortable to use. 
>>>
>>> Just download it, flash to SD Card, hit the user button and you're 
>>> ready. You can then grab your tunes from a NAS (Samba or NFS), from 
>>> External Drives (a powered hub is suggested) or listen to your favourite 
>>> Web Radios.
>>>
>>> You can also use it as an Airport receiver to stream your tunes from 
>>> compatible devices! Last but not least, with an Android app you can 
>>> configure several Volumio powered beagles to play simoultaneously to obtain 
>>> multiroom audio! 
>>>
>>> This project comes with tons of passion and love for music. And thanks 
>>> to Beagleboard for giving such an amazing board to work with. The 
>>> performance on Beagleboard Black are really exciting! 
>>>
>>> CURRENT FEATURES:
>>>
>>> -Ready to play: flash it and you're ready 
>>> -Audiophile Quality: bit perfect playback
>>> -FLAC, WAV, MP3, AAC, ALAC, PLS support
>>> -Music libraries on Samba, NFS and USB drives
>>> -Webradios support out of the box
>>> -Control it via integrated Webui with PC, Smartphone, Tablet
>>> -Airplay capability
>>> -Ramplay Support 
>>> -DSD Native Playback
>>> -Multiroom Playback via Android App
>>> -Output playback device Selection
>>> -Audio out via HDMI, USB, Analog Jack, S/PDIF, I2S (depends on platform)
>>> -Compatible with all UAC2 compliant USB DACs
>>> -Wireless Network configuration 
>>> -Various resampling options, up to 32bit/384khrtz
>>>
>>> You can grab it at volumio.org
>>>
>>> Very eager to know what you guys think of it! 
>>>
>>  -- 
>> For more options, visit http://beagleboard.org/discuss
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to beagleboard...@googlegroups.com .
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[beagleboard] Re: BBB more reliable than Raspberry Pi - SD card corruption?

[kyle]

Cleaver!   As long as you are not controlling power to other things that is 
extremely cool.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[beagleboard] Re: Workmanship?

[David Anders]

Paul:

all of the surface mounted components are done with pick-n-place machine so 
they are usually very accurate, however all boards are inspected with 
"Automated Optical Inspection". you can see the process here 
http://youtu.be/FcqQvH41OR4 . with this in mind the inspection process is 
programmed in using a "golden board", but there are circumstances which 
might cause a false positive acceptance on the boards. we inspected 
approximately 500 boards by hand for this specific issues and didn't find 
any duplication of this assembly failure, however we are adding an 
additional check in the the AOI for this IC to make sure it is applied 
properly. 

we will be happy to exchange you board at not cost to you. please contact 
r...@circuitco.com to initiate the process.

thanks
Dave 

On Monday, January 27, 2014 8:38:04 PM UTC-6, Paul O'Connor wrote:
>
> I got a Beaglebone Black from Adafruit Industries which had some poor 
> quality soldering -- see my post at 
> http://www.adafruit.com/forums/viewtopic.php?f=49&t=48935
> for details.
> Anyone else have problem like 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/groups/opt_out.

[beagleboard] Re: BBB more reliable than Raspberry Pi - SD card corruption?

[Fredrik Olofsson]

here's how i solved it using a single pushbutton to safely turn on and off 
the bbb...
https://github.com/redFrik/udk10-Embedded_Systems/tree/master/udk140123#--start-stop-button
comments welcome.
_f

On Tuesday, January 28, 2014 5:33:14 PM UTC+1, ky...@cranehome.info wrote:
>
> I'm working on a PCB now to mate with some software to allow the user to 
> press a button, which will send a long GPIO signal to the ARM system.  A 
> daemon process monitors that GPIO and does an orderly shutdown when it goes 
> low.   The daemon also sets another GPIO high as it begins to shutdown.   
> When that line falls low again after the board powers down then the 
> external power switch cuts the power completely.  This was designed to plug 
> into my own power distribution board for a robot.
>
> Might be not-to-difficult to make up a carrier board for that PCB that 
> just feeds the BBB (or a RaspPi) with a barrel connector and a two-pin 
> cable.  If the prototypes function right I could send you one.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [beagleboard] Re: BBB more reliable than Raspberry Pi - SD card corruption?

[David Goodenough]

On Tuesday 28 January 2014 06:52:00 k...@cranehome.info wrote:
> Is that the case now with your Pi implementation?   No proper shutdown?
> 
> The EMMC is subject to FS corruption from improper shutdown same as any
> media.  In general I try to keep the FS utilization to under 60 to 70%.
>  Give the thing lots of room to wear-level, especially with an OS that
> likes to write crap to disk constantly.
The other thing to try for any partition that you need to write to, is to
use a file system that is designed for use on such media.  There are several
but you would need to see which fitted your needs.

David

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [beagleboard] Re: Attention if order LVDS-Board from chalk-elec!!!

[klimets]

Hello guys, 

My name is Yuri, I'm CTO of ZetaOri Technologies - the parent company of 
ChalkElec. Maxim sent to me link to this topic, that's how I know about 
these problems with supply and come here. ChalkElec has own director, and 
they operate independently from us since last year, but still have to 
report to us monthly, and we can take control of company operations. Based 
on what I read here, I see that situation is really bad and we should do 
something immediately. I will try to book tickets to Malaysia to go there 
and check whats happening right in place. Will provide update in couple 
days. 

Meantime, please send your complaints directly to my email. I have no idea 
how many customers are awaiting for shipping, so I will appreciate if you 
can briefly state just important information - your full name, order #, 
when order has been placed, and which email you did tried to contact. 
Please, state "ChalkElec order# XXX" as email subject. 

I apologize for all delays, silence, and any inconvenience involved. 
Please, give me couple days to reach Malaysia, then I will try to improve 
situation.

Yuri.  

On Tuesday, January 28, 2014 10:07:42 AM UTC+4, lisarden wrote:
>
> Hey guys!
>
> I know the director of Chalk-elec in person and gonna report about 
> problems to him immediately.
>
> They are good people. Don't blame them earlier. It is not that easy to 
> manufacture displays
> 27 Янв 2014 г. 23:47 пользователь "John Syn" > 
> написал:
>
>> I just got an e-mail from Andrew Lim of Chalkboard Electronics with a link
>> to the USPS tracking website which shows my package is in Los Angeles. I
>> had originally used the Malasian Post tracking website for a RR..MY
>> tracking number which showed nothing, but entering this tracking number
>> into USPS show my package was shipped. BTW, I did enter a complaint with
>> PayPal and perhaps that is why my package is on its way.
>>
>> Regards,
>> John
>>
>>
>>
>>
>> On 1/25/14, 3:58 AM, "Michael Eitel" > 
>> wrote:
>>
>> >Am Freitag, 24. Januar 2014 22:04:05 UTC+1 schrieb john3909:
>> >> From:  
>> >> Reply-To:  
>> >> Date:  Friday, January 24, 2014 at 9:27 AM
>> >> To:  
>> >> Cc:  , 
>> >> Subject:  [beagleboard] Re: Attention if order LVDS-Board from
>> >>chalk-elec!!!
>> >>
>> >>
>> >>
>> >> Here the same... No reply, No cash back, nothing... Bad company
>> >> I ordered the HDMI to LVDS convertor Nov 30 and I haven¹t received it
>> >>either.  Sent me shipping details Jan 16 with a tracking number for
>> >>Malaysia Post, but looks like it is fake.
>> >>
>> >>
>> >> Le dimanche 28 juillet 2013 17:23:43 UTC+2, asso.a...@gmail.com a 
>> écrit
>> >>:I ordered the screen over a month ago and the money were sent the same
>> >>day with paypal. After 3 emails they answerd me and said they will send
>> >>it out within one week. 2 weeks later and I stil havent received the
>> >>screen. Now a month later and no screen or money back or anything else.
>> >> DO NOT RECOMEND ever buying anything from them.
>> >>
>> >> Den lördagen den 28:e januari 2012 kl. 09:59:00 UTC+1 skrev
>> >>robo:attention if you like to order LVDS -Board on
>> >>
>> >> www.chalk-elec.com
>> >> this company is very dubios !!
>> >>
>> >> details:
>> >>
>> >> I ordered on 28.December and payed via paypal
>> >>
>> >> I ordered with extra cost "DHL EXPRESS"
>> >>
>> >>
>> >> in 2.week in january i received nothing.
>> >>
>> >> i wrote some mails , and always the answer: is sended,
>> >>
>> >> i ask for the tracking number . :
>> >>
>> >> today i received the mail with the tracking number bat :
>> >>
>> >>
>> >> i called the DHL.
>> >>
>> >> 1. this is not a DHL - Package !!
>> >>
>> >> 2. It is a Number for a german Post -Package !
>> >>
>> >>
>> >> I called the German Post:
>> >>
>> >> 1.this Number can not be find in the System
>> >>
>> >> 2. this Number is not Express Number , Express-Number begin not with
>> >>
>> >> "R" , begin with "E"
>> >>
>> >> 3.normally at the End of the Number is source - Country:
>> >>
>> >> on this number is DE !!! (source Germany ) not MY(Malaysia)
>> >>
>> >>
>> >> it is very dubios company ...
>> >>
>> >> I booked my mony back today, i develop it by self , i think it is
>> >>
>> >> faster
>> >>
>> >> regards
>> >>
>> >> robo
>> >>
>> >>
>> >> --
>> >>
>> >> For more options, visit http://beagleboard.org/discuss
>> >>
>> >> ---
>> >>
>> >> You received this message because you are subscribed to the Google
>> >>Groups "BeagleBoard" group.
>> >>
>> >> To unsubscribe from this group and stop receiving emails from it, send
>> >>an email to beagleboard...@googlegroups.com.
>> >>
>> >> For more options, visit https://groups.google.com/groups/opt_out.
>> >
>> >Hi
>> >
>> >I'm not surprised. They do not answer on my mails neither.
>> >Having problems with non running 10" lcd set.  I invested in a brick!!!
>> >Mike
>> >
>> >--
>> >For more options, visit http://beagleboard.org/discuss
>> >---
>> >You received this message because you are subscribed to the Google Groups
>> >"B

Re: [beagleboard] Re: SPI input is always 0 with BeagleBoneBlack Anstrom images

[samridhak]

Have you had any luck getting the spi0 clock working on the BBB (rev A6) 
using Ubuntu (3.8.13-bone30) ? I've done all the following
1) Added "capemgr.enable_partno=BB-SPIDEV0" to uEnv.txt in boot/uboot . 
This is the right uEnv.txt file as its in the FAT boot portion.
2) checking with "cat /sys/devices/bone_capemgr.9/slots"  I see the SPIDEV 
override
3) checking "ls -al /dev/spi*" I get the expected "/dev/spidev1.0 and 
/dev/spidev1.0" files
4) I added Adafruit_BB library and the CS pin (P9_17) can be toggled from 
here
5) Shorting pins 21 and 18 I can see data transfer so internally the spi 
clock works as expected.

However connected SPI_CLK(P9_22) to a logic analyzer I see no clock signal! 
I am certain the logic analyzer is ok since with hdmi enabled I can see 
clock signals on pins 25 and 31. I don't know why I am not getting a clock 
signal for SPI0. I just get the clock 'low'. The same thing happens when I 
disable hdmi and enable spidev1 instead; I get no clock signal on SPI1 
clock  (pin 31). 

Any suggestions on what I may be missing? 

Le mardi 1 octobre 2013 10:55:57 UTC-5, lper...@fiu.edu a écrit :
>
> Rafael, Would you mind posting you DTS file??? I have been trying to make 
> the SPI clocl work, but I haven't had any luck!
>
> Thank you, 
>
> Laura
>
> El lunes, 16 de septiembre de 2013 07:28:18 UTC-4, Rafael Fiebig-Bindner 
> escribió:
>>
>> Just for clearence: Deactivate Pullup/-down is only needed at clock. 
>> Am Montag, 16. September 2013 11:22:43 UTC+2 schrieb Andrew Wagner:
>>
>>> Hi Arlen, 
>>>
>>> The coverage for setup up a device overlay tree here is pretty good: 
>>>
>>>
>>> http://learn.adafruit.com/introduction-to-the-beaglebone-black-device-tree/overview
>>>  
>>>
>>> With that and glancing at some other samples, we were able to get 
>>> writing to work.  We did not get reading working in time for our 
>>> deadline, and resorted to bitbanging from userspace code.   I have not 
>>> had a chance to try Rafael's advice (clock as input, deactivate pull 
>>> up / pull down). 
>>>
>>> Cheers, 
>>> Andrew 
>>>
>>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[beagleboard] Re: BBB more reliable than Raspberry Pi - SD card corruption?

[kyle]

I'm working on a PCB now to mate with some software to allow the user to 
press a button, which will send a long GPIO signal to the ARM system.  A 
daemon process monitors that GPIO and does an orderly shutdown when it goes 
low.   The daemon also sets another GPIO high as it begins to shutdown.   
When that line falls low again after the board powers down then the 
external power switch cuts the power completely.  This was designed to plug 
into my own power distribution board for a robot.

Might be not-to-difficult to make up a carrier board for that PCB that just 
feeds the BBB (or a RaspPi) with a barrel connector and a two-pin cable. 
 If the prototypes function right I could send you one.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [beagleboard] Automotive Cape

[Micka]

By curiousity, when are you planning to release this cap ? :p


On Tue, Jan 28, 2014 at 4:28 PM,  wrote:

> Hi Eric,
> Yes adding the compass as well could easily be done as we are already
> using the MPU-6050 and it is a compatible replacement.
>
> The mini-PCI-e is the socket that a 3G/LTE card can be attached to, the
> interface to the beagle is USB and has the SIM interface as well to make
> things easy
> A GPS 3v3 LNA booster is also planned to allow the use of GPS antennas
> with LNA.
>
> Having the mini-PCIe enables the use of any card the user chooses.  We
> have used SierraWireless and Huawei modules for the 3G uplink.
>
> Marc
>
> On Monday, January 27, 2014 7:42:08 PM UTC, Eric wrote:
>>
>> adding compass functionality would add very little to the cost and be
>> quite useful.  It's the difference between usung an invensense
>> MPU-6050 6 axis or an MPU-9150 9 axis sensor.  an altimeter would be
>> nice as well.  I'd be interested in just how you intend to provide
>> mini-PCI-e on the bone but I don't see how it's needed for 3G-LTE or
>> GPS interfacing to the bone.  most of those modules are serially
>> controlled and where sound comes into play the bone has i2s and audio
>> serial port abilities that can either drive a dac/listen to an adc or
>> even speak directly to some modules over asp/i2s.
>>
>> Eric
>>
>> On Mon, Jan 27, 2014 at 9:37 AM,   wrote:
>> > Hello,
>> > I am part of a startup that has developed a system that is used to
>> analyse
>> > vehicles in they way they are driven and also track the journeys.
>> >
>> > We are producing a cape to use for development of our next version and
>> > thinking  about offering it for sale to the open source community.  The
>> > basics of the interface are:
>> > CAN
>> > ODBII via SN1110 OBD to UART Interpreter
>> > Mini-PCIe for 3G-LTE/GPS card
>> > 6 axis accel and gyro
>> > RTC
>> > USB expansion for WiFi dongle (possibly supporting 802.11p)
>> > Bi directional GPIO for vehicle signals (Ignition in GPIO_0 wakeup
>> domain)
>> >
>> > And maybe some more.
>> >
>> > Are there any requests/requirements that you think might be of benefit
>> to
>> > make the cape more usable ?
>> >
>> > Any feedback appreciated.
>> >
>> > Kind Regards
>> > Marc
>> >
>> > --
>> > For more options, visit http://beagleboard.org/discuss
>> > ---
>> > You received this message because you are subscribed to the Google
>> Groups
>> > "BeagleBoard" group.
>> > To unsubscribe from this group and stop receiving emails from it, send
>> an
>> > email to beagleboard...@googlegroups.com.
>> > For more options, visit https://groups.google.com/groups/opt_out.
>>
>  --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[beagleboard] PPS Support from GPIO

[lee]

I have what I think is a working DTS as the UART is working fine but I 
cannot get the system to read the PPS from a GPS unit I have connected.

Below is my DTS and the UART 4 is working fine and I have the GPS's PPS 
connected to P8-26 and so I'm hoping my DTS puts it into Mode7 on that pin.

PPS support is inside my kernel

Any ideas at all?

Lee

/*
 * Copyright (C) 2013 the8thlayerof.net
 *
 * GPS cape for UART4
 *
 * 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.
 */
/dts-v1/;
/plugin/;

/ {
compatible = "ti,beaglebone", "ti,beaglebone-black";

/* identification */
part-number = "T8LO-GPS";
version = "00A0";

/* state the resources this cape uses */
exclusive-use =
/* the pin header uses */
"P9.11",/* uart4_rxd */
"P9.13",/* uart4_txd */
"P8.26",/* gpio1_29   */
/* the hardware ip uses */
"uart4",
"gpio1_29";

fragment@0 {
target = <&am33xx_pinmux>;
__overlay__ {
gps_uart4_pins: pinmux_gps_uart4_pins {
pinctrl-single,pins = <
0x70 0x26 /* P9.11 
uart4_rxd.uart4_rxd MODE6 INPUT (RX) */
0x74 0x26 /* P9.13 
uart4_txd.uart4_rxd MODE6 OUTPUT (TX) */
>;
};

gps_pps_pins: pinmux_gps_pps_pins {
pinctrl-single,pins = <
0x7c 0x27 /* P8.26 gpio1_29 */
>;
};
};
};

fragment@1 {
target = <&uart5>; /* really uart4 */
__overlay__ {
status = "okay";
pinctrl-names = "default";
pinctrl-0 = <&gps_uart4_pins>;
};
};

fragment@2 {
target = <&ocp>;
__overlay__ {
pps {
compatible = "pps-gpio";
status = "okay";
pinctrl-names = "default";
pinctrl-0 = <&gps_pps_pins>;
gpios = <&gpio2 7 0 >;
assert-rising-edge;
};
};
};
};

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [beagleboard] Automotive Cape

[marcmltd]

Hi Eric,
Yes adding the compass as well could easily be done as we are already using 
the MPU-6050 and it is a compatible replacement.

The mini-PCI-e is the socket that a 3G/LTE card can be attached to, the 
interface to the beagle is USB and has the SIM interface as well to make 
things easy
A GPS 3v3 LNA booster is also planned to allow the use of GPS antennas with 
LNA.

Having the mini-PCIe enables the use of any card the user chooses.  We have 
used SierraWireless and Huawei modules for the 3G uplink.

Marc

On Monday, January 27, 2014 7:42:08 PM UTC, Eric wrote:
>
> adding compass functionality would add very little to the cost and be 
> quite useful.  It's the difference between usung an invensense 
> MPU-6050 6 axis or an MPU-9150 9 axis sensor.  an altimeter would be 
> nice as well.  I'd be interested in just how you intend to provide 
> mini-PCI-e on the bone but I don't see how it's needed for 3G-LTE or 
> GPS interfacing to the bone.  most of those modules are serially 
> controlled and where sound comes into play the bone has i2s and audio 
> serial port abilities that can either drive a dac/listen to an adc or 
> even speak directly to some modules over asp/i2s. 
>
> Eric 
>
> On Mon, Jan 27, 2014 at 9:37 AM,  > 
> wrote: 
> > Hello, 
> > I am part of a startup that has developed a system that is used to 
> analyse 
> > vehicles in they way they are driven and also track the journeys. 
> > 
> > We are producing a cape to use for development of our next version and 
> > thinking  about offering it for sale to the open source community.  The 
> > basics of the interface are: 
> > CAN 
> > ODBII via SN1110 OBD to UART Interpreter 
> > Mini-PCIe for 3G-LTE/GPS card 
> > 6 axis accel and gyro 
> > RTC 
> > USB expansion for WiFi dongle (possibly supporting 802.11p) 
> > Bi directional GPIO for vehicle signals (Ignition in GPIO_0 wakeup 
> domain) 
> > 
> > And maybe some more. 
> > 
> > Are there any requests/requirements that you think might be of benefit 
> to 
> > make the cape more usable ? 
> > 
> > Any feedback appreciated. 
> > 
> > Kind Regards 
> > Marc 
> > 
> > -- 
> > For more options, visit http://beagleboard.org/discuss 
> > --- 
> > You received this message because you are subscribed to the Google 
> Groups 
> > "BeagleBoard" group. 
> > To unsubscribe from this group and stop receiving emails from it, send 
> an 
> > email to beagleboard...@googlegroups.com . 
> > For more options, visit https://groups.google.com/groups/opt_out. 
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [beagleboard] Re: [BBB][Angstrom Distribution] [RS485] Applying a custom Patch

[Zachary Thorson]

>
>
> Now, I have developed an application which is combination of both send and 
> recv. I mean , after sending one byte on UART from BBB to other host 
> machine, I just wait for input bytes to receive(added receive timepout at 
> 10 sec). Now in this cae, even if I do not send any character from host 
> machine, BBB detects one/two arbitary bytes. 
>

Could you clarify what you mean by this?  I am assuming you are essentially 
using one host as a master and one as the slave.  Do you mean when neither 
end is transmitting, you are seeing arbitrary bytes, or that when the 
master sends a request out, you that same master sees bytes even if nothing 
is transmitted by either host?

If the random bytes are all 0's or all 1's (0x00, 0xFF) that might indicate 
some problems in what the non-driven state of the line voltage is.

If the bytes seem similar to what was being transmitted, you might be 
getting reflections if the line is not terminated properly.

This seems that driver changes GPIO position (from send mode to recv mode) 
> before transmitte buffer gets empty. 
>

Is this a guess from the behavior, or did you watch the signal lines, or 
use printk statements in the patch?


> Did any one has face this problem? Can you guys please share your thoughts 
> on this?
>

I have not seen this issue and have been using the patch at 38400 baud with 
an ADM2582 chip for a number of months now. 

 

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [beagleboard] Re: BeBoPr+ vs Replicape

[Elias Bakken]

Haha, Charles! Great suggestion : )

I think your page will suffice for now : )

On Tuesday, January 28, 2014 4:34:26 PM UTC+1, Charles Steinkuehler wrote:
>
> On 1/28/2014 9:23 AM, Bas Laarhoven wrote: 
> > 
> > Good job, I think we need web page for this. Who's first? (I'm to biased 
> > since I made the BeBoPr++ ;-) 
>
> Well, I've got the capes page on my blog: 
>
> http://bb-lcnc.blogspot.com/p/hardware-capes.html 
>
> ...but I really don't want to make keeping it updated a full-time job! 
>
> The differences we're talking about now are fairly subtle.  I propose 
> the time-honored tradition where both Elias and Bas put up comparison 
> charts showing how their board is all green-boxes and check marks, while 
> the other board is all red boxes and minus signs.  I'll put links to 
> both charts on my capes page!  :) 
>
> -- 
> Charles Steinkuehler 
> cha...@steinkuehler.net  
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[beagleboard] Re: BBB more reliable than Raspberry Pi - SD card corruption?

[Sian]

Thanks, I will take that into account and work around it best I can.

Again thanks for your input.

Sian

On Tuesday, January 28, 2014 2:52:00 PM UTC, ky...@cranehome.info wrote:
>
> Is that the case now with your Pi implementation?   No proper shutdown?
>
> The EMMC is subject to FS corruption from improper shutdown same as any 
> media.  In general I try to keep the FS utilization to under 60 to 70%. 
>  Give the thing lots of room to wear-level, especially with an OS that 
> likes to write crap to disk constantly.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [beagleboard] Re: BeBoPr+ vs Replicape

[Bas Laarhoven]

On 28-1-2014 16:34, Charles Steinkuehler wrote:

On 1/28/2014 9:23 AM, Bas Laarhoven wrote:

Good job, I think we need web page for this. Who's first? (I'm to biased
since I made the BeBoPr++ ;-)

Well, I've got the capes page on my blog:

http://bb-lcnc.blogspot.com/p/hardware-capes.html

...but I really don't want to make keeping it updated a full-time job!

The differences we're talking about now are fairly subtle.  I propose
the time-honored tradition where both Elias and Bas put up comparison
charts showing how their board is all green-boxes and check marks, while
the other board is all red boxes and minus signs.  I'll put links to
both charts on my capes page!  :)



ROFL


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

To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [beagleboard] Re: BeBoPr+ vs Replicape

[Charles Steinkuehler]

On 1/28/2014 9:23 AM, Bas Laarhoven wrote:
> 
> Good job, I think we need web page for this. Who's first? (I'm to biased
> since I made the BeBoPr++ ;-)

Well, I've got the capes page on my blog:

http://bb-lcnc.blogspot.com/p/hardware-capes.html

...but I really don't want to make keeping it updated a full-time job!

The differences we're talking about now are fairly subtle.  I propose
the time-honored tradition where both Elias and Bas put up comparison
charts showing how their board is all green-boxes and check marks, while
the other board is all red boxes and minus signs.  I'll put links to
both charts on my capes page!  :)

-- 
Charles Steinkuehler
char...@steinkuehler.net

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [beagleboard] Re: BeBoPr+ vs Replicape

[Bas Laarhoven]

On 28-1-2014 15:33, Charles Steinkuehler wrote:

On 1/28/2014 8:18 AM, Elias Bakken wrote:

Dave, I might be able to shed some more light on this, unless you are
completely set on making your own cape (Which is a lot of fun BTW :)
I am also biased since I have made the Replicape, but I'll try to be
objective and summarize the differences as I see them:


Good job, I think we need web page for this. Who's first? (I'm to biased 
since I made the BeBoPr++ ;-)


Dave: I agree with Elias, it's fun to build your own cape. But don't 
expect to get rich!



A great comparison, Elias.  A few minor comments in-line.


Replicape - BeBoPr++
5 steppers - 4 steppers


On board yes, but with the Penta Stepper board, or with external drivers 
the BeBoPr++

board also support 5 axes.


Stepper current programmable by ADC - stepper current adjustable with a
trim-pot.
Microstepping programmable via SPI down to 1/32 nd  - Microstepping with
dip switches down to 1/8 th (?)

The BeBoPr uses 3 dip switches, and will support whatever mirco-stepping
is available on your Pololu drivers of choice (ie: 1/16 or 1/32 if the
driver supports it).  This is just like the RAMPS or most other common
3D printer shields for the Arduino.


Indeed, there is no difference in microstep options between the BeBoPr++ 
and the Replicape.
The Penta Stepper driver board also uses software setting of the 
microstepping. These DIP

switches are so horribly expensive !




Stackable for LCD3/Reach or similar - Not stackable, but can use the
HDMI/I2C for display.
Low pass filter in analog input - Voltage clams on analog inputs


The BeBoPr++ is meant to be the last cape of a stack. Since some LCDs 
also want to be

the last cape, only on of these can be used.
But the BeBoPr provides a firm mounting base for capes and with the LVDS 
cape

it's possible to use an LCD with touch, or just use the HDMI output.


There is low pass filtering on the BeBoPr analog inputs, as well as
input protection.


Yes, and even some RAMPS people are now implementing this design :-)




No over-voltage protection on end-stops  - ?

All I/O on the BeBoPr is protected and level-shifted, including the end
stops.


Indeed, and the inputs are schmitt-trigger inputs, i.e. have hysteresis 
for slow changing signals.
This is a nice feature if you are using optical sensors (e.g. slot 
sensors, opto interrupters, etc.).


The BeBoPr++ inputs can also be used as 5V TTL compatible inputs. I'm 
not sure about the
Replicape inputs, AFAIK it's inputs connect directly to the BeagleBone. 
So in that case, using

5 Volts input levels is not possible.




Open source Hardware, software and firmware - Open source software (?)
$179 - $120 (is this right for the ++ board?)  + four stepper boards ($10
each?)


The BeBoPr++ will cost around $99 (depending on exchange rate fluctuations).

-- Bas


Bas has designed an add-on board to drive five steppers called the penta
board:

https://github.com/modmaker/BeBoPr/wiki/Penta-Stepper-Board

...you can also use the header the penta board connects to for driving
off-board stepper drivers if you need more power (for driving a real
milling machine, as an example).

Both are great boards, and which one will work best depends on exactly
what you're trying to do, whether you've got any Pololu drivers on-hand,
etc.



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

To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[beagleboard] Awkward booting problem with the BBB

[deepak karki]

I'm posting after reading similar topics on this Google group, none of the 
solutions worked. [also my problem is a bit different than the ones before, 
I have been struggling for about a month to get my BBB working!]

Here is the sequence of problems-failed solutions I have been through with 
my board :
1. About a month back I bought a BBB from a local retailer. Worked 
perfectly for first two days, I was able to ssh, install pyBBIO etc.
2. The next time I booted (tried to) my  board, it failed. Only power 
button was on, other LED's didn't even start blinking. I plugged out the 
power, tried 5 minutes later, it worked! ssh-ed again and shut it down 
(sudo shutdown 0)
3. Next time while booting, I had the same problems, removing powering and 
starting again did not help.
4. I downloaded Arch Linux on a microSD card, put it into the BBB powered 
the board holding the boot button, within half a minute I was able to SSH 
again! Arch worked.
5. I wasn't that happy with the Arch distribution, even though it worked. 
So I got an Ubuntu image on my microSD. Tried booting the Black the same 
way holding the boot button, but all that happened was all 4 LED's were on 
for ~15 minutes [ I still don't know why this happens! ] Then the led's 
started to blink, I was able to SSH. Sadly this happens every time I boot 
with Ubuntu (via microSD).
6. Later I thought I would re-flash Angstrom, and got the emmc-flasher 
image on my microSD. Booted the board with the boot button pressed. 
According to the manual the lights should have started flashing, and once 
the image is written all 4 LED's should turn on [
http://derekmolloy.ie/write-a-new-image-to-the-beaglebone-black/ ]. But for 
me all the 4 LED's were switched on from the power on stage, for ~5 min, 
later they started to blink, but after 10 min or so, all 4 LED's abruptly 
went off. (In the instructions it says that all 4 LED's will go on when 
writing is complete)
7. But anyway hoping that writing to the eMMC was complete, I booted the 
board normally. USR0 switches on first followed by USR1, USR2. Then it 
freezes here. I'm STUCK!!

What should I do now? 
also a couple more questions :
- What does holding down the boot button do if the img in the SD card in 
not a emmc-flasher? Does it just boot from the SD card or does it also get 
written to emmc?
- Is there some setting by which I can boot via the SD card without having 
to press the boot button every time and also not having to burn the image 
on the emmc?

regds,
Deepak

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [beagleboard] Awkward booting problem with the BBB

[Robert Nelson]

On Tue, Jan 28, 2014 at 9:00 AM, deepak karki  wrote:
> I'm posting after reading similar topics on this Google group, none of the
> solutions worked. [also my problem is a bit different than the ones before,
> I have been struggling for about a month to get my BBB working!]
>
> Here is the sequence of problems-failed solutions I have been through with
> my board :
> 1. About a month back I bought a BBB from a local retailer. Worked perfectly
> for first two days, I was able to ssh, install pyBBIO etc.
> 2. The next time I booted (tried to) my  board, it failed. Only power button
> was on, other LED's didn't even start blinking. I plugged out the power,
> tried 5 minutes later, it worked! ssh-ed again and shut it down (sudo
> shutdown 0)
> 3. Next time while booting, I had the same problems, removing powering and
> starting again did not help.
> 4. I downloaded Arch Linux on a microSD card, put it into the BBB powered
> the board holding the boot button, within half a minute I was able to SSH
> again! Arch worked.
> 5. I wasn't that happy with the Arch distribution, even though it worked. So
> I got an Ubuntu image on my microSD. Tried booting the Black the same way
> holding the boot button, but all that happened was all 4 LED's were on for
> ~15 minutes [ I still don't know why this happens! ] Then the led's started
> to blink, I was able to SSH. Sadly this happens every time I boot with
> Ubuntu (via microSD).
> 6. Later I thought I would re-flash Angstrom, and got the emmc-flasher image
> on my microSD. Booted the board with the boot button pressed. According to
> the manual the lights should have started flashing, and once the image is
> written all 4 LED's should turn on
> [http://derekmolloy.ie/write-a-new-image-to-the-beaglebone-black/ ]. But for
> me all the 4 LED's were switched on from the power on stage, for ~5 min,
> later they started to blink, but after 10 min or so, all 4 LED's abruptly
> went off. (In the instructions it says that all 4 LED's will go on when
> writing is complete)
> 7. But anyway hoping that writing to the eMMC was complete, I booted the
> board normally. USR0 switches on first followed by USR1, USR2. Then it
> freezes here. I'm STUCK!!

You could grab a usb-serial adapter and find out..

> What should I do now?
> also a couple more questions :
> - What does holding down the boot button do if the img in the SD card in not
> a emmc-flasher? Does it just boot from the SD card or does it also get
> written to emmc?

Holding the button guarntees it'll try to load MLO/u-boot.img from the
SD card first.

> - Is there some setting by which I can boot via the SD card without having
> to press the boot button every time and also not having to burn the image on
> the emmc?

A proper uEnv.txt in your sd card will guarntee it..  Otherwise just
"dd if=/dev/zero of=/dev/mmcblk1" bootloader gone from eMMC...

Regards,

-- 
Robert Nelson
http://www.rcn-ee.com/

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[beagleboard] Re: BBB more reliable than Raspberry Pi - SD card corruption?

[kyle]

Is that the case now with your Pi implementation?   No proper shutdown?

The EMMC is subject to FS corruption from improper shutdown same as any 
media.  In general I try to keep the FS utilization to under 60 to 70%. 
 Give the thing lots of room to wear-level, especially with an OS that 
likes to write crap to disk constantly.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [beagleboard] BBB more reliable than Raspberry Pi - SD card corruption?

[Robert Nelson]

On Tue, Jan 28, 2014 at 8:37 AM, Sian McNeill  wrote:
> Hi,
>
> I'm currently running a data logging application on a Raspberry Pi, I'm
> running into a lot problems with SD card corruption. I'm looking into moving
> it to run on a Beagle Bone Black via the EMMC rather than external SD card.
>
> I'm using the latest Ubuntu Saucy image, flashed to the EMMC. Where the BBB
> will be housed there may well be random power outages, though it will
> hopefully be through a UPS.
>
> Without a proper shutdown sequence am I going to risk corruption on the
> EMMC?

Yes.. It doesn't matter what arm device you use. Without a proper
shutdown, any media will eventually get corrupted with random power
failures.

Things that help:
1: use 'noatime' on mount to limit writes
2: read-only root file system

or just get a ups..

Regards,

-- 
Robert Nelson
http://www.rcn-ee.com/

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[beagleboard] BBB more reliable than Raspberry Pi - SD card corruption?

[Sian McNeill]

Hi,

I'm currently running a data logging application on a Raspberry Pi, I'm 
running into a lot problems with SD card corruption. I'm looking into 
moving it to run on a Beagle Bone Black via the EMMC rather than external 
SD card.

I'm using the latest Ubuntu Saucy image, flashed to the EMMC. Where the BBB 
will be housed there may well be random power outages, though it will 
hopefully be through a UPS.

Without a proper shutdown sequence am I going to risk corruption on the 
EMMC?

Are people having better stability with the BBB compared to the Pi?

Thanks!

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [beagleboard] Re: Solved - I now have reliable WiFi on the Bone

[kyle]

I've had good luck with Arch Linux and the ASUS N10.   I just install 
wpa_supplicant and from there use the standard netctl profile system and it 
will connect up no problem.   I gave up on Angstrom a while ago.   Same 
adapter simply would not run in that and there were so many other issues I 
just quit trying.   


I put this in /etc/netctl/wlan0-MYSSID

Pre_up='sleep 10'
Connection=wireless
Description='Automatically generated profile by wifi-menu'
Interface=wlan0
Security=wpa
ESSID='MYSSID'
IP=dhcp
Key='thisismysecretkey'

Then it's: 
# netctl start wlan0-MYSSID

If that is successful then:
# netctl enable wlan0-MYSSID
Will bring the connection up at boot

It gets more complicated to handle coming up when it's plugged in or 
connecting to several networks automatically but I don't need any of that 
for my purpose.   Also note I have problems getting NTP to run right on 
wireless.  Takes too long to come up and it seems NTP gives up before the 
network is available.   I have an RTC connected on I2C-1 though so I never 
got too interested in solving this.   I just use a cron job and ntpdate 
once a day to keep things close once the RTC has been set.


All the other small adapters I have tried are problematic.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [beagleboard] Re: BeBoPr+ vs Replicape

[Charles Steinkuehler]

On 1/28/2014 8:18 AM, Elias Bakken wrote:
> Dave, I might be able to shed some more light on this, unless you are 
> completely set on making your own cape (Which is a lot of fun BTW :) 
> I am also biased since I have made the Replicape, but I'll try to be 
> objective and summarize the differences as I see them: 

A great comparison, Elias.  A few minor comments in-line.

> Replicape - BeBoPr++
> 5 steppers - 4 steppers
> Stepper current programmable by ADC - stepper current adjustable with a 
> trim-pot.
> Microstepping programmable via SPI down to 1/32 nd  - Microstepping with 
> dip switches down to 1/8 th (?) 

The BeBoPr uses 3 dip switches, and will support whatever mirco-stepping
is available on your Pololu drivers of choice (ie: 1/16 or 1/32 if the
driver supports it).  This is just like the RAMPS or most other common
3D printer shields for the Arduino.

> Stackable for LCD3/Reach or similar - Not stackable, but can use the 
> HDMI/I2C for display. 
> Low pass filter in analog input - Voltage clams on analog inputs

There is low pass filtering on the BeBoPr analog inputs, as well as
input protection.

> No over-voltage protection on end-stops  - ?

All I/O on the BeBoPr is protected and level-shifted, including the end
stops.

> Open source Hardware, software and firmware - Open source software (?)
> $179 - $120 (is this right for the ++ board?)  + four stepper boards ($10 
> each?) 

Bas has designed an add-on board to drive five steppers called the penta
board:

https://github.com/modmaker/BeBoPr/wiki/Penta-Stepper-Board

...you can also use the header the penta board connects to for driving
off-board stepper drivers if you need more power (for driving a real
milling machine, as an example).

Both are great boards, and which one will work best depends on exactly
what you're trying to do, whether you've got any Pololu drivers on-hand,
etc.

-- 
Charles Steinkuehler
char...@steinkuehler.net

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

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

[Robert Nelson]

> I had this issue with my MachineKit images until I switched to lightdm
> instead of xdm.  Lightdm is trusted by consolekit (no relation to
> MachineKit! :) and thus allows things like rebooting and user mounting
> of USB devices.
>
> I was running xfce4, however, so lxde might be different.

Yeah, it's lxpanel that can't get the permissions..  We are using
lightdm/systemd underneath lxde..

Regards,

-- 
Robert Nelson
http://www.rcn-ee.com/

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [beagleboard] USB and Ethernet not getting detected on my beagleboard-xM

[Robert Nelson]

On Tue, Jan 28, 2014 at 6:18 AM,   wrote:
>  Uncompressing Linux... done, booting the kernel.
> tor.2': device_add
> regulator: VUSB3V1: 3100 mV normal standby
> twl4030_usb twl4030_usb: Initialized TWL4030 USB module
> regulator: VMMC1: 1850 <--> 3150 mV at 3000 mV normal standby
> regulator: VDAC: 1800 mV normal standby
> regulator: VDVI: 1800 mV normal standby
> regulator: VSIM: 1800 <--> 3000 mV at 1800 mV normal standby
> i2c_omap i2c_omap.3: bus 3 rev4.0 at 100 kHz
> Switching to clocksource 32k_counter
> musb_hdrc: version 6.0, musb-dma, host, debug=0
> musb_hdrc: USB Host mode controller at fa0ab000 using DMA, IRQ 92
> musb_hdrc musb_hdrc: MUSB HDRC host driver
> musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1
> hub 1-0:1.0: USB hub found
> hub 1-0:1.0: 1 port detected
> musb_stage2_irq 803: unhandled DISCONNECT transition (a_idle)
> NET: Registered protocol family 2
> IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
> TCP established hash table entries: 16384 (order: 5, 131072 bytes)
> TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
> TCP: Hash tables configured (established 16384 bind 16384)
> TCP reno registered
> UDP hash table entries: 256 (order: 0, 4096 bytes)
> UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
> NET: Registered protocol family 1
> RPC: Registered udp transport module.
> RPC: Registered tcp transport module.
> RPC: Registered tcp NFSv4.1 backchannel transport module.
> NetWinder Floating Point Emulator V0.97 (double precision)
> VFS: Disk quotas dquot_6.5.2
> Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
> JFFS2 version 2.2. (NAND) �© 2001-2006 Red Hat, Inc.
> msgmni has been set to 1007
> alg: No test for stdrng (krng)
> io scheduler noop registered
> io scheduler deadline registered
> io scheduler cfq registered (default)
> omapfb: configured for panel omap3beagle
> omapfb: DISPC version 3.0 initialized
> Console: switching to colour frame buffer device 128x48
> omapfb: Framebuffer initialized. Total vram 1572864 planes 1
> omapfb: Pixclock 64000 kHz hfreq 59.0 kHz vfreq 76.9 Hz
> Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
> serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654
> serial8250.1: ttyS1 at MMIO 0x4806c000 (irq = 73) is a ST16654
> serial8250.2: ttyS2 at MMIO 0x4902 (irq = 74) is a ST16654
> console [ttyS2] enabled
> brd: module loaded
> loop: module loaded
> usbmon: debugfs is not available
> ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
> ehci-omap ehci-omap.0: OMAP-EHCI Host Controller
> ehci-omap ehci-omap.0: new USB bus registered, assigned bus number 2
> ehci-omap ehci-omap.0: irq 77, io mem 0x48064800
> ehci-omap ehci-omap.0: USB 2.0 started, EHCI 1.00
> hub 2-0:1.0: USB hub found
> hub 2-0:1.0: 3 ports detected
> Initializing USB Mass Storage driver...
> usbcore: registered new interface driver usb-storage
> USB Mass Storage support registered.
> usbcore: registered new interface driver libusual
> i2c /dev entries driver
> TCP cubic registered
> NET: Registered protocol family 17
> NET: Registered protocol family 15
> Power Management for TI OMAP3.
> VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
> regulator_init_complete: incomplete constraints, leaving VDVI on
> regulator_init_complete: incomplete constraints, leaving VDAC on
> drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
> Waiting for root device /dev/mmcblk0p2...
> mmc0: new SD card at address b2d2
> mmcblk0: mmc0:b2d2 SU01G 968 MiB
>  mmcblk0: p1 p2
> kjournald starting.  Commit interval 5 seconds
> EXT3-fs (mmcblk0p2): using internal journal
> EXT3-fs (mmcblk0p2): mounted filesystem with writeback data mode
> VFS: Mounted root (ext3 filesystem) on device 179:2.
> Freeing init memory: 132K
> INIT: version 2.86 booting
> Please wait: booting...
> Starting udev
> udev: starting version 151
> Remounting root file system...
> Caching udev devnodes
> Populating dev cache
> ALSA: Restoring mixer settings...
> Configuring network interfaces... /usr/sbin/alsactl: load_state:1625: No
> soundcards found...
> ifconfig: SIOCGIFFLAGS: No such device
> ifconfig: SIOCGIFFLAGS: No such device
> eth0  No such device
>
> ifconfig: SIOCGIFFLAGS: No such device
> ifconfig: SIOCGIFFLAGS: No such device
> ifconfig: SIOCGIFFLAGS: No such device
> usb0  No such device
>
> ifconfig: SIOCGIFFLAGS: No such device
> done.
> Starting portmap daemon: portmap.
> net.ipv4.conf.default.rp_filter = 1
> net.ipv4.conf.all.rp_filter = 1
> hwclock: can't open '/dev/misc/rtc': No such file or directory
> Thu Jul 25 00:23:00 UTC 2013
> hwclock: can't open '/dev/misc/rtc': No such file or directory
> INIT: Entering runlevel: 5
> Starting system message bus: dbus.
> Starting Dropbear SSH server: dropbear.
> Starting advanced power management daemon: No APM support in kernel
> (failed.)
> Starting syslogd/klogd: done
>  * Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon
>...done.
>
> .-

[beagleboard] discard option on rootfs

[iustinian . input]

Hello,

Is it safe to add discard as a mount option for the rootfs on the eMMC. I 
am sometimes writing big chunks of data on the rootfs and it is getting 
sluggish.

Using debian and Linux arm 3.8.13-bone37 #1 SMP Thu Jan 23 00:56:41 UTC 
2014 armv7l GNU/Linux rcn kernels.

Alternatively doing fstrim -v / helps with trim. Gerald, I know that the 
Micron eMMC supports trim operations I was wondering if it is fully 
implemented.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[beagleboard] Re: Won't boot when using hdmi header pins, even though hdmi is disabled

[kyle]

Are you driving any of the pins with a high or low at power on?   Every pin 
in the LCD_DATA range is used by the bone to select it's boot mode and are 
configured on the board to be set at a default value.   If you drive those 
pins with another value you just altered the boot configuration.   You need 
a buffer with output enable that is gated with SYS_RESETn.   It must not 
drive those LCD_DATA pins until SYS_RESETn goes high at which point the 
boot mode is selected and underway.  Unfortunately that means you likely 
also need an inverter for most any common buffer with an output enable.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[beagleboard] Re: BeBoPr+ vs Replicape

[Elias Bakken]

Dave, I might be able to shed some more light on this, unless you are 
completely set on making your own cape (Which is a lot of fun BTW :) 
I am also biased since I have made the Replicape, but I'll try to be 
objective and summarize the differences as I see them: 

Replicape - BeBoPr++
5 steppers - 4 steppers
Stepper current programmable by ADC - stepper current adjustable with a 
trim-pot.
Microstepping programmable via SPI down to 1/32 nd  - Microstepping with 
dip switches down to 1/8 th (?) 
Stackable for LCD3/Reach or similar - Not stackable, but can use the 
HDMI/I2C for display. 
Low pass filter in analog input - Voltage clams on analog inputs
No over-voltage protection on end-stops  - ?
Open source Hardware, software and firmware - Open source software (?)
$179 - $120 (is this right for the ++ board?)  + four stepper boards ($10 
each?) 



On Monday, January 20, 2014 4:56:46 PM UTC+1, Dave Covert wrote:
>
>
> Can someone tell me the difference between a BePoPr+ cape and a Replicape?
>
> Dave
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [beagleboard] BeagleBone Power switch problems.

[Gerald Coley]

What sort of battery?

Gerald



On Tue, Jan 28, 2014 at 5:31 AM,  wrote:

> Hi,
>
> When powering down the BBB using S3 (Power) it works fine when powered via
> USB or 5v DC input. I have wired a battery to the testpoints that go to the
> PMIC (U2) and the switch no longer functions as expected. It shuts down but
> then immediately restarts.
>
> Any Ideas?
>
> Many Thanks!
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [beagleboard] Won't boot when using hdmi header pins, even though hdmi is disabled

[Gerald Coley]

I suspect that you are messing with the boot pins. These pins are read to
determine the boot mode. Did you by chance read the System Reference Manual
on this topic?

Gerald



On Tue, Jan 28, 2014 at 1:09 AM,  wrote:

> Hoping someone can help.
>
> I'm trying to use some of the P8 hdmi header pins as GPIOs.
>
> They work fine if I boot the BBB without them plugged in, and once boot
> plug them in.
> But the BBB won't boot if they are plugged in when power is applied.
> Nothing appears on the console tty.
>
> Thanks in advance.
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [beagleboard] Re: [BBB][Angstrom Distribution] [RS485] Applying a custom Patch

[Micka]

Enjoy :

// 8N1 :
mode . c_cflag &= ( ~ CSIZE )  ; mode . c_cflag |= CS8 ;
mode . c_cflag &= ( ~ PARENB ) ;
mode . c_cflag &= ( ~ CRTSCTS ) ;
/*
  raw same as -ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr
-icrnl -ixon -ixoff -iuclc -ixany -imaxbel -opost -isig -icanon -xcase min
1 $
 */
mode . c_iflag |= IGNBRK   ;
mode . c_iflag |= IGNPAR   ;
mode . c_iflag &= ( ~ INLCR  ) ;
mode . c_iflag &= ( ~ ICRNL  ) ;
mode . c_iflag &= ( ~ IXON   ) ;
mode . c_iflag &= ( ~ IXOFF  ) ;
mode . c_oflag &= ( ~ ONLCR  ) ;
mode . c_oflag &= ( ~ OCRNL  ) ;
mode . c_lflag &= ( ~ ISIG   ) ;
mode . c_lflag &= ( ~ ICANON ) ;
mode . c_lflag &= ( ~ ECHO   ) ;
rv=tcsetattr ( pContext->iHandlerConnection , 0 /* no special action */ , &
mode );


On Tue, Jan 28, 2014 at 11:36 AM,  wrote:

> Hello Micka,
>
> Thanks for your prompt response. I was using 115200. Now I have tried with
> 38400 and 9600 as well but still the problem persists.
>
> Can you do me a favor?  Can you please send the termios structure
> configurations with which query-response type application works at your
> end? Here is the configurations I am using:
>
> struct termios my_termios, new_termios;
> int fd0 = open("/dev/ttyO4", O_RDWR | O_NDELAY | O_NOCTTY);
>
> tcgetattr(fd0, &my_termios);
> my_termios.c_iflag &= ~(IGNBRK | BRKINT | ICRNL | INLCR | PARMRK |
> INPCK | ISTRIP | IXON);
> my_termios.c_oflag &= ~(OCRNL | ONLCR | ONLRET | ONOCR | OFILL |
> OLCUC | OPOST);
> my_termios.c_lflag &= ~(ECHO | ECHONL | ICANON | IEXTEN | ISIG |
> ECHOK | ECHOCTL | ECHOPRT);
> my_termios.c_cflag &= ~(CSIZE | PARENB);
> my_termios.c_cflag &= ~CRTSCTS;
> my_termios.c_cflag |= CS8 | CLOCAL | CREAD;
> my_termios.c_cflag &= ~CBAUD;
> my_termios.c_cflag |= B9600;
> my_termios.c_cc[VMIN] = 0;
> my_termios.c_cc[VTIME] = 5;
> rv = tcsetattr(fd0, TCSANOW, &my_termios);
> tcgetattr(fd0, &new_termios);
>
> Thanks,
> Ashish
>
> On Monday, January 27, 2014 7:23:01 PM UTC+5:30, Mickae1 wrote:
>
>> What is the baudRate ? Can you spy the communication with an other device
>> ?  ( serial adapter rs485/rs232 )
>>
>> In my case, baudrate 38400 work pretty well, without noise.
>>
>> and please don't UNDERLINE !
>>
>> Micka,
>>
>>
>> On Mon, Jan 27, 2014 at 10:54 AM,  wrote:
>>
>>> Hi All,
>>>
>>> I have a interesting issue:
>>>
>>> What I have did is:
>>>
>>>- Downloaded Angstrom linux
>>>- Applied RS485 patch
>>>- Compiled kernel image and push it to BBB.
>>>
>>> Now I have developed two applications:
>>>
>>>1. send.c : This application periodically sends the data on UART
>>>2. recv.c: This application waits to read the data from UART.
>>>
>>> Both above application works pretty well without any issue. Even I do
>>> not have to manually drive the GPIO. (Driver patch handles GPIO value
>>> perfectly.).
>>>
>>> *Problem:*
>>>
>>> *Now, I have developed an application which is combination of both send
>>> and recv. I mean , after sending one byte on UART from BBB to other host
>>> machine, I just wait for input bytes to receive(added receive timepout at
>>> 10 sec). Now in this cae, even if I do not send any character from host
>>> machine, BBB detects one/two arbitary bytes. This seems that driver changes
>>> GPIO position (from send mode to recv mode) before transmitte buffer gets
>>> empty. *
>>>
>>> Did any one has face this problem? Can you guys please share your
>>> thoughts on this?
>>>
>>> Thank,
>>> Ashish
>>>
>>> On Tuesday, December 3, 2013 11:23:48 PM UTC+5:30, hbigl...@gmail.comwrote:

 Zach,

 That is great info!

 Thanks a bunch,

 Haik

 On Tuesday, December 3, 2013 11:42:10 AM UTC-5, Zachary Thorson wrote:

> I am using a custom built cape for my application, so I have not
> tested it.  Though according to the schematics it looks like the chip does
> not support those rates.
>
> According to the schematic at:
> http://beagleboardtoys.info/index.php?title=BeagleBone_RS485
>
> It looks like the RS485 cape uses a TI transceiver part no: SN75HVD12D
>  http://www.ti.com/lit/ds/symlink/sn75hvd12.pdf
>
>
> 
>
> Should be able to go up to 1Mbps, but not much higher.
>
> Checking the ARM Datasheet (AM335x ARM Cortex -A8 MPU Technical
> Reference Manual):
>
> 19.1.1 UART Mode Features
> The general features of the UART/IrDA module when operating in UART
> mode are:
>
>- 16C750 compatibility
>- Baud rate from 300 bps up to 3.6864 Mbps
>- Auto-baud between 1200 bps and 115.2 Kbps
>
>
> Since on the ARM side, you have slightly higher max data rates, so if
> you had a faster chip you could approach the rate you need given the right
> design.  If you n

[beagleboard] Won't boot when using hdmi header pins, even though hdmi is disabled

[miller . garym]

Hoping someone can help.

I'm trying to use some of the P8 hdmi header pins as GPIOs.

They work fine if I boot the BBB without them plugged in, and once boot 
plug them in.
But the BBB won't boot if they are plugged in when power is applied.
Nothing appears on the console tty.

Thanks in advance.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [beagleboard] Re: [BBB][Angstrom Distribution] [RS485] Applying a custom Patch

[ashishagrawal . ecc]

Hello Micka,

Thanks for your prompt response. I was using 115200. Now I have tried with 
38400 and 9600 as well but still the problem persists.

Can you do me a favor?  Can you please send the termios structure 
configurations with which query-response type application works at your 
end? Here is the configurations I am using:

struct termios my_termios, new_termios;
int fd0 = open("/dev/ttyO4", O_RDWR | O_NDELAY | O_NOCTTY);

tcgetattr(fd0, &my_termios);
my_termios.c_iflag &= ~(IGNBRK | BRKINT | ICRNL | INLCR | PARMRK | 
INPCK | ISTRIP | IXON);
my_termios.c_oflag &= ~(OCRNL | ONLCR | ONLRET | ONOCR | OFILL | 
OLCUC | OPOST);
my_termios.c_lflag &= ~(ECHO | ECHONL | ICANON | IEXTEN | ISIG | 
ECHOK | ECHOCTL | ECHOPRT);
my_termios.c_cflag &= ~(CSIZE | PARENB);
my_termios.c_cflag &= ~CRTSCTS;
my_termios.c_cflag |= CS8 | CLOCAL | CREAD;
my_termios.c_cflag &= ~CBAUD;
my_termios.c_cflag |= B9600;
my_termios.c_cc[VMIN] = 0;
my_termios.c_cc[VTIME] = 5;
rv = tcsetattr(fd0, TCSANOW, &my_termios);
tcgetattr(fd0, &new_termios);

Thanks,
Ashish
On Monday, January 27, 2014 7:23:01 PM UTC+5:30, Mickae1 wrote:
>
> What is the baudRate ? Can you spy the communication with an other device 
> ?  ( serial adapter rs485/rs232 ) 
>
> In my case, baudrate 38400 work pretty well, without noise.
>
> and please don't UNDERLINE !
>
> Micka,
>
>
> On Mon, Jan 27, 2014 at 10:54 AM, >wrote:
>
>> Hi All,
>>
>> I have a interesting issue:
>>
>> What I have did is:
>>
>>- Downloaded Angstrom linux
>>- Applied RS485 patch
>>- Compiled kernel image and push it to BBB. 
>>
>> Now I have developed two applications:
>>
>>1. send.c : This application periodically sends the data on UART
>>2. recv.c: This application waits to read the data from UART. 
>>
>> Both above application works pretty well without any issue. Even I do not 
>> have to manually drive the GPIO. (Driver patch handles GPIO value 
>> perfectly.).
>>
>> *Problem:*
>>
>> *Now, I have developed an application which is combination of both send 
>> and recv. I mean , after sending one byte on UART from BBB to other host 
>> machine, I just wait for input bytes to receive(added receive timepout at 
>> 10 sec). Now in this cae, even if I do not send any character from host 
>> machine, BBB detects one/two arbitary bytes. This seems that driver changes 
>> GPIO position (from send mode to recv mode) before transmitte buffer gets 
>> empty. *
>>
>> Did any one has face this problem? Can you guys please share your 
>> thoughts on this?
>>
>> Thank,
>> Ashish
>>
>> On Tuesday, December 3, 2013 11:23:48 PM UTC+5:30, hbigl...@gmail.comwrote:
>>>
>>> Zach,
>>>
>>> That is great info! 
>>>
>>> Thanks a bunch,
>>>
>>> Haik
>>>
>>> On Tuesday, December 3, 2013 11:42:10 AM UTC-5, Zachary Thorson wrote:
>>>
 I am using a custom built cape for my application, so I have not tested 
 it.  Though according to the schematics it looks like the chip does not 
 support those rates.

 According to the schematic at:
 http://beagleboardtoys.info/index.php?title=BeagleBone_RS485

 It looks like the RS485 cape uses a TI transceiver part no: SN75HVD12D
  http://www.ti.com/lit/ds/symlink/sn75hvd12.pdf


 

 Should be able to go up to 1Mbps, but not much higher.

 Checking the ARM Datasheet (AM335x ARM Cortex -A8 MPU Technical 
 Reference Manual):

 19.1.1 UART Mode Features
 The general features of the UART/IrDA module when operating in UART 
 mode are:

- 16C750 compatibility
- Baud rate from 300 bps up to 3.6864 Mbps
- Auto-baud between 1200 bps and 115.2 Kbps 


 Since on the ARM side, you have slightly higher max data rates, so if 
 you had a faster chip you could approach the rate you need given the right 
 design.  If you need faster than what is natively on the ARM, you could 
 look into a custom solution with the PRU, but I don't have any experience 
 with that.


 Zach

 On Tuesday, December 3, 2013 6:17:45 AM UTC-6, hbigl...@gmail.comwrote:
>
> Hi Mika,
>
> I need to go two orders of magnitude higher (3.8 Meg, for a short 
> distance of six feet, half duplex).  Is there a chance with BBB?
>
> Thanks,
> Haik
>
> On Tuesday, December 3, 2013 3:40:39 AM UTC-5, Mickae1 wrote:
>>
>> Hi,
>>
>> Well, I'm working with the BaudRate 38400 and I don't have any 
>> problem. I didn't try further.
>>
>> micka,
>>
>>
>> On Tue, Dec 3, 2013 at 3:13 AM,  wrote:
>>
>>> Hi all,
>>>
>>> Interesting Work!  What is the max baud rate you can get from this 
>>> rs485 cape on BBB?
>>>
>>> Haik
>>>
>>>
>

[beagleboard] Re: Clone Ubuntu EMMC on BBB

[Cristian Astorino]

is it possible to use initrd with angstrom? I would like to boot from emmc 
with uuid. Actually when microsd is inserted the system boot from microsd 
and I would like to avoid that.

Regards

Il giorno domenica 5 gennaio 2014 23:33:02 UTC+1, Brian Piccioni ha scritto:
>
> Hello and thank you in advance for the help.
>
> I know that, in general, this topic has been addressed before. I looked 
> through all the posts, followed whatever methods, etc., were suggested but 
> I can't get it to work (it being cloning my eMMC on one BBB to another BBB).
>
> I live in rural Canada and downloading costs me $10/gb so I am cautious 
> about downloading stuff unless i have to, etc..
>
> My 'source' system is Ubuntu 13.04 (GNU/Linux 3.8.13-bone21 armv7l). 
> Initially my target was an 'out of the box' BBB. 
>
> I booted the 'source' system from an Anstrom 'bootable' microSD, mounted a 
> USB drive, in the USB directory I executed 
>
> dd if=/dev/mmcblk1 of=BeagleBoneBlack-eMMC-image-Jan52014.img 
> bs=10M
>
> The command completed with no errors and a reassuring amount of data 
> copied (1.9gb)
>
> Then I booted the 'destination' system from an Anstrom 'bootable' microSD, 
> mounted my USB drive, and in the USB directory executed 
>
> dd if=BeagleBoneBlack-eMMC-image-Jan52014.img of=/dev/mmcblk1 
> bs=10M
>
> Again, the command completed with no errors and a reassuring amount of 
> data copied (1.9gb)
>
>
> Unfortunately, when I boot the destination machine, nothing much happens 
> except a flashing LED. I can't SSH into the board and it doesn't even show 
> up on my network.
>
> Figuring there was something Ubuntu related I flashed the destination BBB 
> with Ubuntu 12.4, which I had around. It worked fine, however, when I 
> repeated the above procedure (including booting Angstrom off microSD) I got 
> the same result.
>
>
> I wonder if there is something wrong with my eMMC partion table on the 
> source BBB (even though it works fine). When I execute fdisk -l I get the 
> following (note the *doesn't contain a valid partition table* reports) 
>
> Disk /dev/mmcblk1: 1920 MB, 1920991232 bytes
> 255 heads, 63 sectors/track, 233 cylinders, total 3751936 sectors
> Units = sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x
>
> Device Boot  Start End  Blocks   Id  System
> /dev/mmcblk1p1   *  63  144584   72261c  W95 FAT32 
> (LBA)
> /dev/mmcblk1p2  144585 3743144 1799280   83  Linux
>
> Disk /dev/mmcblk1boot1: 1 MB, 1048576 bytes
> 4 heads, 16 sectors/track, 32 cylinders, total 2048 sectors
> Units = sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x
>
> Disk /dev/mmcblk1boot1 doesn't contain a valid partition table
>
> Disk /dev/mmcblk1boot0: 1 MB, 1048576 bytes
> 4 heads, 16 sectors/track, 32 cylinders, total 2048 sectors
> Units = sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x
>
> Disk /dev/mmcblk1boot0 doesn't contain a valid partition table
>
>
> I would be very grateful if somebody could tell me what I am doing wrong.
>
> Thank you
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[beagleboard] Workmanship?

[Paul O'Connor]

I got a Beaglebone Black from Adafruit Industries which had some poor 
quality soldering -- see my post at 
http://www.adafruit.com/forums/viewtopic.php?f=49&t=48935
for details.
Anyone else have problem like 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/groups/opt_out.

[beagleboard] HDMI Audio

[Clint Slade]

Hi, I'm new to BeagleBones.

When I connect my BBB to my monitor via HDMI loud white noise starts as it 
boots and does not stop. The speakers are fine, they work with other 
devices.

I have tried a speaker test from terminal, and the white noise becomes 
quieter but is still apparent.

My resolution is 1980 x 1020. Out of the box Angstrom.

Please provide your suggestions.
Thanks!

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[beagleboard] No HDMI Audio

[Clint Slade]

Hi, I am new to BeagleBone. When I connect my BBB to my monitor via HDMI, loud 
white noise starts as it boots and does not stop.

The speakers are fine, they work with other devices using HDMI.

I have tried a speaker test from terminal, and the white noise becomes 
quieter during the test but is still apparent.

My resolution is 1980 x 1020. I am running out of the box Angstrom.

Let me know your suggestions.
Thanks!

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [beagleboard] Reading a Quadrature Encoder connected to a Beaglebone [black]

[willehwark]

Nathaniel,

First of all, thank you very much for all the work you have put into the 
BeagleBone and provided to the community through your Github repository. I 
am working on a robotics project using a BeagleBone Black and have 
thoroughly enjoyed using it as a hardware platform. Recently, I've been 
working towards getting a rotary encoder reading up and running using your 
eQEP method, but, being inexperienced with Linux kernel compilation, have 
run into a problem I can't seem to solve. I've made it through most of 
Derek Molloy's tutorial and patched it with your eqep script, but haven't 
figured out how to deploy the image to SD card. Instead of install_image.sh 
in the linux-dev/tools directory, all I have is install_kernel.sh. Having 
configured the system.sh MMC variable for my SD card (/dev/sdd), I run the 
script, it asks the "are you 100% sure" question, I enter "y", then it 
unmounts, displays the partitions on the card, and the script finishes 
without copying anything onto the card. Any advice or input would be 
greatly appreciated! I admit I don't really know what I'm doing, but I've 
searched and searched for an answer and haven't found one yet. 

Thanks,
Willie

On Thursday, July 25, 2013 2:38:29 AM UTC-5, Teknoman117 wrote:
>
> Its just a work in progress, but here's what I have now that its midnight. 
>  Tomorrow I'll through together some documentation, test it further, and 
> put together an API.  Essentially in its current form its a couple of 
> device tree overlays, a kernel patch (been using Robert's linux-dev 
> am33x-v3.8 kernel) which puts in the driver, and there is an example of 
> polling the position attribute.  I'll put some docs together tomorrow, I'm 
> tired.
>
> https://github.com/Teknoman117/beaglebot/tree/master/encoders
>
> Nathaniel Lewis
> CTO at E1FTW Games
> 3rd year Undergraduate, Computer Science and Engineering
> Project Manager for the Robotics Society at UC Merced
> Undergraduate Lab Technician Intern at MESA Labs
> (925) 961 7578
> linux.r...@gmail.com 
>
> On Jul 24, 2013, at 12:18 PM, Nathaniel Lewis 
> > 
> wrote:
>
> I've actually put together a kernel driver for the eQEP hardware that 
> presents a poll able sysfs interface.  It plugs beautifully into the device 
> tree, and supports absolute and relative modes.  Relative resets the 
> counter and notifies a polling program based on a provided period, which 
> drives the eQEP unit timer.  I'm posting all my code to my blog and to 
> github today.
>
> - Nathaniel Lewis
>
> On Wednesday, July 24, 2013, tbh wrote:
>
>> My overall goal is like the title says: I need to read a quad encoder 
>> count, and I have a beaglebone black.  Eventually, I'll be using c++.  Any 
>> help on how to proceed or links on things I should read are appreciated.
>>
>> I've seen 3 ways of reading an encoder on the beaglebone: (1)polling 
>> GPIO 
>> pins,
>>  
>> (2)using interrupts in a kernel driver, and (3)using the eQEP built in to 
>> the hardware of the beaglebone SOC.  I'm interested in (3) because it seems 
>> to me that it would be the most efficient. However, it seems like most 
>> people are using (2), and I can't find a whole lot on how to do (3). 
>>
>> Here's what I have found so far in case it's useful to anyone else.
>> - the TRM for the bealgebone 
>> SOC. 
>> Section 15.4 is where the eQEP is documented.
>> - A thread 
>> hereapparently
>>  about enhancing an already working eQEP driver.
>> - A thread from the TI Community asking about linux drivers for 
>> eQEP
>> .
>> - A wiki page from a TI presentation about using eQEP with one of their 
>> dev 
>> boards
>> .
>> - Two threads with the same original post, and slightly different 
>> responses. They are a bit over my head. 
>> thread1 
>> thread2 
>> - A reference in some comments on a blog 
>> postthat
>>  they got an eQEP driver working to read a quad encoder (but without 
>> any explanation).
>>
>> I know people are working on the problem of making (3) easy to use. Is 
>> there some other link on how to do it that is eluding me?  
>>
>> If there's not, in the meantime, I'm interested in device drivers, and I 
>> think it's practical information, so I'd like to learn as much about them 
>> as I can. Perhaps I'll even get to the point where I can help the ongoing 
>> eQEP effort. 

Re: [beagleboard] RFC: Universal Device Tree

[Charles Steinkuehler]

On 1/28/2014 12:04 AM, William Hermans wrote:
> 
> *"I'm currently leaning towards 'dt-bone-universal', but I'm open to*
> *suggestions."*
> 
> how about something like bone-gpio-universal ? Maybe even
> bone-gpio-default? Personally i think adding "dt" to the name is pretty

After sleeping on it, I am now leaning towards:

  beaglebone-universal-io (github project name)
  bone-universal-00A0.dts (device tree file name)

You're right that dt is fairly redundant, and the whole point of this
exercise is to make it possible to access special hardware modes (pwm,
spi, etc) from userspace.  It's already possible to do that with gpio,
so including gpio in the name seems limiting.

-- 
Charles Steinkuehler
char...@steinkuehler.net

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [beagleboard] Re: espeak in beaglebone black

[Md.Ss 123]

thanks all for assistance.i've configured the asound.conf file and got
espeak in action. :)


On Mon, Jan 27, 2014 at 6:38 AM, KurtE  wrote:

> Earlier when I was using Angstrom, I ended up having to download and build
> Espeak, but when I converted to the Debian versions, I could install it as
> you mentioned.
>
> However the PCM I believe is always defaulting to output to the HDMI
> sound.  To get it to work with a USB sound card I plugged in, I found I
> needed to edit a sound configuration file: Here is what I have:
>
> kurt@BeagleBone:~$ cat /etc/asound.conf
> pcm.!default sysdefault:Device
>
>
>
> On Sunday, January 26, 2014 6:35:46 AM UTC-8, ss sefat wrote:
>>
>> i want to use espeak on beaglebone black . i simply did "opkg install
>> espeak" to install espeak . bt when i write command in command prompt to
>> speak something it produced no sound . i used 'espeak "hello espeak" '. how
>> can i make espeak to work on beaglebone black.plz help me. thanks in
>> advance.
>>
>  --
> 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/t70cbmDYh4Y/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/groups/opt_out.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[beagleboard] Uart star and stop bit.

[Anders]

Hello,

Is there's a way how I can send a minimum of 11 (LOW) bits over the UART 
without being interrupted by the UART's start and stop bit? Do i need to 
modify some UART setting even though in general UART automatically adds 
start and stop bit and it cannot be removed. I really need at the beginning 
of communication to get 13-26 (LOW bits) followed by standard serial 
communication .

Regards,

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[beagleboard] BeagleBone Power switch problems.

[nevans31]

Hi,

When powering down the BBB using S3 (Power) it works fine when powered via 
USB or 5v DC input. I have wired a battery to the testpoints that go to the 
PMIC (U2) and the switch no longer functions as expected. It shuts down but 
then immediately restarts.

Any Ideas?

Many Thanks!

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[beagleboard] Beaglebone Ethernet Not working with 10/100 switch

[nevans31]

Hi,

Does anybody know why my beaglebone won't obtain an ethernet IP address 
when connected through a 10/100 ethernet switch?
It works fine when connected directly to a router.

Many Thanks!

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [beagleboard] Re: How to increase appearance time of penguin logo..?

[Kishor Dhanawade]

Hello Doug,
I am not expert with linux. Can you please guide me about
which file I need to study and edit from kernel source to achieve my
purpose?? Thanking you.


On Mon, Jan 27, 2014 at 5:48 AM, doog  wrote:

> that would probably be part of the init scripts. Since it's not beagle
> related and is instead a GNU/Linux thing, you should be able to google what
> manages the spash screen and switching to the log console.  Once you find
> this you'll likely have to do the changes in the initramfs structure and
> rebuild/compress it.
>
> Doug
>
> --
> 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/04U3ssflXoM/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/groups/opt_out.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[Micka]

Well, It's good that it works in other device :)

Micka,


On Mon, Jan 27, 2014 at 9:32 PM, Terry Storm  wrote:

> Brilliant
>
> Thank you Robert, and thank you Micka for the patch.
>
> Just ran it up, booted from SD card and I cant fault the touch in the few
> minutes I have played with it.
> Great news, thank you both.
>
> Will continue to test.
>
> Terry
>
> On Tuesday, 28 January 2014 02:45:40 UTC+13, RobertCNelson wrote:
>
>> On Mon, Jan 27, 2014 at 4:36 AM, Terry Storm 
>> wrote:
>> > Great news
>> >
>> > Can someone please link me to the latest Debian/Ubuntu image which
>> features
>> > this fix? Is there is pre-made image available, or do I need to build
>> it?
>> > Ditto for Arch Linux, would love to try that one out too with the fix
>> for
>> > that.
>>
>> 
>> https://groups.google.com/d/msg/beagleboard/w9PfhGkByQU/bE_BNG4vgHgJ
>>
>> Regards,
>>
>> --
>> Robert Nelson
>> http://www.rcn-ee.com/
>>
>  --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.