Re: Embedded clocks

Jim Granville wrote:
rickman wrote:
<snip>

If I am going to require a time reference at the receiver the simplest
scheme I know of is just async serial data with a start and a stop bit.

This is not quite the simplest.

It imposes clock tolerance requirements, and is half duplex, so the
Transmit has to generate it's own clock.

But if I have an oscillator, I have a clock available. That is my
point. RS-232 has very loose requirements for a clock. An RC may not
be good enough, but it doesn't take much.

If you want to ease that, you can do something like the LIN bus, which
gives a auto-baud pre-amble, but that is getting complex for CPLDs.

Way too complex. I am looking at a very small package and I may be
limited to 64 logic cells. In fact I don't know that I can make this
work in such a small part. The problem is that one end of the link has
to be built into a cable housing where the signals are fanned out
again. I don't need a lot of IO, but I expect it will take more than
64 logic cells.


No point in using Manchester encoding if I am transferring the data
over a wire just a few inches long.

Many TV remote's use manchester, and they do that to allow the use of RC
clocks, and straight from battery operation.

If you want the simplest scheme, in a CPLD, use one-wire, because that
is duplex, and does not need to generate a TX clock, just a Tx time slot
( which can be monostable derived ).

I don't see one wire as being any simpler than a UART. One wire is
just bit async rather than byte async. You still need a timer to time
the bits.

If you can get up to 2 wires, then i2c & variants are a widely used
standard, and it does not take too much CPLD resource.

Yeah, I have thought about I2C, but it would have to run at High Speed
to work properly due to the addressing overhead. SPI would work too,
but would use all four pins leaving us no spares. A UART interface
could use two wires, one for transmit and one for receive. The word
size can be application specific with dedicated bits for discrete
signals. Most importantly, I think it will be the smallest in a CPLD.

.

Relevant Pages

  • Re: Async Processors
    ... The async processor has a data path and a handshake path ... I don't see how you can async clock logic without ... As SOC designs add more and more analog and even RF onto the ...
    (comp.arch.fpga)
  • Re: Async Processors
    ... The async processor has a data path and a handshake path ... of logic to generating and propagating the clock. ... As SOC designs add more and more analog and even RF onto the ...
    (comp.arch.fpga)
  • Re: 96 cabrio possible electrical prob?
    ... > circumstances the clock has been reset. ... so it's apparently not a system-wide power outage going on here. ... way to stop the clock is to disconnect this wire. ...
    (rec.autos.makers.vw.watercooled)
  • Re: low speed communication
    ... forwarded clock (for nine signals), and a bus like this for each direction. ... use another wire. ... FAST, which is very close to 50 ohms, and there should be no overshoot, ...
    (comp.arch.fpga)
  • Re: SR and electrical resistance, and rates
    ... > Given identical wires, wire A and wire B. Both wires are parallel to ... > wires A and B I have a battery, and an electron counter and a clock at ...
    (sci.physics.relativity)