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 - Henning_S

Pages: [1]
1
TFTs / Re: NHD-4.3-480800EF-CTXP#-T - HX8369 continious memory write problem
« on: September 17, 2014, 06:51:40 AM »
Update: I tested all of this with a second display, with which there were no problems. No additional delays were needed and everything worked as expected. So it seems that the display I first used had some error in the controller.

2
TFTs / Re: NHD-4.3-480800EF-CTXP#-T - HX8369 continious memory write problem
« on: September 08, 2014, 03:14:21 AM »
Thanks for your code! Unfortunately this didn't work for me, but I had confirmation that I was using the right commands.

This lead to some more testing and I was finally able to get it to work.
The problem seemed to be that the used interface is too fast for continious GRAM data write. I added some NOPs after each data write to delay the next write and now the display is showing the sent pixel data.
I'm using a STM32F2 microcontroller and writing to the display via the FSMC (memory controller) 16 bit data interface und using the lowest address bit as command/data control signal.
What's strange is that during initialization I write to the display's LUT for color conversion (command 0x2D followed by 192 consecutive bytes as data) and there all data is received correctly, without an extra delay. There seems to be a slower timing for GRAM access than register access contrary to the datasheet information where register access has a 100 ns write cycle and GRAM 33 ns write cycle in SLPOUT.


3
TFTs / NHD-4.3-480800EF-CTXP#-T - HX8369 continious memory write problem
« on: September 04, 2014, 02:27:24 AM »
Hello!

I am using the above mentioned display in 16-bit RGB565 mode. When writing data as single pixels (commands 0x2A and 0x2B with same start/end adress, followed by command 0x2C with a single data write afterwards) everything works fine, but a frame update is slow (12 writes for one pixel).
To speed this up I set a window via the 0x2A/0x2B commands, followed by command 0x2C with multiple data writes afterwards. This leads to a black display panel and no following single pixel write changes anything.

Is there a known problem with this setup or is there another command/setting needed to get this to work? Maybe I have overlooked something in the datasheet controller.

Many tanks in advance.

Regards,
Henning

4
TFTs / Re: NHD-4.3-480800EF-CTXP#-T - Broken?
« on: September 04, 2014, 01:19:13 AM »
Unfortunately I have the same issue with both displays I ordered from Mouser ~1 month ago. Do you guys handle the RMA or should I contact Mouser directly?

Pages: [1]