Search results

Bug-free lines I write, Errors flee before compile - Silence in the logs

I think I sent you the one with the SDcard connector, allows you to use SDHC1 via the SDcard slot on a T41 instead of wiring SDHC2 to pins. Just needs one wire in the header to a pin for sleep, IIRC. That's the device I used to get the first one of these things to work. But @defragster seems to...

@joepasquariello Thanks for FlasherX! Works like a charm. Just got it working to flash a Teensy 4.0 via ESP32-S3 Wifi / UART to T4.0. I use EEPROM on the T4.0, so got burned by the same issue of being informed there was not enough buffer space in flash (which lead me here, eventually). Given the...

I had a version of this board that plugged into the SDcard slot on the T4.1. I can't recall correctly, but I think the INT GPIO might be optional, so that setup would only require a single additional GPIO pin, although obviously you can't insert an SDcard :)

Must have added SER_WHITE to the colors and forgot to add it to the "blank" section Colored messages make it so much easier to "scan" console logs, even simply making error logging red means you see it at a glance rather than hunting, and with color-coded messages for different classes, your...

Just comment out line 81 in misc_defs.h, and they'll not appear, no need for extensive code changes #define USE_DEBUG_COLORS

Hahahah, thanks, it started as an essential app (the lightning trigger part) and I just kept adding and adding less and less useful stuff until it eventually just became a catch-all as I had built so much infrastructure for everything :) Screen is a BuyDisplay 7", but SSD1963....pretty fast...

Here is my info: 816MHz (with PSRAM @ 198MHz and SD card @ 99MHz) Speed set in code via set_arm_clock Copper heatsink, 10mm x 10mm x 4mm Teensy is tightly sandwiched lengthwise between two 4.5” x 2.5” PCBs, but ends are open...screen/audio chip is above, main board below PCBs are two layer...

Good test @KenHahn and if OC'd CPU results are in the master list, would be good to throw some OC'd Teensy ones, too, for reference. When my T41s are operational, they run at 816MHz with passive cooling (small copper finned heatsink), been doing that for several years without any issues on any...

You mean..... Like the brand new account of yours that Paul allowed whose sole purpose was to dunk on his sole manufacturer and advertise a product to compete with him, something your OWN rules prohibit over on your patch?! If I was you I really would take a breath, enjoy your new baby or a...

Well, this thread went down well with my popcorn! So as I understand it, Some at Adafruit have a long-standing beef with some behavior from SparkFun, so to "get them back" they propose open source hardware that differs completely from a Teensy 4.x in terms of capabilities, and advertise it on...

Be interested to hear more feedback on the UNO Q. As someone who has migrated to Pi 5 for screen-based projects, but pairing it with the Teensy4.1 for the things it is good at, this SBC / MUC hybrid intrigued me, but it seems to be two underpowered devices paired together and possibly coupled in...

That's a good question. We're running at 528MHz. The original code owner has a board from dogbone06 that was used in the forums, I'm using a later revision with several hardware changes. I had modified my local clockspeed.c to increase the voltage if clockspeed was greater than 528MHz (to 1.3v)...

Interesting timing! This week, I was helping diagnose code on a custom Teensy with SDRAM (I2S audio player software) that was experiencing random crashes. Whilst making code changes to attempt to diagnose / resolve, the test plays a song too loudly and got annoying repeatedly playing it, and...

Hahahaha, nice! Although I need to check the code, negative compression of the data isn't good :)

Interesting idea but "sending the screen frames as JPGs" would also require "server-side" software on the Teensy, right? Plus, this implements remote touch too, not just screen casting, so you'd need something on the Teensy side to interpret that. *edit* You probably meant client side :) The...

Hmm, not as it stands, no.....but just pushed an update to the repo which guards ethernet code with the #define USE_ETHERNET in the header, and defaulted it to commented out, so it should build without ethernet now.

Good luck!!

Double-sided tape on the standoff and no-one will ever know it's taped :) I noticed the '32Khz' on the silkscreen, which I assume is to provide the external sleep clock. We had some debate on this with the 1DX when it was not showing signs of life initially, but it was not necessary to provide...

Would there be space on a Teensy-sized WiFi / BT shield for the user to (optionally) add the eth MagJack/header/cap and make it a full 'connectivity' shield? I'm guessing 'not quite' from a width perspective, but I'd say it's worth considering? For the WiFi programming on the @Dogbone06...

I'd check the resistors around your crystal circuit, particularly the 2.2M one

It's disappointing, right, that they can't play it from SDRAM? I think it's because this screen is meant to be used by really low end MCUs in an end product, so they offer all that acceleration onboard for 2D and the product manufacturer can add a flash chip with any final images/videos they...

It doesn't result in an overflow. That line you get the compiler warning on is guarded by: else if((DRAM_FREQ>=32)&&(DRAM_FREQ<=39)) so that code will not be executed unless DRAM_FREQ is between 32 and 39 inclusive, so the overflow situation warned about will not happen for higher values of...

It seems as the years go by, I'm having the same issue :)

Hmmm, haven't really looked, but I wouldn't bet money on it, unfortunately.....I haven't looked at every source exhaustively, but when I've been looking at 800*480 resolution, the NT35510 doesn't seem to be present in much larger than 4-5". The SSD1963 is available at 800*480 in 7" from a couple...

On the RA8889, I've gone as high as: #define OSC_FREQ 10 #define DRAM_FREQ 250 #define CORE_FREQ 210 #define SCAN_FREQ 50 using 8080 16 bit parallel. Improves the speed of the display both with 2D functions and writing to SDRAM, but it still is nowhere close to what I can...

Yep, CPU is fast. ILI9341 not so much and, if you're using blocking SPI transactions to update the screen, SPI runs at a fraction of that 600MHz clock, so depending on your screen resolution, screen update size and wiring, you can burn up several milliseconds per refresh.

No less than QWERTY keyboards are irrational today. Made sense, once :) "Back in the day", analog TV sets used the 60Hz frequency of the electricity supply in the US/Japan as a frame sync.....and as with all old standards, as new things evolved but had to work with existing tech, the standards...

Depending on the refresh rate of the screen (typically 60Hz), it isn't going to update the display pixels from the framebuffer any more frequently than every 1000/60ms (16.67), so any writes to the framebuffer more frequently than that are generally never going to be visible and wasted...

DigitalRead works just fine....I also suggested above removing the while loop to see if it functions, as it's obviously related to the read state of the switch.... @MarkT suggested debouncing, which I concur as a good diagnostic option, but you stated "debounce should not be required" when, in...

What kind of switch is it, and what duration is it pressed for? If it is a momentary push switch, absolutely the mechanical action could cause it to chatter high/low rapidly as @MarkT suggests, so it could be a rapid high/low that drops into your bypass on high but is low and it will exit, and...

How are you determining one way works fine, and the other doesn't, ie what indications do you get that data is passing back and forth in one way, but not the other? I see no prints, etc. to inform you of that. Just guessing here, but what is connected to Serial1 and Serial2, and what actually...

If you haven't already, you can increase the PSRAM clock speed. It defaults to 88Mhz, but 133Mhz is commonly the recommended speed in this forum usually compatible with the "stock" PSRAM chips. I've gone higher than that on PSRAM chips rated for 133Mhz default ((180Mhz one some and 198Mhz on...

It's stuck in an infinite loop in: while(1); The semi-colon needs to be removed, as it breaks the statement so the guarded code is not attached to the while. It's effectively the same as if you wrote: while(1) {}; { if (Serial1.available()) { ... } It would never leave the...

This sounds very similar to the issue here. Fix listed here is to close the Serial Monitor https://forum.pjrc.com/index.php?threads/arduino-downloading-index.76192/#post-352600

This looks awesome, I'd like to try it soon on the T41, if you're willing to share once you've got all the gremlins out! eLCDIF has been working on a custom Teensy made by @Dogbone06 with 32MB SDRAM, and @Rezo made a library for this, I believe its public. I have been playing with that using...

@KurtE - To verify how to use this on a custom Teensy using the same SDIO2 pins defined in your SdFat mods: 1) Make the changes present in your PR for imxrt.h 2) Download your SdFat_Experiment_SDIO2 library 3) Add SDClass sd_io2; and sd_io2.sdfs.begin(SdioConfig(FIFO_SDIO | USE_SDIO2))...

Take a look at this ADC library for the Teensy: Teensy 3.0, 3.1, 3.2, LC, 3.5, 3.6, 4, 4.1 ADC implementation library created by Pedro Villanueva This has a lot of configuration options and examples to guide you

One option would be: _pimxrt_spi->TDR = __builtin_bswap16(d); Another: _pimxrt_spi->TDR = (d >> 8) | (d << 8); Not sure which is the most efficient method (or if it compiles to be the same byte code), but could aid your testing and you could measure. From an efficiency point of view, it's...

Confessions are good for the soul! Sorry for your loss :( I don't use the IDE setting (or rather, have it set to 600), just what I set in code. I poll the tempmon each second and have a graph overlay available that stays on top of my UI showing the temp, useful when I was testing more. My UI...

This looks promising? https://github.com/bitbank2/zlib_turbo Larry does great work with JPEG and PNG decoders that work well on the Teensy.....

FWIW - I have been running my Teensy 4.1at 816Mhz for 4-5 years now, for long periods at a time each use. All my Teensys subjected to this are still operational. I have a small (10mm x 10mm x 4mm) cheap, copper heatsink sitting on the processor chip and the Teensy is squished between two PCBs...

@MichaelMeissner Spinal Tap was indeed my inspiration :)

To simplify and put into context - EEPROM.put on the T4 will do the same as .update for you, so use EEPROM.put. If the user constantly saves their settings every hour, 24 hours a day, 7 days a week, it will take them almost 12 years to do 100,000 saves and likely 50-100 years of doing this...

Without code, hard to correctly diagnose but...here's some stuff to think about: Teensy Loader will initialize the RTC clock when you program the Teensy and maintain power. If you power it down and up again, without a battery maintaining the RTC, it will reset to zero. You also will need to...

The driver library and Windows / MacOS client software have been updated to support streaming buffers over USBSerial1. Just need a bare Teensy 4.x and a USB cable!

I realize what you need, I forgot they named the support documentation this way, too. This document helped when I was figuring out some stuff for the NT35510 a few years ago....I'll PM you a link to the NT35510 Application Notes PDF I have, v0.07. I haven't seen this file distributed much online...

Is that a specific file you are looking for? Or are you making up a name to match NXP style documentation, where they present a full working solution, source code included, for the NT35510 in an "Application Note"?

If you have a Teensy with Ethernet and a TFT screen that you update with buffers of 16 bit RGB565 pixel data you should be able to use this code, along with the supplied Mac or Windows client, to also display (and control) the screen remotely on your desktop via the network...

The PlatformIO inspect function does the analysis on a compiled ELF file, compiled in debug mode (to get extra info to generate the report). Obviously, the linker cannot generate the ELF if section sizes are too large for the regions. So, it's not exactly a PlatformIO issue..... Does it build...