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

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.

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.