The 6610 LCD comes with 2 different controllers. The Epson S1D15G10 and the Philips PCF8833. You can find some images here. If you got one with an Philips controller, you are lucky. The Philips controller is supposed to be pretty robust, while the Epson is supposed to be very tricky to get right due to its over sensitive nature to voltages and settings. I was not lucky enough to get a display with a Philips controller. Damn it. Nevertheless, I tried to get the display right. After working on it for days, all I got was an orangish display. No true colors. I was able to display whatever I wanted, but in just one color, Orange. This problem was widely reported on the Net.

The good thing about the 6610 LCD is that it has backlight LEDs already mounted. The 3530 LCD does not have backlight and this can be tricky to set up and color LCDs. You need really powerful, tiny white LEDs to evenly light the LCD from the back. Unless you have a support board, this can be tricky to get right.

After having spent at least 16-20 hours trying to get the 6610 display right, I moved on to the 3530 display that has a lesser resolution of about 97×66, but is good enough for most tasks. I got a display within few hours of work. But when I try to execute the PASET command, the one that sets the cursor on a row you specify, it skips a row! For example, if you are trying to draw a rectangle using a line fill algorithm, the alternate rows would be skipped.  I tried various workarounds, but to no relief. So, I have to sadly let go of my experiments with color. I am wasting too much time and soldering lead on this.

I have been reading since long about interfacing a Nokia 3310 LCD to many different microcontrollers. There are many libraries available for these different microcontrollers that make programming these devices trivial. But where to get these devices? Luckily for us Indians, it is ridiculously easy to procure one of them. I just went to Chennai’s Ritchie street and got myself one. Not only did I get a monochrome 3310 LCD, I also got a 4K colour LCD that comes with the Nokia 6610!

The shop was in the dingiest of places. You could never suspect that civilization could exist there. But there it was, teaming with activity. Here you could get virtually any replacement for cell phone spares. What’s more, I saw cell phone repair manuals, with complete schematics! I wonder if these came from China, there was markings in a foreign tongue resembling the Chinese language. Every major Indian city must have one of these shops.

I first asked for a Nokia 3310 display. The shopkeeper promptly asked me if I wanted “O.G” or duplicate. The “O.G” meant original. Beware, these are really not the original spares themselves, just two different qualities of the counterfeit spares available in the market, as I later found out. The 6610 colour display came as a separate package, just the LCD, but the 3310 LCD came with a frame, it also had the ear piece. For some wierd reason, the shopkeeper warned me not to remove the earpiece. I ignored him since I needed space to shove in a capacitor. Things are fine. The “original” and the “duplicate” items had a difference of Rs. 25 among them. The “originals” for the 3310 and the 6610 cost me 150 and 350 respectively.

The 3310 is very simple to interface. It can talk to the SPI port of the AVR or any other microcontroller. It uses a Philips PCD 8455 controller that is simple to understand. But why reinvent the wheel for regular tasks? There is a wonderful library written by our friend, Louis Frigon. You can see that here. So I went about making myself a simple AVR programmer as described by Pramode in his wonderful article here. I was previously running off a breadboard. This time around I bought a ZIF socket for easy installation and removal of the chip being programmed. This can save a lot of time and it is also gentle on the chip.

Then came the part of soldering the 8 wires on the Nokia LCD. Well you don’t need 8, but 7, since pin number 7 is connected to a capacitor that is grounded. I normally use a 10W soldering iron that is available usually for Rs. 20, but this time I knew the old guy was not a match for the precision required for the job. So I got myself a relatively expensive one from Goot that came with a sharp tip.

With this iron, it was easy to solder the wires. I also managed to solder the 4.7 uF electrolytic capacitor on the pad itself. But I guess I pulled the wires a little bit, some pads then became loosely connected, internally, as I would later find out. If your soldering is bad, don’t even try it! Get someone who can do it for you. If you are too used to the breadboard, you may find this a tad difficult. Connecting these many flimsy wires to a breadboard can be a pain. So, I decided to use a general purpose PCB.

The LCD requires a 3.3 V power supply. I’m sure that a 3V power supply will work. Some sites also hint this. But I wanted to try out 3.3V, since I have never used components for that before. I called up my hardware wizard friend, Selva, my ex-colleague from Novatium. He suggested either LM317 or LM1086. There are fixed and adjustable versions of these useful chips. I suggest that using the 317 with 2 resistors is a simple way to avoid using the pricey LM1086 that costs Rs. 250. The LM317 costs a mere Rs. 15.

When I connected power and switched on, nothing! Well I rechecked and powered on, nothing again. I got this very familiar feeling of frustration. On closely examining the LCD soldering I saw that I had pulled the wires hard and the pads were not in their natural shape. I pressed the pads down with one finger and then powered on. And there I saw the words “God is Great”. With a line I had drawn from (1,1) to (30,30) just to check out the line routine.

main() {

LcdInit();

LcdStr(FONT_1X,"God is Great");

LcdLine(1,1,30,30,PIXEL_ON);

LcdUpdate();

}

Now is time for something more interesting.

The Colour LCD

Well, working with the monochromatic 3310 LCD was easy and just a few hours work. The colour LCD will be challenging both in terms of hardware(the pads are microscopic) and software. There is no library available.

”
Virtualization is going mainstream and there are several tools being
developed by many 3rd parties that deal with various virtual machine
technologies. Several of these tools are licensed under the GPL. One
promising library, LibVirt (http://libvirt.org) is licensed under the
LGPL. As of today, Libvirt supports KVM, Xen and QEMU. If it needs to
support OpenVZ quickly, it would be great if the userland control code
is available in a library format under the LGPL, whereas the utilities
can still be GPL. Re-inventing the wheel is a waste of time for
everyone involved since it will take considerable time to include
freshly writen code to control OpenVZ based VMs into LibVirt.

Will OpenVZ(SWSoft) be willing to release the userland control code
(most of it in the “lib” directory of the vzctl distribution) under
the LGPL so that other tools can use it efficiently?
“

There was one user, who came forward to do the work, by properly splitting the tools and core functions into and library proper and programs that link to it, if it was agreed that the code be released under the LGPL.

After many days, there seems to have been some consideration on those lines. One SWSoft(the company behind OpenVZ) employee,  has replied to a user who is having problems with the current library thus:

”
current libvzctl imho is brain damaged as it was never actually been designed properly. after the licensing question will be resolved I think it will be greately reworked.
“

If the tools are reworked on, and a LGPL version of the tools is available, then integration into LibVirt will be a breeze and it will save a lot of “reinventing the wheel”.

There is a lot to catch up with, but the PDFs are a pain to read while sitting on the system. So, I ordered printed manuals from Intel. They sincerely sent it by international priority delivery. All for free. Thanks Intel!

OpenVZ is a operating system level virtualization solution that lets users run many instances of virtual servers(each can be a different distro) on the same hardware. Whats more, the overhead is almost negligible.

EasyVZ is currently alpha quality software and definitely contains bugs and incomplete features and is released in the spirit of “releasing early”.

The project page is here.

When I had once been to Thrissur, Pramode gave me an ATMega8, AVR architecture based microcontroller. This is a very interesting chip. It features in-system programming, thus the higher voltage needed to burn the on-chip Flash memory is generated internally and the device programmer becomes drastically simple. It also has a GCC port and can be programmed in C! The AVR series can also work without an external crysal oscillator circuit, which is optional, if you want to operate in higher frequencies. So for a blinking LED circuit, you only need a couple of resistors and a capacitor apart from the chip and the LED itself. Of course, you need power supply.

Since then, I have also bought myself some ATTiny15L microcontrollers that are tiny 8 pin ones and can clock up tp 1.6MHz. Since most instructions are single cycle, they can execute 1.6 million instructions per second. Just look at the 2051 programmer and at the breadboard, which is an ATMega8 programming circuit, the sheer lack of additional components is striking. That board also serves as a blinking LED test circuit. A blinking LED in microcontroller programming is the usual “Hello world!” equivalent.

One microcontroller family I haven’t touched is the PIC family, need to pic’ it up

I used DOS on my 386 PC to learn C and assembly. DOS can’t run many programs at once, although there are multi-tasking shells available for it. There are however clever ways of running small programs by hooking on to some interrupt routines. These programs are called TSRs, Terminate, but Stay Resident programs. For example to display a small text clock on a corner of the screen, I once hooked to the timer interrupt, and displayed the time by writing the time string directly into video memory. By hooking what I mean is that you replace the ISR with your own routine, and then you call the old ISR routime, which you before replacing. The timer interrupt is called 18.2 times a second, thus I get a chance to run several times a second without being explicitly executed by any user. The IVT or the Interrupt Vector Table (a table containing the addresses of each Interrupt Service Routine), is located at address 0000:0000 in the x86 architecture, and contains the address of the all the ISRs.
Many “resident” viruses use the TSR methodology to do interesting things. The main DOS interrupt is int 0×21. They would hook to it and thus got control every time a system call was made. They then check the syscall number in the AH register. If it was something like the “exec” call, they would open the file to be executed and infect it!

When you are learning about programming hardware at a low level, it helps to have an operating system for several reasons. But robust operating systems like Linux or UNIX come in the way of low level programming if you use user level processes. I see DOS more like a monitor, rather than an Operating System. It provides very primitive services of a file system and rudimentary memory management. When your program is running on the CPU, you are on your own and you were free to do anything. This allows for great freedom while you are learning about PC hardware. You can poke around ports, play around with interrupts, write directly to video memory, etc. It was a stage in my learning process that greatly enhanced my knowledge of PC programming.

Although PCs came equiped with the 80386 processor since 1986, DOS never used its full services. The full power of 32 bit processors was used only after Windows ‘95 was released. Almost a full decade after the hardware was out! There were some utilities like DPMI that allowed the use of protected mode under DOS, not many programs used it. But DOS applications remained so popular that Intel was forced to design in a feature into its CPUs that allowed DOS to be run within a full protected mode operating system. This feature is the vm86 feature of x86 CPUs, that lets you emulate multiple 8086 processors with a single 80386 or better processor. When you start a DOS box in Windows 3.11/95/98/ME, you are using this feature.

I really wonder if people who learn programming now-a-days are exposed to DOS at all. Since it is really stupid, it forces to budding programmer to be intelligent.

The operating system installed was MS DOS 6.22 and I happily played Prince of Persia on it for hours. I was pretty clear what I wanted to do with this PC. I wanted to learn the C programming language beacuse someone had told me that I could write a “virus” with it! Man, I was determined. Being a student of B.A English Language and Literature, I had no clue which book to choose, so I went to a bookshop and bought “C For Dummies” by Dan Gookin. Well, file I/O wasn’t there in that book. For that I had to buy the second volume!! That book sure screwed my understanding of C. I guess if someone wants to learn C, why the hell does he have to be a dummy? And if he were a dummy, why on earth does he want to learn C? But anyways, the dummy there was me. Now, having spent years in the industry, I don’t dare tell anyone how I first learnt C. This is the first time I’m confessing.

As I spent time with C, I realized that it was not a good language to write viruses with. Parallely I was learning digital electronics, since I wanted to upgrade fro being an analog electronics hobbyist. During this phase, I got interested in Microprocessors and thus assembly language. My favorite assembler was A86, due to the lesser red tape it had when compared to TASM and MASM.

I hit the Internet and started downloading source code for DOS viruses. It was a very interesting phase in my learning indeed. I even bought a book on the subject. “A date with Computer Viruses” by Nitin Chandra. It was a funky book with source code in assembly for a DOS .COM file virus and a cleaner for that virus writen in C. Both worked as advertised.

The viruses I liked most were Dribble, Ambulance and Casino. Dribble would make characters on the DOS display dribble down and they would get stuck if other characters were encountered during the “fall”. Ambulance would send a small ASCII ambulance wailing across the screen at random times. The sound effect simply amazed me. This was from the PC’s internal speaker, which is literally unused today. Casino was a dreaded and destructive virus. It would basically encrypt the MBR or Master boot record or the Partition Table. This would render the data on the disk unusable. But that is not all. It would get activated on the author’s birthday, If I recall correctly, and would challenge user to play a slot machine game which it would display. If the user won, the partition table would be restored, or else, the virus displayed a vulgar message and quit! The source code for all these viruses and more is available from here. Be careful what you do with this stuff.

I did manage to write a DOS .COM virus and I was very proud of myself. However, I never managed to write a .EXE virus, which is bit more difficult to write. Dissecting and playing around with Viruses has taught me a lot – this was my first look at programs that others had writen and I had learnt a lot from these wierd programmers. In a sense, these viruses were the first “open source” programs I saw.

I eventually sold off my 386 based PC and bought a 486 for Rs. 6000. It came with SCO UNIX installed on it. It had no compiler and I complained to the guy who sold it to me. Eventually I installed Linux on to it. It was the beginning of a new story. In the honour of my first computer, my cell phone number ends with “80386″.