Embedded

Back to Editors' Blog

PolyCore Updates Multicore Tools

by Bryon Moyer

April 24, 2012 at 7:53 PM

We took a look at PolyCore’s tools away back when MCAPI had first been approved as a standard for low-level multicore communication in embedded systems.

They’ve just announced an upgrade, and they continue with their goal of abstracting away a lot of the fiddly bits that are necessary to get different processes talking to each other in a multicore setup. In particular, they have structured things in a way that’s intended to make it easier for you to write a program on one platform and then port it to another with much less work.

While the earlier version focused more on laying the underlying communication plumbing, their update builds on that by focusing on resource configurability.

  • Memory maps can be made portable. You create them graphically giving them abstract properties, and then the actual map is resolved at build time when you target a specific platform.
  • You can map resource pools.
  • You can map links between two different address spaces that may be virtual, or, more likely, may represent different physical memories.
  • You can define memory access regions, which are basically shared portions of memory that are more narrowly circumscribed for things like avoiding data copying.
  • You can improve performance by controlling the scheduling of the resources needed for sending and receiving messages in a manner that reduces overhead.
  • Messages can now be multi-cast – that is, sent to multiple named destinations, but not to everyone (which would be broadcast).

You can find more info in their release

Channels

Embedded.

 
    submit to reddit  



Related Articles

Who Controls the Power?

Open Power Foundation Aims to Make PowerPC More Plentiful

by Jim Turley

Once upon a time, there were many little RISC processors frolicking in the deep green microprocessor forest. There was the jaunty little ARM. The bright little SPARC. The mighty little MIPS. The aristocratic little PowerPC. And so many others. They all played and laughed and had ever such a good time.

Then, one by one, the happy little RISC processors started disappearing. Were they gobbled up by the big, bad CISC processor that lurked in the woods? Did they cross over the Wheatstone Bridge and into another land? Or did they just get lost in the tall grass, wandering aimlessly until their mommies and daddies forgot about them? ...

iWatch, You Speculate Incessantly

by Bruce Kleinman, FSVadvisors

I held out as long possible before writing anything iWatch related. The irony is that I am iFatigued with everyone iGuessing about an iUnnanounced product, and yet here I am contributing to the noise. iCaramba! The proverbial last straw: I read a piece comparing Microsofts unannounced wearable to Apples unannounced wearable. OMG.

And AFTER deciding to write this piecebut before I could startanother piece appeared with the declarative headline Heres Everything We Know About the iWatch. And because I cannot make up stuff this good, apparently the things we KNOW include:...

Dont Pass Me By

Project Ara Dev Boards and the Internet of Moving Things

by Amelia Dalton

The pedal is to the metal, our motor is running, and Fish Fry is hitting the open road. At the wheel this week is mCube...

Off to the Android Races

New EEMBC Benchmark Measures Android Speed

by Jim Turley

I dont always benchmark my Android devices. But when I do, I prefer AndEBench-Pro. The Most Boring Man in the WorldBenchmarking,...

And Then There Was One

InvenSense Scoops up Movea, Trusted Positioning

by Bryon Moyer

Once upon a time, roughly a month ago, there were sensor makers, who made sensors and did some amount of their own sensor fusion software,...


Login Required

In order to view this resource, you must log in to our site. Please sign in now.

If you don't already have an acount with us, registering is free and quick. Register now.

Sign In    Register