[beagleboard] Failure when using rpmsg. pru_rproc_remove: removing rproc 4a338000.pru repeats every 15 seconds.

[Brian Kuschak]

Hello,

I’m seeing a strange problem with rpmsg on BBB after installing AM3358 
Debian 10.3 2020-04-06 4GB SD IoT.  

$ cat /proc/version
Linux version 4.19.94-ti-r42 (voodoo@x3-am57xx-beagle-x15-2gb) (gcc version 
8.3.0 (Debian 8.3.0-6)) #1buster SMP PREEMPT Tue Mar 31 19:38:29 UTC 2020

$ lsb_release -d
Description: Debian GNU/Linux 10 (buster)

Reproducible using this hello world rpmsg example: 
https://github.com/tickbw/Beaglebone-PRU-RPMsg-HelloWorld

After starting the PRUs:
sudo sh -c "echo start > /sys/class/remoteproc/remoteproc0/state"
sudo sh -c "echo start > /sys/class/remoteproc/remoteproc1/state"

Running the hello userspace app an arbitrary number of times is 
successful.  Everything seems fine.
$ ./hello 
Message received from PRU_0: hello world_0
Message received from PRU_1: hello world_1

15 seconds later, and repeating every 15 seconds thereafter, the kernel 
removes and adds the PRU (as remoteproc 3 and 4 this time). This repeats 
indefinitely.  Any further attempts to run hello results in a kernel oops.  
If the hello app is never run, this still happens.

[  360.884172] remoteproc remoteproc1: remote processor 4a338000.pru is now 
up

[  376.013704] pru-rproc 4a338000.pru: pru_rproc_remove: removing rproc 
4a338000.pru

[  376.030081] pru-rproc 4a334000.pru: pru_rproc_remove: removing rproc 
4a334000.pru

[  376.111078] remoteproc remoteproc3: 4a334000.pru is available

[  376.128645] pru-rproc 4a334000.pru: PRU rproc node pru@4a334000 probed 
successfully

[  376.146324] remoteproc remoteproc4: 4a338000.pru is available

[  376.165866] pru-rproc 4a338000.pru: PRU rproc node pru@4a338000 probed 
successfully

[  391.758087] pru-rproc 4a338000.pru: pru_rproc_remove: removing rproc 
4a338000.pru

[  391.772782] remoteproc remoteproc4: releasing 4a338000.pru

[  391.785913] pru-rproc 4a334000.pru: pru_rproc_remove: removing rproc 
4a334000.pru

[  391.807367] remoteproc remoteproc3: releasing 4a334000.pru

[  391.867104] remoteproc remoteproc3: 4a334000.pru is available

[  391.882393] pru-rproc 4a334000.pru: PRU rproc node pru@4a334000 probed 
successfully

[  391.903894] remoteproc remoteproc4: 4a338000.pru is available

[  391.919233] pru-rproc 4a338000.pru: PRU rproc node pru@4a338000 probed 
successfully

Maybe a red herring, but I understand 
virtio_rpmsg_bus:rpmsg_send_offchannel_raw() has a 15 second timeout if it 
cannot obtain a buffer.  This seems unlikely as the hello program runs 
fine, many times, until 15 seconds elapses.

If the PRU firmware never calls rpmsg_init() or other rpmsg functions, then 
it happily runs forever.

I never saw this problem on Debian 8.6 and kernel 4.4.36-ti-r72. Any ideas?

Output of /opt/scripts/tools.version.sh, lsmod, and full dmesg attached.

Brian

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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/abc2b263-7e3f-44aa-bc79-249598afff91%40googlegroups.com.


dmesg
Description: Binary data


lsmod
Description: Binary data
git:/opt/scripts/:[b39ec679648a6be8f25f48bd1c9784c1fc5a0c46]
eeprom:[A335BNLT00C03917BBBK2102]
model:[TI_AM335x_BeagleBone_Black]
dogtag:[BeagleBoard.org Debian Buster IoT Image 2020-04-06]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2019.04-2-g07d5700e21]:[location: dd MBR]
UBOOT: Booted Device-Tree:[am335x-boneblack-uboot.dts]
UBOOT: Loaded Overlay:[AM335X-PRU-RPROC-4-19-TI-00A0]
UBOOT: Loaded Overlay:[BB-BONE-eMMC1-01-00A0]
kernel:[4.19.94-ti-r42]
/boot/uEnv.txt Settings:
uboot_overlay_options:[enable_uboot_overlays=1]
uboot_overlay_options:[disable_uboot_overlay_video=1]
uboot_overlay_options:[disable_uboot_overlay_audio=1]
uboot_overlay_options:[disable_uboot_overlay_wireless=1]
uboot_overlay_options:[disable_uboot_overlay_adc=1]
uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-19-TI-00A0.dtbo]
pkg check: to individually upgrade run: [sudo apt install --only-upgrade ]
pkg:[bb-cape-overlays]:[4.14.20200430.0-0~buster+20200430]
pkg:[bb-wl18xx-firmware]:[1.20200420.1-0~buster+20200424]
pkg:[kmod]:[26-1]
WARNING:pkg:[librobotcontrol]:[NOT_INSTALLED]
pkg:[firmware-ti-connectivity]:[20190717-2rcnee1~buster+20200305]
groups:[debian : debian adm kmem dialout cdrom floppy audio dip video plugdev users systemd-journal bluetooth netdev i2c gpio pwm eqep remoteproc admin spi iio docker tisdk weston-launch xenomai cloud9ide]
cmdline:[console=ttyO0,115200n8 root=/dev/mmcblk1p1 ro rootfstype=ext4 rootwait]
dmesg | grep remote
[   27.011803] remoteproc remoteproc0: 4a334000.pru is available
[   27.263688] remoteproc remoteproc1: 4a338000.pru is available
[   29.746981] remoteproc remoteproc2: wkup_m3 is available
[   29.821887] remoteproc remoteproc

Re: [beagleboard] Re: Installing cross-platform for Debian Buster

[Brian Tremaine]

Note, I removed the CD-ROM entries from my sources.list and apt update now
completes without error:
   root@debian:/etc/apt# apt update
   Hit:1 http://deb.debian.org/debian buster-updates InRelease
   Hit:2 http://security.debian.org/debian-security buster/updates InRelease
   Reading package lists... Done
   Building dependency tree
   Reading state information... Done
   All packages are up to date.
   root@debian:/etc/apt#

I still can't find any cross-build-essential results from apt-cache search.



On Sun, Sep 15, 2019 at 2:31 PM Brian Tremaine  wrote:

> Hi Dennis,
> I edited my sources.list as attached, adding the [trusted=yes]. I think
> this was the key. Now when I run apt update I get a longer response and no
> warnings of untrusted repository.
>
> After that I was able to the following commands to install Guest Additions:
> apt-get update && apt-get upgrade
> apt-get install build-essential module-assistant
> m-a prepare
>  --> then Under Devices select Insert Guest Additions CD
> Image...
>  this evidently causes VB to download GuestAdditions iso image
> mount /media/cdrom
> sh /media/cdrom/VBoxLinuxAdditions.run
>
> The install then proceeded and took a couple minutes after it  downloaded
> a GuestAdditions iso image. It didn't use any Guest Additions file that I
> downloaded.
>
> I can now use Guest Addition features such as copy & paste and change
> window size.
>
> My apt update still shows errors (near bottom) and I can't install any
> crossbuild essential files. apt-cache search cross-build-essential still
> gives no response. I get an error:  "Please use apt-cdrom to make this
> CD-ROM recognized by APT. apt-get update cannot be used to add new CD-ROMs".
>
> Regards,
>
>
> On Sun, Sep 15, 2019 at 1:49 PM Dennis Lee Bieber 
> wrote:
>
>> On Sun, 15 Sep 2019 10:53:12 -0700, Brian Tremaine
>>  declaimed the
>> following:
>>
>> >Thanks Dennis, I'll give this a try today !!
>> >On the guest additions I downloaded a deb file but when I try to mnt in
>> the
>> >cdrom it errors with invalid file type. This project (VM & installing
>> >tools) is definitely a much bigger project than anticipated. ...
>> >
>>
>> You don't "mount" deb package files.
>>
>> You copy them to a location in the Debian OS, and use apt to
>> install
>> them...
>>
>> I think I'd downloaded them on the Windows side, then sftp to my
>> working directory -- I'd tried (again, from the shell command history
>> file)
>>
>>18  sudo apt-get install linux-headers-$(uname -r)
>>19  ls
>>20  sudo apt install ./virtualbox-guest-dkms_6.0.10-dfsg-5_all.deb
>>21  sudo apt install ./virtualbox-guest-utils_6.0.10-dfsg-5_amd64.deb
>>22  sudo apt install ./virtualbox-guest-x11_6.0.10-dfsg-5_amd64.deb
>>23  sudo apt install ./virtualbox-guest-utils_6.0.10-dfsg-5_amd64.deb
>>24  sudo wget -O -
>>
>> https://db.debian.org/fetchkey.cgi?fingerprint=FEDEC1CB337BCF509F43C2243914B532F4DFBE99
>> | apt-key add
>>25  sudo su
>>26  ls
>>27  sudo apt-get remove virtualbox-guest-utils
>>28  sudo apt install ./virtualbox-guest-utils_6.0.10-dfsg-5_amd64.deb
>> ./virtualbox-guest-x11_6.0.10-dfsg-5_amd64.deb
>>
>> but they didn't seem to work properly. Later after finding some version in
>> ISO format (VBoxGuestAdditions_6.0.12.iso -- Oh, and I seem to be running
>> VBox 6.0.12 also -- so fresh it wasn't on the Oracle download page, but
>> showed up as an option when running the .10 installer in some advanced
>> mode), mounting it, copying the contents to a directory on disk, and then
>> running the install script (I've NEVER managed to get the installer to run
>> from "CD" image). The copy was done using drag&drop, so not visible in the
>> command lines
>>
>>31  mkdir ga
>>32  cd ga
>>33  sudo ./autorun.sh
>>34  cd ..
>>35  ls
>>36  ls -al
>>37  sudo adduser wulfraed vboxsf
>>
>> I also had to shutdown the virtual machine and reboot it for some
>> changes to take place. The last command above was to make the shared
>> folder
>> work for my user account. The shutdown/reboot seemed needed to make both
>> the shared folder and clipboard sharing work (I did, for some time, also
>> have problems with mouse integration).
>>
>> wulfraed@debian:~$ ls -l Downloads/ ga/
>> Downloads/:
>> total 103972
>> -rw-r--r-- 1 wulfraed w

Re: [beagleboard] Re: Installing cross-platform for Debian Buster

[Brian Tremaine]

Hi Dennis,
I edited my sources.list as attached, adding the [trusted=yes]. I think
this was the key. Now when I run apt update I get a longer response and no
warnings of untrusted repository.

After that I was able to the following commands to install Guest Additions:
apt-get update && apt-get upgrade
apt-get install build-essential module-assistant
m-a prepare
 --> then Under Devices select Insert Guest Additions CD
Image...
 this evidently causes VB to download GuestAdditions iso image
mount /media/cdrom
sh /media/cdrom/VBoxLinuxAdditions.run

The install then proceeded and took a couple minutes after it  downloaded a
GuestAdditions iso image. It didn't use any Guest Additions file that I
downloaded.

I can now use Guest Addition features such as copy & paste and change
window size.

My apt update still shows errors (near bottom) and I can't install any
crossbuild essential files. apt-cache search cross-build-essential still
gives no response. I get an error:  "Please use apt-cdrom to make this
CD-ROM recognized by APT. apt-get update cannot be used to add new CD-ROMs".

Regards,


On Sun, Sep 15, 2019 at 1:49 PM Dennis Lee Bieber 
wrote:

> On Sun, 15 Sep 2019 10:53:12 -0700, Brian Tremaine
>  declaimed the
> following:
>
> >Thanks Dennis, I'll give this a try today !!
> >On the guest additions I downloaded a deb file but when I try to mnt in
> the
> >cdrom it errors with invalid file type. This project (VM & installing
> >tools) is definitely a much bigger project than anticipated. ...
> >
>
> You don't "mount" deb package files.
>
> You copy them to a location in the Debian OS, and use apt to
> install
> them...
>
> I think I'd downloaded them on the Windows side, then sftp to my
> working directory -- I'd tried (again, from the shell command history file)
>
>18  sudo apt-get install linux-headers-$(uname -r)
>19  ls
>20  sudo apt install ./virtualbox-guest-dkms_6.0.10-dfsg-5_all.deb
>21  sudo apt install ./virtualbox-guest-utils_6.0.10-dfsg-5_amd64.deb
>22  sudo apt install ./virtualbox-guest-x11_6.0.10-dfsg-5_amd64.deb
>23  sudo apt install ./virtualbox-guest-utils_6.0.10-dfsg-5_amd64.deb
>24  sudo wget -O -
>
> https://db.debian.org/fetchkey.cgi?fingerprint=FEDEC1CB337BCF509F43C2243914B532F4DFBE99
> | apt-key add
>25  sudo su
>26  ls
>27  sudo apt-get remove virtualbox-guest-utils
>28  sudo apt install ./virtualbox-guest-utils_6.0.10-dfsg-5_amd64.deb
> ./virtualbox-guest-x11_6.0.10-dfsg-5_amd64.deb
>
> but they didn't seem to work properly. Later after finding some version in
> ISO format (VBoxGuestAdditions_6.0.12.iso -- Oh, and I seem to be running
> VBox 6.0.12 also -- so fresh it wasn't on the Oracle download page, but
> showed up as an option when running the .10 installer in some advanced
> mode), mounting it, copying the contents to a directory on disk, and then
> running the install script (I've NEVER managed to get the installer to run
> from "CD" image). The copy was done using drag&drop, so not visible in the
> command lines
>
>31  mkdir ga
>32  cd ga
>33  sudo ./autorun.sh
>34  cd ..
>35  ls
>36  ls -al
>37  sudo adduser wulfraed vboxsf
>
> I also had to shutdown the virtual machine and reboot it for some
> changes to take place. The last command above was to make the shared folder
> work for my user account. The shutdown/reboot seemed needed to make both
> the shared folder and clipboard sharing work (I did, for some time, also
> have problems with mouse integration).
>
> wulfraed@debian:~$ ls -l Downloads/ ga/
> Downloads/:
> total 103972
> -rw-r--r-- 1 wulfraed wulfraed 55446104 Sep 11 12:22
> code_1.38.0-1567547996_amd64.deb
> -rw-r--r-- 1 wulfraed wulfraed 51016290 Sep 13 13:53
> eclipse-inst-linux64.tar.gz
>
> ga/:
> total 62800
> -r--r--r-- 1 wulfraed wulfraed  763 Jan 21  2019 AUTORUN.INF
> -r-xr-xr-x 1 wulfraed wulfraed 6384 Sep  3 05:50 autorun.sh
> drwxr-xr-x 2 wulfraed wulfraed 4096 Sep 11 11:33 cert
> drwxr-xr-x 2 wulfraed wulfraed 4096 Sep 11 11:33 NT3x
> drwxr-xr-x 2 wulfraed wulfraed 4096 Sep 11 11:33 OS2
> -r-xr-xr-x 1 wulfraed wulfraed 4821 Sep  3 05:50 runasroot.sh
> -r--r--r-- 1 wulfraed wulfraed  547 Sep  3 05:56 TRANS.TBL
> -r--r--r-- 1 wulfraed wulfraed  3732295 Sep  3 05:49
> VBoxDarwinAdditions.pkg
> -r--r--r-- 1 wulfraed wulfraed 3949 Sep  3 05:49
> VBoxDarwinAdditionsUninstall.tool
> -r-xr-xr-x 1 wulfraed wulfraed  8611252 Sep  3 05:50 VBoxLinuxAdditions.run
> -r--r--r-- 1 wulfraed wulfraed 16587264 Sep  3 05:51
> VBoxSolarisAdd

Re: [beagleboard] Re: Installing cross-platform for Debian Buster

[Brian Tremaine]

Thanks Dennis, I'll give this a try today !!
On the guest additions I downloaded a deb file but when I try to mnt in the
cdrom it errors with invalid file type. This project (VM & installing
tools) is definitely a much bigger project than anticipated. ...

On Sun, Sep 15, 2019 at 10:39 AM Dennis Lee Bieber 
wrote:

> On Sat, 14 Sep 2019 10:06:07 -0700 (PDT), Brian Tremaine
>  declaimed the
> following:
>
> >
> >
> >I now have Debian 10 (Buster) in a VirtualBox 6.0 VM on a Windows 10
> >laptop. I've been working through Derek Molloy's book on setting up the
> >cross-platform tools.
> >
>
> Which is something I just updated to earlier this week (took
> forever to
> get the Virtual Box Guest Additions to build/work).
>
> >
> >In chapter 7 (page 309) when I give command apt-cache search
> >cross-build-essential there is no response, just prompt
> >
> >root@debian:~#
> >
> >
> >When I issue command sudo apt install crossbuild-essential-armhf I get:
> >reading package list … done
> >building dependency tree
> >reading state information … done
> >E: unable to locate package crossbuild-essential-armhf
> >
> From my command history
>
>77  sudo apt-cache search cross-build-essential
>78  sudo apt-get install crossbuild-essential-armhf
>
> wulfraed@debian:~$ !77
> sudo apt-cache search cross-build-essential
> [sudo] password for wulfraed:
> crossbuild-essential-amd64 - Informational list of cross-build-essential
> packages
> crossbuild-essential-arm64 - Informational list of cross-build-essential
> packages
> crossbuild-essential-armel - Informational list of cross-build-essential
> packages
> crossbuild-essential-armhf - Informational list of cross-build-essential
> packages
> crossbuild-essential-i386 - Informational list of cross-build-essential
> packages
> crossbuild-essential-mips - Informational list of cross-build-essential
> packages
> crossbuild-essential-mips64el - Informational list of cross-build-essential
> packages
> crossbuild-essential-mipsel - Informational list of cross-build-essential
> packages
> crossbuild-essential-powerpc - Informational list of cross-build-essential
> packages
> crossbuild-essential-ppc64el - Informational list of cross-build-essential
> packages
> crossbuild-essential-s390x - Informational list of cross-build-essential
> packages
> wulfraed@debian:~$
>
>
> >
> >Side note, I installed Debian using 3 iso DVD images. When I upgrade
> >packages I get prompted to mount a DVD. I have mounted each of the 3
> DVD's
> >and tried the above install with the same result on each.
> >
>
> I used the GUI "Expert" mode installation -- when asked for
> repository
> options I included them. (I also disable root login!) I also told it to
> scan each of the DVD images while it was setting up the apt repositories.
>
> >
> >Any suggestions how to proceed? I am stuck.
> >
>
> Check your repository sources list to ensure you have more than
> just
> the DVDs in it (mine follows), and then do an apt-get update before
> searching for things.
>
> -=-=-=-
> wulfraed@debian:~$ cat /etc/apt/sources.list
> #
>
> deb [trusted=yes] cdrom:[Debian GNU/Linux 10.0.0 _Buster_ - Official amd64
> DVD Binary-3 20190706-10:24]/ buster contrib main
> deb [trusted=yes] cdrom:[Debian GNU/Linux 10.0.0 _Buster_ - Official amd64
> DVD Binary-2 20190706-10:24]/ buster contrib main
> deb [trusted=yes] cdrom:[Debian GNU/Linux 10.0.0 _Buster_ - Official amd64
> DVD Binary-1 20190706-10:24]/ buster contrib main
>
> deb http://deb.debian.org/debian/ buster main non-free contrib
> deb-src http://deb.debian.org/debian/ buster main non-free contrib
>
> deb http://security.debian.org/debian-security buster/updates main contrib
> non-free
> deb-src http://security.debian.org/debian-security buster/updates main
> contrib non-free
>
> # buster-updates, previously known as 'volatile'
> deb http://deb.debian.org/debian/ buster-updates main contrib non-free
> deb-src http://deb.debian.org/debian/ buster-updates main contrib non-free
>
> # buster-backports, previously on backports.debian.org
> deb http://deb.debian.org/debian/ buster-backports main contrib non-free
> deb-src http://deb.debian.org/debian/ buster-backports main contrib
> non-free
> -=-=-=-
>
> (Actually -- I've just now commented out the DVD entries; after all, the
> index files won't be updating so I don't need the "failed to download"
> messages from apt-get update for them)
>
> Installing Eclipse was the big pain. You'd think the

[beagleboard] Installing cross-platform for Debian Buster

[Brian Tremaine]

I now have Debian 10 (Buster) in a VirtualBox 6.0 VM on a Windows 10 
laptop. I've been working through Derek Molloy's book on setting up the 
cross-platform tools.


In chapter 7 (page 309) when I give command apt-cache search 
cross-build-essential there is no response, just prompt 

root@debian:~#


When I issue command sudo apt install crossbuild-essential-armhf I get:
reading package list … done
building dependency tree
reading state information … done
E: unable to locate package crossbuild-essential-armhf


Side note, I installed Debian using 3 iso DVD images. When I upgrade 
packages I get prompted to mount a DVD. I have mounted each of the 3 DVD's 
and tried the above install with the same result on each.


Any suggestions how to proceed? I am stuck.   


~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/7ca6265b-820f-4bdc-b2da-0e0cafc75bc0%40googlegroups.com.

Re: [beagleboard] Setting up Debian VM for BBB

[Brian Tremaine]

I'll admit I'm a newbie at this. I'm following Derek Molloy's book and
videos, specifically chapter 7 in his book,
http://exploringbeaglebone.com/chapter7/
He uses a windows host and VirtualBox running debian to set up a tool chain
using Eclipse CDT and QEMU to write & debug code for the Beaglebone,
including remote debug on the BB. The BB is running an arm hard float
debian. I'll post a progress report when I get it working,

Brian

On Sun, Sep 8, 2019 at 7:45 PM Robert Heller  wrote:

> At Sun, 8 Sep 2019 15:54:36 -0700 (PDT) beagleboard@googlegroups.com
> wrote:
>
> >
> >
> >
> > Thank you! My immediate problem was I was using the armhf iso on the VM.
> I
> > changed this to the debian i386 iso and it booted. I'm ready to install.
> I
> > guess my next lurking issue will be QEMM. I'm using Derek Molloy's book
> and
> > video as a guideline in this adventure,
>
> The i386 processor type matches what the x86_64 processors can run as
> virtual
> machines.  Note: the i386 iso is not a BBB iso and cannot run beagleboard
> programs.
>
> >
> > Thanks,
> > Brian
> >
> > On Sunday, September 8, 2019 at 2:02:30 PM UTC-7, shabaz wrote:
> > >
> > > Hi Brian,
> > >
> > > It could be I don't understand something fundamental, or something
> very
> > > strange is being attempted.
> > >
> > > A Windows 10 PC, if it has an x86 or x64 processor, cannot use
> VirtualBox
> > > in this manner, to run a Linux image intended for a BBB. The BBB
> doesn't
> > > have an x86 or x64 processor, and VirtualBox isn't intended for
> emulating
> > > ARM processors (unless things have changed significantly.. I have not
> tried
> > > VirtualBox for years).
> > >
> > > --
> > > *From:* beagl...@googlegroups.com  <
> beagl...@googlegroups.com
> > > > on behalf of Brian Tremaine  > > >
> > > *Sent:* 08 September 2019 17:57
> > > *To:* BeagleBoard >
> > > *Subject:* [beagleboard] Setting up Debian VM for BBB
> > >
> > > Hi All,
> > > I realize my question is VirtualBox related but I'm stuck trying to
> set up
> > > Debian 'Buster' as my VM for my BBB.
> > > I've gone through several blogs on the setup but it still won't boot
> > > Debian.
> > >
> > > My iso image is: debian-10.0.0-armhf-netinst.iso
> > > When I start the VM it drops me into a UEFI shell. If I then go to
> FS0:
> > > and do a directory I can 'see' the Debian files.
> > >
> > > [image: Capture1.PNG]
> > >
> > >
> > >
> > > [image: Capture2.PNG]
> > >
> > > I have no idea what the UEFI shell is or why I'm there  Can you
> help
> > > me boot Debian? Here is a screenshot of my VM setup:
> > >
> > > [image: Capture3.PNG]
> > >
> > > Thanks in advance 
> > >
> > >
> > >
> > >
> > > --
> > > For more options, visit http://beagleboard.org/discuss
> > > ---
> > > You received this message because you are subscribed to the Google
> Groups
> > > "BeagleBoard" group.
> > > To unsubscribe from this group and stop receiving emails from it, send
> an
> > > email to beagl...@googlegroups.com .
> > > To view this discussion on the web visit
> > >
> https://groups.google.com/d/msgid/beagleboard/9c5d802a-6ee7-4c52-baf7-9d4528aabaa0%40googlegroups.com
> > > <
> https://groups.google.com/d/msgid/beagleboard/9c5d802a-6ee7-4c52-baf7-9d4528aabaa0%40googlegroups.com?utm_medium=email&utm_source=footer
> >
> > > .
> > >
> >
>
> --
> Robert Heller -- 978-544-6933
> Deepwoods Software-- Custom Software Services
> http://www.deepsoft.com/  -- Linux Administration Services
> hel...@deepsoft.com   -- Webhosting Services
>
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to 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/20190909024506.9A8D826C07E4%40sharky3.deepsoft.com
> .
>


-- 
*TremaineConsultingGroup.com*
LinkedIn <https://linkedin.com/in/btremaine/>

669-273-6035

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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/CANqZkw_LJgk5_1cupqCNOihKyQFTf5Wn%3DDHsy%3DrfVJxe32OxEg%40mail.gmail.com.

Re: [beagleboard] Setting up Debian VM for BBB

[Brian Tremaine]

Thank you! My immediate problem was I was using the armhf iso on the VM. I 
changed this to the debian i386 iso and it booted. I'm ready to install. I 
guess my next lurking issue will be QEMM. I'm using Derek Molloy's book and 
video as a guideline in this adventure,

Thanks,
Brian

On Sunday, September 8, 2019 at 2:02:30 PM UTC-7, shabaz wrote:
>
> Hi Brian,
>
> It could be I don't understand something fundamental, or something very 
> strange is being attempted.
>
> A Windows 10 PC, if it has an x86 or x64 processor, cannot use VirtualBox 
> in this manner, to run a Linux image intended for a BBB. The BBB doesn't 
> have an x86 or x64 processor, and VirtualBox isn't intended for emulating 
> ARM processors (unless things have changed significantly.. I have not tried 
> VirtualBox for years).
>
> ------
> *From:* beagl...@googlegroups.com   > on behalf of Brian Tremaine  >
> *Sent:* 08 September 2019 17:57
> *To:* BeagleBoard >
> *Subject:* [beagleboard] Setting up Debian VM for BBB 
>  
> Hi All, 
> I realize my question is VirtualBox related but I'm stuck trying to set up 
> Debian 'Buster' as my VM for my BBB.
> I've gone through several blogs on the setup but it still won't boot 
> Debian.
>
> My iso image is: debian-10.0.0-armhf-netinst.iso
> When I start the VM it drops me into a UEFI shell. If I then go to FS0: 
> and do a directory I can 'see' the Debian files.
>
> [image: Capture1.PNG]
>
>
>
> [image: Capture2.PNG]
>
> I have no idea what the UEFI shell is or why I'm there  Can you help 
> me boot Debian? Here is a screenshot of my VM setup:
>
> [image: Capture3.PNG]
>
> Thanks in advance 
>
>
>  
>
> -- 
> For more options, visit http://beagleboard.org/discuss
> --- 
> You received this message because you are subscribed to the Google Groups 
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to beagl...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/beagleboard/9c5d802a-6ee7-4c52-baf7-9d4528aabaa0%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/beagleboard/9c5d802a-6ee7-4c52-baf7-9d4528aabaa0%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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/54995406-1095-41d2-9ff1-57e432930cd1%40googlegroups.com.

[beagleboard] Re: Setting up Debian VM for BBB

[Brian Tremaine]

Another note, my host is Windows 10 Home 10.0.17134 build 17134

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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/3ecf7d2b-5805-47b8-8287-d263ddbf58e7%40googlegroups.com.

[beagleboard] Re: Setting up Debian VM for BBB

[Brian Tremaine]

If I disable EFI under System I get response "No bootable medium found!"

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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/d5f730ee-7ea2-4df5-b4eb-d9431a98ea87%40googlegroups.com.

Re: [beagleboard] Setting up Debian VM for BBB

[Brian Tremaine]

Note: If I disable EFI bootable medium found!

On Sun, Sep 8, 2019 at 9:57 AM Brian Tremaine  wrote:

> Hi All,
> I realize my question is VirtualBox related but I'm stuck trying to set up
> Debian 'Buster' as my VM for my BBB.
> I've gone through several blogs on the setup but it still won't boot
> Debian.
>
> My iso image is: debian-10.0.0-armhf-netinst.iso
> When I start the VM it drops me into a UEFI shell. If I then go to FS0:
> and do a directory I can 'see' the Debian files.
>
> [image: Capture1.PNG]
>
>
>
> [image: Capture2.PNG]
>
> I have no idea what the UEFI shell is or why I'm there  Can you help
> me boot Debian? Here is a screenshot of my VM setup:
>
> [image: Capture3.PNG]
>
> Thanks in advance 
>
>
>
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/9c5d802a-6ee7-4c52-baf7-9d4528aabaa0%40googlegroups.com
> <https://groups.google.com/d/msgid/beagleboard/9c5d802a-6ee7-4c52-baf7-9d4528aabaa0%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>


-- 
*TremaineConsultingGroup.com*
LinkedIn <https://linkedin.com/in/btremaine/>

669-273-6035

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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/CANqZkw_1fY5TC-NazDnKXAvJa0KhZ_seKh6FQGkpC0%3D98b2V0g%40mail.gmail.com.

[beagleboard] Setting up Debian VM for BBB

[Brian Tremaine]

Hi All,
I realize my question is VirtualBox related but I'm stuck trying to set up 
Debian 'Buster' as my VM for my BBB.
I've gone through several blogs on the setup but it still won't boot Debian.

My iso image is: debian-10.0.0-armhf-netinst.iso
When I start the VM it drops me into a UEFI shell. If I then go to FS0: and 
do a directory I can 'see' the Debian files.

[image: Capture1.PNG] 



[image: Capture2.PNG]

I have no idea what the UEFI shell is or why I'm there  Can you help me 
boot Debian? Here is a screenshot of my VM setup:

[image: Capture3.PNG]

Thanks in advance 


 

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

Re: [beagleboard] Resolving DNS on BBB Rev C Debian

[Brian Tremaine]

I was able to find the info I wanted. It is topic "Cannot ping google in
BBB even after sharing internet" and it was an answer from John Mitton.

I edited file interfaces under /etc/network and added two dns-nameservers
lines for 8.8.8.8 and 8.8.4.4. I added the entries under iface usb0 inet
static
Then I rebooted (required) and it all worked.  I can now ping
www.google.com or any other valid site and get ping data.

Thanks





On Fri, Sep 6, 2019 at 2:27 PM Brian Tremaine  wrote:

> Hi,.
>
> I was following Derek Malloy's tutorial on setting up my USB network on
> BBB. I have the latest Rev C board with Debian.
> the file resolv.conf does not exist and is linked to another file that
> doesn't exist, see below:
>
>  lrwxrwxrwx 1 root root  24 Oct  7 16:40 resolv.conf ->
> /run/connman/resolv.conf
>
> I saw somewhere a way around this but have misplaced the material. I think
> there is a file I need to add nameservers to ... The last I time I tried a
> fix I ended up bricking my BB and had to reflash. I don't know if the
> bricking was a code issue or a hot power down issue.
>
> 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/91784ef3-4134-458d-9b29-1d5156cc0a64%40googlegroups.com
> <https://groups.google.com/d/msgid/beagleboard/91784ef3-4134-458d-9b29-1d5156cc0a64%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>


-- 
*TremaineConsultingGroup.com*
LinkedIn <https://linkedin.com/in/btremaine/>

669-273-6035

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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/CANqZkw-hiA082aafwe_D3Fwyr0_j8yPM8cnCLsx1HBjP4DS86Q%40mail.gmail.com.

[beagleboard] Resolving DNS on BBB Rev C Debian

[Brian Tremaine]

Hi,.

I was following Derek Malloy's tutorial on setting up my USB network on 
BBB. I have the latest Rev C board with Debian.
the file resolv.conf does not exist and is linked to another file that 
doesn't exist, see below:

 lrwxrwxrwx 1 root root  24 Oct  7 16:40 resolv.conf -> 
/run/connman/resolv.conf

I saw somewhere a way around this but have misplaced the material. I think 
there is a file I need to add nameservers to ... The last I time I tried a 
fix I ended up bricking my BB and had to reflash. I don't know if the 
bricking was a code issue or a hot power down issue.

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/91784ef3-4134-458d-9b29-1d5156cc0a64%40googlegroups.com.

Re: [beagleboard] Re: How to connect to wifi network at home?

[Brian Tremaine]

I was able to get this part working thanks to Derek Malloys videos.
In windows Network and sharing your wifi adapter will appear as well as the
local private adapter to the BBB
In the wifi adapter go to properties--> sharing and allow sharing to the
private adapter.
Once that is done, go to the private adapter --> properties. Click Internet
protocol Version 4 (TCP/IPV4) then in the window that pops up select both
Obtain IP and Obtain DNS automatically.

Brian



On Tue, Sep 3, 2019 at 6:32 PM user pc  wrote:

> Thank you. Can I do this without connecting the BBB wifi to a PC and share
> the internet connection?
>
>
> 2019年9月3日火曜日 10時34分57秒 UTC-4 Mark A. Yoder:
>>
>> Here's[1] some notes I have on connecting.  Do they help?
>>
>> --Mark
>>
>> [1] https://elinux.org/EBC_Exercise_06_Setting_Up_Wifi
>>
>> On Monday, September 2, 2019 at 8:11:18 PM UTC-4, user pc wrote:
>>>
>>> Hi, I am new to BB. I have a BeagleBone Black Wireless. Could you please
>>> let me know how to connect it to home wifi network? I can run the board via
>>> usb cable or independently connect it to an external monitor. I once
>>> connected to a monitor but could not find any option to allow me to connect
>>> it to the wireless internet at home. 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/06f98ec6-f99b-4f2f-b62d-92900e64ca99%40googlegroups.com
> <https://groups.google.com/d/msgid/beagleboard/06f98ec6-f99b-4f2f-b62d-92900e64ca99%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>


-- 
*TremaineConsultingGroup.com*
LinkedIn <https://linkedin.com/in/btremaine/>

669-273-6035

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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/CANqZkw9qnsy6-qL-TQZb0SOWnvFN29BZzvotdApMUPMnu3PQ0A%40mail.gmail.com.

[beagleboard] resolv.conf on BB Black Rev C / Debian

[Brian Tremaine]

I finally got my BB to ping 8.8.8.8 through my windows 10 laptop BUT I 
cannot modify resolv.conf to add the name server for www.google.com.

in directory /etc resolv.conf is shown in red, what does this mean? typing 
more resolv.conf gives 'no such file or directory'

Is there a different way to resolve names using the BB Black Rev C running 
Debian? 

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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/8fa5207e-8cf4-4058-831e-1792c02bc7e3%40googlegroups.com.

[beagleboard] Re: Cannot ping google in BBB even after sharing internet

[Brian Tremaine]

I realize this is an old post but I'm hoping to get some answers ;)  : 
Problems pinging www.google.com
 
I have a BeagleBone Black Rev C that is running the latest Debian. I've 
been going through Derek Malloys book and video to get things started 
(excellent material BTW), 

I am connected to a Win 10 laptop (64-bit) using the USB interface and am 
using putty to connect through SSH. My problem is I cannot ping a DNS name, 
i.e. www.google.com. pinging 8.8.8.8 does work. When I try to edit /etc/ 
resolv.conf it says file does not exist. On the terminal the file 
resolv.conf is shown in red; What does this mean?

Can anybody help with hints on how to set up name server on BB Black Rev C 
with Debian?

Thanks,
Brian

On Saturday, January 17, 2015 at 3:47:24 AM UTC-8, Raj_RB wrote:
>
> Hi,
>
> 1) I downloaded 'bone-debian-7.5-2014-05-14-2gb' (BBB eMMC flasher) from '
> http://beagleboard.org/latest-images' and the website given MD5 checksum 
> matched with my downloaded zip file. Then used Win32 Disk Imager (since 
> windows 7), for image writing 4GB microSD.
>
> 2) Inserted microSD into BBB and pressed the boot button and then applied 
> power using the power adapter. (Please note that I have not connected 
> Ethernet and USB cable for power during the whole flashing process). But 
> only power supply LED got lit and not the user LEDs for around 5 seconds. 
> Then I removed the power supply and while pressing the boot button, I 
> provided the power supply and then all LEDs got lit for an instance and 
> then the LEDs started to glow erratically. Within 20 mins all the User 
> LED were off and did not ON again as against the standard procedure in 
> which all LEDs must glow after successful flashing of eMMC.
>
> 3) So, I thought to see if this works and I removed the microSD and power. 
> Then I connected BBB with my PC (by USB) using putty (SSH). I was able to 
> login successfully into debian but I was not able to ping google after 
> adding new gateway (192.168.7.1) and changing nameserver to 8.8.8.8 in 
> '/etc/resolv.conf' file.
>
> Please note that before SSH-ing, I shared my wifi internet with BBB in 
> Network settings(Windows 7) and also I changed the IP address of my BBB to 
> 192.168.7.1. All this worked earlier for me by following this youtube link: 
> (https://www.youtube.com/watch?v=D-NEPiZDSx8). 
>
> Also, BBB (Linux USB ethernet/ RNDIS gadget) in Network settings shows 'No 
> Internet access' eventhough I have shared internet and changed my ip 
> address to 192.168.7.1 with subnet mask 255.255.255.0 leaving the DNS 
> server addresses blank as in the youtube video.
>
> But now it doesn't work eventhough I have already done the same procedure 
> (flashing) many times now with the same result and feeling really 
> frustrated now. Please let me know if I am missing anything here. Is it due 
> to the flashing issue? 
> Waiting for all your inputs! Thank you!!
>
>
> Output:
>
> BeagleBoard.org BeagleBone Debian Image 2014-05-14
> Support/FAQ: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian
> deb...@192.168.7.2 's password:
> Last login: Thu May 15 02:19:40 2014 from 192.168.7.1
> debian@beaglebone:~$ sudo su
> root@beaglebone:/home/debian# route add default gw 192.168.7.1
> root@beaglebone:/home/debian# route -n
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use Iface
> 0.0.0.0 192.168.7.1 0.0.0.0 UG 0 0 0 usb0
> 192.168.7.0 0.0.0.0 255.255.255.252 U 0 0 0 usb0
> root@beaglebone:/home/debian# cat /etc/resolv.conf
> domain localdomain
> search localdomain
> nameserver 192.168.1.1
> root@beaglebone:/home/debian# vim /etc/resolv.conf
> root@beaglebone:/home/debian# cat /etc/resolv.conf
> domain localdomain
> search localdomain
> nameserver 8.8.8.8
> root@beaglebone:/home/debian# ping http://www.google.com
> ping: unknown host http://www.google.com
> root@beaglebone:/home/debian#
>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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/22ad93f3-c979-4f1d-a7ac-cc661f523dd5%40googlegroups.com.

[beagleboard] Help!!! - lost connection to BB Rev C

[Brian Tremaine]

I've been trying to connect to the internet via and USB with my BB Black 
Rev C and in doing so I Iost all USB connection to the BB !!!

As background my laptop is a Win 10 (64 bit system). I was able to connect 
to the Beaglebone and ping 192.168.7.1 and 198.168.7.2 from my BB using SSH 
or from my PC command window. I enabled sharing and used /sbin/route add 
default gw 192.168.7.1 to be able to ping 8.8.8.8.

Next I worked on the DNS resolution. This got me into problems. I modified 
etc/networks/interfaces to add nameserver 8.8.8.8 and nameserver 8.8.8.9 to 
the entry for usb0. The gateway was set properly and I changed the mask to 
255.255.255.0. I also added the nameserver lines to resolv.conf. 
Immediately after this, with out powering down pinging www.google.com 
worked as did other websites !!! success.

As a next test I powered down the BB and restarted. --- Now my laptop 
does not see the BB. My ethernet 2 adapter, which was the BB gateway, says 
media disconnected. Using a web browser on 192.168.7.1 or 192.168.7.2 times 
out with an error, no website found..

How do I recover, AND, what could have caused this problem. 

  -- Thanks for your help, awaiting all replies.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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/d79dd49a-67ab-4158-bf03-38098681f387%40googlegroups.com.

[beagleboard] Using ROS (rosserial) on PocketBeagle

[Brian Malbec]

I'm brand new to using Ubuntu, PocketBeagles, and ROS (Robotic Operating 
System). My current task is to read Xbox controller data on one 
PocketBeagle and be able to receive it on another PocketBeagle. The 
transmission medium is a pair of XBee S2C's. So far, I have been able to 
use /dev/ttyO4 on both PocketBeagles, and the XBees seem to be able to 
successfully communicate, as well as send Xbox controller data. 

Recently, my team and I discovered a package in ROS called rosserial, which 
claims to be able to send ROS serial messages. What we hope this means is 
that we will be able to send more data to the receiving PocketBeagle (under 
the belief that these ROS messages are smaller in size compared to sending 
raw controller data). Unfortunately, it seems that all of the support for 
this package is for Arduino, with little-to-no support for any other type 
of hardware, specifically embedded Linux. Rosserial also seems to have 
extensions for embeddedlinux and XBee, but nothing seems to be working. Is 
there anyone on this forum that is knowledgeable in ROS (especially 
rosserial) that can assist me?

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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/589d5c3e-0782-4760-8159-a6d7fbf2b5a3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Disappearing static IP address

[Brian Larson]

I have not had a lot of time to dig into this more but wanted to post a 
quick comment about what I initially found after trying this solution.

After running the command I lost my dynamic IP and was left with the static 
one. I rebooted the Beaglebone and had my dynamic IP back but lost my name 
resolution. I was unable to ping the static IP I have set on my laptop 
(might be a firewall issue) but was able to ping google (using ip not 
name). My laptop is connected to wifi and a wired network switch that has 
internet access which my Beaglebone is connected to and I was able to ping 
the WIFI address but not the static IP on my laptop but I was successful in 
pinging the Beaglebone from my laptop.

# connmanctl config ethernet_38d2697463bf_cable --ipv4 manual 192.168.1.100 
255.255.255.0 192.168.1.1 --nameservers 8.8.8.8
# ip addr show eth0 
4: eth0:  mtu 1500 qdisc 
pfifo_fast state UP group default qlen 1000
link/ether 38:d2:69:74:63:bf brd ff:ff:ff:ff:ff:ff
inet 192.168.1.100/24 brd 192.168.1.255 scope global eth0:1
   valid_lft forever preferred_lft forever
inet6 fe80::3ad2:69ff:fe74:63bf/64 scope link
   valid_lft forever preferred_lft forever

$ ping www.google.com
   ping: www.google.com: Temporary failure in name resolution

$ ping 172.217.0.4
   PING 172.217.0.4 (172.217.0.4) 56(84) bytes of data.
   64 bytes from 172.217.0.4: icmp_seq=1 ttl=54 time=10.4 ms
   64 bytes from 172.217.0.4: icmp_seq=2 ttl=54 time=10.4 ms
   64 bytes from 172.217.0.4: icmp_seq=3 ttl=54 time=10.6 ms
   64 bytes from 172.217.0.4: icmp_seq=4 ttl=54 time=11.0 ms
   64 bytes from 172.217.0.4: icmp_seq=5 ttl=54 time=10.8 ms
   64 bytes from 172.217.0.4: icmp_seq=6 ttl=54 time=10.8 ms
   64 bytes from 172.217.0.4: icmp_seq=7 ttl=54 time=10.3 ms
   ^C
   --- 172.217.0.4 ping statistics ---

$ ping 8.8.8.8
   PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
   64 bytes from 8.8.8.8: icmp_seq=1 ttl=57 time=15.3 ms
   64 bytes from 8.8.8.8: icmp_seq=2 ttl=57 time=17.0 ms
   64 bytes from 8.8.8.8: icmp_seq=3 ttl=57 time=15.2 ms
   64 bytes from 8.8.8.8: icmp_seq=4 ttl=57 time=15.2 ms
   64 bytes from 8.8.8.8: icmp_seq=5 ttl=57 time=15.8 ms
   64 bytes from 8.8.8.8: icmp_seq=6 ttl=57 time=15.1 ms
   ^C
   --- 8.8.8.8 ping statistics ---

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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/4c68eaf9-0a51-4ab9-a0bf-946c2e35746c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Disappearing static IP address

[Brian Larson]

Hi All,

I have a project with my Beaglebone Black which needs a static and dynamic 
IP. I set up my /etc/network/interfaces file to have eth0 as dhcp and then 
added an IP alias of eth0:1 with a static IP. I did a reboot with the 
network cable unplugged to make sure that it comes up on boot and 
everything looked good for about 10 minutes until my static IP disappeared. 
At this point I tried to connect the network cable and the dhcp eth0 came 
up fine but the static eth0:1 still did not show and was unable to ping it 
from my laptop. Output below along with interfaces contents. I have the 
network cable disconnected because the device will not always have one 
connected at boot and needed to test this condition. Also I need two IPs 
because I need to send data out to the Internet and won't always know the 
IP scheme that is being used and also need to connect to a local device 
using a 192.168.1.x IP. This problem seems similar to this one 
https://unix.stackexchange.com/questions/211215/mysterious-disappearing-static-ip-address-on-wifi-interface-under-debian
 
other than I'm using the on-board network port and I didn't see wicd 
running on my system.

It appears that so far I am able to get the IP to stick by using the 
command "ip addr add 192.168.1.100/24 dev eth0". I then created a shell 
script and a service that runs the shell script at boot.

I am no Linux expert but have what appears to be a workaround for something 
that I should have been able to do in the /etc/network/interfaces file. Am 
I missing something in my interfaces file that would make this work or is 
the shell script/service the best way to accomplish this task?

I'm sorry if this is more of a Linux question than a Beaglebone question 
but since the Beaglebone comes stock with Linux and I am using a Beaglebone 
I thought I would post it here.

*** network cable disconnected 
***
debian@beaglebone:~$ uname -a
Linux beaglebone 4.4.91-ti-r133 #1 SMP Tue Oct 10 05:18:08 UTC 2017 armv7l 
GNU/Linux

debian@beaglebone:~$ date
Tue Oct 10 12:09:14 UTC 2017

debian@beaglebone:~$ ip addr show eth0
4: eth0:  mtu 1500 qdisc pfifo_fast 
state DOWN group default qlen 1000
link/ether 11:22:33:44:55:bb brd ff:ff:ff:ff:ff:ff
inet 192.168.1.100/24 brd 192.168.1.255 scope global eth0:1
   valid_lft forever preferred_lft forever

debian@beaglebone:~$ date
Tue Oct 10 12:21:32 UTC 2017

debian@beaglebone:~$ ip addr show eth0
4: eth0:  mtu 1500 qdisc pfifo_fast 
state DOWN group default qlen 1000
link/ether 11:22:33:44:55:bb brd ff:ff:ff:ff:ff:ff

*** connected network cable 
***
debian@beaglebone:~$ ip addr show eth0
4: eth0:  mtu 1500 qdisc pfifo_fast state 
UP group default qlen 1000
link/ether 11:22:33:44:55:bb brd ff:ff:ff:ff:ff:ff
inet 192.168.254.212/24 brd 192.168.254.255 scope global eth0
   valid_lft forever preferred_lft forever
inet6 fe80::3ad2:69ff:fe74:63bf/64 scope link
   valid_lft forever preferred_lft forever

   
*** /etc/network/interfaces 
***
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
iface eth0 inet dhcp

auto eth0:1
iface eth0:1 inet static
 address 192.168.1.100
 netmask 255.255.255.0

# Example to keep MAC address between reboots
#hwaddress ether DE:AD:BE:EF:CA:FE

##connman: ethX static config
#connmanctl services
#Using the appropriate ethernet service, tell connman to setup a static IP 
address for that service:
#sudo connmanctl config  --ipv4 manual   
 --nameservers 

##connman: WiFi
#
#connmanctl
#connmanctl> tether wifi off
#connmanctl> enable wifi
#connmanctl> scan wifi
#connmanctl> services
#connmanctl> agent on
#connmanctl> connect wifi_*_managed_psk
#connmanctl> quit

# Ethernet/RNDIS gadget (g_ether)
# Used by: /opt/scripts/boot/autoconfigure_usb0.sh
iface usb0 inet static
address 192.168.7.2
netmask 255.255.255.252
network 192.168.7.0
gateway 192.168.7.1
***

Thanks in advance for any help/insight into this issue.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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/dfcb306f-6ea2-440c-809f-dd5b19b9766b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] I have a BBB Rev C (4 gig) but fdisk only shows that the eMMC has 1.8 gigs.

[Brian Wiegand]

That is interesting. So Adafruit must have sent me a SUPER old version
On Sun, Oct 8, 2017 at 7:32 AM Robert Nelson 
wrote:

> On Sun, Oct 8, 2017 at 1:07 AM, Brian Wiegand  wrote:
> >> I'm not even sure where to begin with this one. Fdisk really shouldn't
> be
> >> showing wrong disk sizes and I've checked file-systems, deleted and
> rewrote
> >> the partition tables, deleted and created partitions.
> >
> >
> > Has anyone else had this strange problem before? Any more information I
> can
> > provide.
>
> > eeprom:[A335BNLT0A5C3313BBBK3434]
>
> 0A5C is not a rev "C", it's rev "A" with only 2GB eMMC..
>
> Regards,
>
> --
> Robert Nelson
> https://rcn-ee.com/


So I wasn't sold the Rev C. Adafruit has some explaining to do. Thanks for
the insight Robert..

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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/CAEqJHpVE2YZbSSxONPaoUgPqTFPobFPAG9_VjA%3D93uVMOV9qKg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] I have a BBB Rev C (4 gig) but fdisk only shows that the eMMC has 1.8 gigs.

[Brian Wiegand]

>
> I'm not even sure where to begin with this one. Fdisk really shouldn't be 
> showing wrong disk sizes and I've checked file-systems, deleted and rewrote 
> the partition tables, deleted and created partitions.


Has anyone else had this strange problem before? Any more information I can 
provide.

Fdisk output.

root@beaglebone:/# fdisk -l
Disk /dev/mmcblk0: 14.7 GiB, 15719727104 bytes, 30702592 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: 0xad20d647


Device Boot Start  End  Sectors  Size Id Type
/dev/mmcblk0p1 * 8192 30702591 30694400 14.7G 83 Linux




Disk /dev/mmcblk1: 1.8 GiB, 1920991232 bytes, 3751936 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xe9000d91


Device Boot Start End Sectors  Size Id Type
/dev/mmcblk1p1   2048 3751935 3749888  1.8G 83 Linux




Disk /dev/mmcblk1boot1: 1 MiB, 1048576 bytes, 2048 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes




Disk /dev/mmcblk1boot0: 1 MiB, 1048576 bytes, 2048 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Version script.

root@beaglebone:/opt/scripts/tools# ./version.sh
git:/opt/scripts/:[9e4538c8313aae2d2ff50b07ec5e0ee7685a840c]
eeprom:[A335BNLT0A5C3313BBBK3434]
dogtag:[BeagleBoard.org Debian Image 2017-09-21]
bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot 2017.09-3-
g11d92ba68a]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2017.09-rc2-2-g7c9353
]
kernel:[4.4.88-ti-r125]
nodejs:[v6.11.3]
uboot_overlay_options:[enable_uboot_overlays=1]
uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-4-
TI-00A0.dtbo]
uboot_overlay_options:[enable_uboot_cape_universal=1]
pkg:[bb-cape-overlays]:[4.4.20170921.0-0rcnee1~stretch+20170921]
pkg:[bb-wl18xx-firmware]:[1.20170829-0rcnee1~stretch+20170829]
pkg:[firmware-ti-connectivity]:[20170823-1rcnee0~stretch+20170830]


-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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/0305a78a-54af-43f7-b6fa-c3c1fc6d0ab0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Failed password for invalid user in /var/log/auth.log ?

[Brian Yates]

Mr. Nelson was correct on guess #2. And yes, it's all a bit over my head, 
but I'm trying...thanks for the help.
On Monday, April 10, 2017 at 8:31:05 PM UTC-4, RobertCNelson wrote:
>
> On Mon, Apr 10, 2017 at 5:33 PM, Drew Fustini  > wrote: 
> > Has anyone seen ssh warnings similar to this in /var/log/auth.log on 
> > their BeagleBone? 
> > 
> > pam_unix(sshd:auth): check pass; user unknown 
> > pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 
> > tty=ssh ruser= rhost=103.207.37.232 
> > Failed password for invalid user support from 103.207.37.232 port 57227 
> ssh2 
> > fatal: Read from socket failed: Connection reset by peer [preauth] 
> > Did not receive identification string from 103.207.37.232 
> > Address 123.31.31.90 maps to localhost, but this does not map back to 
> > the address - POSSIBLE BREAK-IN ATTEMPT! 
> > Invalid user support from 123.31.31.90 
> > input_userauth_request: invalid user support [preauth] 
> > pam_unix(sshd:auth): check pass; user unknown 
>
>
> So the beagle with an address of 123.31.31.90, had a host trying to 
> connect, and it blocked it: 
>
> beagle: 
> http://ipaddress.is/123.31.31.90 
>
> host trying to connect: 
> http://ipaddress.is/103.207.37.232 
>
> This either occurred from two ways: 
>
> 1: his upstream provider gave him a new ip address 
>
> 2: he connected the Beagle directly to the web. 
>
> I'm going to guess #2, and his board is either a bot now, or probally 
> will be shortly.. 
>
> aka, get a firewall, port forward, don't use port 22, etc... 
>
> 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/739bf169-c0c7-4c61-8442-8243034db7a5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: 2017-03-19 images published on beagleboard.org/latest-images

[Brian Cooke]

RobertCNelson figured out why I couldn't boot a BBB after flashing Debian 
8.7 (Jessie) 2017-03-19 onto an SD card. It was an old bootloader in eMMC. 
(see 
https://github.com/julianduque/beaglebone-io/pull/32#issuecomment-292926642 
and the responses.)

On Sunday, April 2, 2017 at 12:59:23 PM UTC+2, Brian Cooke wrote:
>
> For some reason I can't manage to boot a BBB after flashing Debian 8.7 
> (Jessie) 2017-03-19 onto an SD card.
> The following command was used to flash the SD card:
>
> xz -dkc bone-debian-8.7-iot-armhf-2017-03-19-4gb.img.xz > /dev/sdc
>
> Has something related to flashing/booting changed compared to previous 
> releases?
>
> I have the same issue with bone-debian-8.7-iot-armhf-2017-03-26-4gb.img.xz
>
> On Wednesday, March 22, 2017 at 8:16:44 AM UTC+1, Jason Kridner wrote:
>>
>>
>> https://jkridner.wordpress.com/2017/03/22/2017-03-19-beaglebone-debian-images-published/
>>  
>>
>> Debian 8.7 (Jessie) 2017-03-19 images are now published on 
>> https://beagleboard.org/latest-images, but this version isn’t likely to 
>> live more than a few weeks before we push yet another. The big update here 
>> is eliminating the need to install drivers for any of Windows, Mac or Linux 
>> host users when working over USB networking. This was accomplished by 
>> updating the default RNDIS interface to use a USB 
>> class/subclass/protocol recommended by Microsoft for users of Windows Vista 
>> and newer 
>> <https://msdn.microsoft.com/en-us/library/windows/hardware/ff538820(v=vs.85).aspx>.
>>  
>> To support Mac OS X out of the box, we added a second virtual network 
>> interface supporting the CDC-ECM mode, rather than RNDIS.
>>
>> Mac users are no longer recommended to install HoRNDIS 
>> <http://joshuawise.com/horndis>, but man do we appreciate all that 
>> Joshua Wise did in supporting the BeagleBoard.org community by creating 
>> that product and continuing to resolve issues around it on subsequent OS X 
>> releases. Mac users should now be able to discover their boards using 
>> http://beaglebone.local as Bonjour/Avahi/mDNS is a standard service on 
>> OS X, but note that http://192.168.6.2 should be the new magic IP 
>> address for this new interface.
>>
>> One issue I’ve seen on Macs with the latest image is the interface now 
>> shows itself as a gateway, encouraging you to drive traffic through this 
>> port—and that could mess up your connection to the Internet. Your 
>> BeagleBone should proxy the traffic fine if it is connected to the 
>> Internet, but the DNS proxy isn’t working the best, meaning you might not 
>> be able to look up the names of servers on the Internet. One quick 
>> work-around is to apply the Google DNS servers (8.8.8.8, 8.8.4.4) to your 
>> new network adapter. There are many alternatives to that, but those are 
>> ones I know off the top of my head. I think we should be able to address 
>> this whole experience issue by asking Joshua how he avoided the issue with 
>> HoRNDIS—and that is the next step.
>>
>> The other big updates here are some fixes to BoneScript (0.6.1) and 
>> libroboticscape (0.3.4) for BeagleBone Blue 
>> <https://beagleboard.org/blue>, the new robotics-focused BeagleBone. 
>> Many feature gaps and bugs remain, but this fixes some of the immediate 
>> show-stoppers for people getting started. Now that the board is out there 
>> in 1,000s of users hands, I expect the bug reports to start rolling in and 
>> we can use that to drive immediate development to resolve issues.
>>
>> So, long live 2017-03-19…. but not very long.
>>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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/1ed2525e-ab88-4990-a0aa-69e8d7f3762a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Can't update debian version 7.11

[Brian Yates]

I recently put a Debian 7.11 image on my BeagleBone Black RevC. The image 
file is : bone-debian-7.11-lxde-4gb-armhf-2016-06-15-4gb.img. 
When I try to update, the following error messages appear:
devo@beaglebone:~$ sudo apt-get update
Err http://repos.rcn-ee.com wheezy Release.gpg
  Could not resolve 'repos.rcn-ee.com'
Err http://httpredir.debian.org wheezy Release.gpg
  Could not resolve 'httpredir.debian.org'
Err http://httpredir.debian.org wheezy-updates Release.gpg
  Could not resolve 'httpredir.debian.org'
Err http://security.debian.org wheezy/updates Release.gpg
  Could not resolve 'security.debian.org'
Reading package lists... Done
W: Failed to fetch 
http://httpredir.debian.org/debian/dists/wheezy/Release.gpg  Could not 
resolve 'httpredir.debian.org'

W: Failed to fetch 
http://httpredir.debian.org/debian/dists/wheezy-updates/Release.gpg  Could 
not resolve 'httpredir.debian.org'

W: Failed to fetch 
http://security.debian.org/dists/wheezy/updates/Release.gpg  Could not 
resolve 'security.debian.org'

W: Failed to fetch http://repos.rcn-ee.com/debian/dists/wheezy/Release.gpg  
Could not resolve 'repos.rcn-ee.com'

W: Some index files failed to download. They have been ignored, or old ones 
used instead.

Drew Fustini suggested I post this here. 

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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/f8ca3b04-08b4-491a-884f-2eca1487af2c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: 2017-03-19 images published on beagleboard.org/latest-images

[Brian Cooke]

For some reason I can't manage to boot a BBB after flashing Debian 8.7 
(Jessie) 2017-03-19 onto an SD card.
The following command was used to flash the SD card:

xz -dkc bone-debian-8.7-iot-armhf-2017-03-19-4gb.img.xz > /dev/sdc

Has something related to flashing/booting changed compared to previous 
releases?

I have the same issue with bone-debian-8.7-iot-armhf-2017-03-26-4gb.img.xz

On Wednesday, March 22, 2017 at 8:16:44 AM UTC+1, Jason Kridner wrote:
>
>
> https://jkridner.wordpress.com/2017/03/22/2017-03-19-beaglebone-debian-images-published/
>  
>
> Debian 8.7 (Jessie) 2017-03-19 images are now published on 
> https://beagleboard.org/latest-images, but this version isn’t likely to 
> live more than a few weeks before we push yet another. The big update here 
> is eliminating the need to install drivers for any of Windows, Mac or Linux 
> host users when working over USB networking. This was accomplished by 
> updating the default RNDIS interface to use a USB class/subclass/protocol 
> recommended by Microsoft for users of Windows Vista and newer 
> .
>  
> To support Mac OS X out of the box, we added a second virtual network 
> interface supporting the CDC-ECM mode, rather than RNDIS.
>
> Mac users are no longer recommended to install HoRNDIS 
> , but man do we appreciate all that Joshua 
> Wise did in supporting the BeagleBoard.org community by creating that 
> product and continuing to resolve issues around it on subsequent OS X 
> releases. Mac users should now be able to discover their boards using 
> http://beaglebone.local as Bonjour/Avahi/mDNS is a standard service on OS 
> X, but note that http://192.168.6.2 should be the new magic IP address 
> for this new interface.
>
> One issue I’ve seen on Macs with the latest image is the interface now 
> shows itself as a gateway, encouraging you to drive traffic through this 
> port—and that could mess up your connection to the Internet. Your 
> BeagleBone should proxy the traffic fine if it is connected to the 
> Internet, but the DNS proxy isn’t working the best, meaning you might not 
> be able to look up the names of servers on the Internet. One quick 
> work-around is to apply the Google DNS servers (8.8.8.8, 8.8.4.4) to your 
> new network adapter. There are many alternatives to that, but those are 
> ones I know off the top of my head. I think we should be able to address 
> this whole experience issue by asking Joshua how he avoided the issue with 
> HoRNDIS—and that is the next step.
>
> The other big updates here are some fixes to BoneScript (0.6.1) and 
> libroboticscape (0.3.4) for BeagleBone Blue , 
> the new robotics-focused BeagleBone. Many feature gaps and bugs remain, but 
> this fixes some of the immediate show-stoppers for people getting started. 
> Now that the board is out there in 1,000s of users hands, I expect the bug 
> reports to start rolling in and we can use that to drive immediate 
> development to resolve issues.
>
> So, long live 2017-03-19…. but not very long.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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/cda1bada-e6e6-4de8-bbd4-76dc78aa7c4c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Removal of Components from BBBW for Custom PCB.

[Brian Dohler]

Hi All,


I'm making a custom BBBW for a school project. I'm adding a few peripherals 
but would like to strip down what is unnecessary in order to save on BOM 
costs. The first to go is the large HDMI chip. It looks like there's a few 
small components which support it. I just want to be sure that i can remove 
them without causes issues for the Linux OS. 



<https://lh3.googleusercontent.com/-kgNvY-hzXz0/WCT7d9RuuLI/Bcc/GngTMWHb5qQjnGZ75mHENF8Gg6rGSlCvgCLcB/s1600/Capture.PNG>

I'm in particular interested in the components above. OSC1 outputs to 
GPIO3_21, which is used in the Cape header. I'm curious if the OSD3358 ever 
uses this clock as an input, however, or whether it's just to save space in 
the headers.

Thanks in advance,
Brian Dohler

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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/ef847373-3571-4ff3-ae66-317d61eed0ac%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Hardware watchdog for BBB

[Brian Anderson]

You might be interested in the Beaglebone Power Cape from Andice Labs 
(http://andicelabs.com). Ron recently posted a blog entry on using the Power 
Cape to address some of the issues you are raising. The Power Cape has an 
onboard microprocessor, battery charger, etc.

ba

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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/aadf2585-68c0-449e-b08e-ebeb4c080145%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Power - shutdown

[Brian Anderson]

> I think what I am leaning on doing is providing 5V directly to the VDD_5V 
> connector with a diode fused battery+external power through a controllable 
> regulator, and then using a tiny micro (most likely a PIC) to monitor power 
> loss and then trigger an interrupt on a pin to cause the shutdown, then 
> wait for the shutdown and then turn off power.  If power comes up during 
> this process, the front end can halt powering the BBB until it is fully 
> down.  
>
> I'll get a couple BBBs to experiment and if this works, I'll post what I 
> came up with.
>
>
You might find the Beaglebone Power Cape 
 from Andice Labs interesting.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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/179a6587-4533-4a6c-9dab-c78e3ba265c5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] BBB SSH issues, Please Help

[brian . searle]

Hello, I'm having trouble using SSH to connect to my BBB. 

I just got it for a school project, and was trying to set it up to connect 
with my Mac OS X. So I followed the getting started steps and everything 
worked great. Installed the 2 drivers and used the ssh root@192.168.7.2 and 
installed googles Go. Also Added a few path variables to the bottom of the 
bashrc file. Everything worked, and tested the basic helloworld.go program, 
which ran. I wanted to disconnect everything and reconnect to be sure once 
everything was off for awhile it still worked. So I unplugged the USB cable 
to the BBB and then replugged it in. However the ssh command just hangs 
(also tried to connect via web browser but no good). I then tried to 
reinstall the drivers, and it worked. Ran the helloworld.go program, and it 
was still good. So I disconnected more safely this time. I ejected the 
drive from the Desktop, and then unplugged the usb cable. Replugged the USB 
cable, but the ssh command would hang again. I tried repeating the 
reinstall the drives (multiple times) method but it didn't work this time. 
I've tried pressing the BBB onboard reset button and the on/off button but 
I can't seem to get the SSH command to not hang. Please help! thank you 
(sorry if this is a repost but I couldn't find anything relevant).

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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: BLE and WIFI module for beaglebone black.

[Brian Anderson]

> Hi,
> thanks for reply!
> cape is costly solution.
> I am thinking of using a module. 
> similar to the module in link below-
>
> http://www.cnx-software.com/2015/11/18/redbear-duo-is-a-breadboard-friendly-wi-fi-ble-iot-board-based-on-ampak-ap6212-module-crowdfunding/
>

Or, if you are just interested in experimenting with WiFi and BT , want to 
easily get something running, and don't care about tightly integrated 
solutions, you could use USB dongles and a _powered_ USB hub.

 TP-Link TL-WN722N works great and has good kernel driver/firmware support 
(based on Atheros chipset).

As far as BT, I have successfully used JBtek and Kinovo USB dongles.

The issue with any module is going to be kernel driver and firmware support.

ba

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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] Using Connman for WiFi AP/tether...

[Brian Anderson]

> Do you know how to ConnMan to create a access point without password? 
>  is ConnMan suport that ?
>

Unfortunately, no.  Connman requires a passphrase.   In fact, the 
passphrase must be at least 8 and no more than 63 characters.  You can see 
this in the source code (technology.c, line 926).

ba

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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] Using Connman for WiFi AP/tether...

[Brian Anderson]

>
> Yeah, once we find a Windows "mDNS" discovery (like Bonjour but 
> distribtable) we can stick in that in the flash drive that pop's up, 
> and switch usb0 to connman.. 
>

Yes, thats a good idea.  Any while you are at it, maybe a "preconfigured" 
PuTTY or something like that so users can automagically and hassle free 
connect to their shiny new board via usb ethernet?

>
> > 
> > Also, this Wikipedia article on ".local" is enlightening.  The article 
> > suggests that counting on hostname.local resolution may not scale well 
> to 
> > Windoze environments. 
>
> I think as long as it works on one, that's good enough for out of box. ;) 
>

Yes, I guess that's correct!  External networks not involved! 

ba

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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] Using Connman for WiFi AP/tether...

[Brian Anderson]

> >>> >> Drop dnsmasq/create_ap, add back udhcpd 
>

Just curious, why udhcpd rather than dnsmasq?  Isn't dnsmasq supposed to be 
"light weight"?  Err, lighter than udhcpd?  What is the difference between 
the two? 
 

> >>  I presume you 
> >> have told Connman to ignore usbx  interfaces in /etc/connman/main.conf? 
> > 
> > Here's the configuration i'm using at the moment, i'll test adding an 
> > ignore for usbx 
> > 
> > 
> https://github.com/RobertCNelson/omap-image-builder/blob/master/target/chroot/beagleboard.org-jessie.sh#L190-L220


Hmm, I see you are ignoring usb0 rather than all usb interfaces.  I suppose 
that is the only possiblity on BBB.  Not sure about other boards.

BTW, does it work to put a USB hub between the host and gadget and thus 
connect multiple hosts (laptop, desktop, etc.) to the usb ethernet and thus 
serve up many IP addresses from usb0 gadget?

 

> Okay, that should solve a race: 
>

Cool. 

ba

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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] Using Connman for WiFi AP/tether...

[Brian Anderson]

> >> yeah, very racy, and a bad idea. ;) 
> >> 
> >> So i now have things working a littler closer to a connman only 
> solution.. 
> >> 
> >> Drop dnsmasq/create_ap, add back udhcpd 
> >> 
> >> usb0 : udhcpd (192.168.7.2) 
> >> wlan0: connman ap (192.168.0.1) 
>

Assuming Connman manages wlanx (AP or STA) as well as ethx.  I presume you 
have told Connman to ignore usbx  interfaces in /etc/connman/main.conf?

>> 
> >> Windows 10 (usb0, beaglebone.local doesn't work) 
>

Hmm.  So, if udhcpd is managing the _static_ address on usb0, then counting 
on mDNS hostname discovery in no longer a requirement, just a nice to 
have?  For Windoze users, they call still access via static IP, other 
platforms can access via static IP via hostname.local.  With that said, if 
we do include mDNS for Windoze users, and start advertising hostname.local 
as the _preferred_ way of access, then _eventually_ we could rid ourselves 
of the static IP access method.

Also, this  Wikipedia article on 
".local" is enlightening.  The article suggests that counting on 
hostname.local resolution may not scale well to Windoze environments.

>> 
> >> I wonder Jason's thought on "shipping" this installer? 
> >> 
> >> https://support.apple.com/kb/DL999?locale=en_US 
> > 
> > Does it work? 
>
> It does work on Windows 10, "http://beaglebone.local"; comes up over 
> usb0 just fine.. 
>
> >Do they provide a redistribution license? 
>
> I haven't found a clear license on that, everyone seems to link to it. 
> Or users are too cut it out of the itunes.exe binary.. yuck. 
>
> (maybe we can just link in the documentation for windows users) 
>
> 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] Using Connman for WiFi AP/tether...

[Brian Anderson]

> > So one has to wonder if it would be wise to eliminate 
> > /etc/network/interfaces (or at least have everthing commented out with 
> > warnings) to help prevent the often occurring confusion when Connman 
> > overrides definitions in /etc/network/interfaces.  And, of course, 
> > /etc/network/interfaces is supposed to be "legacy". 
>
> I think we will just blank it out, then users can add there own tweaks.. 
>

With a big fat warning about connman overriding certain settings!
 

>
> I think i figured out how to get the usb0 to start at 192.168.7.2 
>
> https://paste.debian.net/413402/


Err, couldn't figure out from the pastebin.  Looked at your repo, and it 
appears you are trying to have some control over what the starting IP 
address that DHCP will hand out for tethering?  If so, I don't think you 
can necessarily assume that the USB gadget will be the first thing needing 
an address can you? What if one tethers WiFi then USB?  What if there is an 
address conflict with the localhost or USB host?  I'm assuming that connman 
deals with these use cases when allocating a new IP address via its 
internal DHCP.  And you still won't get the "static" address you desire.


>
> (so much stuff is hard-coded for 192.168.7.2) 
>

Ya, and therein lies the problem it seems.  Maybe it would be best to bite 
the bullet here and go for .local discovery?  OTOH, not sure if 
mDNS hostname discovery works on a Windoze machine?


ba

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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] Using Connman for WiFi AP/tether...

[Brian Anderson]

On Tuesday, March 8, 2016 at 2:01:36 PM UTC-8, RobertCNelson wrote:
>
> PS, i'm also switched to 'git' on the build: 
>
>
> https://github.com/rcn-ee/repos/commit/dd480e6dac1317eac1cc15b2a60740e7ba53128e
>  
>
> It's currently building, so i'll retest in a bit.. 
>
> > Did you unplug/replug the USB cable from the desktop?  When first 
> enabling 
> > this with the cable plugged in, it seems to require a re-plug to get 
> DHCP to 
> > issue an IP.  But I suppose your dhclient request from the desktop side 
> > should have triggered this. 
>
> That's actually going to be a problem. On the BeagleBone Green, power 
> comes thru usb0...  (and i've run out of BeagleBone Black's at 
> work...) 
>

Ya.  I have a couple of BBGs and didn't read the fine print close enough to 
see that there is no barrel jack.
So, I have an Andice Labs Power Cape at the ready and/or build my own power 
supply as power over USB is obviously such a non-starter for real work.

 

>
> I've tried, restarting connman.service, that didn't help... We might 
> have to fake a hotplug event? 
>

Sounds like the right thing, but I haven't done that before. I suppose a 
hotplug event on boot iff a usb cable is plugged in?
 

>
> >> (systemd: 215 debian jessie) 
> >> 
> >> dnsmasq/create_ap removed 
> >> 
> >> $(dirname $0)/autoconfigure_usb0.sh disabled... 
> >> 
> >> bone: 
> >> 
> >> usb0  Link encap:Ethernet  HWaddr ec:24:b8:d2:06:a0 
> >>   inet6 addr: fe80::ee24:b8ff:fed2:6a0/64 Scope:Link 
> >>   UP BROADCAST RUNNING MULTICAST DYNAMIC  MTU:1500  Metric:1 
> >>   RX packets:6 errors:0 dropped:0 overruns:0 frame:0 
> >>   TX packets:20 errors:0 dropped:0 overruns:0 carrier:0 
> >>   collisions:0 txqueuelen:1000 
> >>   RX bytes:1968 (1.9 KiB)  TX bytes:6180 (6.0 KiB) 
> > 
> > 
> > Do you see a tether interface (ip addr)?  Attached log has output from 
> ip on 
> > bone.  And of course, if you have rebooted, you need to enable the 
> tether 
> > again unless you have setup things for persistent tethering...some 
> connman 
> > config parameter. 
>
> Nope, no tether, and i've enabled: 
>
> PersistentTetheringMode=true 
>
> err.. 
>
> that seems like it was it!! 
>
> mkdir /etc/connman/ 
> mv /etc/connman.conf /etc/connman/main.conf 
>
> reboot... 
>
> Mar 08 21:57:44 beaglebone connmand[307]: usb0 {RX} 0 packets 0 bytes 
> Mar 08 21:57:44 beaglebone connmand[307]: usb0 {TX} 3 packets 390 bytes 
> Mar 08 21:57:44 beaglebone connmand[307]: usb0 {newlink} index 3 
> address EC:24:B8:D2:06:A0 mtu 1500 
> Mar 08 21:57:44 beaglebone connmand[307]: usb0 {newlink} index 3 
> operstate 6  
> Mar 08 21:57:45 beaglebone connmand[307]: usb0 {RX} 0 packets 0 bytes 
> Mar 08 21:57:45 beaglebone connmand[307]: usb0 {TX} 3 packets 390 bytes 
> Mar 08 21:57:45 beaglebone connmand[307]: usb0 {newlink} index 3 
> address EC:24:B8:D2:06:A0 mtu 1500 
> Mar 08 21:57:45 beaglebone connmand[307]: usb0 {newlink} index 3 
> operstate 6  
> Mar 08 21:57:45 beaglebone connmand[307]: usb0 {newlink} index 3 
> address EC:24:B8:D2:06:A0 mtu 1500 
> Mar 08 21:57:45 beaglebone connmand[307]: usb0 {newlink} index 3 
> operstate 6  
> Mar 08 21:57:45 beaglebone connmand[307]: usb0 {newlink} index 3 
> address EC:24:B8:D2:06:A0 mtu 1500 
> Mar 08 21:57:45 beaglebone connmand[307]: usb0 {newlink} index 3 
> operstate 6  
> Mar 08 21:57:45 beaglebone connmand[307]: usb0 {newlink} index 3 
> address EC:24:B8:D2:06:A0 mtu 1500 
> Mar 08 21:57:45 beaglebone connmand[307]: usb0 {newlink} index 3 
> operstate 6  
> Mar 08 21:57:45 beaglebone kernel: device usb0 entered promiscuous mode 
> Mar 08 21:57:45 beaglebone kernel: tether: port 1(usb0) entered forwarding 
> state 
> Mar 08 21:57:45 beaglebone kernel: tether: port 1(usb0) entered forwarding 
> state 
>
> bone: 
>
> tetherLink encap:Ethernet  HWaddr ec:24:b8:d2:06:a0 
>   inet addr:192.168.0.1  Bcast:192.168.0.255  Mask:255.255.255.0 
>   inet6 addr: fe80::38b0:4eff:feb4:9211/64 Scope:Link 
>   UP BROADCAST RUNNING MULTICAST DYNAMIC  MTU:1500  Metric:1 
>   RX packets:684 errors:0 dropped:0 overruns:0 frame:0 
>   TX packets:360 errors:0 dropped:0 overruns:0 carrier:0 
>   collisions:0 txqueuelen:0 
>   RX bytes:66369 (64.8 KiB)  TX bytes:38011 (37.1 KiB) 
>
> usb0  Link encap:Ethernet  HWaddr ec:24:b8:d2:06:a0 
>   inet6 addr: fe80::ee24:b8ff:fed2:6a0/64 Scope:Link 
>   UP BROADCAST RUNNING MULTICAST DYNAMIC  MTU:1500  Metric:1 
>   RX packets:684 errors:0 dropped:0 overruns:0 frame:0 
>   TX packets:380 errors:0 dropped:0 overruns:0 carrier:0 
>   collisions:0 txqueuelen:1000 
>   RX bytes:66369 (64.8 KiB)  TX bytes:60067 (58.6 KiB) 
>
> desktop: 
>
> enxec24b8d206af: flags=4163  mtu 1500 
> inet 192.168.0.2  netmask 255.255.255.0  broadcast 192.168.0.255 
> inet6 fe80::ee24:b8ff:fed2:6af  prefixlen 64  scopeid 0x20 
> ether ec:24:b8:d2:06:a

Re: [beagleboard] Using Connman for WiFi AP/tether...

[Brian Anderson]

>
>> sudo dhclient enxec24b8d206af not getting an ip... 
>>
>
> Didn't have to do that.  Well, maybe that would have negated the need to 
> re-plug the cable.  I have an IP on the host side:
>
>
OK, I rebooted the Bone and enabled the tether from the Bone.  IP didn't 
show up on laptop.  dhclient on the laptop hung (well, maybe it would 
timeout but I was impatient).  Re-plugging the cable got me a shiny new IP 
on the laptop (eth1).  Laptop is running Linux Mint and Network Manager.

ba 

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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] Using Connman for WiFi AP/tether...

[Brian Anderson]

 

>
>
> Humm, not getting an ip over usb0 yet, (connman with 9e96310) 
>

Did you unplug/replug the USB cable from the desktop?  When first enabling 
this with the cable plugged in, it seems to require a re-plug to get DHCP 
to issue an IP.  But I suppose your dhclient request from the desktop side 
should have triggered this.
 

> (systemd: 215 debian jessie) 
>
> dnsmasq/create_ap removed 
>
> $(dirname $0)/autoconfigure_usb0.sh disabled... 
>
> bone: 
>
> usb0  Link encap:Ethernet  HWaddr ec:24:b8:d2:06:a0 
>   inet6 addr: fe80::ee24:b8ff:fed2:6a0/64 Scope:Link 
>   UP BROADCAST RUNNING MULTICAST DYNAMIC  MTU:1500  Metric:1 
>   RX packets:6 errors:0 dropped:0 overruns:0 frame:0 
>   TX packets:20 errors:0 dropped:0 overruns:0 carrier:0 
>   collisions:0 txqueuelen:1000 
>   RX bytes:1968 (1.9 KiB)  TX bytes:6180 (6.0 KiB) 
>

Do you see a tether interface (ip addr)?  Attached log has output from ip 
on bone.  And of course, if you have rebooted, you need to enable the 
tether again unless you have setup things for persistent tethering...some 
connman config parameter.
 

>
> root@beaglebone:~# journalctl | grep conn | grep usb0 
> Mar 08 20:22:54 beaglebone connmand[322]: usb0 {create} index 3 type 1 
>  
> Mar 08 20:22:54 beaglebone connmand[322]: usb0 {update} flags 4098  
> Mar 08 20:22:54 beaglebone connmand[322]: usb0 {newlink} index 3 
> address EC:24:B8:D2:06:A0 mtu 1500 
> Mar 08 20:22:54 beaglebone connmand[322]: usb0 {newlink} index 3 
> operstate 2  
> Mar 08 20:22:54 beaglebone connmand[322]: Adding interface usb0 [ gadget ] 
> Mar 08 20:22:54 beaglebone connmand[322]: usb0 {update} flags 102467 
>  
> Mar 08 20:22:54 beaglebone connmand[322]: usb0 {newlink} index 3 
> address EC:24:B8:D2:06:A0 mtu 1500 
> Mar 08 20:22:54 beaglebone connmand[322]: usb0 {newlink} index 3 
> operstate 6  
> Mar 08 20:22:54 beaglebone connmand[322]: usb0 {add} route fe80:: gw 
> :: scope 0  
>
> Hmmm.  That's it?  I have _lots_ more output (see attached file).

Note also, that I have a wired connection on eth0 as well as a powered hub 
with a TP-Link and BT dongle attached.  Not that the TP-Link and BT dongle 
matter.  But I am wondering about eth0.
 

>
> root@beaglebone:~# cat /var/lib/connman/settings 
> [global] 
> OfflineMode=false 
>
> [Wired] 
> Enable=true 
> Tethering=false 
>
> [Gadget] 
> Enable=true 
> Tethering=true 
>
>
Pretty much same as mine.

FWIW, I also have /etc/connman/main.conf:

# Place this file in /etc/connman/main.conf

[General]

# Don't manage mesh point interfaces of the form "mpx"...
NetworkInterfaceBlacklist=mp

# Ordered list of preferred technologies to connect to.
PreferredTechnologies=ethernet,wifi
 

> Desktop: 
>
>
> enxec24b8d206af: flags=4163  mtu 1500 
> ether ec:24:b8:d2:06:af  txqueuelen 1000  (Ethernet) 
> RX packets 20  bytes 5020 (4.9 KiB) 
> RX errors 0  dropped 0  overruns 0  frame 0 
> TX packets 7  bytes 2702 (2.6 KiB) 
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0 
>
> sudo dhclient enxec24b8d206af not getting an ip... 
>

Didn't have to do that.  Well, maybe that would have negated the need to 
re-plug the cable.  I have an IP on the host side:

brian_anderson@htc-thinkpad1 ~ $ ip a
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default 
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host 
   valid_lft forever preferred_lft forever
2: eth0:  mtu 1500 qdisc pfifo_fast 
state DOWN group default qlen 1000
link/ether 54:ee:75:31:34:94 brd ff:ff:ff:ff:ff:ff
inet6 fe80::56ee:75ff:fe31:3494/64 scope link 
   valid_lft forever preferred_lft forever
4: wlan0:  mtu 1500 qdisc mq state DOWN 
group default qlen 1000
link/ether e8:b1:fc:46:1d:ba brd ff:ff:ff:ff:ff:ff
inet6 fe80::eab1:fcff:fe46:1dba/64 scope link 
   valid_lft forever preferred_lft forever
39: eth1:  mtu 1500 qdisc pfifo_fast state 
UNKNOWN group default qlen 1000
link/ether d0:5f:b8:fd:1e:d6 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.2/24 brd 192.168.0.255 scope global eth1
   valid_lft forever preferred_lft forever
inet6 fe80::d25f:b8ff:fefd:1ed6/64 scope link 
   valid_lft forever preferred_lft forever
 

I attached a log.txt file with a bunch of details.

ba

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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.
Bone
===

debian@htc-bbb4:~/Data/projects/connman$ cat /etc/dogtag
BeagleBoard.org Debian Image 2016-02-21

debian@htc-bbb4:~/Data/projects/connman$ uname -r
4.1.18-ti-rt-r51

debian@htc-bbb4:~/Data/projects/connman$ ls -l /etc/network
tota

[beagleboard] Using Connman for WiFi AP/tether...

[Brian Anderson]

I wanted to document some steps that I took to get Connman working for 
setting up a WiFI AP.  Connman terminology for this is "tethering".  All of 
this was done on a recent (Feb2016) Debian Jessie distro with the 4.1.x TI 
kernel.

1.  There is an issue with the systemd connman.service unit file.  Connman 
needs to be able to dynamically load kernel modules in order for tethering 
to work.  The systemd unit file lacks the CAP_SYS_MODULE capability in the 
CapabilityBoundingSet property.  The proper setting should be:

CapabilityBoundingSet=CAP_KILL CAP_NET_ADMIN CAP_NET_BIND_SERVICE 
CAP_NET_RAW CAP_SYS_TIME CAP_SYS_MODULE

I first attempted to add a systemd drop-in to merge this into the distros 
connman.service, but alas, also ran into systemd issue 1221 
(https://github.com/systemd/systemd/issues/1221).  Apparently this systemd 
issue was fixed after release 226.  Currently, RCN Debian images run 
systemd 215.  So, you will have to directly modify 
/lib/systemd/system/connman.service to correct this capability deficiency.

I have posted a bug report to the Connman mail list, and a patch has been 
committed to Connman mainline to fix this missing capability (commit 
9e96310).

2.  Stop and disable dnsmasq service.  dnsmasq is being used for DHCP on 
the usb gadget.  dnsmasq apparently conflicts with Connman's internal DHCP.

3.  I renamed /etc/dnsmasq.d/usb0-dhcp to /etc/dnsmasq.d/usb0-dhcp~ to 
disable boot time setup being performed by 
/opt/scripts/boot/autoconfigure_usb0.sh

4.  I renamed /etc/network/interfaces to /etc/network/interfaces.org to 
avoid any conflicts and confusion between Connman and legacy ifup/ifdown 
and test that Connman can truely deal with all network setup without having 
to resort to any legacy tools.

After these fixes, I can now successfully setup a WiFI AP using 
`connmanctl`.  Traffic on the AP will have internet traffic routed to the 
ethernet interface.  Client STAs connected to the AP will have DHCP 
allocated IP addresses (typically on the 192.168.0.1/24 network).

connmanctl enable wifi
connmanctl tether wifi on  

Note that I can also setup a usb gadget tether using similar `connmanctl` 
commands:

connmanctl enable gadget
connmanctl tether gadget on

A client connected to the usb gadget will also have a DHCP allocated IP 
address (again typically on the 192.168.0.1/24 network).  You may need to 
re-plug the USB cable in order to have an IP address allocated after you 
turn on the tether.

So, all of this avoids the `create_ap` hackery and the necessity to run 
dnsmasq for the usb ethernet gadget.  Unfortunately, I see no way to use 
this method to allocate a static IP address on the usb gadget.  Reading the 
Connman mail list, I doubt defining a static IP for the usb gadget would 
ever be supported as in general there is no way to guarantee that wouldn't 
be a conflict with the static IP...or at least that's the way I read the 
discussion.  But, the BBB _does_ show up via mDNS on the client (in this 
case, my Linux laptop).  Both the BBB web site and the "workstation" show 
up via Avahi Discovery browser.  And I can ssh to the BBB via 
.local.  So, maybe we don't necessarily need a static IP to 
supporting "connecting" to the BBB from usb clients?

This all seems to be encouraging as a possible path to addressing the 
"requirements" that JasonK enumerated in this thread: 
https://groups.google.com/forum/#!category-topic/beagleboard/v4_A2x1I5gs

ba

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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: [beagle-alpha] debian jessie: device-tree-compiler: upgrade for v4.1.x+ kernel's..

[Brian Adams]

We've moved to the 4.1.x kernels in our products so it seems we are largely
unaffected.  Thanks for the clarification.
On Feb 24, 2016 7:13 AM, "Robert Nelson"  wrote:

> On Wed, Feb 24, 2016 at 9:04 AM, Brian Adams  wrote:
> > Robert,
> >
> > When you say it will break building external dtd on target, does that
> imply
> > that dtd building will need to be done during image builds?  Not sure
> what
> > was meant by that sentence.
>
> Hi Brian,
>
> So right now, we have 2 versions of dtc installed by default..
>
> The current package "device-tree-compiler" -> /usr/bin/dtc
>
> Which only works for 3.8.x based kernel overlay's..  (these *.dtbo
> overlays will not load on v4.1.x+ based kernel's due to internal
> overlay changes)..
>
> For v4.1.x kernel's we ship a patched dtc at /usr/local/bin/dtc
>
> Which only works on 4.1.x+ kernel's (they won't load on 3.8.x kernel's)
>
> What i want to do, is essentially, remove the old dtc and ship only
> the 4.1.x-dtc as "/usr/bin/dtc"
>
> and then package the "bb.org-overlays".
>
> This only affects users who build a custom *.dtbo on target, there's
> nothing stopping you from building on an external machine and copying
> over, or using this script:
>
> https://github.com/RobertCNelson/tools/blob/master/pkgs/dtc.sh
>
> to add back the "3.8.x-dtc"...
>
> Regards,
>
> --
> Robert Nelson
> https://rcn-ee.com/
>
> --
> You received this message because you are subscribed to the Google Groups
> "Beagle Alpha" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagle-alpha+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

[beagleboard] Re: [beagle-alpha] debian jessie: device-tree-compiler: upgrade for v4.1.x+ kernel's..

[Brian Adams]

Robert,

When you say it will break building external dtd on target, does that imply
that dtd building will need to be done during image builds?  Not sure what
was meant by that sentence.

Thanks,
Brian
On Feb 23, 2016 5:51 PM, "Robert Nelson"  wrote:

> I think it's time we say good bye to that old 3.8.x based kernel, it's
> served thing well.. (for jessie+)
>
> What i'm planning to do, push a "device-tree-compiler" package update,
> which will break "3.8.x dtbo's" * (and therefore support v4.1.x+)  For
> building "external" *.dtbo's on target...
>
> 3.8.13 users on jessie can still use:
> https://github.com/RobertCNelson/tools/blob/master/pkgs/dtc.sh  to get
> the "dtc compiler for 3.8.x"..
>
> This is the first step in packaging the "bb.org-overlays" repo, and
> allow "console" users a small base image and get the v4.1.x overlay
> *.dtbo's..
>
> Any last minute thoughts?
>
> * wheezy/trusty users WILL NOT be affected, that will support 3.8.13
> till the end of time.  Only jessie+ (and therefore xenial)
>
> Regards
>
> --
> Robert Nelson
> https://rcn-ee.com/
>
> --
> You received this message because you are subscribed to the Google Groups
> "Beagle Alpha" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagle-alpha+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] How to set WIFI in Debian?

[Brian Anderson]

Jason, this is excellent!  Having something along the lines of what you 
call out here out of the box would be great, especially if it was very 
clear how to "configure" said setup w/o having to resort to "legacy" (e.g. 
ifup/down/config) tools.

This would also be especially useful with future/planned boards that have 
builtin WiFi and/or BT.  And as a stretch, maybe even an iOS/Android 
companion app to help with setup/onboarding.  I understand that the BBB is 
supposed to be an embedded systems "learning" platform, so maybe having 
something so consumer friendly is asking a lot.  Even so, there seems to be 
an inordinate number of issues posted here concerning initial networking 
setup, so maybe something like this isn't so far off track as many people 
struggle with this.  Addressing the whole "onboarding" issue is also a huge 
deal for anyone considering what it takes to make a consumer friendly 
device.  A reference implementation would be a great learning experience.  
There are not a lot (maybe no) open source solutions to this problem.  I do 
know that the AllJoyn folks have defined an OnBoarding service spec to help 
address this, but there isn't much as far as implementation here yet.  
There may be other efforts (OIC?), but I am unaware of them.

Good thoughts!

ba

On Wednesday, February 17, 2016 at 8:39:24 AM UTC-8, Jason Kridner wrote:
>
> Perhaps we need to fully define the requirement such that experts can 
> provide the lowest memory and least complex solution?
>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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] How to set WIFI in Debian?

[Brian Anderson]

>> nah use connman, i have it installed by default on jessie images. ;) 
>>
>> ~$ sudo connmanctl 
>> connmanctl> enable wifi 
>>
>
> If connected to BeagleBone with it acting as an access point (AP), this 
> seems to result in immediately losing connection. Is there a way to keep 
> the AP active?
>

Ya.  I don't think connman plays well with create_ap.  You can probably 
work around this by telling connman to not manage wlan0 by placing 
something like the following in /etc/connman/main.conf

NetworkInterfaceBlacklist=wlan

This will prevent connman from attempting to manage _any_ wlan interface.  
But of course, you won't later be able to use connman with that interface 
to connect as a STA.

It seems to be a point of confusion about how to setup and manage 
persistent settings for networking.  People often are tripped up by the 
fact that connman may be interfering with their attempts to make changes 
using /etc/network/interfaces and friends.  It would be great if we could 
come up with ways to prevent this confusion.

I do know that connman will setup an AP (called tethering).  Unfortunately, 
the only way I could get this to work was by stopping dnsmasq.  For some 
reason, dnsmasq was preventing connman for establishing the AP...my guess 
is that connman wants to do DHCP and conflicts with dnsmasq.

I wonder if it would be possible to have connman manage the USB link and 
thus avoid all the hackery in /etc/network/interfaces and dnsmasq?

Alternatively, I wonder if network manager might be a better all around 
choice for one stop shopping for network management in lieu of connman?  I 
don't have any personal experience, but others (DeKay) have supposedly had 
luck using nm.



 

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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] UART1 using BB-UART1 vs cape-universal

[Brian Anderson]

OK, thanks Robert. I'll try an updated kernel and see what happens. 


Issue fixed on 4.1.17-ti-rt-r46.  Thanks!
 

> Curious, what was the issue and why didn't it manifest itself with the 
> different settings in cape-universal?
>
> Still interested in why the pull-up/pull-down values are different in 
> cape-universal vs BB-UART.
>
> ba
>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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] Use GPIO as non-root user?

[Brian Anderson]

My comments are really to do with what I perceive as best practices on how 
one would approach building systems that are "security conscious".  Of 
course, "convenience" may direct us in different directions during 
development.  I am not sure what you are trying to imply by "safe" as in 
protecting the GPIOs from misuse.  I don't actually see any way to 
accomplish that.  What I do think one can do is to be aware of security 
considerations and not unnecessarily present an attack surface that can 
compromise the entire system.


*Using sudo seems much less secure as it exposes the application to being 
>> exploited for security flaws. And since the application is running as root, 
>> it has access to everything.*
>>
>
> So, we have a device on a system that can potentially cause physical 
> damage to external hardware when something like a wrong GPIO state is 
> toggled, or such. How would sudo be less secure in this context?
>

It wouldn't.  And that is not my point.  I am not talking about how to 
protect the GPIOs from "bad behaved" programs that are "trusted" as implied 
by the fact that they are running as a normal user in the group that has 
access to those GPIOs.  If an application is trusted (is a member of the 
appropriate group or for that matter can sudo), it is a hopeless task to 
protect the GPIOs from misuse.  What I am trying to point out is that 
running an app as "root" (sudo, set uid, whatever) exposes a security 
attack vector...a vector that has access to _all_ system resources.  I 
would claim that it is an unnecessary exposure...from a security point of 
view.  YMMV when it comes to "convenience".
 

> In fact under certain conditions it would be less safe using groups.
>

How would an application running at a non-root level using groups to access 
protected resources be less "safe" than an application running as root 
using sudo?
 

>
> Also, "root has access to everything" is wrong. Reread what I've written 
> above about running specific commands through sudo.
>

Errr, an application running as root, by definition, has access to _all_ 
system resources.  The fact that you are limiting just a single 
application/user to run sudo doesn't limit the attack surface for that 
application.  If your root application is compromised in some way, then the 
entire system can be compromised.  Running as a normal user does not 
present the same attack surface...its much smaller and sandboxed by the 
kernel.  Running as root affords no protection enforcement by the kernel.

ba
 

>
> On Fri, Feb 5, 2016 at 6:05 PM, Brian Anderson  > wrote:
>
>> Err, why?
>>
>> Groups are frequently used to restrict access to resources. Android 
>> exploits groups for permissions and to sandbox applications.  And the 
>> kernel enforces access.
>>
>> Using sudo seems much less secure as it exposes the application to being 
>> exploited for security flaws. And since the application is running as root, 
>> it has access to everything.
>>
>> But maybe I'm missing something?
>>
>> ba
>>
>> --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you 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] Use GPIO as non-root user?

[Brian Anderson]

Err, why?

Groups are frequently used to restrict access to resources. Android exploits 
groups for permissions and to sandbox applications.  And the kernel enforces 
access.

Using sudo seems much less secure as it exposes the application to being 
exploited for security flaws. And since the application is running as root, it 
has access to everything.

But maybe I'm missing something?

ba

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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] UART1 using BB-UART1 vs cape-universal

[Brian Anderson]

OK, thanks Robert. I'll try an updated kernel and see what happens. Curious, 
what was the issue and why didn't it manifest itself with the different 
settings in cape-universal?

Still interested in why the pull-up/pull-down values are different in 
cape-universal vs BB-UART.

ba

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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] UART1 using BB-UART1 vs cape-universal

[Brian Anderson]

I have a sensor hooked up to UART1.  This seems to work just fine using 
cape-universal and config-pin to setup P9-24 and P9-26 in uart mode.

When I modify uEnv.txt to use BB-UART1 overlay, I am unable to read data 
from the sensor.

Relevant portions of uEnv.txt looks like this:

# Don't enable cape-universal
cmdline=coherent_pool=1M quiet

# Enable UART1 and I2C1 overlays
cape_enable=bone_capemgr.enable_partno=BB-I2C1,BB-UART1

And I have commented out the original cmdline:

#cmdline=coherent_pool=1M quiet cape_universal=enable

Slots look like this:

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

Kernel and rootfs:

debian@bbb2:~$ uname -r
4.1.16-ti-rt-r44
debian@bbb2:~$ cat /etc/dogtag
BeagleBoard.org Debian Image 2016-01-17

I have also pulled the latest bb.org-overlays and run install.sh.

I have this working on another system with 4.1.13-ti-r35 with the 
2015-11-09 rootfs.  If I am correct in analyzing the BB-UART1 dtb that is 
working on this system, it appears as if P9_24 is configured with a 
pulldown resistor and P9_26 is configured with a pullup resistor.  The 
BB-UART1 dtb on the system where this is not work (and the current version 
from bb.org-overlays) has no pullup/pulldown resistors configured for those 
pins.  Looking at cape-universal (that works), it appears as if P9_24 and 
P9_26 are both configured with pullups.

So, I'm assuming that this is why my current BB-UART1 setup is not working.

Is the configuration of the current BB-UART1 (actually all of them) without 
pullup/pulldown for UART mode by design?  If so, why?  And of course, the 
converse question for cape-universal.

Not being a H/W guy, maybe someone can inform me as to why my current 
BB-UART1 doesn't work and why these dtb's are thusly configured.

ba

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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: 802.11s mesh networking with Beaglebone Black

[Brian Anderson]

Just so it's understood. You do not need to install a new rootfs image in 
> order to install, and use a newer kernel. In other words, I'm personally 
> using Wheezy 7.8, and a 4.1.x kernel.
>

Of course.  Just thinking that if there wasn't any other reason to stay on 
Wheezy, it would be a good thing to upgrade to a recent Jessie image and 
get support for the latest tools that are available there (e.g. iw, ip).  
Latest versions of these tools are unlikely to have been backported to 
Wheezy.  I do know that older versions of iw did not properly support mesh 
points.

One other thing, if your image is running connman, you will want to make 
sure it doesn't interfere (try to manage) any interfaces you create.  I 
typically create my mesh points on "mp0", so I have a 
/etc/connman/main.conf something like the following to ensure that connman 
ignores mp0 (actually ignores any mpX interface):

# Place this file in /etc/connman/main.conf

[General]

# Don't manage mesh point interfaces of the form "mpx"...
NetworkInterfaceBlacklist=mp

ba


-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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: 802.11s mesh networking with Beaglebone Black

[Brian Anderson]

I believe that the problem is that your kernel's ath9k driver does not 
include complete support 802.11s.  Later kernels do support the required 
driver functionality.  You can see this from the iw output in that "mesh 
point" is not a supported interface mode:

Supported interface modes:
>  * IBSS
>  * managed
>  * AP
>  * AP/VLAN
>  * monitor
>  * P2P-client
>  * P2P-GO
>

Note the abscense of "mesh point" in this output.

Here is the output from my system (/etc/dogtag: BeagleBoard.org Debian 
Image 2016-01-17; uname -r: 4.1.15-ti-rt-r41)

Supported interface modes:
 * IBSS
 * managed
 * AP
 * AP/VLAN
 * monitor
 * mesh point
 * P2P-client
 * P2P-GO


I would highly recommend updating to a recent Debian 8.x image and a 4.1.x 
kernel.  IIRC, anything older than 3.19 didn't work too well with mesh 
mode.  I have not tried with 4.1.x but I would expect that it should work 
fine.

ba
debian@bbb2:~$ 
ba 

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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] uSD/eMMC not mounting when booting from eMMC/uSD

[Brian Anderson]

> With lxqt, i have this disabled by default: 
>
>
> https://github.com/rcn-ee/repos/blob/master/pcmanfm-qt/suite/jessie/debian/patches/desktop-defaults.patch#L20
>  
>
> Look at these values; 
>
> [Volume] 
> AutoRun=true 
> CloseOnUnmount=false 
> MountOnStartup=false 
> MountRemovable=false 
>
> /home/${USER}/.config/pcmanfm-qt/lxqt/settings.conf 
>  
>

Got it.  Thanks.

FWIW, it threw me a bit when the volume label of the eMMC (as flashed by 
the flasher image) showed as "BOOT".  I first thought that this was the old 
boot partition, but it's really rootfs.  The normal image (on the uSD) 
shows as "rootfs".

debian@beaglebone:~$ sudo blkid
/dev/mmcblk0p1: LABEL="rootfs" UUID="cf6fe36e-7116-41eb-849f-d6c5e41cc387" 
TYPE="ext4"
/dev/mmcblk1p1: LABEL="BOOT" UUID="d3ea6827-343b-48e2-ac60-b925be97d3b9" 
TYPE="ext4"
/dev/mmcblk0: PTTYPE="dos"
/dev/mmcblk1: PTTYPE="dos"
debian@beaglebone:~$ lsblk
NAME MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
mmcblk1boot0 179:16   02M  1 disk 
mmcblk1boot1 179:24   02M  1 disk 
mmcblk0  179:00 29.7G  0 disk 
`-mmcblk0p1  179:10 29.7G  0 part /
mmcblk1  179:80  3.6G  0 disk 
`-mmcblk1p1  179:90  3.6G  0 part /media/debian/BOOT

 

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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] uSD/eMMC not mounting when booting from eMMC/uSD

[Brian Anderson]

I just grabbed the 2015-12-07 image and flasher image and placed them on 
separate uSD cards.  I used the flasher image to flash the eMMC.  Board 
boots fine.

I then inserted the uSD card with the normal image.  Apparently, it doesn't 
automagically mount anymore.  I see in ``dmesg that the system sees the new 
device:

[  598.137586] mmc0: new high speed SDHC card at address 
[  598.150733] mmcblk1: mmc0: SE32G 29.7 GiB 
[  598.161203]  mmcblk1: p1

`lsblk` can see the uSD card:

debian@beaglebone:~$ lsblk
NAME MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
mmcblk0boot0 179:802M  1 disk 
mmcblk0boot1 179:16   02M  1 disk 
mmcblk0  179:00  3.6G  0 disk 
└─mmcblk0p1  179:10  3.6G  0 part /
mmcblk1  179:24   0 29.7G  0 disk 
└─mmcblk1p1  179:25   0 29.7G  0 part 

But, no mountie...

debian@beaglebone:~$ df -h
Filesystem  Size  Used Avail Use% Mounted on
udev 10M 0   10M   0% /dev
tmpfs98M  8.4M   90M   9% /run
/dev/mmcblk0p1  3.5G  2.8G  595M  83% /
tmpfs   245M  4.0K  245M   1% /dev/shm
tmpfs   5.0M  4.0K  5.0M   1% /run/lock
tmpfs   245M 0  245M   0% /sys/fs/cgroup
tmpfs49M 0   49M   0% /run/user/1000

Note that I can mount the uSD by hand thusly:

debian@beaglebone:~$ sudo mount /dev/mmcblk1p1 temp
debian@beaglebone:~$ df -h
Filesystem  Size  Used Avail Use% Mounted on
udev 10M 0   10M   0% /dev
tmpfs98M  8.4M   90M   9% /run
/dev/mmcblk0p1  3.5G  2.8G  595M  83% /
tmpfs   245M  4.0K  245M   1% /dev/shm
tmpfs   5.0M  4.0K  5.0M   1% /run/lock
tmpfs   245M 0  245M   0% /sys/fs/cgroup
tmpfs49M 0   49M   0% /run/user/1000
/dev/mmcblk1p1   30G  2.7G   25G  10% /home/debian/temp
debian@beaglebone:~$ ls temp
bbb-uEnv.txt  dev   ID.txt  media opt   run   sys  var
bin   etc   lib mnt   proc  sbin  tmp
boot  home  lost+found  nfs-uEnv.txt  root  srv   usr
debian@beaglebone:~$ 

I can repeat this same sequence by rebooting from the uSD card and the same 
happens w.r.t. eMMC.

On another system, (BeagleBoard.org Debian Image 2015-11-01, 
4.1.13-ti-r35), I am apparently getting the same behavior.

I seem to remember that automagical mounting of the uSD/eMMC used to 
happen.  Maybe this was explicitly removed to avoid confusion?  Or is this 
something that bit-rotted?

ba


-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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: Issue with UART1 and UART2...

[Brian Anderson]

Good point.  Downgraded to r33 and indeed UART1 and 2 (and 4) work just 
fine!  So, this is an issue with r34.

On Monday, November 30, 2015 at 3:13:44 PM UTC-8, Lee Armstrong wrote:
>
> Does this happen with r33? 

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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] Issue with UART1 and UART2...

[Brian Anderson]

I'm having an issue trying to use UART1 and UART2.  I can get UART4 to work 
fine.

cat /etc/dogtag
BeagleBoard.org Debian Image 2015-11-01
uname -r
4.1.13-ti-r34

I've disabled cape-universal and enabled the UARTs in uEnv.txt:

cmdline=coherent_pool=1M quiet
cape_enable=bone_capemgr.enable_partno=BB-UART1,BB-UART2,BB-UART4

I can see the loaded capes:

 0: PF  -1 
 1: PF  -1 
 2: PF  -1 
 3: PF  -1 
 4: P-O-L-   0 Override Board Name,00A0,Override Manuf,BB-UART1
 5: P-O-L-   1 Override Board Name,00A0,Override Manuf,BB-UART2
 6: P-O-L-   2 Override Board Name,00A0,Override Manuf,BB-UART4

Symptom is (e.g.)  `stty -F /dev/ttyS2 -a' prints info but then hangs for a 
number of seconds and finally seems to timeout and I get the bash prompt 
again (no error message).  Trying to echo something (e.g. echo 'hello 
world' >/dev/ttyS2) also hangs with no output but eventually appears to 
timeout (with no output).  I have seen.

These same things seem to work fine for /dev/ttyS4.

I have a FTDI cable hooked up to the RX/TX pins on the BBB UART.  Using 
screen on the host side (a Mac) to display serial data.

FWIW:

dmesg|grep tty
[0.00] Kernel command line: console=ttyO0,115200n8 
bone_capemgr.enable_partno=BB-UART1,BB-UART2,BB-UART4 
root=UUID=afd9b951-1277-4c59-9ea3-46a1824b7a46 ro rootfstype=ext4 rootwait 
fixrtc coherent_pool=1M quiet
[0.000458] WARNING: Your 'console=ttyO0' has been replaced by 'ttyS0'
[3.375973] 44e09000.serial: ttyS0 at MMIO 0x44e09000 (irq = 155, 
base_baud = 300) is a 8250
[3.383668] console [ttyS0] enabled
[4.091115] 48022000.serial: ttyS1 at MMIO 0x48022000 (irq = 192, 
base_baud = 300) is a 8250
[4.101751] 48024000.serial: ttyS2 at MMIO 0x48024000 (irq = 193, 
base_baud = 300) is a 8250
[4.102859] 481a8000.serial: ttyS4 at MMIO 0x481a8000 (irq = 194, 
base_baud = 300) is a 8250

I have also tried all of this using cape-universal and config-pin and 
manually enabling UART mode on the appropriate pins.  Same symptoms 
including a working /dev/ttyS4.

What am I missing?

Cheers,

ba

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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 doesn't sometimes start. Only Power LED is on

[Brian Adams]

We are building our images using the omap-image-builder scripts.  Looks 
like everything is current (u_boot_release="v2015.10-rc3") yet we are still 
experiencing a 4.5% boot failure rate where we have a single power light 
and no other leds lit. Do I understand correctly that the uboot software 
fix that checks for any key press essentially reduces the failure rate 
because the random noise on the uart would have to be in the range of a 
real key-code to stop the boot sequence? And if that is right, that while 
reduced, there is still a range of noise that can abort the boot sequence?

On Tuesday, August 11, 2015 at 7:13:14 AM UTC-7, RobertCNelson wrote:
>
> On Mon, Aug 10, 2015 at 10:18 PM,  > wrote: 
> > Hi, 
> > 
> > Robert, in place of 2015-07-17 image, I see 2015-07-28 image. In any 
> way, 
> > how it is fixed? 
>
> Just weekly build snapshots, look at the log for major changes: 
>
> https://github.com/RobertCNelson/omap-image-builder/commits/master 
>
> >I just tried to flash it to my BBB and I still can go into 
> > u-boot pressing any single key. Shouldn't it be some key sequence like 
> > "uboot"? 
>
> It's just a single key over the usart... 
>
> If it's not working, you more then likely have a version in eMMC not from 
> me 
>
> 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] What's the plan for a Debian distro with a recent version of node.js?

[Brian Adams]

Anyone know the plans for moving to a more recent release of node.js with 
the next Debian release?  Or where to find that information?

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

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

[Brian Cooke]

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

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

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

Re: [beagleboard] Building Debian to eMMC

[Brian Adams]

Follow up a year later.  What's the fastest ARMv7 system that folks are 
using for things like generating the images? Anyone tried compiling images 
with the Jetson TK1 or Odroid XU4?  

On Sunday, July 27, 2014 at 7:22:17 AM UTC-7, RobertCNelson wrote:
>
>
> On Jul 27, 2014 9:09 AM, "Jetty" > wrote:
> >
> > I'm attempting to build linux from source and create an eMMC flasher 
> image.  I have Ubuntu 14.04.01 32 bit installed and have got to the point 
> where I'm trying to
> > create the flasher. 
> >
> > The process hangs with qemu, and it says here:
> >
> > 
> http://www.elinux.org/Beagleboard:BeagleBoneBlack_Rebuilding_Software_Image
> >
> > "You'll want a fairly beefy ARM system to run this script."
> >
> > I guess that isn't the BBB.  What system does Robert use to build the 
> flasher?
>
> It will run on the BBB, just needs around 4gb free of space. For official 
> images I use one of my quad core cortex a9, 2gb, data boards.
>
> Regards,
>
> >
> > -- 
> > For more options, visit http://beagleboard.org/discuss
> > --- 
> > You received this message because you are subscribed to the Google 
> Groups "BeagleBoard" group.
> > To unsubscribe from this group and stop receiving emails from it, send 
> an email to beagleboard...@googlegroups.com .
> > For more options, visit https://groups.google.com/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] PMW on P8.13 and P8.19 on Debian 8.1 / Linux 4.1.2-ti-r4

[Brian Cooke]

The goal is to update a tool called bot-io  
to function with the 4.1 kernel. Among other things, bot-io allows pins to 
be configured to use drivers that beaglebone-universal-io doesn't support 
like gpio-keys and gpio-leds, so beaglebone-universal-io can't be 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.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] PMW on P8.13 and P8.19 on Debian 8.1 / Linux 4.1.2-ti-r4

[Brian Cooke]

On a BeagleBone Black running Debian 8.1 / Linux 4.1.2-ti-r4 
, I'd like 
to be able to enable PWM on P8.13 and P8.19 using two different device tree 
overlays rather that a single overlay.

The two overlays currently being used are show below. If the first overlay 
for P8.13 is used, it will work correctly. If the second overlay for P8.19 
is used, it will also work correctly. However, if both overlays are used at 
the same time, only the first one activated will work correctly. The second 
one will fail to function. I'd imagine the problem is related to fragment@2 
in the overlays, but I can't figure out what needs to be done to make it 
function correctly. Any help in figuring out how to solve the issue would 
be greatly appreciated.

*Overlay for PWM on P8.13*

/dts-v1/;
/plugin/;

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

  exclusive-use =
"P8.13",
"ehrpwm2B";

  fragment@0 {
target = <&am33xx_pinmux>;
__overlay__ {
  bot_pwm_p8_13_pins: pinmux_bot_pwm_p8_13_pins {
pinctrl-single,pins = <
  0x024 0x4
>;
  };
};
  };

  fragment@1 {
target = <&epwmss2>;
__overlay__ {
  status = "okay";
};
  };

  fragment@2 {
target = <&ehrpwm2>;
__overlay__ {
  pinctrl-names = "default";
  pinctrl-0 = <&bot_pwm_p8_13_pins>;
  status = "okay";
};
  };
};

*Overlay for PWM onP8.19*

/dts-v1/;
/plugin/;

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

  exclusive-use =
"P8.19",
"ehrpwm2A";

  fragment@0 {
target = <&am33xx_pinmux>;
__overlay__ {
  bot_pwm_p8_19_pins: pinmux_bot_pwm_p8_19_pins {
pinctrl-single,pins = <
  0x020 0x4
>;
  };
};
  };

  fragment@1 {
target = <&epwmss2>;
__overlay__ {
  status = "okay";
};
  };

  fragment@2 {
target = <&ehrpwm2>;
__overlay__ {
  pinctrl-names = "default";
  pinctrl-0 = <&bot_pwm_p8_19_pins>;
  status = "okay";
};
  };
};


-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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 : Using Systemd service to make wireless stable is not working as expected

[Brian Anderson]

Connman is installed in the latest Debian Jessie full testing images. It works 
fine for me for managing WiFi.  I can't say whether Connman is installed in the 
console images as I have not used them.  I posted some additional information 
in this thread: 
https://groups.google.com/forum/m/#!category-topic/beagleboard/rRHUR8mltmg

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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: Having to manually start Wifi

[Brian Anderson]

Since you are using Jessie images, have you tried using ConnMan to manage 
the WiFi connection rather than resorting to all of this systemd and 
ifup/ifdown stuff?

You can configure ConnMan using the "connmanctl" command line utility, or 
via the "cmst" GUI utility. to setup your link (ssid, credentials).  Or, 
you can create a config file and put it in 
/var/lib/connman/my_config.config.  There is documentation in the ConnMan 
source tree on this format.  I've also attached a template for reference.  
You might also consider adding '/etc/connman/main.conf' and specify 
PreferredTechnologies in the order that you want.  Again, there is 
documentation in the ConnMan source tree on this file, and also the Google 
will help.

Note that if you use this method, you should NOT do any wifi configuration 
in /etc/network/interfaces as ConnMan will override these.  If you would 
rather use /etc/network/interfaces, then be careful that you don't also 
have conflicting configuration setup with ConnMan, as ConnMan will override 
configuration in /etc/network/interfaces.

I use the ConnMan method all the time for my work and have no problem 
getting a WiFi connection after boot using my TP-Link TL-WN-722N (uses an 
Atheros chipset), Jessie snapshot images, and 3.19.x kernels.

ba

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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.


connman-example.config
Description: Binary data

Re: [beagleboard] External BBB Power LED

[Brian Lloyd]

On Sat, Mar 7, 2015 at 12:52 PM, Brian Lloyd  wrote:

>
>
> On Sat, Mar 7, 2015 at 12:48 PM, Walker Archer 
> wrote:
>
>> I have a project where a BeagleBone Black will be completely inside a
>> case.  But I would really like to be sure that the board gets powered down
>> properly when shutting down.  Ideally I'd like to have a panel-mounted LED
>> that mimicked the BBB power LED.
>>
>
> How about a plastic light-pipe to carry the light from the board-mounted
> LED to the front panel? It is a mechanical solution but pretty simple.
>

Mouser lists over 3500 options for doing this. Go to the Mouser web site
and search on "light pipe".

-- 



Brian Lloyd
706 Flightline Drive
Spring Branch, TX 78070
br...@lloyd.aero
+1.210.802-8FLY (1.210.802-8359)

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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] External BBB Power LED

[Brian Lloyd]

On Sat, Mar 7, 2015 at 12:48 PM, Walker Archer  wrote:

> I have a project where a BeagleBone Black will be completely inside a
> case.  But I would really like to be sure that the board gets powered down
> properly when shutting down.  Ideally I'd like to have a panel-mounted LED
> that mimicked the BBB power LED.
>

How about a plastic light-pipe to carry the light from the board-mounted
LED to the front panel? It is a mechanical solution but pretty simple.

-- 



Brian Lloyd
706 Flightline Drive
Spring Branch, TX 78070
br...@lloyd.aero
+1.210.802-8FLY (1.210.802-8359)

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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] Different Linux images

[Brian Anderson]

> As a secondary, we got a lot of bugs fixed from ti on am335x, that 
> were issues in 3.8 for some users. 
>
> pm/usb/ethernet/etc..   


> Right now there's three variants: 
>
> The first two have been around for awhile: 
>
> linux-image-3.14.33-ti-r51 
>

How does the 3.14.33-ti series kernels compare to 3.19.0-bone3?  Have the 
TI patches in 3.14.33 been upstreamed into later kernels such as 3.19.0?

I have been running on the 3.19.0 series for awhile (Debian Jessie rootfs 
from November and late January).  When I tried the 3.14.xx-ti series back 
in the January time frame the kernel was hanging periodically under heavy 
I/O load (like doing an rsync of the rootfs to a remove host).  I was also 
having issues with the kernel hanging when doing performance testing using 
"iperf3" between 2 BBB's on a wireless network (the iperf "server" host 
would hiccup periodically).  The 3.19.0 series has proved to be more 
stable.  (I have been working with an 802.11s mesh setup using TP-Link 
WN722N in case anyone is interested.)

Should I be going back to the 3.14.33-ti series?  I know "don't fix it if 
it ain't broke", but just wondering about the details of 3.14.33-ti versus 
later kernels.

Great work Robert!  Hope to see you at ELC next month.

ba

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

[beagleboard] Re: Static IP on eth0

[Brian Anderson]

Enric,

I think your problem may be related to ConnMan.  ConnMan is a network 
manager that is installed on the Jessie test images.  It manages your 
network connections, including eth.  Any settings you have in 
/etc/network/interfaces is overriden by ConnMan, and thus this is why you 
see a DHCP assigned address rather than the static address configured in 
/etc/network/interfaces when you reboot.

You can disable ConnMan (not recommended), tell ConnMan to not manage eth0 
on your behalf and manage things yourself (again, not recommended), or use 
ConnMan to setup a static IP address.  Using ConnMan to setup a static IP 
address will be "persistent", that is it will survive reboots.  This is 
pretty simple:

First, determine the "service" name of your ethernet:

*connmanctl services*

Using the appropriate ethernet service, tell connman to setup a static IP 
address for that service:

su*do connmanctl config  --ipv4 manual   
 --nameservers *

You will need to pick an IP address compatible with your network and router.

For example:

$ connmanctl services
*AO Wiredethernet_d05fb8ed4f78_cable
$ sudo connmanctl config ethernet_d05fb8ed4f78_cable --ipv4 manual 
10.0.1.100 255.255.255.0 10.0.1.1 --nameservers 8.8.8.8

You should then see the new address using the "ip" command:

$ ip addr show dev eth0
2: eth0:  mtu 1500 qdisc 
pfifo_fast state UP group default qlen 1000
link/ether d0:5f:b8:ed:4f:78 brd ff:ff:ff:ff:ff:ff
inet 10.0.1.100/24 brd 10.0.1.255 scope global eth0
   valid_lft forever preferred_lft forever
inet6 fe80::d25f:b8ff:feed:4f78/64 scope link 
   valid_lft forever preferred_lft forever

You should now also be able to "ping" an address such as "google.com".

You can revert back to a DHCP configuration simply as follows:

$ sudo connmanctl config ethernet_d05fb8ed4f78_cable --ipv4 dhcp

It would be best if you have a FTDI serial cable so you can see what is 
going on at the console in case something goes wrong.  Actually, it would 
be best to issues these commands from the console rather than ssh'ing.

Hope this helps

ba

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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] i2c-bus - A new Node.js I2C module

[Brian Cooke]

There is one more thing:


   - i2c-bus is io.js and Node.js compatible - tested with io.js 1.0.2 on a 
   BeagleBone Black running Ubuntu 14.04.1 LTS (GNU/Linux 3.14.26-ti-r43 
   armv7l)
   

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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: Having problems cloning eMMC

[brian]

So the original BBB does boot fine.  But how can I re-install bootloader 
for BBB2?  But it is my understanding, the bootloader is what is in the 
Fat32 partition?  It looks the same as the other one.  

total 9820

drwxr-xr-x 2 root root2048 Apr 23 16:22 App
   
-rwxr-xr-x 1 root root 223 Apr 23 16:22 autorun.inf
   
drwxr-xr-x 2 root root2048 Apr 23 20:21 debug
 
drwxr-xr-x 4 root root4096 Apr 23 16:22 Docs
  
drwxr-xr-x 5 root root2048 Apr 23 16:22 Drivers
   
drwxr-xr-x 2 root root2048 Apr 23 16:22 dtbs
  
-rwxr-xr-x 1 root root  51 Apr 23 16:22 ID.txt

-rwxr-xr-x 1 root root 286 Apr 23 20:20 initrd.img

-rwxr-xr-x 1 root root   41174 Apr 23 16:22 LICENSE.txt
   
-rwxr-xr-x 1 root root   81264 Apr 23 20:22 MLO
   
-rwxr-xr-x 1 root root   16822 Apr 23 16:22 README.htm

-rwxr-xr-x 1 root root 292 Apr 23 16:22 README.md
 
drwxr-xr-x 2 root root2048 Apr 23 16:22 scripts
   
-rwxr-xr-x 1 root root 313 Apr 23 16:22 SOC.sh

-rwxr-xr-x 1 root root   16822 Apr 23 16:22 START.htm
 
drwxr-xr-x 2 root root2048 Aug 15  2014 System Volume Information
 
-rwxr-xr-x 1 root root  401800 Apr 23 20:22 u-boot.img

-rwxr-xr-x 1 root root1513 Sep 15  2014 uEnv.txt
  
-rwxr-xr-x 1 root root1514 Aug 21  2014 uEnv.txt~
 
-rwxr-xr-x 1 root root 2870063 Apr 23 20:20 uInitrd
   
-rwxr-xr-x 1 root root 3717760 Apr 23 16:22 zImage
  




On Tuesday, January 20, 2015 at 12:46:40 PM UTC-5, RobertCNelson wrote:
>
> On Tue, Jan 20, 2015 at 11:38 AM,  > 
> wrote: 
> > I'm not sure what you mean by bootloader.  But I just read in entire 
> mmcblk1 
> > (When booting off a SD card to image) on one BBB using dd, and output to 
> > another using dd. 
> > 
> > // BBB 1 
> > dd bs=4M if=/dev/mmcblk1 of=image.bin 
> > 
> > // BBB 2 
> > dd bs=4M if=image.bin of=/dev/mmblk1 
>
> At which point, it's likely your original "/dev/mmcblk1" didn't have 
> the bootloader installed either. 
>
> Regards, 
>
> -- 
> Robert Nelson 
> http://www.rcn-ee.com/ 
>

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

Re: [beagleboard] Re: Having problems cloning eMMC

[brian]

I'm not sure what you mean by bootloader.  But I just read in entire 
mmcblk1 (When booting off a SD card to image) on one BBB using dd, and 
output to another using dd.  

// BBB 1
dd bs=4M if=/dev/mmcblk1 of=image.bin

// BBB 2
dd bs=4M if=image.bin of=/dev/mmblk1

On Tuesday, January 20, 2015 at 12:23:49 PM UTC-5, RobertCNelson wrote:
>
> On Tue, Jan 20, 2015 at 11:19 AM, Brian Wagener  > wrote: 
> > It is not a uSD but internal eMMC. And you can see from fdisk output 
> boot 
> > flag is set. 
>
> and how exactly did you install the bootloader to the eMMC? 
>
> Regards, 
>
> -- 
> Robert Nelson 
> http://www.rcn-ee.com/ 
>

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

Re: [beagleboard] Re: Having problems cloning eMMC

[Brian Wagener]

It is not a uSD but internal eMMC. And you can see from fdisk output boot
flag is set.
On Jan 20, 2015 10:44 AM, "Graham Haddock"  wrote:

> Did you set the "boot" bit on the 8gb flash card?
>
> The later versions of the OS can not see or boot from the uSD card unless
> the "boot" bit is set.
>
> The "CC" string means that the BBB can not see the card, and is trying
> to boot from
> the serial port.
>
> --- Graham
>
> ==
>
> On Tue, Jan 20, 2015 at 8:07 AM,  wrote:
>
>> So I got my 8gb flash, and resized original boards partition to be
>> smaller than second board.  So now the problem is I have flashed new board,
>> and it will not boot up.  I can mount and view both partitions correctly,
>> and everything looks ok, but I only get "CCC" when trying to boot and
>> viewing with FTDI cable.   Any ideas?
>>
>> Disk /dev/mmcblk1: 3867 MB, 3867148288 bytes
>>
>> 4 heads, 16 sectors/track, 118016 cylinders, total 7553024 sectors
>>
>> Units = sectors of 1 * 512 = 512 bytes
>>
>> Sector size (logical/physical): 512 bytes / 512 bytes
>>
>> I/O size (minimum/optimal): 512 bytes / 512 bytes
>>
>> Disk identifier: 0x
>>
>>
>>
>> Device Boot  Start End  Blocks   Id  System
>>
>> /dev/mmcblk1p1   *2048  198655   98304e  W95 FAT16 (
>> LBA)
>>
>> /dev/mmcblk1p2  198656 7571455 3686400   83  Linux
>>
>>
>>
>> On Tuesday, December 2, 2014 at 11:20:13 PM UTC-5, Graham wrote:
>>>
>>> I think you will have two problems.
>>>
>>> First, you can not put a 4GB file on a 4 GB card, because there must
>>> also be room for the
>>> Linux OS, and depending on the version, this can be another 1 GB, or
>>> more.
>>>
>>> Second problem is that when you install a 2 GB image on a 4 GB card, the
>>> partition as
>>> installed is typically about 2 GB, and the rest of the card can not be
>>> used, until you
>>> expand the partition to the full size of the card.
>>>
>>> So, for working with the 4 GB eMMC version of the Beaglebone Black, you
>>> must use
>>> at least an 8 GB card.  I use 16 GB, so that there is room for about
>>> three images
>>> that are not compressed.  You can not go larger than 32 GB at this time.
>>>
>>> --- Graham
>>>
>>> ==
>>>
>>> On Tuesday, December 2, 2014 5:57:16 PM UTC-6, br...@forceconstant.com
>>> wrote:

 So in that other thread, it was instructed to use the same dd command
 "dd if=/dev/mmcblk1 of=/mnt/BeagleBoneBlack-eMMC-image-$RANDOM.img
 bs=10M" to create image, so why would mine only end up 2GB instead of 4GB?
 I cannot follow those instructions exactly, as I only have a 4GB SD card,
 so maybe this is the problem since the eMMC is 4GB also.

 On Tuesday, December 2, 2014 5:22:47 PM UTC-5, janszyma...@gmail.com
 wrote:
>
> there is another thread here *Duplicate BeagleBone black setup*
> 
>  dated
> Nov 28, where you will find a solution to your problem.
> Good luck.
> Jan
>
> On Wednesday, December 3, 2014 6:32:08 AM UTC+11,
> br...@forceconstant.com wrote:
>
>> I am trying to clone an existing BBB, so my first try is using the
>> scripts on http://elinux.org/BeagleBone_
>> Black_Extracting_eMMC_contents .  So first thing I notice is the
>> .img file created was only 2GB, whereas this is a newer BBB that has 4GB
>> eMMC.  So when I updated script to write the img to new BBB, it no longer
>> boots from eMMC.  i would like to make exact copies including uENV.txt,
>> etc.  Does anyone know why this is not working?
>>
>> The read command script is
>>
>> #!/bin/sh
>> echo timer > /sys/class/leds/beaglebone\:green\:usr0/trigger
>> dd if=/dev/mmcblk1 of=/mnt/BeagleBoneBlack-eMMC-image-$RANDOM.img
>> bs=10M
>> sync
>> echo default-on > /sys/class/leds/beaglebone\:green\:usr0/trigge
>>
>  --
>> 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/u12eEHlfvmE/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> beagleboard+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

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

[beagleboard] Re: Having problems cloning eMMC

[brian]

So I got my 8gb flash, and resized original boards partition to be smaller 
than second board.  So now the problem is I have flashed new board, and it 
will not boot up.  I can mount and view both partitions correctly, and 
everything looks ok, but I only get "CCC" when trying to boot and viewing 
with FTDI cable.   Any ideas?

Disk /dev/mmcblk1: 3867 MB, 3867148288 bytes
  
4 heads, 16 sectors/track, 118016 cylinders, total 7553024 sectors

Units = sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 512 bytes
 
I/O size (minimum/optimal): 512 bytes / 512 bytes
 
Disk identifier: 0x
   
 
 
Device Boot  Start End  Blocks   Id  System
   
/dev/mmcblk1p1   *2048  198655   98304e  W95 FAT16 (LBA)
  
/dev/mmcblk1p2  198656 7571455 3686400   83  Linux



On Tuesday, December 2, 2014 at 11:20:13 PM UTC-5, Graham wrote:
>
> I think you will have two problems.
>
> First, you can not put a 4GB file on a 4 GB card, because there must also 
> be room for the 
> Linux OS, and depending on the version, this can be another 1 GB, or more.
>
> Second problem is that when you install a 2 GB image on a 4 GB card, the 
> partition as
> installed is typically about 2 GB, and the rest of the card can not be 
> used, until you
> expand the partition to the full size of the card.
>
> So, for working with the 4 GB eMMC version of the Beaglebone Black, you 
> must use
> at least an 8 GB card.  I use 16 GB, so that there is room for about three 
> images
> that are not compressed.  You can not go larger than 32 GB at this time.
>
> --- Graham
>
> ==
>
> On Tuesday, December 2, 2014 5:57:16 PM UTC-6, br...@forceconstant.com 
> wrote:
>>
>> So in that other thread, it was instructed to use the same dd command "dd 
>> if=/dev/mmcblk1 of=/mnt/BeagleBoneBlack-eMMC-image-$RANDOM.img bs=10M" to 
>> create image, so why would mine only end up 2GB instead of 4GB?  I cannot 
>> follow those instructions exactly, as I only have a 4GB SD card, so maybe 
>> this is the problem since the eMMC is 4GB also.
>>
>> On Tuesday, December 2, 2014 5:22:47 PM UTC-5, janszyma...@gmail.com 
>> wrote:
>>>
>>> there is another thread here *Duplicate BeagleBone black setup* 
>>> 
>>>  dated 
>>> Nov 28, where you will find a solution to your problem.
>>> Good luck.
>>> Jan
>>>
>>> On Wednesday, December 3, 2014 6:32:08 AM UTC+11, 
>>> br...@forceconstant.com wrote:
>>>
 I am trying to clone an existing BBB, so my first try is using the 
 scripts on http://elinux.org/BeagleBone_Black_Extracting_eMMC_contents 
 .  So first thing I notice is the .img file created was only 2GB, whereas 
 this is a newer BBB that has 4GB eMMC.  So when I updated script to write 
 the img to new BBB, it no longer boots from eMMC.  i would like to make 
 exact copies including uENV.txt, etc.  Does anyone know why this is not 
 working?

 The read command script is 

 #!/bin/sh
 echo timer > /sys/class/leds/beaglebone\:green\:usr0/trigger 
 dd if=/dev/mmcblk1 of=/mnt/BeagleBoneBlack-eMMC-image-$RANDOM.img 
 bs=10M 
 sync
 echo default-on > /sys/class/leds/beaglebone\:green\:usr0/trigge

>>>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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] i2c-bus - A new Node.js I2C module

[Brian Cooke]

Sure, here are a number of things that come to mind:

   - All methods have asynchronous and synchronous forms (i2c has the 
   synchronous form although it looks like it has the asynchronous form)
   - It offers more complete support for the SMBus protocols (quick 
   command, send byte, receive byte, write byte/word, read byte/word, I2C 
   block transaction (I2C block transaction are not part of the SMBus 
   specification))
   - It supports plain I2C (see methods i2cRead, i2cReadSync, i2cWrite, 
   i2cWriteSync)
   - It offers runtime information about the functionality supported by the 
   bus/adapter (like 'i2cdetect -F 1', see methods i2cFuncs and i2cFuncsSync, 
   see example 
   https://github.com/fivdi/i2c-bus/blob/master/example/i2cdetect.js)
   - One i2c-bus object can handle multiple devices
   - Because it supports the SMBus receive byte protocol (see methods 
   receiveByte and receiveByteSync) it's possible to scan for devices (like 
   'i2cdetect -y -r 1', see example 
   https://github.com/fivdi/i2c-bus/blob/master/example/i2cscan.js). This 
   resolves https://github.com/kelly/node-i2c/issues/27
   - ...



On Tuesday, December 23, 2014 2:42:42 PM UTC+1, Jason Kridner wrote:
>
> Can you describe any advantages it has over node-i2c? 
>
> On Tue, Dec 23, 2014 at 5:08 AM, Brian Cooke  > wrote: 
> > I've written a new Node.js module called i2c-bus for accessing I2C 
> devices 
> > on Linux boards like the BeagleBone Black. 
> > 
> > It can be found here on github: https://github.com/fivdi/i2c-bus 
> > 
> > -- 
> > For more options, visit http://beagleboard.org/discuss 
> > --- 
> > You received this message because you 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] bot-io - A new Node.js module for ADC, GPIO, PWM, UARTs, ...

[Brian Cooke]

I've written a new module called bot-io for ADC, GPIO, PWM, UARTs, and more 
on the BeagleBone Black.

It can be found here on github: https://github.com/fivdi/bot-io

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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] i2c-bus - A new Node.js I2C module

[Brian Cooke]

I've written a new Node.js module called i2c-bus for accessing I2C devices 
on Linux boards like the BeagleBone Black.

It can be found here on github: https://github.com/fivdi/i2c-bus

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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: Having problems cloning eMMC

[brian]

So in that other thread, it was instructed to use the same dd command "dd 
if=/dev/mmcblk1 of=/mnt/BeagleBoneBlack-eMMC-image-$RANDOM.img bs=10M" to 
create image, so why would mine only end up 2GB instead of 4GB?  I cannot 
follow those instructions exactly, as I only have a 4GB SD card, so maybe 
this is the problem since the eMMC is 4GB also.

On Tuesday, December 2, 2014 5:22:47 PM UTC-5, janszyma...@gmail.com wrote:
>
> there is another thread here *Duplicate BeagleBone black setup* 
> 
>  dated 
> Nov 28, where you will find a solution to your problem.
> Good luck.
> Jan
>
> On Wednesday, December 3, 2014 6:32:08 AM UTC+11, br...@forceconstant.com 
> wrote:
>
>> I am trying to clone an existing BBB, so my first try is using the 
>> scripts on http://elinux.org/BeagleBone_Black_Extracting_eMMC_contents 
>> .  So first thing I notice is the .img file created was only 2GB, whereas 
>> this is a newer BBB that has 4GB eMMC.  So when I updated script to write 
>> the img to new BBB, it no longer boots from eMMC.  i would like to make 
>> exact copies including uENV.txt, etc.  Does anyone know why this is not 
>> working?
>>
>> The read command script is 
>>
>> #!/bin/sh
>> echo timer > /sys/class/leds/beaglebone\:green\:usr0/trigger 
>> dd if=/dev/mmcblk1 of=/mnt/BeagleBoneBlack-eMMC-image-$RANDOM.img bs=10M 
>> sync
>> echo default-on > /sys/class/leds/beaglebone\:green\:usr0/trigge
>>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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] Having problems cloning eMMC

[brian]

I am trying to clone an existing BBB, so my first try is using the scripts 
on http://elinux.org/BeagleBone_Black_Extracting_eMMC_contents .  So first 
thing I notice is the .img file created was only 2GB, whereas this is a 
newer BBB that has 4GB eMMC.  So when I updated script to write the img to 
new BBB, it no longer boots from eMMC.  i would like to make exact copies 
including uENV.txt, etc.  Does anyone know why this is not working?

The read command script is 

#!/bin/sh
echo timer > /sys/class/leds/beaglebone\:green\:usr0/trigger 
dd if=/dev/mmcblk1 of=/mnt/BeagleBoneBlack-eMMC-image-$RANDOM.img bs=10M 
sync
echo default-on > /sys/class/leds/beaglebone\:green\:usr0/trigge

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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] Maximum SD card size for BBB

[Brian Heckathorne]

Thank you very much that info should be in the bbb wiki very helpful and
good to know. Especially that a usb device could solve the issue. I take
lots of pictures order of thousands and need the space but dont want to
goto a power hungry usb disk drive.
On Nov 20, 2014 10:15 PM, "Robert Nelson"  wrote:

> On Thu, Nov 20, 2014 at 10:12 PM, Brian  wrote:
> > Maybe the correct question is what does the BBB have?
> >
> > Because SDXC uses a different file system called exFAT and it works
> > differently than standard SD cards, this new format is NOT backwards
> > compatible with host devices that only take SD (128MB to 2GB) or host
> > devices that only take SDHC (4GB to 32GB). Most host devices built after
> > 2010 should be SDXC compatible."
> >
> > Is it an SDHC or SDXC?
>
> The "ip" block on the am335x can not handle "SDXC", you'll have to use
> an external usb adapter to use SDXC cards on the bbb.
>
> 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/rK3y2ih1kig/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] Maximum SD card size for BBB

[Brian]

Maybe the correct question is what does the BBB have? 

Because SDXC uses a different file system called exFAT and it works 
differently than standard SD cards, this new format is NOT backwards 
compatible with host devices that only take SD (128MB to 2GB) or host 
devices that only take SDHC (4GB to 32GB). Most host devices built after 
2010 should be SDXC compatible."

Is it an SDHC or SDXC?

On Monday, July 21, 2014 11:00:35 AM UTC-5, Gerald wrote:
>
> And I can confirm this is correct.
>
> Gerald
>
>
>
> On Mon, Jul 21, 2014 at 10:40 AM, Robert Nelson  > wrote:
>
>> On Mon, Jul 21, 2014 at 10:34 AM, Eric Fort > > wrote:
>> > so can someone link to something definitive stating that for the beagle 
>> bone
>> > (black) 32GB SDHC is the biggest card supported (assuming this is 
>> correct)?
>>
>> From:
>> http://en.wikipedia.org/wiki/Secure_Digital#SDXC
>>
>> The Secure Digital eXtended Capacity (SDXC) format, announced in
>> January 2009 and defined in Version 3.01 of the SD specification,
>> supports cards up to 2 TB (2048 GB), compared to a limit of 32 GB for
>> SDHC cards in the SD 2.0 specification. SDXC adopts Microsoft's exFAT
>> file system as a mandatory feature.
>>
>> aka:
>> microSDHC 32GB is your limit..
>>
>> 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...@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] Maximum SD card size for BBB

[Brian]

Do SDXC cards work in the BBB? Or is it SDHC cards only? 



On Monday, July 21, 2014 11:00:35 AM UTC-5, Gerald wrote:
>
> And I can confirm this is correct.
>
> Gerald
>
>
>
> On Mon, Jul 21, 2014 at 10:40 AM, Robert Nelson  > wrote:
>
>> On Mon, Jul 21, 2014 at 10:34 AM, Eric Fort > > wrote:
>> > so can someone link to something definitive stating that for the beagle 
>> bone
>> > (black) 32GB SDHC is the biggest card supported (assuming this is 
>> correct)?
>>
>> From:
>> http://en.wikipedia.org/wiki/Secure_Digital#SDXC
>>
>> The Secure Digital eXtended Capacity (SDXC) format, announced in
>> January 2009 and defined in Version 3.01 of the SD specification,
>> supports cards up to 2 TB (2048 GB), compared to a limit of 32 GB for
>> SDHC cards in the SD 2.0 specification. SDXC adopts Microsoft's exFAT
>> file system as a mandatory feature.
>>
>> aka:
>> microSDHC 32GB is your limit..
>>
>> 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...@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] UWN-200 WiFi Dongle support in 3.14 kernels...

[Brian Anderson]

FWIW, I should note that my original problems were on a wheezy image.  I 
switched back and forth between a 3.8 and a 3.14 kernel.  My problems were 
all with the 3.14 kernel.

I am not familiar with jessie as of yet.  So, your problems may be 
modulated by that too besides the kernel.  Does jessie use systemd?  Does 
jessie use a different wireless configuration mechanism than wheezy?  I 
suppose its time to do some research unless someone has already dealt with 
wireless configuration with jessie and cares to weigh in.

ba

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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] UWN-200 WiFi Dongle support in 3.14 kernels...

[Brian Anderson]

DeKay,

No, unfortunately I have not gotten back to this.  The BBB is my occasional 
hobby, and I have not had the time recently to get back to things.  And, I 
am finding it a challenge to keep up with the plethora of snapshots and 
kernel upgrades...not quite sure what to choose as a "stable" option so 
that I can actually do something useful besides flashing snapshots and 
updating kernels.  But, I have recently made good on my threat to acquire 
some TP-Link dongles, so I will try things out when I have a chance 
(traveling this week, so probably won't get to this for a week or so).

I am having WLAN problems similar to yours in 3.14: freezes, having to 
> manually bring up the link, etc.  Wired links work fine.  Did you make any 
> progress?  A couple of things I found along the way that might help you or 
> others.
>

I'd like to try my scenarios again with the latest 3.14 kernels using the 
TP-Link.  Have you tried the latest and greatest?  Not sure I really care 
about anything any more besides the Atheros chip sets as everything else 
seems to be a huge waste of time.
 

>
> - "iwconfig" in 3.14 says my dongle has no wireless extensions.  But "iw" 
> works properly.  I believe that iwconfig is being depracated in favor of iw.
>
 
Yes, that is also my understanding. 


> - newer kernels are apparently defaulting to inhibiting RF output.  I 
> figured this out when I tried to do an "ifconfig wlan0 up" in Jessie and it 
> complained it couldn't because of "rfkill".  Doing this in wheezy just 
> failed silently... *nice*.  Doing "apt-get install rfkill" followed by 
> "rfkill unblock all" got that working.  Next I have to tell systemd to 
> remember that across reboots.
>

Interesting.  Guess I need to have a look at rfkill, thats a new one on 
me.  So, are you thinking that in newer kernels (beyond 3.8), the default 
is to not obey the enable on boot stanzas in /etc/networking/interfaces?  
That additional stuff is needed?  Can someone confirm or deny this 
assumption?  Seems a bit odd that this is necessary, but I suppose it would 
explain the observed behavior.  Has anyone else had this type of problem 
with enabling wireless interfaces in 3.14 kernels?
 

>
> I have a TP-Link dongle that causes the kernel to Ooops, and a 
> ZD1211-based one that doesn't see the outside world even after it gets an 
> IP address via me manually running "dhclient wlan0" on it.  I feel your 
> pain.
>

Yes, like I said I never got back to this.  It feels like deju vu all over 
again with WiFi dongles.  One of the reasons I caved in and bought a bunch 
of TP-Link dongles is that most of the recommendations indicate that the 
Atheros chipset and the ath9k_htc driver is one of the better options.  Is 
anyone else using WiFi dongles with 3.14?

BTW, I never saw a kernel ooops.  It just hung, no dmesg, no console log 
indications.  But, the hang was when I unplugged the dongle on an enabled 
interface.  A bit different than what you are seeing I believe, except for 
the common fact that we cannot actually send traffic thru the 
dongle/interface to the outside world.  It seems implausible that everyone 
else is also not able to send traffic thru the wireless interface on newer 
kernels without a flurry of reports here, so I am thinking we are missing 
something.  Could this be something with the gateway config having changed 
in newer kernels?  I can't remember whether I could get to the BBB via WiFi 
from a machine on the same subnet as I probably was SSHing to the BBB via a 
hardwired ethernet connection.  It might be interesting to see if you can 
access the BBB via WiFi from a machine on the same subnet (without a 
hardwired ethernet connection) if you haven't already done so.

On side note, the kernel command line option was indicated not via an 
ooops, but a failure to load the driver as I remember.  The error was 
pretty clear in the dmesg log.  The solution wasn't, but Robert got me past 
that quite quickly.
 
ba

>
> On Friday, 26 September 2014 14:44:07 UTC-6, Brian Anderson wrote:
>>
>>
>> I now need to manually enable the link (ifup ra0) to get the interface to 
>> come up.  Shouldn't these interfaces come up at boot time due to the "auto" 
>> stanza?  They did in 3.8.  Has something changed in 3.14 that prevents the 
>> interface from coming up automagically at boot time?  I have the same 
>> problem with another USB dongle, I need to manually enable the link (ifup 
>> wlan0).
>>
>> And of course...when I unplugged the 2 dongles (that were both up), 
>> everything froze (no panic, no nice blue led's flashing, just the power led 
>> on).  I think its the Realtec dongle that was on wlan0.  Rebooted, with 
>> just the Realtec don

[beagleboard] PWM and GPIO on Wheezy and Jessie

[Brian DeLacey]

There are two versions of Debian: Wheezy is mainstream now, and Jessie is 
the next mainstream release. PWM is not working on Jessie, due to the newer 
version of Linux.

If you are running Jessie, and would like to get some PWM applications 
working, Robert Nelson offered a quick, painless way to install to an 
earlier version of Linux that works with PWM:

sudo apt-get update

sudo apt-get install linux-image-3.8.13-bone67

sudo reboot

After you do this, you'll get an older version v3.8 of Linux with the 
capemgr that works. (Robert noted that a  mainline solution for Jessie, to 
100% replace v3.8 overlays, is still probably a year away.)

For Jessie, i2c/gpio/uart all work fine with v3.14.x However, sometimes you 
need to enable pinmux/cape - see the following link:

https://github.com/RobertCNelson/dtb-rebuilder/blob/3.14-ti/src/arm/am335x-boneblack.dts

If you want to explore BeagleBoneBlack PWM, here is an easy-to-follow, 
short video on controlling servos: 


https://www.youtube.com/watch?v=CceitHWEaKU .


I was able to control a couple of PWM servos and a number of GPIO pins 
using the Dart language. I’ve posted a short 7-second video of the Dart 
application running on a BeagleBoneBlack that with Jessie, using the older 
kernel:

 http://youtu.be/uG9kP6q_3po



I've posted a few additional details at the following page:

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

Re: [beagleboard] Re: BeagleBone Black resets periodic when connected to JTAG with CCS v6

[Brian Hutchinson]

On Thu, Oct 23, 2014 at 4:34 PM, John Syn  wrote:

>
>
> From: Brian Hutchinson 
> Reply-To: "beagleboard@googlegroups.com" 
> Date: Thursday, October 23, 2014 at 8:31 AM
> To: "beagleboard@googlegroups.com" 
> Subject: [beagleboard] Re: BeagleBone Black resets periodic when
> connected to JTAG with CCS v6
>
> On Wed, Oct 22, 2014 at 4:59 PM, Brian Hutchinson 
> wrote:
>
>> Hi,
>>
>> I'm trying to do some things with BBB using CCSv6 and a XDS560v2 USB.
>>
>> Doing kernel debug and trying to use stop/mode debugging.  The .ccxml
>> file I made for BBB (selected the BBB board from the menu list when I set
>> up target configuration) included a .gel file for the CortexA8 and so I
>> stubbed that out as that was causing me problems at first.
>>
>> Now when I run the debug configuration, it connects to target and loads
>> symbols for the kernel I'm working on but before I can set a hardware
>> breakpoint and click resume to start debugging ... the board spontaneously
>> runs (CCS changes from being suspended to running) and I see the board boot
>> in my serial console.
>>
>> So it is like a watchdog or something is firing and resetting the board
>> ... or something like that.
>>
>> Anyone got experience with using JTAG and CCS with BBB and know what is
>> going on?
>>
>> Here is basically what I'm doing:
>> I have a kernel/rootfs etc. that works on SD card.
>>
>> I hold down button while powering up to make BBB boot from SD.
>>
>> I stop in u-boot.
>>
>> Next I run the debug configuration I made for BBB that connects to target
>> and loads kernel symbols.
>>
>> Before I can do much of anything, the board takes off running when I
>> don't expect it to.
>>
>> Regards,
>>
>> Brian
>>
>>
>>
> Just to answer my own question ... I think I discovered part of my
> problem.  I'm using u-boot 2014.07 and I learned that turned on the
> watchdog by default.
>
> In uboot I tried:
>
> U-Boot# mw.l 44e35048 
> U-Boot# mw.l 44e35048 
>
> ... to disable the watchdog and then I didn't get a reset when I ran my
> debug configuration and connected to the target.
>
> But now I can't get hardware brakepoints to work :(
>
> A while back, I managed to get CCSV6 and USB560M working with BBB.
> Hardware breakpoints worked fine. Make sure you build the Kernel configured
> with the following options:
>
> CONFIG_DEBUG_INFO=y
> CONFIG_DEBUG_INFO_REDUCED  is not set
> CONFIG_LOCKUP_DETECTOR is not set
> CONFIG_DETECT_HUNG_TASK is not set
> CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
>
> Currently I'm using a Lauterbach emulator which supports full kernel aware
> debugging. TI had kernel aware debugging in CCSV4, but they removed that
> feature in CCSV5 and CCSV6. They keep saying they plan to add it back, but
> nothing so far.
>
> Regards,
> John
>

Ah, man!  I blew away my .config and didn't realize it and
CONFIG_DEBUG_INFO wasn't set!  I bet that's it.

I have one project that works (another TI Cortex A8 target) with HW
breakpoints and one that doesn't and was scratching my head wondering why.

I've been able to debug some other TI Cortex A8 stuff with latest mainline
kernel and that appears to be working OK except for the annoying
optimisation jumping around problem.  Still good enough to help me
determine what code is being used and what is dead while trying to figure
out dts.

Thanks for the heads up.  I was like "I have that set" and double checked
and didn't.  Hate it when that happens :)

Regards,

Brian

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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: BeagleBone Black resets periodic when connected to JTAG with CCS v6

[Brian Hutchinson]

On Wed, Oct 22, 2014 at 4:59 PM, Brian Hutchinson 
wrote:

> Hi,
>
> I'm trying to do some things with BBB using CCSv6 and a XDS560v2 USB.
>
> Doing kernel debug and trying to use stop/mode debugging.  The .ccxml file
> I made for BBB (selected the BBB board from the menu list when I set up
> target configuration) included a .gel file for the CortexA8 and so I
> stubbed that out as that was causing me problems at first.
>
> Now when I run the debug configuration, it connects to target and loads
> symbols for the kernel I'm working on but before I can set a hardware
> breakpoint and click resume to start debugging ... the board spontaneously
> runs (CCS changes from being suspended to running) and I see the board boot
> in my serial console.
>
> So it is like a watchdog or something is firing and resetting the board
> ... or something like that.
>
> Anyone got experience with using JTAG and CCS with BBB and know what is
> going on?
>
> Here is basically what I'm doing:
> I have a kernel/rootfs etc. that works on SD card.
>
> I hold down button while powering up to make BBB boot from SD.
>
> I stop in u-boot.
>
> Next I run the debug configuration I made for BBB that connects to target
> and loads kernel symbols.
>
> Before I can do much of anything, the board takes off running when I don't
> expect it to.
>
> Regards,
>
> Brian
>
>
>
Just to answer my own question ... I think I discovered part of my
problem.  I'm using u-boot 2014.07 and I learned that turned on the
watchdog by default.

In uboot I tried:

U-Boot# mw.l 44e35048 
U-Boot# mw.l 44e35048 

... to disable the watchdog and then I didn't get a reset when I ran my
debug configuration and connected to the target.

But now I can't get hardware brakepoints to work :(

Regards,

Brian

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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 resets periodic when connected to JTAG with CCS v6

[Brian Hutchinson]

Hi,

I'm trying to do some things with BBB using CCSv6 and a XDS560v2 USB.

Doing kernel debug and trying to use stop/mode debugging.  The .ccxml file
I made for BBB (selected the BBB board from the menu list when I set up
target configuration) included a .gel file for the CortexA8 and so I
stubbed that out as that was causing me problems at first.

Now when I run the debug configuration, it connects to target and loads
symbols for the kernel I'm working on but before I can set a hardware
breakpoint and click resume to start debugging ... the board spontaneously
runs (CCS changes from being suspended to running) and I see the board boot
in my serial console.

So it is like a watchdog or something is firing and resetting the board ...
or something like that.

Anyone got experience with using JTAG and CCS with BBB and know what is
going on?

Here is basically what I'm doing:
I have a kernel/rootfs etc. that works on SD card.

I hold down button while powering up to make BBB boot from SD.

I stop in u-boot.

Next I run the debug configuration I made for BBB that connects to target
and loads kernel symbols.

Before I can do much of anything, the board takes off running when I don't
expect it to.

Regards,

Brian

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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] Wireless mesh networking

[Brian Anderson]

Thanks Phillip.  I'll have a look at your book.

Actually, I am really interested in 802.11 based mesh networks because of 
bandwidth requirements.  I am interested in 802.11 based mesh networks and 
routing protocols and how to configure things to setup this style of 
wireless mesh network.  I am thinking that the 802.15.4 stuff relies on the 
Zigbee/Xbee mesh routing stuff rather than the 802.11s stuff in the recent 
Linux kernels.

Cheers,

ba

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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] Wireless mesh networking

[Brian Anderson]

Hi all,

I am interested in setting up a wireless mesh network using a collection of 
BBBs (and possibly other devices).  Does anyone have experience setting up 
a wireless mesh network using BBB?

I am not really interested in a so-called "wireless distribution system" 
that is used to extend an SSID across a wide area using wireless mesh 
networking.  I am much more interested in setting up a network of 
cooperating nodes that talk with each other (and to the internet via a 
gateway/mesh portal connected simultaneously to the internet and the mesh).

In particular, I'm interested in:

  * What distro and kernel are you using?
  * Ideally this would be with one of RCNs Debian images, but if not, 
I'm interested in what you might have used.
  * If you have done something with a Linux based system other than a 
BBB, I'd like to know about that too.
  * What mesh routing protocol was used?  Batman, Babel/AHCP, HWMP, OLSR, 
...
  * Steps to configure the mesh network and gateway.
  * Did you use 802.11s?  If so, presumably using the 802.11s support in 
the kernel?
  * WiFi chipset that was used (presumably supporting mesh mode).  SOFTMAC 
or HARDMAC?

I have researched the topic fairly extensively and can probably set 
something up via trial and error myself.  Prior to diving into that, I 
wanted to see if anyone has already done some work with wireless mesh 
networking and BBB (or something else) and would be willing to share their 
experience and knowledge!

Thanks in advance.

Cheers,

ba

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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] UWN-200 WiFi Dongle support in 3.14 kernels...

[Brian Anderson]

> We are closer.. ;) (someday i should actually take those modules out 
> of the bag and really test. ;) ) 
>

Ha!  And some day I'll get around to buying a couple TP-Link TL-WN722N and 
stop having to muck around with this stuff!

 
> can you add: 
>
> coherent_pool=2M 
>

Done.  Well, that got rid of the alloc errors. Still get the unknown device 
in dmesg, but apparently that is to be expected as other devices that load 
correctly seem to exhibit the same unknown device message.

Now onwards through the fog...

I have the following in /etc/network/interfaces (sans actual AP ssid and 
credentials) which worked just fine with 3.8:

auto wlan0
iface wlan0 inet dhcp
wpa-ssid ""
wpa-psk ""

# Logic Supply UWN-200 (RaLink)
auto ra0
iface ra0 inet dhcp
wpa-ssid ""
wpa-psk ""

I now need to manually enable the link (ifup ra0) to get the interface to 
come up.  Shouldn't these interfaces come up at boot time due to the "auto" 
stanza?  They did in 3.8.  Has something changed in 3.14 that prevents the 
interface from coming up automagically at boot time?  I have the same 
problem with another USB dongle, I need to manually enable the link (ifup 
wlan0).

And of course...when I unplugged the 2 dongles (that were both up), 
everything froze (no panic, no nice blue led's flashing, just the power led 
on).  I think its the Realtec dongle that was on wlan0.  Rebooted, with 
just the Realtec dongle, can plug and unplug it with no problems.  But if I 
enable the link (ifup wlan0), then unplug it, boom.  Doing the same with 
the UWN-200 RaLink dongle doesn't seem to cause the same crash/hang.

Note that neither the UWN-200 nor the Realtec devices are successfully 
associating with the AP configured in /etc/network/interfaces.  They 
associate just fine in 3.8 with the same /etc/network/interfaces.

Geez, back to WiFi dongle hell...

ba

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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] UWN-200 WiFi Dongle support in 3.14 kernels...

[Brian Anderson]

> sudo apt-get install mt7601u-modules-`uname -r` 
> sudo depmod -a `uname -r` 
> sudo update-initramfs -uk `uname -r` 
>
>
Done.  Still no go.  dmesg:

[   31.962611] usb 2-1.4.3: device v148f p7601 is not supported
[   31.974163] usb 2-1.4.3: New USB device found, idVendor=148f, 
idProduct=7601
[   31.974191] usb 2-1.4.3: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[   31.978577] 
[   31.978577] 
[   31.978577] === pAd = e0de5000, size = 860808 ===
[   31.978577] 
[   31.979148] ERROR: 256 KiB atomic DMA coherent pool is too small!
[   31.979148] Please increase it with coherent_pool= kernel parameter!
[   32.014321] <-- ERROR in Alloc Bulk buffer for HTTxContext!
[   32.014353] ---> RTMPFreeTxRxRingMemory
[   32.014394] <--- RTMPFreeTxRxRingMemory
[   32.014405] ERROR!!! Failed to allocate memory - TxRxRing
[   32.015109] <-- RTMPAllocAdapterBlock, Status=3
[   32.015759] rt2870: probe of 2-1.4.3:1.0 failed with error -1

I do see the new driver:

ls /lib/modules/3.14.19-ti-r26/kernel/drivers/net/wireless
at76c50x-usb.ko  ath  libertas  *mt7601Usta.ko*  mwifiex  p54  rt2x00  
rtl818x  rtlwifi  ti  zd1201.ko  zd1211rw

ba

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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] UWN-200 WiFi Dongle support in 3.14 kernels...

[Brian Anderson]

I have recently started to try out the new 3.14.19-ti kernel using the 
2014-09-03 image.

Apparently the UWN-200 (Ralink) WiFi dongle is no longer recognized in the 
3.14 kernel.  Seems to work fine in with the 3.8 kernel.

>From the 3.14.19-ti-r26 kernel dmesg:

[   32.371373] usb 2-1.4.3: device v148f p7601 is not supported
[   32.384124] usb 2-1.4.3: New USB device found, idVendor=148f, 
idProduct=7601
[   32.384151] usb 2-1.4.3: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3

And in the rootfs:

> ls /lib/modules/3.14.19-ti-r26/kernel/drivers/net/wireless
at76c50x-usb.ko  libertas  p54 rtl818x  ti zd1211rw
ath  mwifiex   rt2x00  rtlwifi  zd1201.ko

Whilst for the 3.8 kernel:

> ls /lib/modules/3.8.13-bone64/kernel/drivers/net/wireless
at76c50x-usb.ko  brcm80211mac80211_hwsim.ko  rndis_wlan.ko  ti
ath  hostap   mt7601Usta.ko  rt2x00 zd1201.ko
b43  libertas mwifiexrtl818xzd1211rw
b43legacylibertas_tf  p54rtl8192cu

I don't see the mt7601Usta.ko module in the 3.14 area.

Is this chipset no longer supported in the 3.14 kernel?  Is it 
inadvertently missing?

Cheers,

ba

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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] Setting up TFTP and NFS

[Brian Anderson]

William,

Thanks for the comments.  Yes, I am in the same position as you...a year 
on.  I've not touched Linux in any serious way for a long time.  I have 
been involved in a number of commercial deployments that target 
CentOS/RHEL.  My role was that of a Java server developer, so I didn't get 
all that close to the metal.  I am just recently coming off of 3 years of 
serious Android development work and hoping to transition to some embedded 
stuff (Android and/or embedded Linux) professionally over the next couple 
of years.  So, I do appreciate your input.

FWIW, I am thinking that things _might_ have changed a bit since you last 
looked.  I'm using Mint-17 self described on their release page as:

Linux Mint 17 features Cinnamon 2.2, MDM 1.6, a Linux kernel 3.13 and 
an Ubuntu 14.04 package base.

Apparently this is not LMDE...that is a different distribution that the 
Mint folks offer (and yes, that is still Debian testing, assuming jessie).  
I remember reading up on Mint changing directions a bit in the not too far 
distant past, concentrating on improving UI on top of a core Ubuntu 
distro.  So far, so good.  Nice UI, performant enough.  No problems with 
package conflicts.

Regarding the usbnet stuff, I read your response to be that usbnet offers 
the potential for a higher bandwidth connection than available over the 
Ethernet jack on the BBB.  Correct?  All other things being the same?  That 
is, NFS rootfs mount, TFTP, ...

Cheers,

ba

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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] Setting up TFTP and NFS

[Brian Anderson]

> If you want my opinion, ditch Linux mint *NOW*. Personally I will not use 
> anything other than Debian for a support system to the BBB, and would NEVER 
> use X for this purpose. Especially in a VM . . .
>
> Yeah yeah, Linux mint is based on Ubuntu and Debian( testing ) ( depending 
> on version ), but thats part of the problem.  
>
>
Hmmm, OK!  Would you like to enumerate why you wouldn't use Mint?  I was 
under the impression the Mint-17 is based upon Ubuntu 14.04LTS, and thus 
fairly stable.  Personally, I can't stand Unity...but YMMV.  What distro 
would you suggest?

Well, at the moment, all I have is my MBP laptop to support this effort.  
So, either I setup NFS on the MAC and hope for the best, or use a VM 
running some Linux.  I thought I'd give the VM approach a try as a first 
step in order to not introduce native MAC NFS vagaries into the mix.  
Probably could try that option now that I have things limping along.

When you say NEVER use X, I'm assuming you mean running X windows on a dev 
env (Linux Mint)?  I'm not running X on the BBB (well, I do often use X 
forwarding to the MAC/XQuartz for stuff like (gasp) emacs, xterm, ...).  My 
thought was to do dev on the MAC (straight away or via a VM) using a shared 
file system between the MAC and BBB so I didn't have to copy files around, 
nor risk loosing everything if the BBB goes toes in the air or the uSD 
craps out.

I'm all ears on suggestions for a good dev setup though!

Cheers,

ba

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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] Setting up TFTP and NFS

[Brian Anderson]

>
> When you copied the rootfs, the root device is listed in /etc/fstab, 
> along with the fsck call. Just minimze it: 
>
> voodoo@hades:$ cat /opt/wheezy/etc/fstab 
> debugfs  /sys/kernel/debug  debugfs  defaults  0  0 
>

Yes, on the failing rootfs I see the / mount (/dev/mmcblk0p2  /  ext4  
noatime,errors=remount-ro  0  1)

I'll eliminate that and give it another try.
 

>
> Btw, here's how i setup the nfs rootfs.. I first boot the bbb, with 
> the microSD, then run this: 
>
>
> https://github.com/RobertCNelson/boot-scripts/blob/master/tools/developers/nfs-rsync.sh
>  
>
> Just change all occurances of: 
>
> 192.168.0.10 & /opt/wheezy/ 
>
> and it should work for you. 
>

Thanks!  I'll have a look.

Maybe the auto generation isn't working when I boot from a virgin rootfs 
created from the tarball?
Is your expectation that one should be able to use the rootfs tarball as 
the basis for a root file system mounted on NFS, mounted on flash?
Is it possible that the initial bootup is assuming something that it 
shouldn't be?

Thanks again!

Cheers,

ba

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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] Setting up TFTP and NFS

[Brian Anderson]

@Robert - Thanks for confirming!

@William - Interesting.  Can you shed some additional light on this 
approach?  usbnet is Ethernet over USB, correct?  Is this just an 
alternative to using the wired Ethernet jack...and thus one still is 
mounting the rootfs via NFS from a NAS or something like that?  Or is this 
a different approach?  How does the BBB access/mount the rootfs?  Would 
this approach work for supporting cross development on a Linux laptop with 
a filesystem shared with the BBB?

I was able to download a kernel via TFTP, boot and successfully mount an 
NFS rootfs...sorta.

I had originally setup a rootfs on the NFS share as follows:

Setup a uSD card:

   - Created using 
   
https://rcn-ee.net/deb/testing/2014-08-05/lxde/bone-debian-7.6-lxde-armhf-2014-08-05-4gb.img.xz
   - Configured and setup on a BBB Rev C.
   - Successfully booted, run, and updated numerous times on the BBB.

Shutdown the BBB, move the uSD card to my MAC.  Then, from Linux Mint 
running in Virtual Box on the MAC:

   - Mount the uSD card.
   - Create a tarball from the mounted uSD card whilst sudo.
   - Untar the tarball into the exported NFS share location on Linux Mint 
   whilst sudo.

My assumption was that I should be able to move/copy the rootfs from the 
uSD card using a separate system.  Note that the uSD card was NOT running a 
live system when I made the copies.

Unfortunately, when the BBB subsequently tries to boot using the copied 
rootfs, the following happens:

[] Checking root file system...fsck from util-linux 2.20.1
fsck.ext4: No such device or address while trying to open /run/rootdev
Possibly non-existent or swap device?
fsck died with exit status 8

So, I resorted to creating a fresh rootfs using 
https://rcn-ee.net/deb/testing/2014-08-05/lxde/debian-7.6-lxde-armhf-2014-08-05.tar.xz.

All went fine and the system booted and I could ssh to it.

Unfortunately, this system seems to have some broken network setup.  A bit 
of digging reveals that /etc/resolv.conf is not setup correctly:

domain localdomain
search localdomain
nameserver 192.168.1.1

Whilst /etc/resolv.conf from the rootfs on the original uSD card that I've 
been using:

domain hsd1.wa.comcast.net.
search hsd1.wa.comcast.net.
nameserver 10.0.1.1

Also, /etc/network/interfaces does not have the stanzas for the USB gadget, 
and /etc/udhcpd.conf is not setup properly.  There may be other issues, but 
this is as far as I've looked.

Obviously something is either missing or went awry.

Thoughts?

Cheers,

ba

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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] Setting up TFTP and NFS

[Brian Anderson]

I am attempting to setup a BBB to boot via TFTP and mount a rootfs via NFS.

I am using Robert Nelson's 2014-08-05 Debian lxde release image.  I've 
examined the nfs-uEnv.txt in the boot partition and had a brief look at how 
the various environment variables interact with the default uboot setup.  
With the latest BBB uboot setup, it appears that TFTP boot and NFS rootfs 
functionality are now "packaged" together.

I've also read William Herman's guides to setting up to boot via TFTP and 
mount the rootfs using NFS.  Whilst helpful, these guides are now a bit 
dated (published June 2013) with respect to the latest uboot default setup.

I have setup a VirtualBox image running Linux Mint on my MAC.  I have 
configured this image to be a NFS server and have arranged to export a 
rootfs (copied from a uSD card flashed with a disk image or created 
directly from RCN's rootfs tarball).  I have also configured TFTP on this 
image.

My questions:

   - Where/how do I obtain a "zImage" to boot using TFTP?  Is this simply 
   the vmlinuz-xxx image in the /boot partition of the rootfs? (Running the 
   "file" command on a vmlinuz image reports it to be a " Linux kernel ARM 
   boot executable zImage (little-endian)".)
   - Unlike the normal so-called "uname" boot, the nfsboot setup does not 
   appear to use an initrd ramfs image.
  - What function does this file system provide?
  - What impact, if any, does the lack of an initrd image have on a 
  system booted via TFTP and running a rootfs via NFS?
   - In this new setup, what are the best practices for updating the kernel?
   - Given this setup, is it advisable to arrange to mount a user home 
   directory via another NFS share to support development?  Or would it be 
   better to include the user home directory as part of a single (rootfs) NFS 
   mount to keep things simple?

Thanks in advance!

ba

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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] Gyro code help

[Brian]

So I'm trying to get X value from the analog gyro Sparkfun Gyro Breakout 
LPY503AL
https://www.sparkfun.com/products/11341

I'm trying to port this from http://www.pieter-jan.com/node/7

So here's what I'm trying to do, just have an angle change when it rotates 
on Z axis. That's all I want, just to know then it's moved and which way. 
My noobness is so bad in this area. Any help would be much appreciated! I'm 
guessing I'm going about this all wrong!


my code

var b = require('bonescript');

var gyroValue = 0; 
var offset = .70;
var angle = parseFloat('0');
var gyroRate = parseFloat('');

function callADC(){
gyroValue = b.analogRead('P9_40');
gyroRate = (gyroValue - offset) * 1.8; // Sensitivity has been found 
trial/error
angle += gyroRate / 100.0;
//console.log('Analog Read Value x: ' +angle); 
console.log('gyroRate : ' +gyroRate); 
console.log('gyroValue: ' +gyroValue); 
console.log('gyroAngle: ' +angle); 
}

//callADC will be invoked 20 times a sec or once every 50 ms
var loop = setInterval(callADC, 50);



I cannot figure out offsets or what the sensitivity should be. 

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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] OTA update (remote/field updates) strategies

[brian larochelle]

Does anyone have any thoughts on BBB updating/upgrading strategies.  The 
two I'm looking at are image based updates, or debian apt based updates.

1. image based with two kernel partitions, two rootfs partitions.  Download 
an unpack new kernel and rootfs to unused partitions and then modify u-boot.
2. use debian apt repo's + custom repo's.  this sounds interesting, would 
have to read up on deb packaging and dependencies.

Any thoughts on these, other interesting strategies?  

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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: RIP Never Used BBB

[Brian Heckathorne]

John no worries my friend I hope you didnt take offense im a Texan to boot
and was only thinking outloud. Wasnt implying anyone made a mistake or how
smart they are or are not. Ive been quite surprised how on top of
everything Gerald is. No doubts John hope you didnt take offense or think I
was downing the product any. Was NOT the case. I think its a great product
and cant wait to see whats next.

Personally I wish the support for bonescript was larger but that will take
time.
On Jul 30, 2014 5:27 PM, "John Syn"  wrote:

>
> From: 
> Reply-To: "beagleboard@googlegroups.com" 
> Date: Wednesday, July 30, 2014 at 1:11 PM
> To: "beagleboard@googlegroups.com" 
> Subject: Re: [beagleboard] Re: RIP Never Used BBB
>
> I wasn't saying make it bullet proof, just some simple goof proofs. Like
> on the 5v plug, that kind of thing. I get the whole cost thing and by and
> large agree.
>
> I'm sure to try and cover everything would cost a bit, Not sure why anyone
> would be putting 220v to the 5v plug, but i could understand reverse
> polarity on the 5v plug. Not sure it needs to be gone to the extreme.
>
> How hard/costly is it to fix something like reverse polarity or blown
> gpio? if repairs are easy enough, perhaps protection isn't worth it.
>
> Think economics and not technical. Since there were very few returns
> because of reverse polarity, it isn’t cost effective to add the protection
> to each board. For example, circuitco has shipped 177,000 BBB multiplied by
> $10 protection is $1,770,000. Less than 20 returned because of reverse
> polarity at $55 each is $1,100. The solution is obvious. Gerald is very
> smart and he knows what he is doing ;-) Users just need to be more careful.
>
> Regards,
> John
>
>
>
> On Wednesday, July 30, 2014 3:00:10 PM UTC-5, john3909 wrote:
>>
>>
>> From: 
>> Reply-To: "beagl...@googlegroups.com" 
>> Date: Wednesday, July 30, 2014 at 12:50 PM
>> To: "beagl...@googlegroups.com" 
>> Cc: 
>> Subject: [beagleboard] Re: RIP Never Used BBB
>>
>> I think I would of paid 10 - 12 extra bux for a BBB that had some
>> protection. Feels like at any moment my BBB might suddenly spontaneously
>> contract "magic smoke" disease and all it's electrons fall out.
>>
>> Since there are very few of you who have done this, why should the rest
>> of us have to pay the extra cost. I think there are less than 20 out of
>> 150,000 boards shipped.
>>
>> Regards,
>> John
>>
>>
>>
>> On Tuesday, July 29, 2014 10:42:01 PM UTC-5, candy...@gmail.com wrote:
>>>
>>>
>>> hello people, please excuse my for my Tarzan English.
>>> first connect my BBB with a 5V supply 4A with the negative in the
>>> middle, might have killed her so easily?
>>> now with the positive in the middle got hot and nothing more happend.
>>
>> --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you 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.
>
>  --
> 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/iiqYyjTuGHM/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] analogy Gyro breakout help?

[Brian Heckathorne]

I'm having a heck of a time figuring out the Gyro-py breakout. 

https://www.sparkfun.com/products/11341

I have it hooked up in to p9_40, and I can't figure out how to get it to 
read correctly. I've searched and searched for info related to conversion 
or whatever is needed to read an analog gyro correctly. If anyone has some 
info on how to do this in bonescript please fill me in!

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.