[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4688: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3823)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4690: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3823)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4691: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3823)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4692: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3823)
Parallella Community • View topic - Scalable solution

Scalable solution

Forum for anything not suitable for the other forums.

Scalable solution

Postby adexmont » Fri Oct 17, 2014 10:48 am

NOTE: This post born from the confusion in my mind by thinking about how can i get a good scalable modular device and why none big producer is providing a good solution for a home user and the need to clarify some point.
I think that a real clustering solution may reach home market and enterprise with a unique solution with the consequence of a wide standards and compatibility.
I post here with the hope that someone else already thought about this or if not someone will.


As project ara aim to, I'm try to understand if and how is theoretically possible to assemble a set of hardware that allow end users to simply assemble their hardware at the size he care. (18 cpu for real time application instead of 2 TB of ram for managing in real time enormous file; free your immagination)
Based on the block structure as: cpu, ram, rom, I/O peripherals i ended with the solution of a connector that itself handle the route process of the signal in a 4 way node for all of the mentioned blocks (cpu, ram, rom, I/O peripherals).

My low knoledge do not allow me to practically evaluate a similar connector and i was not able to find out something similar on the market (beside the fact that a lot of routing device are sold like parallel, usb or ethernet hub/router).

So here is the question: is it realistic to think about a connector (4 way) that include a bridge chip that rute the signal in the right place and provide a universal bus system that self recognizes the expansion ?

Writing this post i'm thinking in an open sourced solution that provide a similar service as the unipro (project-ara) is providing for the future modules.

If i don't get wrong inside the epiphany core there's a piece that route the data to the right core, is it possible to include that piece in a 4 way connector for example, or in a sort of backplane (more than 4 way) where the expansion device are all different as function but the connector still the same ?

In this way we could have a good possibility to scale, but it's to far for me to evaluate the problem on designing something like this.

The pourpuse of this is to scale from a simple device (raspi, arduino, old gsm phones, basic android tablet) to a big and complex system as the computer that handle the weight of internet (mainframes, structures that allow cloud services, ecc) as simple as a kid build stuffs with bricks :D.

The bottle neck at my eyes is the "bus" system, mean the structure that recognizes and allow component to communicate eachother, so a parallel and universal structure (as i understand that unipro do) cold be the first step to a real scalable system.


So, just for the try to explain myself better try to imagine a small board as parallella , surrounded by 4 universal connector that allow you to expand the device with other same boards, or just connect the the end termination needed (video, audio, general peripherals or what the user need).

This may result in a lot more component but in a lot more versatility. the fact that the connector is unique and universal should allow to a mass production the minimization of the cost for it.

Lot of simple devices interconnected at my eyes are better than a little single and complex device that do everything; the single device may give more performance but surely if it is too complex he is going to end is life late or soon, simple device can have a longest term of support.

for example : what should be done to make the provided samtec connector on parallella working as the unipro connection system on ara-project ?

Thanks for your patience, your considerations and your hints in addition to the thanks for your great job you did and still doing.
adexmont
 
Posts: 121
Joined: Thu Oct 24, 2013 12:58 pm

Re: Scalable solution

Postby shodruk » Fri Oct 17, 2014 7:55 pm

Very interesting!
Is that like this?
square01.png
Epiphany Module
square01.png (48.4 KiB) Viewed 18775 times

square02.png
Zynq Module
square02.png (39.01 KiB) Viewed 18775 times

square03.png
Connected Modules
square03.png (88.28 KiB) Viewed 18775 times
Shodruky
shodruk
 
Posts: 464
Joined: Mon Apr 08, 2013 7:03 pm

Re: Scalable solution

Postby adexmont » Sat Oct 18, 2014 4:09 pm

adexmont
 
Posts: 121
Joined: Thu Oct 24, 2013 12:58 pm

Re: Scalable solution

Postby shodruk » Sun Oct 19, 2014 4:25 pm

Nice CGs!
Yes, I was inspired by your idea.
I think it is necessary for Epiphany to be implemented as such a scalable modular boards because Zynq is too "luxurious" to drive only one Epiphany.
Shodruky
shodruk
 
Posts: 464
Joined: Mon Apr 08, 2013 7:03 pm

Re: Scalable solution

Postby aolofsson » Sun Oct 19, 2014 6:17 pm

shodruky, alexdemont:
A modular approach has always been the plan...but as usual time has been a constraint.
Funny timing coincidence to your post:-)
We kicked off a modular multi-Epiphany board design a few weeks ago. (16 chips/board).
Andreas
User avatar
aolofsson
 
Posts: 1005
Joined: Tue Dec 11, 2012 6:59 pm
Location: Lexington, Massachusetts,USA

Re: Scalable solution

Postby adexmont » Sun Oct 19, 2014 7:17 pm

adexmont
 
Posts: 121
Joined: Thu Oct 24, 2013 12:58 pm

Re: Scalable solution

Postby shodruk » Mon Oct 20, 2014 1:26 pm

Shodruky
shodruk
 
Posts: 464
Joined: Mon Apr 08, 2013 7:03 pm

Re: Scalable solution

Postby xilman » Mon Oct 20, 2014 4:33 pm

xilman
 
Posts: 80
Joined: Sat May 10, 2014 8:10 pm
Location: UK

Re: Scalable solution

Postby adexmont » Fri Oct 24, 2014 10:51 am

just to get back to the main question of the post, here you can see a bad made sketch of what i have in mind about including chip bridge inside the connector.
https://www.youtube.com/watch?v=0F2GEvlU4yQ

Reading about zynq inside tech i imagine one pin dedicated to the route action doable with different voltage (0.1V chanel 1, 0.2V chanel 2 , and so on; chanel are 8)

Are my thought realizable?
What are pros and cons you can estimate about this ?

Thanks
adexmont
 
Posts: 121
Joined: Thu Oct 24, 2013 12:58 pm


Return to General Discussion

Who is online

Users browsing this forum: No registered users and 32 guests

cron