Re: [beagleboard] conflict with "cape-bone-iio" overlay and simple pinmux overlay?

[Chris Falk]

Wow, that was totally it!!  Changed the helper name and now both overlays 
are working together.  Ugh, this one had me tearing my hair out for a 
while..  Wish there was a debug/error print or something in dmesg to make 
it more obvious..  Hey thanks so much for your help Jason!

On Friday, February 21, 2014 7:21:36 PM UTC-6, Jason Kridner wrote:
>
>
>
>
> On Fri, Feb 21, 2014 at 3:53 PM, > wrote:
>
>> Hi Jason,
>>
>> Yes, I was using Derek Molloy's DTS file as a template.  The only 
>> difference is that I edited it for the following
>>
>> 0x198 0x37  /* P9_30 102 OUTPUT MODE7 */
>>
>> I posted the relevant dmesg output in my first post.  I wasn't sure how 
>> to attach a file to this thread...
>>
>> Guy:
>>   I did look at both DTS files and as far as I could tell there is not a 
>> conflict with pins.  I also tried assigning other GPIO pins values, and 
>> those did not take effect either.
>>
>
> My first guess is it is the name 'helper' that is in conflict with names 
> in the other part of the device tree. Try renaming 'helper' to 
> 'my_pin_helper' or something fun like that. Just a shot in the dark, but 
> I've run into a similar sort of problem before.
>  
>
>>
>> On Friday, February 21, 2014 2:17:36 PM UTC-6, Jason Kridner wrote:
>>>
>>>
>>>
>>>
>>> On Fri, Feb 21, 2014 at 2:47 PM,  wrote:
>>>
 Hello,

 I am trying to use both the "cape-bone-iio" device tree overlay for 
 analog input, and a simple pin-muxing overlay (see attached DTS file) 

>>>
>>> I don't see an attachment. Googling for the name I found 
>>> https://github.com/derekmolloy/boneDeviceTree/
>>> blob/master/overlay/DM-GPIO-Test.dts. Is this the same file or did you 
>>> edit it?
>>>  
>>>
 to change the direction of various gpio pins.  Although they both work 
 on their own, it seems that there is a problem when loaded together.  The 
 first overlay always works, and the second *seems* to load just fine, but 
 does not take effect..

 *Example 1 (first load cape-bone-iio, then DM-GPIO-Test)*

 root@beaglebone:~# echo cape-bone-iio > $SLOTS
 [   70.330541] bone-capemgr bone_capemgr.8: part_number 
 'cape-bone-iio', version 'N/A'
 [   70.341287] bone-capemgr bone_capemgr.8: slot #7: generic override
 [   70.347943] bone-capemgr bone_capemgr.8: bone: Using override eeprom 
 data at slot 7
 [   70.355978] bone-capemgr bone_capemgr.8: slot #7: 'Override Board 
 Name,00A0,Override Manuf,cape-bone-iio'
 [   70.368667] bone-capemgr bone_capemgr.8: slot #7: Requesting part 
 number/version based 'cape-bone-iio-00A0.dtbo
 [   70.380219] bone-capemgr bone_capemgr.8: slot #7: Requesting 
 firmware 'cape-bone-iio-00A0.dtbo' for board-name 'Override Board Name', 
 version '00A0'
 [   70.395034] bone-capemgr bone_capemgr.8: slot #7: dtbo 
 'cape-bone-iio-00A0.dtbo' loaded; converting to live tree
 [   70.407309] bone-capemgr bone_capemgr.8: slot #7: #1 overlays
 [   70.421631] bone-iio-helper helper.14: ready
 [   70.433579] bone-capemgr bone_capemgr.8: slot #7: Applied #1 
 overlays.

 root@beaglebone:~# ls /sys/devices/ocp.2/helper.14/
 AIN0  AIN1  AIN2  AIN3AIN4  AIN5  AIN6  AIN7driver
 modalias  power  subsystem  uevent
 root@beaglebone:~# ls /sys/bus/iio/devices/iio\:device0
 bufferin_voltage0_raw  in_voltage2_raw  in_voltage4_raw  
 in_voltage6_raw  name   scan_elements  trigger
 devin_voltage1_raw  in_voltage3_raw  in_voltage5_raw  
 in_voltage7_raw  power  subsystem  uevent


 root@beaglebone:~# echo DM-GPIO-Test > $SLOTS
 [  286.033107] bone-capemgr bone_capemgr.8: part_number 'DM-GPIO-Test', 
 version 'N/A'
 [  286.043079] bone-capemgr bone_capemgr.8: slot #8: generic override
 [  286.049605] bone-capemgr bone_capemgr.8: bone: Using override eeprom 
 data at slot 8
 [  286.057622] bone-capemgr bone_capemgr.8: slot #8: 'Override Board 
 Name,00A0,Override Manuf,DM-GPIO-Test'
 [  286.071044] bone-capemgr bone_capemgr.8: slot #8: Requesting part 
 number/version based 'DM-GPIO-Test-00A0.dtbo
 [  286.082390] bone-capemgr bone_capemgr.8: slot #8: Requesting 
 firmware 'DM-GPIO-Test-00A0.dtbo' for board-name 'Override Board Name', 
 version '00A0'
 [  286.103360] bone-capemgr bone_capemgr.8: slot #8: dtbo 
 'DM-GPIO-Test-00A0.dtbo' loaded; converting to live tree
 [  286.115233] bone-capemgr bone_capemgr.8: slot #8: #2 overlays
 [  286.122388] bone-capemgr bone_capemgr.8: slot #8: Applied #2 
 overlays.

 root@beaglebone:~# cat $PINS | grep 998
 pin 102 (44e10998) 0027 pinctrl-single  *<-- 
 unchanged*

  0: 54:PF--- 
  1: 55:PF--- 
  2: 56:PF--- 
  3: 57:PF--- 
  4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G
  5: ff:P-O-L Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT

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

[Jason Kridner]

On Wed, Jan 29, 2014 at 4:09 PM, Robert Nelson wrote:

> Lets keep this going, round 4...
>
> First, for tracking please report all bugs to:
> http://bugs.elinux.org/projects/debian-image-releases
>
> Fixes:
> 3.8.13-bone37 -> 3.8.13-bone39
> * rs485 support from Micka
> * dir-changeable propery for gpio-of-helper from Charles
> * cape-bone-proto from me *(new default pinmux)
>
> New Packages:
> python-pip, python-setuptools, python2.7-dev
>
> Fixes:
> systemd: limit journal to 8Mb (should fix ever expandign /var/logs issues)
> cape-bone-proto loaded on bootup by /etc/default/capemgr
>

I have to say, I don't like this on by default. It drove my robot crazy!
Driving pins without detection seems like an overall BAD(tm) idea.


> chromium: 32.0.1700.76 -> 32.0.1700.102
> nodejs: 0.10.24 -> 0.10.25
> https://github.com/beagleboard/am335x_pru_package.git >
> /opt/source/am335x_pru_package
> multiarch: added /lib/ld-linux.so.3 (for those HelloWorld users with
> the wrong gcc "armel" compiler..)
> Adafruit_BBIO installed
> default apache moved from port 80 to 8080 (bonescript.socket takes over
> port 80)
> "grow_partition.sh" script for users of the microSD image..
> * cd /opt/scripts/
> * git pull
> * ./tools/grow_partition.sh
> * sudo reboot
> * (after a few minutes, df -h should use the whole disk..)
> bonescript-autorun.service enabled
>
> LCD3/LCD4/LCD7 users, xinput_calibrator is installed by default..
> Can you please compare 3.8.13-bone36 with 3.8.13-bone39 to test
> Micka's touchcreen fix?
>
> I've tried to make it very easy to test via:
>
> cd /opt/scripts/tools
> sudo ./update_kernel.sh --kernel v3.8.13-bone36
> sudo rm /etc/pointercal.xinput
> sudo reboot
>
> cd /opt/scripts/tools
> sudo ./update_kernel.sh --kernel v3.8.13-bone39
> sudo rm /etc/pointercal.xinput
> sudo reboot
>
> So please compare and contrast bone36/bone39, as we really need
> testing from users..
>
> Camera people (3.1MP and RadiumBoards):
> What userspace programs are we missing? gstreamer? OpenCV plugins?
>
> I really want to include a default shell script that'll take a picture
> and allow end users to validate the 3.1/Radium capes work.. (it'll be
> installed under /opt/scripts/capes/)  Or even some html5 bone101
> voodoo and show the image in the browser window?
>
> Questions? Should we switch to connman? (i'm still testing this too..)
>
> To test:
> apt-get remove wicd-* --purge
> apt-get install connman
> (no good gui with connman)
>
> Does your "cape" work?
>
> Does your wifi adapter work? Are we missing it's firmware?
>
> So go forward and test the first "beta" release. There are 3 files on
> the web server, depending on what you want to do. Using the same
> standard procedure found here:
> http://elinux.org/Beagleboard:Updating_The_Software
>
> http://rcn-ee.net/deb/testing/2014-01-29/
>
> 3cc218e9303c6823035585364e2de2c0
> ./BBB-eMMC-flasher-debian-7.3-2014-01-29-2gb.img.xz
> d7e00474379a85edcf6385bc9584466c  ./bone-debian-7.3-2014-01-29-2gb.img.xz
> 2d0c043b311cc31bd6286c4c2058b174  ./debian-7.3-lxde-armhf-2014-01-29.tar.xz
>
> An eMMC "flasher" which can be installed to any 2GB or greater microSD
> card. [BBB-eMMC-flasher-debian-7.3-2014-01-29-2gb.img.xz]
>
>
> http://rcn-ee.net/deb/testing/2014-01-29/BBB-eMMC-flasher-debian-7.3-2014-01-29-2gb.img.xz
>
> It takes about 10-15 Minutes to dd microSD (2GB), 15 minutes to flash
> eMMC (look for full 4 LED's)
>
> 2GB standalone image that can be flashed to any 2GB or greater.
> [bone-debian-7.3-2014-01-29-2gb.img.xz]
>
>
> http://rcn-ee.net/deb/testing/2014-01-29/bone-debian-7.3-2014-01-29-2gb.img.xz
>
> It takes about 10-15 Minutes to dd microSD (2GB)
>
> To resize once booted:
> * cd /opt/scripts/
> * git pull
> * ./tools/grow_partition.sh
> * sudo reboot
>
> Finally one of my classic "setup_sdcard.sh".
> [debian-7.3-lxde-armhf-2014-01-22.tar.xz]
>
>
> http://rcn-ee.net/deb/testing/2014-01-29/debian-7.3-lxde-armhf-2014-01-29.tar.xz
>
> Note for users who use my classic "setup_sdcard.sh" script, here is
> the magic options to get the beaglebone project files + systemd.
>
> sudo ./setup_sdcard.sh --mmc /dev/sdX --uboot bone
> --beagleboard.org-production --enable-systemd
>
> To "rebuild"
> git clone git://github.com/beagleboard/image-builder.git
> cd image-builder
> git checkout bb.org-v2014.01.29 -b tmp
> touch release
> ./beagleboard.org_image.sh
>
> --
> 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

Re: [beagleboard] conflict with "cape-bone-iio" overlay and simple pinmux overlay?

[Jason Kridner]

On Fri, Feb 21, 2014 at 3:53 PM,  wrote:

> Hi Jason,
>
> Yes, I was using Derek Molloy's DTS file as a template.  The only
> difference is that I edited it for the following
>
> 0x198 0x37  /* P9_30 102 OUTPUT MODE7 */
>
> I posted the relevant dmesg output in my first post.  I wasn't sure how to
> attach a file to this thread...
>
> Guy:
>   I did look at both DTS files and as far as I could tell there is not a
> conflict with pins.  I also tried assigning other GPIO pins values, and
> those did not take effect either.
>

My first guess is it is the name 'helper' that is in conflict with names in
the other part of the device tree. Try renaming 'helper' to 'my_pin_helper'
or something fun like that. Just a shot in the dark, but I've run into a
similar sort of problem before.


>
> On Friday, February 21, 2014 2:17:36 PM UTC-6, Jason Kridner wrote:
>>
>>
>>
>>
>> On Fri, Feb 21, 2014 at 2:47 PM,  wrote:
>>
>>> Hello,
>>>
>>> I am trying to use both the "cape-bone-iio" device tree overlay for
>>> analog input, and a simple pin-muxing overlay (see attached DTS file)
>>>
>>
>> I don't see an attachment. Googling for the name I found
>> https://github.com/derekmolloy/boneDeviceTree/
>> blob/master/overlay/DM-GPIO-Test.dts. Is this the same file or did you
>> edit it?
>>
>>
>>> to change the direction of various gpio pins.  Although they both work
>>> on their own, it seems that there is a problem when loaded together.  The
>>> first overlay always works, and the second *seems* to load just fine, but
>>> does not take effect..
>>>
>>> *Example 1 (first load cape-bone-iio, then DM-GPIO-Test)*
>>>
>>> root@beaglebone:~# echo cape-bone-iio > $SLOTS
>>> [   70.330541] bone-capemgr bone_capemgr.8: part_number 'cape-bone-iio',
>>> version 'N/A'
>>> [   70.341287] bone-capemgr bone_capemgr.8: slot #7: generic override
>>> [   70.347943] bone-capemgr bone_capemgr.8: bone: Using override eeprom
>>> data at slot 7
>>> [   70.355978] bone-capemgr bone_capemgr.8: slot #7: 'Override Board
>>> Name,00A0,Override Manuf,cape-bone-iio'
>>> [   70.368667] bone-capemgr bone_capemgr.8: slot #7: Requesting part
>>> number/version based 'cape-bone-iio-00A0.dtbo
>>> [   70.380219] bone-capemgr bone_capemgr.8: slot #7: Requesting firmware
>>> 'cape-bone-iio-00A0.dtbo' for board-name 'Override Board Name', version
>>> '00A0'
>>> [   70.395034] bone-capemgr bone_capemgr.8: slot #7: dtbo
>>> 'cape-bone-iio-00A0.dtbo' loaded; converting to live tree
>>> [   70.407309] bone-capemgr bone_capemgr.8: slot #7: #1 overlays
>>> [   70.421631] bone-iio-helper helper.14: ready
>>> [   70.433579] bone-capemgr bone_capemgr.8: slot #7: Applied #1 overlays.
>>>
>>> root@beaglebone:~# ls /sys/devices/ocp.2/helper.14/
>>> AIN0  AIN1  AIN2  AIN3AIN4  AIN5  AIN6  AIN7drivermodalias
>>> power  subsystem  uevent
>>> root@beaglebone:~# ls /sys/bus/iio/devices/iio\:device0
>>> bufferin_voltage0_raw  in_voltage2_raw  in_voltage4_raw
>>> in_voltage6_raw  name   scan_elements  trigger
>>> devin_voltage1_raw  in_voltage3_raw  in_voltage5_raw
>>> in_voltage7_raw  power  subsystem  uevent
>>>
>>>
>>> root@beaglebone:~# echo DM-GPIO-Test > $SLOTS
>>> [  286.033107] bone-capemgr bone_capemgr.8: part_number 'DM-GPIO-Test',
>>> version 'N/A'
>>> [  286.043079] bone-capemgr bone_capemgr.8: slot #8: generic override
>>> [  286.049605] bone-capemgr bone_capemgr.8: bone: Using override eeprom
>>> data at slot 8
>>> [  286.057622] bone-capemgr bone_capemgr.8: slot #8: 'Override Board
>>> Name,00A0,Override Manuf,DM-GPIO-Test'
>>> [  286.071044] bone-capemgr bone_capemgr.8: slot #8: Requesting part
>>> number/version based 'DM-GPIO-Test-00A0.dtbo
>>> [  286.082390] bone-capemgr bone_capemgr.8: slot #8: Requesting firmware
>>> 'DM-GPIO-Test-00A0.dtbo' for board-name 'Override Board Name', version
>>> '00A0'
>>> [  286.103360] bone-capemgr bone_capemgr.8: slot #8: dtbo
>>> 'DM-GPIO-Test-00A0.dtbo' loaded; converting to live tree
>>> [  286.115233] bone-capemgr bone_capemgr.8: slot #8: #2 overlays
>>> [  286.122388] bone-capemgr bone_capemgr.8: slot #8: Applied #2 overlays.
>>>
>>> root@beaglebone:~# cat $PINS | grep 998
>>> pin 102 (44e10998) 0027 pinctrl-single  *<--
>>> unchanged*
>>>
>>>  0: 54:PF---
>>>  1: 55:PF---
>>>  2: 56:PF---
>>>  3: 57:PF---
>>>  4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G
>>>  5: ff:P-O-L Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI
>>>  7: ff:P-O-L Override Board Name,00A0,Override Manuf,cape-bone-iio
>>>  8: ff:P-O-L Override Board Name,00A0,Override Manuf,DM-GPIO-Test
>>>
>>> *Example 2 (first load DM-GPIO-Test, then cape-bone-iio)*
>>>
>>> root@beaglebone:~# cat $PINS | grep 998
>>> pin 102 (44e10998) 0027 pinctrl-single  *<--
>>> default value*
>>>
>>> root@beaglebone:~# echo DM-GPIO-Test > $SLOTS
>>> [   90.459668] bone-capemgr bone_capemgr.8: part_number 'DM-GPIO-Test',
>>> version 'N/A'
>>> [   90.469663] bone-c

Re: [beagleboard] Re: Availability - how come nobody has any BeagleBone Black to sell?

[Gerald Coley]

eMMC for one. Schedules are extended out. You have some we can buy? Some of
the crystals as well.

Gerald



On Fri, Feb 21, 2014 at 4:58 PM, rh_  wrote:

> On Fri, 21 Feb 2014 15:19:58 -0600
> Gerald Coley  wrote:
>
> > Interesting. I am not sure Stephen King could stand the competition of
> > another horror writer!
> >
> > I will think it over!
>
> So which parts are in short supply?
>
> --
> 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 and Linux Drivers

[Richard Rice]

Hey everyone,

I'm having some issues with some Linux drivers on Black and need some 
direct help. Please email me directly if interested or know someone in the 
Bay Area, CA that can.

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] USB port not working on my BeagleBone Black

[ajith92]

Hey brian smith have u worked on kinect after connecting into beagle 
bone ?? my kinect s recognized by the BBB ... wat should i do after tat


On Thursday, 1 August 2013 05:36:52 UTC+5:30, Brian Smith wrote:
>
> Hello Isaac,
>
> I have the Kinect running on my Beaglebone using a powered USB hub. I'm 
> not sure if that's why you're having the problem or not; I actually ran 
> across your post while researching if the powered USB hub is necessary when 
> connecting the Kinect to the BB since I want to get the whole setup mobile 
> on batteries or something.
>
> The USB hub that I'm using is Belkin model#: F4U040.
>
> Brian
>
> On Wednesday, July 24, 2013 12:53:15 PM UTC-7, Isaac Flores wrote:
>>
>>
>>
>> On Wednesday, July 24, 2013 12:02:18 PM UTC-7, Gerald wrote:
>>>
>>> What you describe is the way it works. You have to have the device or a 
>>> Hub plugged in on power up for it to be recognized.
>>>
>>> Gerald
>>>
>>>
>>>
>>> On Wed, Jul 24, 2013 at 1:54 PM,  wrote:
>>>
 Hello, 

 I booted my BeagleBone Black A5B with Raring Ubuntu 13.04. I used the 
 image from:

 http://rcn-ee.net/deb/rootfs/raring/ubuntu-13.04-console-armhf-2013-07-22.tar.xz

 I followed the steps from the elinux.org using the sd_setup script. Then I 
 was able to install OpenCV, OpenNI,and PrimeSense Kinect Driver.
 When I plugged in the Kinect, the board did not read it and the Kinect did 
 not power on. I tried *lsusb *and it was not reading the Kinect. 

 Then *dmesg | tail* gave me the following : 
 *[ 5981.901031]  gadget: sending command-failure status*


 After this I tried to connect my logitech webcam. The board did not read 
 as well, so then I rebooted the board with with the camera plugged in the 

 usb port. Once it booted the camera was recognized. I then tried the same 
 with the Kinect, but it still did not turn on the Kinect camera. After 
 that I 
 tried using a USB splitter, more specifically a "Media-To-Go.com 7-in-1 
 Card Reader with USB HUB". In order the USB Hub to work, I had to reboot 
 with it plugged in, 

 I then connected the Kinect to this and it turned on. Also *lsusb *showed 
 the Kinect was working. So I tried running an OpenNI sample program but it 
 would fail saying the Kinect was not connected.

 So is there something wrong with my USB port? My driver? Also do I need to 
 reboot the board with a device plugged in for it to read it?

 Any help will be greatly appreciated. Thank you in advanced! 




  -- 
 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: Availability - how come nobody has any BeagleBone Black to sell?

[Gerald Coley]

Interesting. I am not sure Stephen King could stand the competition of
another horror writer!

I will think it over!

Gerald



On Fri, Feb 21, 2014 at 3:13 PM, Przemek Klosowski <
przemek.klosow...@gmail.com> wrote:

> On Fri, Feb 21, 2014 at 12:46 PM, Gerald Coley 
> wrote:
> > I appreciate the feedback ! We are all busting it to get things back up
> to
> > the new norm! There is a long line of people between us and the parts we
> > need.
> >
> Can you say which parts are the bottleneck?
>
> Your experience spinning up this amazing operation is quite unique and
> it would be a great resource to other budding entrepreneurs if you
> would write your story.  Others could definitely learn from where the
> difficulties were and how you resolved them, especially if you didn't
> expect them to be hard beforehand.
>
> --
> 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: Availability - how come nobody has any BeagleBone Black to sell?

[Eric Palmer]

Gerald

The BBB is an amazing piece of work. It has gotten me excited about
embedded systems like never before. Thanks


On Fri, Feb 21, 2014 at 12:46 PM, Gerald Coley wrote:

> I appreciate the feedback ! We are all busting it to get things back up to
> the new norm! There is a long line of people between us and the parts we
> need.
>
> Gerald
>
>
>
> On Fri, Feb 21, 2014 at 11:37 AM, doog  wrote:
>
>>
>>
>> On Friday, February 21, 2014 8:02:46 AM UTC-8, Gerald wrote:
>>>
>>> I just oversee the manufacturing and support of beagleboard.org. Any
>>> other issues are theirs.
>>>
>>> Gerald
>>>
>>>
>> And you are doing one heck of a good job! I sure hope you don't let the
>> few who keep complaining make you feel like you're not. So please keep up
>> the good work and brush off the digs that you're not doing enough and try
>> to enjoy what you're doing. Some of us appreciate your efforts bringing
>> such an awesome board to us individuals so we can enjoy your efforts and do
>> great things with it.
>>
>> 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.
>>
>
>  --
> 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.
>



-- 
Eric Palmer

-- 
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: Availability - how come nobody has any BeagleBone Black to sell?

[Przemek Klosowski]

On Fri, Feb 21, 2014 at 12:46 PM, Gerald Coley  wrote:
> I appreciate the feedback ! We are all busting it to get things back up to
> the new norm! There is a long line of people between us and the parts we
> need.
>
Can you say which parts are the bottleneck?

Your experience spinning up this amazing operation is quite unique and
it would be a great resource to other budding entrepreneurs if you
would write your story.  Others could definitely learn from where the
difficulties were and how you resolved them, especially if you didn't
expect them to be hard beforehand.

-- 
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] Failed angstrom build

[Artie Lekstutis]

Have you tried the directions on http://www.angstrom-distribution.org/? 
That worked fine for me the last time I ran it in a VirtualBox VM 
running Ubuntu 12.04.3 64 bits.


I've had trouble with some of what Derek Molloy documented, especially 
after the referenced toolchain was removed from angstrom-distribution.org


Artie

On 1/20/2014 5:54 AM, Jeremy Van wrote:
I'm trying to build Angstrom with bitbake. I followed the instructions 
on Derek Molloy's Site 
.  After 
running:


$bitbake cloud9-image


| ERROR: ld.so: object 'libpseudo.so' from LD_PRELOAD cannot be 
preloaded: ignored.
| update-alternatives: Linking 
/home/jay/angstrom/setup-scripts/build/tmp-angstrom_v2013_06-eglibc/work/beaglebone-angstrom-linux-gnueabi/cloud9-image/1.0-r0/rootfs//usr/bin/top 
to /usr/bin/top.procps
| update-alternatives: Linking 
/home/jay/angstrom/setup-scripts/build/tmp-angstrom_v2013_06-eglibc/work/beaglebone-angstrom-linux-gnueabi/cloud9-image/1.0-r0/rootfs//usr/bin/uptime 
to /usr/bin/uptime.procps
| update-alternatives: Linking 
/home/jay/angstrom/setup-scripts/build/tmp-angstrom_v2013_06-eglibc/work/beaglebone-angstrom-linux-gnueabi/cloud9-image/1.0-r0/rootfs//usr/bin/free 
to /usr/bin/free.procps
| update-alternatives: Linking 
/home/jay/angstrom/setup-scripts/build/tmp-angstrom_v2013_06-eglibc/work/beaglebone-angstrom-linux-gnueabi/cloud9-image/1.0-r0/rootfs//usr/bin/pkill 
to /usr/bin/pkill.procps
| update-alternatives: Linking 
/home/jay/angstrom/setup-scripts/build/tmp-angstrom_v2013_06-eglibc/work/beaglebone-angstrom-linux-gnueabi/cloud9-image/1.0-r0/rootfs//usr/bin/pmap 
to /usr/bin/pmap.procps

|
| ERROR: Function failed: do_rootfs (see 
/home/jay/angstrom/setup-scripts/build/tmp-angstrom_v2013_06-eglibc/work/beaglebone-angstrom-linux-gnueabi/cloud9-image/1.0-r0/temp/log.do_rootfs.20961 
for further information)
ERROR: Task 7 
(/home/jay/angstrom/setup-scripts/sources/meta-ti/recipes-misc/images/cloud9-image.bb, 
do_rootfs) failed with exit code '1'
NOTE: Tasks Summary: Attempted 5589 tasks of which 5588 didn't need to 
be rerun and 1 failed.

No currently running tasks (5588 of 5592)

Summary: 1 task failed:
/home/jay/angstrom/setup-scripts/sources/meta-ti/recipes-misc/images/cloud9-image.bb, 
do_rootfs

Summary: There was 1 WARNING message shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.

Has anyone had any similar problems?
--
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] conflict with "cape-bone-iio" overlay and simple pinmux overlay?

[cfalk3]

Hi Jason,

Yes, I was using Derek Molloy's DTS file as a template.  The only 
difference is that I edited it for the following

0x198 0x37  /* P9_30 102 OUTPUT MODE7 */

I posted the relevant dmesg output in my first post.  I wasn't sure how to 
attach a file to this thread...

Guy:
  I did look at both DTS files and as far as I could tell there is not a 
conflict with pins.  I also tried assigning other GPIO pins values, and 
those did not take effect either.

On Friday, February 21, 2014 2:17:36 PM UTC-6, Jason Kridner wrote:
>
>
>
>
> On Fri, Feb 21, 2014 at 2:47 PM, > wrote:
>
>> Hello,
>>
>> I am trying to use both the "cape-bone-iio" device tree overlay for 
>> analog input, and a simple pin-muxing overlay (see attached DTS file) 
>>
>
> I don't see an attachment. Googling for the name I found 
> https://github.com/derekmolloy/boneDeviceTree/blob/master/overlay/DM-GPIO-Test.dts.
>  
> Is this the same file or did you edit it?
>  
>
>> to change the direction of various gpio pins.  Although they both work on 
>> their own, it seems that there is a problem when loaded together.  The 
>> first overlay always works, and the second *seems* to load just fine, but 
>> does not take effect..
>>
>> *Example 1 (first load cape-bone-iio, then DM-GPIO-Test)*
>>
>> root@beaglebone:~# echo cape-bone-iio > $SLOTS
>> [   70.330541] bone-capemgr bone_capemgr.8: part_number 'cape-bone-iio', 
>> version 'N/A'
>> [   70.341287] bone-capemgr bone_capemgr.8: slot #7: generic override
>> [   70.347943] bone-capemgr bone_capemgr.8: bone: Using override eeprom 
>> data at slot 7
>> [   70.355978] bone-capemgr bone_capemgr.8: slot #7: 'Override Board 
>> Name,00A0,Override Manuf,cape-bone-iio'
>> [   70.368667] bone-capemgr bone_capemgr.8: slot #7: Requesting part 
>> number/version based 'cape-bone-iio-00A0.dtbo
>> [   70.380219] bone-capemgr bone_capemgr.8: slot #7: Requesting firmware 
>> 'cape-bone-iio-00A0.dtbo' for board-name 'Override Board Name', version 
>> '00A0'
>> [   70.395034] bone-capemgr bone_capemgr.8: slot #7: dtbo 
>> 'cape-bone-iio-00A0.dtbo' loaded; converting to live tree
>> [   70.407309] bone-capemgr bone_capemgr.8: slot #7: #1 overlays
>> [   70.421631] bone-iio-helper helper.14: ready
>> [   70.433579] bone-capemgr bone_capemgr.8: slot #7: Applied #1 overlays.
>>
>> root@beaglebone:~# ls /sys/devices/ocp.2/helper.14/
>> AIN0  AIN1  AIN2  AIN3AIN4  AIN5  AIN6  AIN7drivermodalias  
>> power  subsystem  uevent
>> root@beaglebone:~# ls /sys/bus/iio/devices/iio\:device0
>> bufferin_voltage0_raw  in_voltage2_raw  in_voltage4_raw  
>> in_voltage6_raw  name   scan_elements  trigger
>> devin_voltage1_raw  in_voltage3_raw  in_voltage5_raw  
>> in_voltage7_raw  power  subsystem  uevent
>>
>>
>> root@beaglebone:~# echo DM-GPIO-Test > $SLOTS
>> [  286.033107] bone-capemgr bone_capemgr.8: part_number 'DM-GPIO-Test', 
>> version 'N/A'
>> [  286.043079] bone-capemgr bone_capemgr.8: slot #8: generic override
>> [  286.049605] bone-capemgr bone_capemgr.8: bone: Using override eeprom 
>> data at slot 8
>> [  286.057622] bone-capemgr bone_capemgr.8: slot #8: 'Override Board 
>> Name,00A0,Override Manuf,DM-GPIO-Test'
>> [  286.071044] bone-capemgr bone_capemgr.8: slot #8: Requesting part 
>> number/version based 'DM-GPIO-Test-00A0.dtbo
>> [  286.082390] bone-capemgr bone_capemgr.8: slot #8: Requesting firmware 
>> 'DM-GPIO-Test-00A0.dtbo' for board-name 'Override Board Name', version 
>> '00A0'
>> [  286.103360] bone-capemgr bone_capemgr.8: slot #8: dtbo 
>> 'DM-GPIO-Test-00A0.dtbo' loaded; converting to live tree
>> [  286.115233] bone-capemgr bone_capemgr.8: slot #8: #2 overlays
>> [  286.122388] bone-capemgr bone_capemgr.8: slot #8: Applied #2 overlays.
>>
>> root@beaglebone:~# cat $PINS | grep 998
>> pin 102 (44e10998) 0027 pinctrl-single  *<-- 
>> unchanged*
>>
>>  0: 54:PF--- 
>>  1: 55:PF--- 
>>  2: 56:PF--- 
>>  3: 57:PF--- 
>>  4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G
>>  5: ff:P-O-L Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI
>>  7: ff:P-O-L Override Board Name,00A0,Override Manuf,cape-bone-iio
>>  8: ff:P-O-L Override Board Name,00A0,Override Manuf,DM-GPIO-Test
>>
>> *Example 2 (first load DM-GPIO-Test, then cape-bone-iio)*
>>
>> root@beaglebone:~# cat $PINS | grep 998  
>> pin 102 (44e10998) 0027 pinctrl-single  *<-- 
>> default value*
>>
>> root@beaglebone:~# echo DM-GPIO-Test > $SLOTS
>> [   90.459668] bone-capemgr bone_capemgr.8: part_number 'DM-GPIO-Test', 
>> version 'N/A'
>> [   90.469663] bone-capemgr bone_capemgr.8: slot #7: generic override
>> [   90.476312] bone-capemgr bone_capemgr.8: bone: Using override eeprom 
>> data at slot 7
>> [   90.484332] bone-capemgr bone_capemgr.8: slot #7: 'Override Board 
>> Name,00A0,Override Manuf,DM-GPIO-Test'
>> [   90.496939] bone-capemgr bone_capemgr.8: slot #7: Requesting part 
>> number/version based 'DM-GPIO-Test-00A0.dtbo

Re: [beagleboard] conflict with "cape-bone-iio" overlay and simple pinmux overlay?

[Guy Grotke]

They probably have a collision on one or more pins.  Have you looked at their 
respective .dts files to see if there is a conflict?  Try assigning pins to one 
or the other.
My (very limited) experience with the cape manager leads me to believe it is 
not very good about giving you informative messages when there is a conflict or 
defective .dtbo file.


From: cfa...@gmail.com 
Sent: Friday, February 21, 2014 11:47 AM
To: beagleboard@googlegroups.com 
Subject: [beagleboard] conflict with "cape-bone-iio" overlay and simple pinmux 
overlay?

Hello,

I am trying to use both the "cape-bone-iio" device tree overlay for analog 
input, and a simple pin-muxing overlay (see attached DTS file) to change the 
direction of various gpio pins.  Although they both work on their own, it seems 
that there is a problem when loaded together.  The first overlay always works, 
and the second *seems* to load just fine, but does not take effect..

Example 1 (first load cape-bone-iio, then DM-GPIO-Test)


root@beaglebone:~# echo cape-bone-iio > $SLOTS
[   70.330541] bone-capemgr bone_capemgr.8: part_number 'cape-bone-iio', 
version 'N/A'
[   70.341287] bone-capemgr bone_capemgr.8: slot #7: generic override
[   70.347943] bone-capemgr bone_capemgr.8: bone: Using override eeprom data at 
slot 7
[   70.355978] bone-capemgr bone_capemgr.8: slot #7: 'Override Board 
Name,00A0,Override Manuf,cape-bone-iio'
[   70.368667] bone-capemgr bone_capemgr.8: slot #7: Requesting part 
number/version based 'cape-bone-iio-00A0.dtbo
[   70.380219] bone-capemgr bone_capemgr.8: slot #7: Requesting firmware 
'cape-bone-iio-00A0.dtbo' for board-name 'Override Board Name', version '00A0'
[   70.395034] bone-capemgr bone_capemgr.8: slot #7: dtbo 
'cape-bone-iio-00A0.dtbo' loaded; converting to live tree
[   70.407309] bone-capemgr bone_capemgr.8: slot #7: #1 overlays
[   70.421631] bone-iio-helper helper.14: ready
[   70.433579] bone-capemgr bone_capemgr.8: slot #7: Applied #1 overlays.

root@beaglebone:~# ls /sys/devices/ocp.2/helper.14/
AIN0  AIN1  AIN2  AIN3AIN4  AIN5  AIN6  AIN7drivermodalias  power  
subsystem  uevent
root@beaglebone:~# ls /sys/bus/iio/devices/iio\:device0
bufferin_voltage0_raw  in_voltage2_raw  in_voltage4_raw  in_voltage6_raw  
name   scan_elements  trigger
devin_voltage1_raw  in_voltage3_raw  in_voltage5_raw  in_voltage7_raw  
power  subsystem  uevent




root@beaglebone:~# echo DM-GPIO-Test > $SLOTS
[  286.033107] bone-capemgr bone_capemgr.8: part_number 'DM-GPIO-Test', version 
'N/A'
[  286.043079] bone-capemgr bone_capemgr.8: slot #8: generic override
[  286.049605] bone-capemgr bone_capemgr.8: bone: Using override eeprom data at 
slot 8
[  286.057622] bone-capemgr bone_capemgr.8: slot #8: 'Override Board 
Name,00A0,Override Manuf,DM-GPIO-Test'
[  286.071044] bone-capemgr bone_capemgr.8: slot #8: Requesting part 
number/version based 'DM-GPIO-Test-00A0.dtbo
[  286.082390] bone-capemgr bone_capemgr.8: slot #8: Requesting firmware 
'DM-GPIO-Test-00A0.dtbo' for board-name 'Override Board Name', version '00A0'
[  286.103360] bone-capemgr bone_capemgr.8: slot #8: dtbo 
'DM-GPIO-Test-00A0.dtbo' loaded; converting to live tree
[  286.115233] bone-capemgr bone_capemgr.8: slot #8: #2 overlays
[  286.122388] bone-capemgr bone_capemgr.8: slot #8: Applied #2 overlays.

root@beaglebone:~# cat $PINS | grep 998
pin 102 (44e10998) 0027 pinctrl-single  <-- unchanged

0: 54:PF--- 
1: 55:PF--- 
2: 56:PF--- 
3: 57:PF--- 
4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G
5: ff:P-O-L Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI
7: ff:P-O-L Override Board Name,00A0,Override Manuf,cape-bone-iio
8: ff:P-O-L Override Board Name,00A0,Override Manuf,DM-GPIO-Test


Example 2 (first load DM-GPIO-Test, then cape-bone-iio)


root@beaglebone:~# cat $PINS | grep 998  
pin 102 (44e10998) 0027 pinctrl-single  <-- default 
value

root@beaglebone:~# echo DM-GPIO-Test > $SLOTS
[   90.459668] bone-capemgr bone_capemgr.8: part_number 'DM-GPIO-Test', version 
'N/A'
[   90.469663] bone-capemgr bone_capemgr.8: slot #7: generic override
[   90.476312] bone-capemgr bone_capemgr.8: bone: Using override eeprom data at 
slot 7
[   90.484332] bone-capemgr bone_capemgr.8: slot #7: 'Override Board 
Name,00A0,Override Manuf,DM-GPIO-Test'
[   90.496939] bone-capemgr bone_capemgr.8: slot #7: Requesting part 
number/version based 'DM-GPIO-Test-00A0.dtbo
[   90.508493] bone-capemgr bone_capemgr.8: slot #7: Requesting firmware 
'DM-GPIO-Test-00A0.dtbo' for board-name 'Override Board Name', version '00A0'
[   90.530293] bone-capemgr bone_capemgr.8: slot #7: dtbo 
'DM-GPIO-Test-00A0.dtbo' loaded; converting to live tree
[   90.542078] bone-capemgr bone_capemgr.8: slot #7: #2 overlays
[   90.554967] bone-capemgr bone_capemgr.8: slot #7: Applied #2 overlays.

root@beaglebone:~# cat $PINS | grep 998
pin 102 (44e10998) 0037 pinctrl-single  <-- expected 
value from what wa

Re: [beagleboard] Re: Audio Cape Rev B schematics ?

[David Anders]

yes but it won't be posted until we are ready to ship...

Dave


On Friday, February 21, 2014 2:04:28 PM UTC-6, john3909 wrote:
>
>
>
> From: David Anders >
> Reply-To: >
> Date: Friday, February 21, 2014 at 8:18 AM
> To: >
> Subject: [beagleboard] Re: Audio Cape Rev B schematics ?
>
> Valentin,
>
> the audio cape revb is in production now and should be available for 
> purchase within 14 to 21 days.
>
> the design files for the audio cape revb are available on the wiki page: 
> http://www.elinux.org/CircuitCo:Audio_Cape_RevB#Documentations
>
> Do you have a device tree overlay for this board?
>
>
>
> On Wednesday, February 19, 2014 4:01:21 AM UTC-6, Valentin Le bescond 
> wrote:
>>
>> Hello everyone !
>>
>> First question for me on this group... big day...
>>
>> I am looking for BeagleBone audio cape Rev B schematics (announced @ 
>> elinux.com). Does anyone know who I might ask for it ?
>>
>> In other words, I have been waiting for a month an a half to be able to 
>> buy a audio cape (in France) an so far every "where to buy" is out of stock.
>>
>> But anyway I wanted to make a custom audio cape based on the available 
>> one.
>>
>> I looked at the schematics (Rev A) and saw there was a lot of DVI things 
>> in it. Then I saw a yet-to-come Rev B with what seems to be a much cleaner 
>> PCB (audio only ?). Plus it has a AIC3104 (instead of the 3106) which adds 
>> selectable bias voltage !
>>
>> So : nowhere to buy + available schematics (I hope) = let's build it !
>>
>> Does anyone have any info that could help me getting started ? 
>>
>> 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...@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] conflict with "cape-bone-iio" overlay and simple pinmux overlay?

[Jason Kridner]

On Fri, Feb 21, 2014 at 2:47 PM,  wrote:

> Hello,
>
> I am trying to use both the "cape-bone-iio" device tree overlay for analog
> input, and a simple pin-muxing overlay (see attached DTS file)
>

I don't see an attachment. Googling for the name I found
https://github.com/derekmolloy/boneDeviceTree/blob/master/overlay/DM-GPIO-Test.dts.
Is this the same file or did you edit it?


> to change the direction of various gpio pins.  Although they both work on
> their own, it seems that there is a problem when loaded together.  The
> first overlay always works, and the second *seems* to load just fine, but
> does not take effect..
>
> *Example 1 (first load cape-bone-iio, then DM-GPIO-Test)*
>
> root@beaglebone:~# echo cape-bone-iio > $SLOTS
> [   70.330541] bone-capemgr bone_capemgr.8: part_number 'cape-bone-iio',
> version 'N/A'
> [   70.341287] bone-capemgr bone_capemgr.8: slot #7: generic override
> [   70.347943] bone-capemgr bone_capemgr.8: bone: Using override eeprom
> data at slot 7
> [   70.355978] bone-capemgr bone_capemgr.8: slot #7: 'Override Board
> Name,00A0,Override Manuf,cape-bone-iio'
> [   70.368667] bone-capemgr bone_capemgr.8: slot #7: Requesting part
> number/version based 'cape-bone-iio-00A0.dtbo
> [   70.380219] bone-capemgr bone_capemgr.8: slot #7: Requesting firmware
> 'cape-bone-iio-00A0.dtbo' for board-name 'Override Board Name', version
> '00A0'
> [   70.395034] bone-capemgr bone_capemgr.8: slot #7: dtbo
> 'cape-bone-iio-00A0.dtbo' loaded; converting to live tree
> [   70.407309] bone-capemgr bone_capemgr.8: slot #7: #1 overlays
> [   70.421631] bone-iio-helper helper.14: ready
> [   70.433579] bone-capemgr bone_capemgr.8: slot #7: Applied #1 overlays.
>
> root@beaglebone:~# ls /sys/devices/ocp.2/helper.14/
> AIN0  AIN1  AIN2  AIN3AIN4  AIN5  AIN6  AIN7drivermodalias
> power  subsystem  uevent
> root@beaglebone:~# ls /sys/bus/iio/devices/iio\:device0
> bufferin_voltage0_raw  in_voltage2_raw  in_voltage4_raw
> in_voltage6_raw  name   scan_elements  trigger
> devin_voltage1_raw  in_voltage3_raw  in_voltage5_raw  in_voltage7_raw
> power  subsystem  uevent
>
>
> root@beaglebone:~# echo DM-GPIO-Test > $SLOTS
> [  286.033107] bone-capemgr bone_capemgr.8: part_number 'DM-GPIO-Test',
> version 'N/A'
> [  286.043079] bone-capemgr bone_capemgr.8: slot #8: generic override
> [  286.049605] bone-capemgr bone_capemgr.8: bone: Using override eeprom
> data at slot 8
> [  286.057622] bone-capemgr bone_capemgr.8: slot #8: 'Override Board
> Name,00A0,Override Manuf,DM-GPIO-Test'
> [  286.071044] bone-capemgr bone_capemgr.8: slot #8: Requesting part
> number/version based 'DM-GPIO-Test-00A0.dtbo
> [  286.082390] bone-capemgr bone_capemgr.8: slot #8: Requesting firmware
> 'DM-GPIO-Test-00A0.dtbo' for board-name 'Override Board Name', version
> '00A0'
> [  286.103360] bone-capemgr bone_capemgr.8: slot #8: dtbo
> 'DM-GPIO-Test-00A0.dtbo' loaded; converting to live tree
> [  286.115233] bone-capemgr bone_capemgr.8: slot #8: #2 overlays
> [  286.122388] bone-capemgr bone_capemgr.8: slot #8: Applied #2 overlays.
>
> root@beaglebone:~# cat $PINS | grep 998
> pin 102 (44e10998) 0027 pinctrl-single  *<--
> unchanged*
>
>  0: 54:PF---
>  1: 55:PF---
>  2: 56:PF---
>  3: 57:PF---
>  4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G
>  5: ff:P-O-L Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI
>  7: ff:P-O-L Override Board Name,00A0,Override Manuf,cape-bone-iio
>  8: ff:P-O-L Override Board Name,00A0,Override Manuf,DM-GPIO-Test
>
> *Example 2 (first load DM-GPIO-Test, then cape-bone-iio)*
>
> root@beaglebone:~# cat $PINS | grep 998
> pin 102 (44e10998) 0027 pinctrl-single  *<--
> default value*
>
> root@beaglebone:~# echo DM-GPIO-Test > $SLOTS
> [   90.459668] bone-capemgr bone_capemgr.8: part_number 'DM-GPIO-Test',
> version 'N/A'
> [   90.469663] bone-capemgr bone_capemgr.8: slot #7: generic override
> [   90.476312] bone-capemgr bone_capemgr.8: bone: Using override eeprom
> data at slot 7
> [   90.484332] bone-capemgr bone_capemgr.8: slot #7: 'Override Board
> Name,00A0,Override Manuf,DM-GPIO-Test'
> [   90.496939] bone-capemgr bone_capemgr.8: slot #7: Requesting part
> number/version based 'DM-GPIO-Test-00A0.dtbo
> [   90.508493] bone-capemgr bone_capemgr.8: slot #7: Requesting firmware
> 'DM-GPIO-Test-00A0.dtbo' for board-name 'Override Board Name', version
> '00A0'
> [   90.530293] bone-capemgr bone_capemgr.8: slot #7: dtbo
> 'DM-GPIO-Test-00A0.dtbo' loaded; converting to live tree
> [   90.542078] bone-capemgr bone_capemgr.8: slot #7: #2 overlays
> [   90.554967] bone-capemgr bone_capemgr.8: slot #7: Applied #2 overlays.
>
> root@beaglebone:~# cat $PINS | grep 998
> pin 102 (44e10998) 0037 pinctrl-single   *<--
> expected value from what was in the overlay*
>
> root@beaglebone:~# echo cape-bone-iio > $SLOTS
> [  224.500468] bone-capemgr bone_capemgr.8: part_number 'cape-bone-iio',
> version 'N/A'

[beagleboard] Re: conflict with "cape-bone-iio" overlay and simple pinmux overlay?

[cfalk3]

I am not sure how to attach a file, so here is my DTS file...

/dts-v1/;
/plugin/;

/{
   compatible = "ti,beaglebone", "ti,beaglebone-black";
   part-number = "DM-GPIO-Test";
   version = "00A0";

   fragment@0 {
 target = <&am33xx_pinmux>;

 __overlay__ {
  pinctrl_test: DM_GPIO_Test_Pins {
pinctrl-single,pins = <

0x078 0x07  /* P9_12 60 OUTPUT MODE7 */
0x074 0x07  /* P9_13 31 OUTPUT MODE7 */

   /* OUTPUT  GPIO(mode7) 0x07 pulldown, 0x17 
pullup, 0x?f no pullup/down */
   /* INPUT   GPIO(mode7) 0x27 pulldown, 0x37 
pullup, 0x?f no pullup/down */

>;
  };
 };
   };

   fragment@1 {
target = <&ocp>;
__overlay__ {
test_helper: helper {
compatible = "bone-pinmux-helper";
pinctrl-names = "default";
pinctrl-0 = <&pinctrl_test>;
status = "okay";
};
};
};
};


On Friday, February 21, 2014 1:47:39 PM UTC-6, cfa...@gmail.com wrote:
>
> Hello,
>
> I am trying to use both the "cape-bone-iio" device tree overlay for analog 
> input, and a simple pin-muxing overlay (see attached DTS file) to change 
> the direction of various gpio pins.  Although they both work on their own, 
> it seems that there is a problem when loaded together.  The first overlay 
> always works, and the second *seems* to load just fine, but does not take 
> effect..
>
> *Example 1 (first load cape-bone-iio, then DM-GPIO-Test)*
>
> root@beaglebone:~# echo cape-bone-iio > $SLOTS
> [   70.330541] bone-capemgr bone_capemgr.8: part_number 'cape-bone-iio', 
> version 'N/A'
> [   70.341287] bone-capemgr bone_capemgr.8: slot #7: generic override
> [   70.347943] bone-capemgr bone_capemgr.8: bone: Using override eeprom 
> data at slot 7
> [   70.355978] bone-capemgr bone_capemgr.8: slot #7: 'Override Board 
> Name,00A0,Override Manuf,cape-bone-iio'
> [   70.368667] bone-capemgr bone_capemgr.8: slot #7: Requesting part 
> number/version based 'cape-bone-iio-00A0.dtbo
> [   70.380219] bone-capemgr bone_capemgr.8: slot #7: Requesting firmware 
> 'cape-bone-iio-00A0.dtbo' for board-name 'Override Board Name', version 
> '00A0'
> [   70.395034] bone-capemgr bone_capemgr.8: slot #7: dtbo 
> 'cape-bone-iio-00A0.dtbo' loaded; converting to live tree
> [   70.407309] bone-capemgr bone_capemgr.8: slot #7: #1 overlays
> [   70.421631] bone-iio-helper helper.14: ready
> [   70.433579] bone-capemgr bone_capemgr.8: slot #7: Applied #1 overlays.
>
> root@beaglebone:~# ls /sys/devices/ocp.2/helper.14/
> AIN0  AIN1  AIN2  AIN3AIN4  AIN5  AIN6  AIN7drivermodalias  
> power  subsystem  uevent
> root@beaglebone:~# ls /sys/bus/iio/devices/iio\:device0
> bufferin_voltage0_raw  in_voltage2_raw  in_voltage4_raw  
> in_voltage6_raw  name   scan_elements  trigger
> devin_voltage1_raw  in_voltage3_raw  in_voltage5_raw  in_voltage7_raw  
> power  subsystem  uevent
>
>
> root@beaglebone:~# echo DM-GPIO-Test > $SLOTS
> [  286.033107] bone-capemgr bone_capemgr.8: part_number 'DM-GPIO-Test', 
> version 'N/A'
> [  286.043079] bone-capemgr bone_capemgr.8: slot #8: generic override
> [  286.049605] bone-capemgr bone_capemgr.8: bone: Using override eeprom 
> data at slot 8
> [  286.057622] bone-capemgr bone_capemgr.8: slot #8: 'Override Board 
> Name,00A0,Override Manuf,DM-GPIO-Test'
> [  286.071044] bone-capemgr bone_capemgr.8: slot #8: Requesting part 
> number/version based 'DM-GPIO-Test-00A0.dtbo
> [  286.082390] bone-capemgr bone_capemgr.8: slot #8: Requesting firmware 
> 'DM-GPIO-Test-00A0.dtbo' for board-name 'Override Board Name', version 
> '00A0'
> [  286.103360] bone-capemgr bone_capemgr.8: slot #8: dtbo 
> 'DM-GPIO-Test-00A0.dtbo' loaded; converting to live tree
> [  286.115233] bone-capemgr bone_capemgr.8: slot #8: #2 overlays
> [  286.122388] bone-capemgr bone_capemgr.8: slot #8: Applied #2 overlays.
>
> root@beaglebone:~# cat $PINS | grep 998
> pin 102 (44e10998) 0027 pinctrl-single  *<-- 
> unchanged*
>
>  0: 54:PF--- 
>  1: 55:PF--- 
>  2: 56:PF--- 
>  3: 57:PF--- 
>  4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G
>  5: ff:P-O-L Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI
>  7: ff:P-O-L Override Board Name,00A0,Override Manuf,cape-bone-iio
>  8: ff:P-O-L Override Board Name,00A0,Override Manuf,DM-GPIO-Test
>
> *Example 2 (first load DM-GPIO-Test, then cape-bone-iio)*
>
> root@beaglebone:~# cat $PINS | grep 998  
> pin 102 (44e10998) 0027 pinctrl-single  *<-- 
> default value*
>
> root@beaglebone:~# echo DM-GPIO-Test > $SLOTS
> [   90.459668] bone-capemgr bone_capemgr.8: part_numb

Re: [beagleboard] Re: Audio Cape Rev B schematics ?

[John Syn]

From:  David Anders 
Reply-To:  
Date:  Friday, February 21, 2014 at 8:18 AM
To:  
Subject:  [beagleboard] Re: Audio Cape Rev B schematics ?

> Valentin,
> 
> the audio cape revb is in production now and should be available for purchase
> within 14 to 21 days.
> 
> the design files for the audio cape revb are available on the wiki page:
> http://www.elinux.org/CircuitCo:Audio_Cape_RevB#Documentations
Do you have a device tree overlay for this board?
> 
> 
> On Wednesday, February 19, 2014 4:01:21 AM UTC-6, Valentin Le bescond wrote:
>> Hello everyone !
>> 
>> First question for me on this group... big day...
>> 
>> I am looking for BeagleBone audio cape Rev B schematics (announced @
>> elinux.com  ). Does anyone know who I might ask for it ?
>> 
>> In other words, I have been waiting for a month an a half to be able to buy a
>> audio cape (in France) an so far every "where to buy" is out of stock.
>> 
>> But anyway I wanted to make a custom audio cape based on the available one.
>> 
>> I looked at the schematics (Rev A) and saw there was a lot of DVI things in
>> it. Then I saw a yet-to-come Rev B with what seems to be a much cleaner PCB
>> (audio only ?). Plus it has a AIC3104 (instead of the 3106) which adds
>> selectable bias voltage !
>> 
>> So : nowhere to buy + available schematics (I hope) = let's build it !
>> 
>> Does anyone have any info that could help me getting started ?
>> 
>> 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.


-- 
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] conflict with "cape-bone-iio" overlay and simple pinmux overlay?

[cfalk3]

Hello,

I am trying to use both the "cape-bone-iio" device tree overlay for analog 
input, and a simple pin-muxing overlay (see attached DTS file) to change 
the direction of various gpio pins.  Although they both work on their own, 
it seems that there is a problem when loaded together.  The first overlay 
always works, and the second *seems* to load just fine, but does not take 
effect..

*Example 1 (first load cape-bone-iio, then DM-GPIO-Test)*

root@beaglebone:~# echo cape-bone-iio > $SLOTS
[   70.330541] bone-capemgr bone_capemgr.8: part_number 'cape-bone-iio', 
version 'N/A'
[   70.341287] bone-capemgr bone_capemgr.8: slot #7: generic override
[   70.347943] bone-capemgr bone_capemgr.8: bone: Using override eeprom 
data at slot 7
[   70.355978] bone-capemgr bone_capemgr.8: slot #7: 'Override Board 
Name,00A0,Override Manuf,cape-bone-iio'
[   70.368667] bone-capemgr bone_capemgr.8: slot #7: Requesting part 
number/version based 'cape-bone-iio-00A0.dtbo
[   70.380219] bone-capemgr bone_capemgr.8: slot #7: Requesting firmware 
'cape-bone-iio-00A0.dtbo' for board-name 'Override Board Name', version 
'00A0'
[   70.395034] bone-capemgr bone_capemgr.8: slot #7: dtbo 
'cape-bone-iio-00A0.dtbo' loaded; converting to live tree
[   70.407309] bone-capemgr bone_capemgr.8: slot #7: #1 overlays
[   70.421631] bone-iio-helper helper.14: ready
[   70.433579] bone-capemgr bone_capemgr.8: slot #7: Applied #1 overlays.

root@beaglebone:~# ls /sys/devices/ocp.2/helper.14/
AIN0  AIN1  AIN2  AIN3AIN4  AIN5  AIN6  AIN7drivermodalias  
power  subsystem  uevent
root@beaglebone:~# ls /sys/bus/iio/devices/iio\:device0
bufferin_voltage0_raw  in_voltage2_raw  in_voltage4_raw  
in_voltage6_raw  name   scan_elements  trigger
devin_voltage1_raw  in_voltage3_raw  in_voltage5_raw  in_voltage7_raw  
power  subsystem  uevent


root@beaglebone:~# echo DM-GPIO-Test > $SLOTS
[  286.033107] bone-capemgr bone_capemgr.8: part_number 'DM-GPIO-Test', 
version 'N/A'
[  286.043079] bone-capemgr bone_capemgr.8: slot #8: generic override
[  286.049605] bone-capemgr bone_capemgr.8: bone: Using override eeprom 
data at slot 8
[  286.057622] bone-capemgr bone_capemgr.8: slot #8: 'Override Board 
Name,00A0,Override Manuf,DM-GPIO-Test'
[  286.071044] bone-capemgr bone_capemgr.8: slot #8: Requesting part 
number/version based 'DM-GPIO-Test-00A0.dtbo
[  286.082390] bone-capemgr bone_capemgr.8: slot #8: Requesting firmware 
'DM-GPIO-Test-00A0.dtbo' for board-name 'Override Board Name', version 
'00A0'
[  286.103360] bone-capemgr bone_capemgr.8: slot #8: dtbo 
'DM-GPIO-Test-00A0.dtbo' loaded; converting to live tree
[  286.115233] bone-capemgr bone_capemgr.8: slot #8: #2 overlays
[  286.122388] bone-capemgr bone_capemgr.8: slot #8: Applied #2 overlays.

root@beaglebone:~# cat $PINS | grep 998
pin 102 (44e10998) 0027 pinctrl-single  *<-- unchanged*

 0: 54:PF--- 
 1: 55:PF--- 
 2: 56:PF--- 
 3: 57:PF--- 
 4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G
 5: ff:P-O-L Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI
 7: ff:P-O-L Override Board Name,00A0,Override Manuf,cape-bone-iio
 8: ff:P-O-L Override Board Name,00A0,Override Manuf,DM-GPIO-Test

*Example 2 (first load DM-GPIO-Test, then cape-bone-iio)*

root@beaglebone:~# cat $PINS | grep 998  
pin 102 (44e10998) 0027 pinctrl-single  *<-- 
default value*

root@beaglebone:~# echo DM-GPIO-Test > $SLOTS
[   90.459668] bone-capemgr bone_capemgr.8: part_number 'DM-GPIO-Test', 
version 'N/A'
[   90.469663] bone-capemgr bone_capemgr.8: slot #7: generic override
[   90.476312] bone-capemgr bone_capemgr.8: bone: Using override eeprom 
data at slot 7
[   90.484332] bone-capemgr bone_capemgr.8: slot #7: 'Override Board 
Name,00A0,Override Manuf,DM-GPIO-Test'
[   90.496939] bone-capemgr bone_capemgr.8: slot #7: Requesting part 
number/version based 'DM-GPIO-Test-00A0.dtbo
[   90.508493] bone-capemgr bone_capemgr.8: slot #7: Requesting firmware 
'DM-GPIO-Test-00A0.dtbo' for board-name 'Override Board Name', version 
'00A0'
[   90.530293] bone-capemgr bone_capemgr.8: slot #7: dtbo 
'DM-GPIO-Test-00A0.dtbo' loaded; converting to live tree
[   90.542078] bone-capemgr bone_capemgr.8: slot #7: #2 overlays
[   90.554967] bone-capemgr bone_capemgr.8: slot #7: Applied #2 overlays.

root@beaglebone:~# cat $PINS | grep 998
pin 102 (44e10998) 0037 pinctrl-single   *<-- 
expected value from what was in the overlay*

root@beaglebone:~# echo cape-bone-iio > $SLOTS
[  224.500468] bone-capemgr bone_capemgr.8: part_number 'cape-bone-iio', 
version 'N/A'
[  224.510629] bone-capemgr bone_capemgr.8: slot #8: generic override
[  224.517183] bone-capemgr bone_capemgr.8: bone: Using override eeprom 
data at slot 8
[  224.525207] bone-capemgr bone_capemgr.8: slot #8: 'Override Board 
Name,00A0,Override Manuf,cape-bone-iio'
[  224.538451] bone-capemgr bone_capemgr.8: slot #8: Requesting part 
number/version based 'cape-bone-iio-0

Re: [beagleboard] Failed angstrom build

[John Syn]

On 2/20/14, 11:08 PM, "geir...@gmail.com"  wrote:

>My build failed the same way.  I am compiling on a Ubuntu 13.10(x64)
>system. 
>
>Did you find out what the cause was?
How can anyone help you when we have no idea what you are referring too?
Please respond by retaining some of the previous posting for context so we
know what you are talking about.

Regards,
John
> 
>
>-- 
>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] Disable USB mass storage

[Robert Nelson]

/opt/scripts/boot/am335*
On Feb 21, 2014 11:45 AM, "Steve G"  wrote:

> Hi RCN,
>
> How about your latest Ubuntu demo image?
>
> SG
>
> On Thursday, February 6, 2014 9:33:52 AM UTC-5, RobertCNelson wrote:
>
>>
>>
>>
>> On Thu, Feb 6, 2014 at 8:05 AM,  wrote:
>>
>>> When I connect the BeagleBone Black to my PC it shows up as as USB mass
>>> storage device. Is there some way that I can disable this function? I want
>>> to use Ethernet over USB but I don't want it to act as a storage device.
>>>
>>
>> In Angstrom:
>>
>> modify:
>>
>> /usr/bin/g-ether-load.sh
>>
>> https://github.com/beagleboard/meta-beagleboard/
>> blob/master/meta-beagleboard-extras/recipes-support/usb-
>> gadget/gadget-init/g-ether-load.sh#L64
>>
>> see:
>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/
>> linux.git/tree/Documentation/usb/gadget_multi.txt
>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/
>> linux.git/tree/Documentation/usb/mass-storage.txt
>>
>> Regards,
>>
>> --
>> Robert Nelson
>> http://www.rcn-ee.com/
>>
>  --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>

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

Re: [beagleboard] Re: Availability - how come nobody has any BeagleBone Black to sell?

[Gerald Coley]

I appreciate the feedback ! We are all busting it to get things back up to
the new norm! There is a long line of people between us and the parts we
need.

Gerald



On Fri, Feb 21, 2014 at 11:37 AM, doog  wrote:

>
>
> On Friday, February 21, 2014 8:02:46 AM UTC-8, Gerald wrote:
>>
>> I just oversee the manufacturing and support of beagleboard.org. Any
>> other issues are theirs.
>>
>> Gerald
>>
>>
> And you are doing one heck of a good job! I sure hope you don't let the
> few who keep complaining make you feel like you're not. So please keep up
> the good work and brush off the digs that you're not doing enough and try
> to enjoy what you're doing. Some of us appreciate your efforts bringing
> such an awesome board to us individuals so we can enjoy your efforts and do
> great things with it.
>
> 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.
>

-- 
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] Disable USB mass storage

[Steve G]

Hi RCN,
 
How about your latest Ubuntu demo image?
 
SG

On Thursday, February 6, 2014 9:33:52 AM UTC-5, RobertCNelson wrote:

>
>
>
> On Thu, Feb 6, 2014 at 8:05 AM, > wrote:
>
>> When I connect the BeagleBone Black to my PC it shows up as as USB mass 
>> storage device. Is there some way that I can disable this function? I want 
>> to use Ethernet over USB but I don't want it to act as a storage device.
>>
>
> In Angstrom:
>
> modify:
>
> /usr/bin/g-ether-load.sh
>
>
> https://github.com/beagleboard/meta-beagleboard/blob/master/meta-beagleboard-extras/recipes-support/usb-gadget/gadget-init/g-ether-load.sh#L64
>
> see:
>
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/usb/gadget_multi.txt
>
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/usb/mass-storage.txt
>
> 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] Re: Availability - how come nobody has any BeagleBone Black to sell?

[doog]

On Friday, February 21, 2014 8:02:46 AM UTC-8, Gerald wrote:
>
> I just oversee the manufacturing and support of beagleboard.org. Any 
> other issues are theirs.
>
> Gerald
>
>
And you are doing one heck of a good job! I sure hope you don't let the few 
who keep complaining make you feel like you're not. So please keep up the 
good work and brush off the digs that you're not doing enough and try to 
enjoy what you're doing. Some of us appreciate your efforts bringing such 
an awesome board to us individuals so we can enjoy your efforts and do 
great things with it.

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] Re: CLKOUT2 access in RCN 3.12 kernel?

[Gerald Coley]

Sounds like they may not setup properly in the DTS file.

Gerald



On Fri, Feb 21, 2014 at 11:03 AM, Drew  wrote:

> I'm definitely interested!
> Thank you for the reply and the hints.
> I assumed my GPMC wasn't working in 3.12 because of missing CLKOUT2..
> Now I see that maybe ALL of my GPMC signals are dead...?
> (I'll have to break out the scope and double check that..)
>
>
>  --
> 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] dht22 on BeagleBoard Black

[selsinork]

On 20/02/14 17:14, mharris...@gmail.com wrote:
> I want to connect a Adsong dht22 (am2302) to the BBB. 
No idea if you've tried it or not, but there's a kernel driver here
https://gitorious.org/dht22-driver/dht22-driver/source/6e32bfc31de1e96c550b7678474ddcfa6f61336e:

There are a number of humidity sensors supported directly by the kernel
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/hwmon/sht15.c
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/hwmon/sht21.c
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/hwmon/hih6130.c

Using one of those would provide you with a tested and working solution.

It all depends though, what do you want to get from the experience?  Do you 
simply want it to work, or do you want to learn how to get it working yourself?

-- 
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: CLKOUT2 access in RCN 3.12 kernel?

[Drew]

I'm definitely interested!
Thank you for the reply and the hints.
I assumed my GPMC wasn't working in 3.12 because of missing CLKOUT2..
Now I see that maybe ALL of my GPMC signals are dead...?
(I'll have to break out the scope and double check that..)

-- 
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] dht22 Temp/RH Sensor on BBB

[Eric Palmer]

The datasheet shows how the am2302 works. It is a 1 wire device which
actually can be pretty easy to program. I did some of this with dallas
sensors on an arduino a long time ago. (dallas uses a different format).

Any language that can access the gpio ports on the BBB can be used.  My
preference for applications that are not time critical is python because C
gives me hives.  (okay just kidding, I just like python for easy stuff).

Adafruit has a tutorial for raspberry pi in python. You should be able to
adapt it easily to the BBB.
http://learn.adafruit.com/dht-humidity-sensing-on-raspberry-pi-with-gdocs-logging





On Fri, Feb 21, 2014 at 11:45 AM,  wrote:

> I have a Adsong dht22 (am2302) sensor that I would like to use on BBB.  I
> used C many years ago so I am pretty rusty with that.  After trying many
> code samples, I have not been able to come with with a working sensor.
>  What language/code would be best to use with BBB for a dht22 sensor?
>  Would bone script be better?  Would it be better to use i2c, analog, or
> other types of sensors instead with BBB (I need temp and RH)?  Any
> suggestions and links to working code would be greatly appreciated!  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.
>



-- 
Eric Palmer

-- 
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] dht22 Temp/RH Sensor on BBB

[Eric Palmer]

I meant to include the datasheet link
http://www.adafruit.com/datasheets/Digital%20humidity%20and%20temperature%20sensor%20AM2302.pdf
always start with the datasheet.


On Fri, Feb 21, 2014 at 11:58 AM, Eric Palmer  wrote:

> The datasheet shows how the am2302 works. It is a 1 wire device which
> actually can be pretty easy to program. I did some of this with dallas
> sensors on an arduino a long time ago. (dallas uses a different format).
>
> Any language that can access the gpio ports on the BBB can be used.  My
> preference for applications that are not time critical is python because C
> gives me hives.  (okay just kidding, I just like python for easy stuff).
>
> Adafruit has a tutorial for raspberry pi in python. You should be able to
> adapt it easily to the BBB.
>
> http://learn.adafruit.com/dht-humidity-sensing-on-raspberry-pi-with-gdocs-logging
>
>
>
>
>
> On Fri, Feb 21, 2014 at 11:45 AM,  wrote:
>
>> I have a Adsong dht22 (am2302) sensor that I would like to use on BBB.  I
>> used C many years ago so I am pretty rusty with that.  After trying many
>> code samples, I have not been able to come with with a working sensor.
>>  What language/code would be best to use with BBB for a dht22 sensor?
>>  Would bone script be better?  Would it be better to use i2c, analog, or
>> other types of sensors instead with BBB (I need temp and RH)?  Any
>> suggestions and links to working code would be greatly appreciated!  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.
>>
>
>
>
> --
> Eric Palmer
>



-- 
Eric Palmer

-- 
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] dht22 Temp/RH Sensor on BBB

[mharrisny1]

I have a Adsong dht22 (am2302) sensor that I would like to use on BBB.  I 
used C many years ago so I am pretty rusty with that.  After trying many 
code samples, I have not been able to come with with a working sensor. 
 What language/code would be best to use with BBB for a dht22 sensor? 
 Would bone script be better?  Would it be better to use i2c, analog, or 
other types of sensors instead with BBB (I need temp and RH)?  Any 
suggestions and links to working code would be greatly appreciated!  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 Using MySQL

[sofjk]

I am attempting to cross compile a C program using MySQL on Ubuntu for the 
Beaglebone.  I can compile manually on either the Beaglebone or Ubuntu and 
it works.  However when I compile in Eclipse to do the cross compiling it 
fails.  Does anyone have a solution or idea on how to get cross compiling 
of MySQL to work?

-- 
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 USB WiFi and LiPo batteries

[doog]

BTW, maybe it would be best to create a new topic/post the the forum 
instead of hijacking this thread on LiPo battery usage/charging.

Doug

On Friday, February 21, 2014 5:50:28 AM UTC-8, wing chwan wrote:
>
>
>
> hi i am using beagle bone black 
> it is powering usb cam and gpios can u help me
> how many mah battry must i use
>
>

-- 
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 USB WiFi and LiPo batteries

[doog]

On Friday, February 21, 2014 5:47:34 AM UTC-8, wing chwan wrote:
>
>
>
> hi can any body help me i am using usb cam as well as gpio for my beagle 
> bone black i need more power than usual what would u recommend
>
> an externally powered USB hub can be a good option. but you'll need to 
understand how much power is needed and to do that you can empirically test 
it by measuring the current drawn from the 5V supply powering the BBB while 
your camera is installed and running. A better way is to look at the 
specifications for power of your camera and in the BBB docs.

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.

[beagleboard] Re: Audio Cape Rev B schematics ?

[David Anders]

Valentin,

the audio cape revb is in production now and should be available for 
purchase within 14 to 21 days.

the design files for the audio cape revb are available on the wiki page: 
http://www.elinux.org/CircuitCo:Audio_Cape_RevB#Documentations

On Wednesday, February 19, 2014 4:01:21 AM UTC-6, Valentin Le bescond wrote:
>
> Hello everyone !
>
> First question for me on this group... big day...
>
> I am looking for BeagleBone audio cape Rev B schematics (announced @ 
> elinux.com). Does anyone know who I might ask for it ?
>
> In other words, I have been waiting for a month an a half to be able to 
> buy a audio cape (in France) an so far every "where to buy" is out of stock.
>
> But anyway I wanted to make a custom audio cape based on the available one.
>
> I looked at the schematics (Rev A) and saw there was a lot of DVI things 
> in it. Then I saw a yet-to-come Rev B with what seems to be a much cleaner 
> PCB (audio only ?). Plus it has a AIC3104 (instead of the 3106) which adds 
> selectable bias voltage !
>
> So : nowhere to buy + available schematics (I hope) = let's build it !
>
> Does anyone have any info that could help me getting started ? 
>
> 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.

Re: [beagleboard] Re: Availability - how come nobody has any BeagleBone Black to sell?

[Gerald Coley]

I just oversee the manufacturing and support of beagleboard.org. Any other
issues are theirs.

Gerald



On Fri, Feb 21, 2014 at 9:57 AM, Bas Laarhoven  wrote:

>
> Ah I see. Somehow I knew this, but you seem to know much about internal
> circuitco issues.
> Sorry for that, but I'm unable to reach anyone at circuitco. I've had a
> deal with Bob and later
> got a commitment from Clint to resolve the matter. But circuitco never
> delivered and now
> seems to think it's easier to ignore the situation. Expensive lesson
> learned, so much for trusting people.
>
> -- Bas
>
>
>
>
> On 21-2-2014 16:22, Gerald Coley wrote:
>
> I work for TI.
>
>  Gerald
>
>
>
> On Fri, Feb 21, 2014 at 9:21 AM, Bas Laarhoven  wrote:
>
>>
>> You're not speaking for circuitco then?
>>
>> -- Bas
>>
>>
>>
>> On 21-2-2014 16:17, Gerald Coley wrote:
>>
>> I would think that is up to whomever it is that owes you.
>>
>>  Gerald
>>
>>
>>
>> On Fri, Feb 21, 2014 at 9:14 AM, Bas Laarhoven  wrote:
>>
>>>
>>> Good to hear, does that also include thinking about paying your debt to
>>> this cape developer ?
>>>
>>> -- Bas
>>>
>>>
>>>
>>> On 21-2-2014 15:41, Gerald Coley wrote:
>>>
>>> We are thinking about a lot of things right now.
>>>
>>>  Gerald
>>>
>>>
>>>
>>> On Fri, Feb 21, 2014 at 8:38 AM, Robert Nelson 
>>> wrote:
>>>



  On Fri, Feb 21, 2014 at 8:28 AM, Gerald Coley 
 wrote:

> Expedite fees? Well we used to do that on the earlier boards. But
> there is zero buffer on these boards. The idea of loosing say $700,000 is
> not something that makes a lot of sense. Having deals and POs in
> place with distributors and then telling them, Oh sorry, you have to pay
> more is tough.
>
>  I am thinking of maybe taking the price to say $75 in the future.
>

  +1 I think you should do that..

  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.
>>>
>>>
>>>--
>>> 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.
>>
>>
>>--
>> 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.
>
>
>  --
> 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: Availability - how come nobody has any BeagleBone Black to sell?

[Mahendra Gunawardena]

I believe the current demand is due to the price point. With demand the
price needs to go down. The supply issues need to be sorted out.



On Fri, Feb 21, 2014 at 10:40 AM, Robert P. J. Day wrote:

> On Fri, 21 Feb 2014, Micka wrote:
>
> > WHAT are you saying ? It's to the Cap builder to do something !!!
> >
> > PLUS, if you want something to work in the open source, you have to
> > do it yourself, that the price of open source !
> >
> > I wanted the RS485 CAP work and I had Zero knowledge in Linux
> > Kernel, It took me 2 month to understand how to make it Happen.
> >
> > I wanted to fix the issue with the LCD ( Jitter Problem) => I just
> > needed to find out where was the driver source => I fixed it !
>
>   can we please take this kind of bickering offline? It's really
> pretty unseemly.
>
> rday
>
> --
>
> 
> Robert P. J. Day Ottawa, Ontario, CANADA
> http://crashcourse.ca
>
> Twitter:   http://twitter.com/rpjday
> LinkedIn:   http://ca.linkedin.com/in/rpjday
> 
>
> --
> 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/Z3JfUIkxOl8/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: Availability - how come nobody has any BeagleBone Black to sell?

[Bas Laarhoven]

Ah I see. Somehow I knew this, but you seem to know much about internal 
circuitco issues.
Sorry for that, but I'm unable to reach anyone at circuitco. I've had a 
deal with Bob and later
got a commitment from Clint to resolve the matter. But circuitco never 
delivered and now
seems to think it's easier to ignore the situation. Expensive lesson 
learned, so much for trusting people.


-- Bas



On 21-2-2014 16:22, Gerald Coley wrote:

I work for TI.

Gerald



On Fri, Feb 21, 2014 at 9:21 AM, Bas Laarhoven > wrote:



You're not speaking for circuitco then?

-- Bas



On 21-2-2014 16:17, Gerald Coley wrote:

I would think that is up to whomever it is that owes you.

Gerald



On Fri, Feb 21, 2014 at 9:14 AM, Bas Laarhoven mailto:s...@xs4all.nl>> wrote:


Good to hear, does that also include thinking about paying
your debt to this cape developer ?

-- Bas



On 21-2-2014 15:41, Gerald Coley wrote:

We are thinking about a lot of things right now.

Gerald



On Fri, Feb 21, 2014 at 8:38 AM, Robert Nelson
mailto:robertcnel...@gmail.com>>
wrote:




On Fri, Feb 21, 2014 at 8:28 AM, Gerald Coley
mailto:ger...@beagleboard.org>>
wrote:

Expedite fees? Well we used to do that
on the earlier boards. But there is zero buffer on
these boards. The idea of loosing say $700,000 is
not something that makes a lot of sense. Having
deals and POs in place with distributors and then
telling them, Oh sorry, you have to pay more is tough.

I am thinking of maybe taking the price to say $75
in the future.


+1 I think you should do that..

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.


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


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


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

Re: [beagleboard] Availability - how come nobody has any BeagleBone Black to sell?

[George Erhart]

Thanks for the tip ... they are only charging a $4.99 premium on the BBB 
and as of a few minutes ago, claimed they were in stock. So, I ordered one 
and it is suppose to ship on Monday (2/24). So, we will see. I had a 
backorder with Sparkfun, but their expected date slipped from 2/19 to 4/5 
... so I cancelled the order. 

-- 
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: Availability - how come nobody has any BeagleBone Black to sell?

[Robert P. J. Day]

On Fri, 21 Feb 2014, Micka wrote:

> WHAT are you saying ? It's to the Cap builder to do something !!!
>
> PLUS, if you want something to work in the open source, you have to
> do it yourself, that the price of open source !
>
> I wanted the RS485 CAP work and I had Zero knowledge in Linux
> Kernel, It took me 2 month to understand how to make it Happen.
>
> I wanted to fix the issue with the LCD ( Jitter Problem) => I just
> needed to find out where was the driver source => I fixed it !

  can we please take this kind of bickering offline? It's really
pretty unseemly.

rday

-- 


Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter:   http://twitter.com/rpjday
LinkedIn:   http://ca.linkedin.com/in/rpjday


-- 
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] problem with sending float type data serially using c++

[kyle]

You may be better off in the long run coding this to convert the value to 
string data, transmit the string and convert back on the other end.   No reason 
you can't send binary jibberish over the wire but debugging that later on can 
be a real bear.   If you have tons of floats to send with huge values then 
maybe it's worth it to send the binary data instead. 

-- 
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: Availability - how come nobody has any BeagleBone Black to sell?

[Micka]

WHAT are you saying ? It's to the Cap builder to do something !!!


PLUS, if you want something to work in the open source, you have to do it
yourself, that the price of open source !

I wanted the RS485 CAP work and I had Zero knowledge in Linux Kernel, It
took me 2 month to understand how to make it Happen.

I wanted to fix the issue with the LCD ( Jitter Problem) => I just needed
to find out where was the driver source => I fixed it !


Micka,


On Fri, Feb 21, 2014 at 4:14 PM, Bas Laarhoven  wrote:

>
> Good to hear, does that also include thinking about paying your debt to
> this cape developer ?
>
> -- Bas
>
>
>
> On 21-2-2014 15:41, Gerald Coley wrote:
>
> We are thinking about a lot of things right now.
>
>  Gerald
>
>
>
> On Fri, Feb 21, 2014 at 8:38 AM, Robert Nelson wrote:
>
>>
>>
>>
>>  On Fri, Feb 21, 2014 at 8:28 AM, Gerald Coley wrote:
>>
>>> Expedite fees? Well we used to do that on the earlier boards. But there
>>> is zero buffer on these boards. The idea of loosing say $700,000 is not
>>> something that makes a lot of sense. Having deals and POs in
>>> place with distributors and then telling them, Oh sorry, you have to pay
>>> more is tough.
>>>
>>>  I am thinking of maybe taking the price to say $75 in the future.
>>>
>>
>>  +1 I think you should do that..
>>
>>  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.
>
>
>  --
> 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] problem with sending float type data serially using c++

[kyle]

A float is just 4 bytes of binary data that is coded to show the decimal point 
position and the number before and after the point.  The trick is that you have 
to tell the C++ compiler that you are not making a stupid mistake and really do 
want to treat the float as an array of bytes:

void send_float (float f)
{
  // Cast float to a pointer to bytes - Tells C++ you really mean to do that.
  byte* bytes = (byte*)&f; 

  // write the data to the serial
  Serial.write (bytes, sizeof(f));
}

-- 
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: Availability - how come nobody has any BeagleBone Black to sell?

[Gerald Coley]

I work for TI.

Gerald



On Fri, Feb 21, 2014 at 9:21 AM, Bas Laarhoven  wrote:

>
> You're not speaking for circuitco then?
>
> -- Bas
>
>
>
> On 21-2-2014 16:17, Gerald Coley wrote:
>
> I would think that is up to whomever it is that owes you.
>
>  Gerald
>
>
>
> On Fri, Feb 21, 2014 at 9:14 AM, Bas Laarhoven  wrote:
>
>>
>> Good to hear, does that also include thinking about paying your debt to
>> this cape developer ?
>>
>> -- Bas
>>
>>
>>
>> On 21-2-2014 15:41, Gerald Coley wrote:
>>
>> We are thinking about a lot of things right now.
>>
>>  Gerald
>>
>>
>>
>> On Fri, Feb 21, 2014 at 8:38 AM, Robert Nelson 
>> wrote:
>>
>>>
>>>
>>>
>>>  On Fri, Feb 21, 2014 at 8:28 AM, Gerald Coley 
>>> wrote:
>>>
 Expedite fees? Well we used to do that on the earlier boards. But there
 is zero buffer on these boards. The idea of loosing say $700,000 is not
 something that makes a lot of sense. Having deals and POs in
 place with distributors and then telling them, Oh sorry, you have to pay
 more is tough.

  I am thinking of maybe taking the price to say $75 in the future.

>>>
>>>  +1 I think you should do that..
>>>
>>>  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.
>>
>>
>>--
>> 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.
>
>
>  --
> 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: Availability - how come nobody has any BeagleBone Black to sell?

[Bas Laarhoven]

You're not speaking for circuitco then?

-- Bas


On 21-2-2014 16:17, Gerald Coley wrote:

I would think that is up to whomever it is that owes you.

Gerald



On Fri, Feb 21, 2014 at 9:14 AM, Bas Laarhoven > wrote:



Good to hear, does that also include thinking about paying your
debt to this cape developer ?

-- Bas



On 21-2-2014 15:41, Gerald Coley wrote:

We are thinking about a lot of things right now.

Gerald



On Fri, Feb 21, 2014 at 8:38 AM, Robert Nelson
mailto:robertcnel...@gmail.com>> wrote:




On Fri, Feb 21, 2014 at 8:28 AM, Gerald Coley
mailto:ger...@beagleboard.org>> wrote:

Expedite fees? Well we used to do that
on the earlier boards. But there is zero buffer on these
boards. The idea of loosing say $700,000 is not something
that makes a lot of sense. Having deals and POs in
place with distributors and then telling them, Oh sorry,
you have to pay more is tough.

I am thinking of maybe taking the price to say $75 in the
future.


+1 I think you should do that..

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.


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


--
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: Availability - how come nobody has any BeagleBone Black to sell?

[Gerald Coley]

I would think that is up to whomever it is that owes you.

Gerald



On Fri, Feb 21, 2014 at 9:14 AM, Bas Laarhoven  wrote:

>
> Good to hear, does that also include thinking about paying your debt to
> this cape developer ?
>
> -- Bas
>
>
>
> On 21-2-2014 15:41, Gerald Coley wrote:
>
> We are thinking about a lot of things right now.
>
>  Gerald
>
>
>
> On Fri, Feb 21, 2014 at 8:38 AM, Robert Nelson wrote:
>
>>
>>
>>
>>  On Fri, Feb 21, 2014 at 8:28 AM, Gerald Coley wrote:
>>
>>> Expedite fees? Well we used to do that on the earlier boards. But there
>>> is zero buffer on these boards. The idea of loosing say $700,000 is not
>>> something that makes a lot of sense. Having deals and POs in
>>> place with distributors and then telling them, Oh sorry, you have to pay
>>> more is tough.
>>>
>>>  I am thinking of maybe taking the price to say $75 in the future.
>>>
>>
>>  +1 I think you should do that..
>>
>>  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.
>
>
>  --
> 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: Availability - how come nobody has any BeagleBone Black to sell?

[Bas Laarhoven]

Good to hear, does that also include thinking about paying your debt to 
this cape developer ?


-- Bas


On 21-2-2014 15:41, Gerald Coley wrote:

We are thinking about a lot of things right now.

Gerald



On Fri, Feb 21, 2014 at 8:38 AM, Robert Nelson 
mailto:robertcnel...@gmail.com>> wrote:





On Fri, Feb 21, 2014 at 8:28 AM, Gerald Coley
mailto:ger...@beagleboard.org>> wrote:

Expedite fees? Well we used to do that on the earlier boards.
But there is zero buffer on these boards. The idea of loosing
say $700,000 is not something that makes a lot of sense.
Having deals and POs in place with distributors and then
telling them, Oh sorry, you have to pay more is tough.

I am thinking of maybe taking the price to say $75 in the future.


+1 I think you should do that..

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.


--
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: Availability - how come nobody has any BeagleBone Black to sell?

[Eric Palmer]

+1 on $75

Sent from my iPhone

> On Feb 21, 2014, at 9:28 AM, Gerald Coley  wrote:
> 
> Expedite fees? Well we used to do that on the earlier boards. But there is 
> zero buffer on these boards. The idea of loosing say $700,000 is not 
> something that makes a lot of sense. Having deals and POs in place with 
> distributors and then telling them, Oh sorry, you have to pay more is tough.
> 
> I am thinking of maybe taking the price to say $75 in the future.
> 
> Gerald
> 
> 
>> On Thu, Feb 20, 2014 at 11:51 PM,  wrote:
>> Appreciate the figures of 700/day on supply and 140,000 on back orders (200 
>> days of supply.. phew!).
>> 
>> This is an awesome product. What you saw until October was just people 
>> trying it out.  They've concluded it is a good product and are ordering it 
>> in greater quantities.  That is where we are and I hear similar stories from 
>> others. An order build up of 140,000 in two months, even with supply of 
>> 700/day suggests an incoming demand of 3500+ per day.  I believe you will 
>> see this kind of demand continue.  None of these buyers want to get into 
>> manufacturing--Circuitco is good at it.  It would be a shame to see a great 
>> product go sideways due to supply issues.
>> 
>> Given that the main constraint is lead time for some components: if 
>> sweeteners such as expedite fees can help, I think the community won't mind 
>> a higher price.. say $48 or $50, to ensure a demand-supply balance.
>> 
>> 
>> 
>>> On Friday, February 21, 2014 9:01:54 AM UTC+5:30, Gerald wrote:
>>> We did this. A year ago when we launched the product. Things were fine 
>>> until roughly October. Demand has risen due to people using boards in 
>>> products  They never told anyone about their pending demand. They thought 
>>> the boards just magically appear in the cabbage patch. 
>>> 
>>> We build to distributor orders and schedules. We are close to getting out 
>>> of this.
>>> 
>>> I appreciate your offer of help. But this is not just a analytic problem. 
>>> It is a data problem. We have plugged the data into the formula and are 
>>> adjusting to that new data and working to fill the pipeline and to get 
>>> orders shipped.
>>> 
>>> Gerald
>>> 
>>> 
 On Thu, Feb 20, 2014 at 9:21 PM, Anil Gupta  wrote:
 Dave,
 Gerald,
 
 From my experience with product fulfillment: a good plan would establish a 
 target date when the product would be broadly available in the market with 
 only occasional shortages.   A key to this is to show back orders as a % 
 of weekly production, and whether back orders are reducing or increasing 
 as we fulfill back orders and receive new orders each week.  There would 
 be a weekly review of whether the target date is likely to be met, 
 production plan and any changes, and a new date, if needed.  Sudden orders 
 and other unexpected situations are common in all kinds of fulfillment 
 situations and there are lots of good systems to deal with this.
 
 I am happy to volunteer to do weekly analytics.
 
 elinux.org only shows monthly shipments, with little clue around demand 
 and back order situation.  It is nice to know that "circuitco is in full 
 production" but we need to provide lots more facts.
 
 Dr. Anil Gupta
 
 
> On Wed, Feb 19, 2014 at 2:35 AM, David Anders  wrote:
> as gerald stated, circuitco is in full production of the beaglebone black 
> and continues to ship daily to a wide range of distributors. these 
> distributors fill back-orders first before showing stock.
> 
> http://elinux.org/Beagleboard:BeagleBoneBlack#Board_Shipments
> 
> Dave
> 
>> On Tuesday, February 18, 2014 1:46:30 AM UTC-6, anil.g...@gmail.com 
>> wrote:
>> I have been looking for 3+ weeks and unable to find any stock anywhere.
>> 
>> Is there a way to see the order backlog with Circuitco and current 
>> supply capability?  Is the issue getting better or worse? (My anecdotal 
>> experience suggests it may be getting worse.)  The current situation is 
>> frustrating.  If the news is bad, let us know it early and deal with it. 
>>  Right now, there is no data at all.
>> 
>> Gerald: thanks for your timely and open updates.
>> 
>>> On Wednesday, February 12, 2014 1:25:00 AM UTC+5:30, Gerald wrote:
>>> We are focused on the community. Feel free to build it yourself 
>>> however. All the materials to build it are provided for free and you 
>>> don't have to pay any development costs.
>>> 
>>> 
>>> 
>>> Gerald
 
 -- 
 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

Re: [beagleboard] Re: Future of the Angstrom distribution for Beaglebone

[chmorgan]

On Monday, December 2, 2013 5:15:06 PM UTC-5, John Syne wrote:

>
> On 12/2/13, 12:15 PM, "David Lambert" > 
> wrote: 
>
> >On 12/02/2013 01:02 PM, Jason Kridner wrote: 
> >> Angstrom site is simply undergoing a move. However, the community does 
> >> seem to be pushing the project in the direction of Debian. 
> >Does this probable move to Debian mean that systemd will not be 
> supported? 
> SystemD is supported on Debian. I believe Robert Nelson is looking into 
> making SystemD as the default for Jessie. 
> Regards, 
> John 
> > 
> >Dave. 
> > 
>


As of last week the Debian CTTE has decided on systemd for jessie.

Chris
 

-- 
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: Availability - how come nobody has any BeagleBone Black to sell?

[Gerald Coley]

We are thinking about a lot of things right now.

Gerald



On Fri, Feb 21, 2014 at 8:38 AM, Robert Nelson wrote:

>
>
>
> On Fri, Feb 21, 2014 at 8:28 AM, Gerald Coley wrote:
>
>> Expedite fees? Well we used to do that on the earlier boards. But there
>> is zero buffer on these boards. The idea of loosing say $700,000 is not
>> something that makes a lot of sense. Having deals and POs in
>> place with distributors and then telling them, Oh sorry, you have to pay
>> more is tough.
>>
>> I am thinking of maybe taking the price to say $75 in the future.
>>
>
> +1 I think you should do that..
>
> Regards,
>
> --
> Robert Nelson
> http://www.rcn-ee.com/
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>

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

Re: [beagleboard] Re: Availability - how come nobody has any BeagleBone Black to sell?

[Robert Nelson]

On Fri, Feb 21, 2014 at 8:28 AM, Gerald Coley wrote:

> Expedite fees? Well we used to do that on the earlier boards. But there is
> zero buffer on these boards. The idea of loosing say $700,000 is not
> something that makes a lot of sense. Having deals and POs in
> place with distributors and then telling them, Oh sorry, you have to pay
> more is tough.
>
> I am thinking of maybe taking the price to say $75 in the future.
>

+1 I think you should do that..

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] Re: CLKOUT2 access in RCN 3.12 kernel?

[Gerald Coley]

Most people are still on the 3.8 kernel.

Gerald


On Fri, Feb 21, 2014 at 2:07 AM,  wrote:

> Is there really nobody interested in using the GPMC on the BeagleBone
> Black?
>
>
> Am Dienstag, 18. Februar 2014 11:35:06 UTC+1 schrieb quik...@gmail.com:
>
>> I seems that what you are trying to do is to setup GPMC access on the
>> BeagleBone Black using kernel 3.12.x. The steps to do this are as follows:
>>
>> (1) You must boot using an external micro SDHC card because the internal
>> eMMC must be disabled
>> (2) Disable eMMC and HDMI in uEnv.txt by adding optargs=capemgr.disable_
>> partno=BB-BONE-EMMC-2G,BB-BONELT-HDMI,BB-BONELT-HDMIN
>> (3) After booting cape manager will still load both capes. The must be
>> removed manually.
>> (4) In the sources of kernel 3.12.x we must modify
>> /arch/arm/boot/dts/am335x-boneblack.dts to free up the reset pin for the
>> eMMC device. This is done by changing status from "ok" to disabled in
>> section &mmc2
>> (5) It should now be possible to load your custom .dts file without any
>> warnings
>>
>> Unfortunately, the GPMC is still not working in kernel 3.12. I have
>> tested this using 3.12.8 and 3.12.10. I cannot see any activity on the GPMC
>> signals. The same procedure is working in kernel 3.8.13.
>>
>>
>>
>> Am Freitag, 17. Januar 2014 17:55:11 UTC+1 schrieb Drew Moore:
>>>
>>> Thanks for responding..
>>>
>>> I did
>>> grep clkout2 *.dts
>>> in both directories and found that clkout2 didn't show up in the 3.8 but
>>> did show up in 3.12
>>> in 3.12 it shows up in am335x-evm.dts and also am335x-evmsk.dts.. (and
>>> dove-cubox.dts but I don't think that is related)
>>>
>>> I also just noticed that it also shows up in am335x-bone-common.dtsi,
>>> (3.12) which now seems more likely to be the beaglebone related file.
>>>
>>> Here's that chunk from my device tree file..
>>>
>>> fragment@0 {
>>> target = <&am33xx_pinmux>;
>>> __overlay__ {
>>> gpmc_pins: pinmux_gpmc_pins {
>>> pinctrl-single,pins = <
>>> /* 0x20 = Fast, RX_enabled, pullup, pullup_enable,
>>> mode 0 */
>>> 0x000 0x20/* gpmc_ad0.gpmc_ad0 MODE0 | INPUT |
>>> PULLUP */
>>> 0x004 0x20/* gpmc_ad1.gpmc_ad1 MODE0 | INPUT |
>>> PULLUP */
>>> 0x008 0x20/* gpmc_ad2.gpmc_ad2 MODE0 | INPUT |
>>> PULLUP */
>>> 0x00C 0x20/* gpmc_ad3.gpmc_ad3 MODE0 | INPUT |
>>> PULLUP */
>>> 0x010 0x20/* gpmc_ad4.gpmc_ad4 MODE0 | INPUT |
>>> PULLUP */
>>> 0x014 0x20/* gpmc_ad5.gpmc_ad5 MODE0 | INPUT |
>>> PULLUP */
>>> 0x018 0x20/* gpmc_ad6.gpmc_ad6 MODE0 | INPUT |
>>> PULLUP */
>>> 0x01C 0x20/* gpmc_ad7.gpmc_ad7 MODE0 | INPUT |
>>> PULLUP */
>>> 0x020 0x20/* gpmc_ad8.gpmc_ad8 MODE0 | INPUT |
>>> PULLUP */
>>> 0x024 0x20/* gpmc_ad9.gpmc_ad9 MODE0 | INPUT |
>>> PULLUP */
>>> 0x028 0x20/* gpmc_ad10.gpmc_ad10 MODE0 | INPUT |
>>> PULLUP */
>>> 0x02C 0x20/* gpmc_ad11.gpmc_ad11 MODE0 | INPUT |
>>> PULLUP */
>>> 0x030 0x20/* gpmc_ad12.gpmc_ad12 MODE0 | INPUT |
>>> PULLUP */
>>> 0x034 0x20/* gpmc_ad13.gpmc_ad13 MODE0 | INPUT |
>>> PULLUP */
>>> 0x038 0x20/* gpmc_ad14.gpmc_ad14 MODE0 | INPUT |
>>> PULLUP */
>>> 0x03C 0x20/* gpmc_ad15.gpmc_ad15 MODE0 | INPUT |
>>> PULLUP */
>>>
>>> 0x078 0x04/* gpmc_ben1.gpmc_dir MODE4 | OUTPUT */
>>> 0x080 0x00/* gpmc_cscn1.gpmc_cscn1 MODE0 |
>>> OUTPUT */
>>> 0x08C 0x00/* gpmc_clk.gpmc_clk MODE0 | OUTPUT */
>>> 0x090 0x00/* gpmc_advn_ale.gpmc_advn_ale MODE0 |
>>> OUTPUT */
>>> 0x094 0x00/* gpmc_oen_ren.gpmc_oen_ren MODE0 |
>>> OUTPUT */
>>> 0x098 0x00/* gpmc_wen.gpmc_wen MODE0 | OUTPUT */
>>> 0x09C 0x00/* gpmc_ben0_cle.gpmc_ben0_cle MODE0 |
>>> OUTPUT */
>>> 0x1b4 0x03/* xdma_event_intr1.clkout2 MODE3 |
>>> OUTPUT */
>>> >;
>>> };
>>> };
>>> };
>>>
>>> I used BB-BONE-CAM3 as a starting point but yes, I'm mostly guessing at
>>> what this stuff means.
>>> My next guess is that the last line above is in the wrong section..
>>> clkout2 is not a gpmc pin.
>>>
>>> I don't have any /include/ lines in my file.. just
>>> compatible = "ti,beaglebone", "ti,beaglebone-black";
>>> from the CAM3 file I modified.
>>>
>>>
>>>
>>>  --
> 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://grou

Re: [beagleboard] How to install linux-headers-3.8.13-bone30

[Robert Nelson]

On Thu, Feb 20, 2014 at 10:31 PM,  wrote:

> Can you tell me how install this headers.
>

wget 
sudo dpkg -i 

or even:

wget
https://raw.github.com/gkaindl/beaglebone-ubuntu-scripts/master/bb-get-rcn-kernel-source.sh
chmod +x bb-get-rcn-kernel-source.sh
./bb-get-rcn-kernel-source.sh

Will set it up automatically.



> If you ubuntu-armhf images are not supported by your scripts where can I
> find the image files support by yours.
>

Let's see, the "debian testing" image posted to this group every week..

https://groups.google.com/d/msg/beagleboard/D1ioNrzzXfQ/LdfJ2ccuiY4J

The ones posted here:
http://elinux.org/BeagleBoardUbuntu

and here:
http://elinux.org/BeagleBoardDebian

and here:
http://eewiki.net/display/linuxonarm/Home

etc/etc..

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] Re: Availability - how come nobody has any BeagleBone Black to sell?

[Gerald Coley]

Expedite fees? Well we used to do that on the earlier boards. But there is
zero buffer on these boards. The idea of loosing say $700,000 is not
something that makes a lot of sense. Having deals and POs in
place with distributors and then telling them, Oh sorry, you have to pay
more is tough.

I am thinking of maybe taking the price to say $75 in the future.

Gerald


On Thu, Feb 20, 2014 at 11:51 PM,  wrote:

> Appreciate the figures of 700/day on supply and 140,000 on back orders
> (200 days of supply.. phew!).
>
> This is an awesome product. What you saw until October was just people
> trying it out.  They've concluded it is a good product and are ordering it
> in greater quantities.  That is where we are and I hear similar stories
> from others. An order build up of 140,000 in two months, even with supply
> of 700/day suggests an incoming demand of *3500+ per day.*  I believe you
> will see this kind of demand continue.  None of these buyers want to get
> into manufacturing--Circuitco is good at it.  It would be a shame to see a
> great product go sideways due to supply issues.
>
> Given that the main constraint is lead time for some components: if
> sweeteners such as expedite fees can help, I think the community won't mind
> a higher price.. say $48 or $50, to ensure a demand-supply balance.
>
>
>
> On Friday, February 21, 2014 9:01:54 AM UTC+5:30, Gerald wrote:
>
>> We did this. A year ago when we launched the product. Things were fine
>> until roughly October. Demand has risen due to people
>> using boards in products  They never told anyone about
>> their pending demand. They thought the boards just magically appear in the
>> cabbage patch.
>>
>> We build to distributor orders and schedules. We are close to getting out
>> of this.
>>
>> I appreciate your offer of help. But this is not just a analytic problem.
>> It is a data problem. We have plugged the data into the formula and
>> are adjusting to that new data and working to fill the pipeline and to get
>> orders shipped.
>>
>> Gerald
>>
>>
>> On Thu, Feb 20, 2014 at 9:21 PM, Anil Gupta  wrote:
>>
>>> Dave,
>>> Gerald,
>>>
>>> From my experience with product fulfillment: a good plan would establish
>>> a target date when the product would be broadly available in the market
>>> with only occasional shortages.   A key to this is to show back orders as a
>>> % of weekly production, and whether back orders are reducing or increasing
>>> as we fulfill back orders and receive new orders each week.  There would be
>>> a weekly review of whether the target date is likely to be met, production
>>> plan and any changes, and a new date, if needed.  Sudden orders and other
>>> unexpected situations are common in all kinds of fulfillment situations and
>>> there are lots of good systems to deal with this.
>>>
>>> I am happy to volunteer to do weekly analytics.
>>>
>>> elinux.org only shows monthly shipments, with little clue around demand
>>> and back order situation.  It is nice to know that "circuitco is in full
>>> production" but we need to provide lots more facts.
>>>
>>> Dr. Anil Gupta
>>>
>>>
>>> On Wed, Feb 19, 2014 at 2:35 AM, David Anders wrote:
>>>
 as gerald stated, circuitco is in full production of the beaglebone
 black and continues to ship daily to a wide range of distributors. these
 distributors fill back-orders first before showing stock.

 http://elinux.org/Beagleboard:BeagleBoneBlack#Board_Shipments

 Dave

 On Tuesday, February 18, 2014 1:46:30 AM UTC-6, anil.g...@gmail.comwrote:
>
> I have been looking for 3+ weeks and unable to find any stock anywhere.
>
> Is there a way to see the order backlog with Circuitco and current
> supply capability?  Is the issue getting better or worse? (My anecdotal
> experience suggests it may be getting worse.)  The current situation is
> frustrating.  If the news is bad, let us know it early and deal with it.
>  Right now, there is no data at all.
>
> Gerald: thanks for your timely and open updates.
>
> On Wednesday, February 12, 2014 1:25:00 AM UTC+5:30, Gerald wrote:
>>
>> We are focused on the community. Feel free to build it yourself
>> however. All the materials to build it are provided for free and you 
>> don't
>> have to pay any development costs.
>>
>>
>> Gerald
>>
>>
>>
>>>  --
>>> 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

[beagleboard] Re: BBB USB WiFi and LiPo batteries

[wingchwan]

hi can any body help me i am using usb cam as well as gpio for my beagle 
bone black i need more power than usual what would u recommend

-- 
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 USB WiFi and LiPo batteries

[wingchwan]

hi i am using beagle bone black 
it is powering usb cam and gpios can u help me
how many mah battry must i use

-- 
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 with spi device after reset on beaglebone black with angstrom

[mutual . jun]

insert into uEnv.txt file and reboot

optargs=quiet drm.debug=7 capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN
capemgr.enable_partno=BB-SPI1-01


 Make sure it is enabled.
 
ls -al /dev/spidev1.*

ref. 
http://elinux.org/BeagleBone_Black_Enable_SPIDEV#Enabling_SPIDEV_with_Cape_Manager
2013년 9월 19일 목요일 오후 8시 27분 40초 UTC+9, mxii@googlemail.com 님의 말:
>
> Hello all.
>
> i have followed several how-to's to init and enable the SPI on beaglebone 
> black!
> init and use is no problem ..
>
> but after the reset the device is not present..
>
> i have modified the "uEnv.txt" ..
>
> but no spi dev after boot up ..
>
> i have to manual get it with this "echo BB... > 
> /sys/devices/bone_capemgr.*/slots" command..
>
> someone else had the same problem?
>
> i think its just a little think.. but what and where? =)
>

-- 
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: Boot from USB or serial

[terry . barnaby47]

We are developing a board based on the TI AM3358 processor and we are using 
the Beaglebone Black as a development test platform prior to the real 
hardware becoming available.
Our system will have eMMC memory but no microSD card so we intend to do a 
boot/install via the USB or serial port.
We are testing this out using the Beaglebone Black but it is not working.
We can boot our own Linux from the microSD card by powering up with the S2 
boot button pressed fine.
However if we power up (via a USB-B cable) without a microSD card and the 
S2 boot button pressed the BBB does not seem to try and boot via the USB or 
serial.
Our host is Linux and a "lsusb" shows no new devices (We were expecting an 
Ethernet gadget device). Minicom or a raw serial port program connected to 
UART0 shows no ASIC id (what ever that is) being sent.
Any ideas ?

-- 
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: Boot from USB or serial

[terry . barnaby47]

We are designing a system based on the TI AM3358 processor and are using a 
Beaglebone black as a development board prior to getting the real hardware.
The real hardware will have eMMC memory but will not have a microSD card 
socket so for a bare metal boot/install we plan to use USB or serial.
We have been trying to do this with our Beaglebone black, but without 
success.
We can boot from our own Linux image on a microSD card by holding down the 
S2 button and powering up fine.
If we remove the microSD card and power up (via a mini USB-B cable plugged 
into the mini USB socket) with S2 pressed the system does not boot, as 
expected, but does not appear to try and boot via USB or serial.
We are using a Linux host system and the command "lsusb" shows no extra 
devices, we were expecting an Ethernet Gadget device. A minicom (or raw 
program) connection to the serial port (UART0) doesn't show any output, we 
were expecting an ASIC id (whatever that looks like).
Any idea why this is not working ?

-- 
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] Failed angstrom build

[geirert]

My build failed the same way.  I am compiling on a Ubuntu 13.10(x64) system. 

Did you find out what the cause was? 

-- 
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: DHT-22 and Beaglebone

[mharrisny1]

Hi,

I am trying to use this code with an Adsong dht22 (am2302) temp/rh sensor 
running on the BBB.  I haven't used C for a number of years so I am kind of 
rusty.  What modifications did you make to compile it with g++ on the BBB? 
 How does portG map to the pinout on the BBB? Or what pin do I connect the 
data line to on the BBB?

Thanks!

On Tuesday, October 8, 2013 11:06:43 AM UTC-4, Lloyd Bailey wrote:
>
> You can modify this code http://www.acmesystems.it/?id=89
>
> I have and it works on my Beaglebone black. :)
>
> On Wednesday, 28 August 2013 04:25:30 UTC+1, CJNZ wrote:
>>
>> Hi Hunyue,
>>
>> I am trying to get the SHT15 working on a classic Beagle.
>> I realise this is an old thread, but I am struggling a bit with the code.
>> Do you still have a code example that you could share?
>> Did you just connect clock and data to standard GPIO and 3.3 and ground?
>>
>> Thanks,
>> CJ
>>
>> On Tuesday, October 16, 2012 7:41:20 PM UTC+13, H wrote:
>>>
>>> On Mon October 15 2012 19:08:51 Aaron Patterson wrote: 
>>> > On Mon, Oct 15, 2012 at 4:58 PM, Dan Watts 
>>>  wrote: 
>>> > > Hi, 
>>> > > 
>>> > > You're right: the Adafruit code does look odd. 
>>> > > 
>>> > > As you say, to initiate communication with the DHT11/DHT22, 
>>> > > you're supposed to pull the signal low for > 18 ms, then 
>>> > > high, then wait for the signal to be pulled low again. 
>>> > > Their code appears to skip the pull-high part.  I can only 
>>> > > assume that the Pi stops pulling the signal low when it 
>>> > > switches to input mode. 
>>> > > 
>>> > > The only possible problem I can see in your code is that you 
>>> > > might not be pulling the signal low for long enough: perhaps 
>>> > > the usleep(2000) should be usleep(2)? Also, trying to 
>>> > > catch that 40 microsecond signal that begins the DHT22's 
>>> > > response is tricky - that's probably why the Pi's code 
>>> > > doesn't pull the line high explicitly.  Perhaps dropping the 
>>> > > digitalWrite(HIGH) from your code would have the same 
>>> > > effect? 
>>> > 
>>> > I gave both of these a whirl, and they did not work.  I am 
>>> >  able to see the signal on my oscilloscope, though I'm new to 
>>> >  using the oscilloscope, so I'm not 100% sure. 
>>> > 
>>> > > I have my doubts about whether reading data from the DHT22 
>>> > > can work reliably from Linux code, given the tight timing 
>>> > > involved.  Apparently the Adafruit code is managing to do it 
>>> > > on the Pi, but there is a warning at the beginning of their 
>>> > > tutorial saying it may not work, and perhaps the library 
>>> > > they are using is more optimized than what is available for 
>>> > > the Bone. 
>>> > 
>>> > Yes, I read that.  I'm starting to have the same doubts as 
>>> >  well. 
>>> > 
>>> > > Personally, I wimped out and use a separate processor to 
>>> > > read the DHT22.  I actually use a .Net Micro Framework 
>>> > > processor for this (which surprisingly is able to handle the 
>>> > > timings) and serial I/O, but something like the ATTiny2313 
>>> > > and I2C would be a better design. 
>>> > 
>>> > I'm starting to think I might need to do the same.  I'll give 
>>> >  the Pi a try, and I've got an Electric Imp on the way, so 
>>> >  I'll probably try it too. 
>>>
>>>
>>> That would appear to be an overkill to toss in another processor. 
>>> Prehaps a different part would be more appropriate? 
>>>
>>> FWIW, I recently got a humidity sensor working on the classic 
>>> Beagle. This is the SHT-15 part. Everything pretty much was drop 
>>> in. Hookup. The setup was: 
>>>
>>> SHT-15 -  - Beagle Classic. 
>>>
>>> Driver for it was all upstream. It is built on top of the GPIO 
>>> subsystem. The level converter and 3.3V are option on the 
>>> beaglelcd board. Write up for it will be posted as time permits. 
>>>
>>> Since IO on the bone is 3.3V, the level converter won't be 
>>> needed. 
>>>
>>> > 
>>> > I've built a meat curing fridge, and I'm trying to build an 
>>> >  internet enabled controller.  I've built a monitor for it 
>>> >  using the TI Launchpad, and I'd like to build something that 
>>> >  will post the information to the internet (without hooking up 
>>> >  to my laptop and reading from a TTY).  I suppose I could try 
>>> >  XBee, but everything seems much harder since I'm not using an 
>>> >  Arduino. :-( 
>>> > 
>>> > Anyway, thanks for the response.  If I can't get the Pi or the 
>>> >  Imp to work out, I'll hook the Launchpad up to the Bone via 
>>> >  UART. 
>>> > 
>>> > Again, thanks for your time.  I appreciate the response! 
>>> > 
>>>
>>> -- 
>>> Hunyue Yau 
>>> http://www.hy-research.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: serial port programming in c++

[arunbarnabasjohn]

On Wednesday, February 19, 2014 9:47:46 PM UTC+5:30, ss sefat wrote:
>
> i connected the arduino usb with bbb. bbb recognize arduino as 
> /dev/ttyACM0 . now i want to communicate with arduino using serial 
> communication in c++ . i tried several times using fopen() .bt bt bbb 
> cannot open "/dev/ttyACM0" for writing. can any one give me a simple demo 
> code which completely works without any error .plz help me. thanks in 
> advance .
>

The usual method of serial port communication used in linux may be used. If 
you search the internet for serial communication using c++ on linux you can 
get many code examples, its not difficult to implement serial communication 
in C++

-- 
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: Availability - how come nobody has any BeagleBone Black to sell?

[anil . gupta778]

Appreciate the figures of 700/day on supply and 140,000 on back orders (200 
days of supply.. phew!).

This is an awesome product. What you saw until October was just people 
trying it out.  They've concluded it is a good product and are ordering it 
in greater quantities.  That is where we are and I hear similar stories 
from others. An order build up of 140,000 in two months, even with supply 
of 700/day suggests an incoming demand of *3500+ per day.*  I believe you 
will see this kind of demand continue.  None of these buyers want to get 
into manufacturing--Circuitco is good at it.  It would be a shame to see a 
great product go sideways due to supply issues.

Given that the main constraint is lead time for some components: if 
sweeteners such as expedite fees can help, I think the community won't mind 
a higher price.. say $48 or $50, to ensure a demand-supply balance.



On Friday, February 21, 2014 9:01:54 AM UTC+5:30, Gerald wrote:
>
> We did this. A year ago when we launched the product. Things were fine 
> until roughly October. Demand has risen due to people 
> using boards in products  They never told anyone about 
> their pending demand. They thought the boards just magically appear in the 
> cabbage patch. 
>
> We build to distributor orders and schedules. We are close to getting out 
> of this.
>
> I appreciate your offer of help. But this is not just a analytic problem. 
> It is a data problem. We have plugged the data into the formula and 
> are adjusting to that new data and working to fill the pipeline and to get 
> orders shipped.
>
> Gerald
>
>
> On Thu, Feb 20, 2014 at 9:21 PM, Anil Gupta 
> > wrote:
>
>> Dave,
>> Gerald,
>>
>> From my experience with product fulfillment: a good plan would establish 
>> a target date when the product would be broadly available in the market 
>> with only occasional shortages.   A key to this is to show back orders as a 
>> % of weekly production, and whether back orders are reducing or increasing 
>> as we fulfill back orders and receive new orders each week.  There would be 
>> a weekly review of whether the target date is likely to be met, production 
>> plan and any changes, and a new date, if needed.  Sudden orders and other 
>> unexpected situations are common in all kinds of fulfillment situations and 
>> there are lots of good systems to deal with this.
>>
>> I am happy to volunteer to do weekly analytics.
>>
>> elinux.org only shows monthly shipments, with little clue around demand 
>> and back order situation.  It is nice to know that "circuitco is in full 
>> production" but we need to provide lots more facts.
>>
>> Dr. Anil Gupta
>>
>>
>> On Wed, Feb 19, 2014 at 2:35 AM, David Anders 
>> 
>> > wrote:
>>
>>> as gerald stated, circuitco is in full production of the beaglebone 
>>> black and continues to ship daily to a wide range of distributors. these 
>>> distributors fill back-orders first before showing stock.
>>>
>>> http://elinux.org/Beagleboard:BeagleBoneBlack#Board_Shipments
>>>
>>> Dave
>>>
>>> On Tuesday, February 18, 2014 1:46:30 AM UTC-6, anil.g...@gmail.comwrote:

 I have been looking for 3+ weeks and unable to find any stock anywhere.

 Is there a way to see the order backlog with Circuitco and current 
 supply capability?  Is the issue getting better or worse? (My anecdotal 
 experience suggests it may be getting worse.)  The current situation is 
 frustrating.  If the news is bad, let us know it early and deal with it. 
  Right now, there is no data at all.

 Gerald: thanks for your timely and open updates.

 On Wednesday, February 12, 2014 1:25:00 AM UTC+5:30, Gerald wrote:
>
> We are focused on the community. Feel free to build it yourself 
> however. All the materials to build it are provided for free and you 
> don't 
> have to pay any development costs.
>  
>
> Gerald
>
>
>
>>  -- 
>> 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] How to install linux-headers-3.8.13-bone30

[jayakarthigeyan]

Can you tell me how install this headers. If you ubuntu-armhf images are 
not supported by your scripts where can I find the image files support by 
yours.

On Friday, 21 February 2014 06:50:25 UTC+5:30, RobertCNelson wrote:
>
>
>
>
> On Thu, Feb 20, 2014 at 6:04 PM, >wrote:
>
>> While trying to prepare a driver to be installed on my beaglebone black I 
>> came across the following error
>>
>> E: Unable to locate package linux-headers-3.8.13-bone30
>> E: Couldn't find any package by regex 'linux-headers-3.8.13-bone30'
>>
>
> These headers?
>
> http://rcn-ee.net/deb/precise-armhf/v3.8.13-bone30/
>
>  
>
>>
>> I am running  Ubuntu 12.04.4 LTS (GNU/Linux 3.8.13-bone30 armv7l) 
>> available at http://www.armhf.com/index.php/download/
>>
>> I downloaded the source at 
>> https://github.com/RobertCNelson/linux-dev/releases/tag/3.8.13-bone30and 
>> then used the command ./build_kernel.sh.
>>
>> After the build, while using the command ./tools/install_kernel.sh as 
>> said at https://github.com/RobertCNelson/linux-dev
>>
>> I got the following message
>>
>> I see...
>> fdisk -l:
>> Disk /dev/mmcblk0: 15.9 GB, 15931539456 bytes
>> Disk /dev/mmcblk1: 1920 MB, 1920991232 bytes
>> Disk /dev/mmcblk1boot1: 1 MB, 1048576 bytes
>> Disk /dev/mmcblk1boot0: 1 MB, 1048576 bytes
>>
>> lsblk:
>> NAME MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
>> mmcblk1boot0 179:16   0 1M  1 disk
>> mmcblk1boot1 179:24   0 1M  1 disk
>> mmcblk0  179:00  14.9G  0 disk
>> |-mmcblk0p1  179:10 1M  0 part 
>> /home/ubuntu/linux-dev-3.8.13-bone30/depl
>> `-mmcblk0p2  179:20  14.9G  0 part /
>> mmcblk1  179:80   1.8G  0 disk
>> |-mmcblk1p1  179:9096M  0 part
>> `-mmcblk1p2  179:10   0   1.7G  0 part
>> -
>> Are you 100% sure, on selecting [/dev/mmcblk0] (y/n)? y
>>
>> Debug: Existing Partition on drive:
>> -
>>
>> Disk /dev/mmcblk0: 15.9 GB, 15931539456 bytes
>> 4 heads, 16 sectors/track, 486192 cylinders, total 31116288 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: 0x80008000
>>
>> Device Boot  Start End  Blocks   Id  System
>> /dev/mmcblk0p1   *2048409510241  FAT12
>> /dev/mmcblk0p240963111628715556096   83  Linux
>>
>> Unmounting Partitions
>> -
>> Starting Partition Search
>> -
>> Trying: [/dev/mmcblk0p1]
>> Partition: [/dev/mmcblk0p1] trying: [vfat], [ext4]
>> Partition: [vfat]
>> Installing 3.8.13-bone30 to /dev/mmcblk0p1
>> `/home/ubuntu/linux-dev-3.8.13-bone30/deploy/3.8.13-bone30.zImage' -> 
>> `/home/ubuntu/linux-dev-3.8.13-bone30/deploy/disk/zImage'
>> cp: writing `/home/ubuntu/linux-dev-3.8.13-bone30/deploy/disk/zImage': No 
>> space left on device
>> cp: failed to extend 
>> `/home/ubuntu/linux-dev-3.8.13-bone30/deploy/disk/zImage': No space left on 
>> device
>> :
>>
>>
>>  In the system.sh file I have set MMC=/dev/mmcblk0
>>
>>  And for your information, I have an expanded file system in which I have 
>> installed ubuntu desktop. 
>>
>
> Patches welcome, "armhf.com's" images are not currently supported by my 
> scripts.
>
> 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] BBB + PREEMPT_RT

[David Goodenough]

On Friday 21 February 2014 03:27:01 Giuseppe Iellamo wrote:
> Or just try Xenomai...
> 
> https://github.com/cdsteinkuehler/linux-dev/tree/3.8.13-bone39-xenomai
> 
While this may be answer to the original poster's question, it is of no
relevance to my point which is that the Sitara processor encourages a 
different way of solving the real time problem by having PRUSS processors
in the SoC to do the real time bits independently of the main processor

David
> 
> Il giorno venerdì 21 febbraio 2014 11:03:24 UTC+1, David Goodenough ha
> 
> scritto:
> > On Friday 21 February 2014 00:20:39 quik...@gmail.com wrote:
> > > I am trying to figure out how to create a kernel for the BBB that
> > 
> > supports
> > 
> > > PREEMPT_RT. It's kind of strange that the BBB's default kernel does not
> > > even have PREEMPT activated. Such a board doesn't fit to many embedded
> > > applications where we need at least some kind of determinism. It is even
> > > worse, that nobody seems to care about this problem. Contrary to that,
> > 
> > the
> > 
> > > Raspberry PI's standard kernel has PREEMPT activacted from the very
> > > beginning.
> > > 
> > > I have tested Robert Nelsons kernel 3.8.13-r9
> > > (https://github.com/beagleboard/kernel/tree/3.8-rt). It does not have
> > > PREEMPT_RT activated by default. When doing so, it does not boot. But
> > > activating PREEMPT does work. However, development of this branch has
> > > stopped several months ago. The official source for RT Linux (3.8.13)
> > 
> > has
> > 
> > > evolved since then. Meanwhile there's an rt17 patch set
> > > (https://www.kernel.org/pub/linux/kernel/projects/rt/3.8/). Did anybody
> > > give this a try? Does it work with the BBB?
> > 
> > Surely the point of the Beaglebone, or rather its processor, is that you
> > do not need to put the time critical bits on the main processor, you put
> > them in the PRUSS processors.
> > 
> > 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: Getting started with bare-metal programming on BBB

[Satz Klauer]

Thanks for the feedback. Meanwhile I'm happy with StarterWare from TI.

On Thu, Feb 20, 2014 at 3:12 PM, Elavarasu  wrote:
> Hi,
>
> There is a way to do baremetal with x-loader as a startup..without the
> emulator.
>
> This link will provide the idea..
>
> http://beagleboard.lohray.com/vm-larix/bare-metal-hello-world
>
>
> --
> Elavarasu.
>
>
> On Saturday, October 19, 2013 7:29:24 PM UTC+5:30, Satz Klauer wrote:
>>
>> Hi,
>>
>> I plan to do some bare-metal programming with the BBB (mainly for personal
>> reasons and to play with hard realtime environments, so please do not try to
>> soften me up to use Linux ;-)
>>
>> As a first task and to get a feeling for the hardware I'd try to access
>> the LEDs (configure the GPIOs they are connected with as digital output and
>> write 0/1 to them).
>>
>> My question: is there a getting-started-guide for this?
>>
>> Or to go more in detail:
>>
>> - I already found the CPU manual at TI's pages
>> - I found a compiler arm-none-eabi-gcc - is it the correct one?
>> - I still need header files where register addresses for the CPU are
>> predefined
>> - I still need a description how to download my created binaries to the
>> board so that they are started immediately (instead of the Linux-Distro)
>>
>> Any Ideas where I can find these things?
>>
>> Thanks!
>>
> --
> 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/gm_GPuYtCCY/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] problem with sending float type data serially using c++

[ss sefat]

i can send 1 byte char type data form bbb serially. now i am stuck with 
sending float type data . here is my code for sending data serially .

fd = open("/dev/ttyO1", O_RDWR | O_NOCTTY);
char byte_out[] = {0x47};
write(fd, byte_out, strlen(byte_out)+1);

how can i write(or send) float type data serially . plz help me . 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] BBB + PREEMPT_RT

[Giuseppe Iellamo]

Or just try Xenomai...

https://github.com/cdsteinkuehler/linux-dev/tree/3.8.13-bone39-xenomai


Il giorno venerdì 21 febbraio 2014 11:03:24 UTC+1, David Goodenough ha 
scritto:
>
> On Friday 21 February 2014 00:20:39 quik...@gmail.com wrote: 
> > I am trying to figure out how to create a kernel for the BBB that 
> supports 
> > PREEMPT_RT. It's kind of strange that the BBB's default kernel does not 
> > even have PREEMPT activated. Such a board doesn't fit to many embedded 
> > applications where we need at least some kind of determinism. It is even 
> > worse, that nobody seems to care about this problem. Contrary to that, 
> the 
> > Raspberry PI's standard kernel has PREEMPT activacted from the very 
> > beginning. 
> > 
> > I have tested Robert Nelsons kernel 3.8.13-r9 
> > (https://github.com/beagleboard/kernel/tree/3.8-rt). It does not have 
> > PREEMPT_RT activated by default. When doing so, it does not boot. But 
> > activating PREEMPT does work. However, development of this branch has 
> > stopped several months ago. The official source for RT Linux (3.8.13) 
> has 
> > evolved since then. Meanwhile there's an rt17 patch set 
> > (https://www.kernel.org/pub/linux/kernel/projects/rt/3.8/). Did anybody 
> > give this a try? Does it work with the BBB? 
> Surely the point of the Beaglebone, or rather its processor, is that you 
> do not need to put the time critical bits on the main processor, you put 
> them in the PRUSS processors. 
>
> 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: learning ARM assy with BBB

[dd]

ok, i ordered the jtag & 16 bit logic analyzer.  away we go.  
i wouldn't expend any effort bashing the status quo.  they are there by 
choice.
rock on! dd
ps why 2 logic analyzers?

On Thursday, February 20, 2014 6:51:24 PM UTC+2, azzythehillbilly mir wrote:
>
> Hi DD, 
> I plan to start a blog of my own as soon as I can get away from making 
> money.
>  
> I will chronicle my struggle with the ARM and will surely 
> fleece/rip apart C, Linux and all that stuff.
> Also might be able to show some of my assembly work.
>  
> Do get the J-tag. it seems easy to use and makes downloading code ( or is 
> it uploading?)a breeze.
>  
> Get your J-tag from Aliexpress. Yes they are all the same. (Segger Clones)
>  
> Also get the Saleae logic 8 and 16 wire  logic analyzers(clone/rip-off) . 
> The 16 bit analyzer at 27US$ post paid is a steal. (@Aliexpress)
> The 16 line because you can set it to monitor only 3 lines so that it may 
> then run at 100MHz. 
> The 8 line device can theoretically do a max of 25 MHz.
>  
> This thing is an extremely useful device. And I do emphasize extremely. 
> About 50 times better than a debug tool or software.
>  
> Azzy
>
>  
>  --
> Date: Thu, 20 Feb 2014 03:00:35 -0800
> From: ddlaw...@rocketmail.com 
> To: beagl...@googlegroups.com 
> Subject: Re: [beagleboard] Re: learning ARM assy with BBB
>
> hi azzy.  i never used a jtag.  i assume they are a standard interface 
> device.  can i buy any jtag?  
> do you you have a website on your work?  sounds interesting..dd
>
> On Thursday, February 20, 2014 8:31:47 AM UTC+2, azzythehillbilly mir 
> wrote: 
>
>   Hi DD,
>  
> AnthonyMerlino.us looks like a good blog.  Thanks for the link
>  
>   I have a J-tag which cost me  US$10.73  post paid from this guy here. 
>  
>
> www.aliexpress.com/item/ARM-Emulator-supports-ARM7-ARM9-ARM11-Cortex-M3-core-ADS-IAR-STM32-ARM-Emulator-JTAG-interface/1457219031.html
>  
> There are a host of others selling the J-Tag on Aliexpress. I would not 
> recommend this seller as they forgot to ship the CD and have never kept 
> their promise to send a replacement. Anyway I downloaded the drivers from 
> J-tag directly. (student version, which is complete) The device seems to be 
> working well.  
>  
> Azzythehillbilly
>  --
> Date: Wed, 19 Feb 2014 08:34:23 -0800
> From: ddlaw...@rocketmail.com
> To: beagl...@googlegroups.com
> Subject: [beagleboard] Re: learning ARM assy with BBB
>
> Hi again Azzy.  Here is a tutorial on the BBB with starterware & a jtag 
> cable.  
>
> http://anthonymerlino.us/uncategorized/getting-started-with-beaglebone-black-bbb-and-starterware
> It looks thorough.  Need to buy jtag first.  It should not be difficult 
> getting around the starterware code.  
> And one can rip their drivers!  
>
> Also, on this forum under thread  
> Confused about developing bare-metal applications for BBB
> Frank Hunleth gives instructions at 7/22/13 and 7/23/13 on how to hack 
> u-boot. 
>
> So, it looks like we have our work cut out for us!  
>
> later..dd
>
> On Monday, October 28, 2013 5:18:24 PM UTC+2, azzythehillbilly mir wrote: 
>
>  Hi Forum,
>  
> I have a problem and I am hoping that I kind soul will direct me whereby I 
> am able to help myself get on my feet.
> This is a bit embarrassing, but here it goes. I got myself a BBB because I 
> want to switch from using  MCS-51 processors and the like.  I have no 
> formal schooling in processors or electronics.  I started working on 
> processors around 1980 when I got hold of an Ohio scientific and later an 
> AppleII+. Later moved to Z80/Z8000/8086/68030 and similar as I started to 
> formally design HW and SW for embedded systems. 
> Never had to bother even with  C so have been hacking merrily away with 
> Assembly only. Rarely adding ( with difficulty) bits of code for floating 
> point when my own extended math routines simply would not do.  This works 
> for me as I have learned to cram as much functionality as possible into 
> limited resources.  I can get working code written and debugged faster than 
> most C coders can. I know nearly zero about Linux//Ubuntu/Fedora. Unless 
> someone has worked on the simple old controllers one might not understand 
> how exciting ( mouth watering even! ) it is to contemplate the peripherals 
> this Sitara 3359 processor provides. I just need to get a jump start.
>  
> Here is the problem, I want to write code for the Sitara-3359 and learn 
> the nuts and bolts of low level programming (assy). I need some kind of a 
> simple IDE Where I can take control of the processor from reset onwards ( 
> barring un-by passable initializing code prewritten  into the processor?).  
> I have been searching all over the net for just that but come up frustrated 
> by the huge number of names/acronyms and all. There are just too many 
> branches to investigate. I get lost every time I try.  For the moment I 
> want merely to exercise

Re: [beagleboard] BBB + PREEMPT_RT

[David Goodenough]

On Friday 21 February 2014 00:20:39 quikcj...@gmail.com wrote:
> I am trying to figure out how to create a kernel for the BBB that supports
> PREEMPT_RT. It's kind of strange that the BBB's default kernel does not
> even have PREEMPT activated. Such a board doesn't fit to many embedded
> applications where we need at least some kind of determinism. It is even
> worse, that nobody seems to care about this problem. Contrary to that, the
> Raspberry PI's standard kernel has PREEMPT activacted from the very
> beginning.
> 
> I have tested Robert Nelsons kernel 3.8.13-r9
> (https://github.com/beagleboard/kernel/tree/3.8-rt). It does not have
> PREEMPT_RT activated by default. When doing so, it does not boot. But
> activating PREEMPT does work. However, development of this branch has
> stopped several months ago. The official source for RT Linux (3.8.13) has
> evolved since then. Meanwhile there's an rt17 patch set
> (https://www.kernel.org/pub/linux/kernel/projects/rt/3.8/). Did anybody
> give this a try? Does it work with the BBB?
Surely the point of the Beaglebone, or rather its processor, is that you
do not need to put the time critical bits on the main processor, you put
them in the PRUSS processors.

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: webmin advice needed

[William Hermans]

Well, my comment was meant to reflect that blanket comments such as these
are silly.

I've been tinkering with a Linux appliance of sorts using the BBB myself.
Granted, the BBB runs headless, and the UI is displayed / partially powered
by the client via Nodejs. This is also very fast.


On Thu, Feb 20, 2014 at 6:33 PM, Ron Morgan  wrote:

>
> I have only been running the BBB headless. I am impressed with how fast it
> is wtihout graphics. the default install is not bad with a gui.. but the
> cpu and ram are quite busy supporting all of that overhead.
>
> actually he works for ibm's server support department. I forgot to ask at
> what level.. but he did support while teaching the class from his laptop. I
> remember he was offten logged into servers that were bought my governments
> around the world and he could fix just about any issue with ssh. he was
> quite hi up in his orgization.
>
> On Thursday, February 20, 2014 12:46:55 AM UTC-7, William Hermans wrote:
>>
>> GUI's are for the weak ? Gee, I hope your instructor does not try to
>> create / sell anything resembling a Linux appliance . . .
>>
>> When working with Linux in a server capacity I do tend to agree though.
>>
>>  --
> 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] BBB + PREEMPT_RT

[Bas Laarhoven]

On 21-2-2014 9:20, quikcj...@gmail.com wrote:
I am trying to figure out how to create a kernel for the BBB that 
supports PREEMPT_RT. It's kind of strange that the BBB's default 
kernel does not even have PREEMPT activated. Such a board doesn't fit 
to many embedded applications where we need at least some kind of 
determinism. It is even worse, that nobody seems to care about this 
problem. Contrary to that, the Raspberry PI's standard kernel has 
PREEMPT activacted from the very beginning.


A long, long time ago (with the original BeagleBone) I tried this, but 
ran into problems with the NIC driver. There's probably a reason it's 
not enabled by default! Feel free to try though, maybe some problems 
have been fixed since then.


-- Bas



I have tested Robert Nelsons kernel 3.8.13-r9 
(https://github.com/beagleboard/kernel/tree/3.8-rt). It does not have 
PREEMPT_RT activated by default. When doing so, it does not boot. But 
activating PREEMPT does work. However, development of this branch has 
stopped several months ago. The official source for RT Linux (3.8.13) 
has evolved since then. Meanwhile there's an rt17 patch set 
(https://www.kernel.org/pub/linux/kernel/projects/rt/3.8/). Did 
anybody give this a try? Does it work with the BBB?



--
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] BBB + PREEMPT_RT

[quikcjack]

I am trying to figure out how to create a kernel for the BBB that supports 
PREEMPT_RT. It's kind of strange that the BBB's default kernel does not 
even have PREEMPT activated. Such a board doesn't fit to many embedded 
applications where we need at least some kind of determinism. It is even 
worse, that nobody seems to care about this problem. Contrary to that, the 
Raspberry PI's standard kernel has PREEMPT activacted from the very 
beginning.

I have tested Robert Nelsons kernel 3.8.13-r9 
(https://github.com/beagleboard/kernel/tree/3.8-rt). It does not have 
PREEMPT_RT activated by default. When doing so, it does not boot. But 
activating PREEMPT does work. However, development of this branch has 
stopped several months ago. The official source for RT Linux (3.8.13) has 
evolved since then. Meanwhile there's an rt17 patch set 
(https://www.kernel.org/pub/linux/kernel/projects/rt/3.8/). Did anybody 
give this a try? Does it work with the BBB?


-- 
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: CLKOUT2 access in RCN 3.12 kernel?

[quikcjack]

Is there really nobody interested in using the GPMC on the BeagleBone Black?


Am Dienstag, 18. Februar 2014 11:35:06 UTC+1 schrieb quik...@gmail.com:
>
> I seems that what you are trying to do is to setup GPMC access on the 
> BeagleBone Black using kernel 3.12.x. The steps to do this are as follows:
>
> (1) You must boot using an external micro SDHC card because the internal 
> eMMC must be disabled
> (2) Disable eMMC and HDMI in uEnv.txt by adding 
> optargs=capemgr.disable_partno=BB-BONE-EMMC-2G,BB-BONELT-HDMI,BB-BONELT-HDMIN
> (3) After booting cape manager will still load both capes. The must be 
> removed manually. 
> (4) In the sources of kernel 3.12.x we must modify 
> /arch/arm/boot/dts/am335x-boneblack.dts to free up the reset pin for the 
> eMMC device. This is done by changing status from "ok" to disabled in 
> section &mmc2
> (5) It should now be possible to load your custom .dts file without any 
> warnings
>
> Unfortunately, the GPMC is still not working in kernel 3.12. I have tested 
> this using 3.12.8 and 3.12.10. I cannot see any activity on the GPMC 
> signals. The same procedure is working in kernel 3.8.13.
>
>
>
> Am Freitag, 17. Januar 2014 17:55:11 UTC+1 schrieb Drew Moore:
>>
>> Thanks for responding..
>>
>> I did
>> grep clkout2 *.dts 
>> in both directories and found that clkout2 didn't show up in the 3.8 but 
>> did show up in 3.12
>> in 3.12 it shows up in am335x-evm.dts and also am335x-evmsk.dts.. (and 
>> dove-cubox.dts but I don't think that is related)
>>
>> I also just noticed that it also shows up in am335x-bone-common.dtsi, 
>> (3.12) which now seems more likely to be the beaglebone related file.
>>
>> Here's that chunk from my device tree file..
>>
>> fragment@0 {
>> target = <&am33xx_pinmux>;
>> __overlay__ {
>> gpmc_pins: pinmux_gpmc_pins {
>> pinctrl-single,pins = <
>> /* 0x20 = Fast, RX_enabled, pullup, pullup_enable, 
>> mode 0 */
>> 0x000 0x20/* gpmc_ad0.gpmc_ad0 MODE0 | INPUT | 
>> PULLUP */
>> 0x004 0x20/* gpmc_ad1.gpmc_ad1 MODE0 | INPUT | 
>> PULLUP */
>> 0x008 0x20/* gpmc_ad2.gpmc_ad2 MODE0 | INPUT | 
>> PULLUP */
>> 0x00C 0x20/* gpmc_ad3.gpmc_ad3 MODE0 | INPUT | 
>> PULLUP */
>> 0x010 0x20/* gpmc_ad4.gpmc_ad4 MODE0 | INPUT | 
>> PULLUP */
>> 0x014 0x20/* gpmc_ad5.gpmc_ad5 MODE0 | INPUT | 
>> PULLUP */
>> 0x018 0x20/* gpmc_ad6.gpmc_ad6 MODE0 | INPUT | 
>> PULLUP */
>> 0x01C 0x20/* gpmc_ad7.gpmc_ad7 MODE0 | INPUT | 
>> PULLUP */
>> 0x020 0x20/* gpmc_ad8.gpmc_ad8 MODE0 | INPUT | 
>> PULLUP */
>> 0x024 0x20/* gpmc_ad9.gpmc_ad9 MODE0 | INPUT | 
>> PULLUP */
>> 0x028 0x20/* gpmc_ad10.gpmc_ad10 MODE0 | INPUT | 
>> PULLUP */
>> 0x02C 0x20/* gpmc_ad11.gpmc_ad11 MODE0 | INPUT | 
>> PULLUP */
>> 0x030 0x20/* gpmc_ad12.gpmc_ad12 MODE0 | INPUT | 
>> PULLUP */
>> 0x034 0x20/* gpmc_ad13.gpmc_ad13 MODE0 | INPUT | 
>> PULLUP */
>> 0x038 0x20/* gpmc_ad14.gpmc_ad14 MODE0 | INPUT | 
>> PULLUP */
>> 0x03C 0x20/* gpmc_ad15.gpmc_ad15 MODE0 | INPUT | 
>> PULLUP */
>>
>> 0x078 0x04/* gpmc_ben1.gpmc_dir MODE4 | OUTPUT */
>> 0x080 0x00/* gpmc_cscn1.gpmc_cscn1 MODE0 | OUTPUT 
>> */
>> 0x08C 0x00/* gpmc_clk.gpmc_clk MODE0 | OUTPUT */
>> 0x090 0x00/* gpmc_advn_ale.gpmc_advn_ale MODE0 | 
>> OUTPUT */
>> 0x094 0x00/* gpmc_oen_ren.gpmc_oen_ren MODE0 | 
>> OUTPUT */
>> 0x098 0x00/* gpmc_wen.gpmc_wen MODE0 | OUTPUT */
>> 0x09C 0x00/* gpmc_ben0_cle.gpmc_ben0_cle MODE0 | 
>> OUTPUT */
>> 0x1b4 0x03/* xdma_event_intr1.clkout2 MODE3 | 
>> OUTPUT */
>> >;
>> };
>> };
>> };
>>
>> I used BB-BONE-CAM3 as a starting point but yes, I'm mostly guessing at 
>> what this stuff means.
>> My next guess is that the last line above is in the wrong section.. 
>> clkout2 is not a gpmc pin.
>>
>> I don't have any /include/ lines in my file.. just 
>> compatible = "ti,beaglebone", "ti,beaglebone-black";
>> from the CAM3 file I modified.
>>
>>
>>
>>

-- 
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 kernel 3.12.10/ GPMC

[quikcjack]

Is there really nobody interested in using the GPMC on the BeagleBone Black?


Am Montag, 17. Februar 2014 12:17:14 UTC+1 schrieb quik...@gmail.com:
>
> I am testing kernel 3.12.10 on the BBB. The system boots without issues. 
> To be able to use the GPMC bus we must disable eMMC and HDMI. I did modify 
> the uEnv.txt accordingly. I also modified
> am335x-boneblack.dts and set status="disabled" in section &mmc2.
>
> After that I can successfully load my .dts file without any errors. I also 
> checked dmesg. But when trying to access the GPMC nothing happens on the 
> GPMC signals. The same .dts file works without issues in kernel 3.8.13. 
>
> Does anybody use the GPMC on the BBB and has done some testings in kernel 
> 3.12.x?
>

-- 
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] Adding splashscreen to u-boot.

[Kishor Dhanawade]

Hello,
I am using Beaglebone black with ubuntu-12.04(3.8.13). I observed 
that penguin logo appears on the screen which is after starting kernel i.e. 
this is kernel splashscreen. I want to add splashscreen during the start of 
u-boot(U-Boot 2014.01). Is it possible??  Has anyone done it for Beaglebone 
Black board?? Where to start ??
   Thanking you.

Regards,
kishor 

-- 
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] DVI on original BB Rev. C3

[Robert Kuhn]

Hi,

RobertCNelson:

Does this attached patch help against: 
> https://github.com/RobertCNelson/armv7-multiplatform (v3.13.x branch) ?
>

Will try that on monday. 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.