Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


About Dolence

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Moderator, please delete this topic. It's been a long time and I couldn't even initialize this display properly. I'm abandoning this project. Thanks.
  2. OK, so after testing the display in GPIO mode using an Arduino Mega and stating my display is fine I did some tests. I made a new STM32CUBEMX project using my board (nucleo-f746zg) with all the uneeded periperals left aside. I then set the FMC options reflecting my actual wiring: CS on NE1 Memory Type: LCD Interface LCD Register Select: A16 Data: 16 bits I have my display wired as this: ----- STM 32 ---------- SSD1963 ---- PD6 LCD_RESET /RESET PD4 FMC_NOE E_RD PD5 FMC_NWE R/W_WR PD7 FMC_NE1 /CS PD11 FMC_A16 D/C PD14 FMC_D0 DB0 PD15 FMC_D1 DB1 PD0 FMC_D2 DB2 PD1 FMC_D
  3. Using an arduino mega and TFT library provided by manufacturer the display worked. It isn't defective. I don't even know if I'm glad or sad LOL.
  4. Changed my nucleo to external 5V power, checked all the wiring lines one by one 3 times using an multimeter to be sure, tried to send init commands directly in a barebone fashion. Nothing produced any different result. I noticed my display has come with a 20mhz crystal instead a 10mhz as mentioned in gdisp_lld_SSD1963.c driver file PLL and SYS clock configurations, don't know if it could be the cause. I'm starting to suspect my display is defective.
  5. Ok, some updates... static void fmc_setup(void) { unsigned char FMC_Bank; rccEnableAHB3(RCC_AHB3ENR_FMCEN, 0); IOBus busD = {GPIOD, (1 << 0) | (1 << 1) | (1 << 4) | (1 << 5) | (1 << 7) | (1 << 8) | (1 << 9) | (1 << 10) | (1 << 11) | (1 << 14) | (1 << 15), 0}; IOBus busE = {GPIOE, (1 << 7) | (1 << 8) | (1 << 9) | (1 << 10) | (1 << 11) | (1 << 12) | (1 << 13) | (1 << 14) | (1 << 15), 0}; palSetBusMode(&busD, PA
  6. Hi Joel. Thanks. I've changed optimization level to 0 in makefile and FMC increasing from 0x60000000 to 0x6fffffff. Main thread sleep time was reduced to 2 ms as well. Ok, now we've got some things happening! Look like A16 goes low while we output some juicy data to sub bank1. And how it goes high when the address change to the next sub bank. I didn't understood that signal change sequence while going from low to high. Is it fine? What should be the next step? Figure out timings? What about 6800 and 8080 modes thing? Please, just give me a north to fo
  7. Ok, so following this board administrator advices I'm trying to isolate the problem. Started a project with nothing but FMC test code. I did it like this: #include "ch.h" #include "hal.h" //#include "gfx.h" static void fmc_setup(void) { unsigned char FMC_Bank; rccEnableAHB3(RCC_AHB3ENR_FMCEN, 0); IOBus busD = {GPIOD, (1 << 0) | (1 << 1) | (1 << 4) | (1 << 5) | (1 << 7) | (1 << 8) | (1 << 9) | (1 << 10) | (1 << 11) | (1 << 14) | (1 << 15), 0}; IOBus busE = {GPIOE, (1 << 7) | (
  8. Joel, thanks for helping and I'm sorry for taking your time. I now you are a very busy person and I really appreciate your attention. Knowing this, now I see the value 0x60020000 is wrong for FSMC_A16 since it would be a 1 on the 18th bit address bit 17. It should be 0x60010000. Unless I missed something, all the pins are correctly set, including Register Select which is PD11. I will triple-check this. I will do all the recommended tests using a scope and check timings in display datasheet, as suggested. I still have two things that I didn't get. 1) Looking at the st
  9. H! I've been trying to make this work without success so if anyone could help me I would be very glad. I'm trying to get this display working with my STM32F746ZG based nucleo144 board. Display is 800x480px 7" drived by SSD1963 in 16-bit 8080 parallel mode. I have Register Select at A16/PD11. I don't know if the selected mode is wrong and how to change it or fi I have the FMC peripheral initialized properly. Anyone could please explain these lines to me? I can see from where 0x60000000 come from, but what about 0x60020000? #define GDISP_REG (*((volatile uint16_t
  10. Guys, thanks for all clarifications. I will take all the information in account, probably going with an F7 and RA8875.
  11. Hi cpu20! Thanks for your reply. I've been doing my homework in the past few days. With my current setup I can't even display gifs and pngs. Looking into the drivers, SSD ones appears to already have hardware acceleration implemented. RA8875 have more hardware acceleration options but almost none of them are present on driver. I don't know how easy would be to a newbie guy like me implement those functions. I will take a look on how it was done on another driver. The MCU I was planning to use was an STM32F4 with192 kB ram and 1 MB flash. For image storage, is possible to hook an
  12. Hi! I'm basically an AVR 8-bit withou much experience with real time OSes. Recently I've been learning ChibiOS and STM32 microcontrollers. Using uGFX I was able to properly drive an small and very slow 2.2" ILI9341 SPI display. I want to buy a bigger and faster display for use in a future project. I will probably pick an FSMC capable STM32, unless someone say LTDC would be a better option. Actually I have considered these options: 9 in 1) 9 inch LCD Module TFT Display w/OPTL Touch Panel,I2C+Serial SPI 2) 9"TFT LCD Module Touch Display w/SSD1963 Controlle
  13. I found this bug when TextEdit is used:
  14. I'm having the same problem here.
    µGFX-Studio allows fast and intuitive GUI design for your application. Even it's in early development phase it's beign constantly improved and is very usable on latest version (0.13). Using this very handy tool to design your GUI is easy and will allow the generated code to be used in your project in just a few clicks.
  • Create New...