| ??? 10/30/11 20:29 Read: times |
#184458 - Get real processor Responding to: ???'s previous message |
You do not (!!!) want to implement a SPI slave in software unless the SPI transfer speed is very slow.
The slave will not have any way to inform the master if it is receiving ok or not. Any single signal change that is missed because you sampled the signal too late means you got a transfer error. The world is full of very cheap processors with SPI implemented in hardware. Do you have any reason why not selecting one of them? |
| Topic | Author | Date |
| SPI Slave in 89S52 | 01/01/70 00:00 | |
| Get real processor | 01/01/70 00:00 | |
| Topic Author Date | 01/01/70 00:00 | |
| Big problem | 01/01/70 00:00 | |
| Look for a different model | 01/01/70 00:00 | |
| Try 8051 BASCOM | 01/01/70 00:00 | |
| at what speed | 01/01/70 00:00 | |
| Interpreters have an easier life. | 01/01/70 00:00 | |
| Soft SPI speed | 01/01/70 00:00 | |
| But how to combine that loop with a real program? | 01/01/70 00:00 | |
| and more | 01/01/70 00:00 | |
| Software master trivial - slave is not | 01/01/70 00:00 | |
| SPI analysis is made, results? | 01/01/70 00:00 | |
| There _may_ be a solution - but maybe not acceptable | 01/01/70 00:00 | |
| sure, and so what? | 01/01/70 00:00 | |
| SPI at 100Kbps | 01/01/70 00:00 | |
| Still gives puny transfer rate with significant limitations | 01/01/70 00:00 | |
| the answer is | 01/01/70 00:00 | |
| Fully Interlocked Handshaking. | 01/01/70 00:00 | |
Quite common | 01/01/70 00:00 |