21 Jun
2013
21 Jun
'13
11:53 a.m.
On Jun 21, 2013, at 2:06 PM, Philipp Hachtmann <hachti at hachti.de> wrote:
On 19.06.2013 21:25, Tony Duell wrote:
Just make sure that whatever you use to do the conversion can recognize
a break signal from the FTDI chip and can send the same over its UART;
I don't recall about the AVRs, but I've worked with a number of micros
that just don't have a clue about break conditions.
Of course, if you're bit-banging the serial output, that part is solved
already. On the other side, though, if you're using one of the parallel
FIFO chips, I don't know if they handle the break condition at all, or
how if so.
- Dave
Most things become simple if somebody else does
most of the work....
Yess :-)
OK, make said device appaear as an FTDI converter
IC (since drivers for
that are pretty much standard) but with the required baud rates. Heck,
make it ignore whatever commands are used to set the baud rate but to
ahve eitehr an physical switch to select the baud trate or a pin to feed
in a 16* clock .
That was the idea when I read the last posting: I could make a little board with an
original FTDI chip and a little AVR that does the serial part of the game. Additionally
I'd fit a jumper/switch to select the baud rate.
Serial IO via TTL on solder pads and an optionally installable MAX232.
Who would be willing to pay around EUR 25 for such a little board? Let me know! If there
are enough requests, I will make them.
Supported settings would be at least
5 bit, 1.5 stop bits: 45.45, 45.45, 50, 75, 100
5 bit, 2 stop bits: 45.45, 45.45, 50, 75, 100
8 bit, 2 stop bits: 110
On the PC side the software could set whatever baud rate it likes - would be ignored.