Author Topic: Problem with NHD?C0220BiZ?FSW?FBW?3V3M I2C Display  (Read 1182 times)

0 Members and 1 Guest are viewing this topic.

Offline rill17Topic starter

  • Contributor
  • Posts: 15
  • Country: mt
Problem with NHD?C0220BiZ?FSW?FBW?3V3M I2C Display
« on: March 15, 2017, 03:45:59 pm »
I am designing a project which uses the NHD?C0220BiZ?FSW?FBW?3V3M I2C display, however i am failing to display any characters despite receiving an acknowledge from the in built ST7036 controller. I think the problem might be the LCD initialization, the datasheet is quite poor when it comes to sending data. Attached i have the data i am sending the display as captured by a serial decoder. i tried two methods, one with added delays and the other without delays(delays as specified in the datasheet). Can anyone tell me what i am doing wrong??
 

Offline Throy

  • Regular Contributor
  • *
  • Posts: 53
  • Country: de
Re: Problem with NHD?C0220BiZ?FSW?FBW?3V3M I2C Display
« Reply #1 on: March 15, 2017, 04:26:12 pm »
 

Offline rill17Topic starter

  • Contributor
  • Posts: 15
  • Country: mt
Re: Problem with NHD?C0220BiZ?FSW?FBW?3V3M I2C Display
« Reply #2 on: March 15, 2017, 04:30:48 pm »
yeah, i sent the serial data in the second image based on that code, still nothing
 

Offline Throy

  • Regular Contributor
  • *
  • Posts: 53
  • Country: de
Re: Problem with NHD?C0220BiZ?FSW?FBW?3V3M I2C Display
« Reply #3 on: March 15, 2017, 06:13:40 pm »
It appears you've forgotten the "Slave" byte according to their code.

It should be: 0x78 0x00 0x38 0x39 0x14 0x78 0x5E 0x6D 0x0C 0x01 0x06

Or is the first byte not being interpreted correctly by your scope? It's kinda hard for me to read the clock and data lines.


Nevermind I see the 0x78 in the table below as the address + R/W now.
« Last Edit: March 15, 2017, 06:20:03 pm by Throy »
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf