Closed dsyleixa closed 5 years ago
Fixed by #30.
Objection - AFAICS, the issue is not fixed yet: https://github.com/adafruit/Adafruit_HX8357_Library/pull/30 is not about arbitrary clock speed frequencies. Furthermore, https://github.com/adafruit/Adafruit_HX8357_Library/pull/30 is about ESP8266, and I am using ESP32 and M4!
Additionally, https://github.com/adafruit/Adafruit_HX8357_Library/pull/30 is just about a constant HX8357B, but that is just a char value uint8_t HX8357B = 11
OTOH, 11 is no SPI frequency at all. Instead, SPI frequencies are e.g. uint32_t 10000000 (10MHz), 30000000 (30MHz), 80000000 (80MHz), or 120000000 (120MHz).
So how to change the SPI bus clock frequency to either 10000000 (10MHz), 30000000 (30MHz), 80000000 (80MHz), or 120000000 (120MHz)?
PS; Please re-open this issue because it is not fixed yet!
thanks for reopening!
update, tested anew: as to Adafruit_HX8357::begin
tft.begin(10000000) is appearently slower than ttft.begin() (void) or tft.begin(HX8357D) or tft.begin(HX8357B),
but .begin(20000000) is as fast as begin(void) or begin(HX8357D) or begin(HX8357B), and this can not be made faster than just that, which actually was the intention,
OTOH values >= 40000000 make the tft not respond any more (white screen, testet with 240MHz ESP32).
I believe the chip has a maximum frequency of 16MHz. By default, the lib tries to set it to 24MHz and then it falls back to 16MHz. So setting it to 20MHz will have the same result. Attempting to drive it faster will not make it work better, but giving it 240MHz is just way too fast for it. As you have demonstrated, you are able to set it arbitrarily and it responds (just not how you'd prefer) 10MHz is slower than 16MHz, etc. Closing this bug since it's not an issue.
@makermelissa: thank you for your reply. Nonetheless, this now sounds different from what was stated in a prior post, i.e. that SPI can be accelerated even to more than that by overclocking though: https://github.com/adafruit/Adafruit_HX8357_Library/issues/24#issuecomment-487159696 OTOH, your statement that you would "believe" does actually not mean that you knew either facts for certain, does it?
@dsyleixa we are committed to providing a friendly, safe and welcoming environment for all.
your recent comments here and in our forums can be improved. if the antagonistic behavior continues, the next steps will be to ban from our forums and github.
I don't see your point, tbh, I'm never unfriendly and I am looking for constructive results. I am also dedicated in testing and improving proposals and have already provided several enhancement suggestions. OTOH, I am a customer of your products, I purchaased lot of items and even am advertising your products widly in our German Robotics forum (e.g., Feather boards); anyway , if things didn't work, a topic had to be issued, Nonetheless, sometimes support was given and sometimes not or sometimes inconsistant. I really am curious what is supposed to be unfriendly about that. Perhaps take into account, that I am not a native English speaker and most of my posts are translated by Google translate which then is responsible for the choice of words.
hello, this is a bug report.
SPI clock speed for HX8357 can not be changed or increased by Adafruit_HX8357::begin(uint32_t freq),. (I have the 3.5" HX8357 Featherwing for Feather M4, Arduino IDE 1.8.8)
As to Adafruit_HX8357::begin(uint32_t freq),
for which freq do HX8357D or HX8357B stand for, passed as "freq" ? if I write to Serial it says: Serial.println(HX8357B); // --> 11 Serial.println(HX8357D); //--> 13 But thats no SPI frequency, is it? So is it a SPI_clock_devider or what else?
anyway, I can pass any arbitrary value to tft.begin(n), e.g. HX8357B, HX8357D, 40000000, 20000000, or 1 or 2, or anything else; for a graphic bench mark the output speed stays always the same, either way which value I am passing - so how to make SPI faster?
[code]
[/code]