|BeagleBone announcement||Jason Kridner||11/1/11 9:03 AM|
There's a new dog in the pack! The BeagleBone was announced
yesterday. For those of you hanging out at
http://beagleboard.org/chat, you've probably been hearing about it for
about a month. It is real, but there are still very few of them out
there. I am mailing some A2 boards out to some key
partners/developers now, but the production version, A3, is going
straight to ramp-mode. The only difference is a change in the
Ethernet PHY to improve the throughput, which we are now quite happy
with how it is getting around 95Mbps under iperf.
The BeagleBone schematics and BOM are now up on
The page for updates is http://beagleboard.org/bone. I'll try to get
===What is the BeagleBone?===
===How can I buy one?===
===How does Linux make the BeagleBone easier to use than a
===What does this mean for the future of the BeagleBoard and the
===When will the BeagleBone be available?===
===How much will the BeagleBone cost?===
===Is this just a TI marketing gimmick?===
Several semiconductor manufacturers are attempting to duplicate the
The current open hardware movement is much akin to early home computer
===Why aren't the BeagleBone expansion headers compatible with the Arduino?===
We are anxious to work with open hardware partners looking to generate
===What are the export restrictions?===
===What is the processor used in the board?===
===Is there a road-map for peripheral boards?===
Plans for a Wi-Fi+Battery board are still in the very preliminary
===If I want to make a "cape", is there a starting point?===
We'll generally refer to them as "capes" because Underdog is a beagle
===Is this board a stand-alone board or is it supposed to be used in
===What if I already have a JTAG-based debugger?===
===How do I get software to run on the BeagleBone?===
===Where is the software source code?===
===What if I just want the boot-loader and kernel sources?===
|Re: [beagleboard] BeagleBone announcement||Sid Boyce||11/1/11 9:39 AM|
This is already causing a buzz right across the SDR (Software Defined
One post wondered if ... I quote:-
The McASP is very capable and much more sophisticated than the Atmel's
The processor also has the horsepower and FPU desired, and at $89 it is
Looks like a good candidate to design a multichannel audio-widget.
Damien Martin mentioned before that TI itself might be very interested
|Re: [beagleboard] BeagleBone announcement||vladimir||11/1/11 11:11 AM|
Jason Kridner wrote:
I, for one, welcome our new bony overlords
|Re: [beagleboard] BeagleBone announcement||lopsta.e...@googlemail.com||11/3/11 1:14 AM|
so this board runs linux, but it is also easily programmabel as a microcontroller, right?
what language is used for the microcontroller part?
coming from the Arduino, how would i for example integrate image recognition via OpenCV with controlling IO ports for a robotic application. One part is a Linux application, the other is my custom code, how do both communicate with each other?
I think this is a game changer and what i see so far i really love the concept. specially the onboard IDE is mindblowing. having said that as a hardcore Arduino user.
|Re: [beagleboard] BeagleBone announcement||Jason Kridner||11/3/11 7:57 AM|
On Thu, Nov 3, 2011 at 4:14 AM, <lopsta.e...@googlemail.com> wrote:
I wouldn't say it can be programmed as a microcontroller, per se, but
There is a processing element called a PRU. My plan is enable
Right now, the challenge is to get the hardware out there, knowing
I expect a lot of platforms to be able to utilize the software once we
> what language is used for the microcontroller part?
> coming from the Arduino, how would i for example integrate
You have all the mechanisms of Linux to have them communicate.
> I think this is a game changer and what i see so far i really love the
Thanks! I've really wanted to get it out there so that people realize
|Re: [beagleboard] BeagleBone announcement||lazarman||11/3/11 12:00 PM|
Uh easily programmable?
Linux device drivers required
From Android 4G on HTC Sense dual core SnapDragon.
what language is used for the microcontroller part?
coming from the Arduino, how would i for example integrate
I think this is a game changer and what i see so far i really love the--
You received this message because you are subscribed to the Google Groups "Beagle Board" group.
To view this discussion on the web visit https://groups.google.com/d/msg/beagleboard/-/atPoS5w4Vy0J.
To post to this group, send email to beagl...@googlegroups.com.
To unsubscribe from this group, send email to beagleboard...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/beagleboard?hl=en.
|Re: [beagleboard] BeagleBone announcement||Jason Kridner||11/3/11 12:48 PM|
On Thu, Nov 3, 2011 at 3:00 PM, laza...@yahoo.com <laza...@yahoo.com> wrote:
> Uh easily programmable?
That's the idea, but it'll simplify over time. If you are looking for
> Linux device drivers required
No Linux device drivers that haven't already been shipping for years
We used a USB PID registered to TI (the one for the XDS100v2) for the
Of course, the other ways to interface your Linux PC to it, such as
And, of course, you are always free to replace the entire system code.
The build process is better aligned with upstream than previous board
|Re: [beagleboard] BeagleBone announcement||mrShu||11/3/11 1:03 PM|
May I ask you guys how many PWM outputs does the BeagleBone have?
Thanks in advance.
|Re: [beagleboard] BeagleBone announcement||Gerald||11/3/11 1:15 PM|
Up to 8.
|Re: [beagleboard] BeagleBone announcement||mrShu||11/3/11 1:18 PM|
|Re: [beagleboard] BeagleBone announcement||Jason Kridner||11/3/11 1:41 PM|
On Thu, Nov 3, 2011 at 4:18 PM, mr.Shu <mrs...@gmail.com> wrote:
With some concern of getting too far ahead of myself: not in the
|Re: BeagleBone announcement||Albert||11/4/11 3:16 AM|
Beaglebone is a direct competitor to Arduino! Great work, TI!
> >>> On 3 November 2011 19:48, Jason Kridner <jkrid...@beagleboard.org> wrote:
> >>>> On Thu, Nov 3, 2011 at 3:00 PM, lazar...@yahoo.com <lazar...@yahoo.com>
|Re: BeagleBone announcement||Tawez||11/4/11 6:07 AM|
On Nov 1, 5:03 pm, Jason Kridner <jkrid...@beagleboard.org> wrote:Realy great idea!
It will be my next toy^Wtool ;)
There is one thing, I don't like:
The Ethernet socket is located too close to the "line" of expansion
sockets (as I can see on BeagleBone photos).
This will bring some pain for cape designers and DIY makers, because
every cape will have to have additional cut in the pcb for ethernet
All the rest seems to be SUPERB!
|Re: [beagleboard] BeagleBone announcement||Koen Kooi||11/4/11 7:54 AM|
> On Nov 1, 5:03 pm, Jason Kridner <jkrid...@beagleboard.org> wrote:
Yes, you can see that cut in action at http://www.flickr.com/photos/koenkooi/6301342037/in/photostream
|Re: [beagleboard] Re: BeagleBone announcement||Gerald||11/4/11 7:55 AM|
That is why the cape has a notch in it. It acts a s a key to make sure the boards are not plugged in backwards. Yo uwill be able to learn mor eon this when I release the SRM on Monnday.
|Re: [beagleboard] Re: BeagleBone announcement||Gerald||11/4/11 7:56 AM|
That is why they are called capes!
|Re: [beagleboard] Re: BeagleBone announcement||Jan Detlefsen||11/4/11 8:00 AM|
i think the cut is okay, all capes will just have it. it's also not a
big deal to get PCBs produced in those shapes.
are there any files available to start tinkering with some ideas for capes?
|Re: BeagleBone announcement||Mark A. Yoder||11/4/11 8:04 AM|
I'd like to know more about the PRU. Is this something that's on the other Beagles?
|Re: [beagleboard] Re: BeagleBone announcement||Gerald||11/4/11 8:05 AM|
We are working on making those files available. It will be a few weeks before they are ready. The SRM wil have the dimensions on it.
|Re: [beagleboard] Re: BeagleBone announcement||Jason Kridner||11/4/11 8:39 AM|
On Fri, Nov 4, 2011 at 11:04 AM, Mark A. Yoder <mark.a...@gmail.com> wrote:
PRU is new and, honestly, the software support will be immature for it
|Re: [beagleboard] Re: BeagleBone announcement||Jan Detlefsen||11/4/11 8:11 AM|
sorry what does SRM stand for? is that a file format?
|Re: [beagleboard] Re: BeagleBone announcement||Charlie||11/4/11 8:35 AM|
Why not just use the longer pin headers like we do with the Arduino?
That way you don't have to cut the PCB in weird shapes and you get more
space for schtuff.
|Re: [beagleboard] Re: BeagleBone announcement||Gerald||11/4/11 8:49 AM|
System Reference Manual. It is a PDF document.
|Re: [beagleboard] Re: BeagleBone announcement||Gerald||11/4/11 8:51 AM|
It acts as a key. We have symmetrical connectors with no key to prevent a person from plugging in the board backwards.If someone wants to create a board with longer pins, then they may do so.
|Re: [beagleboard] Re: BeagleBone announcement||Jayanth Acharya||11/4/11 9:28 AM|
On Fri, Nov 4, 2011 at 3:46 PM, Albert <light...@gmail.com> wrote:Beaglebone is a direct competitor to Arduino! Great work, TI!
These are really exciting times and Beaglebone is truly exhilarating news, however Arduino's are in an altogether different league, in spite of it's very humble specs.
The popularity of Arduinos is not their hardware, i.e. the Arduino boards, or the sheilds. It is the software and the level it abstracts the hardware to.
Hardware more capable and elegant have existed before Arduino (Wiring! mbeds, the wide range of Olimex's), or ones that were hacker friendly (Propellers), but Arduino stole it, because of it's software, it's beautiful software-hardware integration, open-source everything and a very inclusive approach to the community. This, in spite of the fact that, as a company Atmel isn't easy to deal with, from hacker community standpoint. Try ordering samples from them :-)
More than a year back (or so), when MSP430's Valueline protoboards started selling for $4.30 (including shipping, expedited 2nd day, world-wide -- for free), people said that it's an Arduino killer. With the order of magnitude price difference, it ought to have been, but unfortunately none of that happened. Reason is anyone's guess.
IMHO, key to Beaglebone (or other similar) board's true mass adoption will be driven to a large extent by software ease-of-use without sacrificing flexibility. The good thing is that a POSIX kernel/OS and userland comes for free in form of Linux / Android, once the BSP is ported. However, asking a newbie who has tried building their own Angstrom kernel+root image, how they fared, I think it's clear that lot needs to be done. The Beagles are lot more complex and capable beasts, and software to tame / harness them is an order-of-magnitude harder. For a artist-hacker, or an embedded n00b, Android learning curve is nothing compared to the Beagle's learning curve, or the effort to get a Beagle to a point where it is usable. I guess, the day Beagles get Arduino like (from ease and don't-make-me-think) SDK / developer capabilities, the scale of adoption might drive the price in the current Arduino ranges (Ah, dreaming, already).
|Re: BeagleBone announcement||Andy||11/4/11 3:12 PM|
On Nov 4, 10:35 am, Charlie Fullerton <cwfullerton21...@gmail.com>
> Why not just use the longer pin headers like we do with the Arduino?
> That way you don't have to cut the PCB in weird shapes and you get more
> space for schtuff.
> On 11/4/2011 11:00 AM, Jan Detlefsen wrote:
While on the topic of headers, it looks to me like there's a serious
lack of return (ground) pins on the connectors.
I was looking at doing something with the LCD interface, and you have
24 high speed signals and clock all jammed into one header with two
ground pins at the other end. There are no source terminations on the
LCD lines. I expect if you try to run those directly to a typical
panel with a few inches of FPC tail or some cable, the signals are
going to look mighty bad by the time they cross a couple of
connectors, cable, and get to the receiver.
|Re: BeagleBone announcement||Tawez||11/4/11 4:20 PM|
Ok. This is a good reason to have this notch ;)
On Nov 4, 3:55 pm, Gerald Coley <ger...@beagleboard.org> wrote:
> That is why the cape has a notch in it. It acts a s a key to make sure the
> boards are not plugged in backwards. Yo uwill be able to learn mor eon this
> when I release the SRM on Monnday.
> On Fri, Nov 4, 2011 at 8:07 AM, Tawez <tawe...@gmail.com> wrote:
> > On Nov 1, 5:03 pm, Jason Kridner <jkrid...@beagleboard.org> wrote:
> > > There's a new dog in the pack! The BeagleBone was announced
> > > yesterday.
> > Realy great idea!
> > It will be my next toy^Wtool ;)
> > There is one thing, I don't like:
> > The Ethernet socket is located too close to the "line" of expansion
> > sockets (as I can see on BeagleBone photos).
> > This will bring some pain for cape designers and DIY makers, because
> > every cape will have to have additional cut in the pcb for ethernet
> > socket :|
> > All the rest seems to be SUPERB!
> > --
> > Best Regards
> > Tawez
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Beagle Board" group.
> > To post to this group, send email to beagl...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > beagleboard...@googlegroups.com.
> > For more options, visit this group at
|Re: [beagleboard] Re: BeagleBone announcement||Gerald||11/4/11 4:50 PM|
On th etopic of ground pins, if you look at the BeagleBoard and BeagleBoard-xm we have even less grounds. We have no issue driving LCDs in that configuration. We always add a buffer there as we have to do voltage level translation. On the BeagleBone, We have DVID board working today with a buffer and the source terminations on the DVI-D board. It looks very nice!
|Re: BeagleBone announcement||W5UXH||11/4/11 8:30 PM|
On Nov 3, 8:57 am, Jason Kridner <jkrid...@beagleboard.org> wrote:
> There is a processing element called a PRU. My plan is enable
> multiple "loop" functions to be created and to perform introspection
> on those loops to identify if the loop can be moved entirely to a PRU.
> A PRU has a ultra-low-latency response to the GPIO pins connected to
Without any understanding of the PRU, I wonder if it will be possible
to have "ultra-low-latency" response to internal timer interrupts? My
interest is to be able to set a timer to generate durations as short
as 12 msec, with precision on the order of 100 usec, so that I am able
to set the logic state of a GPIO pin to logic 1 ("ON") and turn it
back off after time out. I would like to be able to do this in a C
environment (dropping to assembly if required). I would need the same
precision for off durations (e.g. the capability of creating a square
wave of 12 msec on, 12 msec off). In actual operation, the on / off
cycles would be variable, not true square waves. Also, 12 msecs is
the extreme minimum duration (this is the length of a morse code "dot"
at 100 wpm).
I currently plan to investigate the use of my new Beagleboard-XM to
see if it is possible to do this with High Resolution Timers, but the
PRU comments from Jason about ultra-low-latency and real hard time for
the Beaglebone certainly caught my attention.
(I do not recall if the list standard is top or bottom posting, so I
apologize it I chose wrong.)
|Re: BeagleBone announcement||Mark A. Yoder||11/7/11 10:37 AM|
When will we see Cloud9 running on the Beagle? I'm ready to start playing with it.
|Re: [beagleboard] Re: BeagleBone announcement||Koen Kooi||11/7/11 11:19 AM|
opkg install cloud9 works in recent angstrom builds
|Re: BeagleBone announcement||Mark A. Yoder||11/7/11 1:48 PM|
Hmmm.... doesn't work for me. It doesn't appear in opkg list
How do I check the age of my distribution?
|Re: [beagleboard] Re: BeagleBone announcement||Jason Kridner||11/7/11 2:05 PM|
On Mon, Nov 7, 2011 at 4:48 PM, Mark A. Yoder <mark.a...@gmail.com> wrote:
I believe it is only on Angstrom-core. You'd need to switch to that.
> --Mark> https://groups.google.com/d/msg/beagleboard/-/gSbjNMokLGEJ.
|Re: BeagleBone announcement||Mark A. Yoder||11/8/11 7:33 AM|
Does that mean when I go to  to build an image for Choose the complexity of the options below I select 'advanced' and for Select the release you want to base your rootfs image on. I select 'core-eglibc'?
|Re: [beagleboard] Re: BeagleBone announcement||Jason Kridner||11/8/11 7:44 AM|
Yes. Each of the three options are built from different revision
|Re: BeagleBone announcement||Lolo-A8||11/19/11 11:45 AM|
The two PRUs make this chip quite interesting (the $5 price too
In my designs, I usually have a lot of switches, A/B encoders,
potentiometers and LEDs to read and drive.
Those are very simple operations but usually requires a lot of
multiplexing (using external muxes or creating a matrix) at fairly
high rate especially for the A/B encoders where you might not want to
miss any events.
I think the PRUs will be wonderful for that without taxing the main
core at all.
If I had to do that in the past, I might have used a simple external
micro, communicating with the main micro that runs linux using UART,
I2C or SPI.
Now, it is probably not necessary anymore thanks to PRU, as long as
there are enough free GPIOs :)
From what I understand, you could also do high resolution PWM on any
GPIOs thanks to PRU (?)
It would be amazing if this chip could be programmed like a micro-
Do you have an idea on the minimum time it takes the beaglebone to
> On Fri, Nov 4, 2011 at 11:04 AM, Mark A. Yoder <mark.a.yo...@gmail.com> wrote:
> > I'd like to know more about the PRU. Is this something that's on the other
> > Beagles?
> PRU is new and, honestly, the software support will be immature for it
> for a while. You can find it on the OMAP-L138 and AM1808 as well. I
> have a roadmap to have support for it in bonescript by Summer.
> > --Mark
|Re: BeagleBone announcement||Johannes Klug||11/22/11 3:37 AM|
On Nov 1, 5:03 pm, Jason Kridner <jkrid...@beagleboard.org> wrote:> ===How does the BeagleBone compare to the current BeagleBoard or
> The BeagleBoard-xM is still the extra MIPS and extra memory
> BeagleBoard with the greatest USB host expansion capabilities. If the
> original BeagleBoard has all the horsepower and USB host capabilities
> you need, but what you really want is easier and more extensive
> expansion, on-chip Ethernet, analog-to-digital data conversion and a
> lower cost, then the BeagleBone is the BeagleBoard for you.
Is there an analog-to-digital converter on board? What are its
How many digital I/O pins are there to use?
I could not find that information on the website.
|Re: [beagleboard] Re: BeagleBone announcement||Gerald||11/22/11 6:24 AM|
You might try checking out the datasheet for the processor. The Technical Reference Manual will be helpful as well.
|Re: BeagleBone announcement||MRO||11/28/11 6:59 AM|
I am new to Linux but I'd like use Android on Beaglebone.
Waiting to buy my BeagleBone, is there any tutorial which I can start
Is it necessary use a Linux(ubuntu) Host to deal with Beagleboards, or
|Re: [beagleboard] Re: BeagleBone announcement||Jason Kridner||11/28/11 1:22 PM|
On Mon, Nov 28, 2011 at 9:59 AM, MRO <mro...@phxtecno.com> wrote:
Depends on what you want to do. You can do quite a bit with a Windows host.
|Re: BeagleBone announcement||David||12/2/11 8:41 PM|
Why only 10/100 Base=T and not 10/100/1000 Base-T?
Just wondering. Also does anyone know of an a 1000 Base-T to SPI
|Re: [beagleboard] Re: BeagleBone announcement||Gerald||12/2/11 9:12 PM|
10/100 is less expensive and it is also good enough. We had a price point we needed to hit and it was a fight to get there.
|Re: BeagleBone announcement||David||12/5/11 9:14 AM|
That is understandable. Too bad because I was thinking that it could
make a really good router/firewall/wifi device. Make a shield with a
second NIC, wifi, and maybe a few sata ports and you have one heck of
Of course it is a very interesting device as it is for a large number
On Dec 3, 12:12 am, Gerald Coley <ger...@beagleboard.org> wrote:
> On Fri, Dec 2, 2011 at 10:41 PM, David <lwat...@gmail.com> wrote:
|Re: [beagleboard] Re: BeagleBone announcement||Gerald||12/5/11 9:26 AM|
There is always some functionality sacrificed when it comes to cost!
|Re: [beagleboard] Re: BeagleBone announcement||Stanley Seibert||12/5/11 9:40 AM|
On a semi-related question:
Is there any clever way to connect a USB device on a cape to the USB bus on the BeagleBone without a separate cable between the two boards?
|Re: [beagleboard] Re: BeagleBone announcement||Gerald||12/5/11 10:37 AM|
Not that I can think of.
|Re: BeagleBone announcement||David||12/5/11 2:17 PM|
Is the ethernet port intergrated into the chipset? Just wondering if
working from the beagle bone one could spin a board with 1000 Base-T.
|Re: [beagleboard] Re: BeagleBone announcement||Jason Kridner||12/5/11 2:42 PM|
On Mon, Dec 5, 2011 at 5:17 PM, David <lwa...@gmail.com> wrote:
Yes, the chip has a dual gigabit Ethernet switch.
|Re: BeagleBone announcement||Leon||12/18/11 5:00 AM|
I've ordered a BeagleBone from Mouser. For some reason, they have had
to apply for permission to export the board to me in the UK and I've
had to complete an End User Certificate.
|Re: BeagleBone announcement||Jamie Laing||12/18/11 3:40 PM|
Beaglebone takes a picture of itself...
> yesterday. For those of you hanging out athttp://beagleboard.org/chat, you've probably been hearing about it for
> about a month. It is real, but there are still very few of them out
> there. I am mailing some A2 boards out to some key
> partners/developers now, but the production version, A3, is going
> straight to ramp-mode. The only difference is a change in the
> Ethernet PHY to improve the throughput, which we are now quite happy
> with how it is getting around 95Mbps under iperf.
> The BeagleBone schematics and BOM are now up onhttp://beagleboard.org/hardware/design. The system reference manual
> and other docs should be showing up later this week.
> The page for updates ishttp://beagleboard.org/bone. I'll try to get
> a blog post out later today as well, but no promises there. Other
> people's posts seem to be telling most of the news anyway. For those
> of you too lazy to bring up a browser window, here are the current
> contents ofhttp://beagleboard.org/bone(without all of the links,
> videos or pictures):
> ===What is the BeagleBone?===
> The BeagleBone is the low-cost, high-expansion hardware-hacker focused
> BeagleBoard. It is a bare-bones BeagleBoard that acts as a USB or
> Ethernet connected expansion companion for your current BeagleBoard
> and BeagleBoard-xM or works stand-alone. The BeagleBone is small even
> by BeagleBoard standards and with the high-performance ARM
> capabilities you expect from a BeagleBoard, the BeagleBone brings
> full-featured Linux to places it has never gone before.
> ===How can I buy one?===
> Distributors are coming on-line now and enabling pre-orders. Boards
> should ship to distributors before the end of November. Find the
> currently on-line distributors athttp://beagleboard.org/buy.
> ===What is the BeagleBone capable of doing?===
> At over 1.5 billion Dhrystone operations per second and vector
> floating point arithmetic operations, the BeagleBone is capable of not
> just interfacing to all of your robotics motor drivers, location or
> pressure sensors and 2D or 3D cameras, but also running OpenCV, OpenNI
> and other image collection and analysis software to recognize the
> objects around your robot and the gestures you might make to control
> it. Through HDMI, VGA or LCD expansion boards, it is capable of
> decoding and displaying mutliple video formats utilizing a completely
> open source software stack and synchronizing playback over Ethernet or
> USB with other BeagleBoards to create massive video walls. If what you
> are into is building 3D printers, then the BeagleBone has the
> extensive PWM capabilities, the on-chip Ethernet and the 3D rendering
> and manipulation capabilities all help you eliminate both your
> underpowered microcontroller-based controller board as well as that PC
> from your basement.
> ===What are the detailed hardware specifications?===
> Keep coming back! These will be updated soon. Some additional details
> are in the latest BeagleBoard.org flyer.
> Board size: 3.4" x 2.1"
> Shipped with 2GB microSD card with the Angstrom Distribution with
> node.js and Cloud9 IDE
> Single cable development environment with built-in FTDI-based
> serial/JTAG and on-board hub to give the same cable simultaneous
> access to a USB device port on the target processor
> Industry standard 3.3V I/Os on the expansion headers with easy-to-use
> 0.1" spacing
> On-chip Ethernet, not off of USB
> Easier to clone thanks to larger pitch on BGA devices (0.8mm vs.
> 0.4mm), no package-on-package memories, standard DDR2 vs. LPDDR,
> integrated USB PHYs and more.
> Where are the design materials?
> These are still being updated ahead of boards shipping, but you can
> find the latest versions always on the BeagleBoard.org Hardware Design
> ===How does Linux make the BeagleBone easier to use than a
> microcontroller-based platform?===
> The advantage of full-featured Linux is the Linux community. While the
> template-based coding of systems like the Arduino make it easy to
> copy-and-paste simple projects and a limited number of more complex
> libraries that don't have a lot of interaction, 20 years of Linux
> development have generated an extensive set of highly interoperable
> software that can be utilized and collaborated upon, without
> sacrificing the simplicity of doing something like toggling an LED or
> switch or reading an analog or I2C-based sensor.
> language interpreter with a rapidly growing community. The evented I/O
> model enables both building highly scalable web servers and being
> responsive to the many sensors within your embedded system. As part of
> the shipping image with the BeagleBone, we are looking to provide the
> git-enabled Cloud9 IDE that allows you to edit node.js applications
> directly over your web browser by simply pointing it to the
> BeagleBone. While this technology will be in a highly-alpha quality
> state intended to communicate the possibilities for making a quantum
> jump in rapid prototyping with Linux when the BeagleBone is initially
> launched, we intend to collaborate with the Linux, Cloud9 IDE
> (Ajax.org), node.js, github.com and BeagleBoard communities to evolve
> this to Arduino-like simplicity, without the need to install any
> development tools or understand Linux programming details. Development
> of the application library will be done entirely in the open and is
> awaiting launch until there is broad availability of the hardware to
> avoid any undue refactoring that might come from not having the proper
> collaboration and review.
> ===What does this mean for the future of the BeagleBoard and the
> The BeagleBoard and BeagleBoard-xM will continue to be manufactured
> and available for purchase for several years to come (no end of life
> in sight). We can be confident of this thanks to TI's commitment to
> having parts availability for 10+ years for the key components. There
> have been instances where we've needed to update non-TI components on
> the BeagleBoard, such as the recent upgrade from 256MB of NAND flash
> on the BeagleBoard to 512MB due to the end-of-life of the memory
> device. We believe the upgrade shows our commitment to continued
> production and support of the existing platforms.
> ===When will the BeagleBone be available?===
> Some distributors are taking orders now. Rev A2 boards are just
> shipping to active community members now. Rev A3 boards (production
> version) will start shipping to distributors before the end of
> ===How much will the BeagleBone cost?===
> That is ultimately up to the distributors, but the suggested retail
> price is $89. I am confident this will give some room for people
> wanting to make clones can do so at a very competitive cost. The
> AM335x has been announced to be available for as little as $5.
> ===Is this just a TI marketing gimmick?===
> It is certainly not a marketing gimmick for the key leaders of the
> project. We really do care about giving to the open hardware movement
> and the projects it enables us to do personally and through
> electronics education.
> Several semiconductor manufacturers are attempting to duplicate the
> community building success of the BeagleBoard and have cut the price
> on their development tools, even to the point of giving away chips and
> subsidizing the cost of other components on the board. Ultimately, I
> think this is a good thing for developers who are aware of this by
> lowering the cost of evaluating processor technology. However, for
> those of us who feel personally responsible for the BeagleBoard, we
> feel it is different than virtually all of those other efforts and
> that it must stand on the quality of the technology and our commitment
> to be a part of the BeagleBoard community, actively supporting
> newcomers who seek to take ownership of the direction of the project.
> We are personally excited about what we can do with the BeagleBoard
> and would do it even if TI didn't pay us for it (and not all of us are
> paid by TI, even though I am).
> The current open hardware movement is much akin to early home computer
> and radio hobbyist activities in its highly collaborative nature. We
> aren't anti-competitive or looking to use our admittedly unfair
> advantage of working closely with TI. Arduinos are great for what they
> do, as are any number of ARM and non-ARM based embedded development
> systems. To that end, we won't accept subsidies from TI on chips,
> though we do get volume pricing that other solutions selling the
> volume of the BeagleBoard and fostering open development would be able
> to get. We have had challenges with some small groups trying to get
> similar pricing, but believe we have resolved this at every turn. We
> are committed to advancing open hardware for the benefit of all and
> are seeking to enable new things with the BeagleBoard and BeagleBone,
> not degrade or discount the great contributions to open hardware that
> have come before or will come after.
> ===Why aren't the BeagleBone expansion headers compatible with the Arduino?===
> We set out to enable something different than the Arduino, though
> certainly having the breadth of add-on boards available to the Arduino
> is in our goals. While it would have been possible to make this happen
> and it is still possible to make an add-on board that would adapt to
> that interface, the performance and cost of interfacing to Arduino
> shields as-is would under-utilize the capabilities of the underlying
> Linux-based system and compete in places where an Arduino is really
> the right solution.
> We are anxious to work with open hardware partners looking to generate
> and sell...
> read more »
|Re: [beagleboard] Re: BeagleBone announcement||David Goodenough||12/19/11 6:30 AM|
Farnell do not seem to have this problem. They shipped mine and it
arrived last friday - no End User Certificate required.
|Re: [beagleboard] Re: BeagleBone announcement||Leon||12/19/11 8:03 AM|
I've canceled the Mouser order and ordered one from Farnell. I don't
|Re: [beagleboard] Re: BeagleBone announcement||David Goodenough||12/19/11 8:45 AM|
I got the notification from them that they were available on thursday just
before lunch, and ordered immediately. The unit left Belgium, headed to
Cologne, arrived at Castle Donnington in the UK at 3am the following morning
and arrived here around 1pm.
|Re: BeagleBone announcement||bone head||12/19/11 9:13 AM|
I just got my beaglebone from Farnell UK.
It was shipped last Thursday and arrived Friday!
There were 65 in stock on Thursday when they shipped mine, now 55.
I got the usb to serial ports working under XP 32 bit after following
|Re: [beagleboard] Re: BeagleBone announcement||Gerald||10/10/12 8:44 AM|
I know of no such plans.
On Wed, Oct 10, 2012 at 10:21 AM, Ath_06 <alexander....@gmail.com> wrote:
Anyone knows if beagle board is thinking to use the OMAP5 in some future boards?
|Re: [beagleboard] Re: BeagleBone announcement||lkcl||10/28/12 5:43 PM|
On Wed, Oct 10, 2012 at 10:21 AM, Ath_06 <alexander....@gmail.com> wrote:
i've put in a request for access to the OMAP5 in to TI, for the Rhombus Tech initiative, in order to create an EOMA-68 CPU Card around it. whilst they're pretty small PCBs (appx 75x45mm) there's quite a bit that can be packed on them and, with care, it may be possible to add optional expansion headers that make them "beagle-board-like".
if this is something that is of interest to you then please do make yourself known, as it will help enormously.