I've kind of been coming to that conclusion as I have been thinking about how to send and receive data.Silvester wrote:IMHO it would be impractical to use a driver to control I2C. Minerva's way of doing it seemed best and gives complete control of the bus.Martin_Head wrote: I have been toying with the idea of writing a driver for the Q68's I2C bus.
I will take a look at the above. My Minerva manual does not have any of the MK2 stuff in it. I saw the I2C_IO_BIN file on the Minerva disk. Which I plan to disassemble.See Minerva's implementation http://www.dilwyn.me.uk/docs/manuals/mi ... ual_11.pdf Page 53 onwards.Tinyfpga wrote:I don't know how to use the I2C bus.
Although you'll need to be familiar with I2C generally and target device datasheets. Ian Burkinshaw wrote some interesting articles on i2C with QL http://www.dilwyn.me.uk/docs/hardware/IanB/ianb.html
The thing is, I don't have any experience of I2C, and I don't have any I2C devices. I've started writing some assembler bit banging code based on the Wikipedia I2C page, and I'm thinking about testing it by trying to read and write to the Q68 backup clock chip.
Also I'm thinking that the Minerva I2C stuff may be in the Minerva source code, which may be worth looking at.