Search results

I'm also driving an 800x480 display with the ST7277. I had issues similar to what you described but was able to resolve it. Here are the settings I ended up with: static constexpr uint32_t kHeight = 480; static constexpr uint32_t kVerticalFrontPorch = 14; static constexpr uint32_t...

Yeah, that flash chip won't work. See the "supported chips" section here: https://www.pjrc.com/store/ic_mkl02_t4.html

I haven't had any issues with the Preci-Dip 801 series.

I basically copied the traces from the MIMXRT1060_EVK design files on the NXP site. I certainly can't tell if what you have will work, but here are some details from the kicad trace inspector for the GPIO_EMC_* traces in my design:

Okay, first things first, it looks like this is using the HX8357D controller (found here). Looking at one of the examples for pin definitions and I see this: https://github.com/adafruit/TFTLCD-Library/blob/2f917ad72bf9d2c39cb741d2435df537770e8eca/examples/graphicstest/graphicstest.ino#L11-L27...

I followed through a bit on my thoughts and ended up cutting a PR: https://github.com/PaulStoffregen/cores/pull/753. It's not complete, but I'd be happy to complete it if @Paul can confirm that this has a possibility of being merged.

Checkout the "Power Up Sequence" on the bootloader page Paul linked to and walk through the steps (use the buttons to help you visualize) until you understand the flow. I would try to add more information here, but I don't think I can do it more clearly/succinctly than it already is on that page.

@KurtE thanks for working on getting this rolling. I've had some time to sift through the cores along with your experimental variants repo and I threw together a (currently very messy) script that generates a bunch of defines using data scraped from the annotated reference manual. My goal is...

The temptation to overclock is real, but I'm just playing it safe for now :p

Hey folks, I'm happy to report I was able to create a custom teensy with sdram using this thread as a reference 😁 I was already in the throws of designing a custom teensy board that had usb host, usb device, and microsd all on a single edge, and adding the sdram was a no brainer. The driving...

My main hesitation around connecting it is that I don't know if doing that will have some sort of impact on the sdram functionality. This snippet from the hardware design guide is what is causing my anxiety: The SDRAM interface (running at up to 166 MHz) is one of the critical interfaces for the...

I'm working on a custom PCB with SDRAM loosely based on @Dogbone06's deboard v5 and I'm trying to decipher exactly which MKL02 pins are required for a teensy 4.x compatible pcb. The pin in question is `PTA1/IRQ_1`, which routes to the iMXRT1062's `GPIO_EMC_01` in the schematic on pjrc.com: On...

@Dogbone06 did you make any updates to accomodate this comment? I'm looking at what I believe is the last version of the schematic/pcb posted, but I think i need to connect cc1, cc2, dp, and dm from L10 (the IP6520) to USB2 as in this schematic found elsewhere on the net: That said, I have no...

Whoops, I just realized the significance of 10x10. It looks like the devboard should use the DVL6B variant of the chip? It looks like that is available at both Mouser and Digikey, so perhaps a rework attempt is still possible?

Thanks for the details. It sounds like the assumption right now is that using the ...DVJ6B chip variant available on the PJRC store and elsewhere on the internet would address the issue, but that particular variant is less available (or just not available) at fab houses that are used for PCB...

Hey folks, any update on how the v5 devboards turned out? Is everything working as expected? I'm about to head down the dual frame buffer + elcdif rabbit hole, and given @Rezo 's success I'm thinking the lastest schematic/pcb posted in this thread would be the best place for me to get started...

You can definitely get well over 60fps at 16bit color with an ILI9341 using https://github.com/vindar/ILI9341_T4. That said, the true frame rate (and how "solid" it is) will come down to how much detail you have per frame, and how you go about scheduling everything your app is doing in loop{}.

Keeping a single thread for the general ideas and then kicking off new threads for more specific projects seems to make sense to me. This thread is a good read, and I think it's about to get a lot better very soon 😀

Mind if I ask how you're manufacturing these? I'm particularly curious about the MKL02 chip. Are you manually adding the chip from the PJRC store after having the rest assembled at JLCPCB?

Ah ha! The bottom layer strikes again!

I use 1uf, but please take that with a grain of salt. I'm just a hobbyist! On another note, I'm looking over the schematic and pcb, and I can't find U4 (W25Q128JVPIM) on the pcb. This is my first time using easy eda, so please forgive me if its there and I just don't know how to use the thing 😅

@Dogbone06 have you tested the sdcard on a previous generation? I'd expect a decoupling capacitor at the sdcard 3.3v pin would improve reliability 🤔

It looks like you already have these: AD_B1_00 AD_B1_01 AD_B1_02 AD_B1_06 AD_B1_07 AD_B1_08 AD_B1_09 AD_B1_10 AD_B1_11 AD_B1_15 That would make these pins the missing ones from the GPIO_AD_B1 bank: AD_B1_03 AD_B1_04 AD_B1_05 AD_B1_12 AD_B1_13 AD_B1_14

FWIW I've had success using blackketter/teensy4_header_breakout (forum post here) as a starting point for making my own PCB to get access to the SD_* pins via a surface mounted teensy 4.0: I was surprised by the quality of the castilated holes from JLCPCB, but the cost was a bit over the top. I...

WRT post editing time limit, it looks like this might be the setting you're looking for: https://xenforo.com/community/threads/edit-post-time-limit.49152/

Regarding Domingo's recommendation to use neopixels, I'd also highly recommend them, especially if you have one of the pins that Paul's WS2812Serial library utilizes. It allows you to control n RGB leds using a single serial tx pin. So if you want to create a 20 led VU meter that goes from blue...

I have an update on this: the pcb I ordered from my first pass at the schematic appears to work correctly! I ended up adding some jumper pads for IM* pins in case I had chosen the incorrect interface mode, but it seemed to work when I soldered it up to match the schematic. A couple of notes...

Looks like it's going to around for a while: https://forum.pjrc.com/index.php?threads/future-teensy-features-pinout.57842/post-332995

After mucking around a bit and analyzing the components on the pcb for the non IPS display I already have, I think this schematic summarizes what I need to do: As mentioned before, I'd appreciate any input to confirm whether this looks correct.

Hey folks, I've been working on a project for a few months now, and I'm trying to polish the hardware a bit in a new iteration. Currently I'm using a Teensy 4.1 along with the Color 320x240 TFT Touchscreen, ILI9341 Controller Chip display purchased from PJRC. While the combo is performing well...

Hey folks, I'm working on a project and I'd like to use C++17/gnu++17 instead of 14. I'm able to get 17 working fine, but I'm wondering if there is a reason that it's not the default. grep teensy41.build.flags.cpp ~/.arduino15/packages/teensy/hardware/avr/1.58.1/boards.txt...