Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Saurabh_B

Pages: 1 2 [3] 4 5 ... 26
TFTs / Re: working with nhd-7.0-800480ef-asxv-t with buildroot framebuffer
« on: November 16, 2017, 08:15:38 AM »
Can you give us more information as to what issues you are having?

OLEDs / Re: NHD-2.8-25664UCB2 display - Linux device driver
« on: November 08, 2017, 08:03:56 AM »

Unfortunately we do not have any Linux drivers for our monochrome displays.

However there are plenty of people who have made drivers for this and other displays online:
The first one I found was FBTFT:
Another would be the Luma:

TFTs / Re: FT5336 problem with sensitivity and gesture
« on: November 01, 2017, 04:56:10 PM »
Sorry for the misunderstanding.

The firmware on the CTP is often programmed by the display manufacturer.
The different versions on the firmware could be perfectly normal, however you would have to check their application notes to see what might have changed.

More than likely the standard values of the registers will be different. You would need to adjust the threshold & sensitivity of the touch panel.

TFTs / Re: FT5336 problem with sensitivity and gesture
« on: November 01, 2017, 11:16:17 AM »
This might be a firmware related issue, i would recommend contacting FTDI for more support. they've worked with more manufacturers than we have and they might have a fix for it.

TFTs / Re: NHD-2.4-240320CF-CSXN#-F Brightness Adjustment
« on: November 01, 2017, 11:13:47 AM »

For our LCDs you are directly connected to the LEDs, the power is not controlled by the ST7789s.

I would recommend using an external current limiting circuit into the anode for the display.

OLEDs / Re: OLED Update timing problem
« on: October 26, 2017, 04:05:03 PM »
I am still unsure how you are getting characters to show up when the display is powered on.
All of our OLED displays do not show any information until they have been given data to show.

Would it be possible to show me a picture of what characters you are seeing, also a video describing the problem.

I believe the DDRAM of the OLED display is being updated when the power is not appled.

One simple solution is to use the display OFF command after the display boots up from a reset / power off. After this i would recommend doing a clear display before using the display ON command.

OLEDs / Re: OLED Update timing problem
« on: October 25, 2017, 04:01:24 PM »
When you reset the MCU do you know if it sends any random information out of the port that's connected to the LCD?

OLEDs / Re: Characters Mirrored on NHD-0420CW Display
« on: October 25, 2017, 04:00:17 PM »
Unfortunately the pins are not available to the end user.

They do come out to the PCB on pins 5 & 6 of the ribbon connector that soldered onto the back of the display.

Character LCDs / Re: How to program LCD-0224AZ-FSW-GBW
« on: October 25, 2017, 08:09:49 AM »
Unfortunately we do not have a guide on how to do this with linux.
However there are plenty of libraries and tools available that can help you drive the display.

I would recommend looking at the following:

OLEDs / Re: OLED Update timing problem
« on: October 24, 2017, 08:26:49 AM »
You are probably sending information to the display quite fast for this to happen.
Is it possible for you to insert a delay between each character you write to the display. Also inserting a delay between any commands sent.

Typically i recommend a 600Ás delay between most commands / data writes.
You will need about a 2ms display after sending a clear display or return home command.

After the reset is applied are you reinitializing the display?

OLEDs / Re: OLED Update timing problem
« on: October 24, 2017, 08:02:57 AM »
What OLED are you using?
Depending on the controller used the timing will be different.

Character LCDs / Re: NHD-0224BZ1-FSW-FBW - SOLDERING
« on: October 24, 2017, 08:02:25 AM »
Yes, you would be able to solder a 2x8 pin header onto the display.
You will need 2.54mm pitch, or 0.100" pitch pins for this.

OLEDs / Re: NHD-0216AW-IB3 I2C help
« on: October 18, 2017, 09:40:28 AM »

You would only need to send the start condition once, and you would only need to send the address once after this start condition.

You will however need to send a "command byte" between each data byte sent. I would recommend looking at Figure 5-7 of the Controller datasheet.
This can be found on page 11 here:

This command byte would need to be sent between any instruction/data byte sent to the display, and it allows you to change the D/C# bit which determines whether the following byte that follows will be used as data or an instruction.

Pages: 1 2 [3] 4 5 ... 26