Riddle: What do you call a beast configured like a kilocore only it's a MEGAcore?
A single Power PC processing core hooked up to an FPGA.
Which requires the hapless software programmer to also be a logic designer. Which degenerates to a situation where you have no software traction, and therefore no apps, and therefore no customers, and therefore no real product. Just a really cool idea that doesn't quite fly.
on a side note i really think its the right time for "kilocore" Michael O'Brien, tranputer/XMOS pioneer dave may, and ARM Inc to get together with some VC and make a mass produced ARM A15/ Mali T600 based Achronix FPGA on the 22nm or lower Intel Process ASAP ;)
"startup attempts many-core revolution"
i have to agree jayson, infact its already been done before a long time ago now April 4, 2006 in the so called Rapport Inc's "kilocore"
"Kilocore, from Rapport Inc. and IBM, is a high-performance, low-power multi-core microprocessor that has 1,025 cores. It contains a single PowerPC processing core, and 1,024 eight-bit Processing Elements running at 125 MHz each, which can be dynamically reconfigured, connected by a shared interconnect. It allows high performance parallel processing."
and OC lets not forget to give other credit wher eits due too, that being dave may (not related :) of XMOS many multicore fame.....
sure this France pretenders version is using more modern process and adds current busses etc but lets not forget the past and still living broard shoulders Joel Monnier is standing on...
A "general purpose" 5 watt 256 VLIW flow processor for "embedded applications" in the fields of "image processing, signal processing, control (??), communications and data security"?
Doesn't sound too general purpose to me. Am I missing something here?
In the least, the application needs to be amenable to flow processing. That's why there aren't any "general purpose" many-core flow-processors out there.
So what's the angle here?
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.