I have previously written about how I built an RS-232 adaptor for the Control 16, but this alone did not allow me to communicate with the Control 16 as I did not know its communication protocol. As I did not have the PCI card to act as a master and provide something for the C16 to communicate with, I was not able to sniff the communications and reverse engineer them. My solution instead was to replace the firmware running on the C16’s microcontroller with one that I custom wrote, and which used my own communication protocol.

Control 16 Architecture

The Control 16 is based around an Atmel AT89C52 microcontoller.  I replaced this with an AT89S52 for development as I could then use its in-circuit serial programming feature.  Using a multimeter I traced some of the connections between the microcontroller and other ICs on the board, and inferred the rest.  The result was that I was able to map out a block diagram of the mainboard, as shown below.

Control 16 Architecture Block Diagram

I’m not going to go into a lengthy explanation of the architecture unless there is someone out there who it’s useful to, so if that is you then post a comment and let me know.

Firmware Replacement

I developed the firmware replacement using the SDCC toolchain.  I have released the code under the GPL v3 license in case it may be of use to anyone. It can be downloaded here: C16Firmware. Please not that there is a bug in the current version of the firmware code. I will update it at some point, if you need it sooner let me know.

This firmware detects events from the sliders, buttons, jog wheel, and rotary encoders (though these have issues) and transmits their values via the serial port. It is also allows the values of the LEDs to be set via commands received on the serial port. So all-in-all it is almost fully functional.  The communication protocol is a fairly simple text-based protocol.

Now that the firmware is completed, the next stage in my C16 project is to develop software that runs on the host PC and converts between the simple text based protocol of the C16, and some other midi control protocol that can be used by DAW software.

Control 16 Regulator/IO Board

The pinout of the RJ-45 connector is as follows (pin 1 is on the left when looking into the connector, therefore on the right in the photo above):

While the above pinout may appear a little random at first glance, when using standard CAT5 cable it means that the pairs are RS422 in; RS422 out; +5v and GND; and +12v and GND.

Here is a schematic for a RS422 to RS232 converter, similar to what I am using myself (though I have been providing power from a lab power supply at this stage.)

Control 16 - Proprietary interface to RS232 adaptor

Please note that while I have successfully connected power and data to my control 16 without blowing it up, this information is only provided as a guide and I recommend double checking it against your actual hardware before connecting anything to your control 16.

Setup

1. Add yourself to the lp group so that you can access the parallel port without needing to be superuser (you will need to log out and back in again after this command):
   sudo usermod -a -G lp <username>
   
2. Install uisp:
   sudo aptitude install uisp
3. Connect the JTAG cable to your target device as follows:
   

   JTAG	Target
   Vcc	Vcc
   GND	GND
   TDI	MOSI
   TDO	MISO
   TCK	SCK
   TMS	RST

Some useful UISP commands

These are given for AT89S52, but for other AVR series it should work if you just drop the -d89 flag and use the appropriate part number. The main thing to note here is that the dprog flag is set to xil to indicate we are using a DLC5 for programming.

If you have issues try adding -v=3 or -v=4 for more verbose output from UISP.

T6963C Controller

The 50573 is based around a Toshiba T6963C controller IC.  Documentation for these is plentiful and there is plenty of software available to talk to them (e.g. LCD4Linux, serdisplib, etc.).  Given that the 50573 is based around the T6963C it makes it fairly similar to some of the other DMF LCDs for which datasheets are easier to find (e.g. the DMF-50136NF-FW). Beware though, the pinout is different.

Pinout

Pin descriptions

Most of these pins (\RESET, Dx, C/D, \CE, \WR, \RD)  connect directly back to the T6963C, so just have a look at the datasheet for more information.

Vdd and Vss are power supply, which is 5V.  Vee is the LCD driving supply, there is special timing and voltages for this, so check out the datasheet of a similar DMF display (e.g. DMF-50136NF-FW).  Basically, when the LCD is in a reset state (as it is at power up), then this should be Vdd. To actually display something on the LCD this needs to be -15v.

I have called pin 20 the page select pin, as this seems to be an appropriate name for its function, so far as I can tell.  If someone can correct me on this, then please do so.  This pin is connected to the most significant address pin of the LCD’s display RAM (which stores what is currently being displayed on the screen).  Therefore, using this signal it is possible to quickly change between ‘pages’ in this RAM.  To be honest, I haven’t used this feature yet and have just left it tied to either Vdd or Vss with no problems.

Internal Wiring

There are some connections to the T6963C chip which may be of interest. The table below details them and their meanings:

These pins configure the T6963C for the following:

• Lines 10
• Vertical Dots 80
• Columns 64
• Font 8×8