mjs513

While @KurtE has been busy with CSI we also been playing with the OV5640 5MB camera which we got from Adrafruit: https://www.adafruit.com/product/5673 for the most part it was compatible with Flexio that we used for the OV2640 but of course lib...

Thought I would mention, I am currently playing with trying to add CSI support for this library, as the Teensy 4.1 has enough of the CSI pins exposed for 8-bit transfers, and the control signals. I am starting off with the OV7675 camera, and I...

I think it might have more to do with the ER-TFTM101-1 display as I am using the same length wires as well. I do not have any other displays to test with...

As some of you know I made a 4.5 (facelift) that adds USB-PD (USB Power Delivery up to 12V). And it also has SDCARD. Those are the only changes made (moved the boot button position as well), hence the word facelift. The USB Host port has sort of...

Here is a slightly updated version of the spreadsheet that I currently have:

Note: that is simply a print to pdf of one of the pages in the excel document: https://github.com/KurtE/TeensyDocuments/blob/master/Teensy4x%20Pins.xlsx Note: @mjs513 did a modified version of this that I think is in @defragster github project...

@wwatson Really nice job and alot of testing to find the issue!!!! Nice that you got the three branches set up - at least for SPI probably keeps it cleaner. Still waiting for my lcd/camera shield to test with the SDRAM board - hopefully today...

Update ER-TFTM1011-1 10.1" LCD is working on the T4.1, MicroMod and SDRAM Dev Board V4.0. All except MicroMod work with 8-bit and 16 bit bus configuration. The T4.1 is by far the most stable of all three. The SDRAM board and MicroMod are unstable...

If you are building a specific board for a specific purpose, I say have at it! IF you like hard coding it like: IOMUXC_SW_MUX_CTL_PAD_GPIO_AD_B1_13 = 0x4U; IOMUXC_CSI_DATA04_SELECT_INPUT = 0; IOMUXC_SW_PAD_CTL_PAD_GPIO_AD_B1_13 = 0x0U, go for...

Yes you are right that B1_12-15 are already on the board. We should probably make a new version of the excel document which has all of these pins on it... As for mixing CSI and FlexIO. Not sure how... Probably need to read those sections in...

@mjs513 did the one for the devboard that I am looking at. Looks like most of the pins are there. We are currently using AD_B1_04 through AD_B1_15 Mike does the below look correct to you as well? The T4.1 defines we were using.. The numbers...

Quick answer is yes. in one of the conversation posts I listed them as well: which is the same on your list.

I’ll make a gen5 of this board, all I need from you is a complete list of pins. I know you’re very good with the pin stuff since you made those PDF’s on Git. The SD-Card uses the SDIO pins yes.

Ditto since I am using @KurtE's mods - makes life a lot easier

Works for me, with the Devboard, as I created a variant that had all of the extra pins defined. Otherwise you would not have pin numbers to work with... True, typo...

A couple of questions and things I am playing with... With the 4.5 and SD adapter: guessing you used SDIO pins? (Same ones as defined for Micromod?) of if SPI which IO pins? CSI pins - I am in the process of integrating in some CSI support...

I did not bring out any special ports. All that was done was SDCARD and USB-PD. But ofc we can keep going and make a gen5 that has more stuff. But it needs coordinating, Rezo and KurtE together could make a full pin mapping, that would be ideal...

One question did you bring out the csi pins?

Wow you been busy!!! Nice job

So I decided to make a facelift, adding SDCARD and USB-PD which supports the PD protocol up to 12V. There are pads to solder if you just want to use the second port as a pass through with 5V. Meaning, it will deliver the same 5V coming into the...

Just wondering, are you saying that on the current Devboard 4, that the 3.3v Voltage regulator is maybe to anemic to run some of the different devices that you have connected to it? And that maybe we should add another one to connect the...

Testing the different cameras on the SDRAM board became problematic - not sure if wiring/connector issue but alot of problems we were seeing was with the wiring as @KurtE mentioned on the camera thread about wiring. So we decided to make a...

Since a Teensy 4.x is so fast, I would add a delayMicroseconds(1); after the clockpin going low as well, like so: uint32_t SPIencoder::readRegister(void){ // Initiate variables uint8_t inputstream = 0; int outputVal = 0; uint8_t...

Don't know much about this encoder to be honest but my guess the problem could be with the delays in this function: uint32_t SPIencoder::readRegister(void){ // Initiate variables uint8_t inputstream = 0; int outputVal = 0; uint8_t...

Thanks for the response. I wired up the dev board again and started testing with the baseline driver code I posted. It shows something is wrong in the dev board/MicroMod side of my code. No matter what I set the bus speed to loading the same...

Thanks Kurt - probably should add some of this to the repo on the examples :) Anyway for those of you that don't know about the projects I mentioned earlier, they all use single class, #include "Camera.h", to call the different cameras and if a...

To give you an idea ran the OV2640 camera using the Aducam at SVGA resolution with an antique special effect in jpeg format Same JPEG image downsampled on a ILI9341:

@KurtE and I have been at it again. This time creating a library that supports a number Arducam/Arduino camera modules: Model FrameSizes Pixel Formats Omnivision OV2640 FRAMESIZE_VGA //640x480 FRAMESIZE_QQVGA, // 160x120...

@PaulStoffregen Updated existing PR for this fix. Did run @defragsters QPINAND data integrity sketch and all appears working. Did notice that there are a few outstading PRs against LittleFS that were never incorporated. Probably should be...

Just a follow up - looks like the cmd 8 needs to be initialialized, so the new function should read: const char * LittleFS_QPINAND::getMediaName(){ uint8_t buf[5] = {0, 0, 0, 0, 0}; // cmd index 8 = read ID bytes FLEXSPI2_LUT32 =...

Finally got my test board out and can confirm something is wrong - I am seeing the same issue. Without calling getMediaName failing. Its been a while since I worked on this but will see I can remember.

Here is the SDRAM board and ER-TFTM101-1 TFT working in 8080 8-bit mode. It's a start:) Waiting on some info to try out 16-bit 8080 mode...

Hi Defragster - I am using @jmarsh's SDRAM_EXTMEM library. I only had to modify one sketch that was setup for the T41. The rest of them work out of the box. The sketch that I modified was "flexio_vga.ino" which basically just changed the VSYNC...

Just re-did it all and it's working :D Must have messed up on the wiring. Probably one off. It now works out of the box...

@jmarsh - Tested the elcdif sketches. Impressive:D Did not realize the mandelbrot sketch was animated. Now to hook up the 10.1" LCD and test... EDIT: By the way the T41 on the breadboard is the first T41 I got from PJRC. It has the white...

First simple experiment on SDRAM board works. Adapted my 4-bit VGA library based on @jmarsh's driver to the dev board. Just had to change two pin defines for FlexIo2 for HSYNC and VSYNC which is used in several places in the FlexIO begin method...

Just received the sdram development board today:D I ran through all of the test programs that I know about without a problem. I need to make sure I have all of the pinout info for this board. It is a version 4 board. I thought I would start out...

Actually you still need these parts in place of gpioRead() and gpioWrite(): pFlex->setIOPinToFlexMode(12); // For /RD signal pFlex->setIOPinToFlexMode(10); // For /WR signal So here is a a version of lcdDataRead() that works...

Thanks, I'll take a look at it. So far it has been my lack of knowledge of FlexIO and DMA that has slowed me down but I'm starting to understand it more...

Not having much luck on win11 pc. Every time I download. Funny though while I still get the trust issue from MS norton reports hello3 as safe.

This latest one appears to work... Got the two messages that Defragter mentioned and then: And ran from terminal window and it worked

The short and simple answer is you should uninstall or delete SdFat you've installed, so Arduino IDE will use the copy of SdFat which comes with Teensyduino. When you install a library, usually Arduino IDE gives your installed copy priority...

Posted an article on the website today with info about how the Windows EXE cross compile and signing works. https://www.pjrc.com/how-to-cross-compile-and-sign-windows-exe-on-linux-with-yubikey-token/ Hopefully it can help other people who want...

Downloaded and ran on windows 11 with Norton. Saw the same as @defragster - reported it safe to MS, then said keep anyway with no issues with Norton. Ran hello2.exe and ran fine - and saw the same signature as @PaulS

My startup, Bolder Flight Systems, recently completed development and flight validation of a Portable Data Acquisition System (PDAS) for manned aircraft. It was developed with the International Test Pilots School (ITPS). GNSS-aided inertial...

Kurt et All: The resistor combination you are seeing on that pin is what we in the hardware world call a "digital active termination". Why Sparkfun has done this is anybody's guess. As you have already surmised that pin will only be usable with...

In the case of the ATP, I believe that this is due to the Voltage Regulator they choose for the board. AP7361C states: Wide Input Voltage Range: 2.2V – 6.0V And yes if you build your own board, with different VR or DC to DC converter, you can...

You can alter the alert/panic temps in the core files: https://github.com/PaulStoffregen/cores/blob/master/teensy4/tempmon.c#L10 Change this at your own risk. I have set my panic to over 100c for a product that sits in direct sunlight (and is...

Sorry for the delay in getting back to you. My guess is that it has a different PID/VID than the one I am using or that is covered in the library. Trying to remember how to sort it out. Lets see if we can figure it out though. First you...

The MicroMod is working with the ER-TFTM101-1 display. Still have to get the DMA portion working on the MicroMod. The images were produced in 8-bit mode none DMA, 100ms to display both pictures. I'm sure DMA will speed things up. By the time...