[beagleboard] Beagleboard X15 Microsoft Visual Studio GUI example project

[Kevin Hudson]

I am working on a project that uses the Beagleboard X15 as the hardware
platform.  My task is to write a GUI that runs on the X15 using Microsoft
Visual Studio 2017.  Do you know of any example project code that is
available anywhere that I can use to get started and as a reference?  Thank
you for your help.

 

Kevin Hudson

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

Re: [beagleboard] CLoud9 TIDL example sees CMEM Error after recent upgrade

[Kevin de Beer]

Thanks!

This fixed my problems for me.

On Friday, March 27, 2020 at 3:23:17 AM UTC+1, jonnymo wrote:
>
> In the GitHub issue that was filed, I noted the following which seems to 
> get the camera active again:
>
>  
>
> Setting '-d /dev/video1' in the common Makefile seemed to do the trick. I 
> now have video from the camera in the TIDL example.
>
> This is what I changed at line 170 in the Makefile at:
> /var/lib/cloud9/common$
>
> else ifeq ($(PROC),tidl)
> ti-mct-heap-check -c
> sudo mjpg_streamer -i "input_opencv.so -d /dev/video1 -r 640x480 
> --filter ./$(TARGET)$(EXE)" -o "output_http.so -p 8080 -w 
> /usr/share/mjpg-streamer/www"
> else
>
>
>
> On Thu, Mar 26, 2020 at 9:20 AM Robert Nelson  > wrote:
>
>> On Thu, Mar 26, 2020 at 10:27 AM > 
>> wrote:
>> >
>> > Hi,
>> > I just came across this post that is relevant to the same problem. I 
>> just started working on this Beaglebone AI two days ago. I got the latest 
>> os image and updates and upgrades everything. I tried 
>> classification.tidl.cpp and I got the same last message that Jon Morss 
>> got.  And your latest message was about /dev/video0. On my board I got 
>> /dev/video0, /dev/video1 and it does recognize the camera. Do you mean that 
>> I can fix it with the change to the default dev for the camera ? And where 
>> can I change that? I worked with OpenCV and this VideoCapture::open() 
>> failed message seems to indicate a wrong /dev/video index?
>>
>> Please submit a bug to:
>>
>> https://github.com/beagleboard/cloud9-examples
>>
>> the classification demo should allow you to specify a video offset..
>>
>> Regards,
>>
>> -- 
>> Robert Nelson
>> https://rcn-ee.com/
>>
>> -- 
>> For more options, visit http://beagleboard.org/discuss
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to beagl...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/beagleboard/CAOCHtYjyA8yTBWKs-%3DFUoE4kh20XgiQNpheJLfnzHG7_ouqVNA%40mail.gmail.com
>> .
>>
>

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

[beagleboard] Case with cooling fan for Beaglebone AI board

[Kevin Kun Zhang]

I developed a case with cooling fan to solve the BeagleBone AI board 
overheat issue, and it is also a protection to avoid short circuits. 
https://www.fellowintelligence.com.au/sales.html 


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

Re: [beagleboard] Error: selected processor does not support `isb ' in ARM mode

[Kevin McKinney]

This is my version below.

Prompt $ arm-cortex_a8-linux-gnueabihf-gcc --version
arm-cortex_a8-linux-gnueabihf-gcc (crosstool-NG 1.24.0.6-afaf7b9) 8.3.0
Copyright (C) 2018 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

I installed it via:
git clone //github.com/crosstool-ng/crosstool-ng.git
cd crosstool-ng
./bootstrap
./configure --enable-local
make
make install

On Thu, Jul 18, 2019 at 10:39 PM Robert Nelson  wrote:
>
> On Thu, Jul 18, 2019 at 9:01 PM Kevin McKinney  wrote:
> >
> > Hi, I am attempting to cross compile the Linux Kernel 4.20 to be loaded on 
> > my BeagleBone Black, however I am receiving the below error:
> >
> >   AS  usr/initramfs_data.o
> > /tmp/cc6hWxZG.s: Assembler messages:
> > /tmp/cc6hWxZG.s:39: Error: selected processor does not support `isb ' in 
> > ARM mode
> > /tmp/cc6hWxZG.s:90: Error: selected processor does not support `isb ' in 
> > ARM mode
> > /tmp/cc6hWxZG.s:354: Error: selected processor does not support `isb ' in 
> > ARM mode
> > scripts/Makefile.build:291: recipe for target 'arch/arm/vfp/vfpmodule.o' 
> > failed
> > make[1]: *** [arch/arm/vfp/vfpmodule.o] Error 1
> > Makefile:1060: recipe for target 'arch/arm/vfp' failed
> > make: *** [arch/arm/vfp] Error 2
> > make: *** Waiting for unfinished jobs
>
> Your cross compiler smell's fishy...
>
> arm-cortex_a8-linux-gnueabihf-gcc --version
>
> Regards,
>
> --
> Robert Nelson
> https://rcn-ee.com/



-- 
Thanks,
Kevin

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

[beagleboard] Error: selected processor does not support `isb ' in ARM mode

[Kevin McKinney]

Hi, I am attempting to cross compile the Linux Kernel 4.20 to be loaded on 
my BeagleBone Black, however I am receiving the below error:

  AS  usr/initramfs_data.o
/tmp/cc6hWxZG.s: Assembler messages:
/tmp/cc6hWxZG.s:39: Error: selected processor does not support `isb ' in 
ARM mode
/tmp/cc6hWxZG.s:90: Error: selected processor does not support `isb ' in 
ARM mode
/tmp/cc6hWxZG.s:354: Error: selected processor does not support `isb ' in 
ARM mode
scripts/Makefile.build:291: recipe for target 'arch/arm/vfp/vfpmodule.o' 
failed
make[1]: *** [arch/arm/vfp/vfpmodule.o] Error 1
Makefile:1060: recipe for target 'arch/arm/vfp' failed
make: *** [arch/arm/vfp] Error 2
make: *** Waiting for unfinished jobs
  CC  init/do_mounts_rd.o
  AR  usr/built-in.a
  CC  init/do_mounts_initrd.o
/tmp/ccBVuroD.s: Assembler messages:
/tmp/ccBVuroD.s:1680: Error: selected processor does not support `cpsid i' 
in ARM mode
/tmp/ccBVuroD.s:1819: Error: selected processor does not support `cpsid i' 
in ARM mode
/tmp/ccBVuroD.s:1876: Error: selected processor does not support `cpsie i' 
in ARM mode
/tmp/ccBVuroD.s:2073: Error: selected processor does not support `cpsie i' 
in ARM mode
scripts/Makefile.build:291: recipe for target 'init/main.o' failed
make[1]: *** [init/main.o] Error 1
make[1]: *** Waiting for unfinished jobs
/tmp/cc8dytlI.s: Assembler messages:
/tmp/cc8dytlI.s:808: Error: selected processor does not support `dmb ish' 
in ARM mode
/tmp/cc8dytlI.s:811: Error: architectural extension `mp' is not allowed for 
the current base architecture
/tmp/cc8dytlI.s:812: Error: selected processor does not support `pldw [r3]' 
in ARM mode
/tmp/cc8dytlI.s:815: Error: selected processor does not support `pld [r3]' 
in ARM mode
/tmp/cc8dytlI.s:821: Error: selected processor does not support `ldrex 
r2,[r3]' in ARM mode
/tmp/cc8dytlI.s:823: Error: selected processor does not support `strex 
r1,r2,[r3]' in ARM mode
/tmp/cc8dytlI.s:828: Error: selected processor does not support `dmb ish' 
in ARM mode
scripts/Makefile.build:291: recipe for target 'init/do_mounts.o' failed
make[1]: *** [init/do_mounts.o] Error 1
Makefile:1060: recipe for target 'init' failed
make: *** [init] Error 2
ERROR

I am running the below commands, and it is crashing on line 14 "building 
the zImage". Has anyone seen this problem before?

  1 #!/bin/bash
  2 
  3 PATH=${HOME}/x-tools/arm-cortex_a8-linux-gnueabihf/bin/:$PATH
  4 
  5 cd linux-stable
  6 if [ $? != 0 ]; then echo "ERROR"; exit; fi
  7 
  8 make ARCH=arm CROSS_COMPILE=arm-cortex_a8-linux-gnueabihf- mrproper
  9 if [ $? != 0 ]; then echo "ERROR"; exit; fi
 10 
 11 make ARCH=arm multi_v7_defconfig
 12 if [ $? != 0 ]; then echo "ERROR"; exit; fi
 13 
 14 make -j4 ARCH=arm CROSS_COMPILE=arm-cortex_a8-linux-gnueabihf- zImage
 15 if [ $? != 0 ]; then echo "ERROR"; exit; fi
 16 
 17 make -j4 ARCH=arm CROSS_COMPILE=arm-cortex_a8-linux-gnueabihf- modules
 18 if [ $? != 0 ]; then echo "ERROR"; exit; fi
 19 
 20 make ARCH=arm CROSS_COMPILE=arm-cortex_a8-linux-gnueabihf- dtbs
 21 if [ $? != 0 ]; then echo "ERROR"; exit; fi
 22 

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

Re: [beagleboard] HDMI audio with kernel 4.8

[Kevin Matthews]

Hi Robert,

Ok, we'll work on upgrading.

I appreciate the reference and the quick response. I'd seen quite a bit of
audio functionality land in 4.9.x but wasn't sure if it was required - it
can be challenging to prove a negative.

Best,

-Kevin


On Wed, Jun 26, 2019 at 8:14 PM Robert Nelson 
wrote:

> On Wed, Jun 26, 2019 at 7:48 PM  wrote:
> >
> > Hi all,
> >
> > Is it possible to configure HDMI audio on the BeagleBoneBlack using a
> v4.8 stock Linux kernel?
> >
> > I'm working with custom hardware that is based on the BBB schematic and
> stock Linux v4.8. The HDMI circuit is intentionally similar - the DRM and
> McASP pins from the Sitara are connected to a tda19988. We have HDMI video
> working, actually, but I'm struggling to configure the audio. Still
> learning
> >
> > We're largely based on this dts with the McASP pins adjusted to use
> McASP1 instead of McASP0 per the custom hardware.
> >
> > I've noticed that the tda998x driver in kernel v4.8 doesn't support the
> audio-ports setting. Is there another way to configure the audio?
> >
> > I've tried duplicating the above BBB overlay's settings but have found
> that snd_soc_get_dai_name() fails because it can't find the tda19988 in the
> component_list. Specifically, it defers the probe multiple times and
> eventually gives up. Perhaps there is another setting the device tree that
> will add the tda19988 to the DAI list?
> >
> > I've been experimenting with configuring a simple-audio-card with a
> dummy audio codec using the snd-soc-dummy driver. It looks like the
> snd-soc-dummy driver doesn't have any device tree bindings in kernel v4.8,
> but it seems possible to patch them in. However, I'm not sure that this is
> the right way to go.
> >
> > Perhaps there's a different approach entirely?
>
> hdmi took for ever to get in mainline... sadly in 4.9.x
>
>
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/arch/arm/boot/dts/am335x-boneblack.dts?h=v4.9.1&id=8506912b969b60aacc733315eeeb46b014d920a4
>
> Here are some reference commits..
>
> Regards,
>
> --
> Robert Nelson
> https://rcn-ee.com/
>

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

Re: [beagleboard] Re: Board recovery

[Kevin Krugielki]

And they load from the board. There is no SD card being used.

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

Re: [beagleboard] Re: Board recovery

[Kevin Krugielki]

My projects run on the black board. They dont use monitors while we are
using them. I have it out and plugged into a monitor and powered on but
nothing on the screen during boot or while on.

On Sun, May 19, 2019, 9:37 AM Dennis Lee Bieber 
wrote:

> On Sat, 18 May 2019 20:02:03 -0700 (PDT), Kevin Krugielki
>  declaimed
> the following:
>
> >  Long story short. I have thses boards but have no access to them. Is
> there a way i can login and get the code from these without having the user
> info?
>
> Lacking in a lot of information...
>
> WHICH boards? There are a few generations of BeagleBOARDs, a
> BeagleBONE
> white, a few generations of BeagleBONE blacks, and spin-off (WiFi instead
> of Ethernet, the blue, etc.)
>
> Are you running from eMMC or SD card? If you boot from whichever
> is not
> the current running mode, can you gain access? {If the boards are running
> from eMMC, you should be able to get a working SD card and boot from it}.
> Once you have a booted system, MOUNT the other device (if booting from SD
> card, mount the eMMC) -- then copy the passwd and shadow files from the
> working OS to the mounted system (make backups of the original files -- in
> case you need to recreate custom users). Unmount, remove SD card, reboot.
> The passwd and shadow files should contain user/password data for a regular
> board so you should now be able to log in.
>
>
> --
> Wulfraed Dennis Lee Bieber AF6VN
> wlfr...@ix.netcom.com
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/7513ee17qiklkertcbnthgsk3atq9aubn9%404ax.com
> .
> For more options, visit https://groups.google.com/d/optout.
>

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

[beagleboard] Board recovery

[Kevin Krugielki]

Hello everyone,
 
I had a project being built from someone. I paid to develop this project 
and now that it is done we have been using it. But unfortunately i had a 
handshake agreement with him and paid for all the r&d he sold this project to 
anthor company with some minor tweaks to the web UI.Anyways im going to start 
somewhat over and will hire someone else. There was alot of data we used for 
volume calculations and many other variables to write the code. 
  Long story short. I have thses boards but have no access to them. Is there a 
way i can login and get the code from these without having the user info? 

 TIA

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

[beagleboard] P9_25_pinmux not found in /sys/devices/platform/ocp ?

[Kevin M.]

Hi, 

I am currently using a BBB with Debian Jessie 8.8 and 4.4.x kernel 
installed. I was trying to configure the P9_25 pin using the command 
"config-pin P9_25 gpio_pu" but the BBB keeps throwing me the error 

P9_25 pinmux file not found!
> bash: /sys/devices/platform/ocp/ocp*P9_25_pinmux/state: No such file or 
> directory
>
>
I have loaded the cap-universal-00A0 overlay from this github page

https://github.com/cdsteinkuehler/beaglebone-universal-io

and I believe that it should have created a P9_25_pinmux dir in the 
/sys/devices/platform/ocp/ which is apparently missing. 

I have been working on this for a couple of days already mostly because I 
don't know much about embedded system as I'm currently a newbie. Any help 
would be 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/ed6dee5b-77ce-40c8-bc56-2e0e63f3bac1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: eQEP position-compare sync output does not match encoder index pulse

[Kevin B]

For those interested, and electrical engineer solved the problem.

The issue was noise in the A/B channels from the encoder. This was causing 
extra pulses to be registered.


On Tuesday, June 20, 2017 at 9:40:59 AM UTC-7, Kevin B wrote:
>
> Hi all.
>
> I am working on a project using the BBB PRU and eQEP module. At given 
> positions I am using a pulse to trigger the shutter on a camera that is 
> pointed at the motor that is driving the encoder. For testing purposes I am 
> attempting to get a pulse on every rotation so I can easily compare the 
> image from one rotation to the next to confirm that I am properly trigging 
> every rotation. ‘
>
> This is my first time using the BBB, and it has been quite the learning 
> experience. I have been using the AM335x technical reference manual 
> <http://www.ti.com/lit/ds/symlink/am3358.pdf> (starts on page 1650) as a 
> guide for doing this. 
>
>  
>
> The problem:
>
> Using an oscilloscope with the green probe attached to position compare 
> sync output index pin (P8_31) and the red probe attached to the index input 
> from the encoder on each rotation of the motor I am seeing the time between 
> the pulses varying (see attached image Problem.gif, a picture is worth a 
> thousand words). It is important to note that the system technically works, 
> however because the difference in timing I am unable to capture the images 
> that I need. The goal is to be able to consistently get the expected image.
>
>  
>
> Things I have tried:
>
> Switching the sync output pulse between the strobe and index pins. No 
> change in behavior.
>
> Adjusting the value put into the position-compare register. I tried both 
> 4,001 and 3,999. In each case I still see variance between the 
> position-compare sync output and the index pulse.
>
> Hooking the camera shutter up directly to the index pulse from the encoder 
> and the resulting images show little to no change from one rotation to the 
> next. The camera itself is hooked to a PC that is receiving the image. This 
> confirms that my method for capturing images seems adequate.
>
>  
>
> Questions:
>
> I am working on the assumption that the position-compare register on the 
> eQEP module, when set to 4k for my encoder, should exactly match the index 
> pulse coming from the encoder. Is this assumption correct?
>
> Are there any additional debugging steps I could take to determine why 
> this is happening?
>
>  
>
> Technical details:
>
> Linux beaglebone 3.8.13-bone84 #1 SMP Sun Feb 12 02:54:13 UTC 2017 armv7l 
> GNU/Linux
>
>  
>

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

[beagleboard] eQEP position-compare sync output does not match encoder index pulse

[Kevin B]

Hi all.

I am working on a project using the BBB PRU and eQEP module. At given 
positions I am using a pulse to trigger the shutter on a camera that is 
pointed at the motor that is driving the encoder. For testing purposes I am 
attempting to get a pulse on every rotation so I can easily compare the 
image from one rotation to the next to confirm that I am properly trigging 
every rotation. ‘

This is my first time using the BBB, and it has been quite the learning 
experience. I have been using the AM335x technical reference manual 
 (starts on page 1650) as a 
guide for doing this. 

 

The problem:

Using an oscilloscope with the green probe attached to position compare 
sync output index pin (P8_31) and the red probe attached to the index input 
from the encoder on each rotation of the motor I am seeing the time between 
the pulses varying (see attached image Problem.gif, a picture is worth a 
thousand words). It is important to note that the system technically works, 
however because the difference in timing I am unable to capture the images 
that I need. The goal is to be able to consistently get the expected image.

 

Things I have tried:

Switching the sync output pulse between the strobe and index pins. No 
change in behavior.

Adjusting the value put into the position-compare register. I tried both 
4,001 and 3,999. In each case I still see variance between the 
position-compare sync output and the index pulse.

Hooking the camera shutter up directly to the index pulse from the encoder 
and the resulting images show little to no change from one rotation to the 
next. The camera itself is hooked to a PC that is receiving the image. This 
confirms that my method for capturing images seems adequate.

 

Questions:

I am working on the assumption that the position-compare register on the 
eQEP module, when set to 4k for my encoder, should exactly match the index 
pulse coming from the encoder. Is this assumption correct?

Are there any additional debugging steps I could take to determine why this 
is happening?

 

Technical details:

Linux beaglebone 3.8.13-bone84 #1 SMP Sun Feb 12 02:54:13 UTC 2017 armv7l 
GNU/Linux

 

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

.origin 0
.entrypoint START

#include "PRU_encoder.hp"

#define EQEP1 0x48302180
#define QPOSCNT 0x0
#define QPOSCMP 0xC
#define QDECCTL 0x28
#define QEPCTL 0x2A
#define QPOSCTL 0x2E
#define QEINT 0x30
#define QFLG 0x32
#define QCLR 0x34


START:

// Enable OCP master port
LBCO r0, CONST_PRUCFG, 4, 4
CLR  r0, r0, 4 // Clear SYSCFG[STANDBY_INIT] to enable OCP master port
SBCO r0, CONST_PRUCFG, 4, 4

// Configure the block index register for PRU0 by setting c24_blk_index[7:0] and
// c25_blk_index[7:0] field to 0x00 and 0x00, respectively.  This will make C24 point
// to 0x (PRU0 DRAM) and C25 point to 0x2000 (PRU1 DRAM).
MOV r0, 0x
MOV r1, CTBIR_0
SBBO r0, r1, 0x00, 4

//The number of values to watch for
LBCO r1, CONST_PRUDRAM, 4, 4
//LBCO r2, CONST_PRUDRAM, 8, 4
//The starting offset of the values
MOV r2, 0x8

//Load the base address of the EQEP unit
MOV r4, EQEP1

//Enable sync-output
LBBO r5, r4, QDECCTL, 2
SET r5, r5, 13 //Sync output enable, 0=disabled, 1=enabled
CLR r5, r5, 12 //Sync output pin 0=index, 1=strobe
SET r5, r5, 10 //Swap quadrature-clock inputs
SBBO r5, r4, QDECCTL, 2

//Enabled position compare interrupt
LBBO r5, r4, QEINT, 2
CLR r5, r5, 11 //Disable timeout interrupt
SET r5, r5, 8 //Enable position-compare match interrupt
SET r5, r5, 7 //Enable position-compare ready interupt
SBBO r5, r4, QEINT, 2

//Setup the eQEP Position-Compare Control
LBBO r5, r4, QPOSCTL, 2
CLR r5, r5, 15 //Shadow disabled
CLR r5, r5, 14 //Load on QPOSCNT = 0
SET r5, r5, 12 //Enabled Position-compare
//Pins 0-11 control the width of the position-compare output pulse
//0 = 1 x 4 x SYSCLKOUT
//1 = 2 x 4 x SYSCLKOUT
//2-FFF = 3 x 4 x SYSCLKOUT
SET r5, r5, 0
SET r5, r5, 1
SET r5, r5, 2
SET r5, r5, 3
SET r5, r5, 4
SET r5, r5, 5
SET r5, r5, 6
SET r5, r5, 7
SET r5, r5, 8
SET r5, r5, 9
SET r5, r5, 10
SET r5, r5, 11
SET r5, r5, 12
SBBO r5, r4, QPOSCTL, 2

//Set the position counter to reset when the maximum position is reached
LBBO r5, r4, QEPCTL, 2
SET r5, r5, 12 //Enabled position-compare unit
SBBO r5,

[beagleboard] BBBW testing

[Kevin Gordon]

Progress:
The error I struck using grow_partition.sh was: 

Re-reading the partition table ... 
sfdisk: BLKRRPART: Device or resource busy 
sfdisk: The command to re-read the partition table failed. 
Run partprobe(8), kpartx(8) or reboot your system now, 
before using mkfs 
sfdisk: If you created or changed a DOS partition, /dev/foo7, say, then use 
dd(1) 
to zero the first 512 bytes:  dd if=/dev/zero of=/dev/foo7 bs=512 count=1 
(See fdisk(8).) 

I rebooted and ran: 

root@beaglebone:/opt/scripts/tools# ./version.sh 
git:*/opt/scripts/*:[e066cb50c5eda24ce09227b1a155da823d56225a] 
eeprom:[A335BNLTBWA51646BBWG0358] 
dogtag:[BeagleBoard.org Debian Image 2017-02-12] 
bootloader:[/dev/mmcblk0]:[U-Boot 2017.03-rc1-3-ga09f2d] 
bootloader:[/dev/mmcblk1]:[U-Boot 2016.11-rc3-2-g73df7f] 
kernel:[4.4.48-ti-r88] 
nodejs:[v4.7.3] 
root@beaglebone:/opt/scripts/tools# df 
Filesystem 1K-blocksUsed Available Use% Mounted on 
udev   10240   0 10240   0% /dev 
tmpfs  999563036 96920   4% /run 
/dev/mmcblk0p1   7376168 2934944   4090164  42% / 
tmpfs 249884   4249880   1% /dev/shm 
tmpfs   5120   4  5116   1% /run/lock 
tmpfs 249884   0249884   0% /sys/fs/cgroup 
tmpfs  49980   0 49980   0% /run/user/1000 

root@beaglebone:/opt/scripts/tools# fdisk -l /dev/mmcblk0 

Disk /dev/mmcblk0: 7.2 GiB, 7744782336 bytes, 15126528 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 
Disklabel type: dos 
Disk identifier: 0xc9171f1a 

Device Boot Start  End  Sectors  Size Id Type 
/dev/mmcblk0p1 * 8192 15126527 15118336  7.2G 83 Linux 

I HAVE NOT RUN mkfs. 

So there is only one partition BUT it starts at 8192 sectors. Is there 
absolutely nothing pior to 8192 sectors? Is there a MRB in the first 512 
bytes? If I used dd in linux must I allow for that? Why so many sectors 
(8192)? 

The version is: bootloader:[/dev/mmcblk0]:[U-Boot 
2017.03-rc1-3-ga09f2d] Is U-Boot 2017.03-rc1-3 sufficiently up to 
date? 

This is how my slots are at present: 

0: P---L- 0 4D 7.0 LCD CAPE- 4DCAPE-70T ,00A3,4D SYSTEMS ,BB-BONE-LCD7-01 

1: PF -1 

2: PF -1 

3: PF -1 

In /boot/uEnv.txt I uncommented: enable_uboot_overlays=1 and 
disable_uboot_overlay_video=1 

Moved /uEnv.txt to /uEnv.txt.old 

I shutdown the BBBW and it actually shutdown not rebooted After so long 
faulty? 

After restart checked slots which was the same as above. 

In /boot/uEnv.txt I uncommented:disable_uboot_overlay_audio=1 

In /boot/uEnv.txtadded 
cape_enable=bone_capemgr.enable_partno=BB-UART1,BB-I2C1,BB-UART4 

I shutdown the BBBW but it rebooted. 

New slots: 

0: P---L- 0 4D 7.0 LCD CAPE- 4DCAPE-70T ,00A3,4D SYSTEMS ,BB-BONE-LCD7-01 

1: PF -1 

2: PF -1 

3: PF -1 

4: P-O-L- 1 Override Board Name,00A0,Override Manuf,BB-UART1 

5: P-O-L- 2 Override Board Name,00A0,Override Manuf,BB-I2C1 

6: P-O-L- 3 Override Board Name,00A0,Override Manuf,BB-UART4 

I tried adding BB-ADC with no effect. BB-BONE-LCD7-01 uses some of AIN 
pins. AIN0 to AIN3? Not sure. 

root@beaglebone:/home/debian# cd /sys/bus/iio/devices/iio:device0 
root@beaglebone:/sys/bus/iio/devices/iio:device0# ls -al 
total 0 
drwxr-xr-x 5 root root0 Feb 20 23:41 . 
drwxr-xr-x 4 root root0 Feb 20 23:41 .. 
drwxr-xr-x 2 root root0 Feb 21 03:49 buffer 
-r--r--r-- 1 root root 4096 Feb 21 03:49 dev 
-rw-r--r-- 1 root root 4096 Feb 21 03:49 in_voltage4_raw 
-rw-r--r-- 1 root root 4096 Feb 21 03:49 in_voltage5_raw 
-rw-r--r-- 1 root root 4096 Feb 21 03:49 in_voltage6_raw 
-rw-r--r-- 1 root root 4096 Feb 21 03:49 in_voltage7_raw 
-r--r--r-- 1 root root 4096 Feb 21 03:49 name 
lrwxrwxrwx 1 root root0 Feb 21 03:49 of_node -> 
../../../../../../firmware/devicetree/base/ocp/tscadc@44e0d000/adc 
drwxr-xr-x 2 root root0 Feb 21 03:49 power 
drwxr-xr-x 2 root root0 Feb 21 03:49 scan_elements 
lrwxrwxrwx 1 root root0 Feb 21 03:49 subsystem -> 
../../../../../../bus/iio 
-rw-r--r-- 1 root root 4096 Feb 20 23:41 uevent 
root@beaglebone:/sys/bus/iio/devices/iio:device0# 

I guess from the above I can use AIN3 to AIN6? 

The important result is that using uboot overlays does NOT impact on 
wireless. 

Regards, 

Kevin. 

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

[beagleboard] Re: Testing BBBW

[Kevin & Pauline Gordon]

Hi Robert,

The error I struck using grow_partition.sh was:

Re-reading the partition table ...
sfdisk: BLKRRPART: Device or resource busy
sfdisk: The command to re-read the partition table failed.
Run partprobe(8), kpartx(8) or reboot your system now,
before using mkfs
sfdisk: If you created or changed a DOS partition, /dev/foo7, say, then 
use dd(1)

to zero the first 512 bytes:  dd if=/dev/zero of=/dev/foo7 bs=512 count=1
(See fdisk(8).)

I rebooted and ran:

root@beaglebone:/opt/scripts/tools# ./version.sh
git:/opt/scripts/:[e066cb50c5eda24ce09227b1a155da823d56225a]
eeprom:[A335BNLTBWA51646BBWG0358]
dogtag:[BeagleBoard.org Debian Image 2017-02-12]
bootloader:[/dev/mmcblk0]:[U-Boot 2017.03-rc1-3-ga09f2d]
bootloader:[/dev/mmcblk1]:[U-Boot 2016.11-rc3-2-g73df7f]
kernel:[4.4.48-ti-r88]
nodejs:[v4.7.3]
root@beaglebone:/opt/scripts/tools# df
Filesystem 1K-blocksUsed Available Use% Mounted on
udev   10240   0 10240   0% /dev
tmpfs  999563036 96920   4% /run
/dev/mmcblk0p1   7376168 2934944   4090164  42% /
tmpfs 249884   4249880   1% /dev/shm
tmpfs   5120   4  5116   1% /run/lock
tmpfs 249884   0249884   0% /sys/fs/cgroup
tmpfs  49980   0 49980   0% /run/user/1000

root@beaglebone:/opt/scripts/tools# fdisk -l /dev/mmcblk0

Disk /dev/mmcblk0: 7.2 GiB, 7744782336 bytes, 15126528 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
Disklabel type: dos
Disk identifier: 0xc9171f1a

Device Boot Start  End  Sectors  Size Id Type
/dev/mmcblk0p1 * 8192 15126527 15118336  7.2G 83 Linux

I HAVE NOT RUN mkfs.

So there is only one partition BUT it starts at 8192 sectors. Is there 
absolutely nothing pior to 8192 sectors? Is there a MRB in the first 512 
bytes? If I used dd in linux must I allow for that? Why so many sectors 
(8192)?


The version is: bootloader:[/dev/mmcblk0]:[U-Boot 
2017.03-rc1-3-ga09f2d] Is U-Boot 2017.03-rc1-3 sufficiently up 
to date?


This is how my slots are at present:

0: P---L- 0 4D 7.0 LCD CAPE- 4DCAPE-70T ,00A3,4D SYSTEMS ,BB-BONE-LCD7-01

1: PF -1

2: PF -1

3: PF -1

In /boot/uEnv.txt I uncommented: enable_uboot_overlays=1 and 
disable_uboot_overlay_video=1


Moved /uEnv.txt to /uEnv.txt.old

I shutdown the BBBW and it actually shutdown not rebooted After so 
long faulty?


After restart checked slots which was the same as above.

In /boot/uEnv.txt I uncommented:disable_uboot_overlay_audio=1

In /boot/uEnv.txtadded 
cape_enable=bone_capemgr.enable_partno=BB-UART1,BB-I2C1,BB-UART4


I shutdown the BBBW but it rebooted.

New slots:

0: P---L- 0 4D 7.0 LCD CAPE- 4DCAPE-70T ,00A3,4D SYSTEMS ,BB-BONE-LCD7-01

1: PF -1

2: PF -1

3: PF -1

4: P-O-L- 1 Override Board Name,00A0,Override Manuf,BB-UART1

5: P-O-L- 2 Override Board Name,00A0,Override Manuf,BB-I2C1

6: P-O-L- 3 Override Board Name,00A0,Override Manuf,BB-UART4

I tried adding BB-ADC with no effect. BB-BONE-LCD7-01 uses some of AIN 
pins. AIN0 to AIN3? Not sure.


root@beaglebone:/home/debian# cd /sys/bus/iio/devices/iio:device0
root@beaglebone:/sys/bus/iio/devices/iio:device0# ls -al
total 0
drwxr-xr-x 5 root root0 Feb 20 23:41 .
drwxr-xr-x 4 root root0 Feb 20 23:41 ..
drwxr-xr-x 2 root root0 Feb 21 03:49 buffer
-r--r--r-- 1 root root 4096 Feb 21 03:49 dev
-rw-r--r-- 1 root root 4096 Feb 21 03:49 in_voltage4_raw
-rw-r--r-- 1 root root 4096 Feb 21 03:49 in_voltage5_raw
-rw-r--r-- 1 root root 4096 Feb 21 03:49 in_voltage6_raw
-rw-r--r-- 1 root root 4096 Feb 21 03:49 in_voltage7_raw
-r--r--r-- 1 root root 4096 Feb 21 03:49 name
lrwxrwxrwx 1 root root0 Feb 21 03:49 of_node -> 
../../../../../../firmware/devicetree/base/ocp/tscadc@44e0d000/adc

drwxr-xr-x 2 root root0 Feb 21 03:49 power
drwxr-xr-x 2 root root0 Feb 21 03:49 scan_elements
lrwxrwxrwx 1 root root0 Feb 21 03:49 subsystem -> 
../../../../../../bus/iio

-rw-r--r-- 1 root root 4096 Feb 20 23:41 uevent
root@beaglebone:/sys/bus/iio/devices/iio:device0#

I guess from the above I can use AIN3 to AIN6?

The important result is that using uboot overlays does NOT impact on 
wireless.


Regards,

Kevin.

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

To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/03acef72-4bc9-a07a-bfdd-14339b64b014%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Testing BBBW

[Kevin & Pauline Gordon]

Many thanks Robert. In the past I have used 
https://www.sdcard.org/downloads/formatter_4/ and 
https://sourceforge.net/projects/win32diskimager/ to make my sdcards. 
Your script finds errors in their result.


Using linux how do you suggest I should make my sdcards compatiable with 
your script?


Regards,

Kevin.








































































































































































































































































On 2/20/2017 3:33 AM, Robert Nelson wrote:

On Sun, Feb 19, 2017 at 9:25 PM, Kevin & Pauline Gordon
  wrote:

Has something changed with bone-debian-8.7-lxqt-4gb-armhf-2017-02-12-4gb.img
?

root@kgDebian:/home/kevin# fdisk /dev/sdc1

Welcome to fdisk (util-linux 2.25.2).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.

/dev/sdc1: device contains a valid 'ext4' signature, it's strongly
recommended to wipe the device by command wipefs(8) if this setup is
unexpected to avoid possible collisions.

Device does not contain a recognized partition table.
Created a new DOS disklabel with disk identifier 0x10b30ea5.

Command (m for help): q

root@kgDebian:/home/kevin# umount -v /dev/sdc1
umount: /media/kevin/rootfs (/dev/sdc1) unmounted

I have not seen this message before: Device does not contain a recognized
partition table.

What is the best way to increase the partition size?

bootup once and use the built-in script:

http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Expanding_File_System_Partition_On_A_microSD

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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/003895e8-41db-e8a6-ea20-93d6487b82b7%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Testing BBBW

[Kevin & Pauline Gordon]

Has something changed with 
bone-debian-8.7-lxqt-4gb-armhf-2017-02-12-4gb.img ?


root@kgDebian:/home/kevin# fdisk /dev/sdc1

Welcome to fdisk (util-linux 2.25.2).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.

/dev/sdc1: device contains a valid 'ext4' signature, it's strongly 
recommended to wipe the device by command wipefs(8) if this setup is 
unexpected to avoid possible collisions.


Device does not contain a recognized partition table.
Created a new DOS disklabel with disk identifier 0x10b30ea5.

Command (m for help): q

root@kgDebian:/home/kevin# umount -v /dev/sdc1
umount: /media/kevin/rootfs (/dev/sdc1) unmounted

I have not seen this message before: Device does not contain a 
recognized partition table.


What is the best way to increase the partition size?

Many thanks,

Kevin.

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

To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/8d10a308-b884-5b4c-cb6a-dc68e9069c7a%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: BBBW wlan0 testing

[Kevin Gordon]

Extra item (9) #shutdown no longer is successful. BBBW immediately self 
reboots..

On Sunday, 19 February 2017 16:06:16 UTC+13, Kevin Gordon wrote:
>
> I have been trying to resolve what causes a successful setup of connman to 
> fail in Beaglebone Black Wireless. These are the steps:
> (1) Make a SDcard using bone-debian-8.7-lxqt-4gb-armhf-2017-02-12-4gb 
> (successful)
> (2) Use connmamctl to setup wlan0 (successful)
> (3) #apt-get update #apt-get install leafpad #apt-get install gdbserver 
> (successful)
> (4) #nano /boot/uEnv.txt (remove # from 
> "dtb=am335x-boneblack-emmc-overlay.dtb")
> (5) reboot
> (5) #ifconfig -a (HEY wlan0 has disappeared and eth0 is now present with 
> no internet)
> (6) #nano /boot/uEnv.txt (replace # in front of 
> "dtb=am335x-boneblack-emmc-overlay.dtb")
> (7) #reboot
> (8) #ifconfig -a (HEY wlan0 has appeared and eth0 reappeared with internet 
> working!)
> @RobertCNelson please help!
>

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

[beagleboard] BBBW wlan0 testing

[Kevin Gordon]

I have been trying to resolve what causes a successful setup of connman to 
fail in Beaglebone Black Wireless. These are the steps:
(1) Make a SDcard using bone-debian-8.7-lxqt-4gb-armhf-2017-02-12-4gb 
(successful)
(2) Use connmamctl to setup wlan0 (successful)
(3) #apt-get update #apt-get install leafpad #apt-get install gdbserver 
(successful)
(4) #nano /boot/uEnv.txt (remove # from 
"dtb=am335x-boneblack-emmc-overlay.dtb")
(5) reboot
(5) #ifconfig -a (HEY wlan0 has disappeared and eth0 is now present with no 
internet)
(6) #nano /boot/uEnv.txt (replace # in front of 
"dtb=am335x-boneblack-emmc-overlay.dtb")
(7) #reboot
(8) #ifconfig -a (HEY wlan0 has appeared and eth0 reappeared with internet 
working!)
@RobertCNelson please help!

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

[beagleboard] Re: PRU pruss_uio: pins are not configured from the driver error

[Kevin Cox]

ok, so I have a working PRU_gpioToggle example on PRU 1 using the uio_pruss 
driver.  After some trial and error and alot of searching the forums I was 
able to create an overlay that worked:

*modified the uio_pruss_enable.dts file to look like below, could have 
created a new file as well.  I took most of everything below from 
/opt/source/bb.org-overlays/src/arm/cape-universal.dts. 
 dtb=am335x-boneblack-emmc-overlay.dtb in /boot/uEnv.txt I believe, keeps 
cape-universal from loading which would interfere with my overlay.*

/dts-v1/;
/plugin/;

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

// identification
part-number = "uio_pruss_enable";
version = "00A0";

exclusive-use =
   "P8.11", "pru0", "pru1", "pruss";

fragment@0 {
   target = <&am33xx_pinmux>;
   __overlay__ {
  P8_11_pruout_pin: pinmux_P8_11_pruout_pin { /* Mode 6, 
Pull-Down, RxActive */
 pinctrl-single,pins = <0x034  0x26>;
  };
   };
};

fragment@1 {
   target = <&ocp>;
   __overlay__ {
  P8_11_pinmux {
 compatible = "bone-pinmux-helper";
 status = "okay";
 pinctrl-names = "pruout";
 pinctrl-0 = <&P8_11_pruout_pin>;
  };
   };
};

  };

*Then using  config-pin:*   
   config-pin overlay uio_pruss_enable
   config-pin P8_11 pruout

*cat  /sys/devices/platform/ocp/ocp:P8_11_pinmux/state*
   pruout

*cat /sys/devices/platform/bone_capemgr/slots*
0: PF  -1
1: PF  -1
2: PF  -1
3: PF  -1
4: P-O-L-   0 Override Board Name,00A0,Override Manuf,uio_pruss_enable

Side note: if using PRU_gpioToggle example need to modify gpio=0x8000 to 
toggle P8_11.

On Tuesday, January 17, 2017 at 12:14:40 PM UTC-5, Kevin Cox wrote:
>
> I am trying to toggle a GPIO pin (P8_11) using PRU0.  I was able to load 
> the uio_pruss driver by using the steps below, when I do lsmod this looks 
> correct as well.  I also am able to load a program successfully into the 
> PRU using the prussdrv_xxx interface.  However it looks like I do not have 
> my overlay correct.  I modified the uio_pruss_enable-A00.dts overlay file 
> (see below) based on the most current posts I could find.  Yet my dmesg 
> output shows a "pins are not configured from the driver" error and
> I do not see the correct value (6) for pin 15 in the pinmux file. I don't 
> understand when/how uio_pruss driver picks up the changes in the 
> uio_pruss_enable file or whether I have it in the correct format.  There 
> seems to be multiple ways this file can be configured depending on kernel 
> and kernel version.
>
> *modify uEnv.txt*
>dtb=am335x-boneblack-emmc-overlay.dtb
>cape_enable=bone_capemgr.enable_partno=uio_pruss_enable
>
> *modify am335x-boneblack-emmc-overlay.dt*b
> #include "am33xx-pruss-uio.dtsi"
>
> *modify /etc/modprobe.d/pruss-blacklist.con*f
>blacklist pruss
>blacklist pruss_intc
>blacklist pru-rproc
>
> *root@beaglebone:~# lsmod | grep pru*
> uio_pruss   5504  0
> uio10524  2 uio_pruss,uio_pdrv_genirq
>
> uname -a
>4.4.30-ti-r64
>
> */sys/kernel/debug/pinctrl/44e10800.pinmux/pins*:
>pin 15 (44e1083c.0) 0027 pinctrl-single
>
> *modified /opt/source/bb.org-overlays/src/arm/uio_pruss_enable-00A0.dts*
> /dts-v1/;
> /plugin/;
> / {
> compatible = "ti,beaglebone", "ti,beaglebone-black", 
> "ti,beaglebone-green";
> // identification
> part-number = "uio_pruss_enable";
> version = "00A0";
>
> exclusive-use =
>"P8.11", "pru0";
>
> fragment@0 {
>target = <&am33xx_pinmux>;
>__overlay__ {
>   pru_pru_pins: pinmux_pru_pru_pins {
>
>   pinctrl-single,pins = <
>  0x34 0x06
>  >;
>   };
>};
> };
>
> fragment@1 {
>target = <&ocp>;
>__overlay__ {
>   test_helper: helper {
>  compatible = "bone-pinmux-helper";
>  pinctrl-names = "default";
>  pinctrl-0 = <&pru_pru_pins>;
>  status = "okay";
>   };
>};
> };
>   };
>
> *compiled using: dtc -@ -O dtb -b 0 -o 
> /lib/firmware/uio_pruss_e

[beagleboard] Re: PRU pruss_uio: pins are not configured from the driver error

[Kevin Cox]

Thank you Robert.  I have previously tried that source with the pruss node. 
 It's where I started.  When it didn't work, I tried other variants from 
other people's posts.  Below is the decoded output of my dtbo file with the 
pruss node.  I've also trued it with fragment@1 instead of fragment@2. 
 I've also tried with both ocp node and pruss node.

*dtc -I dts uio_pruss_enable-00A0.dts*
/dts-v1/;

/ {
compatible = "ti,beaglebone", "ti,beaglebone-black", 
"ti,beaglebone-green";
part-number = "uio_pruss_enable";
version = "00A0";
exclusive-use = "P8.11", "pru0", "pru1";
fragment@0 {
target = <0xdeadbeef>;
__overlay__ {
pinmux_pru_pru_pins {
pinctrl-single,pins = <0x34 0x6>;
linux,phandle = <0x1>;
phandle = <0x1>;
};
};
};
fragment@2 {
target = <0xdeadbeef>;
__overlay__ {
status = "okay";
pinctrl-names = "default";
pinctrl-0 = <0x1>;
};
};
__symbols__ {
pru_pru_pins = 
"/fragment@0/__overlay__/pinmux_pru_pru_pins";
};
__local_fixups__ {
fragment@2 {
__overlay__ {
pinctrl-0 = <0x0>;
};
};
};
__fixups__ {
am33xx_pinmux = "/fragment@0:target:0";
pruss = "/fragment@2:target:0";
};
};


On Tuesday, January 17, 2017 at 12:14:40 PM UTC-5, Kevin Cox wrote:
>
> I am trying to toggle a GPIO pin (P8_11) using PRU0.  I was able to load 
> the uio_pruss driver by using the steps below, when I do lsmod this looks 
> correct as well.  I also am able to load a program successfully into the 
> PRU using the prussdrv_xxx interface.  However it looks like I do not have 
> my overlay correct.  I modified the uio_pruss_enable-A00.dts overlay file 
> (see below) based on the most current posts I could find.  Yet my dmesg 
> output shows a "pins are not configured from the driver" error and
> I do not see the correct value (6) for pin 15 in the pinmux file. I don't 
> understand when/how uio_pruss driver picks up the changes in the 
> uio_pruss_enable file or whether I have it in the correct format.  There 
> seems to be multiple ways this file can be configured depending on kernel 
> and kernel version.
>
> *modify uEnv.txt*
>dtb=am335x-boneblack-emmc-overlay.dtb
>cape_enable=bone_capemgr.enable_partno=uio_pruss_enable
>
> *modify am335x-boneblack-emmc-overlay.dt*b
> #include "am33xx-pruss-uio.dtsi"
>
> *modify /etc/modprobe.d/pruss-blacklist.con*f
>blacklist pruss
>blacklist pruss_intc
>blacklist pru-rproc
>
> *root@beaglebone:~# lsmod | grep pru*
> uio_pruss   5504  0
> uio10524  2 uio_pruss,uio_pdrv_genirq
>
> uname -a
>4.4.30-ti-r64
>
> */sys/kernel/debug/pinctrl/44e10800.pinmux/pins*:
>pin 15 (44e1083c.0) 0027 pinctrl-single
>
> *modified /opt/source/bb.org-overlays/src/arm/uio_pruss_enable-00A0.dts*
> /dts-v1/;
> /plugin/;
> / {
> compatible = "ti,beaglebone", "ti,beaglebone-black", 
> "ti,beaglebone-green";
> // identification
> part-number = "uio_pruss_enable";
> version = "00A0";
>
> exclusive-use =
>"P8.11", "pru0";
>
> fragment@0 {
>target = <&am33xx_pinmux>;
>__overlay__ {
>   pru_pru_pins: pinmux_pru_pru_pins {
>
>   pinctrl-single,pins = <
>  0x34 0x06
>  >;
>   };
>};
> };
>
> fragment@1 {
>target = <&ocp>;
>__overlay__ {
>   test_helper: helper {
>  compatible = "bone-pinmux-helper";
>  pinctrl-names = "default";
>  pinctrl-0 = <&pru_pru_pins>;
>  status = "okay";
>   };
>};
> };
>   };
>
> *compiled using: dtc -@ -O dtb -b 0 -o 
> /lib/firmware/uio_pruss_enable-00A0.dtbo 
> /opt/source/bb.org-overlays/src/arm/uio_pruss_enable-00A0.dts*
>
>
> *dmesg*
> [0.00] Kernel comman

[beagleboard] PRU pruss_uio: pins are not configured from the driver error

[Kevin Cox]

I am trying to toggle a GPIO pin (P8_11) using PRU0.  I was able to load 
the uio_pruss driver by using the steps below, when I do lsmod this looks 
correct as well.  I also am able to load a program successfully into the 
PRU using the prussdrv_xxx interface.  However it looks like I do not have 
my overlay correct.  I modified the uio_pruss_enable-A00.dts overlay file 
(see below) based on the most current posts I could find.  Yet my dmesg 
output shows a "pins are not configured from the driver" error and
I do not see the correct value (6) for pin 15 in the pinmux file. I don't 
understand when/how uio_pruss driver picks up the changes in the 
uio_pruss_enable file or whether I have it in the correct format.  There 
seems to be multiple ways this file can be configured depending on kernel 
and kernel version.

*modify uEnv.txt*
   dtb=am335x-boneblack-emmc-overlay.dtb
   cape_enable=bone_capemgr.enable_partno=uio_pruss_enable

*modify am335x-boneblack-emmc-overlay.dt*b
#include "am33xx-pruss-uio.dtsi"

*modify /etc/modprobe.d/pruss-blacklist.con*f
   blacklist pruss
   blacklist pruss_intc
   blacklist pru-rproc

*root@beaglebone:~# lsmod | grep pru*
uio_pruss   5504  0
uio10524  2 uio_pruss,uio_pdrv_genirq

uname -a
   4.4.30-ti-r64

*/sys/kernel/debug/pinctrl/44e10800.pinmux/pins*:
   pin 15 (44e1083c.0) 0027 pinctrl-single

*modified /opt/source/bb.org-overlays/src/arm/uio_pruss_enable-00A0.dts*
/dts-v1/;
/plugin/;
/ {
compatible = "ti,beaglebone", "ti,beaglebone-black", 
"ti,beaglebone-green";
// identification
part-number = "uio_pruss_enable";
version = "00A0";

exclusive-use =
   "P8.11", "pru0";

fragment@0 {
   target = <&am33xx_pinmux>;
   __overlay__ {
  pru_pru_pins: pinmux_pru_pru_pins {

  pinctrl-single,pins = <
 0x34 0x06
 >;
  };
   };
};

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

*compiled using: dtc -@ -O dtb -b 0 -o 
/lib/firmware/uio_pruss_enable-00A0.dtbo 
/opt/source/bb.org-overlays/src/arm/uio_pruss_enable-00A0.dts*


*dmesg*
[0.00] Kernel command line: console=tty0 console=ttyO0,115200n8 
bone_capemgr.enable_partno=uio_pruss_enable root=/dev/mmcblk0p1 
rootfstype=ext4 rootwait coherent_pool=1M quiet cape_universal=enable
[2.531643] bone_capemgr bone_capemgr: enabled_partno PARTNO 
'uio_pruss_enable' VER 'N/A' PR '0'
[2.531685] bone_capemgr bone_capemgr: slot #4: 'Override Board 
Name,00A0,Override Manuf,uio_pruss_enable'
[2.538684] bone_capemgr bone_capemgr: slot #4: dtbo 
'uio_pruss_enable-00A0.dtbo' loaded; overlay id #0
[   40.091997] pruss_uio 4a30.pruss: pins are not configured from the 
driver

*root@beaglebone:~# cat /sys/devices/platform/bone_capemgr/slots*
 0: PF  -1
 1: PF  -1
 2: PF  -1
 3: PF  -1
 4: P-O-L-   0 Override Board Name,00A0,Override Manuf,uio_pruss_enable

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

[beagleboard] Testing BBBW Wireless Setup

[Kevin Gordon]

The steps taken were as follows (same as on 
http://www.rescuerobot.org/drupal/?q=content/beaglebone-black-wireless).
Made an SD Card from bone-debian-8.6-lxqt-4gb-armhf-2017-01-10-4gb.img.xz.
Booted BBBW from card.
>From a Windows 10 PC using TeraTERM connected on 192.168.8.1
Changed timezone.
Completed Wireless configuration using connmanctl:
root@beaglebone:~# connmanctl
Error getting VPN connections: The name net.connman.vpn was not provided by 
any connmanctl> scan wifi
Scan completed for wifi
connmanctl> services
KGNETGEARwifi_506583d635bb_4b474e455447454152_managed_psk
JandJwifi_506583d635bb_4a616e644a_managed_psk
connmanctl> agent on
Agent registered
connmanctl> connect wifi_506583d635bb_4b474e455447454152_managed_psk
Agent RequestInput wifi_506583d635bb_4b474e455447454152_managed_psk
  Passphrase = [ Type=psk, Requirement=mandatory, Alternates=[ WPS ] ]
  WPS = [ Type=wpspin, Requirement=alternate ]
Passphrase? xxx
Connected wifi_506583d635bb_4b474e455447454152_managed_psk
connmanctl> quit
root@beaglebone:~# ifconfig wlan0
wlan0 Link encap:Ethernet  HWaddr 50:65:83:d6:35:bb
  inet addr:192.168.1.4  Bcast:192.168.1.255  Mask:255.255.255.0
  inet6 addr: fe80::5265:83ff:fed6:35bb/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST DYNAMIC  MTU:1500  Metric:1
  RX packets:62 errors:0 dropped:0 overruns:0 frame:0
  TX packets:75 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:10341 (10.0 KiB)  TX bytes:16478 (16.0 KiB)

root@beaglebone:~# apt-get update
root@beaglebone:~# apt-get install leafpad
root@beaglebone:~# apt-get install build-essential git-core 
device-tree-compiler
root@beaglebone:~# apt-get install gdbserver

Edited the /boot/uEnv.txt file.
Removed the "#" from "dtb=am335x-boneblack-emmc-overlay.dtb"
New line added: "cape_enable=bone_capemgr.enable_partno=BB-UART1,BB-I2C1"

Rebooted the BBBW.

ran ifconfig -a
No wlan0 or SoftAp0. Replaced by eth0.

If I try to shutdown the BBBW immediately reboots. 
Is there a possible repair or should I make a new SD Card?

Regards,
Kevin.

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

[beagleboard] Using Android Cellphone to connect to BBBW

[Kevin Gordon]

Setting up connection:
Password:
BeagleBone-nnYZ
Proxy: none
IP Settings: Static
IP Address: 192.168.8.2
Gateway: 192.168.8.1
Network prefix length: 24
DNS 1: 8.8.8.8
DNS 2: 8.8.4.4

Is there a password?
Should the above work?
Many thanks,
Kevin.

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

[beagleboard] Re: Error using connmanctl> enable wifi BBBW

[Kevin Gordon]

Thank you Robert for your reply. I am sending this message from my BBBW. I 
have attached a file showing my configuration. At the beginning of the file 
I have a typing error as I missed the last letter in the connection string 
.psk
I was unable to use journalctl | grep connman (Error:bash :connman: command 
not found
Many thanks,
Kevin
http://www.rescuerobot.org/drupal/?q=content/beaglebone-black-bbb-and-debugging-eclipse

On Friday, 6 January 2017 15:27:40 UTC+13, Kevin Gordon wrote:
>
> I have received a BBBW yesterday. I booted from a SD Card (which has image 
> bone-debian-8.6-lxqt-4gb-armhf-2016-11-06-4gb) previously used on a BBB rev 
> C. Everything functions the same on the BBBW as on the BBB except the 
> network (wired) (the only item listed in connman gui) is not functioning 
> (fair enough). When I run connmanctl> enable wifi BBBW I have error 
> message:"Method "SetProperty" with signature "sv" on interface 
> "net.connman.Technology" doesn't exist".
> Is there a solution for this please?
> Kevin.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/4515aafe-f6c2-49d0-91c3-e3689174141b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
root@beaglebone:~# connmanctl
Error getting VPN connections: The name net.connman.vpn was not 
providedconnmanctl> enable wifi
Error wifi: Already enabled
connmanctl> scan wifi
Scan completed for wifi
connmanctl> services
KGNETGEARwifi_506583d635bb_4b474e455447454152_managed_psk
JandJwifi_506583d635bb_4a616e644a_managed_psk
J+J_guestwifi_506583d635bb_4a2b4a5f6775657374_managed_psk
connmanctl> agent on
Agent registered
connmanctl> connect wifi_506583d635bb_4b474e455447454152_managed_ps
Error /net/connman/service/wifi_506583d635bb_4b474e455447454152_managed_ps: 
Method "Connect" with signature "" on interface "net.connman.Service" doesn't 
exist

connmanctl> 
===
root@beaglebone:~# uname -r
4.4.39-ti-r79
root@beaglebone:~# lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:Debian GNU/Linux 8.6 (jessie)
Release:8.6
Codename:   jessie
===
root@beaglebone:~# ifconfig -a
SoftAp0   Link encap:Ethernet  HWaddr 50:65:83:d6:35:be  
  inet addr:192.168.8.1  Bcast:192.168.8.255  Mask:255.255.255.0
  inet6 addr: fe80::5265:83ff:fed6:35be/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:30 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:0 (0.0 B)  TX bytes:7156 (6.9 KiB)

loLink encap:Local Loopback  
  inet addr:127.0.0.1  Mask:255.0.0.0
  inet6 addr: ::1/128 Scope:Host
  UP LOOPBACK RUNNING  MTU:65536  Metric:1
  RX packets:320 errors:0 dropped:0 overruns:0 frame:0
  TX packets:320 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1 
  RX bytes:25120 (24.5 KiB)  TX bytes:25120 (24.5 KiB)

usb0  Link encap:Ethernet  HWaddr 50:65:83:d6:35:bd  
  inet addr:192.168.7.2  Bcast:192.168.7.3  Mask:255.255.255.252
  UP BROADCAST MULTICAST  MTU:1500  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

wlan0 Link encap:Ethernet  HWaddr 50:65:83:d6:35:bb  
  UP BROADCAST MULTICAST DYNAMIC  MTU:1500  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
=
root@beaglebone:~# connmanctl
Error getting VPN connections: The name net.connman.vpn was not 
providedconnmanctl> enable wifi
Error wifi: Already enabled
connmanctl> scan wifi
Scan completed for wifi
connmanctl> services
KGNETGEARwifi_506583d635bb_4b474e455447454152_managed_psk
JandJwifi_506583d635bb_4a616e644a_managed_psk
J+J_guestwifi_506583d635bb_4a2b4a5f6775657374_managed_psk
connmanctl> agent on
Agent registered
connmanctl> connect wifi_506583d635bb_4b474e455447454152_managed_psk
Agent RequestInput wifi_506583d635bb_4b474e455447454152_managed_psk
  Passphrase = [ Type=psk, Requirement=mandatory, Alternates

[beagleboard] Re: Error using connmanctl> enable wifi BBBW

[Kevin Gordon]

I carried out:
"I now have the BBBW booting from the new image 
(debian-8.6-lxqt-4gb-armhf-2017-01-04-4gb), configuring the 4DCAPE-70T 
display from its eeprom, with keyboard and mouse. 
#ifconfig -a // providing 192.168.8.1 (on the BBBW)
# coomanctl // Error getting VPN connections... (on the BBBW)
connmanctl> enable wifi // already enabled
connmanctl> scan wifi //Scan completed for wifi
connmanctl> services // found my wireless network: KGNETGEAR
connmanctl> agent on //Agent registered
connmanctl> connect wifi_506583d// Error 
/net/connman/serviceMethod "Connect" with signature "" on 
interface..doesn't exist

I also have a Debian pc wired to wireless router KGNETGEAR #ifconfig -a // 
192.168.1.4"

Have I misunderstood:
"Out of the new image, you can ssh into the wifi access point 
(BeagleBone-WXYZ) and use connmanctl to connect to a 2nd access point 
(while still connected to the BBBW thru wifi).."
Does this mean ssh out of the BBBW?
Regards,
Kevin.



On Friday, 6 January 2017 15:27:40 UTC+13, Kevin Gordon wrote:

> I have received a BBBW yesterday. I booted from a SD Card (which has image 
> bone-debian-8.6-lxqt-4gb-armhf-2016-11-06-4gb) previously used on a BBB rev 
> C. Everything functions the same on the BBBW as on the BBB except the 
> network (wired) (the only item listed in connman gui) is not functioning 
> (fair enough). When I run connmanctl> enable wifi BBBW I have error 
> message:"Method "SetProperty" with signature "sv" on interface 
> "net.connman.Technology" doesn't exist".
> Is there a solution for this please?
> Kevin.
>

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

[beagleboard] Re: Error using connmanctl> enable wifi BBBW

[Kevin Gordon]

I now have the BBBW booting from the new image, configuring the 4DCAPE-70T 
display from its eeprom, with keyboard and mouse. #ifconfig -a // providing 
192.168.8.1
# coomanctl // Error getting VPN connections...
connmanctl> enable wifi // already enabled
connmanctl> scan wifi //Scan completed for wifi
connmanctl> services // found my wireless network: KGNETGEAR
connmanctl> agent on //Agent registered
connmanctl> connect wifi_506583d// Error 
/net/connman/serviceMethod "Connect" with signature "" on 
interface..doesn't exist
I also have a Debian pc wired to wireless router KGNETGEAR #ifconfig -a // 
192.168.1.4
Please advise next step.
Many thanks,
Kevin.

On Friday, 6 January 2017 15:27:40 UTC+13, Kevin Gordon wrote:

> I have received a BBBW yesterday. I booted from a SD Card (which has image 
> bone-debian-8.6-lxqt-4gb-armhf-2016-11-06-4gb) previously used on a BBB rev 
> C. Everything functions the same on the BBBW as on the BBB except the 
> network (wired) (the only item listed in connman gui) is not functioning 
> (fair enough). When I run connmanctl> enable wifi BBBW I have error 
> message:"Method "SetProperty" with signature "sv" on interface 
> "net.connman.Technology" doesn't exist".
> Is there a solution for this please?
> Kevin.
>

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

Re: [beagleboard] Error using connmanctl> enable wifi BBBW

[Kevin Gordon]

Thank you Robert for your reply. I downloaded 
bone-debian-8.6-lxqt-4gb-armhf-2017-01-04-4gb.img.xz which I hope is the 
correct selection.

On Friday, 6 January 2017 15:32:40 UTC+13, RobertCNelson wrote:
>
> On Thu, Jan 5, 2017 at 8:27 PM, Kevin Gordon  > wrote: 
> > I have received a BBBW yesterday. I booted from a SD Card (which has 
> image 
> > bone-debian-8.6-lxqt-4gb-armhf-2016-11-06-4gb) previously used on a BBB 
> rev 
> > C. Everything functions the same on the BBBW as on the BBB except the 
> > network (wired) (the only item listed in connman gui) is not functioning 
> > (fair enough). When I run connmanctl> enable wifi BBBW I have error 
> > message:"Method "SetProperty" with signature "sv" on interface 
> > "net.connman.Technology" doesn't exist". 
> > Is there a solution for this please? 
>
> Just grab this build: 
>
> https://rcn-ee.net/rootfs/bb.org/testing/2017-01-04/lxqt-4gb/ 
>
> The initial "connman/tether" setup I setup for out of the box was 
> sub-optimal for the BBBW.. 
>
> (it assumes your making a wifi access point).. 
>
> flash the newest lxqt-4gb image from yesterday 
>
> Out of the new image, you can ssh into the wifi access point 
> (BeagleBone-WXYZ) and use connmanctl to connect to a 2nd access point 
> (while still connected to the BBBW thru wifi).. 
>
> Regards, 
>
> -- 
> Robert Nelson 
> https://rcn-ee.com/ 
>

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

[beagleboard] Error using connmanctl> enable wifi BBBW

[Kevin Gordon]

I have received a BBBW yesterday. I booted from a SD Card (which has image 
bone-debian-8.6-lxqt-4gb-armhf-2016-11-06-4gb) previously used on a BBB rev 
C. Everything functions the same on the BBBW as on the BBB except the 
network (wired) (the only item listed in connman gui) is not functioning 
(fair enough). When I run connmanctl> enable wifi BBBW I have error 
message:"Method "SetProperty" with signature "sv" on interface 
"net.connman.Technology" doesn't exist".
Is there a solution for this please?
Kevin.

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

[beagleboard] Compiling a kernel module for jessie on the Beaglebone itself

[Kevin Stokes]

Trying to compile a module of mine which compiles and works fine on my 
Ubuntu PC. It is basically just usb-skeleton.c but with the usb VendorID 
and ProductID changed.  Now I want to compile it on my BeagleBone.

 I'm running Linux beaglebone 4.1.30-ti-r69 #1 SMP Sun Aug 14 11:23:09 UTC 
2016 armv7l GNU/Linux

  I've downloaded the kernel source via
git clone https://github.com/RobertCNelson/linux-stable-rcn-ee

I've linked the source folder to  /lib/modules/4.1.30-ti-r69/build

The build of my module fails because there is no config.   I tried to use 
the .config from my /boot directory...

I copied /boot/config-4.1.30-ti-r69  to linux-stable-rcn-ee/.config

Not sure what to do now.  So I did

make oldconfig && make prepare

It asked me a thousand questions which I just hit enter to.  Then when it 
was generating .h files, it failed on timeconst.h:

/bin/sh: 1: bc: not found
Kbuild:67: recipe for target 'include/generated/timeconst.h' failed
recipe for target 'prepare0' failed

I'm not trying to rebuild the kernel.  I would just the module build system 
to know how to build my module so that I can use it on my BeagleBone.

Thanks for your time.

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

[beagleboard] Download kernel headers for 4.4.30-ti-r64

[Kevin Cox]

Hello

I am trying to download the kernel headers for my BBB that is offline, so I 
cannot use the apt-get utility.  After some searching, I found a post 
pointing me to
   http://rcn-ee.net/deb/jessie-armhf/ where I found a package that matches 
my system.  After transferring the package to my BBB I did a dpkg-deb -c on 
the file to see what was in it.  I did not see any header files (.h) 
 mainly kernel modules (.ko).  Not sure now I have the right package. Is 
there a right way to do this when your BBB is offline?

Kevin

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

[beagleboard] Re: EQEP pin conflict with MCASP

[Kevin Cox]

thank you, this solved the problem.

On Wednesday, December 28, 2016 at 10:40:34 AM UTC-5, Kevin Cox wrote:
>
> Hello
>
> I am trying to enable and use eqep0 on my BBB (kernel 4.4.30-ti-r64) and 
> am encountering a pin conflict (pin 107) between the eqep driver and mcasp 
> driver
>
> From dmesg output:
>
> [   41.150493] eqep 48300180.eqep: ver. 1.0
> [   41.150628] pinctrl-single 44e10800.pinmux: pin 44e109ac.0 already 
> requested by 48038000.mcasp; cannot claim for 48300180.eqep
> [   41.162226] pinctrl-single 44e10800.pinmux: pin-107 (48300180.eqep) 
> status -22
> [   41.169520] pinctrl-single 44e10800.pinmux: could not request pin 107 
> (44e109ac.0) from group pinctrl_eqep0_pins  on device pinctrl-single
> [   41.182036] eqep 48300180.eqep: Error applying setting, reverse things 
> back
>
>
> In /boot/uEnv.txt I enable bone_eqep0 and disable HDMI with/without audio:
>
> ##Example v4.1.x
> cape_disable=bone_capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN
> cape_enable=bone_capemgr.enable_partno=BB-UART1,bone_eqep0
>
> In /opt/bb.org-overlays/src/arm/bone_eqep0-00A0 shows the following pins 
> being used which none of them map to pin 107 on my BBB:
>
> pinctrl-single,pins = <
> BONE_P9_42B (PIN_INPUT | MUX_MODE1) // GPIO3_18 = EQEP0A_in
> BONE_P9_27  (PIN_INPUT | MUX_MODE1) // GPIO3_19 = EQEP0B_in
> BONE_P9_41B (PIN_INPUT | MUX_MODE1) // GPIO3_20 = EQEP0_index
> BONE_P9_25  (PIN_INPUT | MUX_MODE1) // GPIO3_21 = EQEP0_strobe
>
> I have found a thread here: 
> https://groups.google.com/forum/#!category-topic/beagleboard/audio/YNhtwbe_b4k
>  
> that shows how to disable mcasp0 but I am concerned that something is not 
> configured right as my understanding was that eqep0 should not conflict 
> with other hardware and especially a pin that should not overlap.  Am I 
> missing something obvious.  I thought I could just enable this driver out 
> of the box.
>
> Kevin 
>
>
>

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

[beagleboard] EQEP pin conflict with MCASP

[Kevin Cox]

Hello

I am trying to enable and use eqep0 on my BBB (kernel 4.4.30-ti-r64) and am 
encountering a pin conflict (pin 107) between the eqep driver and mcasp 
driver

>From dmesg output:

[   41.150493] eqep 48300180.eqep: ver. 1.0
[   41.150628] pinctrl-single 44e10800.pinmux: pin 44e109ac.0 already 
requested by 48038000.mcasp; cannot claim for 48300180.eqep
[   41.162226] pinctrl-single 44e10800.pinmux: pin-107 (48300180.eqep) 
status -22
[   41.169520] pinctrl-single 44e10800.pinmux: could not request pin 107 
(44e109ac.0) from group pinctrl_eqep0_pins  on device pinctrl-single
[   41.182036] eqep 48300180.eqep: Error applying setting, reverse things 
back


In /boot/uEnv.txt I enable bone_eqep0 and disable HDMI with/without audio:

##Example v4.1.x
cape_disable=bone_capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN
cape_enable=bone_capemgr.enable_partno=BB-UART1,bone_eqep0

In /opt/bb.org-overlays/src/arm/bone_eqep0-00A0 shows the following pins 
being used which none of them map to pin 107 on my BBB:

pinctrl-single,pins = <
BONE_P9_42B (PIN_INPUT | MUX_MODE1) // GPIO3_18 = EQEP0A_in
BONE_P9_27  (PIN_INPUT | MUX_MODE1) // GPIO3_19 = EQEP0B_in
BONE_P9_41B (PIN_INPUT | MUX_MODE1) // GPIO3_20 = EQEP0_index
BONE_P9_25  (PIN_INPUT | MUX_MODE1) // GPIO3_21 = EQEP0_strobe

I have found a thread here: 
https://groups.google.com/forum/#!category-topic/beagleboard/audio/YNhtwbe_b4k 
that shows how to disable mcasp0 but I am concerned that something is not 
configured right as my understanding was that eqep0 should not conflict 
with other hardware and especially a pin that should not overlap.  Am I 
missing something obvious.  I thought I could just enable this driver out 
of the box.

Kevin 


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

[beagleboard] Beaglebone Black (BBB) and Debugging with Eclipse

[Kevin Gordon]

Beaglebone Black (BBB) and Debugging with Eclipse 

http://www.rescuerobot.org/drupal/?q=content/beaglebone-black-bbb-and-debugging-eclipse

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

[beagleboard] Re: BBB with cape 7inch LCD faulty screen

[Kevin Gordon]

What is the best method to automatically ensure that the display backlight 
is on after boot? Initially the screen is white then switches to faint 
graphics (backlight off). Thank you! Kevin.

On Wednesday, 23 November 2016 02:33:47 UTC+13, Kevin Gordon wrote:
>
> I have built a new host from debian-8.6.0-amd64-CD-1.iso and included 
> eclipse mars.2 with debugging for 
> bone-debian-8.4-lxqt-4gb-armhf-2016-05-13-4gb.img.xz installed on a BBB 
> with a 7 inch LCD cape.
> At the beginning of uEnv.txt I included as a first line:
> dtb=am335x-boneblack-emmc-overlay.dtb
> For file capemgr:
> root@beaglebone:/etc/default# nano capemgr
>   GNU nano 2.2.6   File: capemgr
> # Default settings for capemgr. This file is sourced by /bin/sh from
> # /etc/init.d/capemgr.sh
> # Options to pass to capemgr
> CAPE=BB-BONE-LCD7-01:00A3
> I added the above last line: CAPE=BB-BONE-LCD7-01:00A3
> root@beaglebone:/# cat /sys/devices/platform/bone_capemgr/slots
>  0: PF  -1
>  1: PF  -1
>  2: PF  -1
>  3: PF  -1
>  4: P-O-L-   0 Override Board Name,00A3,Override Manuf,BB-BONE-LCD7-01
> Which I believe means the cape is loaded.
> The above is working satisfactorily except the display is very faint. I 
> can turn on the backlight with:
> Manually:
> root@beaglebone:~# echo 1 > /sys/class/backlight/backlight/bl_power
> Or:
> echo 1 | sudo tee /sys/class/backlight/backlight/bl_power
> Placed in .bashrc
> These turned the backlight on but seemed to cause some mouse and screen 
> instability. If I don't do this everything is stable but so faint that the 
> display is almost unreadable.
> This is a first attempt by me. Any comments or improvements would be much 
> appreciated.
> Many thanks,
> Kevin.
>

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

[beagleboard] BBB with cape 7inch LCD faulty screen

[Kevin Gordon]

I have built a new host from debian-8.6.0-amd64-CD-1.iso and included 
eclipse mars.2 with debugging for 
bone-debian-8.4-lxqt-4gb-armhf-2016-05-13-4gb.img.xz installed on a BBB 
with a 7 inch LCD cape.
At the beginning of uEnv.txt I included as a first line:
dtb=am335x-boneblack-emmc-overlay.dtb
For file capemgr:
root@beaglebone:/etc/default# nano capemgr
  GNU nano 2.2.6   File: capemgr
# Default settings for capemgr. This file is sourced by /bin/sh from
# /etc/init.d/capemgr.sh
# Options to pass to capemgr
CAPE=BB-BONE-LCD7-01:00A3
I added the above last line: CAPE=BB-BONE-LCD7-01:00A3
root@beaglebone:/# cat /sys/devices/platform/bone_capemgr/slots
 0: PF  -1
 1: PF  -1
 2: PF  -1
 3: PF  -1
 4: P-O-L-   0 Override Board Name,00A3,Override Manuf,BB-BONE-LCD7-01
Which I believe means the cape is loaded.
The above is working satisfactorily except the display is very faint. I can 
turn on the backlight with:
Manually:
root@beaglebone:~# echo 1 > /sys/class/backlight/backlight/bl_power
Or:
echo 1 | sudo tee /sys/class/backlight/backlight/bl_power
Placed in .bashrc
These turned the backlight on but seemed to cause some mouse and screen 
instability. If I don't do this everything is stable but so faint that the 
display is almost unreadable.
This is a first attempt by me. Any comments or improvements would be much 
appreciated.
Many thanks,
Kevin.

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

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

[Kevin Fructuoso]

Hi Robert,

I am running some power cycle testing on a rev C board with a debian image 
dated to April 23rd, 2014. I am also seeing this error occur across 
multiple boards. When this error occurs, the boards cannot acquire an IP 
address. Do you know if this image should have resolved the issue?

Phy 0 not found

[8.254476] libphy: PHY 4a101000.mdio:00 not found
[8.259608] net eth0: phy 4a101000.mdio:00 not found on slave 0

It is not preferred for us to update to a newer image if we can work around 
it. Is there a way we can modify the u-boot and u-boot SPL files to detect 
and address this issue?

Is there a way to tell if this error has occurred without checking the 
uboot log? Maybe like a missing device or improper value of a file?

On Tuesday, March 11, 2014 at 6:30:10 AM UTC-7, RobertCNelson wrote:
>
> On Tue, Mar 11, 2014 at 8:26 AM, Robert Kuhn > 
> wrote: 
> > 
> > 
> > Gerald: 
> >> 
> >> Correct. You can also solve the issue by using the correct SW as well. 
> The 
> >> issue is that the processors interferes with the default address 
> settings 
> >> when the PHY reads the pins. If the SW looks for the other addresses, 
> it 
> >> works fine. 
> >> 
> >> Also, removing these caps will also create issues where the board does 
> not 
> >> boot at all. Not exactly a good trade. 
> > 
> > 
> > I got my Ubuntu 12.04 from here:  
> http://www.armhf.com/index.php/download/ 
> > When I searched for "beaglebone+ubuntu" I got many results. So its hard 
> to 
> > find the "correct" software. 
> > 
> > So where can I find it? Do you have a link? 
>
> My "debian" image is now hosted here: 
>
> http://beagleboard.org/latest-images 
>
> For ubuntu you can find images from the same script that generates 
> that image ^ here: 
>
> http://elinux.org/BeagleBoardUbuntu 
>
> But honestly, due to ubuntu's current short eol cycles (9 months), 
> ubuntu isn't that great anymore for long run embedded applications. So 
> i've been losing interest in support ubuntu. 
>
> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/4266e6d4-6bb1-4ef3-8fbe-a8116182a6b3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

[Kevin Fructuoso]

Hi Robert,

I am running some power cycle testing on a rev C board with a debian image 
dated to April 23rd, 2014. I am also seeing this error occur across 
multiple boards. Do you know if this image should have resolved the issue?

It is not preferred for us to update to a newer image if we can work around 
it. Is there a way we can modify the u-boot and u-boot SPL files to detect 
and address this issue?

Is there a way to tell if this error has occurred without checking the 
uboot log? Maybe like a missing device or improper value of a file?

On Tuesday, March 11, 2014 at 6:30:10 AM UTC-7, RobertCNelson wrote:
>
> On Tue, Mar 11, 2014 at 8:26 AM, Robert Kuhn > 
> wrote: 
> > 
> > 
> > Gerald: 
> >> 
> >> Correct. You can also solve the issue by using the correct SW as well. 
> The 
> >> issue is that the processors interferes with the default address 
> settings 
> >> when the PHY reads the pins. If the SW looks for the other addresses, 
> it 
> >> works fine. 
> >> 
> >> Also, removing these caps will also create issues where the board does 
> not 
> >> boot at all. Not exactly a good trade. 
> > 
> > 
> > I got my Ubuntu 12.04 from here:  
> http://www.armhf.com/index.php/download/ 
> > When I searched for "beaglebone+ubuntu" I got many results. So its hard 
> to 
> > find the "correct" software. 
> > 
> > So where can I find it? Do you have a link? 
>
> My "debian" image is now hosted here: 
>
> http://beagleboard.org/latest-images 
>
> For ubuntu you can find images from the same script that generates 
> that image ^ here: 
>
> http://elinux.org/BeagleBoardUbuntu 
>
> But honestly, due to ubuntu's current short eol cycles (9 months), 
> ubuntu isn't that great anymore for long run embedded applications. So 
> i've been losing interest in support ubuntu. 
>
> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/22091aee-fec6-4eac-af20-ba62f809b317%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: enc28j60 Driver

[kevin . diraison]

Hello, 

I've tried your DT for the ENC28J60 device but I've got a problem with 
symbol:







"Could not find symbol 'cpu' "

Then the same problem :

"Could not find symbol 'spi1_cs'

Any advices to solve it?

Best 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/78721c65-11b4-419d-9e37-78d7839f29ba%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] connected to DHCP server but dhcping does not receive answer

[Kevin Fructuoso]

Hi everyone,


I’ve been working with the Beaglebone Black Rev C with Debian. I want to 
have a static IP address if there is no DHCP server available.


The DHCP client I am using is dhclient.


To do so, I installed and plan to use the dhcping command using the command 
“*apt-get install dhcping*”


When there is no DHCP server, I start an alias interface using the ifconfig 
command and the last known IP address: “*ifconfig eth0:0 *”


I’m using the dhcping command as follows to find out if any DHCP servers 
are on the network: “*sudo dhcping –c  -s 
255.255.255.255*”


After the DHCP server is turned off and the IP on eth0 expires, I set the 
alias interface with the above ifconfig command. I then turned the DHCP 
back on and tried to issue the dhcping command. I receive “no answer” 
(meaning no DHCP server) which is not what I expect after having turned on 
the DHCP server. However, if I enter the DHCP servers IP address after the 
–s argument (i.e. "*sudo dhcping –c  –s 192.168.12.1*"), I get 
an answer (meaning DHCP server available). Using “*dhcpdump –i eth0*”, 
issuing dhcping to 255.255.255.255 shows no activity whereas issuing 
dhcping to 192.168.12.1 shows the expected activity.


I found that this is directly related to the interface eth0 not having an 
IP address. With eth0 up, the dhcping command with 255.255.255.255 works as 
expected. Without any IP address on eth0, no answer is received, despite it 
being connected to the server. 


I presume it has to do with how the dhclient releases an IP address when a 
lease expires. I would like to make this robust enough to move from network 
to network with no issues. So if possible, I would like to issue the 
dhcping command to all available servers instead of just one specific one.


Does anyone know why this is the case? Is there any way I can work around 
this?


Thanks, 

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

[beagleboard] ZenHome home automation capes

[kevin . mahoney]

I am working on a line of home automation capes. Each cape will fulfill a 
specific role while also including a set of common sensors for monitoring 
the surrounding environment.  I'm looking for ideas and opinions on systems 
in the home that users would like to connect to the Internet of Things for 
controlling and monitoring. I currently have functional GarageCape and 
ThermoCape prototypes that include temperature and light sensors. They 
include the appropriate electronics to connect to the associated system for 
control and monitoring. I have also developed a compatible Yocto image. I 
am also in search of a small number of beta testers. Please email me if you 
are interested. 

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

Re: [beagleboard] Re: Beaglebone Black Kernel 4.1 PWM and OCP?

[Kevin Ault]

I think there are only three PWM units (ehrpwm0, ehrpwm1, and ehrpwm2), but
two of them have an A and a B.  I didn't dig too far, but I suspect there
are some constraints on how the A and B can be used, such as maybe they
have to both be at the same frequency, but they could have different duty
cycles.  The question about which pwmchipN to export is a good one, and I
think this is where the documentation is the weakest.  I think that when I
had all the PWMs enabled in the device tree, ehrpwm2B was pwmchip6.  I
think it just starts with a base of zero and increments for each enabled
pwm unit.  When I only had ehrpwm2A enabled, I saw only pwmchip0, so I knew
that was it.  An remember, you are not exporting the pin, but the PWM
itself, to user space.  I finally realized that's what 'export' means.  The
pinmux table handles the routing of the PWM output to the physical pin.
I'm pretty sure you are right about P8_13 and P8_19, but I don't recall the
other ehrpwm pins.  I found these tables (
http://www.embedded-things.com/bbb/beaglebone-black-pin-mux-spreadsheet/)
by googling "beaglebone black pin mux table".

On Thu, Oct 1, 2015 at 2:13 AM, Khanh Nguyen 
wrote:

> Hey Kevin,
>
> Thanks for the guide on enabling PWM on kernel 4.1. I'm a little confused
> with PWM now though,...Based on the values that you provide, are you saying
> that, there are only 3 PWM's on the Beagleboard? I thought there were more
> than that or maybe I was wrong.
>
> The 2nd question would be, is this right?
>
> 0x024  0x4corresponds to ehrpwm2B = P8_13
> 0x020  0x4  corresponds to ehrpwm2A = P8_19
> 0x150  0x3corresponds to ehrpwm0A = P9_14
> (Are we missing some pins)
>
> Also, how do you know it's pin 0 to export? I thought this were more like 
> exporting GPIO, whereas you'd need to know which pin is which to export?
>
> Thanks,
> Khanh
>
>
> --
> 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/dkS51WbicTo/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [beagleboard] Re: Beaglebone Black Kernel 4.1 PWM and OCP?

[Kevin Ault]

I am using the ehrpwm2A PWM on P8_19. Usage of this requires the following
device tree overlay (BB-PWM2-00A0.dts):


/dts-v1/;

/plugin/;


/{

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

part-number = "BB-PWM2";

version = "00A0";


fragment@0 {

target = <&am33xx_pinmux>;

__overlay__ {

pinctrl_spec: Panel_Pins {

pinctrl-single,pins = <

0x020 0x04 /* P8_19 MODE4 ehrpwm2A PWM */

>;

};

};

};


fragment@1 {

target = <&ocp>;

__overlay__ {

test_helper: helper {

compatible = "bone-pinmux-helper";

pinctrl-names = "default";

pinctrl-0 = <&pinctrl_spec>;

status = "okay";

};

};

};


fragment@2 {

target = <&epwmss2>;

__overlay__ {

status = "okay";

};

};


fragment@3 {

target = <&ehrpwm2>;

__overlay__ {

status = "okay";

};

};


};


In the above device tree overlay, fragment 0 configures P8_19 to be the
output of PWM2A (instead of a GPIO or other function), and fragments 1, 2,
and 3 enable the needed on-chip peripherals. 'ocp' is on-chip-peripherals,
'epwmss' is PWM sub-system, and 'ehrpwm2' is PWM2.


Compile this overlay using:


dtc -O dtb -o BB-PWM2-00A0.dtbo -b 0 -@ BB-PWM2-00A0.dts


Copy to /lib/firmware:


sudo cp BB-PWM2-00A0.dtbo /lib/firmware


At this point, get to root:


sudo su


Load the device tree overlay (this must be done logged in as root, sudo
won't work – I think because of the redirect).  Note that this path is
different than the earlier kernels due to a redesign of the cape manager:


root@arm:/home/ubuntu# echo BB-PWM >
/sys/devices/platform/bone_capemgr/slots


Check that overlay was loaded:


root@arm:/home/ubuntu# cat /sys/devices/platform/bone_capemgr/slots

 0: PF  -1
 1: PF  -1
 2: PF  -1
 3: PF  -1
 4: P-O-L-   0 Override Board Name,00A0,Override Manuf,BB-PWM2


Check that the pin is configured to output the PWM2A:


root@arm:/home/ubuntu# cat /sys/kernel/debug/pinctrl/44e10800.pinmux/pins |
grep 0820


pin 8 (44e10820.0) 0004 pinctrl-single


You need to see the pinmux at offset $820 have mode 4.  If it is not 4,
your PWM may be working fine, but you won't see the signal on pin P8_19.


You should also see pwmchip0 appear at /sys/class/pwm:


root@arm:/home/ubuntu# ls /sys/class/pwm

pwmchip0


Change to pwmchip0 folder:


root@arm:/home/ubuntu# cd /sys/class/pwm/pwmchip0


Export the PWM to userspace:


root@arm:/sys/class/pwm/pwmchip0# echo 0 > export


You should now see a pwm0 folder:


root@arm:/sys/class/pwm/pwmchip0# ls

device export npwm power pwm0 subsystem uevent unexport


Change to the pwm0 folder, configure the PWM and enable it:


root@arm:/sys/class/pwm/pwmchip0/pwm0# ls

duty_cycle enable period polarity power uevent

root@arm:/sys/class/pwm/pwmchip0/pwm0# echo 100 > period

root@arm:/sys/class/pwm/pwmchip0/pwm0# echo 25 > duty_cycle

root@arm:/sys/class/pwm/pwmchip0/pwm0# echo 1 > enable


I think the units of period and duty_cycle are both nanoseconds (not
confirmed with a scope).  duty_cycle is not a percentage, so these setting
are running the PWM at 1kHz, 25% duty cycle.


Hope this helps!





On Wed, Sep 30, 2015 at 9:53 AM, Kevin Ault  wrote:

> I have the PWM working perfectly on the 4.1 kernel, and I am planning to
> post the solution to this thread within a few days.
>
> On Wed, Sep 30, 2015 at 12:36 AM, Khanh Nguyen 
> wrote:
>
>> No, I haven't been able to get kernel 4.1 and PWM working. I haven't
>> looked at the link you included either. I'll definitely take a look over
>> the weekend. Hey, can you send me the link to this post on google group? I
>> can't seem to find my post...
>>
>> Thanks,
>> Khanh
>>
>> On Sun, Sep 27, 2015 at 4:08 PM,  wrote:
>>
>>>
>>> Khanh,
>>>
>>> Have you got the PWMs working yet?  This documentation (
>>> http://processors.wiki.ti.com/index.php/Linux_Core_PWM_User's_Guide)
>>> most closely matches what I am seeing under the 4.1 kernel, but I had to
>>> fall back on these same old overlays to even see the PWMs.  Seem to able to
>>> export, configure, and enable the PWM, but I'm just not seeing anything on
>>> the output pin.
>>>
>>> -Kevin
>>>
>>>
>>> On Wednesday, September 9, 2015 at 3:20:19 AM UTC-5, Khanh Nguyen wrote:
>>>>
>>>> Hey guys, I'm working on a project where as I was using the
>>>> ocp.X/bone_pwm_P9_11 and such in kernel 3.8. I just recently updated my
>>>> Beaglebone black to kernel 4.1 and couldn't get PWM to work...
>>>>
>>>> I was trying to use dtc, rebuild the device tree overlay. I pulled the
>>>> old am33xx_pwm from
&g

Re: [beagleboard] Re: Beaglebone Black Kernel 4.1 PWM and OCP?

[Kevin Ault]

I have the PWM working perfectly on the 4.1 kernel, and I am planning to
post the solution to this thread within a few days.

On Wed, Sep 30, 2015 at 12:36 AM, Khanh Nguyen 
wrote:

> No, I haven't been able to get kernel 4.1 and PWM working. I haven't
> looked at the link you included either. I'll definitely take a look over
> the weekend. Hey, can you send me the link to this post on google group? I
> can't seem to find my post...
>
> Thanks,
> Khanh
>
> On Sun, Sep 27, 2015 at 4:08 PM,  wrote:
>
>>
>> Khanh,
>>
>> Have you got the PWMs working yet?  This documentation (
>> http://processors.wiki.ti.com/index.php/Linux_Core_PWM_User's_Guide)
>> most closely matches what I am seeing under the 4.1 kernel, but I had to
>> fall back on these same old overlays to even see the PWMs.  Seem to able to
>> export, configure, and enable the PWM, but I'm just not seeing anything on
>> the output pin.
>>
>> -Kevin
>>
>>
>> On Wednesday, September 9, 2015 at 3:20:19 AM UTC-5, Khanh Nguyen wrote:
>>>
>>> Hey guys, I'm working on a project where as I was using the
>>> ocp.X/bone_pwm_P9_11 and such in kernel 3.8. I just recently updated my
>>> Beaglebone black to kernel 4.1 and couldn't get PWM to work...
>>>
>>> I was trying to use dtc, rebuild the device tree overlay. I pulled the
>>> old am33xx_pwm from
>>> https://github.com/beagleboard/devicetree-source/blob/master/arch/arm/boot/dts/am33xx_pwm-00A0.dts
>>> and some of these bad boys bone_pwm_PX_YZ from
>>> https://github.com/beagleboard/devicetree-source/blob/master/arch/arm/boot/dts/bone_pwm_P8_13-00A0.dts.
>>> I know that these are pretty old, but was just thinking maybe it would work
>>> with the new kernel?
>>>
>>> Then I was able to build these device tree overlays and load them into
>>> the /boot/uEnv.txt. However, when I went to /sys/devices/platform, I only
>>> saw ocp:pwm and it's nothing like the old kernel 3.8 where you'd have duty,
>>> period, and all that good stuff. Is this the right way to access PWM or I
>>> had to use the example in the Bacon device tree overlay? If so, is there a
>>> document on how to know which PWM pin to export?
>>>
>>> I've been playing with this new kernel for quite a while now and still
>>> haven't got any luck. Any advice or pointers will be greatly appreciated.
>>>
>>> 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/dkS51WbicTo/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> beagleboard+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/dkS51WbicTo/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [beagleboard] Beaglebone Black image cloning failure

[Kevin Fructuoso]

Hi Julien,

That is something we also came across previously and handled in the same 
way as well. That didn't solve our flashing problem.

The issue was the slightly smaller size of the eMMC. To fix our flashing 
problem, we took a older programmed board and re-sized the partition to 3 
GB. We flashed this image to a micro SD using the compression method on 
http://elinux.org/BeagleBone_Black_Extracting_eMMC_contents. Then we 
flashed a board with the new Kingston eMMC using the decompression method 
detailed the link. The beaglebones with new Kingston eMMCs are now able to 
be flashed with this new image. The initial delay is still required.

On Tuesday, September 15, 2015 at 2:49:30 PM UTC-7, julien wrote:
>
>
> Hi Kevin,
>
> We are cloning BBBs using dd, and we noticed a similar problem: even with 
> a small image, the flashing sometimes fails (blank console when booting 
> from eMMC)
> If we redo exactly the same flashing procedure on the same BBB, it usually 
> works.
> It looks like dd fails when it is started to early after BBB boot. Maybe 
> some I/O overflow if dd is used while the system is still booting and 
> reading a lot of stuff from the sdCard. 
> If we just wait for ~30seconds after the prompt, the flashing procedure 
> looks much more reliable.
>
>
>
>
> On Thursday, August 27, 2015 at 7:23:55 PM UTC+2, Kevin Fructuoso wrote:
>>
>> Thanks for the info. Even though it's slightly smaller, the images I 
>> tried to flash are ~2.1 GB. I would think the smaller size limit shouldn't 
>> make a difference, or is that not entirely correct?
>>
>> I am only familiar with cloning using the dd method used here: 
>> http://elinux.org/BeagleBone_Black_Extracting_eMMC_contents.
>>
>> Can rsync clone the disc image similar to the dd method? Could you please 
>> point me to some references/examples of proper use of rsync to clone a 
>> production beaglebone to another beaglebone using a micro SD card?
>>
>>
>> On Thursday, August 27, 2015 at 8:43:40 AM UTC-7, RobertCNelson wrote:
>>>
>>> On Thu, Aug 27, 2015 at 10:35 AM, Kevin Fructuoso 
>>>  wrote: 
>>> > Hi everyone, 
>>> > 
>>> > 
>>> > 
>>> > I have been working with the BeagleBone Black Rev C for work. It seems 
>>> that 
>>> > I am having an issue cloning an image to the eMMC of a new beaglebone. 
>>> I can 
>>> > successfully clone an image to a microSD card and flash some older 
>>> > beaglebone black Rev C boards without problem. This is similar to user 
>>> > Mgeorgia’s issue on this forum: 
>>> > http://elinux.org/Talk:BeagleBone_Black_Extracting_eMMC_contents 
>>> > 
>>> > 
>>> > 
>>> > When attempting to flash recently received beaglebone blacks, the 
>>> serial 
>>> > output is 100% identical compared to flashing an old beaglebone with 
>>> the 
>>> > same image. The output designates successful flashing. However, the 
>>> new 
>>> > boards do not boot up after a power cycle and never boot again. The 
>>> serial 
>>> > outputs a stream of “.” 
>>> > 
>>> > 
>>> > 
>>> > Using the same method, I can successfully flash the original stock 
>>> image 
>>> > onto the new beaglebones. I can flash images to older beaglebones as 
>>> well. 
>>> > There is only an issue when trying to clone an image from an older 
>>> > beaglebone over to a new beaglebone I recently received, although the 
>>> serial 
>>> > output does not indicate this. All beaglebones I am working with are 
>>> Rev C. 
>>> > 
>>> > 
>>> > 
>>> > I have been using the disk dump command, dd, as per the official eMMC 
>>> > extracting/flashing page: 
>>> > http://elinux.org/BeagleBone_Black_Extracting_eMMC_contents. I also 
>>> tried to 
>>> > flash without on the fly compression. The issue is still present. 
>>> > 
>>> > 
>>> > 
>>> > I want to point out that all of the boards with this issue seem to 
>>> have the 
>>> > wrong eMMC device. The last 15 I received have a Kingston eMMC part 
>>> number 
>>> > “EMMC04G-S100.” When I look at the BOM spreadsheet on the official 
>>> webpage 
>>> > (http://elinux.org/Beagleboard:BeagleBoneBlack), this eMMC is not 
>>> listed 
>>> > there. The only ones are: Kingston KE4CN2H5A and Micron MTFC4GLDEA 0M 
>>> WT. 
>>>
>>> Standard manufacturing procedure, one eMMC goes eol, a newer eMMC comes 
>>> out. 
>>>
>>> For "dd" based backup/recovery tools the newer eMMC is slightly 
>>> smaller.. 
>>>
>>> #Micron 3744MB (bbb): 3925868544 bytes 
>>> #Kingston 3688MB (bbb): 3867148288 bytes 
>>> #Kingston 3648MB (x15): 3825205248 bytes 
>>>
>>> Which is why the official 'flashers" use rsync.. 
>>>
>>> Regards, 
>>>
>>> -- 
>>> Robert Nelson 
>>> https://rcn-ee.com/ 
>>>
>>

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

Re: [beagleboard] Beaglebone Black image cloning failure

[Kevin Fructuoso]

Thanks for the info. Even though it's slightly smaller, the images I tried 
to flash are ~2.1 GB. I would think the smaller size limit shouldn't make a 
difference, or is that not entirely correct?

I am only familiar with cloning using the dd method used here: 
http://elinux.org/BeagleBone_Black_Extracting_eMMC_contents.

Can rsync clone the disc image similar to the dd method? Could you please 
point me to some references/examples of proper use of rsync to clone a 
production beaglebone to another beaglebone using a micro SD card?


On Thursday, August 27, 2015 at 8:43:40 AM UTC-7, RobertCNelson wrote:
>
> On Thu, Aug 27, 2015 at 10:35 AM, Kevin Fructuoso 
> > wrote: 
> > Hi everyone, 
> > 
> > 
> > 
> > I have been working with the BeagleBone Black Rev C for work. It seems 
> that 
> > I am having an issue cloning an image to the eMMC of a new beaglebone. I 
> can 
> > successfully clone an image to a microSD card and flash some older 
> > beaglebone black Rev C boards without problem. This is similar to user 
> > Mgeorgia’s issue on this forum: 
> > http://elinux.org/Talk:BeagleBone_Black_Extracting_eMMC_contents 
> > 
> > 
> > 
> > When attempting to flash recently received beaglebone blacks, the serial 
> > output is 100% identical compared to flashing an old beaglebone with the 
> > same image. The output designates successful flashing. However, the new 
> > boards do not boot up after a power cycle and never boot again. The 
> serial 
> > outputs a stream of “.” 
> > 
> > 
> > 
> > Using the same method, I can successfully flash the original stock image 
> > onto the new beaglebones. I can flash images to older beaglebones as 
> well. 
> > There is only an issue when trying to clone an image from an older 
> > beaglebone over to a new beaglebone I recently received, although the 
> serial 
> > output does not indicate this. All beaglebones I am working with are Rev 
> C. 
> > 
> > 
> > 
> > I have been using the disk dump command, dd, as per the official eMMC 
> > extracting/flashing page: 
> > http://elinux.org/BeagleBone_Black_Extracting_eMMC_contents. I also 
> tried to 
> > flash without on the fly compression. The issue is still present. 
> > 
> > 
> > 
> > I want to point out that all of the boards with this issue seem to have 
> the 
> > wrong eMMC device. The last 15 I received have a Kingston eMMC part 
> number 
> > “EMMC04G-S100.” When I look at the BOM spreadsheet on the official 
> webpage 
> > (http://elinux.org/Beagleboard:BeagleBoneBlack), this eMMC is not 
> listed 
> > there. The only ones are: Kingston KE4CN2H5A and Micron MTFC4GLDEA 0M 
> WT. 
>
> Standard manufacturing procedure, one eMMC goes eol, a newer eMMC comes 
> out. 
>
> For "dd" based backup/recovery tools the newer eMMC is slightly smaller.. 
>
> #Micron 3744MB (bbb): 3925868544 bytes 
> #Kingston 3688MB (bbb): 3867148288 bytes 
> #Kingston 3648MB (x15): 3825205248 bytes 
>
> Which is why the official 'flashers" use rsync.. 
>
> Regards, 
>
> -- 
> Robert Nelson 
> https://rcn-ee.com/ 
>

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

[beagleboard] Beaglebone Black image cloning failure

[Kevin Fructuoso]

Hi everyone,

 

I have been working with the BeagleBone Black Rev C for work. It seems that 
I am having an issue cloning an image to the eMMC of a new beaglebone. I 
can successfully clone an image to a microSD card and flash some older 
beaglebone black Rev C boards without problem. This is similar to user 
Mgeorgia’s issue on this forum: 
http://elinux.org/Talk:BeagleBone_Black_Extracting_eMMC_contents

 

When attempting to flash recently received beaglebone blacks, the serial 
output is 100% identical compared to flashing an old beaglebone with the 
same image. The output designates successful flashing. However, the new 
boards do not boot up after a power cycle and never boot again. The serial 
outputs a stream of “.”

 

Using the same method, I can successfully flash the original stock image 
onto the new beaglebones. I can flash images to older beaglebones as well. 
There is only an issue when trying to clone an image from an older 
beaglebone over to a new beaglebone I recently received, although the 
serial output does not indicate this. All beaglebones I am working with are 
Rev C.

 

I have been using the disk dump command, dd, as per the official eMMC 
extracting/flashing page: 
http://elinux.org/BeagleBone_Black_Extracting_eMMC_contents. I also tried 
to flash without on the fly compression. The issue is still present.

 

I want to point out that all of the boards with this issue seem to have the 
wrong eMMC device. The last 15 I received have a Kingston eMMC part number 
“EMMC04G-S100.” When I look at the BOM spreadsheet on the official webpage (
http://elinux.org/Beagleboard:BeagleBoneBlack), this eMMC is not listed 
there. The only ones are: Kingston KE4CN2H5A and Micron MTFC4GLDEA 0M WT.

 

Does this matter? Could this be causing an issue when flashing the eMMC? Is 
this actually an allowed alternative and the BOM on the page hasn’t been 
updated? I see that this different eMMC has a 5.0 class standard (as 
opposed to the 4.5 and 4.41 of the BOM specified Kingston and Micron chips, 
respectively). 

 

What can I do to get around this? Any help is 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/d/optout.

[beagleboard] BeagleboneBlack Save eMMC script problem - mmcblk1 not in /dev

[kevin]

Hello all,

I'm trying to use the beagleboneblack-save-emmc.zip 
<https://s3.amazonaws.com/beagle/beagleboneblack-save-emmc.zip> found here 
<http://elinux.org/BeagleBone_Black_Extracting_eMMC_contents> to make a 
custom img file from my eMMC contents (so I can flash it to another BBB or 
make a backup or whatever).

When I extract the zip onto the uSD card (FAT32 formatted with boot flag) 
and boot it on my BeagleBone Black, my BBB goes straight to holding LED0 to 
full (meaning it reached the end of the script). Additionally, it creates 
an image file, but the image file is only 20 bytes, and I don't think it's 
an accurate extraction of my eMMC ;)

I've modified autorun.sh to add the lines: 

mount > /mnt/mount.log
ls /dev > /mnt/lsdev.log

Looking at those files, I can see that mmcblk1 isn't in /dev, so logically 
the line that dd's mmcblk1 to the image isn't working right (It's also not 
supposed to be mmcblk0, because that appears to be my uSD card (see 
mount.log)).

This is kinda where my knowledge of Linux runs out. I don't understand how 
things show up in /dev, so I'm lost as to how to fix this .

I appreciate whatever help you can give. I'm at a dead end :)


CONTENTS OF mount.log:
rootfs on / type rootfs (rw)
devtmpfs on /dev type devtmpfs 
(rw,relatime,size=251564k,nr_inodes=62891,mode=755)
proc on /proc type proc (rw,relatime)
devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs (rw,relatime,mode=777)
tmpfs on /tmp type tmpfs (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/dev/mmcblk0p1 on /mnt type vfat 
(rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)


CONTENTS OF lsdev.log:
bus
console
cpu_dma_latency
full
i2c-0
i2c-1
input
kmem
kmsg
log
loop-control
loop0
loop1
loop2
loop3
loop4
loop5
loop6
loop7
mem
mmcblk0
mmcblk0p1
network_latency
network_throughput
null
psaux
ptmx
pts
ram0
ram1
ram10
ram11
ram12
ram13
ram14
ram15
ram2
ram3
ram4
ram5
ram6
ram7
ram8
ram9
random
rtc0
shm
snd
tty
tty0
tty1
tty10
tty11
tty12
tty13
tty14
tty15
tty16
tty17
tty18
tty19
tty2
tty20
tty21
tty22
tty23
tty24
tty25
tty26
tty27
tty28
tty29
tty3
tty30
tty31
tty32
tty33
tty34
tty35
tty36
tty37
tty38
tty39
tty4
tty40
tty41
tty42
tty43
tty44
tty45
tty46
tty47
tty48
tty49
tty5
tty50
tty51
tty52
tty53
tty54
tty55
tty56
tty57
tty58
tty59
tty6
tty60
tty61
tty62
tty63
tty7
tty8
tty9
ttyO0
ttyS0
ttyS1
ttyS2
ttyS3
ubi_ctrl
urandom
usbmon0
usbmon1
vcs
vcs1
vcsa
vcsa1
watchdog
watchdog0
zero


Thanks for any help,

Kevin Johnson
ke...@coolkev.com

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

[beagleboard] eMMC doesn't appear in /dev when using beagleboneblack-save-emmc.zip

[kevin]

Hello Everyone,

I'm having a problem with the beagleboneblack-save-emmc.zip 
<https://s3.amazonaws.com/beagle/beagleboneblack-save-emmc.zip> found on this 
elinux wiki page 
<http://elinux.org/BeagleBone_Black_Extracting_eMMC_contents>. I'm trying 
to extract the eMMC contents to an .img file for a backup.

When I extract the zip onto the uSD card (FAT32 formatted and boot-flag 
set) and boot it on my BeagleBone Black, my BBB goes straight to holding 
LED0 to full (meaning it reached the end of the autorun.sh script). 
Additionally, it creates an image file, but the image file is only 20 
bytes, and I don't think it's an accurate extraction of the eMMC ;)

I've modified autorun.sh to add the lines: 

mount > /mnt/mount.log
ls /dev > /mnt/lsdev.log

pastebin of mount.log: http://pastebin.com/1WZ7Tkea
pastebin of lsdev.log: http://pastebin.com/qkMCVpF1

Looking at those files, I can see that mmcblk1 isn't in /dev, so logically 
the line that dd's mmcblk1 to the image isn't working right. Additionally 
/mmcblk0p1 is mounted to /mnt, so I believe that's my uSD card.

This is kinda where my knowledge of Linux runs out. I don't understand why 
the eMMC isn't showing up in /dev.

I'd appreciate whatever help you can give. I'm at a dead end.


Kevin Johnson



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

[beagleboard] BeagleBone won't put HDD to sleep

[Kevin Osborn]

I am running the latest Ubuntu (2015-02-19) from Robert Nelson. I have a 
Seagate Expansion 4TB external HDD connected through an unpowered USB hub. 
Everything seems to work fine, except for the fact that the HDD never 
sleeps. This is for a backup, so I just want it to run when the backup 
process is running. Instead, it runs all the time.

Any idea how to get it to properly sleep?

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

Re: [beagleboard] Windows won't recognize BBB over USB

[Kevin Osborn]

Got it. I will try to get to see if I can get it connected over serial com
later tonight.

On Wed, Feb 18, 2015 at 4:17 PM, Robert Nelson 
wrote:

> On Wed, Feb 18, 2015 at 6:11 PM, Kevin Osborn 
> wrote:
> > Is that true for the flasher version? I am actually flashing from
> Windows.
> > The problem is that I can't even connect to the BBB.
>
> You can... over the serial com port it creates..
>
> There was a bug, so i opted to enable usb-serial over nothing..
>
> Regards,
>
> --
> Robert Nelson
> http://www.rcn-ee.com/
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/nPxVjXM-sfI/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [beagleboard] Windows won't recognize BBB over USB

[Kevin Osborn]

Is that true for the flasher version? I am actually flashing from Windows. 
The problem is that I can't even connect to the BBB.

-Kevin

On Wednesday, February 18, 2015 at 2:30:37 PM UTC-8, RobertCNelson wrote:
>
> On Wed, Feb 18, 2015 at 4:27 PM, Kevin Osborn  > wrote: 
> > I was running the 10-29-15 version of Ubuntu. So, I decided to update to 
> the 
> > 01-06-15 version of the flasher Ubuntu. I flashed the device, rebooted 
> it, 
> > and everything appeared to run fine. 
> > 
> > So, I then went to plug in the USB cable to my Windows 8 PC. I do not 
> see 
> > the BBB as a network device. I do however see it listed as device ELMO 
> GMAS 
> > (COM5). 
> > 
> > When I previously flashed the device, it definitely showed up as a 
> network 
> > device and I was able to SSH to it. So, I don't know what I did 
> differently 
> > in this case or if the new version of Ubuntu is even a factor at all. 
> > 
> > I am sort of stuck. 
> > 
> > I also tried to connect Putty to the BBB over serial, but I could not 
> get 
> > that working either. 
>
> You need to do two things to 01-06-15.. 
>
> cd /opt/scripts/ 
> git pull 
>
> & 
>
> sudo apt-get update ; sudo apt-get install linux-image-3.14.33-ti-r50 
>
> Regards, 
>
> -- 
> Robert Nelson 
> http://www.rcn-ee.com/ 
>

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

[beagleboard] Windows won't recognize BBB over USB

[Kevin Osborn]

I was running the 10-29-15 version of Ubuntu. So, I decided to update to 
the 01-06-15 version of the flasher Ubuntu. I flashed the device, rebooted 
it, and everything appeared to run fine.

So, I then went to plug in the USB cable to my Windows 8 PC. I do not see 
the BBB as a network device. I do however see it listed as device ELMO GMAS 
(COM5).

When I previously flashed the device, it definitely showed up as a network 
device and I was able to SSH to it. So, I don't know what I did differently 
in this case or if the new version of Ubuntu is even a factor at all.

I am sort of stuck.

I also tried to connect Putty to the BBB over serial, but I could not get 
that working either.

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

Re: [beagleboard] Unable to flash

[Kevin Groce]

For sure.  :)  I have both 3.3v and 5v logic ones.

On Sat, Jan 10, 2015 at 2:04 PM, evilwulfie  wrote:

>  remember 3.3v ftdi ONLY
>
>
> On 1/10/2015 12:39 PM, Kevin Groce wrote:
>
> Rev Sticker says A6A and is stuck on the header.  I will boot and check
> what distro/ver is installed and see if my FTDI adapter will work on the
> console port. Just have not had a moment rest from work.
>
>
>  KG
>
> On Sat, Jan 10, 2015 at 12:20 PM, William Hermans 
> wrote:
>
>>  First of all, you never mentioned what you have installed on the eMMC
>> currently. Secondly, you never mentioned which flasher image you're trying
>> to install, and from where. Also, do you have a serial debug cable ? Serial
>> debug output should be turned on if it is in fact one of Robert's images.
>> Which instructions did you try to follow ? What method did you attempt to
>> put the image on the sdcard ?
>>
>>  You left out a lot of important information . . . knowing the actual
>> revision number of your beaglebone black would be handy too. It should be
>> written on a white sticker stuck on the ethernet jack some where. For
>> instance, on ours it is stuck on the side. Just says "A5A"
>>
>> On Sat, Jan 10, 2015 at 7:59 AM, Kevin Groce  wrote:
>>
>>> So with that being said what would be the best way to flash this to use
>>> more recent bootloaders?
>>>
>>>  Kevin Groce
>>>
>>>  On Fri, Jan 9, 2015 at 10:25 PM, William Hermans 
>>> wrote:
>>>
>>>>  Ah, I suppose it could also be an available space issue, but the
>>>> reason why I mentioned the above first, was that we have two A5A's here,
>>>> and with recent Debian images, I've had to hold the button down until the
>>>> board starts to boot. Where in the past, this was never a problem. Of
>>>> course, I'm booting from sdcard too, but I have Angstrom with 3.8.8 kernel
>>>> on the board ( upgraded once ). SO that should tell you how old the image +
>>>> bootloader is on our boards . . .
>>>>
>>>> On Fri, Jan 9, 2015 at 9:15 PM, William Hermans 
>>>> wrote:
>>>>
>>>>>  Problem with the A6A i believe will be old bootloader versus new
>>>>> bootloader. e.g. Angstrom + old bootloader on the eMMC, newer bootloader +
>>>>> Debian on the sdcard flasher image.
>>>>>
>>>>>  With that said, you should wait for Robert to chime in before taking
>>>>> drastic steps. Such as believing your board is bad. It is not impossible,
>>>>> but I think it is very unlikely.
>>>>>
>>>>> On Fri, Jan 9, 2015 at 8:19 PM, evilwulfie 
>>>>> wrote:
>>>>>
>>>>>>  With a proper image it should flash.
>>>>>>
>>>>>> http://elinux.org/Beagleboard:Debian_On_BeagleBone_Black
>>>>>>
>>>>>>
>>>>>> http://elinux.org/Beagleboard:Ubuntu_On_BeagleBone_Black
>>>>>>
>>>>>>
>>>>>> On 1/9/2015 7:37 PM, Kevin Groce wrote:
>>>>>>
>>>>>> I am having such a hard time with flashing the BBB. I am guessing it
>>>>>> is an A6A revision based on the wiki. I am not a novice when it comes to
>>>>>> flashing but for some reason this bugger wont flash. I have followed the
>>>>>> instructions to a T and results are not forth coming. Do you think I 
>>>>>> could
>>>>>> have a bad board? When I I load the image to the card and press the user
>>>>>> boot button I do not get the LED response that is said to happen after
>>>>>> flash. I have used cheap 8gb SD card and a sandisk 16gb SD card and both
>>>>>> same outcome. Nothing. I need a board that works for a P-port cape 
>>>>>> project.
>>>>>>
>>>>>>
>>>>>>  KG
>>>>>>  --
>>>>>> For more options, visit http://beagleboard.org/discuss
>>>>>> ---
>>>>>> You received this message because you are subscribed to the Google
>>>>>> Groups "BeagleBoard" group.
>>>>>> To unsubscribe from this group and stop receiving emails from it,
>>>>>> send an email to beagleboard+unsubscr...@googlegroups.com.
>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>
>>>>>>
>>>>

Re: [beagleboard] Unable to flash

[Kevin Groce]

Rev Sticker says A6A and is stuck on the header.  I will boot and check
what distro/ver is installed and see if my FTDI adapter will work on the
console port. Just have not had a moment rest from work.


KG

On Sat, Jan 10, 2015 at 12:20 PM, William Hermans  wrote:

> First of all, you never mentioned what you have installed on the eMMC
> currently. Secondly, you never mentioned which flasher image you're trying
> to install, and from where. Also, do you have a serial debug cable ? Serial
> debug output should be turned on if it is in fact one of Robert's images.
> Which instructions did you try to follow ? What method did you attempt to
> put the image on the sdcard ?
>
> You left out a lot of important information . . . knowing the actual
> revision number of your beaglebone black would be handy too. It should be
> written on a white sticker stuck on the ethernet jack some where. For
> instance, on ours it is stuck on the side. Just says "A5A"
>
> On Sat, Jan 10, 2015 at 7:59 AM, Kevin Groce  wrote:
>
>> So with that being said what would be the best way to flash this to use
>> more recent bootloaders?
>>
>> Kevin Groce
>>
>> On Fri, Jan 9, 2015 at 10:25 PM, William Hermans 
>> wrote:
>>
>>> Ah, I suppose it could also be an available space issue, but the reason
>>> why I mentioned the above first, was that we have two A5A's here, and with
>>> recent Debian images, I've had to hold the button down until the board
>>> starts to boot. Where in the past, this was never a problem. Of course, I'm
>>> booting from sdcard too, but I have Angstrom with 3.8.8 kernel on the board
>>> ( upgraded once ). SO that should tell you how old the image + bootloader
>>> is on our boards . . .
>>>
>>> On Fri, Jan 9, 2015 at 9:15 PM, William Hermans 
>>> wrote:
>>>
>>>> Problem with the A6A i believe will be old bootloader versus new
>>>> bootloader. e.g. Angstrom + old bootloader on the eMMC, newer bootloader +
>>>> Debian on the sdcard flasher image.
>>>>
>>>> With that said, you should wait for Robert to chime in before taking
>>>> drastic steps. Such as believing your board is bad. It is not impossible,
>>>> but I think it is very unlikely.
>>>>
>>>> On Fri, Jan 9, 2015 at 8:19 PM, evilwulfie 
>>>> wrote:
>>>>
>>>>>  With a proper image it should flash.
>>>>>
>>>>> http://elinux.org/Beagleboard:Debian_On_BeagleBone_Black
>>>>>
>>>>>
>>>>> http://elinux.org/Beagleboard:Ubuntu_On_BeagleBone_Black
>>>>>
>>>>>
>>>>> On 1/9/2015 7:37 PM, Kevin Groce wrote:
>>>>>
>>>>> I am having such a hard time with flashing the BBB. I am guessing it
>>>>> is an A6A revision based on the wiki. I am not a novice when it comes to
>>>>> flashing but for some reason this bugger wont flash. I have followed the
>>>>> instructions to a T and results are not forth coming. Do you think I could
>>>>> have a bad board? When I I load the image to the card and press the user
>>>>> boot button I do not get the LED response that is said to happen after
>>>>> flash. I have used cheap 8gb SD card and a sandisk 16gb SD card and both
>>>>> same outcome. Nothing. I need a board that works for a P-port cape 
>>>>> project.
>>>>>
>>>>>
>>>>>  KG
>>>>>  --
>>>>> For more options, visit http://beagleboard.org/discuss
>>>>> ---
>>>>> You received this message because you are subscribed to the Google
>>>>> Groups "BeagleBoard" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>>> an email to beagleboard+unsubscr...@googlegroups.com.
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>
>>>>>
>>>>>  --
>>>>> For more options, visit http://beagleboard.org/discuss
>>>>> ---
>>>>> You received this message because you are subscribed to the Google
>>>>> Groups "BeagleBoard" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>>> an email to beagleboard+unsubscr...@googlegroups.com.
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>
>>>>
>>>>
>>>  --
>&

Re: [beagleboard] Unable to flash

[Kevin Groce]

So with that being said what would be the best way to flash this to use
more recent bootloaders?

Kevin Groce

On Fri, Jan 9, 2015 at 10:25 PM, William Hermans  wrote:

> Ah, I suppose it could also be an available space issue, but the reason
> why I mentioned the above first, was that we have two A5A's here, and with
> recent Debian images, I've had to hold the button down until the board
> starts to boot. Where in the past, this was never a problem. Of course, I'm
> booting from sdcard too, but I have Angstrom with 3.8.8 kernel on the board
> ( upgraded once ). SO that should tell you how old the image + bootloader
> is on our boards . . .
>
> On Fri, Jan 9, 2015 at 9:15 PM, William Hermans  wrote:
>
>> Problem with the A6A i believe will be old bootloader versus new
>> bootloader. e.g. Angstrom + old bootloader on the eMMC, newer bootloader +
>> Debian on the sdcard flasher image.
>>
>> With that said, you should wait for Robert to chime in before taking
>> drastic steps. Such as believing your board is bad. It is not impossible,
>> but I think it is very unlikely.
>>
>> On Fri, Jan 9, 2015 at 8:19 PM, evilwulfie  wrote:
>>
>>>  With a proper image it should flash.
>>>
>>> http://elinux.org/Beagleboard:Debian_On_BeagleBone_Black
>>>
>>>
>>> http://elinux.org/Beagleboard:Ubuntu_On_BeagleBone_Black
>>>
>>>
>>> On 1/9/2015 7:37 PM, Kevin Groce wrote:
>>>
>>> I am having such a hard time with flashing the BBB. I am guessing it is
>>> an A6A revision based on the wiki. I am not a novice when it comes to
>>> flashing but for some reason this bugger wont flash. I have followed the
>>> instructions to a T and results are not forth coming. Do you think I could
>>> have a bad board? When I I load the image to the card and press the user
>>> boot button I do not get the LED response that is said to happen after
>>> flash. I have used cheap 8gb SD card and a sandisk 16gb SD card and both
>>> same outcome. Nothing. I need a board that works for a P-port cape project.
>>>
>>>
>>>  KG
>>>  --
>>> For more options, visit http://beagleboard.org/discuss
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "BeagleBoard" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to beagleboard+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>>
>>>  --
>>> For more options, visit http://beagleboard.org/discuss
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "BeagleBoard" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to beagleboard+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>  --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/__xWXqUSDvk/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

[beagleboard] Unable to flash

[Kevin Groce]

I am having such a hard time with flashing the BBB. I am guessing it is an 
A6A revision based on the wiki. I am not a novice when it comes to flashing 
but for some reason this bugger wont flash. I have followed the 
instructions to a T and results are not forth coming. Do you think I could 
have a bad board? When I I load the image to the card and press the user 
boot button I do not get the LED response that is said to happen after 
flash. I have used cheap 8gb SD card and a sandisk 16gb SD card and both 
same outcome. Nothing. I need a board that works for a P-port cape project.


KG

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

[beagleboard] Re: Designing a Power Supply Section for the BeagleBoneBlack

[Kevin D'Souza]

And now I found 

http://www.linear.com/product/LTC3633A-2

Dual Channel 3A, 20V
Monolithic Synchronous
Step-Down Regulator.


Help Someone

On Wednesday, January 7, 2015 8:57:55 PM UTC+5:30, Kevin D'Souza wrote:
>
> Hello Guys, 
>
> I need to design a power supply solution for my application. 
>
> I have 1x BeagleBoneBlack 2x XBee's and a 5v700mA power consuming UART 
> Device. So its 3 devices in total 
>
> BeagleBone- 800mA
> 2x XBeePro 2.4GHz modules-400mA (Max?)
> UART Device600mA
> Total of :--1.8A.
>
> Plan of action first was to have 1x Switching Regulator of 2A and Give 
> power to the BeagleBone, UART Device and an LM1117 to feed the XBees (as 
> the XBees run on 3.3v and not 5v). So i was using 2x Regulators here, 1 
> Switching for the main power and a linear (lm1117) for the XBees, now i 
> came across the 3A/2A/2A output, Synchronous triple buck converter 
> tps652510 <http://www.ti.com/lit/ds/symlink/tps652510.pdf> . 
> 1. Is it wise to use this in my application.?
> 2. Does anyone have any experience with this regulator before? 
> 3. What can be the approximate footprint here? 
>
> Since its a cape i need it to be at-least in a 10cm x 10cm area with XBee 
> mounting space.
>
> There is also the TPS65253 
> <http://www.ti.com/product/tps65253/description> with similar 
> functionality but Dual output. 
>
> Now i am confused as to what to use. 
>
> Any help will be appreciated. 
>
> Regards,
>
> Kevin
>
>
>

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

[beagleboard] Designing a Power Supply Section for the BeagleBoneBlack

[Kevin D'Souza]

Hello Guys, 

I need to design a power supply solution for my application. 

I have 1x BeagleBoneBlack 2x XBee's and a 5v700mA power consuming UART 
Device. So its 3 devices in total 

BeagleBone- 800mA
2x XBeePro 2.4GHz modules-400mA (Max?)
UART Device600mA
Total of :--1.8A.

Plan of action first was to have 1x Switching Regulator of 2A and Give 
power to the BeagleBone, UART Device and an LM1117 to feed the XBees (as 
the XBees run on 3.3v and not 5v). So i was using 2x Regulators here, 1 
Switching for the main power and a linear (lm1117) for the XBees, now i 
came across the 3A/2A/2A output, Synchronous triple buck converter tps652510 
<http://www.ti.com/lit/ds/symlink/tps652510.pdf> . 
1. Is it wise to use this in my application.?
2. Does anyone have any experience with this regulator before? 
3. What can be the approximate footprint here? 

Since its a cape i need it to be at-least in a 10cm x 10cm area with XBee 
mounting space.

There is also the TPS65253 <http://www.ti.com/product/tps65253/description> 
with 
similar functionality but Dual output. 

Now i am confused as to what to use. 

Any help will be appreciated. 

Regards,

Kevin


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

[beagleboard] Relay Alternative for a Low powered module on/off

[Kevin D'Souza]

I have an application that needs a XBee and another module to be turned on 
and off digitally via a BealgeboneBlack.

The Setup is 2 XBee's and an application board is connected to the 
BealgeboneBlack's 
UART and a GPIO for the power state . When the System is Powered ON I need 
1 Xbee and the BealgeboneBlack to come on and do its routines. After the 
system gets a specific signal from the Xbee (wirelessly from a baseStation) 
the board has to turn on the other XBee and application board. And when the 
operation is over, the XBee and Board is to be powered back down. 

I dont want to put them in sleep or low power state, just power both those 
devices off.

Was thinking of using a relay. But i cannot find a 3.3v 1A SMD Equivalent 
system. I am looking for a SMD type of footprint to go on a very compact 
board.

What options do i have?

The XBee needs around 1A Power and the Application board 500mA.

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

Re: [beagleboard] Process Dies after 5 mins

[Kevin D'Souza]

ok so i updated rc.local inside /etc


added 

nohup /pathtomyprogram/program &

exit 0

works well. 

the & Plays an important role and also the /path has to be the custom path 
and not inside /etc i was trying that before. now i just moved it outside. 


THanks Guys!.

CHeers!

On Monday, December 15, 2014 1:22:28 AM UTC+5:30, Kevin D'Souza wrote:
>
> nohup ./myprocess
>
> i put this in a .sh and ran it via init.d 
>
> it doenst spawn the service. >.<
>
> On Monday, December 15, 2014 1:00:01 AM UTC+5:30, meino@gmx.de wrote:
>>
>> Hi, 
>>
>> then the process is missing a controling terminal. 
>> Try to start it with nohup from the script to verify that. 
>>
>>
>>
>>
>> Kevin D'Souza  [14-12-14 20:28]: 
>> > nono 
>> > the process just does UART work up and down (transferring data between 
>> > UARTS). 
>> > 
>> > If i keep the process open in a terminal it runs indefinitley. 
>> > if i run it under the init.d after 5mins it goes off. 
>> > 
>> > no blocking calls, no file io. 
>> > 
>> > is there a way to spawn the process via systemd and keep WATCHDOG=1 
>> > somehow... 
>> > 
>> > On Monday, December 15, 2014 12:12:20 AM UTC+5:30, meino@gmx.de 
>> wrote: 
>> > > 
>> > > Just a shot in the dark: 
>> > > 
>> > > Is it possible, that the process in question is writing a hidden 
>> > > temporary on a tmpfs-filesystem, which returns "no space left 
>> > > on device" after 5 mins of writing to it and the application 
>> > > does not handle that error very wel and dies. 
>> > > Due to the missing "close" the file vanishes and 
>> > > one can start the cycle again? 
>> > > 
>> > > ...?... 
>> > > 
>> > > HTH! 
>> > > Meino 
>> > > 
>> > > 
>> > > 
>> > > 
>> > > evilwulfie > [14-12-14 19:36]: 
>> > > > Restart it upon death with e cron job ? 
>> > > > 
>> > > > what program and why is it exiting ? 
>> > > > 
>> > > > 
>> > > > On 12/14/2014 9:38 AM, Kevin D'Souza wrote: 
>> > > > > Hello Guys 
>> > > > > 
>> > > > > I am using a BEaglebone BLack with Debian. 
>> > > > > 
>> > > > > I added a service to startup using update-rc.d myprogram 
>> defaults. 
>> > > > > 
>> > > > > the program starts at startup but it is killed automatically 
>> after 5 
>> > > mins. 
>> > > > > 
>> > > > > How can i keep it alive forever? I dont want it to die. 
>> > > > > 
>> > > > > Regards, 
>> > > > > 
>> > > > > Kevin 
>> > > > > -- 
>> > > > > For more options, visit http://beagleboard.org/discuss 
>> > > > > --- 
>> > > > > You received this message because you 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  
>> > > > > <mailto:beagleboard+unsubscr...@googlegroups.com >. 
>> > > > > For more options, visit https://groups.google.com/d/optout. 
>> > > > 
>> > > > -- 
>> > > > For more options, visit http://beagleboard.org/discuss 
>> > > > --- 
>> > > > You received this message because you are subscribed to the Google 
>> > > Groups "BeagleBoard" group. 
>> > > > To unsubscribe from this group and stop receiving emails from it, 
>> send 
>> > > an email to beagleboard...@googlegroups.com . 
>> > > > For more options, visit https://groups.google.com/d/optout. 
>> > > 
>> > 
>> > -- 
>> > For more options, visit http://beagleboard.org/discuss 
>> > --- 
>> > You received this message because you are subscribed to the Google 
>> Groups "BeagleBoard" group. 
>> > To unsubscribe from this group and stop receiving emails from it, send 
>> an email to beagleboard...@googlegroups.com. 
>> > For more options, visit https://groups.google.com/d/optout. 
>>
>>

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

Re: [beagleboard] Process Dies after 5 mins

[Kevin D'Souza]

nohup ./myprocess

i put this in a .sh and ran it via init.d 

it doenst spawn the service. >.<

On Monday, December 15, 2014 1:00:01 AM UTC+5:30, meino@gmx.de wrote:
>
> Hi, 
>
> then the process is missing a controling terminal. 
> Try to start it with nohup from the script to verify that. 
>
>
>
>
> Kevin D'Souza > [14-12-14 20:28]: 
> > nono 
> > the process just does UART work up and down (transferring data between 
> > UARTS). 
> > 
> > If i keep the process open in a terminal it runs indefinitley. 
> > if i run it under the init.d after 5mins it goes off. 
> > 
> > no blocking calls, no file io. 
> > 
> > is there a way to spawn the process via systemd and keep WATCHDOG=1 
> > somehow... 
> > 
> > On Monday, December 15, 2014 12:12:20 AM UTC+5:30, meino@gmx.de 
> wrote: 
> > > 
> > > Just a shot in the dark: 
> > > 
> > > Is it possible, that the process in question is writing a hidden 
> > > temporary on a tmpfs-filesystem, which returns "no space left 
> > > on device" after 5 mins of writing to it and the application 
> > > does not handle that error very wel and dies. 
> > > Due to the missing "close" the file vanishes and 
> > > one can start the cycle again? 
> > > 
> > > ...?... 
> > > 
> > > HTH! 
> > > Meino 
> > > 
> > > 
> > > 
> > > 
> > > evilwulfie > [14-12-14 19:36]: 
> > > > Restart it upon death with e cron job ? 
> > > > 
> > > > what program and why is it exiting ? 
> > > > 
> > > > 
> > > > On 12/14/2014 9:38 AM, Kevin D'Souza wrote: 
> > > > > Hello Guys 
> > > > > 
> > > > > I am using a BEaglebone BLack with Debian. 
> > > > > 
> > > > > I added a service to startup using update-rc.d myprogram defaults. 
> > > > > 
> > > > > the program starts at startup but it is killed automatically after 
> 5 
> > > mins. 
> > > > > 
> > > > > How can i keep it alive forever? I dont want it to die. 
> > > > > 
> > > > > Regards, 
> > > > > 
> > > > > Kevin 
> > > > > -- 
> > > > > For more options, visit http://beagleboard.org/discuss 
> > > > > --- 
> > > > > You received this message because you 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  
> > > > > <mailto:beagleboard+unsubscr...@googlegroups.com  
> >. 
> > > > > For more options, visit https://groups.google.com/d/optout. 
> > > > 
> > > > -- 
> > > > For more options, visit http://beagleboard.org/discuss 
> > > > --- 
> > > > You received this message because you are subscribed to the Google 
> > > Groups "BeagleBoard" group. 
> > > > To unsubscribe from this group and stop receiving emails from it, 
> send 
> > > an email to beagleboard...@googlegroups.com . 
> > > > For more options, visit https://groups.google.com/d/optout. 
> > > 
> > 
> > -- 
> > For more options, visit http://beagleboard.org/discuss 
> > --- 
> > You received this message because you are subscribed to the Google 
> Groups "BeagleBoard" group. 
> > To unsubscribe from this group and stop receiving emails from it, send 
> an email to beagleboard...@googlegroups.com . 
> > For more options, visit https://groups.google.com/d/optout. 
>
>

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

Re: [beagleboard] Process Dies after 5 mins

[Kevin D'Souza]

nono
the process just does UART work up and down (transferring data between 
UARTS).

If i keep the process open in a terminal it runs indefinitley.
if i run it under the init.d after 5mins it goes off. 

no blocking calls, no file io. 

is there a way to spawn the process via systemd and keep WATCHDOG=1 
somehow...

On Monday, December 15, 2014 12:12:20 AM UTC+5:30, meino@gmx.de wrote:
>
> Just a shot in the dark: 
>
> Is it possible, that the process in question is writing a hidden 
> temporary on a tmpfs-filesystem, which returns "no space left 
> on device" after 5 mins of writing to it and the application 
> does not handle that error very wel and dies. 
> Due to the missing "close" the file vanishes and 
> one can start the cycle again? 
>
> ...?... 
>
> HTH! 
> Meino 
>
>
>
>
> evilwulfie > [14-12-14 19:36]: 
> > Restart it upon death with e cron job ? 
> > 
> > what program and why is it exiting ? 
> > 
> > 
> > On 12/14/2014 9:38 AM, Kevin D'Souza wrote: 
> > > Hello Guys 
> > > 
> > > I am using a BEaglebone BLack with Debian. 
> > > 
> > > I added a service to startup using update-rc.d myprogram defaults. 
> > > 
> > > the program starts at startup but it is killed automatically after 5 
> mins. 
> > > 
> > > How can i keep it alive forever? I dont want it to die. 
> > > 
> > > Regards, 
> > > 
> > > Kevin 
> > > -- 
> > > For more options, visit http://beagleboard.org/discuss 
> > > --- 
> > > You received this message because you 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  
> > > <mailto:beagleboard+unsubscr...@googlegroups.com >. 
> > > For more options, visit https://groups.google.com/d/optout. 
> > 
> > -- 
> > For more options, visit http://beagleboard.org/discuss 
> > --- 
> > You received this message because you are subscribed to the Google 
> Groups "BeagleBoard" group. 
> > To unsubscribe from this group and stop receiving emails from it, send 
> an email to beagleboard...@googlegroups.com . 
> > For more options, visit https://groups.google.com/d/optout. 
>

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

[beagleboard] Process Dies after 5 mins

[Kevin D'Souza]

Hello Guys 

I am using a BEaglebone BLack with Debian.

I added a service to startup using update-rc.d myprogram defaults.

the program starts at startup but it is killed automatically after 5 mins.

How can i keep it alive forever? I dont want it to die.

Regards,

Kevin

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

[beagleboard] Driving Solid State Relays

[kevin]

We have built a building automation system that runs on the BBB, (it is a 
.NET/mono based solution).   One of the less elegant and more expensive 
parts of the solution is there are multiple layers of relays to support 
controlling high-energy devices like large motors. We use a device from 
controlanything.com via RS-232 which then in turn drives large 
electromagnetic motor contactors.  

What i think would be an amazing solution would be to have an array of 
solid state relays controlled almost directly by the I/O channels on the 
BBB, but i don't think the capacity for current on those channels is quite 
enough.  

Has anyone ran across a cape (or just an external board) that has SSR's and 
appropriate amplifiers to take a digital I/O signal, or alternatively, a 
simple amplifying cape using transistors from a high power source?






 

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

[beagleboard] Initialize system time on boot (wireless)

[kevin . osborn98]

I am a little confused on systemd setup here.

So, my BBB loses its time on bootup. I know that is expected because there 
is not hardware clock.

I also see that ntpdate is supposed to run once a day in cron.daily. 
However, I really want the system to get the correct time on bootup. I am 
running wireless (set to auto), so I need this to run after the wireless 
connection is made.

In syslog, I do see the date being set on bootup, but it is off by years. 
And in /lib/systemd, I see timedated and time-sync. They appear to be in 
systemd, but never loaded. I see other documentation that refers to 
ntpupdate.service, but that doesn't exist here.

So far, I tried installing and uninstalling "apt-get install ntp". I linked 
/etc/localtime to my timezone in /usr/share (America/Los_Angeles). I also 
set /etc/adjtime to LOCAL instead of UTC.

So far, I haven't had any luck.

Mostly, I am just unsure of where to even configure things. I am really 
unfamiliar with systemd. 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/d/optout.

[beagleboard] Update system time on boot (wireless)

[Kevin Osborn]

On bootup, my BBB comes up with an always wrong date/time. Since it has not 
battery, I understand this.

So, I want the BBB to query NTP to get the correct date on bootup. I am 
also running wireless, so it has to happen after the wireless connects. I 
am confused on how to accomplish this with the current Debian and systemd. 
Previous instructions say to just install ntp. But this doesn't appear to 
do anything. I do see timedated and time-sync, but I am unsure if those are 
what I want or how to configure them.

If I run ntpdate manually, it works fine. I also see that cron.daily is 
also set to run ntpdate. In the syslog, I also see two calls to set system 
time from two different IP addresses. Those times are off by years. If I 
run ntpdate against those IP addresses, it runs fine.

Other documentation talks about ntpdate.service or timedatectl (coming in 
Jessie?), but that doesn't exist here.

I also tried setting /etc/adjtime to LOCAL instead of UTC. I do actually 
want local time. I also linked /etc/localtime to 
/use/share/.../America/Los_Angeles.

Mostly I am just trying to figure out how to get started here. I am 
unfortunately rather unfamiliar with systemd. 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/d/optout.

Re: [beagleboard] Clean Debian image

[Kevin Pletinckx]

Thank you for the response. Before I bite the bullet, these images still
come with a user, or will it start with an installer?

---
Kevin Pletinckx

On Tue, Oct 28, 2014 at 7:45 PM, Robert Nelson 
wrote:

> On Tue, Oct 28, 2014 at 1:41 PM, Mustek  wrote:
> > Hello, I'm looking for a pre-built debian build which is pretty much a
> clean
> > install. All the images I can find already have nodejs, cloud9, etc.
> > installed. Since I basically just want to use this as a mini server, I
> don't
> > need all that.
> >
> > So, is there a clean version or do I have to uninstall everything I don't
> > need?
>
> Grab the "console":
>
> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2014-10-22
>
> Or use the "Netinstall":
>
> https://github.com/RobertCNelson/netinstall
>
> and install only what you want...
>
> Regards,
>
> --
> Robert Nelson
> http://www.rcn-ee.com/
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/3XMrI2w1Svc/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

[beagleboard] Multiple i2c Busses on BeagleBoneBlack (more than 2)

[Kevin D'Souza]

Hello Guys,

I have an Application that uses multiple i2c sensors. The beaglebone black 
just has 2x I2C busses. 

Problem, the i2c sensors cannot have a different address (all of them have 
a same address). I used a  multiplexer fed all the sensors the SCL from the 
i2c1 bus and mux'd the SDL lines. Everything works well but now the problem 
is the polling is a bit slow. 

A Hack came across my mind. So, instead of using the i2c bus how about 
Bitbanging the i2c.

Use a Clock Source (SCL from the hardware timer). And the SDL lines Use 
GPIOs. 

So for 8x I2C's I'd have
gpio_1 - scl
gpio_2 - sda1
gpio_3 - sda2
gpio_3 - sda3
.
gpio_n - sda_n

Does the approach make sense?

Is there any other way i can connect the 8 sensors in different channels 
without going through the slow mux?
I want to grab data from all the sensors in a threaded way (parallelly grab 
data) without chaining them.

I dont want to bitbang every i2c SDA and SCL, since the SCL singnal is 
going to be common to all of them i want to keep this as only One SCL and 
have multiple SDA's

Let me know your thoughts,

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

[beagleboard] BBB and virtual box

[kevin . jerome14]

Hi,

I want to connect my BBB to my Virtual machine, based on Linux debian 
wheezy. My host is Windows 8. But I have a problem to communicate with it. 
I have an USB Cable to power up my BBB and an another cable with 3 pins 
(GND, RX ,TX) to dialog with it with GTKterm. I see the peripheric USB but 
when i click on it, this message appears :
 "*USB device Prolific Technology Inc. USB-Serial Controller is busy with a 
previous request*"
What can i do to fix it?

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

[beagleboard] USB Wifi Dongle in USB Hub Causes BBB Board Crash (even though Hub is powered)

[Kevin Wegman]

Hello,

I have been trying to get a wifi dongle 
<http://www.amazon.com/gp/product/B00FA6HR78/ref=oh_aui_detailpage_o04_s00?ie=UTF8&psc=1>
 to 
connect to the internet, but have been having issues with my board powering 
off when the dongle turns on.

What I have tried: I've tried using two different powered USB hubs. The 
first 
<http://www.tigerdirect.com/applications/searchtools/item-details.asp?EdpNo=2157415&SRCCODE=WEBGOOPA&utm_source=google&utm_medium=paid_search&utm_campaign=paid_search_google_pla&scid=scplp624515&gclid=CjwKEAjw9qafBRCRiYrL4-fpuFkSJACvocQ1bNkUYXkXRdwX2UgSHF-7MaUwcdpIbVJFJOplfnQoIxoCwK_w_wcB&gclsrc=aw.ds>
 
has a 5V 2A power supply, and the second 
<http://www.amazon.com/gp/product/B005HARR2W/ref=oh_aui_detailpage_o02_s00?ie=UTF8&psc=1>
 has 
a 5V 4A supply. I have gotten the dongle to work under Angstrom 
distribution (for both hubs) by plugging in the hub with the dongle 
attached and powering on the board (after I had configured the wifi 
settings to work properly). The board would crash 2 or 3 times, but I would 
reset the board after each crash and eventually the dongle would turn on 
and connect to my wifi without issue. With the Debian distribution, the 
board will crash each bootup. To be more specific, the onboard LEDs stop 
flashing and LED 2 remains solid.

My question is this: why is the dongle overdrawing the Beagleone when I 
have it attached to a powered hub? Is there a better hub for this 
application?

Thanks for the help,

Kevin

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

[beagleboard] Unable to locate package ros-hydro

[Kevin Reinaldo]

hi, so yesterday i'm trying to install ROS Hydro in my BBBk. My BBBk is 
using Ubuntu 13.04 Raring.

I've follow the instruction 
from http://wiki.ros.org/hydro/Installation/Ubuntu but everytime i write 
this command: 
 
sudo apt-get install ros-hydro-desktop

it replies with Unable to locate package ros-hydro-desktop 

can anybody help??

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

[beagleboard] Re: chipsee beaglebone lcd/dvi expansion kernel support

[Kevin Nguyen]

I have the ubuntu image working, I'm just running it off of the SD card 
though. I haven't had time to work on moving it to the eMMC.

-Kevin

On Friday, March 21, 2014 3:04:36 PM UTC-4, Jaymes Berkly wrote:
>
> This works well, though it doesn't seem to work for the ubuntu image. 
>> Working on seeing if booting from eMMC is possible. The eMMC is disabled in 
>> the am335x-bbb-exp.dts. After adding the following code below to enable the 
>> eMMC worked but the LCD stopped working too.
>
>  
>
> bone_capemgr {
>
> compatible = "ti,bone-capemgr";
>
> status = "okay";
>
> eeprom = <0xc>;
>
>
>> baseboardmaps {
>
>
>> board@0 {
>
> board-name = "A335BONE";
>
> compatible-name = "ti,beaglebone";
>
> linux,phandle = <0x4b>;
>
> phandle = <0x4b>;
>
> };
>
>
>> board@1 {
>
> board-name = "A335BNLT";
>
> compatible-name = "ti,beaglebone-black";
>
> linux,phandle = <0x4c>;
>
> phandle = <0x4c>;
>
> };
>
> };
>
>
>> slots {
>
> slot@100 {
>
> ti,cape-override;
>
> priority = <0x1>;
>
> compatible = "ti,beaglebone-black";
>
> board-name = "Bone-LT-eMMC-2G";
>
> version = "00A0";
>
> manufacturer = "Texas Instruments";
>
> part-number = "BB-BONE-EMMC-2G";
>
> };
>
> };
>
>
>> capemaps {
>
>
>> cape@1 {
>
> part-number = "BB-BONE-EMMC-2G";
>
>
>> version@00A0 {
>
> version = "00A0";
>
> dtbo = "cape-bone-2g-emmc1.dtbo";
>
> };
>
> };
>
> };
>
> };
>
>
> On Tuesday, March 18, 2014 5:07:53 PM UTC-4, Kevin Nguyen wrote:
>>
>> This isn't the "right" way to do it but it will work.
>>
>> 1. Download the Debian Wheezy 7.2 img from and install it on an SD Card 
>> using the instructions on the site.
>> http://www.armhf.com/index.php/boards/beaglebone-black/
>>
>> 2. Download the pre-built Angstrom image from Chipsee
>> http://www.4shared.com/rar/8lKQ5nSBba/prebuilt-angstrom-bbb-exp-2014.html
>>
>> 3. Extract the pre-built Angstrom image somewhere.
>>
>> 4. Copy the 'boot' folder from the Angstrom image to the SD Card and 
>> replace any duplicate files.
>>
>> 5. Plug in the SD Card and boot up.
>>
>> Note: I haven't verified but if you follow these instructions I don't 
>> think you can flash to the eMMC unless you edit the uEnv.txt
>> On Sunday, March 16, 2014 8:50:33 AM UTC-4, Patrick Horvath wrote:
>>>
>>> Has anyone an image for the capacitive 7" LCD version with debian wheezy?
>>>
>>

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

[beagleboard] Re: chipsee beaglebone lcd/dvi expansion kernel support

[Kevin Nguyen]

This isn't the "right" way to do it but it will work.

1. Download the Debian Wheezy 7.2 img from and install it on an SD Card 
using the instructions on the site.
http://www.armhf.com/index.php/boards/beaglebone-black/

2. Download the pre-built Angstrom image from Chipsee
http://www.4shared.com/rar/8lKQ5nSBba/prebuilt-angstrom-bbb-exp-2014.html

3. Extract the pre-built Angstrom image somewhere.

4. Copy the 'boot' folder from the Angstrom image to the SD Card and 
replace any duplicate files.

5. Plug in the SD Card and boot up.

Note: I haven't verified but if you follow these instructions I don't think 
you can flash to the eMMC unless you edit the uEnv.txt
On Sunday, March 16, 2014 8:50:33 AM UTC-4, Patrick Horvath wrote:
>
> Has anyone an image for the capacitive 7" LCD version with debian wheezy?
>

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

[beagleboard] Writing image to SD Card using OS X Mavericks on a macbook pro

[Kevin McQuown]

I just received my new BBB and wanted to upgrade it to the latest Angstrom 
version.  I have followed the instructions to the letter.  When I insert 
the SD card into my mac using it's SD card reader (not a separate SD Card 
reader via the USB) I am able to write the OS to the card successfully.  Or 
at least it appears to be.  The output I receive is:

3724+0 records in

3724+0 records out

3904897024 bytes transferred in 2459.711570 secs (1587543 bytes/sec)


However when I put the card into the BBB and power it up, I get 3 solid 
blue led lights just above the usb connection and nothing else.   It 
doesn't boot.


Note, that I have also wrote the eMMC-flasher version to the card and then 
insert into the BBB, hold down the button just above the SDCard and power 
it up.  Again, nothing.  I have waited up to a minute with the button down 
and nothing happens.


I am suspecting that when I write the image onto the SDCard using Mavericks 
on my macbook pro that it may not be doing it in the proper format.


Does anyone have any experience with this that might shed some light on 
what I am doing wrong?


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] Failed flashing of debian

[Kevin Chapman]

Appreciate the help very much. I've managed to get past the problem by just 
letting it run it's course. The message eventually ended, and I was back at the 
command line. Currently in the process of trying to get ubuntu back on it. 
Again, many thanks 

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

Re: [beagleboard] Failed flashing of debian

[Kevin Chapman]

I've neglected a piece of information. I'm trying to install the full 
desktops. 

Now, as I said before, I've successfully managed to flash other distros, so 
I don't believe I've made any errors in the actual installation process, 
and I've followed tutorials, where needed

I'm kind of stuck right now, as I can't install/flash anything, as my bbb 
is still not allowing me to boot off the sd for whatever reason. my only 
guess as to why that is, is because theres a script or something running 
from my first attempt at this, and my bbb hasn't finished some piece of it? 

I dunno, thats why I'm here


On Thursday, November 7, 2013 8:33:16 PM UTC-5, Kevin Chapman wrote:
>
> Tried that, but still getting 
> "E: Read, still have 989 to read but none left" prompt when you'd expect 
> the downloading process to take place.
>
> I've followed circuitco's tutorial to the t, but I'm still having this 
> issue. 
>
> On Thursday, November 7, 2013 7:54:08 PM UTC-5, RobertCNelson wrote:
>>
>> On Thu, Nov 7, 2013 at 5:59 PM, Kevin Chapman  wrote: 
>> > I am brand new to Linux, so hopefully I can give enough info to get 
>> help with my problem. 
>> > 
>> > I recently received my bbb, and immediately got to flashing. I've had 
>> success getting Ubuntu (12.04,13.04), android, and reflashing angstrom. 
>> > 
>> > Today I tried to flash debian wheezy. All went normal until trying to 
>> install gnome desktop. I get a message in terminal that says "E:read  989 
>> read but none left" or something to that effect, and it appears to me that 
>> installation is not happening. 
>> > 
>> > Is this normal? All the other distros I flashed showed me they were 
>> making progress, ie;getting, setting up indications on screen. 
>> > 
>> > So, I tried flashing a different image, but my bbb thinks it's still in 
>> reboot phase of installation from after I repartitioned the microsd, before 
>> resize2fs command takes place. So, I can't flash something different, and I 
>> can't flash what I'd started with. What do I do? 
>> > 
>> > I'm sure I've left out pertinent information, so please, help me help 
>> you help me. Tell me what you need to know to help me. Thank you in advance 
>>
>> Reflash with: 
>> http://elinux.org/BeagleBoardDebian#eMMC:_BeagleBone_Black 
>>
>> Making sure to HOLD down the button next to the microSD card BEFORE 
>> you power the board.. 
>>
>> Recovery/reflash should take 6-7 minutes... 
>>
>> 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] Failed flashing of debian

[Kevin Chapman]

Tried that, but still getting 
"E: Read, still have 989 to read but none left" prompt when you'd expect 
the downloading process to take place.

I've followed circuitco's tutorial to the t, but I'm still having this 
issue. 

On Thursday, November 7, 2013 7:54:08 PM UTC-5, RobertCNelson wrote:
>
> On Thu, Nov 7, 2013 at 5:59 PM, Kevin Chapman 
> > 
> wrote: 
> > I am brand new to Linux, so hopefully I can give enough info to get help 
> with my problem. 
> > 
> > I recently received my bbb, and immediately got to flashing. I've had 
> success getting Ubuntu (12.04,13.04), android, and reflashing angstrom. 
> > 
> > Today I tried to flash debian wheezy. All went normal until trying to 
> install gnome desktop. I get a message in terminal that says "E:read  989 
> read but none left" or something to that effect, and it appears to me that 
> installation is not happening. 
> > 
> > Is this normal? All the other distros I flashed showed me they were 
> making progress, ie;getting, setting up indications on screen. 
> > 
> > So, I tried flashing a different image, but my bbb thinks it's still in 
> reboot phase of installation from after I repartitioned the microsd, before 
> resize2fs command takes place. So, I can't flash something different, and I 
> can't flash what I'd started with. What do I do? 
> > 
> > I'm sure I've left out pertinent information, so please, help me help 
> you help me. Tell me what you need to know to help me. Thank you in advance 
>
> Reflash with: 
> http://elinux.org/BeagleBoardDebian#eMMC:_BeagleBone_Black 
>
> Making sure to HOLD down the button next to the microSD card BEFORE 
> you power the board.. 
>
> Recovery/reflash should take 6-7 minutes... 
>
> Regards, 
>
> -- 
> Robert Nelson 
> http://www.rcn-ee.com/ 
>

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

[beagleboard] Failed flashing of debian

[Kevin Chapman]

I am brand new to Linux, so hopefully I can give enough info to get help with 
my problem. 

I recently received my bbb, and immediately got to flashing. I've had success 
getting Ubuntu (12.04,13.04), android, and reflashing angstrom. 

Today I tried to flash debian wheezy. All went normal until trying to install 
gnome desktop. I get a message in terminal that says "E:read  989 read but none 
left" or something to that effect, and it appears to me that installation is 
not happening. 

Is this normal? All the other distros I flashed showed me they were making 
progress, ie;getting, setting up indications on screen. 

So, I tried flashing a different image, but my bbb thinks it's still in reboot 
phase of installation from after I repartitioned the microsd, before resize2fs 
command takes place. So, I can't flash something different, and I can't flash 
what I'd started with. What do I do? 

I'm sure I've left out pertinent information, so please, help me help you help 
me. Tell me what you need to know to help me. Thank you 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.

[beagleboard] Re: Fast boot, no-GUI distro?

[Kevin D'Souza]

Hi!
i made an Angstrom Image, well without GUI, use the Boot files on the 
BeagleBone demo page and just extract this image to your card.
Its 2013.06 Branch Angstrom :) 

Do Tell me how it goes. here's the Link to my image
https://docs.google.com/file/d/0B1CJYc5pls37Q3Fia1ctbmtoNWM/edit?usp=sharing

Get the MLO and u-boot.img from 
http://downloads.angstrom-distribution.org/demo/beaglebone/





On Monday, October 7, 2013 1:04:13 PM UTC+5:30, Rick M wrote:
>
> Hi. I'm getting started with my BBB, having done previous projects with 
> RPi and smaller boards.
>
> I'm wondering if anyone's made an Angstrom distribution designed for fast 
> boot, and that doesn't bother with any of the desktop and other graphical 
> UI elements. I'm embedding this in a robot, don't really want those things, 
> and the faster it boots, the better.
>
> It'd be nice if there was someone making a distro like this on a regular 
> basis, keeping it up to date. It would be a lot faster to install.
>
> Anyway, I'm not much of a linux user per se, and don't really know what 
> can be dumped
>
> Any pointers to projects would be much 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.