defragster
Senior Member+

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

2.8" PJRC w/ILI9341_t3n Display not showing any issues with latest github release Single or Continuous >>- Just the PDE over USB data sync to display image data it seems can get part buffer it holds until the next...

Is this to mate to a T_4.1? Look at PJRC.COM for their adapter - and has link IIRC to OSHPARK where there is a drawing of the PCB - between those two the parts and wiring to the proper indicated MagJack should be...

It has something in the USB COMM SYNC it seems - as noted I restarted and got garbled images - restarted again and counted four finger images perfect from the first. Just did a STOP and RUN restart of the PDE and got...

If the HID message transfer from Teensy is working to Windows and can be polled and read? Assumed that was working - just not the desired behavior sitting in a tight loop watching for the next input? Once that is...

Something odd - as switching to the _t3n generally working here - >> Always on the display : Single or Continuous { who picked those swapped input letters :) } >> Iffy on Processing starting up - restarting it...

Latest Github has fixes that work - using ILI9341_t3 ... NOT "N" > again not sure what changes ... - but going to this also working :: #include "ILI9341_t3n.h" 's' - continuous works! Also for processing:: the...

Correct - 'p' sends a single image. But 's' continuous to display is not doing that. I did change the 320x240 layout - but somehow only grabbing and filling top half of frame - full width is accurate ( and usually...

Switched back to 9341_t3 and still not getting continuous. Here are example processing displayed images I see: <edit> Next processing images has L<>R split again? Will go grab github version ...

Thought maybe it would point to a known change? IT was working when using the 9341 NOT_t3n

That fixed the Left to right drawing split. But still bottom half black and it draws the top half twice?

Also seeing Continuous mode only snapping one pic? Using 9341_t3n

Yes, changed to 9341_t3n - not sure what that does differently. The ON SCREEN 9341 is PERFECT - that screen shot is what Processing presented. It seems to not use current buffer but Snap another Image - maybe it...

Using SFUN and 9341. Ah - so the stored buffer data is unique to 'process'? Other images were broken worse at times

RE :: Okay Dual Serial and SendRaw enabled ... Image is showing - often torn, partial and ugly though? Not a true copy? See the fingers are not in sync ...

Thanks for the tutorial ... I wondered as the only line I saw was //mac ... the sketch was scrolled I see now :( - Opps. Okay Dual Serial and SendRaw enabled ... Image is showing - often torn, partial and ugly...

There is no 'inherent reason' for the LED to blink at 1Hz. That is only controlled by the sketch uploaded to the Teensy. Something interesting is happening - but code loaded on the Teensy is causing that behavior...

Now getting grief building last github : ...\libraries\HM01B0\examples\hm01b0_test\hm01b0_test.ino switched to : #include "ILI9341_t3n.h" ILI9341_t3n tft = ILI9341_t3n(TFT_CS, TFT_DC, TFT_RST); Still...

Cool, Will move to the ili9341_t3n - is that a WIP branch or other? ... I see Master as most recent update 26 days back. :: github.com/KurtE/ILI9341_t3n Got processing onboard to figure that out - seems to come up...

Okay that $15 3.3V SPI 2" ST7789 should arrive Saturday. Thanks for the confirm. Thought that was the PC "Processing" code I've not installed yet on this machine.

What ST7789? 2" and 240x320? I see this : adafruit.com/product/4311 :: 2.0" 320x240 Color IPS TFT Display with microSD Card Breakout How similar is this for faster delivery and no SD ::...

No problem to change to ILI9341_t3n ... I just started with known good installed code as the HM01B0 example just used simple Rectangle to draw for the buffered image and was happy to see it working. Will see if I can...

Not seeing any Serial or Seria2 used in p#7 code to Freeze???? As noted Serial would be USB and Serial1 would be UART1 (on RX1 and TX1 pins ) and Serial2 is UART2 (on RX2 and TX2 pins ) As far as the code hanging...

Here is an #ifdef update version of that sketch to select TFT_ILI9341 or TFT_ST7789 > tried to restore the ST7789 code > removed two warnings about int and uint mismatch Also swapped 2.2" 9341 for a 2.8" PJRC...

Does this lead to a way to have a message queued to the app : docs.microsoft.com/en-us/windows/win32/inputdev/about-raw-input Seems that provides a way to get a WM_INPUT message for a registered device before Windows...

Good CLEANING job mjs513! :: libraries\HM01B0\examples\hm01b0_test > Works single shot and continuous! That is The Machine learning carrier taking an "up" photo from my keyboard tray - As displayed with 2.2" ::...

Never got one of those 7789's - found a 7735 but size is off. ILI9341's galore ...

And for a display? showing #include <ST7735_t3.h> // Hardware-specific library #include <ST7789_t3.h> #include <SPI.h> #include <SD.h> #define TFT_DC 1 #define TFT_CS 5

@mjs513 - is this just plugged in without alteration to the ML Carrier for voltage as Paul may have done?

Assuming this is a T_4.x from context and 912 MHz speed? And no idea how much soldering and other added thermal mass attached. On T_3.6 and prior Teensy the CPU speed was derived from common clocks and changing...

On a 'good' day "unlimited" power is nice :( > Sounds like your attention will be good for having it made right, as usual.

Suppose SFun ATP docs would show the circuit for their USB-C and power to the board and HOST connect. Maybe too much for a quick/simple board - but it would be nice to have that power - especially with display and HOST...

Thanks for that. Busy morning here - the PJRC Carrier board looks good. Having USB-C would be okay - or better. Assuming using that connector is how the SFun ATP board presents more power to the board? Using...

Yes, like before in the other thread for the outputs: for (int i = NB_PADS; i < NB_PADS+NB_PADS; i++) { But - using analogWrite ... with those correct offsets ... should be more direct with hardware support...

@Jibeji - you made a new thread I see ... T_3.2 has PWM driven Analog pins. I just wrote this on a T_4.1 for A9 or pin 23 the T_3.2 has as well. void setup() { Serial.begin(115200); while (!Serial && millis()...

Indeed the T_3.6 was potent at 256 MHz - @BrTaylor can fill more details - seems the IMU cycle was 500Hz with what he was doing years back - and reading GPS strings in addition to the 9DOF IMU - and sending all data off...

Great that was an easy solution for the situation to get your system in spec and ready to ship and install.

@Paul: Minor edit to LFSIntegrity to HALT on failed myfs.begin() :: github.com/PaulStoffregen/LittleFS/pull/11

Minor edit to LFSIntegrity to HALT on failed myfs.begin() :: github.com/PaulStoffregen/LittleFS/pull/11 - just got two T_4.1's mixed up and failed to catch the passing NAND and NOR fail notice on QSPI

@brtaylor might have some real world flying Teensy experience? The T_4.1 bottom QSPI pads can hold PSRAM'S - not static enough perhaps. > how much space is needed? > how many bytes/sec to write? Asking because...

With active INPUT_PULLUP coming from the T_4.0 - could the 5V just be cut? Remove the resistors or stop the source 5V feeding them? That would leave the T_4.0 holding 3.3V until the NO button is closed.

There are solderable boards laid out in breadboard format that headers could be put onto to socket a T_4.1 if not soldered directly. That would give 'generic' but solder reliable access to all pins. Given all the...

RE: Hat/Carrier ID - indeed adding anything would take board space and use up a pin or more or require some 'bus' to be polluted. Or in that rPi hat case - require more effort. Looking at NewPinTest - the code is not...

Indeed confirmed with NewPinTest in p#166 above : No pins change on Display Carrier SD insert/remove. Also updated the PullUp test shows pin#2 held low. So there is possibly a 'signature' for each board reading GPIO in...

P#54 shows: On MMod DataLogger and MACHINE LEARNING PIN 10 is the CARD INSERT says NewPinTest! And p#34 has : NewPinTest sketch I wondered about Carrier Board detect too. Nothing Easy - would be piecemeal for...

Quick note : using the prior posted NewPinTest it showed pin 10 ( also CS? ) as the card insert detect. That would work on SD pins as well for ID - though I did not do that. @KurtE - pulled down the newer non-debug...

Should be some easy change to : UpdateHistogram() @ HD_ThermalCam_v1.0.ino#L694 Display.fillRect(293, 200 - (j * 3), Length, 2, ILI9341_BLACK); Display.fillRect(293 + Length, 200 - (j * 3), 24 - Length, 2,...

Noted sketch was the one in USB_HOST_T36 :: mscTesting.ino Just ran bare 640MB HDD on SATA Adapter and like prior post is shows the APRICORN adapter not the Drive maker as VerndorID: connected 1 initialized...

Nice looking work!

Modified TSET to work with Beta SFun MicroMod Teensy for Windows CMDLINE build :: github.com/Defragster/Tset >> Works with IDE >> Best with Integrated TyCommander, when updated to support MicroMod (done with a...

Yes, the beta included testing of the 15 second restore. Once the Teensy is packed by PJRC the Restore Blink sketch is FROZEN in a no re-write block - so that had to be perfected before production. That code was...

When you say 'removed power'? > That should not be needed, and if the RED LED was in the 'sits there' state and power was removed the Restore was not yet complete - possibly just the failure to fully blank the...

Good work and good luck KurtE! Looking forward to getting to use it. As KurtE saw in Github email - @koromix will build release if the debug version of the edited code works.

Running the newest version of Windows for last years as it has evolved and never any trouble with Windows 10. In fact this machine is on the not yet released 2021 Half One release on the Dev channel. For a NEW...

The sketch ran one time - I hit enter with the FLASH drive directly plugged in > giving the first output block I pulled the FLASH and plugged in the Single Hub Device that has a 120GB HDD in it ( while it was...

Second test - Powered that Hub its internal HDD and added Flash come up. Pulling USB cable turns off the Carrier board and also Using the Nifty Digistump USB power line switch it stays connected USB but switches off...

I copied libs yesterday - just got a compile done in USB_HOST_T36 :: mscTesting.ino SerMon out put below shows it finding First the SINGLE 64MB Flash drive. Wondering about a HUB ... my external (powerable HUB)...

Not sure what sketch is being uploaded? Sounds like it is cratering on starting? Try a simple blink with USB:Serial and add this to start setup() to see if anything shows up with SerMon ready on the right port when...

Not seen email reply - just made an issue as I should have : Koromix/tytools/issues/75

That shows as :: fork of Richard Barry's freeRTOS, optimised for the Arduino AVR devices. It is on the ESP 1 and 2 core and on the NRF's to allow time for radio interruptions <edit>: if an easy Arduino standard...

Good - as it seems from the board : Wire and Wire2 ... once I got enough clarity on the silkscreen and noting the cusp over WIRE1.

@mjs513 - incomplete question - and silkscreen read ... ? There are two qwiic'c on ATP in pic low left and right. Assume left qwiic is WIRE == i2c, and right qwiic is pulling from those pins as WIRE2 == SDA1 ==...

@KurtE: No word from @koromix on update to TyComm to support T.MM - you did it before ... code is 0x26 for T.MM > That would be great. Yes, tiny camera module @mjs512: Pinout 'card' looks handy including note "...

The sniffer looks like fun - I ordered one but never used it yet. Those solder points are tiny targets - but it can work - as long as the 3.3V probe avoids the GND and the GND probe avoids the 3.3V. The #ifdef'd...

Glad to help, have fun with the rest of it.

Yes. The second loop never runs because 5 is not less than NB_PADS==5 try: for (int i = NB_PADS; i < NB_PADS+NB_PADS; i++) { pinMode (i, OUTPUT); digitalWrite(i, HIGH); // <-- this should illuminate...

That is a static reading of the pins in Pull Up or Pull Down when that 'test mode' is entered. Ideally with nothing connected all pins should show 0 on PULL DOWN and 1 on PULL UP, when things are connected, or there...

Opps - that was updated for use on a T_4.0 and 4.1 - not properly #ifdef'd it seems ... I wondered about that ... I'll give it a look ... Here is a quick edit to pull out the 1062 specific code Paul wrote to test...

Cool - glad I asked - that was easier than being first :) ... got run for new windshield install ...

:) - nice to get to use the mapped SFun MMod names! Standard Metric? that's an oxymoron here :) > Thanks :: 4mm M2.5 pitch screw -- > Even if it takes a Longer 10mm and a pair of locked nuts at 4mm - I'll have one...

Me too - you did good :) , didn't see it had been tested with that (pre-release?) 2Mb variant Paul got so just hooked it up. It has been on my mind to see it run so requested one.

@luni - mmBus works on ATP pins G0-G7: void loop() { digitalToggleFast(D0); delay(600); // much blinkier that (1) mmBus = 0xff; // write 8bit value to bus digitalToggleFast(D0); ...

@mjs513 - can you list the current github'ery needed for MSC/MTP/USB_HOST/??? as needed to get current with that?

I saw 'just' written after I posted and started to edit - but never know if posts are read before I can edit ... but the MMod JUST arrived :) That test was created - with two of them special - when @loglow was making...

Sorry - trying to get off this thing for Zzzz's ... The D0 was a total mystery until I looked in the header ... and then read the silkscreen ... left it to be funny ... because you are mapping to be helpful and it...

thread search found it for me - #34 :: MicroMod-Beta-Testing I did edit a BOLD label with advanced on it just now.

Was wondering why SerMon output showed AUDIO when the code snippet did not. But 11 and 13 are the T_3.6 default functions for those pins - so those lines are not useful - unless moving SCK to #14 with audio adapter....