shawn
Senior Member

Yes, I agree that it is indeed a good idea detach the interrupt on the RX watch pin when it's triggered, so it's not triggered on all the other data transitions. Side question: You said: "Rx as a watch pin". Do you...

Thank you all for the suggestions. I will report back if I know more. Hopefully this crashes again in a timely fashion. My plan is to try one thing at a time until crash or "timeout" of a few days. This could be a...

I will try this too. I'm likely to copy files over my PlatformIO install too. Let's see if this approach with PlatformIO is viable... I haven't switched to Catalina yet because of the 64-bit-only support. I still use...

I should add: I'm seeing this with Teensy 3's too, as of late. 3.2 and 3.5, so that probably narrows it down to my machine and nothing anything the Teensy is doing.

@blackketter this is a good question. You mean like cycling the power to the board or something and then loading up a serial monitor of some sort?

Yep, this is a hard one because it's very difficult to reproduce. I'll take your suggestions and do the best I can to figure out what the HEX file was, which step in the procedure was happening, etc., and then re-try...

Thank you both for attempting to help me. @defragster - I'm running tests using a development version of my TeensyDMX program, but I have seen some panics a couple of times when testing something simple (10's of...

It turns out that a lot of decent timing information can be gleaned with just the UART signals. (Verified with a scope and comparing with ostensibly-measured values.) I was avoiding using a separate pin (I'll call it a...

I've been poking around the kernel panic logs, and the log says it crashes in a `teensy_serialmon` thread. In fact, every single one of the kernel panics that have happened recently says that it's in a thread from this...

I don't have nearly the experience of Paul or KurtE, but I will say that it would be my best educated guess that GET_LINE_CODING is not called for every byte. That is, unless the USB driver on your host machine is doing...

What this is for: Measuring where packets of data start and end for my TeensyDMX library (see the latest `teensy4` branch for all the latest stuff). I'm trying to do accurate measurements for both informational purposes...

Ok, I got smarter about this and instead of special-casing `avail==1`, I'm comparing a positive value for `avail` with the watermark size. If it's smaller, then one character time is subtracted. Below is updated code,...

In reply to @blackketter: I've tried different cables and both with and without a powered USB hub (Amazon Basics 7-port USB 3.0 hub); all configurations so far have seen crashes. I'll be trying the other things you...

I'm going to continue playing and see if I can't narrow down when this happens. I'm willing to accept this may be specific to my setup. I'm also willing to bet this doesn't happen on newer computers. Heck, maybe I have...

For posterity, I’ll post the reason why R8 is zero on a Teensy LC. It’s because there’s a 2-stop-but mode and the check is not necessary, as for Teensy 3.2 and below. Same for Teensy 3.5 and 3.6. The latest fixes for...

The reason that Teensy LC was returning zero for R8 was because it has a 2-stop-bit mode and it’s unnecessary to check that bit. Same goes for Teensy 3.5 and 3.6. This has been fixed in v3.2.2. The v4.0.0-alpha.1 has...

I just fixed the DMX receive problems in the TeensyDMX v3.2.0 release. There's a new v3.2.1 release that I've tested on a Teensy LC. Note that the Arduino Library Manager or PlatformIO might not detect the new release...

I just released v3.2.1 that fixes the receive problems in v3.2.0. It's in a branch named `fix-dmx-receive-in-v3.2.0` and not `master`. I'm not sure if the Arduino Library Manager or PlatformIO will find it; if not, you...

I think I found the problem. See the new v4.0.0-alpha.1 release for a fix. I'm using bit 9 (the R8 bit of UARTx_C3) to validate that the first stop bit is high, and if it's low, I accumulate one framing error. On the...

A few notes on your code: To confirm, you're making every 4 pixels the same? Move the `strip.Color` call outside the inner loop because it doesn't depend on `p`. Call `readPacket` just once. For the first check, do...

I've released a new version, v4.0.0-alpha. Let me know if this fixes the problem.

Thank you for helping narrow that down. If v3.2.0 is the culprit then clearly I’ve introduced a problem. I’ll dive in.

Curious, does release v3.1.1 work for you?

I’m curious, what is pin 2 connected to? What does setting it to HIGH do?

Hi, Gard! I’m going to have a look at and re-test Teensy LC support for TeensyDMX. Could you tell me more about your system? For example: How many channels are in each DMX frame? What is the transmission rate?...