Merging and testing MTP and LittleFS pull requests is at the top of my priority list for after the T4 bootloader chip “soft” release. Sorry I can’t do it now... really want to. But so many people...
Type: Posts; User: PaulStoffregen
Merging and testing MTP and LittleFS pull requests is at the top of my priority list for after the T4 bootloader chip “soft” release. Sorry I can’t do it now... really want to. But so many people...
Yup, that's been the plan all along. :)
Yes, very likely.
Look for problems near pin 8. If stray solder got onto the pins of that little chip near pin 8, it would cause this sort of problem.
And just to be clear, this problem almost...
I do have a plan (kinda 2 plans), but so far haven't written anything....
1: For the wav file player and other file-based audio library stuff, I'm planning to add a useFilesystem(FS &filesys)...
It's not going to do anything so complex. And even if it did, the nature of most failures is that you can't attempt the next stage anyway. If communication with the IMXRT fails, there's no way to...
Google search for "DDI0403E". If Google doesn't find the PDF, click the link to ARM's website, then click "Download" to get the PDF.
Once you're viewing the PDF, turn to page B3-602 for the AIRCR...
Microsoft did fix some bugs in usbser.sys between Windows 8 to Windows 10, but apparently not this one.
It's supposed to "just work" if you change to that folder and just run "make" with all the files still located in the places the installer wrote them.
I can understand why you probably want to...
Which Linux distro is this? It's been a while since I've heard of one so terrible. (eg, Gentoo...)
EDIT: oh, I see it's Arch, missed that earlier.
Reality is PJRC only tests the x86 build on...
RTS should work on any digital pin (as the web page documents). Only CTS is scarce.
My gut feeling is the guesswork on msg #28 is probably right. Microsoft probably only supported use of the modern WIN32 APIs in their USBSER.SYS driver. FTDI's driver probably has support for older...
The serial page lists the pins supported by Teensyduino 1.53.
Kurt added support for the XBAR pins, and other nice features like addMemoryForRead(), but that stuff hasn't yet made any non-beta...
No, for USB serial it's just the USBSER.SYS driver built into Windows.
On Windows 10, it loads automatically. On Windows 2000, XP, 7 & 8, Windows doesn't load USBSER.SYS automatically. So a...
Ok, here's the video demo. Sorry about the mediocre quality... not easy to shoot 2 screens and get exposure perfect (and I really need to get back to the bootloader chips... not time to do a more...
Yup, it sure looks that way.
The problem is on the PC side. Nothing you can do on Teensy will help. The combination of Termite & the Windows driver simply isn't sending the control...
Here's a (maybe) similar report, where RTS didn't work.
https://forum.pjrc.com/threads/59612-DTR-Off-blocks-USB-serial-receive?p=230233&viewfull=1#post230233
It turned out Coolterm works. The...
Just a quick update. I am hoping to begin a "soft release" of the T4 bootloader chips next week, and a full release later in February.
A "soft release" means we are going to limit the per-person...
Teensy Loader uses only HID protocol. It never tries to access any serial ports.
In the Arduino IDE, Teensy should appear twice in the Tools > Ports menu. If you select the "Teensy ports" entry,...
When no Teensy is connected in HID bootloader mode, it already does exactly that, but with this message.
23285
And the teensy_reboot utility which Arduino uses to try to ask Teensy to go into...
Not really. But it can detect a lack of USB communication. I had originally planned for the red LED to blink slowly if the PC doesn't complete USB enumeration. It did in the early betas, but...
Does anything appear in the Verbose Info window when the red LED (near the USB connector) turns on? The 2 screenshots in msg #8 and #9 have none of the info indicating any USB communication...
Try Help > Verbose Info. You can copy & paste that info, or use the Log menu to save it to a file. Maybe showing that info will help us figure out what's going wrong.
Teensy Loader might also be configured for one of the smaller boards. Just press the button on Teensy to go into bootloader mode, so Teensy Loader can detect you have Teensy 4.1. Then open the HEX...
Any chance for a photo of it working? Always fun to see lots of LEDs lit up! :D
Teensy 3.x only supports 12 Mbit USB device. Teensy 4.x supports 480 Mbit, but can also run at 12 Mbit, but that is very rare in these modern times. It's been about 20 years since PCs and USB hubs...
Very difficult to say what's really going wrong here. But with a quick look at the Teensy code, this looks like trouble:
void loop() {
// Buffer next command
int count = 0;
...
Yeah, it still *feels* like 2020, which would put msg #32 six days into the future.
Only plausible if not using send_now().
Everything on the Teensy side software should happen in just a few microseconds. When you call send_now(), Teensy definitely isn't "holding on" to...
Looked very briefly at that library. Looks like the hardware SPI is hard-coded to only the main SPI port.
For example, "SPI.begin()" at line 90:
...
I'm not familiar with that library. Is it this one? (from a quick search)
https://github.com/MajicDesigns/MD_MAX72XX
ps: forum messages are editable for only 2 hours, mostly as an anti-spam...
Nope, no idea why. I tried to glance at your schematic, but the max image size the forum allows is too small. Maybe try attaching a PDF to your message? Click "Go Advanced" if you're in the "Quick...
The RTC hardware doesn't do that sort of thing automatically. You need to use code to implement it.
I tried running your test program on a very old Teensy 3.6 prototype with the LQFP chip. The DAC definitely works.
23238
Just to take a step back and look at the "big picture" here, all of the problems you're likely to face are from the hardware running much too fast, rather than not fast enough. I know this may seem...
Probably a mistake or misunderstanding in the wiring. We can probably help more if you show photos of how you really connected it. The best anyone can say is this hardware is definitely known to...
The Ethernet Pins & Socket are now live on the website! :)
https://www.pjrc.com/store/header_socket_3x2.html
23223
I have some good news. Quite some time ago, PJRC ordered a large batch custom length header pins for exactly this use. They finally arrived late last week. I've been reluctant to mention it until...
No. This is the first I've heard from Chrome supporting serial without some sort of 3rd party extension.
Does it work on Linux? My main desktop system is Ubuntu 18.04.
How do I use it? Is...
It's a shame 10/100 Magjack pinouts never followed any sort of standard. So many different & incompatible pinouts for exactly the same circuitry!
FWIW, I just tested editing serial2.c in Arduino 1.8.13 with Teensyduino 1.54-beta5. I changed SERIAL2_TX_BUFFER_SIZE to 512. Indeed Serial2.availableForWrite() returns 511.
I can't explain why...
The latest core library code, which is currently only on github, supports addMemoryForWrite() on Teensy 3.x, thanks to Kurt!
With this feature you no longer need to edit the core library. You can...
Maybe initialize your pointer, so it can't be NULL at startup. So change this:
Q *Qchip;
Q DOC_output; // Queue for DOC
to something like this:
I'd recommend using PWMServo, and of course use only the PWM capable pins.
To use 125 Hz, you'll probably need 2 edits. First, the easy one. Find this line:
...
Hmmm, 16ms... let me guess, Microsoft Windows?
As a quick test, try running a game or playing a video in another window while doing your latency test. Does that shave 15ms off?
Maybe try the command line Teensy Loader?
https://github.com/PaulStoffregen/teensy_loader_cli
It has similar HID code. If that works, maybe you could use its HID code as a guide to get that...
If that was one of the purple prototypes - yeah, it was weak because I hand soldered it without any way to solder the underneath pads (I don't use a reflow oven)
Yes. Use the InternalTemperature library to check the actual temperature inside the chip after your program has been running for quite some time. Do this measurement with your project as it will be...
The short answer is yes, for all practical purposes they're the same. All should work fine.
2 minor caveats:
Some very early (like ~9 years ago) WS2811 used half speed 400 kHz bit rate. ...
Yes, indeed, the moral of this story is you need to do something (or simply avoid doing certain things) to keep the internal temperature below 95°C if you want the chip to last more than 3 years.
The double buffering design, in hindsight, was a mistake on my part. Eventually it should get removed from all the output objects.
In the earliest days of the audio library, back in late 2013, I...