Jump to content

MADRAFi

New Members
  • Content Count

    11
  • Joined

  • Last visited

Community Reputation

1 Neutral

About MADRAFi

  • Rank
    Space Invader
  1. Hi, Yes it is slightly off. Those pins which do not allign are those you have to solder yourself. So I have first put it all together and solder them angled. I am not sure if you will bea ble to have 1 common version supporting all holes perfectly. I would try to swap print for pins with the row of pins closest to the 6 pins group.
  2. The pins on V3 board seems not to align with my arduino. It looks like holes should be where white print is.
  3. I have them produced but still waiting for other parts to arrive to get it assembled.
  4. I want to thank Klaus, author of the firmware for the support. It turned out my screen has different pin layout and cannot be used.
  5. Thanks for suggestion, I have already sent email to author.
  6. I was not asking for sources, I know them have them downloaded. I was asking for contact to author of the code or someone who could point me where is definition of LCD recognition Maybe my screen is slightly different then regular hx8347g
  7. Thanks, I followed the suggestion that you need to flash first and solder later to avoid situation when you do not know if broken unit is due to wrong flashing or soldering I have waited few mins each time I think I gave enough time for each step. To me it looks like firmware does not recognize my screen. Does anyone know how to contact with firmware author? Does anyone know where in source code TFT definitions are?
  8. The screen works if I use Arduino IDE and send sketch from TFTLCD-Library-master->graphicstest the screen ID which works: identifier == 0x7575 I am sure I am uploading the right files PS I have only arduino and LCD connected- trying to flash it before start soldering.
  9. I did exactly that. Everytime I took files from hx8347g subdir (both) I also tried 1.1b files (also coping to the directory of the averdude tool. Every time I did the test I unplugged power (usb) waited few seconds and plugged it back. flashing was successful. You selected COM4 avrdude: AVR device initialized and ready to accept instructions Reading | ################################################## | 100% 0.01s avrdude: Device signature = 0x1e950f (probably m328p) avrdude: NOTE: "flash" memory has been specified, an erase cycle will be performed To disable this feature, specify the -D option. avrdude: erasing chip avrdude: reading input file "eeprom_writer.hex" avrdude: input file eeprom_writer.hex auto detected as Intel Hex avrdude: writing flash (3544 bytes): Writing | ################################################## | 100% 0.76s avrdude: 3544 bytes of flash written avrdude: verifying flash memory against eeprom_writer.hex: avrdude: load data flash data from input file eeprom_writer.hex: avrdude: input file eeprom_writer.hex auto detected as Intel Hex avrdude: input file eeprom_writer.hex contains 3544 bytes avrdude: reading on-chip flash data: Reading | ################################################## | 100% 0.54s avrdude: verifying ... avrdude: 3544 bytes of flash verified avrdude: safemode: Fuses OK (E:00, H:00, L:00) avrdude done. Thank you. Diconnect USB cable from PC and reconnect. RESETting the UNO will NOT suffice !!! Wait until the PCs COM-port is active again then press any key Press any key to continue . . . avrdude: AVR device initialized and ready to accept instructions Reading | ################################################## | 100% 0.01s avrdude: Device signature = 0x1e950f (probably m328p) avrdude: NOTE: "flash" memory has been specified, an erase cycle will be performed To disable this feature, specify the -D option. avrdude: erasing chip avrdude: reading input file "SDrive.hex" avrdude: input file SDrive.hex auto detected as Intel Hex avrdude: writing flash (31098 bytes): Writing | ################################################## | 100% 5.34s avrdude: 31098 bytes of flash written avrdude: verifying flash memory against SDrive.hex: avrdude: load data flash data from input file SDrive.hex: avrdude: input file SDrive.hex auto detected as Intel Hex avrdude: input file SDrive.hex contains 31098 bytes avrdude: reading on-chip flash data: Reading | ################################################## | 100% 3.98s avrdude: verifying ... avrdude: 31098 bytes of flash verified avrdude: safemode: Fuses OK (E:00, H:00, L:00) avrdude done. Thank you. The programming has ended. Press any key to continue . . .
  10. I did run Arduino IDE with TFT example. Screen works fine It is reporting HX8347G 00:42:27.956 -> Found HX8347G LCD driver 00:42:28.198 -> Benchmark Time (microseconds) 00:42:28.233 -> Screen fill 449344 00:42:29.134 -> Text 105688 00:42:32.284 -> Lines 679384 00:42:35.660 -> Horiz/Vert Lines 55444 00:42:36.281 -> Rectangles (outline) 39756 00:42:36.867 -> Rectangles (filled) 1259092 00:42:38.693 -> Circles (filled) 340072 00:42:39.108 -> Circles (outline) 280276 00:42:39.871 -> Triangles (outline) 150444 00:42:40.561 -> Triangles (filled) 803996 00:42:42.074 -> Rounded rects (outline) 112324 00:42:42.732 -> Rounded rects (filled) 1316376 00:42:44.600 -> Done!
  11. I have just started assembling my sdrive-max. It seems I have LCD HX8347G. I have downloaded firmware 1.0 and took files from appropriate directory matching my screen. Flashing process succeeded (I was using batch file from the thread). My Arduino is powered via usb only. After restart it has white screen. No crosses for calibration. It seems the firmware does not recognize the screen. What else can I do to get it working?
×
×
  • Create New...