Wow. I really don't see what I did different. I re-followed steps 9 onwards in post #9
but diagnose_TFT_support.ino is now cycling through colours in portrait and landscape so that it is a HUGE leap forward.
my copy of graphicstest_v25 is still displaying just white screen (and "ID" followed by odd characters in the serial monitor).
Well, click on FAVORITES. Select MCUFRIEND_kbv examples.
Run all of the examples one after another.
Make copies in your sketch folder of any that you want to experiment with.
I am still intrigued by your preference for the Web Editor.
If you want to investigate graphicstest_v25 this is my report.
Sketch uses 31396 bytes (97%) of program storage space. Maximum is 32256 bytes.
Global variables use 2026 bytes (98%) of dynamic memory, leaving 22 bytes for local variables. Maximum is 2048 bytes.
I get a White Screen. There is no way to run a sketch with 98% SRAM.
If I edit graphictest_v25.cpp to use HOW_SLIM=3 it will run some things before crashing. i.e. 88% SRAM is still unsafe.
Global variables use 1803 bytes (88%) of dynamic memory, leaving 245 bytes for local variables. Maximum is 2048 bytes.
But the biggest saving on SRAM is by ensuring
uint16_t scrollbuf[320]; // Adafruit only does 240x320
graphictest_v25.cpp is very OLD. The current graphictest_kbv.ino restricts the scroll buffer to a sensible size.
David.
Thanks David. Just getting back into it now after Easter break. I bought a new Uno and XC4630 and am getting identical results so no hardware specific glitches. I have not tried all the examples you suggest but the following work (in the Web Editor) from
Library > Favourites > MCUFRIEND_kbv > Examples
- diagnose_TFT_support
- aspect_kbv
- testcard_kbv
- TouchScreen_Calibr_native [Uploads and displays text on screen. Responds to touch on screen but I didnāt follow through on all instructions.]
I tried Libraries > Favorites > MCU_FRIEND_KBV > Examples > graphictest_kbv
but got the following compile errors:
TypeError: Cannot read properties of undefined (reading ālengthā)
Error during build: text section exceeds available space in board
I will try using diagnose_TFT_support as a base for my project since it works, is not too big and I can understand the point of most of the code. Thanks again for all your support. I will post a separate summary of what I have found out before marking this post as 'solved'.
Its a bit off-topic for this post but if you email me at lists@backroad.com.au I am happy to explain the (not terribly deep) reasons why I am sticking to the Web Editor.
I edited MCUFRIEND_kbv.cpp in Custom libraries to #define SUPPORT_8230
I ran graphictest_kbv.ino from the Favorite Library examples.
Using library SPI at version 1.0 in folder: /home/builder/.arduino15/packages/arduino/hardware/avr/1.8.4/libraries/SPI
Using library adafruit_gfx_library_1_10_14 at version 1.10.14 in folder: /home/builder/opt/libraries/adafruit_gfx_library_1_10_14
Using library MCUFRIEND_kbv at version 2.9.9-Release in folder: /mnt/create-efs/webide/0a/33/0a33bd1179c57bfa4a19d1bd3e6cef93:david_prentice/libraries_v2/MCUFRIEND_kbv
Using library adafruit_busio_1_11_4 at version 1.11.4 in folder: /home/builder/opt/libraries/adafruit_busio_1_11_4
Using library Wire at version 1.0 in folder: /home/builder/.arduino15/packages/arduino/hardware/avr/1.8.4/libraries/Wire
/home/builder/.arduino15/packages/arduino/tools/avr-gcc/7.3.0-atmel3.6.1-arduino7/bin/avr-size -A /tmp/arduino-build-B403378D9C9956E006DFFE167C59108B/graphictest_kbv.ino.elf
Sketch uses 31530 bytes (97%) of program storage space. Maximum is 32256 bytes.
Global variables use 1712 bytes (83%) of dynamic memory, leaving 336 bytes for local variables. Maximum is 2048 bytes.
Low memory available, stability problems may occur.
Sure enough it uses most of the Flash memory. (practical limit is 100%)
It uses lots of SRAM memory. (practical limit is about 85%)
The sketch is running fine on an Arduino Uno clone.
Yes, the Web Editor is quite handy to use. You always get up to date library Releases. It is simple to edit a Custom library. You can always delete and start again.
David.
I have successfully got my Jaycar XC4630 display shield working on a Duinotech Uno compatible (thanks to David Prentice). However from the documentation it appears that almost all the pins are used. I would eventually like to be able use the SD card reader and touchscreen. I have successfully read from A5 and displayed the results but really for the project I have in mind I need 2 analogue reads, at least one digital output (seems like the shield potentially uses all 13) an RTC and WiFi communications as well as the display shield.
It appears that I could buy a Mega board but is that necessary? I have already invested in a lot of Unos. The Due seems to be more capable again but I dont think Jaycar stock them and they are even pricier.
Previous relevant discussions at:
and
The only spare pin is A5 on a DIP28 Uno.
If you have a clone Uno with TQFP-32 chip you can access A6, A7 (PC6, PC7).
If you are not using the microSD you can access those pins via a 6-way IDC ribbon on the 3x2 SPI header.
I don't know what the Duinotech board looks like. Some Chinese clones have lots of holes for mounting extra pins or sockets.
Angle header strip is very useful for accessing GPIO pins when a Shield is plugged in.
Otherwise buy a Chinese Protoshield with stackable header sockets.
A MEGA2560 has lots of GPIO pins. The TFT will be much slower than a Uno. Buy a Mega2560 TFT Shield if you want reasonable performance.
David.
Topics merged
Hi there, I have this same Jaycar Screen on a genuine Uno, and using Arduino I can not get any life out of it. Hoping for some or any help? (Neewb) - Usual one being a pest lol
- Install Adafruiit_GFX via IDE Library Manager.
- Install MCUFRIEND_kbv via IDE Library Manager.
- Run diagnose_TFT_support.ino from the examples.
- copy-paste the output from the Serial Terminal to your forum message.
The original XC4630 had an Ultrachip UC8230
Looking at #18 it appears that a new Jaycar XC4630 contains a different controller e.g. Himax HX8347
Please let me know. Then I can give you the correct advice.
David.
This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.