Search results

I remember we had a thread for reporting errors/missing infos/etc. about pjrc.com web pages, but I can't find it anymore. So I'm creating a new one, hoping it may help Paul updating the web site. What I've found, in no particular order: https://www.pjrc.com/teensy/td_libs_Audio.html Only...

Thank you Paul. I was suspecting something like that. Maybe the USB device descriptor/capabilities/infos etc. could give some hint too, I'll look into that.

Hello, I have already built a few MIDI devices based upon the Teensy 3.6, thanks to its USB host port. Usually I connect a (single) MIDI controller to the host port and then process the MIDI messages it sends. Now I would like to build a device where one can plug more MIDI USB devices to the...

Don't want to further messing up my message, anyway I think I found a way. When I stumble upon a usbMIDI send function which also needs "type" along with "value", I just define a proper const inside the handler, like: void timeCodeQuarterFrameHandler(const uint8_t data) { const byte type =...

Thanks for the explanation Paul, it makes sense of course. Now: do you have a suggestion to handle my case? Could I simply write the affected handlers as 2-args functions and be done? Like, for example void timeCodeQuarterFrameHandler(byte type, byte value) {...

Hello, I'm implementing a test MIDI device with T3.6. At the moment it just forwards incoming MIDI messages to both a serial MIDI output (DIN) and usb-MIDI. So, I wrote my handlers for various type of incoming MIDI messages. For example: void timeCodeQuarterFrameHandler(const byte data) {...

So sorry to see T3.2 go, it has been, and still is, great. But i fully understand it has to go.

Possibly you would need to edit usb_desc.h too (there are various sections). It is where VID and PID are defined. Its location depends on the Teensy and OS you are using; for Teensy 3.x under Windows, it's <Arduino_folder>\hardware\teensy\avr\cores\teensy3\usb_desc.h

I use PCBWay too. Quite satisfied.

Hi and welcome. Well, spaghetti jumpers directly connected to the Teensy board? Sounds a bit extreme. I would suggest using at least a protoboard, so you can test everything with a breadboard and then replicate 1:1 in a more robust/reliable way, with mounting holes as well...

Thank you very much Vindar!

OLEDs wear out, quite fast if you keep them at high intensity and with semi-fixed content.

Hello Vindar, I'm using your nice ILI9341_T4 library on T4.1 with a 2.8" ILI9341 + XPT2046 touch. I'm now looking for a simple 2D canvas lib (I need a few buttons and a couple of textboxes for my simple GUI) and have found your TGX library. Unfortunately, I did not find any example which...

No issue, provided the two "3.3v" levels are within Teensy tolerance (i.e.: A=3.2V and B=3.4V are OK). The (digital) GNDs have to be common.

@vindar: I cannot thank you enough!! Following your instructions, I managed to have the "lvgl_music_demo" up&running on my T4.1. :D I got 145fps at about 84% CPU load with refresh=5 and SPI at 80 MHz. And CPU clock speed was only 528 MHz. Now, I am trying to figure how to start a new project...

A few OSes have already been ported to the Teensy 4.1. They are realtime OSes, not your typical shell-based or window-based OS, but still. Just to name a few (please note I *did not* try any of them): Zephyr https://docs.zephyrproject.org/latest/introduction/index.html FreeRTOS...

Update: I purchased a new 2.8" display (the non-working one was 2.4") and this one works perfectly, touch included. So I have a faulty 2.4" display, or maybe one that, despite being advertised as having a XPT_2046 touch driver, is equipped with a different chip instead (can't read the writings).

All my RPIs (from 0 to 4B) work without issues at 115200 via UART (pins 8 and 10 + GND). So I would say it's not strictly a RPI_UART-related problem.

I may have a faulty touchscreen then. :(

I moved the touch_cs pin to 5 and changed the code, as per your suggestion, to: #include <ILI9341_t3.h> #include <font_Arial.h> // from ILI9341_t3 #include <XPT2046_Touchscreen.h> #include <SPI.h> #define CS_PIN 5 #define TFT_DC 9 #define TFT_CS 10 #define TIRQ_PIN 2 // MOSI=11, MISO=12...

I am not using the Audio Board. Just Teensy 4.1 + display.

I have the same issue. My setup is described here https://forum.pjrc.com/threads/71367-T4-1-ILI9431_t3-(2-4-quot-display)-inverted-colors , it's the same as in PJRC page: https://www.pjrc.com/store/display_ili9341_touch.html I am testing with Teensy 4.1 (Arduino IDE 1.8.19 + TD 1.57) using...

SOLVED: Had to add tft.invertDisplay(false); which is so very strange! I mean: if I do not add the instruction at all, I get inverted colors. If I add the instruction with "true" as argument, I get inverted colors. If I add the instruction with "false" as argument, which to me it would mean...

I feel your pain! Used LVGL for a RaspberryPi project, with framebuffer touchscreen (no X)... even just have everything properly configured has been a pain. Then there's the question of the continuous updating without backwards compatibility: I started on 5.x and painfully worked my way up to...

Anyway, clock speed does not tell the whole story: 4.x are faster than 3.x even at the same clock speed (arch improvements). So you may actually "downclock 4x more" and get the same speed when running real world code, vs. 3.x.

Something like this maybe?

By the way: does it work with Teensy 4.1 as well? Maybe a silly question, but... just to be sure. :)

Thank you, that's great!

Hello, was wondering, what is the current status of USBHost_t36 vs. reading mass storage devices? In particular, I would like to read a "raw" SD card inserted into a USB card reader (which I would connect to the USB Host port of the T3.6). "Raw" as in "no filesystem": would read it the raw...

Happy birthday Paul!!

Impressive work, Rolf!!

Lots of nice suggestions, thank you!

Sorry, I was not clear. I was not searching another algorithm to read encoders, I've tried them all. I was looking for hint to port Luni's library specifically, from Teensy-only to other boards.

Yes, it's for the (only) USB Host port of the Teensy 3.6. Sure, it's the standard USB Host T3.6 library which comes with Teensyduino: https://github.com/PaulStoffregen/USBHost_t36

By the way. I'm using the great EncoderTool library by luni: https://github.com/luni64/EncoderTool It's absolutely, by far, the best I've ever tried. Much better than Paul's library, which is something. Problem is, it only works on Teensies. They are great, but I would love to use it with...

It depends on what you're driving. For CEM 3394, for example, you just need 100nF caps.

GTK2 dev package is still available on Ubuntu 20 (libgtk2.0-dev). Not sure if it helps.

Interesting library, thanks!

If you declare a global variable like USBHost gUSBHostPort; // g prefix for "global" USBHub gUSBHostHub(gUSBHostPort); MIDIDevice gInputMIDIUSBDevice(gUSBHostPort); then in main loop you can simply do gUSBHostPort.Task(); if (gInputMIDIUSBDevice) // Input device could have been...

Large soundfonts/samples are not exactly easy to manage with a microcontroller, even as powerful as the Teensy. The 4.1 has a very fast integrate microSD slot and quite some RAM for buffering; moreover, it can mount additional memory by soldering small chips (flash and/or PSRAM). And it's very...

Thank you Michael! A bit expensive in EU (Eur 85 + shipping), will ask about overseas shipping (worried about shipping time and customs).

Yes, sorry, I have the bad habit of using the term in a generic way, for both multiplexing and demultiplexing. If you demultiplex each DAC to say 16 channels (example: CD74HC4067, quite cheap), with a single T3.5/3.6 you could have 32 x 12-bit output analog signals. If your goal is controlling...

Depending on the needed accuracy and speed... what about T3.5/3.6 integrated DACs? T3.5s and 3.6s have two onboard 12-bit, independent DACs (pins A21 and A22). You could multiplex them (cheap analog multiplexer) and add appropriate hold capacitors.

Hi, until now, I used the well known small OLED and TFT displays, up to 2.8", without issues. Now I need something much larger: say 4.3" as very minimum, 7" if possible. Resolution is not critical; 320x240 or 480xsomething would suffice. Touchscreen (capacitive) would be great, but not a deal...

I use VisualStudio 2017 + VisualMicro for most of my work (minus TI and Microchip stuff). I like it a lot! I fire up the Arduino IDE only for very simple stuff and trying example sketches on the fly.

I've read those data and they are not really telling much, apart from the very high sleep power consumption (1400 uA @ 5V). Well I guess someone will post real world figures in a few weeks.

Does anybody has clear figures of actual power consumption, for the Pico? I know, I seem to be the only one around here who cares a lot about power consumption ;) , but for me that's very important indeed. For my little battery powered devices, more often than not an M0 "running" at 1 MHz is...

Pin number 13 is already "tied" to the onboard LED of Teensy 3.2. So it will always engage the onboard LED. That said, you can still add another (external) LED to pin 13. LEDs need series resistors to limit the current flowing through them. The value of the required R depends on the LED...

Sure! Read here: https://www.pjrc.com/teensy/td_libs_Bounce.html let us know if you need more support.

Just a quick note: your "delay(3)" works for 115200 data speed; but it's not going to work for different speeds. With my HC-05 (v2 and I only use it as slave, so cannot help with INQ) I have to use 3ms for 115200, 2ms for 230400, 1ms for 460800 and no delay for 921600 (won't work at all at...