I am not able to interface JHD162A LCD to any of the PSoC Kits?

I have not used this display or the drivers you mention, but if you are using 4 bit mode when the display expects 8 bit mode, you can get garbage data. Most of these displays need a delay before sending commands such as "switch to 4 bit mode", so it could be missing the command if the delay is not long enough. Try at least 30 ms of delay.

Is your wiring correct?

check this out this project has a lcd block with 4 data wires interface instead of 8 for a 2x16 character LCD

http://www.cypress.com/?app=forum&id=2492&rID=75707

as for the code

before every print you make you need to set the position from where it would start writing

LCD_Position(1,0);

LCD_PrintNumber(Weight);

LCD_Position(0,0);

LCD_PrintString("Print:");

Yes my wiring is correct the above Image is a custom Component which I found on psoc developer fourm.  and out of ~20 tries I have made the LCD worked once or twice using the above component. I have also double checked the LCD with Arduino's LiquidCrystal Lib and the Lcd works just fine.

I have no luck with the Cypress LCD component. I guess I have to write my own component.

It worked perfectly for me

A common problem with these displays is when the host MCU is reset, it may not reset the LCD and the LCD ends up in a state that the MCU is not expecting. Be sure the LCD is being properly reset and its mode is entirely under control. Find a sequence of instructions that is guaranteed to put the LCD in a known state and execute whenever there is doubt. There are several of these sure-fire sequences published on the net - usually for arduino applications.

@Douglas Wong, I guess the LCD_Start() takes care of resetting the LCD, at-least with the MultiPin component ! I don't know how to view and modify the code for the Stock Component ?

You don't need to modify the code if you can send commands (as opposed to data).

Just find a command sequence that ensures the display ends up in a known state, regardless of where it started.

I think you need to see the low level approach to ensure correct operations. I would checkout this:

http://www.scribd.com/doc/17686517/JHD162A-LCD-Code

Especially the Init code with correct delay...

Your problem is that the display keeps its state during MCU reset. When cold-booting, the initial data mode is 8-bit which you immediately switch to 4-bit which reads data with a pair of EN pulses.

When you reset the MCU, you do not know whether even or odd number of EN pulses were sent. So you have to somhow reset the display even if it does not have reset pin.

This can be done by sending 0x33 0x33 (in 8-bit mode it will mean 4-times switch to 8-bit, in 4-bit mode it will mean once or twice switch to 8-bit). Then you can be sure that you always start from the same state.

Then proceed with regular 0x32 (or 4-bit 0x02 if you have single 4-bit write function), 0x28 to get into 4-bit 2-line mode.

Cheers,

Clem

@gsgill112

Are you using this datasheet?

http://www.itron.com.cn/PDF_file/JHD162A%20SERIES.pdf

Here is someone with same problem and the solution was:

Unsolved JHD162A LCD Initialization

@Clem Martins     The LCD is not the problem, previously I was working with the CharLCd() component in PSoC creator and it pretty much looks like a black box, So I don't know of a way to see the backend code.For the new component I am working I have to incorporate the 0x33 0x33 hack !!Although , I also tried shutting down the power to reset the entire System, as when the LCD boots It doesn't remember the previous stage but that didn't help !!