[beagleboard] Re: WEC 7 Can't BOOT on BBB using SD Card

[rchrdlyon1]

Hi,

I have been using WinCe 6 / .Net Compact Framework on the Beaglebone Black 
and the LCD7 touchscreen with success.

A couple of things you might like to look at:

1. Make sure the partition boot flag is set.
2. Always copy MLO to the partition first.
3. Check if there is any output on debug uart.
4. Contact the person who offered the port for help.

There are separate BSPs for HDMI, LCD7, etc ... You need to select the 
correct BSP from the codeplex web site.

.Net Compact Framework is supported. Touchscreen works well. Providing BSP 
is setup correctly UARTS work. I have found that GUI apps written in c# 
work very well on the Beaglebone Black with touch screen. You use 
VisualStudio on PC to cross-compile apps. I haven't bothered to test 
Activesync yet. Instead I just copy files to the SDHC card.

If you are planning to do some serious application development and use the 
Beaglebone hadrware  features you will have to look at creating you own 
BSP's. Otherwise you will have to get someone else to do it.

Regards ...

 

On Tuesday, June 10, 2014 5:24:55 PM UTC+10, ASWIN PP wrote:
>
>
> Hi friends,
>   I have loaded a 4GB SD card with the MLO, EBOOTSD.nb0 and NK.bin 
> that comes with the Demo package "WEC7 BBB 01.05.00", Also I have formatted 
> the card with Fat32 and 4096 byte sectors (using hp format tool), and I 
> have used the TI SD card utility for flashing the SD card, Also I have 
> pushed the user button before power up, 
> But noting happens!!!
> In some procedure they said to format using hp format tool, copy 
> mlo,ebootsd,nk.bin in correct order and press usr boot button and power up..
> but not booting...
>
> when I power the board up the leds won't flash, , So I think it's a boot 
> problem, How can I be sure that the MLO is in the first sector of the SD 
> card?
> I have loaded angstrom img succsfuly on BeagleBone Black.
> I am using 4gb sd card, windows 7 and virtual machine xp.
> so please consider the issue and help me...
>
> Thanks & Regards
> aswin pp
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from 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: Encouragement for the disencouraged

[rchrdlyon1]

My Observations:
 

   - A large amount Linux documentation is out-of-date.
   - Take any advice from a newsgroup with a degree of skepticism
   - It seems like for every hour spent coding, more than hour is spent 
   retrieving information and resolving Beagle/Linux issues. 
   - Linux is not a real-time operating system
   - Angstrom Linux is OK for embedded applications with soft-real-time 
   constraints
   - Ubuntu/Debian/Arch might be easier if your trying to make a mini 
   personal computer with a binary distribution
   - You can create your own version of Linux for the Beaglebone black 
   using Yocto
   - Yocto is supported by companies like Gumstix, Wind River and Atmel 
   (3.10 is the LTS Kernel)
   - Microsoft Windows CE 6 runs on Beaglebone black quite well.
   - Microsoft Windows CE 6 works with the LCD7 cape/touchscreen
   - Microsoft Internet explorer on the Beaglebone black is slow
   - Microsoft Windows CE 6 worked better than Linux/xwindows/gnome on the 
   LCD7 cape/touchscreen (my opinion)
   - Microsoft Windows Embedded 7 runs on the Beaglebone black
   - It would be great to have a real-time executive like RTEMS running on 
   the Beaglebone Black.
   - If you want to do video, a multicore processor is a much better choice
   - Beaglebone black is a good starting point to evaluate Linux and other 
   operating systems in an embedded environment
   - Beagle/Ti today, plenty of alternatives.

 Always confused 
 
On Wednesday, March 26, 2014 12:31:09 PM UTC+11, Brandon I wrote:

> > My only real issue that I have no idea what the Angstrom is really 
> capable of and what really comes with it.
>  
> I think the biggest hurdle for people is they have some embedded mindset 
> with talk of processors and whatnot. Think of this as it is, a resource 
> limited general purpose Linux computer in a small form factor. You develop 
> for it just like you would a normal desktop computer.
>  
> Don't think of it as what Angstrom is really capable of because Angstrom 
> has nothing to do with it. Install Debian if you want and you'll be able to 
> accomplish the same (maybe with less free RAM) using almost identical code.
>  
> The biggest hurdle I had was to do things right the "Linux way", as in 
> using the abstracted to infinity drivers and sysfs interfaces to do 
> something like access a single register for some hard ip. You can go bang 
> registers and be done with it, but the whole point is that you don't have 
> to care about the specific platform if you use the standard interfaces 
> allowing you to port your code to some other future embedded (or not) 
> system.
>  
> 2 ranty cents for you.
>  
> On Thursday, March 20, 2014 3:05:17 PM UTC-7, Thorsten Gonschior wrote:
>>
>> Hi to you all out there, new to the BBB, new to Linux, new to whatever?
>>  
>> This is no request for a particular solution but somehow a thought to 
>> whats wrong with me, ... or some of the others?
>>  
>> Never worked with Linux or Unix, never did anything else than windows and 
>> TI embedded stuff. I would think of me as a professional senior engineer 
>> for embedded systems, automotive and industrial control.
>>  
>> Now, I entered the embedded Linux world and I am thrilled and frustrated 
>> at the same time. Before some days system and software engineering was 
>> somehow deterministic to me, something you plan and do. yea, welcome to 
>> waynes world.
>>  
>> After reading some hundred hours in the internet, peeking through about 
>> 12 new books I bought like hands on the beagle bone black for hyperdummies 
>> down to realtime driver development in subatomicmicrokernels I am almost as 
>> clueless as before. almost ;) 
>> After trying to do some really complex stuff like hello world on a php 
>> web page I am beginning to understand that I have to let go some very basic 
>> principles of thinking like an engineer if I want to act in and survive 
>> this new scene.
>>  
>> My first impression on the BBB was somehow, oh wow now I can do 
>> everything I always wanted for free. Today I am more on the way of thinking 
>> what I could do if noone or nothing unavoidably unseen screws me up, kicks 
>> me in the back and stabs me with a fork in my ass (in my sleep).
>>  
>>  
>> After this esotheric discourse for all you out there finding yourself 
>> here I will come to the encouragement thing I promised.
>> You cannot make it run? its not there? dont know where, why, how or when?
>>  
>> Its there and it is quite simple and so much more complex you will ever 
>> imagine. Know what? give a damn, go get it and make it any way you can.
>>  
>> Newbie/Noob Rule 1: there is no correct way, there ist never only one 
>> way, and what ever way you find out, if ever, its the wrong one anyway.
>> Newbie/Noob Rule 2: dont do it on your own. its already there. dont even 
>> start thinking how you can solve a subtask. just go and get your component 
>> out of the internet. talking caipirinha serving robots doing your lau

[beagleboard] Re: Controlling power to USB connections

[rchrdlyon1]

Pity you didn't search this group to see if someone has already done it 
before.

Author: AndrewTaneGlen
Date: Jan 17
Subject: "Disabling/Enabling USB Host Power"

And thanks to Andrew for his helpful contribution.

Regards ...

On Wednesday, March 26, 2014 8:36:02 PM UTC+11, Patrick Walters wrote:

> Do you happen to know if this accessible from the CLI?
> I tried looking at :/sys/bus/usb/devices/1-0:1.0/port1/power and thought 
> maybe I could edit the control file, but that didn't seem to work.
>
> 6.11 USB Host  The board is equipped with a single USB host interface 
> accessible from a single USB Type A female connector. Figure 48 is the 
> design of the USB Host circuitry.
> 6.11.1 Power Switch  U8 is a switch that allows the power to the connector 
> to be turned on or off by the processor. It also has an over current 
> detection that can alert the processor if the current gets too high via the 
> USB1_OC signal. The power is controlled by the USB1_DRVBUS signal from the 
> processor
>
> On Monday, March 24, 2014 3:19:41 AM UTC-10, mickeyf wrote:
>
>> I may have spoken hastily. See section 6.11.1 in the SRM.
>>
>>
>>
>> On Sunday, March 23, 2014 12:37:12 AM UTC-7, Patrick Walters wrote:
>>>
>>>
>>> uname -a
>>> Linux beaglebone 3.8.13 #1 SMP Thu Sep 12 10:27:06 CEST 2013 armv7l 
>>> GNU/Linux
>>>
>>> Is it possible to control the power to the USB port on the board or a 
>>> HUB from the CLI?
>>>
>>> My scenario is that I'd like to be able to turn something on\off that is 
>>> powered from the USB connection.
>>>
>>> Thanks,
>>> -p
>>>
>>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from 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: Windows Embedded CE6.0 BSP Support BeagleBoneBlack and Capes Now

[rchrdlyon1]

Unfortunately you have sent our marketing department into rapturous 
overjoy! 

On Wednesday, March 5, 2014 11:56:07 PM UTC+11, steven zhang wrote:
>
> I saw an post on e2e.ti.com.
>
> Transfer the post here to help someone who maybe need.
>
> http://e2e.ti.com/support/embedded/wince/f/353/t/325716.aspx
>
>
> *Hi, All*
>
>
> *We now support Windows Embedded CE 6.0 OS running on BeagleBone and 
> BeagleBoneBlack Boards, with BeagleBoneBlack Capes together.*
>
>
> *Our BSP Features are as following:*
>
>- *High Speed eMMC Support*
>- *SDHC Micro SDCard Support Upto 32G*
>- *512MB DDR3 *
>- *Persistend Registry Support*
>- *HDMI Display Support (1280x720)*
>- *LCD Display Support (800x480,1024x600,800x600,480x272 and so on)*
>- *RS232/RS485 Support*
>- *GPIO Button Support*
>- *Backlight Support*
>- *USB OTG & HOST Support*
>- *SPI Bus and I2C Bus Support*
>- *Resistive and Capactive TouchScreen Support*
>- *AIC3106 Audio Support   *
>- *CPGMAC Ethernet Support*
>- *NANDFlash Support with Firmware into NAND and Bootlogo update 
>dynamically*
>- *External I2C RTC Chip Support*
>- *WL1271 Support (IF NEED)*
>- *NLED Support *
>- *Auto-Run Programs *
>
>  
>
> For anyone who are interested, pls access the web:
>
> http://bbblackwince6bsp.codeplex.com
>
> For any other information, pls contact through email:  
> dev...@live.cn
>

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

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

[rchrdlyon1]

That takes you into Atmel/Element14 SAM5 territory. Atmel are putting 
effort into Linux4Sam (Linux 3.10 LTS, Linux Mainline, and Yocto 1.5.1, 
with a Qt developer kit) and the latest board from Element14 is going to be 
$75.00.

See: http://www.at91.com/linux4sam/bin/view/Linux4SAM/

and for the board itself

See: 
http://www.element14.com/community/docs/DOC-65651?ICID=knode-SAMA5D3-topbanner#anchor2

LTS kernels and Yocto are very important to me for commercial application.


On Saturday, February 22, 2014 1:28:56 AM UTC+11, Gerald wrote:

> Expedite fees? Well we used to do that on the earlier boards. But there is 
> zero buffer on these boards. The idea of loosing say $700,000 is not 
> something that makes a lot of sense. Having deals and POs in 
> place with distributors and then telling them, Oh sorry, you have to pay 
> more is tough.
>
> I am thinking of maybe taking the price to say $75 in the future.
>
> Gerald
>
>
> On Thu, Feb 20, 2014 at 11:51 PM, >wrote:
>
>> Appreciate the figures of 700/day on supply and 140,000 on back orders 
>> (200 days of supply.. phew!).
>>
>> This is an awesome product. What you saw until October was just people 
>> trying it out.  They've concluded it is a good product and are ordering it 
>> in greater quantities.  That is where we are and I hear similar stories 
>> from others. An order build up of 140,000 in two months, even with supply 
>> of 700/day suggests an incoming demand of *3500+ per day.*  I believe 
>> you will see this kind of demand continue.  None of these buyers want to 
>> get into manufacturing--Circuitco is good at it.  It would be a shame to 
>> see a great product go sideways due to supply issues.
>>
>> Given that the main constraint is lead time for some components: if 
>> sweeteners such as expedite fees can help, I think the community won't mind 
>> a higher price.. say $48 or $50, to ensure a demand-supply balance.
>>
>>
>>
>> On Friday, February 21, 2014 9:01:54 AM UTC+5:30, Gerald wrote:
>>
>>> We did this. A year ago when we launched the product. Things were fine 
>>> until roughly October. Demand has risen due to people 
>>> using boards in products  They never told anyone about 
>>> their pending demand. They thought the boards just magically appear in the 
>>> cabbage patch. 
>>>
>>> We build to distributor orders and schedules. We are close to getting 
>>> out of this.
>>>
>>> I appreciate your offer of help. But this is 
>>> not just a analytic problem. It is a data problem. We have plugged the data 
>>> into the formula and are adjusting to that new data and working to fill the 
>>> pipeline and to get orders shipped.
>>>
>>> Gerald
>>>
>>>
>>> On Thu, Feb 20, 2014 at 9:21 PM, Anil Gupta  wrote:
>>>
 Dave,
 Gerald,

 From my experience with product fulfillment: a good plan would 
 establish a target date when the product would be broadly available in the 
 market with only occasional shortages.   A key to this is to show back 
 orders as a % of weekly production, and whether back orders are reducing 
 or 
 increasing as we fulfill back orders and receive new orders each week. 
  There would be a weekly review of whether the target date is likely to be 
 met, production plan and any changes, and a new date, if needed.  Sudden 
 orders and other unexpected situations are common in all kinds of 
 fulfillment situations and there are lots of good systems to deal with 
 this.

 I am happy to volunteer to do weekly analytics.

 elinux.org only shows monthly shipments, with little clue around 
 demand and back order situation.  It is nice to know that "circuitco is in 
 full production" but we need to provide lots more facts.

 Dr. Anil Gupta


 On Wed, Feb 19, 2014 at 2:35 AM, David Anders wrote:

> as gerald stated, circuitco is in full production of the beaglebone 
> black and continues to ship daily to a wide range of distributors. these 
> distributors fill back-orders first before showing stock.
>
> http://elinux.org/Beagleboard:BeagleBoneBlack#Board_Shipments
>
> Dave
>
> On Tuesday, February 18, 2014 1:46:30 AM UTC-6, anil.g...@gmail.comwrote:
>>
>> I have been looking for 3+ weeks and unable to find any stock 
>> anywhere.
>>
>> Is there a way to see the order backlog with Circuitco and current 
>> supply capability?  Is the issue getting better or worse? (My anecdotal 
>> experience suggests it may be getting worse.)  The current situation is 
>> frustrating.  If the news is bad, let us know it early and deal with it. 
>>  Right now, there is no data at all.
>>
>> Gerald: thanks for your timely and open updates.
>>
>> On Wednesday, February 12, 2014 1:25:00 AM UTC+5:30, Gerald wrote:
>>>
>>> We are focused on the community. Feel free to build it yourself 
>>> however. All the materials to build it are provided for free and you

Re: [beagleboard] How are the production BBB images built?

[rchrdlyon1]

Hi,

I'm now getting this error on v2013.12-yocto1.5 cloud9-image.bb, while 
compiling on xubuntu 32-bit 12.04.3. Disk exhaustion is not the cause and I 
don't think it is memory exhaustion. It may be an internal make error. *Are 
you compiling on a 32-bit or 64-bit platform?*

I'll investigate further and maybe post the results on the Angstrom list.

Other Angstrom images seem to be OK.

Regards ...


On Thursday, July 18, 2013 5:17:53 PM UTC+10, Dale Schaafsma wrote:
>
> I crossed my fingers, and resized partitions...got past the disk 
> exhaustion, and strangely now my disk only has 22G. So somewhere between 
> the old 30G and the now available 53G was the magic number.
> Now unfortunately I'm encountering a build failure with nodejs...google 
> told me to raise ulimit -s for this...and that didn't work. The build 
> machine is Debian Wheezy (linux 3.2 if I read things correctly), am I out 
> of luck with the following?
>
> ERROR: Function failed: do_compile (see 
> /home/dales/beagleBoneBlack/angstrom/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/work/armv7a-vfp-neon-angstrom-linux-gnueabi/nodejs-0.8.22-r0/temp/log.do_compile.16430
>  
> for further information)
> ERROR: Logfile of failure stored in: 
> /home/dales/beagleBoneBlack/angstrom/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/work/armv7a-vfp-neon-angstrom-linux-gnueabi/nodejs-0.8.22-r0/temp/log.do_compile.16430
> Log data follows:
> | DEBUG: Executing shell function do_compile
> | make -C out BUILDTYPE=Release V=1
> | make[1]: Entering directory 
> `/home/dales/beagleBoneBlack/angstrom/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/work/armv7a-vfp-neon-angstrom-linux-gnueabi/nodejs-0.8.22-r0/node-v0.8.22/out'
> | make[1]: execvp: printf: Argument list too long
> | make[1]: *** 
> [/home/dales/beagleBoneBlack/angstrom/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/work/armv7a-vfp-neon-angstrom-linux-gnueabi/nodejs-0.8.22-r0/node-v0.8.22/out/Release/obj.target/deps/openssl/libopenssl.a]
>  
> Error 127
> | make[1]: Leaving directory 
> `/home/dales/beagleBoneBlack/angstrom/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/work/armv7a-vfp-neon-angstrom-linux-gnueabi/nodejs-0.8.22-r0/node-v0.8.22/out'
> | make: *** [node] Error 2
> | ERROR: Function failed: do_compile (see 
> /home/dales/beagleBoneBlack/angstrom/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/work/armv7a-vfp-neon-angstrom-linux-gnueabi/nodejs-0.8.22-r0/temp/log.do_compile.16430
>  
> for further information)
> ERROR: Task 861 
> (/home/dales/beagleBoneBlack/angstrom/setup-scripts/sources/meta-openembedded/meta-oe/recipes-devtools/nodejs/
> nodejs_0.8.22.bb, do_compile) failed with exit code '1'
> NOTE: Tasks Summary: Attempted 6529 tasks of which 6526 didn't need to be 
> rerun and 1 failed.
> Waiting for 0 running tasks to finish:
>
>
> Thanks,
> Dale
>
> On Wednesday, July 17, 2013 3:16:37 PM UTC-5, Dale Schaafsma wrote:
>>
>> If I might ask...how much disk is taken up by the cloud9-gnome-image 
>> build?
>> The machine I'm using is a little resource constrained and I've filled 
>> 30+G of disk in my attempt.
>> The specific command I'm using is: MACHINE=beaglebone bitbake 
>> cloud9-gnome-image
>>
>> Thanks,
>> Dale
>> ps. FWIW, I was able to build virtual/kernel, but I haven't yet tried the 
>> resulting kernel, so I may have failed to setup something correctly.
>>
>> On Wednesday, July 17, 2013 12:53:09 PM UTC-5, chmo...@gmail.com wrote:
>>>
>>> Hi Martin.
>>>
>>> I took a look at your post and I can certainly follow it in terms of 
>>> working with an existing image, but I don't believe that the appropriate 
>>> images are created by Angstrom, or at least my eyes are failing me and I 
>>> haven't spotted them.
>>>
>>> In this case I have a rootfs tarball, a uboot binary, the MLO etc, all 
>>> of the separate components, and a blank microsd card, which I believe to be 
>>> what the BBB recipes generate if you follow the instructions in the BB 
>>> white srm and on the angstrom wiki with MACHINE=beaglebone.
>>>
>>> I'm trying to figure out how to generate the production programming 
>>> image, the one on the wiki that boots and programs the production image to 
>>> the emmc, as well as the bootable image, the one where you can boot the 
>>> production image directly off of the microsd card.
>>>
>>> Clearly I can do everything by programming the existing image onto an sd 
>>> card, mounting it and altering it. That doesn't seem like The Right Thing 
>>> to do though.
>>>
>>> Chris
>>>
>>>
>>> On Wednesday, July 17, 2013 11:45:34 AM UTC-4, eskimobob wrote:

 Chris, I'm not entirely sure I am following the main thrust of your 
 question but I may be able to help with a tiny part.
 It is possible to locally mount a disk image and write to it (assuming 
 sudo) without having to write the image to a card and then mount that.  
 You 
 can use "losetup" to create a local loop.
 I've included details about that in a blog post about shrinking a 

Re: [beagleboard] How are the production BBB images built?

[rchrdlyon1]

Don't follow Derek's instructions as they are slightly out of date. To 
build a Angstrom console image on an SD-card:

Angstrom Master
=

Master Branch: v2013.06-yocto1.4

This guide details the process of building a Angstrom linux console image 
from source on an Xubuntu 12.04.3 32-bit Linux host. Your computer must be 
connected to the Internet. The build will take a number of hours and more 
than 600 MB of data and source code will be downloaded.

The angstrom console image includes udev, systemd, connman, ofono, ppp, 
busybox and some package management tools. It is a good starting point to 
evaluate Angstrom linux for use in embedded systems.

Prerequisites

We need some host development tools:

sudo apt-get install sed wget cvs subversion git-core coreutils 
unzip texi2html texinfo docbook-utils gawk python-pysqlite2 diffstat 
help2man make gcc build-essential g++ desktop-file-utils chrpath

/bin/sh (ls -l /bin/sh) is symbolically linked to dash. "dash" is a POSIX 
compliant shell that is much smaller than "bash". Some broken shell scripts 
still make use of bash extensions while calling into /bin/sh. To work 
around this issue call "sudo dpkg-reconfigure dash" and select No when it 
asks you to install dash as /bin/sh. 

Download Angstrom Distribution and Build

To download the master branch of the distribution and configure for the 
beaglebone (both white and black) , enter the following commands:

cd ~/Projects (or your preferred directory)

mkdir Angstrom

cd ./Angstrom

git clone git://github.com/Angstrom-distribution/setup-scripts.git

cd setup-scripts

MACHINE=beaglebone ./oebb.sh config beaglebone

And to compile the console image:

. ./environment-angstrom-v2013.06

bitbake console-image

The previous command creates the root file system, modules, kernel and boot 
files in the deployment directory ():

Angstrom-console-image-eglibc-ipk-v2013.06-beaglebone.rootfs.tar.gz 
(the root filesystem)
Angstrom-console-image-eglibc-ipk-v2013.06-beaglebone.rootfs.tar.xz 
(the root filesystem)
MLO-beaglebone-2014.01  
(first stage of the boot loader)
modules--3.8.13-r23z.2-beaglebone-20140116020947.tgz
(device modules; the exact filename is dependent upon date)
u-boot-beaglebone-2014.01-r0.img
(second stage of the boot loader)
zImage--3.8.13-r23z.2-beaglebone-20140116020947.bin 
(compressed kernel; the exact filename is dependent upon date)

SD Card Creation
=

Installing on SD card manually

Use the gnome disk utility application to create the partitions on a blank 
micro SD card and mount them.

Create DOS Partition with following:

Size:4.000 MB
Type:FAT
Name:boot

Then edit the DOS partition with the following:

Partition Label:
Type:W95 FAT32 (LBA) (0x0c)
Bootable:Check this tickbox

Create a Linux partition to fill the rest of the SD card:

Size:7.880 GB (for my 8 GB card)
Type:Ext4
Name:rootfs
Take Ownership of filesystem:Not checked
Encrypt underlying device:Not checked

Mount both partitions. The dos partition will be mounted at /media/boot and 
the Linux partition will be mounted at /media/rootfs

Copy the Angstrom distribution files to the SD card:

cd ~/Projects/Angstrom/setup-scripts/deploy/eglibc/images/beaglebone

cp MLO-beaglebone-2014.01 /media/boot/MLO

cp u-boot-beaglebone-2014.01-r0.img /media/boot/u-boot.img

sudo tar zxv -C /media/rootfs -f 
Angstrom-console-image-eglibc-ipk-v2013.06-beaglebone.rootfs.tar.gz

sudo tar zxv -C /media/rootfs -f 
modules--3.8.13-r23z.2-beaglebone-20140116020947.tgz

The SD card now is ready for the Beaglebone. Unmount the partitions.

When you power up the Beaglebone make sure you are holding down the boot 
switch. This ensure the boot loader components on the SD card are loaded 
and run in preference to the eMMC. 

Make sure when the system boots for the first time to run:

depmod -a

Unless there is a specific requirement, there is no need to include the 
kernel image or compiled device tree in the dos boot partition. The second 
stage of the boot loader u-boot.img will attempt to load the compressed 
kernel image from the boot directory in the ext4 partition. Also, I have no 
current need for a uEnv.txt file.

It is possible to include development tools in the image by modifying some 
of the image recipe files.

There are scripts that will do this also, but I'm quite happy to do it 
manually.

Creating an SD-card Flasher
=

It's not that hard. Download the latest flasher image and copy it to the 
SD-card. Mount the SD-card on your desktop machine and look at the 
contents. The key areas to examine are:

the build directory in the 

[beagleboard] Re: BBB + PREEMPT_RT

[rchrdlyon1]

Interesting result. Would be nice to see a histogram. I will try and 
duplicate this measurement. Also doing the some measure with the standard 
kernel would be informative.

That upper tail of 132 is a big problem for me.

On Thursday, February 27, 2014 12:53:05 AM UTC+11, quik...@gmail.com wrote:
>
> I have recently tested kernel 3.8.13-rt9 (
> https://github.com/beagleboard/kernel/tree/3.8-rt) using git://
> git.kernel.org/pub/scm/linux/kernel/git/clrkwllms/rt-tests.git. I am 
> using Ubuntu 12.04.4. The load was created using stress –cpu 1 which 
> generates a cpu load of about 100%. I then used cyclictest:
>
>
>  root@ubuntu-armhf:/home/ubuntu/rt-tests# ./cyclictest -l100 -m -n 
> -t1 -p99 -i400 -q
>
> # /dev/cpu_dma_latency set to 0us
>
> T: 0 ( 770) P:99 I:400 C:100 Min: 14 Act: 19 Avg: 18 Max: 132
>
>
>  uname -a reports:
>
> root@ubuntu-armhf:/home/ubuntu/rt-tests# uname -a
>
> Linux ubuntu-armhf 3.8.13-rt9-00899-g160e771 #1 SMP PREEMPT Wed Jun 19 
> 10:49:36 CEST 2013 armv7l armv7l armv7l GNU/Linux
>
>
>  I am absolutely surprised that the result is looking that good.
>
>
>
> Am Freitag, 21. Februar 2014 09:20:39 UTC+1 schrieb quik...@gmail.com:
>>
>> I am trying to figure out how to create a kernel for the BBB that 
>> supports PREEMPT_RT. It's kind of strange that the BBB's default kernel 
>> does not even have PREEMPT activated. Such a board doesn't fit to many 
>> embedded applications where we need at least some kind of determinism. It 
>> is even worse, that nobody seems to care about this problem. Contrary to 
>> that, the Raspberry PI's standard kernel has PREEMPT activacted from the 
>> very beginning.
>>
>> I have tested Robert Nelsons kernel 3.8.13-r9 (
>> https://github.com/beagleboard/kernel/tree/3.8-rt). It does not have 
>> PREEMPT_RT activated by default. When doing so, it does not boot. But 
>> activating PREEMPT does work. However, development of this branch has 
>> stopped several months ago. The official source for RT Linux (3.8.13) has 
>> evolved since then. Meanwhile there's an rt17 patch set (
>> https://www.kernel.org/pub/linux/kernel/projects/rt/3.8/). Did anybody 
>> give this a try? Does it work with the BBB?
>>
>>
>>

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

[beagleboard] Re: BBB + PREEMPT_RT

[rchrdlyon1]

Just a few thoughts ...

It is not possible to have a fully deterministic real-time operating system 
on a processor that uses instruction/data caches. ie you have to turn off 
the cacheing to achieve determinism and eliminate performance jitter (which 
then degrades the average performance).

>From what I understand PREEMPT_RT does not really improve the real-time 
performance of linux if you stick to user level applications. You have to 
start doing things at kernel level, which can get difficult and break many 
of the existing device drivers. Anyway, who said all embedded applications 
require a deterministic real-time performance? Soft real-time performance 
is generally good enough for a lot of applications.

For real-time, the PRU co-processors are the way to go.

There are a number of papers around on the web comparing the performance of 
normal linux, PREEMPT_RT and Xemonai in real-world situations (use google 
to find them). They make for interesting reading and caused me to re-access 
my approach to embedded linux systems. 

Regards ...

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

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

[beagleboard] Re: Failed angstrom build

[rchrdlyon1]

Hi,

There are problems compiling the Angstrom master branch on 64-bit ubuntu 
variants relating to the native libpseudo. There are two alternatives:

Switch to the angstrom-v2013.12-yocto1.5 branch which is meant to include a 
fix (see: 
https://www.mail-archive.com/angstrom-distro-devel@linuxtogo.org/msg06900.html
)

or

Use a 32-bit Ubuntu host.

Update your Angstrom host installation:

cd to the setup-scripts directory

git checkout -f -b angstrom-v2013.12-yocto1.5 
origin/angstrom-v2013.12-yocto1.5 (The force option is necessary if you 
modified local.conf)

MACHINE=beaglebone ./oebb.sh config beaglebone

. ./environment-angstrom-v2013.12

bitbake cloud9-image

I currently testing these steps on a 32-bit host. It will take a couple 
more hours before I can confirm success or failure. Why don't you try it on 
your 64-bit host and let us know how it goes. I'm sure Rhem Raj would like 
to get feedback about this fix.

Regards ...


On Monday, January 20, 2014 9:54:33 PM UTC+11, Jeremy Van wrote:
>
> I'm trying to build Angstrom with bitbake. I followed the instructions on  
> Derek 
> Molloy's 
> Site.  
> After running:
>
> $bitbake cloud9-image
>
>
> | ERROR: ld.so: object 'libpseudo.so' from LD_PRELOAD cannot be preloaded: 
> ignored.
> | update-alternatives: Linking 
> /home/jay/angstrom/setup-scripts/build/tmp-angstrom_v2013_06-eglibc/work/beaglebone-angstrom-linux-gnueabi/cloud9-image/1.0-r0/rootfs//usr/bin/top
>  
> to /usr/bin/top.procps
> | update-alternatives: Linking 
> /home/jay/angstrom/setup-scripts/build/tmp-angstrom_v2013_06-eglibc/work/beaglebone-angstrom-linux-gnueabi/cloud9-image/1.0-r0/rootfs//usr/bin/uptime
>  
> to /usr/bin/uptime.procps
> | update-alternatives: Linking 
> /home/jay/angstrom/setup-scripts/build/tmp-angstrom_v2013_06-eglibc/work/beaglebone-angstrom-linux-gnueabi/cloud9-image/1.0-r0/rootfs//usr/bin/free
>  
> to /usr/bin/free.procps
> | update-alternatives: Linking 
> /home/jay/angstrom/setup-scripts/build/tmp-angstrom_v2013_06-eglibc/work/beaglebone-angstrom-linux-gnueabi/cloud9-image/1.0-r0/rootfs//usr/bin/pkill
>  
> to /usr/bin/pkill.procps
> | update-alternatives: Linking 
> /home/jay/angstrom/setup-scripts/build/tmp-angstrom_v2013_06-eglibc/work/beaglebone-angstrom-linux-gnueabi/cloud9-image/1.0-r0/rootfs//usr/bin/pmap
>  
> to /usr/bin/pmap.procps
> | 
> | ERROR: Function failed: do_rootfs (see 
> /home/jay/angstrom/setup-scripts/build/tmp-angstrom_v2013_06-eglibc/work/beaglebone-angstrom-linux-gnueabi/cloud9-image/1.0-r0/temp/log.do_rootfs.20961
>  
> for further information)
> ERROR: Task 7 
> (/home/jay/angstrom/setup-scripts/sources/meta-ti/recipes-misc/images/
> cloud9-image.bb, do_rootfs) failed with exit code '1'
> NOTE: Tasks Summary: Attempted 5589 tasks of which 5588 didn't need to be 
> rerun and 1 failed.
> No currently running tasks (5588 of 5592)
>
> Summary: 1 task failed:
>   /home/jay/angstrom/setup-scripts/sources/meta-ti/recipes-misc/images/
> cloud9-image.bb, do_rootfs
> Summary: There was 1 WARNING message shown.
> Summary: There was 1 ERROR message shown, returning a non-zero exit code.
>
> Has anyone had any similar problems?
>

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

[beagleboard] Re: syslog in beagleboard

[rchrdlyon1]

If you are running Angstrom and systemd, then syslog has been replaced with 
the journal (see /var/log/README). Your application writes to the journal 
using the syslog api.

The journal is coming to Debian and Ubuntu along with systemd.

On Wednesday, February 19, 2014 12:07:35 AM UTC+11, susam.b...@gmail.com 
wrote:

>
> The syslog.service seems to be empty and there is no configuration file 
> like syslog.conf or rsyslog.conf. So, how can we go about using syslog in 
> an application running on the beagleboard?
>

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

[beagleboard] Re: Customizing BBB Angstrom Kernel?

[rchrdlyon1]

Hi,

If you want to use /etc/network/interface as a configuration file you start 
the network services with the command *ifup -a*. If you can define the wifi 
interface in /etc/network/interface then it will automatically started as 
well. ie  I am talking about a static configuration, where the network 
interfaces are configured and started just after boot (using system). It is 
assumed the wifi dongle remains permanently plugged into the bbb.

Netmanager is useful for dynamic situations. ie You want automatic 
detection of your wi-fi dongle whenever it is plugged in.

Netmanager will allow you to specify a static IP address for the Ethernet 
interface. You will need to have a look at the man pages.

Regards ...



On Wednesday, February 19, 2014 1:57:41 PM UTC+11, Mark Hatch wrote:

> I started to try to debug the board at home, and it actually did show up 
> on my dhcp list. So I do have SSH access!
>
> Here is my /etc/network/interfaces file.
>
> auto lo
> iface lo inet loopback
>
>
> auto eth0
> iface eth0 inet dhcp
>
>
> auto usb0
> iface usb0 inet static
>address 192.168.7.2
>netmask 255.255.255.0
>
>
> auto wlan0
> iface wlan0 inet static
> address 10.42.0.1
> netmask 255.255.255.0
> wireless-essid Capstone
> wireless-mode ad-hoc
>
>
>
> I guess I assumed NetworkManager was tied to /etc/network/interfaces... 
> which I think is wrong...
>
>
> On Tuesday, February 18, 2014 1:28:48 PM UTC-5, Mark Hatch wrote:
>>
>> Thanks Richard, you really have been an enormous help in this process, 
>> and I feel much more comfortable with this. Thank you for helping, I really 
>> have already learned a lot more.
>>
>> Right now I'm trying to tweak the bitbake recipes a bit.
>> I'd like to remove connman and install networkmanager instead.
>> Connman apparently does not have ad-hoc wireless support...
>>
>> All I'm trying to do is get my beagles to autojoin the ad-hoc network on 
>> startup.
>> I initially had some init.d scripts that would use ifconfig and iwconfig 
>> to set up the network, but for some reason these would not work totally 
>> correctly. The static IP would be correct, but in iwconfig it would not be 
>> set up with the ad-hoc network defined...
>>
>> I also followed this guide, set up the service as was discussed in the 
>> link, but it did not function correctly either.
>> http://octopusprotos.com/?p=37
>>
>> I tried removing connman with opkg and installing networkmanager, since I 
>> noticed I did not have a networking service (/etc/systemd/networking or 
>> whatever it is)... (this was a n00b mistake).
>> I ended up losing ssh access... and now am unable to talk to the board.
>> I guess if I had a serial cable I could debug the board, but right now it 
>> doesn't get an IP address (I checked the router's IP tables and it wasn't 
>> there) and the default USB 192.168.7.2 doesn't work either (I'm assuming 
>> connman used to set that up, but that was removed.)
>>
>> Right now the plan is to edit the bitbake recipes to remove connman and 
>> have networkmanager built instead. Then reflash the board. I have a feeling 
>> that there may be an easier way...
>>
>> Thanks again for the help,
>> Mark
>>
>

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

[beagleboard] Building Angstrom Master

[rchrdlyon1]

For the last few months I have working in an environment which has required 
me to create Angstrom linux images for use on the Beaglebone Black. This 
post documents the procedure I have used to create a basic starting 
Angstrom Linux image on an SD-card.

I imagine this will be useful for those who prefer to use a source-based 
linux distribution on the Beaglebone white and black, targeting embedded 
use.

If you intend using the Beaglebone as a miniature, low-cost, arm personal 
computer it might be more convenient to stick with one of the many binary 
distributions, such as arch, emdebian, etc ...



*Angstrom Master Build*
Master Branch: v2013.06-yocto1.4

This guide details the process of building a Angstrom linux console image 
from source on an Xubuntu 12.04.3 32-bit Linux host. Your computer must be 
connected to the Internet. The build will take a number of hours and more 
than 600 MB of data and source code will be downloaded.

The angstrom console image includes boot loader components, compressed 
kernel image, device tree and overlays, device drivers, udev, systemd, 
connman, ofono, ppp, busybox and some package management tools. It is a 
good starting point to evaluate Angstrom linux for use in embedded systems.


*Prerequisites*

We need some host development tools:

sudo apt-get install sed wget cvs subversion git-core coreutils unzip 
texi2html texinfo docbook-utils gawk python-pysqlite2 diffstat help2man 
make gcc build-essential g++ desktop-file-utils chrpath

/bin/sh (ls -l /bin/sh) is symbolically linked to dash. "dash" is a POSIX 
compliant shell that is much smaller than "bash". Some broken shell scripts 
still make use of bash extensions while calling into /bin/sh. To work 
around this issue call "sudo dpkg-reconfigure dash" and select No when it 
asks you to install dash as /bin/sh. 


*Download Angstrom Distribution and Build*

To download the master branch of the distribution and configure for the 
beaglebone (both white and black) , enter the following commands:

cd ~/Projects (*or your preferred directory*)

mkdir Angstrom

cd ./Angstrom

git clone git://github.com/Angstrom-distribution/setup-scripts.git

cd setup-scripts

MACHINE=beaglebone ./oebb.sh config beaglebone

And to compile the console image:

. ./environment-angstrom-v2013.06

bitbake console-image

The previous command creates the root file system archive, modules, kernel 
and boot files in the deployment directory 
(~/Projects/Angstrom/setup-scripts/deploy/eglibc/images/beaglebone):

Angstrom-console-image-eglibc-ipk-v2013.06-beaglebone.rootfs.tar.gz (*the 
root filesystem*)
Angstrom-console-image-eglibc-ipk-v2013.06-beaglebone.rootfs.tar.xz (*the 
root filesystem*)

MLO-beaglebone-2014.01  
   
(*first stage of the boot loader*)

modules--3.8.13-r23z.2-beaglebone-20140116020947.tgz 
(*device 
modules; the exact filename is dependent upon date*)

u-boot-beaglebone-2014.01-r0.img
 
(*second stage of the boot loader*)

zImage--3.8.13-r23z.2-beaglebone-20140116020947.bin  
(*compressed 
kernel image; the exact filename is dependent upon date*)

*SD Card Creation*

Installing on SD card.

Use the gnome disk utility application to create the partitions on a blank 
micro SD card and mount them.

Create DOS Partition with following:

Size:4.000 MB
Type:FAT
Name:boot

Then edit the DOS partition with the following:

Partition Label:
Type:W95 FAT32 (LBA) (0x0c)
Bootable:Check this tickbox

Create a Linux partition to fill the rest of the SD card:

Size:7.880 GB (for my 8 GB card)
Type:Ext4
Name:
rootfs~/Projects/Angstrom/setup-scripts/deploy/eglibc/images/beaglebone
Take Ownership of filesystem:Not checked
Encrypt underlying device:Not checked

Mount both partitions. The dos partition will be mounted at /media/boot and 
the Linux partition will be mounted at /media/rootfs

Copy the Angstrom distribution files to the SD card:

cd ~/Projects/Angstrom/setup-scripts/deploy/eglibc/images/beaglebone

cp MLO-beaglebone-2014.01 /media/boot/MLO

cp u-boot-beaglebone-2014.01-r0.img /media/boot/u-boot.img

sudo tar zxv -C /media/rootfs -f 
Angstrom-console-image-eglibc-ipk-v2013.06-beaglebone.rootfs.tar.gz

sudo tar zxv -C /media/rootfs -f 
modules--3.8.13-r23z.2-beaglebone-20140116020947.tgz

The SD card now is ready for the Beaglebone. Unmount the partitions.

Of course it is possible to write a script to duplicate this procedure, if 
you want it.


*Booting Beagle*

When you power up the Beaglebone Black with the new SD card inserted, make 
sure you are holding down the boot switch fo

[beagleboard] Re: Customizing BBB Angstrom Kernel?

[rchrdlyon1]

Some further comments:

You don't need to rebuild MLO/u-boot.img
You don't need a serial cable. It can be helpful for debugging, but 
thats all.
Have you got the wifi device working correctly on your BBB?

I would recommend you get an micro SD card for testing your new kernel, 
before you copy it to eMMC.

Regards ...

On Tuesday, February 11, 2014 6:45:31 AM UTC+11, Mark Hatch wrote:
>
>
> Hi friends,
>
> Total newbie here, so forgive me.
>
> I'm
>  
> trying to add functionality to iptables so I can use the BBB as a ad-hoc 
> "router", sharing it's Ethernet connection with others.
>
> From what I've gleamed so far I need to add that functionality by 
> recompiling the kernel.
>
> So following the links at http://www.angstrom-distribution.org/ i cloned 
> the setup-scripts.
>
> MACHINE=beaglebone ./oebb.sh config beaglebone
>
> MACHINE=beagleboard ./oebb.sh update
>
> . environment-angstrom-v2013.06
>
> bitbake -c menuconfig virtual/kernel
>
> I then change the options I need, but when I built it made a zImage 
> file... Which confuses me.
>
> Now what I don't understand is that the image I want should be based off 
> the regular systemd image.
>
>
>- 
>
>bitbake systemd-image
>
>
> How do I update the kernel configuration from the systemd image without 
> just building the regular image?
>
> A step-by-step explanation would be awesome, cause I've never 
> customized/built the linux kernel before.
> I also do not have a serial cable yet. Is this necessary for running a 
> custom kernel? Do options in u-boot need to be changed?
>
> I'm sure I'm asking all the wrong questions, but would really appreciate 
> some help!
>
> Here are the options that I need:
>
> Networking  >
>  Networking options  >
>   Network packet filtering framework (Netfilter)--->
>Core Netfilter Configuration >
> <*> Netfilter connection tracking support
> <*> Netfilter Xtables support (required for ip_tables)
> <*>   "NFLOG" target support
> <*>   "conntrack" connection tracking match support
> <*>   "state" match support
>IP: Netfilter Configuration --->
> <*> IPv4 connection tracking support (required for NAT)
> <*> IP tables support (required for filtering/masq/NAT)
> <*>   Packet Filtering
> <*> REJECT target support
> <*>   Full NAT
> <*> MASQUERADE target support
> <*> Packet mangling
>
>

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

[beagleboard] Re: Customizing BBB Angstrom Kernel?

[rchrdlyon1]

Hi,

What your attempting to do is possible with Angstrom Linux. You just have 
to work through a number of setup issues.

If you want to use IP forwarding with NAT it is necessary to recompile the 
kernel. My kernel configuration is:

-> Networking support (NET [=y])
-> Networking options
-> Network packet filtering framework (Netfilter) (NETFILTER 
[=y])
-> Core Netfilter Configuration
 Netfilter connection tracking support
{M} Netfilter Xtables support (required for ip_tables)
*** Xtables combined modules ***
 "NFLOG" target support
 "conntrack" connection tracking match support
 "state" match support
-> IP: Netfilter Configuration
 IPv4 connection tracking support (required for NAT) 
[*] proc/sysctl compatibility with old connection 
tracking (NEW)
 IP Userspace queueing via NETLINK (OBSOLETE)
 IP tables support (required for filtering/masq/NAT)
 "ah" match support
 "ecn" match support
 "rpfilter" reverse path filter match support
 "ttl" match support
 Packet filtering
 REJECT target support
 ULOG target support
 IPv4 NAT
 MASQUERADE target support
 NETMAP target support
 REDIRECT target support
 Packet mangling
 
Before you start spending time rebuilding the kernel ...

Do you want to use DHCP to assign IP addresses to computers attached to 
the ethernet port?

What about DNS?

Have you considering disabling connman?

Regards
RLYON





On Tuesday, February 11, 2014 6:45:31 AM UTC+11, Mark Hatch wrote:
>
>
> Hi friends,
>
> Total newbie here, so forgive me.
>
> I'm
>  
> trying to add functionality to iptables so I can use the BBB as a ad-hoc 
> "router", sharing it's Ethernet connection with others.
>
> From what I've gleamed so far I need to add that functionality by 
> recompiling the kernel.
>
> So following the links at http://www.angstrom-distribution.org/ i cloned 
> the setup-scripts.
>
> MACHINE=beaglebone ./oebb.sh config beaglebone
>
> MACHINE=beagleboard ./oebb.sh update
>
> . environment-angstrom-v2013.06
>
> bitbake -c menuconfig virtual/kernel
>
> I then change the options I need, but when I built it made a zImage 
> file... Which confuses me.
>
> Now what I don't understand is that the image I want should be based off 
> the regular systemd image.
>
>
>- 
>
>bitbake systemd-image
>
>
> How do I update the kernel configuration from the systemd image without 
> just building the regular image?
>
> A step-by-step explanation would be awesome, cause I've never 
> customized/built the linux kernel before.
> I also do not have a serial cable yet. Is this necessary for running a 
> custom kernel? Do options in u-boot need to be changed?
>
> I'm sure I'm asking all the wrong questions, but would really appreciate 
> some help!
>
> Here are the options that I need:
>
> Networking  >
>  Networking options  >
>   Network packet filtering framework (Netfilter)--->
>Core Netfilter Configuration >
> <*> Netfilter connection tracking support
> <*> Netfilter Xtables support (required for ip_tables)
> <*>   "NFLOG" target support
> <*>   "conntrack" connection tracking match support
> <*>   "state" match support
>IP: Netfilter Configuration --->
> <*> IPv4 connection tracking support (required for NAT)
> <*> IP tables support (required for filtering/masq/NAT)
> <*>   Packet Filtering
> <*> REJECT target support
> <*>   Full NAT
> <*> MASQUERADE target support
> <*> Packet mangling
>
>

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

[beagleboard] Re: BBB+FreeBSD RELEASE-10: capes, i2c, UARTs, API and the device tree

[rchrdlyon1]

Hi,

FreeBSD does have an ARM port available. It does use device trees to 
specify hardware, but I don't know if the grammar is the same as that used 
in ARM linux. There is a specific FreeBSD port for Raspberry Pi, but I 
don't know if a BBB port is available.

The best place to check for this is the FreeBSD Wiki. You will need to be a 
pioneer to use FreeBSD on BBB.

Best of luck, etc ...


On Wednesday, January 22, 2014 5:55:08 AM UTC+11, smith.wi...@gmail.com 
wrote:
>
> I see that FreeBSD RELEASE-10 is out and runs on the BBB.  I have it 
> running in a VirtualBox VM (x64 version) and I'm interested enough to try 
> it on the BBB along with my cape & device tree overlay.
>
> Does anyone have *any* idea how to get my cape(s) working:
>
> * Does it support some kind of device-tree-overlay (dts) and/or capemgr?
> * Do I need to build a custom kernel to enable the BBB for things like 
> UART1, SPI0 and I2C
>
> Thanks!
>
>
> -W.
>
>

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

[beagleboard] Re: Angstrom Building for BBB instead of Beaglebone

[rchrdlyon1]

Hi,

I assume you query is in reference to Angstrom Linux?

The build procedure for BeagleBone Black is identical to BeagleBone White. 
The Angstrom web site is somewhat vague about this and many other things. I 
create a console-image root file system using the following:

mkdir Angstrom-v2013.06

cd ./Angstrom-v2013.06

git clone git://github.com/Angstrom-distribution/setup-scripts.git

cd setup-scripts

MACHINE=beaglebone ./oebb.sh config beaglebone

MACHINE=beaglebone ./oebb.sh update

And to compile the console version of the root file system distribution:

. environment-angstrom-v2013.06

bitbake console-image

This will also create u-boot files and a kernel.

You can be more specific and use

bitbake u-boot-denx

to create the u-boot files and

bitbake virtual/kernel

Some other targets are

systemd-imagewhich is a minimal root file system (no x windows)

and

systemd-gnome-image.bb
xfce-nm-image.bb
hardware-bringup-image.bb
development-gnome-image.bb





On Tuesday, January 21, 2014 2:31:18 AM UTC+11, Jan Zwiegers wrote:
>
> How do you configure or what recipes are there to specifically build for 
> BBB instead of BeagleBone?
> The only setups I can find is for BeagleBone.
>
> For instance this OE setup:
>
> $ MACHINE=beaglebone ./oebb.sh config beaglebone
>
> Is there a version for BBB?
>
> As well when building:
>
> $ MACHINE=beagleboard bitbake virtual/kernel
>
> At this moment I cannot figure out the difference and if one need to 
> specify it differently.
>
> Thanks!
>
>

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

[beagleboard] Re: 3G Modems

[rchrdlyon1]

Hi,

I assume you are looking at a 3G modem that interfaces and is powered by 
USB interface. There are a number of issues you have to resolve:

3G modems can draw can draw quite a bit of current. The current consumption 
is variable and depends upon modem activity and 3G signal level. It can 
exceed the BBB USB port current limit on the BBB. So you may need a USB hub 
to power the modem. As an example the Sierra wireless modem I used on the 
last project could draw up to 600 MA when attempting to register on the 3G 
network.

*Angstrom by default uses connman for network management and ofono for 
modem management*. Documentation for these tools is rather sparse and 
terse. Depending upon the modem you intend to use and your networking 
requirements, it is likely that you will have difficultly using 
connman/ofono. I have found it easier to disable connman:

systemctl daemon-reload
systemctl stop connman.service
systemctl disable connman.service

And then start networking using:

/etc/init.d/networking start

To manage the modem connection you can then use pppd in the traditional 
manner. It does work well. The exact method of setting up PPP depends upon 
your modem and carrier. The PPP manual pages are more than adequate.

Alternatively you could install NetworkManager/modem-manager, which might 
make the setup like a debian/ubuntu desktop.

Once you have this working you then need to consider the modem reliability. 
Some modems occasionally do soft resets and drop the USB connection. This 
is a problem for unattended remote operation. For my last project I 
discovered that the modem would intermittently drop the USB interface when 
the 3G signal level was low. This caused problems with PPP and we found it 
necessary to write a helper application to shutdown PPP when the USB 
connection to the modem dropped out and wait until the USB serial ports to 
the modem were re-established before starting PPP again. Hopefully you 
won't have such problems, but you need to do tests with low fluctuating 3G 
signal levels.

Hopefully you won't experience all the problems we had.

Regards ...

On Tuesday, January 7, 2014 12:15:58 AM UTC+11, verster...@gmail.com wrote:
>
> Hello
>
> As part of a project I am working on, it is required to use a 3G modem 
> connected to a Beaglebone Black as the BBB will be placed in a remote 
> location.
> I have acquired Sakis3G, and attempted to use some 3G modems, but they did 
> not work, and the script only told me that it was unable to connect to the 
> modem (eventhough it did pick it up).
>
> Does anyone know where I can find a list of 3G modems compatible with the 
> BBB, or reference me to a tutorial on how to connect to a 3G modem manually.
> One requirement I have is the modem must have a slot where a external 
> antenna can be connected.
>
> Thank you in advance!
> Cornel
>

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

[beagleboard] Angstrom v2013.12 is broken

[rchrdlyon1]

Hi,

Angstrom v2013.12 is broken. The feeds specified in /etc/opkg config files 
do not exist. This means any attempt to use opkg will fail. It is still 
possible to build v2013.12 root file system and install it on the 
beaglebone black. but you can't do much with it. Apparently this is caused 
by changes angstrom is undergoing with respect to hard float support on 
arm7a. Maybe it will be fixed later.

Has anyone experienced problems with V2013.06 when attempting to use opkg 
recently? It apparently has been changed to better support hard float, but 
there is a good chance that there will be problems.

v2012.12 still works.

Regards ...


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

[beagleboard] Re: angstrom build for beaglebone has texinfo issue

[rchrdlyon1]

Hi,
 
The texinfo package was installed from an Ubuntu repository and has the 
version number 4.13a.dfsg.1-8ubuntu. ie It is version 4.13. I suppose you 
have three choices, either install an older version of texinfo, use a 
different host or fix the problem in Angstrom.
 
The INHERIT change won't alter the outcome. I'm just trying to speed up 
kernel rebuilds.
 
Did you check that bash is indeed bash and not dash?
 
While the v2012.12 branch builds correctly, I have had problems with 
v2013.06 (libpseudo issues) and v2013.12 (dtc not included in rootfs) for 
different reasons. I have switched from a 64-bit Mint host back to 32-bit 
Xubuntu host to investigate these problems.
 
Hope this helps 
 

On Wednesday, November 27, 2013 4:24:17 AM UTC+11, Chris Morgan wrote:

> On Tue, Nov 26, 2013 at 9:57 AM,  > 
> wrote: 
> > Is this problem occurring while you are attempting to build the 
> > console-image? I just finished a build a few minutes ago using the 
> > following: 
> > 
> > This guide details the process of building a console image from the 
> Angstrom 
> > source on an Xubuntu 12.04.3 32-bit Linux host. 
> > 
> > Prerequisites 
> > 
> > Then we need some additional development tools. Enter the following: 
> > 
> > sudo apt-get install sed wget cvs subversion git-core coreutils 
> > unzip texi2html texinfo docbook-utils gawk python-pysqlite2 diffstat 
> > help2man make gcc build-essential g++ desktop-file-utils chrpath 
> > 
> > 
> > /bin/sh (ls -l /bin/sh) is symbolically linked to dash. "dash" is a 
> POSIX 
> > compliant shell that is much smaller than "bash". Some broken shell 
> scripts 
> > still make use of bash extensions while calling into /bin/sh. To work 
> around 
> > this issue call "sudo dpkg-reconfigure dash" and select No when it asks 
> you 
> > to install dash as /bin/sh. 
> > 
> > Download Angstrom Distribution and Build 
> > 
> > To download the distribution for Beaglebone enter the following 
> commands: 
> > 
> > cd ~/Projects 
> > 
> > mkdir angstrom-v2012.12 
> > 
> > cd ./angstrom-v2012.12 
> > 
> > git clone git://github.com/Angstrom-distribution/setup-scripts.git 
> > 
> > cd setup-scripts 
> > 
> > MACHINE=beaglebone ./oebb.sh config beaglebone 
> > 
> > MACHINE=beaglebone ./oebb.sh update 
> > 
> > In file setup-scripts/conf/local.conf modify the following line: 
> > 
> > INHERIT += "rm_work" 
> > 
> > to 
> > 
> > # INHERIT += "rm_work" 
> > 
> > And to compile the console version of the distribution: 
> > 
> > . ~/.oe/environment-angstromv2012.12 
> > 
> > bitbake console-image 
> > 
> > During these steps the computer must be connected to the Internet. 
> > 
> > Or are you trying to manually compile manual pages? 
> > 
> > 
>
>
> Hello. 
>
> I'm connected to the internet, I haven't made the changes to INHERIT 
> that you have and I'm trying to build the same target. Running on 
> Fedora 19 here. 
>
> Would you happen to know what version of texinfo you have? I have 
> version 5.1 here. 
>
> Chris 
>

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

[beagleboard] Re: angstrom build for beaglebone has texinfo issue

[rchrdlyon1]

Is this problem occurring while you are attempting to build the 
console-image? I just finished a build a few minutes ago using the 
following:

This guide details the process of building a console image from the 
Angstrom source on an Xubuntu 12.04.3 32-bit Linux host.

Prerequisites

Then we need some additional development tools. Enter the following:

sudo apt-get install sed wget cvs subversion git-core coreutils 
unzip texi2html texinfo docbook-utils gawk python-pysqlite2 diffstat 
help2man make gcc build-essential g++ desktop-file-utils chrpath


/bin/sh (ls -l /bin/sh) is symbolically linked to dash. "dash" is a POSIX 
compliant shell that is much smaller than "bash". Some broken shell scripts 
still make use of bash extensions while calling into /bin/sh. To work 
around this issue call "sudo dpkg-reconfigure dash" and select No when it 
asks you to install dash as /bin/sh. 

Download Angstrom Distribution and Build

To download the distribution for Beaglebone enter the following commands:

cd ~/Projects

mkdir angstrom-v2012.12

cd ./angstrom-v2012.12

git clone git://github.com/Angstrom-distribution/setup-scripts.git

cd setup-scripts

MACHINE=beaglebone ./oebb.sh config beaglebone

MACHINE=beaglebone ./oebb.sh update

In file setup-scripts/conf/local.conf modify the following line:

INHERIT += "rm_work"

to

# INHERIT += "rm_work"

And to compile the console version of the distribution:

. ~/.oe/environment-angstromv2012.12

bitbake console-image

During these steps the computer must be connected to the Internet.

Or are you trying to manually compile manual pages?

On Friday, November 22, 2013 11:25:39 AM UTC+11, chmo...@gmail.com wrote:
>
> I've heard that the texinfo issue with eglibc was fixed some time ago but 
> I'm seeing it on f19 64bit with git master of the angstrom 
> setup-scripts.git:
>
> | LANGUAGE=C LC_ALL=C makeinfo -P 
> /home/cmorgan/projects/angstrom-setup-scripts/build/tmp-angstrom_v2012_12-eglibc/work/armv7a-vfp-neon-angstrom-linux-gnueabi/eglibc-2.16-r15+svnr20393/build-arm-angstrom-linux-gnueabi/manual/
>  
> --output=/home/cmorgan/projects/angstrom-setup-scripts/build/tmp-angstrom_v2012_12-eglibc/work/armv7a-vfp-neon-angstrom-linux-gnueabi/eglibc-2.16-r15+svnr20393/build-arm-angstrom-linux-gnueabi/manual/
> libc.infolibc.texinfo
> | ./message.texi:1446: warning: @end should only appear at a line beginning
> | ./stdio.texi:3138: unknown command `hsep'
> | ./stdio.texi:3138: unknown command `vsep'
> | ./creature.texi:1: warning: node `Checking for Errors' is next for 
> `Feature Test Macros' in menu but not in sectioning
> | ./memory.texi:27: warning: node `Error Messages' is prev for `Memory 
> Concepts' in menu but not in sectioning
> | ./memory.texi:156: warning: node next `Memory Allocation' in menu 
> `Locking Pages' and in sectioning `Resizing the Data Segment' differ
>
>
> Steps to reproduce:
>
> git clone 
> https://github.com/Angstrom-distribution/setup-scriptsangstrom-setup-scripts
> cd angstrom-setup-scripts/
> MACHINE=beaglebone ./oebb.sh config beaglebone
> nano conf/local.conf # I enabled -j8 and 8 parallel steps to speed the 
> compile
> MACHINE=beaglebone ./oebb.sh update
> MACHINE=beaglebone ./oebb.sh bitbake console-image
>
>
> Not sure where to go from 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.
For more options, visit https://groups.google.com/groups/opt_out.

[beagleboard] Re: BBB USB Host issue

[rchrdlyon1]

Plug in FTDI module to usb host

Power up beagle

enter the following command:

 modprobe usbserial vendor=0x0403 product=0x6001

Hopefully after a second or so you will see a new entry in the dev 
directory.


On Saturday, November 16, 2013 9:07:25 AM UTC+11, rno...@gmail.com wrote:
>
> Hi,
>
> I working on a project where I need to use the USB host interface to 
> connect a FTDI module. The problem is that I can't see the  ttyUSB0. If I 
> do lsusb this is what I get:
>
> Bus 001 Device 002: ID 0403:6001 Future Technology Devices International, 
> Ltd FT232 USB-Serial (UART) IC
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>
> So the FTDI module is loaded, but still can't see the ttyUSB0. The kernel 
> version is 3.8.13. Does anyone have any advice on how to make this work? Do 
> I need to add a bone_cape or something else?
>
> Richard
>

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

[beagleboard] Missing dtc package for Angstrom V2013.12?

[rchrdlyon1]

Hi,

With Angstrom V2013.12 there appears to be no dtc package available. ie. 
the command


*opkg install dtc*
always fails with message

   *Unknown package 'dtc'.*

A slightly fatal problem, if you wish to use this version of Angstrom.

I suppose it is possible to download the latest dtc source, patch it, 
compile and then install. Not sure what patches are required and where I 
can source them from?

Regards ...

PS. Yes I did try *opkg update*


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

[beagleboard] Re: USB errors (and hotplug work-around)

[rchrdlyon1]

Have you tried a quick test using a usb hub? This would completely 
eliminate any issues with current drain.

I have found some usb devices have high transient current drains which can 
cause intermittent shutdowns of the USB port on the BBB. I know that you 
are powering your device with an external power supply, but maybe there are 
some issue with the hardware design in the device. A quick test with a hub 
might be revealing?

I have always disabled the USB runtime power management option in the 
kernel. Hot-plugging still seems to work for me, providing the USB device 
is connected during BBB power-up. (I am using Angstrom 2012.12 with the 
latest kernel patches). Where I need hot-plugging and cannot guarantee the 
device will be plugged in on power-up, then a hub must be used. I never 
tried polling with readlink or equivalent.

Regards ..

On Monday, May 13, 2013 2:08:32 AM UTC+10, Andrew Henderson wrote:
>
> Hello all.  I have been working on porting a project of mine (
> http://www.beaglesnes.org) from the BeagleBoard-xM over to the BeagleBone 
> Black.  I am running a Linux kernel based on the am33x-v3.8 branch of 
> Robert Nelson's linux-dev GitHub project.  It is similar to the kernel 
> built directly by the branch's build_kernel.sh script, but I've removed a 
> number of modules, unused file systems, etc. in order to make the kernel a 
> bit smaller.  I use the toolchain fetched by the build_kernel.sh script to 
> build the kernel.  The Linux distro underneath is an Ubuntu Quantal 12.10 
> armhf.  I'm using the v2013.04 u-boot release that I've built using an 
> arm-cortex_a8-linux-gnueabi cross-compiler toolchain (GCC 4.4.6) that I 
> built using crosstool-NG (v1.18.0).
>
> USB ERRORS:
>
> I have most of the issues worked out, but I'm still seeing some issues 
> with the USB subsystem on the board.  I picked back through several 
> thousand messages in the Google group, but I did not see my particular 
> issue addressed.  I will occasionally see the BBB refuse to enumerate an 
> HID gamepad plugged into the USB1 Host port with the following error:
>
> usb 1-1: device descriptor read/64, error -110
>
> My research has shown that a 110 error refers to being unable to enumerate 
> the USB device because power is exceeded.  I'm not sure why this would be 
> the case, since I am using a 5V power supply, rather than supplying power 
> via USB.  The gamepad being plugged into the Host port should not be 
> drawing a lot of power.  The odd thing is that the -110 error will occur 
> after multiple power cycles in a row, but then disappear.  At that point, 
> plugging in the gamepad will work fine for several more power cycles (the 
> USB device will enumerate and be properly identified).  There doesn't seem 
> to be any rhyme or reason to it.  It doesn't matter if the board is hot or 
> cold, if the reset button is pressed or not at the last power cycle, etc. 
>  I'll just get a string of either "working" or "not working" for the USB 
> device enumeration.
>
> I have tried playing with the kernel configuration a bit to see if I might 
> be able to remove this problem.  I tried removing EHCI support to force the 
> gamepad to be enumerated as a USB 1.1 device, since my research has shown 
> that going from USB 2.0 to 1.1 will reduce power usage for some devices. 
>  No luck there.  I also reviewed the patches currently in the GitHub 
> repository, but the closest one that I could see that might effect this is 
> the patch usb/0011-ARM-OMAP-am335x-musb-use-250-for-power.patch.  I didn't 
> see anything in the AM3359A errata that relates to this, either. 
>
> Any suggestions?  Has anyone seen something similar?  Are there any known 
> work-arounds?
>
> HOTPLUG WORK-AROUND:
>
> Some of you might have already seen something similar to this, but I 
> figure that it wouldn't hurt to share my approach on it.  My application 
> (BeagleSNES) supports the hotplugging of USB gamepads on the BB-xM, so I've 
> added support for this in userspace in my BBB port.  My review of 
> the usb/0009-MUSB-Hack-around-to-make-host-port-to-work.patch showed a 
> comment of "After removing the device, issue lsusb to cause it to scan 
> the bus again." Using lsusb doesn't work for me, but "cat 
> /dev/bus/usb/001/001 > /dev/null" does.  If I unplug the gamepad, plug it 
> back in, and then issue that shell command, an ls of "/dev/bus/usb/001" 
> will show that the gamepad has been enumerated again.  I do this 
> programmatically in my code using the following process:
>
> 1. I perform a "cat /dev/bus/usb/001/001 > /dev/null" in the launch script 
> for my app (called from rc.local) to scan the bus prior to start. 
> 2. In my application, I poll once per second or so via readlink() on the 
> file /dev/input/by-path/platform-musb-hdrc.1.auto-usb-0:1:1.0-joystick to 
> see if the gamepad is plugged in.
> 3. If it is plugged in, I make a note of it, open the proper /dev/jsX 
> file, and interact with the gamepad.
> 4. If the gamepad

[beagleboard] Re: kernel-module-iptable-nat / share internet

[rchrdlyon1]

Hi,

I did a similar thing except with a Sierra 3G USB modem providing a 
VOICE/Internet connection and client computers connecting via eth0. So my 
experience has some relevance. I found it necessary to not use CONNMAN, 
otherwise it appeared to be impossible to use ppp. My project requires the 
main AT interface to be used to manage voice communication (dialling, 
answer and hangup, etc ...) and a second data interface is used for data 
connection. pppd is used to manage the second data interface. This is 
totally incompatible with connman/ofono unless I'm prepared to modify 
ofono. Also pppd runs as an autonomous entity handling the data connection 
completely independent of the voice connection. Try doing that with ofono?

Angstrom 2012.12 with kernel 3.8.13 needs to be recompiled to support NAT 
with the following settings for IPV4

*Enable NAT:*

-> Networking support (NET [=y])
-> Networking options
-> Network packet filtering framework (Netfilter) (NETFILTER 
[=y])
-> Core Netfilter Configuration
 Netfilter connection tracking support
{M} Netfilter Xtables support (required for ip_tables)
*** Xtables combined modules ***
 "NFLOG" target support
 "conntrack" connection tracking match support
 "state" match support
-> IP: Netfilter Configuration
 IPv4 connection tracking support (required for NAT) 
[*] proc/sysctl compatibility with old connection 
tracking (NEW)
 IP Userspace queueing via NETLINK (OBSOLETE)
 IP tables support (required for filtering/masq/NAT)
 "ah" match support
 "ecn" match support
 "rpfilter" reverse path filter match support
 "ttl" match support
 Packet filtering
 REJECT target support
 ULOG target support
 IPv4 NAT
 MASQUERADE target support
 NETMAP target support
 REDIRECT target support
 Packet mangling

To implement the connection to the modem I decided to ditch connman/ofono 
and revert to pppd. So I configured /etc/network/interfaces to handle the 
ethernet

*Ethernet Interface*

I wanted a static IP address on the ethernet. (ppp0 interface address is 
dynamically assigned by 3G system).

Modify the file /etc/network/interfaces to contain the following:

# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)
 
# The loopback interface
auto lo
iface lo inet loopback

# Wired interfaces
auto eth0
iface eth0 inet static
address 192.168.0.1
netmask 255.255.255.0
network 192.168.0.0
gateway 192.168.0.2

Modify the file /etc/resolv.conf to contain the following:

# Generated by Connection Manager
nameserver 8.8.8.8

*Connman*

Disable the connman network service with the following commands

systemctl daemon-reload

systemctl stop connman.service

systemctl disable connman.service

*Network Service*

Create a file /lib/systemd/networking.service which contains:

[Unit]
Description=Run the Networking Service
After=syslog.target

[Service]
Type=simple
ExecStartPre=/bin/sh -c 'iptables-restore < /etc/iptables.sav'
ExecStart=/etc/init.d/networking start

[Install]
WantedBy=multi-user.target

Create a link to the networking service file

cd /etc/systemd/system

ln -f /lib/systemd/networking.service networking.service

Start the service:

systemctl daemon-reload

systemctl enable networking.service

*IPTABLES*

For forwarding, modify line in the file /etc/sysctl.conf

# net.ipv4.ip_forward=1

to 

net.ipv4.ip_forward=1

Set-up the routing with the command:

cd /etc

   * iptables -t nat -A POSTROUTING -o ppp0 -j MASQUERADE*

iptables-save > /etc/iptables.sav

Reboot the machine. It should possible to connect a PC to the beagle via 
Ethernet.

*DHCP*

To provide a dhcp server I decided to use *dnsmasq* as it did nice things 
like ensure the correct namerserver addressing was passed to the dhcp 
clients. You will need to download the source code and compile it yourself.

It works rather well. I'm getting 7.2 MBits/sec download and 5 MBIts/sec 
upload (Telstra NextG carrier) which is good for pppd. pppd ensures default 
route is via ppp0 while connection is up. The project was/is to build a 
not-so-mobile phone for use in the rail industry.

Regards ...

On Wednesday, October 16, 2013 11:23:59 PM UTC+11, Max Baum wrote:
>
> Hello
>
> I want to share the internet connection of eth0 with wlan0. (like wifi 
> AP,  hostapd and dhcp-

[beagleboard] Re: Compile Angstrom for Beagle Bone black.

[rchrdlyon1]

This guide details the process of building a Beaglebone (White/Black) 
console image from the Angstrom source on an Ubuntu Linux host. In theory 
you could do this on the target, but it will take a very time and you may 
run out of memory (both NAND and RAM).

*Prerequisites
*
Then we need some additional development tools. Enter the following:

sudo apt-get install sed wget cvs subversion git-core coreutils 
unzip texi2html texinfo docbook-utils gawk python-pysqlite2 diffstat 
help2man make gcc build-essential g++ desktop-file-utils chrpath dosfstools 
kpartx

And finally we need bitbake:

sudo apt-get install bitbake

*Download Angstrom Distribution and Build*

To download the distribution for Beaglebone enter the following commands:


cd ~/Projects

mkdir angstrom-v2012.12

cd ./angstrom-v2012.12

git clone git://github.com/Angstrom-distribution/setup-scripts.git

cd setup-scripts

git checkout angstrom-v2012.12-yocto1.3

MACHINE=beaglebone ./oebb.sh config beaglebone

MACHINE=beaglebone ./oebb.sh update

In file setup-scripts/conf/local.conf modify the following line:

INHERIT += "rm_work"

to

# INHERIT += "rm_work"

And to compile the console version of the distribution:

. ~/.oe/environment-angstromv2012.12

bitbake console-image

During these steps the computer must be connected to the Internet. The 
resulting MLO, u-boot.img and root file system are found in:


~/Projects/angstrom-v2012.12/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/deploy/images/beaglebone

It takes a while for all of this to complete.

On Tuesday, October 15, 2013 8:22:18 PM UTC+11, ashish@xzadium.com 
wrote:
>
> Hello,
>
> I want to use Angstrom linux on Beangle bone black. I come across some 
> steps used to compile Angstrom (from source code) for *BeagleBone* but 
> not for *BeagleBone black.* so My query is:
>
> 1) Can I directly use the images compiled for BeagleBone on BeagleBone 
> Black? If not, can you please refer me some good reference links for the 
> same?
>
> 2) In other linux distribution (like ubuntu), we need MLO, u-boot, uImage 
> & file system image to boot up the board. To use Armstrom on I am following 
> compilation steps from this link:
> http://www.angstrom-distribution.org/building-angstrom. And at the end, 
> it generated uImage. So where are the other components (MLO,, uboot, file 
> system)?Do we need to compile them separately from other source code?
>
> 3) I found different different steps to push the images on Beagle Bone. 
> Can you please refer me what steps I should use?
>
> Thank,
> Ashish
>
>

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

[beagleboard] Re: Which branch for building OE? v2012.12-yocto1.3 still or v2013.06-yocto1.4?

[rchrdlyon1]

Thanks,

That seems to work. It will take a couple more hours to finish. Then we 
will start looking at exactly what has changed.

Step 5 had to be modified as the ~/.oe directory is no longer used. No big 
deal.

Regards 

On Tuesday, October 15, 2013 3:46:52 PM UTC+11, smith.wi...@gmail.com wrote:
>
> On Monday, October 14, 2013 6:31:12 AM UTC-4, rchrd...@gmail.com wrote:
>>
>> How does one use git to select angstrom-v2013.06. I would hope this later 
>> branch has USB driver fixes included (ie babble and hotplug).
>>
>>>
>>>
> It's just a question of which branch you're in, after step #2 in your 
> list, do:
>
> git checkout angstrom-v2013.06-yocto1.4
>
> Then continue with step #3 onwards (step #5 will have a suffix of 
> ...2013.06 rather than 2012.12).
>
>
> -W
>
>

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

[beagleboard] Re: Which branch for building OE? v2012.12-yocto1.3 still or v2013.06-yocto1.4?

[rchrdlyon1]

Hi,

I'm currently building  angstrom-v2012.12console-image using following 
commands:

   1. git clone git://github.com/Angstrom-distribution/setup-scripts.git
   2. cd setup-scripts
   3. MACHINE=beaglebone ./oebb.sh config beaglebone
   4. MACHINE=beaglebone ./oebb.sh update
   5. . ~/.oe/environment-angstromv2012.12
   6. bitbake console-image

How does one use git to select angstrom-v2013.06. I would hope this later 
branch has USB driver fixes included (ie babble and hotplug).

Regards ...


On Monday, October 14, 2013 3:23:36 PM UTC+11, smith.wi...@gmail.com wrote:
>
> On Friday, October 11, 2013 11:03:16 AM UTC-4, smith.wi...@gmail.comwrote:
>>
>> Last time I built OE for the BBB, the recommendation was to 
>> use angstrom-v2012.12-yocto1.3 as angstrom-v2013.06-yocto1.4 didn't 
>> compile.  That was in August, now I see that there's 
>> a angstrom-v2013.12-yocto1.5 in 
>> https://github.com/Angstrom-distribution/meta-angstrom/blob/master/README
>>
>> 1) Does this mean angstrom-v2013.06-yocto1.4 is now "stable" and I should 
>> be using this?  
>> 2) What branch was the 2013.09.04 production release built with?
>>
>>
> To answer my own query, I built both and they both work.  So I guess 
> angstrom-v2013.06-yocto1.4 is "newer".
>
>

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