which uses the following controller:
even though it should be connected/jumpered properly, it doesn't work. i tried to change xbmc's implementation of xenium-lcd-support as i think the lcd's protocol isn't compatible with the one xbmc uses. this is from the lcd's datasheet:
Quote:before transferring real data, start byte has to be transferred. it is composed of succeeding 5 "high" bits,
read write control bit (r/w), register selection bit (rs), and end bit that indicates the end of start byte.
whenever succeeding 5 "high" bits are detected by ks0073, it resets the serial transfer counter and prepares
to receive next informations.
the next input data is the register selection bit which determines which register is to be used, and read write
control bit that determines the direction of data. then end bit is transferred, which must have "low" value to
show the end of start byte.
Quote:(1) write operation (r/w = 0)
after start byte is transferred from mpu to ks0073, 8-bit data is transferred which is divided into 2 bytes,
each byte has 4 bit's real data and 4 bit's partition token data. for example, if real data is "10110001"
(d0 - d7), then serially transferred data becomes "1011 0000 0001 0000" where 2nd and 4th 4 bits must
be "0000" for safe transfer.
to transfer several bytes continuously without changing r/w bit and rs bit, start byte
transfer is needed only at first starting time.
but it looks like the source of the function xeniumspisendbyte is not available as it is an external library.
does anyone know the implementation of this function? or was this provided by ozxodus without source?