Benutzer:Siro/modularprojectconcept: Unterschied zwischen den Versionen
Aus LaborWiki
Siro (Diskussion | Beiträge) K (concept idea modular i2c project) |
Siro (Diskussion | Beiträge) KKeine Bearbeitungszusammenfassung |
||
| Zeile 1: | Zeile 1: | ||
== Problem == | == Problem == | ||
You got a brilliant idea and want to create a new project. | You got a brilliant idea and want to create a new project.<br> | ||
For example an Ethernet mp3 player. | For example an Ethernet mp3 player.<br> | ||
You need: | You need: <br> | ||
a touchscreen | <li>a touchscreen | ||
a keyboard | <li>a keyboard | ||
an amplifier | <li>an amplifier | ||
flash storage | <li>flash storage | ||
mp3 decoder | <li>mp3 decoder | ||
network card | <li>network card | ||
<br> | |||
For each hardware, you have to know the bus specification (bus width, controller, timings, commands, ...). | For each hardware, you have to know the bus specification (bus width, controller, timings, commands, ...). | ||
If you need the hardware for another project you have to create a new layout, that cost time and money. | If you need the hardware for another project you have to create a new layout, that cost time and money.<br> | ||
== Idea == | == Idea == | ||
Using a modular PC like environment. | Using a modular PC like environment.<br> | ||
Instead of using a single controller chip, I'm gonna use multiple small "slave"-chips that are connected to a "master"-chip. | Instead of using a single controller chip, I'm gonna use multiple small "slave"-chips that are connected to a "master"-chip.<br> | ||
<b>Pro:</b><br> | |||
<li>modular | |||
<li>easy: no need to know what hardware, interface, controller, timings are connected to the slave, just give it the orders | |||
<li>fast project setup | |||
<br> | |||
<b>Contra:</b><br> | |||
<li>limited by busspeed (possible up to 1Mbit/s) | |||
<li>multiple devices, multiple errorsources | |||
== Concept == | |||
Using the TWI-Interface (i2c) to connect all chips.<br> | |||
Every chip reports the master it abilities.<br> | |||
Multiple layers for maximum overview and compatibility. <br> | |||
Master<br> | |||
|<br> | |||
|--Slave 1<br> | |||
| |--LCD<br> | |||
| |--keyboard<br> | |||
|--Slave 2<br> | |||
| |--mouse<br> | |||
|--Slave 3<br> | |||
| |--network interface<br> | |||
...<br> | |||
|--Slave n<br> | |||
|--hardware x<br> | |||
<br> | |||
Aktuelle Version vom 2. Februar 2010, 14:23 Uhr
Problem[Bearbeiten | Quelltext bearbeiten]
You got a brilliant idea and want to create a new project.
For example an Ethernet mp3 player.
You need:
For each hardware, you have to know the bus specification (bus width, controller, timings, commands, ...). If you need the hardware for another project you have to create a new layout, that cost time and money.
Idea[Bearbeiten | Quelltext bearbeiten]
Using a modular PC like environment.
Instead of using a single controller chip, I'm gonna use multiple small "slave"-chips that are connected to a "master"-chip.
Pro:
Contra:
Concept[Bearbeiten | Quelltext bearbeiten]
Using the TWI-Interface (i2c) to connect all chips.
Every chip reports the master it abilities.
Multiple layers for maximum overview and compatibility.
Master
|
|--Slave 1
| |--LCD
| |--keyboard
|--Slave 2
| |--mouse
|--Slave 3
| |--network interface
...
|--Slave n
|--hardware x