Dogbone06

@wwatson echoing @mjs513 - great work getting the driver ported to the different boards! FlexIO is a bit confusing at first, but the 8080 stuff is fairly simple to setup and debug compared to other protocols. The place it gets messy and really...

Most of those pins are already there, iirc the only missing ones were some of the data pins around CSI 2 to 5.

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

You have B1_12 and B1_15 available for pixclk and mclk. I would recommend using the pins shared with FlexIO2 wherever possible (for example hsync and vsync are on B1_14 and B1_13), since that's better at handling variable-length (compressed)...

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

My main question would be, what do you even need the Teensy/Arduino pin numbers for when writing code for modules like CSI and FlexIO? You can use IOMUXC_SW_MUX_CTL_PAD_GPIO_x and IOMUXC_SW_PAD_CTL_PAD_GPIO_x to initialize them (which works...

@KurtE can we get an original excel copy of this so that we can edit it? https://github.com/KurtE/TeensyDocuments/blob/master/Teensy4%20MicroMod%20Pins.pdf

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

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

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

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

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

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

@KurtE I’ll add all the pins you want. As that will help the community. So go ahead and together with @mjs513 or anyone else, compile a table of the missing pins. Ideally you’d make a complete table of ALL pins, maybe some of the ones exposed...

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.

Pushed the "DCD" intialization example to github: https://github.com/A-Dunstan/SDRAM_EXTMEM/tree/master/examples/DCD_Init The magic is in dcd.cpp: DeviceConfigurationData is basically a uint32_t array of registers and values to be put in them...

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

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

Was hoping you'd included the voltage regulators for the OV2640's additional requirements... you don't want to see the mess I've got with LM317s.

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

No. The OV2460 runs off three different voltages: 2.8V for the analog sensors, 1.2V for the core and 3.3V for the I/O portion. The ArduCam boards have two regulators on the back to generate the lower voltages from 3.3V but I just have the camera...

I found an Arduino 8080 parallel IF used for the RA8875 (same 8080 interface as RA8876) that uses 74LV245's as buffers for the Due and possibly the Mega 2560 found here. I am going to order up some of these chips if I don't have any left and see...

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

@Rezo Here is the FlexIO2 pin usage I am using: FlexIO2------- Dev Board-------- ER-TFTM101-1 Pin 2:00 -----------> B0_00 -----------> /WR ---> 05 2:01 -----------> B0_01 -----------> /RD ---> 06 2:02 -----------> B0_02 -----------> 2:03...

@wwatson, note that the traces between the NXP and the SDRAM were directly copied from the EVAL board to minimize problems. The SDRAM has worked nicely for everyone else. But there has been some playing around with the capacitor and speeds...

@Rezo maybe you know more? You ran RGB at 24 bits.

Made an interesting discovery: it's possible to initialize the SDRAM even before any code gets executed, by filling out a DCD (Device Configuration Data) struct. The ROM processes it and takes care of programming all the SEMC registers when the...

That’s awesome! Good work :D

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

I appreciate that you posted the working code. Good sport!

It was a RTFM failure on my end. The mention of the missing AudioMemoryCall() made me start again. I had indeed not included all of the audio setup. I was working from the Audio Design tool, not the tutorial sketches which was a mistake. Sorry...

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

I'm not really sure why this is necessary? Both boards have B1_12 & B1_13 and they're not referred to by Teensy pin number (only their pin matrix code and FlexIO ID), so making them dependent on the platform doesn't make much sense to me...

Unless I missed something both B0_12 (35) and B0_13 (34) did not respond to a pin check with and LED connected to them. Just rechecked and they are not connected as well as pin B1_02 (36) and B1_03 (37). The only pin that is labeled as a T41 pin...

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

If those pins are not responding but adjacent pins are, then there is a hardware issue with the board, bad BGA soldering from the production run. @Dogbone06 FYI

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

Hello, I’m on the hunt for an all-in-one SGTL5000 and Amplofier in one PCB. There are such boards from Adafruit and others. But they don’t use the SGTL5000. I’m all new to audio stuff. Appreciate any input. Thanks!

Or use a 🔨 😉 Not sure what temperature solder that was used. Mine was a bit stubborn coming off, so I partially cut it off...

The solder paste used on these boards are high temp 260c, it's actually very good solder. But to get something off you need a good iron and some flux. Or add a little more solder paste from a siringe (the latter is the best and easiest option)...

In the pic above it is the SPEC below the red squiggle here over the 1062 Not so small if you zoom in :) - next to organic sugar and Kosher salt. Add flux or put solder blob on solder tip maybe and it should wipe away easily enough and then...

Awesome it arrived and works! V4.0 is the same so far as all else here. See this post on prior page: https://forum.pjrc.com/index.php?threads/call-to-arms-teensy-sdram-true.73898/post-340933 If you get any SDRAM integrity issues that lone cap...

Thanks, I do have that document. I ran the oneScanCaps.ino sketch and most of the frequencies had no errors. Interestingly enough 166MHz had one error. I am not sure which cap DQS has on the board. I can barely see it even with a magnifying...

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

Not sure, but most of their carrier boards, have something like: That is from their ATP board schematic. As for AREF, don't see that on their stuff. With Teensy it is probably geared more to the 3.3v pin. I don't believe raw VIN is passed to...

To be honest im not sure either. Why would you need to know supply voltage if it won't work with anything much less than 3.3v? Also if it's battery powered there will be a DC-DC converter providing a stable 3.3v regardless of cell voltage...

What I'm wondering is why would Sparkfun connect the pin that way (on the micromod) in the first place though? Since it can't be used as a regular IO pin if it's hardwired to a constant voltage... nor can it be used in analog mode to monitor VIN...

Finally got around to sitting down and mapping out all the exposed pins properly and found something odd - there's a pin labelled BATT_VIN/22/A8. My first thought: "how can this pin be both BATT_VIN and an I/O pin?" The answer is it can't/isn't...