Code placed in a " </> " code block from the toolbar is easier to read and maintains indenting.
the GetDisplay() blanks the whole screen to black every 500 ms - then fully redraws the limit lines and data lines - that explains both the time it...
Paul is posting at 2AM which can only mean he is deep into software mode. Hardware engineers knock off by 7PM ;).
Here are the roadmaps they said can be shared. They are checking to see if they can share their complete slide deck which has...
@jmarsh - seemed interesting - grabbed the two files for IDE 1 building.
Three sketches worked.
#1 - current ST display sketch - maybe two of them - nothing special with FLASHMEM
#2 - LittleFS/Integrity/PROG - runs LittleFS with PROG FLASH...
The half way interrupt, was optional and added for use cases like FrankB had where he was using continuous frame updates,
And when you got half way through the frame, he would load in that half of the next frame into the top half of the buffer...
Currently the read speed for onboard flash on Teensy 4.x is not as optimal as it could be.
It supports a "continuous read" mode where successive reads can skip sending the command byte (which is 0xEB for reads). Since this byte is sent in SPI...
Yes, good find.
My samples are coming out of Taiwan, so probably 2 weeks out. @defragster I can hook you up with a part when they come in. I sent a note to Digikey as they seem to be the most active ISSI distributor to see about getting an...
No help from here ... only one of the ST7796's here
Of course the lib affects other similar displays ST7735? - assume that is the concern? Not sure I have any of them here either?
@KurtE or @mjs513 would be inclined from their prior work - not...
A summary of this:
What happened:
Illogical runtime logic was occurring. An if statement block was being executed at runtime, where debugging print statements showed the conditions inside that statement block would mean the if condition should...
Note two other examples on Mini working properly!
Notably the one of earlier focus: P3_03_TFT_DispBig.ino running faster than ever with rare updates taking double digits for the bars - with min update 2 ms and MAX at 12 ms (SPI at 80 MHz)
Mini looks very good! Smoother update across the blocks! Nice at 16 MHzSPI and all good at 80 MHz SPI
16 MHz SPI:
========================
Async check fillRect: 22; took 7230us
Async check drawChar_bg: 120; took 6927us
Async check drawChar: 14...
New commit, can do async update of the changed (rectangular) area of the framebuffer, which saves you keeping track yourself. See update mode 9 for an example.
Thus far this can’t also be continuous, but who knows what tomorrow will bring?
That sounds about right. I tried to follow what @KenHahn said about the changes he had to make for the MINI, so it should be rotated correctly, not have the red LED illuminated, and have the inversion set correctly.
Indeed, the clip update is...
Thanks! Had to force a clean build as it was using cached parts that were missing updates :( and failing :(
It is running the demo here - except the annoying RED LED on the MINI is triggered :) And it is 180° rotated wrong :)
The updates are...
I solved this problem.
Unlike Serial, Serial1 to Serial8 generate considerable noise back through the Teensy 4.1's 5V supply, which was getting back to my sensitive analog & ADC circuitry.
Missing any return from all execution paths is usually a warning. To make this specific warning an error, use "-Werror=return-type" in your compiler options.
May I suggest also adding "-Wall" to your build options? (Teensyduino includes that by...
Can the function exit without a required return value be made a halting Build Error?
int foo( int param ) {
if (param > 1000)
return param / 2;
}
void setup() {
foo(1001);
}
void loop() {}
sketch_jun17a: In function 'int foo(int)'...
Odd - usually the compiler notes those no return value exits? They should be an ERROR as the code it makes seems to shift the stack or something evil causing odd results or crashes.
Ctrl+T can be a helpful reformat for a misplaced ';' or braces -...
Yes, software support will happen. #784 already merged. It will be in 1.60-beta5.
I might rename "qspi_memory_base" before updating LittleFS, and minor changes like removing the unused PSRAM_IDs[] array might still happen, but small details...
this can't execute - needs to move out of current if(>1000) to an else. As written the print of '0' should not be there given the if(>1000) ???
Do a Ctrl+T and confirm the code indents right
There is an exit path from readPeWithDebounce()...
With the number of changes - the next beta not likely to be the last - and if updated new PR might go in if it safely removes debug?
The initial define then extern const caught my eye too - but figured it worked with various old and new value...
I have confirmed that the parts are real and at least somewhat available.
I have 4 samples of the IS66WVS16M8FBLL-104NLI part coming in. @PaulStoffregen if you'd like a couple to do your own verification, let me know and I'll send a couple...
understood - wanted to if it acted the same under current conditions. If it is worse then, DMA helps - if not ... somehow the UART DMA as done isn't helping
Just wondered ... might be interesting to swap it out in the ISR to see it likely would...
Is good for time measure. It counts with each CPU cycle - so 600 MHz. And reads in 3 cycles so 12-13 times faster than micros() and higher resolution.
if the PWM output is just a Toggle from known states - use digitalToggleFast perhaps. Then no...
Why set the DMA priority that high? Probably little else going on that 64 or 128 wouldn't act the same as far as Rx speed and messing with the code controlling the digital IO. Interesting that USB DMA code doesn't cause issues.
Not seeing...
Here is a fourth beta test for Teensyduino 1.60.
Arduino 2.3.x, all systems:
https://www.pjrc.com/teensy/td_160-beta4/package_teensy_0.60.4_index.json
1: Quit Teensy Loader, if running
2: Use Boards Manager to uninstall Teensy, if previously...
None of the parts on your list appears to be the IS66WVS16M8FBLL. Most web searches seem quite happy to give you some vaguely-related part if there isn't an exact match, unfortunately.
Nope, it’s a 3.3V part, same footprint as the standard 8MB PSRAM, and a glance through the FlexSPI commands used vs. the datasheets suggested nothing needed changing apart from allowing the new chip ID and detecting its size (shamelessly cribbed...
You have done some amazing developments with good results after they started working = extending with SDRAM and other complex builds - amazing so many worked and these had that issue!
Exactly. Those resistors that are on there, even tho they do measure correct resistance, must be baked or on crack or something. Truly odd.
Could probably dive deeper somehow but I don't know how. I've learned a good lesson at least. 4 blinks and...
I did some serious testing to get to the bottom of it. Turns out it truly was bad resistors on the whole batch. I got 10pcs of the Gen5 Dev boards. I figured I'd make a few since I only had one left.
All 10 boards the 2.2M resistor connected to...