Yes, always best to avoid delay() unless it is short and time critical as that stops other normal loop() code.
Seems like that gives the needed tools now to work it out.
It could be done other...
Type: Posts; User: defragster
Yes, always best to avoid delay() unless it is short and time critical as that stops other normal loop() code.
Seems like that gives the needed tools now to work it out.
It could be done other...
Just seeing the code was modified - but not compiled or put into the IDE and using "Ctrl+T" to format the code for posting readability - doing that here it starts like - and has some issues so not...
Didn't follow the link - just provided a snippet in direction of the indicated desires to start and show function and the basic tools that can use Time to control I/O behavior.
Once that is seen...
... better luck in the morning :)
The p#2 code could move the code after the "if ( timeGroup > 1000 )" to an independent function. Except probably the "timeGroup=0;" to leave that in control...
That code will count to 5 for each continuous call of loop() - not noted which Teensy so it could be some 10K, or 100K or even some 1-10 Million per second calls to loop() each second.
It seems...
Also good to know:
Interrupts can have the same or different priority levels on the ARM Teensy's. In groups of 16 between 0 and 255, with 0-15 being the highest level - and most defaulting to 128...
A quick search on dsb - like done to find the syntax - might yield more details ... here's a distilled recall from better notes posted elsewhere ...
Makes sure the handled interrupt indication...
Indeed - when an _isr() takes too long it effectively never exits before re-entering and loop() never gets cycles.
Without sketch code, there is nothing else running in CORE code that would block...
This is the one "F-RAM™" ( F-RAM is a Cypress TM ) :: $13.20 1Mbit >> cypress-semiconductor-corp/FM25V10-G
Another part that works is this $4.41 MRAM 1Mbit >> rohm-semiconductor/MR45V100AMAZAATL...
Was either one powered to see blink before soldering? Other than soldering was either ever connected to anything except the USB cable? Wires or breadboard to anything?
Did the first bad one Never...
FRAM is one makers Ferro RAM ( i.e. mag with retention) where the other is called MRAM
Look up the parts on digikey { in the 'known_chips[]' or probably links in the thread }- they are similar...
With TD 1.54 ( beta 7) :: SD.h now runs/maps into SdFat for the added speed and functionality that brings along.
The SD.h func()'s were just mapped through by Paul, but now the full SdFat...
Good on the missed details Paul - stopped scanning after seeing it doesn't support QSPI ... but has to be 3.3V part. And even some of the supported parts IIRC have slower SPI interface than when...
The one board worked for some time it seems - but the other never did?
It is strange to have two boards go bad.
Boards have distributors. All boards are manufactured and tested and packaged...
Any chip on those pins to memory map with processor supported addressing on QSPI needs setup and interface as done in the linked sources for supported chips.
The linked chip doesn't seem to...
Yes, it uses the same processor and responds the same way.
IIRC > @mjs513 wrote support for MRAM - though smaller - they work. That came about as part of the LittleFS IIRC and the support for that is in current TD 1.54 Beta.
That LittleFS thread and the...
Done, Glad I asked :) - last thing needed is more trouble ...
Just a quick scan of the code, until this showed something like this could be going off the end of an array where for ( j=0 to limit (n_freq) ) - on the last valid entry it is referring and writing...
Supposing this thread was found - but to be sure : forum.pjrc.com/threads/59319-Blynk-Support-for-Teensy-4-0
A post there might be seen by the maintainer if nothing else shows up. Not sure that...
@mjs513 - does this link the ArduCam viewer : arducam.com/arducam-host-application-demonstration/ ... there is a zip onder 'here' : precompiled execute program can be download from here
The test...
@geekguy: Did the 15 second Restore proceed as > Button held 15 seconds to RED LED flash, Button release, some ~30 seconds of RED LED on, then T_4.0 return to 1 second Blink?
> It won't have active...
The "Error opening USB device: No error" may suggests a bad cable or some other software on the system has taken control of the USB Serial port or the Teensy doesn't have an active USB Stack running...
Arghh - github wanted to merge from your tree when nothing changed here - had to remove and start over ...
Installed 'git' but that's foreign - dumping and restarting repositories is a regular...
That ST7789 display is the one I just got and hooked up - so far just to a T_4.1 and indications are it works well and easily with DC.
Has a hand plug to 8" Female wires. Put long males headers in...
If using two UART pin sets, each/all UARTS have unique individually settable baud rate.
Not noted how much data comes in on each stream?
First guess: Alternating between the two each at 10Hz...
Doh - didn't see the single quotes on the 'ZERO'
Is the the switch 'VAR' a byte type by any chance?
Or something odd confusing the compiler optimization?
switch ( VAR&0xF )
I saw some hangs leaving Vid mode as well in some combination with ILI9341 - thought it was just an invalid command series but it was there. Some part of the DMA left active doing interrupt spasms?
@mjs513 does the "case 0x30:" work as "case 48:" ?
I've got outdoor things to do as well. Spring sun is sprouting trees in deck cracks and a pickup firewood to unload.
I did GIT that ST7735...
"V" works SO SMOOTHLY! it only works USE_SPARKFUN - comes up Very Dark without a good "Calibrating Auto Exposure" it seems, and at times it comes up iffy for a bit, one time it was running and went...
Saw the PR to mjs513 was taken -testing:
//#define USE_SPARKFUN 1:
SEEM GOOD :: s, c, D, f, F :: i.e. no signs of tearing or skewing or shift offset in the ILI9341 image
"d" :: (before FlexIO)...
Good luck @KurtE.
Will keep using the ILI9341 then perhaps swap to the ST7789 when your new work is done.
Not sure what is up with 'z' - it can work - but sometimes just aborts it seems.
...
@mjs513 - Noticed the SFun display backlight was on during Pin Testing when it should have been off. Nice the single Teensy lib works and not a pile of others needed.
Saw SPI speed 30 MHz in _t3n...
"F" seems to be working in CallBack w/code like DMA
Last run of DMA was torn down left edge after it centered instead of the top?
Seems I got that in testv3.
s and c work and D too. Not sure what the deal with SPARKFUN define is failed first time - worked without - then repower it worked turned back on?
d - cont DMA...
github finally got me the latest update ...
Using ILI9341 the "F" working perfectly and no frame confusion on 'wiggling' hand giving skew!
>> moving images all drawn in phase : No skew or...
@mjs513 - Paul has a PR pending on your git.
... here a short time - github desktop not showing me changes ... another remove/and fork ... arrgh
Still seeing this ugly (hard coded static)...
Created /mjs513/TMM-HB01B0-Camera/pull/10 for adding hm01b0_testv3.ino for posts noted above
next guess would be to comment the actual SD file I/O - without that it is nothing and would point to TThreads getting bored with nothing to do between the loop delay and the .yield
That is short and sweet - out of runtime to repro now ... not even a second task doing anything - except loop just burning cycles in a delay
With the print of "Success save 1" the first SD write...
Edited above - can't find explicit post, but that seems to have been implied in a Paul post I found versus faulty memory here.
Without the code as noted the needed detail is in the part not shown.
I just found a Fault occurring on the Teensy MicroMod thread - having the Fault code display info might give a better clue if...
Back to running sketch and opps - did a 'z' during 'F' looking at the draw aberrations - and the Frank B Print Hardfaults #535 code gave this error:
Hardfault.
Return Address: 0x106A...
Adding 'z' key to save LAST frameBuffer[] unchanged not taking new image - again seeing Camera mode ( L/R reverse in image facing camera and display )
using 'f' : Not able to recreate the...
RE: p#421 :: Did some repeat 'f' frames while moving left hand up and down - right hand over numPad hitting Up&Enter to trigger 'f' in TyComm - oh look it is in Selfie/Mirror mode again with left...
That works well as far as tested since downloading @mjs513! Other sketches not so much fun and function.
Glad to see 'F' somewhere - had to turf my github again as the multi crossing pulls...
Yes, that is the nature of interrupts. Execution returns to the point and state of the interruption.
Seems to be a typically good exposition - Makes sense to me and I haven't even looked in any of those rabbit holes.
And yes the FlexIO single shot works promisingly well! Been videoing my room...
Not sure about the priority level of SPI interrupts. General interrupts get set to 'mid level' of #128 and can raised (lower number) or lowered and the number blocks jump by 16 { i.e. 0-15 is the...