defragster
Senior Member+

Cool - I hadn't tested image xfer lately - downloaded the ArduCam app - but not yet tried it. This was just a pin test of the breakout and seeing why SD (10) failed ... because it is BUILTIN_SDCARD! Time for yet...

UPDATE on SDIO SD CARD on PJRC MMod Breakout: Captured BMP Image from Camera Does make it to the SD card using :: if (!SD.begin(BUILTIN_SDCARD)) { // if (!SD.begin(10)) { But according to NewPinTest...

Ah Test points - indeed they are clearly wired that way. That solves some wonder about those large 'vias' and those 'T' pins. Nothing to see here. Didn't connect display yet - turned on SDCARD - is has this func...

The only presentation of the QSPI lines {pins#48-54} on T_4.1 are on the bottom side pads. Except for unique CS on each set - the pins are the same on both. Newest T_4.1 card or the info on PJRC.com has image with notes.

Cool - Here's a pic of the bare breakout topside. Shows Qwiic's and SD socket. Evolved from post #349 Noticed "T8" is repeated twice on silkscreen holes around the MMod unit - assume one is T9 { right of T5 or...

Yes, The blink on Pin 13 - the LED pin is because SD uses SPI bus and the Pin 13 is the SCK or Clock pin for the SPI transfers. The T_4.0 doesn't have an alternate pin for SCK. Might be possible to duplicate that...

Good day! Glad I found the need to do the screen write in the callback - scanned the lib/src diffs and didn't see anything jumping out ... so went back to sketch and Voila ... callback getting called in good time but...

Video CallBack needs to write to screen. Picture is fully intact - but scrolling with each redraw Some other minor edits - but my github wants to push direct to #mjs513 and cannot and I don't have option for PR as...

'f' single good, "F" iffy to bad "V" - vid - Black screen ... re p#531 - yes I saw that in sketch now No VID going to "HM01B0_TEENSY_MICROMOD_FLEXIO_8BIT" - but "F" works at 10.23 Hz And 'f' only in...

Not sure which f or F I started with ? Meant 'F' but think I got 'f' ... Nope I was backwards "F" still continuous ... Some more F and f and then : startReadFrameDMA called buffers 20029e84 20238400 Hardfault....

W/ili9341: Says "F" - but using DMA? {if I saw that in the git DIFFS ?} - Single Frame good the 'f' - took some time to get top bottom SYNC - Horizontal - then popped in and Horiz Stable but some verticle Jitter...

'rework' - yep just moved the from git folder to libs ...

That's no fun ... is github up to date - and the bypass example? I can get to try it here with ili9341 in a bit ... ... or ZIP your WIP and post here to avoid cluttering github ... Just hit github - 11 minutes...

Not sure what speeling is either of course ... seems like it may have been Starting the output with the _isr(). For usage of that see PJRC.com for intervalTimer as noted. If the toggle is to be on a known time...

It can help to write out a statement of expected behavior in text. Without that even looking into the behavior of 'close' code won't help because what is wrong won't be obvious not knowing what it should be doing ......

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 ways as well,...

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 sure of the intent: ...

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 to work in reference...

... 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 there, where it could be...

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 that code is missing...

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 (IIRC T_LC has...

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 propagates as handled...

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 loop(). Perhaps...

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 : Both of those...

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 take any code...

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 function just diff names...

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 functionality is also...

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 jumping to QSPI mode....

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 through/by PJRC.

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 support QSPI - so...

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 PaulStoffregen...

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 to j+1: ...

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 thread has useful...

@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 of a single uncanny...

@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 USB at that point -...

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 to recognize the...

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 thing it seems ... ...

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 the PJRC mem board...

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 for small amounts...

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 lib ... Would be nice...

"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 more like that odd...

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) DMA cont repeated...

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. Also REALLY odd the...

@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 - bumped to 60 and...

"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 squiggle start worse...

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 tearing or any anomolies...

@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) save_image_SD()...

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 completed and closed...

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 it is a Fault...

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 (IMPRECISERR) Data bus error...

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 aberrations noted in p#421 &...

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 hand on the left. So...

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 confused me and or the...

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 all day since I left...

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 same highest...

The startup_early_hook() - but does not have full Teensy functionality at that point so only selective parts of the MCU are ready for use. No indication of what code was placed into that local copy of :...

It could save 'lastFPS' and only print on change to stop the 1Hz spew. I just took out the 3 p#395 lines and it seems I have better contrast to the white spots on my dark shirt. Then put them back and got 3 of 4 bad...

Added those three lines in setup() ? - I don't see a diff - maybe? There is good detail now I may not have seen before with a sun bright window backlighting me - about 1/4 of the screen is white wash from window and...

First time I uploaded that Change - from how Paul wrote the rectangle I got tearing. Two uploads after that and then a Reset - all came up with good movie in perfect Sync and seeing the 31 fps - with a pulsing dark...

What 'trouble'? Only change is to add 'F'? As noted some starts get odd sync on timing, but restart works 'most times' - with the way it was. Also noted 'F' MovieMode seems timing race dependent. I did not note...

Final Note before Zzz's: with > //#define USE_SPARKFUN 1 :: It works here now for 'c' and 's'. And image is brighter. >> ALSO it works across code upload or T.MM Reset (TyComm) { edited above post } I put the...

Quick UPDATE :: Frame Update using FlexIO @31 fps <edit>: Ran 1 hour since posting and still running no issue at 31 fps. with : #define TFT_ILI9341 1 for >> "ILI9341_t3n.h" and this in 'F' : ...

@all - Paul - I got github to merge your changes into mine that was in sync with @mjs513 >> Changed to using ILI9341_t3n THIS WORKS !!! >> 'f' : read a frame using FlexIO (changes hardware setup!) <edit> : it now...

I started to do that - but some of the DMA disable stuff isn't compatible so switching that off is needed - and thought I saw you ask for a way to count DMA updates? And other than the Reformat because all the indents...

Indeed, Thread was marked BETA - and a good amount of effort shows GDB generally usable - but has some limitations - for whatever reason the author hasn't updated in 10 months. Whether lack of interest when time was at...

RTC on Teensy 3.x is "Compile Time" - filled in as HEX is created and unchanging - reload the same HEX 22 hours later and it can go back to that time.Off by 2 minutes suggests a long build time or delay in uploading the...

@mjs513: Made PR for the text.ino Sublime 'code reformat' - lots of tabs showing - odd indents? Added 'i' and 1 sec interval timer to track loop cnt and DMA callbacks > DMA has minor affect on loop count/sec and...

Just got around to pulling this morning's changes - will see where it stands - seems the DMA buffer will work for the Continuous sent to Processing without the bogus image result - will try that shortly. Got...

That is a big bunch of data - 300 consecutive 512 byte buffers. Though at 100-200 Mbs throughput that ~1.3M bits should be a blink. Though we've seen PC side using Java isn't a perfect conduit. Also - something...

That did it - it was set before ... The PDE transfer works here in batches. Again maybe it is something about using this USB-C Computer port on a newer faster computer? Had to restart PDE 3 times to get a sync's...

Got the DMA code and the screen goes crazy - seems my 4" Ribbon wires are too long for that speed and signal? Single and Continuous work well. It changes behavior when I touch and move the wire bundle - but...

Okay, I assumed that was like Teensy and would use the net USB speed ... Changed to : myPort = new Serial(this, "COM23", 960000); // Windows Seems to be the same? Also with 9600000

Number always coming up right - not getting a false trigger - but the buffer can start 'skewed' or go skewed :( Implemented "P" { upper case P } for :: g_continuous_pc_mode > quick hack - generally works for some...

Indeed that @Paul OSH board looks a good way to mount and debug. It is intermittently and often perfect - except for some batches. Just restarted and sent 3 PERFECT images - first two Teensy said 'not...

Just restarted PDE again and the back of the T_4.1 card came over perfectly. I have noticed if I stop and start the PDE 'too quickly' it seems I get : 'RuntimeException: Error opening serial port COM23: Port busy'...

Just restarted PDE - broken image again - the delay(3) not the fix :( Here is a Teensy card with light image out of H and V sync: > some of the images before this were worse with garbage <edit> > All sends are...

Quick note - I put in an SD card on the MachL and saved a usable bitmap with 3 hr old github - now see it is fresh 32 minutes ago - lib.prop update Sounds like good progress on something ...

Cloned the @mjs github for camera - not sure where the new code is evolving - have not read today's posts yet ... All seems well! >> Continuous seems FASTER? And it starts with "C" Running the PDE started a few...

Flash is memory too. maybe design a board to hold a PSRAM alive - would take a smaller battery - and it has RAM in the name. Just the fun of getting it the right voltage at the right time - all the time and not ...

This page : pjrc.com/store/ethernet_kit.html It has this image: Using the specified MagJack - all the stuff in the box handles bringing the needed signals to the numbered pins to route to the indicated...