Hi, just wondering if there were any news regarding the imx515 project. Cheers :)

_________________
--lf

Here is a bit of an update...

1. We are still in the process of revising a board we can ship to developers as part of this program. The board we are currently using is too expensive to produce and ship as we have done it the past. Good progress is being made.

2. To get things going a bit faster, ARM Inc. has provided us with a number of TI Beagleboards (Rev C with 256MC of RAM). These have been shipped to the selected developers.

3. We have our first customer orders, which gives us the assurance to say that everything will go ahead with the i.MX515 Developer Program as planned.

R&B :)

_________________
http://bbrv.blogspot.com

Thanks for the update :)

_________________
--lf

http://bbrv.blogspot.com/2009/04/eagle-has-landed.html

R&B :)

_________________
http://bbrv.blogspot.com

Nice

_________________
Past: Pegasos II G4 & Efika
Now : Mac Mini G4 1.5 Ghz & MorphOS 3.1
BlaBla Team Member -> http://blabla.ppa.pl

So, a developer program for a freescale product, which gets started thanks to a non-freescale product.

The idea is to get certain developers access to chips which have the NEON vector engine at a more affordable price and on a more stable (i.e. been released) platform. I couldn't even call Beagleboard stable; we got the latest C2 revision boards, if you check the Beagleboard site for the number of changes and weird stuff older boards do and schematic errors, you will get a flavor for why sometimes "right now" is just too early to run a developer program around. We feel the C2 BeagleBoard got mature enough to throw out there to meet a goal we have internally - get people up to speed on NEON.

Hardware projects which require the features of the i.MX515 won't be eligible and we'll "replace" the Beagleboards at some point (in fact a lot of the project submissions are from people who have already successfully completed similar things on a Beagleboard), but remember the i.MX515 is still going through the last stages of development. There are some things you just don't want to expose in a developer program and some problems just waiting a month means we don't have to continually support some weird kernel patch or be shipping a mass update to a BSP.

_________________
Matt Sealey

Do you know when a specification for the board used in the projects will be available?

Having a spec would allow me to refine my proposal for a NetBSD port.

Thanks,

Marty

We are working hard to nail this down and make it available.

_________________
Matt Sealey

We should have this information online later this month.

R&B :)

_________________
http://bbrv.blogspot.com

Well, here it is past the end of May and we don't yet have the final details to report, but we are getting closer. After all these years, you would think we would not get all wrapped up in the marketing hype. Actually, that is often hard not to do, as the only way to get things moving is to 'get out there...'

http://bbrv.blogspot.com/2007/02/first- ... ising.html

The EFIKA and Open Client are a good case in point. We started the Developer Program early in 2006 and did not ship the EFIKA until November of that year. The SoC we were using had some undocumented problems that we ended up having to solve without support before we could ship. We have had different kinds of problems to solve this time.

We will be back on track soon. We think the i.MX51 is going to help us all create some very interesting products.

R&B :)

_________________
http://bbrv.blogspot.com

Wasn't it in 2006 the Efika was released and shipped? :)

You are right! The change has been made. :)

_________________
http://bbrv.blogspot.com

Yeah.. Time flies!

Closing in on thirty.. Well, a year to go..

Been there, done that... ;-)