shawn
Senior Member

Forgot to add in my previous post (so you don't have to go hunting for the information): PR 672 just affects _serialEvent_default and not the others. I had only added `extern` to that variable. (See also:...

Okay, I'm relieved. Thanks for double-checking. I was concerned because my tests, printing the value from inside `yield()`, showed that it was zero. Maybe it was because I was using GCC 11.3.1-beta2 (from Teensyduino...

Ok, it sounds like `_serialEvent_default` being zero inside `yield()` isn't a problem, then? To confirm, this line of code, as it stands right now, won't execute (without adding `extern` to the `_serialEvent_default`...

The fix in PR 682 doesn't address LTO builds. It addresses an issue that was introduced by PR 672 for _all_ builds, including for non-LTO builds. This is the important detail. Right now, even without building with LTO,...

Please forgive me for being a broken record, and I acknowledge you've likely seen this PR and are likely still deciding what to do, but I think this particular fix is important to restore `yield()` to its behaviour...

@ckahlo (and any others that may know): Would you happen to know how to use the payload key (AES) with the DCP? More information: in the interests of understanding how things work, I like to go through any...

I like differential signals over (maybe shielded) twisted pair, for noise immunity. Any signals could be converted to differential signals, really, but they all require a little extra hardware (transceivers). Something...

I feel I need to add: QNEthernet is very reliable (notwithstanding any undiscovered bugs). My understanding is that it was being called from an interrupt context, and the library is expressly not designed to be used...

If you wanted to give it a shot yourself, the protocol specification is in RFC 2131, “Dynamic Host Configuration Protocol.”

There's two ways: 1. Use a lower-layer stack such as lwIP or FNET and write the server on top of that. There's a few Teensy 4.1 libraries that include an IP stack: QNEthernet (lwIP) and NativeEthernet (FNET). You'll...

There were some interested folks, so I'm online now for a little while.

Yes, you’re correct. Once a connection finishes closing, is aborted, or times out and is closed automatically, the connection is free to be used again. In lwIP lingo, these are called PCB’s. See also:...

To which circular buffer do you refer? Which library or source file? If you run the iperf (v2) app on your computer, and the IPerfServer example on the Teensy, you'll likely see something exceeding 70 or 80Mbps over...

I’ll add this note for future readers: the reason it’s only able to accept 8 connections is because the connections are never closed, and because the library is configured by default for up to 8 connections. If there...

Fun fact: the link status is polled approximately 8 times a second in QNEthernet. I’ve used many Teensy 4.1s with networking programs and haven’t seen issues like this, so I’m fairly certain it’s not likely to be the...

I should have said, "nothing actually processes a connection" because the connections are technically accepted under the covers, it's just that your program does nothing with that information.

...and `errno`. (Forgot about this one.)

I'm hosting another right now if anyone's interested. I'll be on for the next half hour or so, and longer if anyone joins. Meeting link: https://meet.google.com/tsd-eapa-xnb

Actually, the real purpose is so information isn't lost. Interoperating with `ferror()` from stdio is a side benefit.

I'm having some confusion because on one hand, your test program doesn't accept client connections nor reads from any connected clients (because nothing is connected), but on the other, you describe "all connected...

I just released 0.19.0. The changes: ### Added * Added `Ethernet.loop()` calls to the `EthernetClient::write()` functions when the send buffer is full. * Added Ethernet hardware detection to support (well,...

Yep, that's fine. It merely looks at what's in the library's library.properties file, and `lwip-master` is simply based on top of the current `master`, which is also currently at 0.19.0-snapshot. I didn't change that...

There. I just changed `EthernetUDP::send()` to return an `int` and pushed to the GitHub repo (https://github.com/ssilverman/QNEthernet). Could you retry and post which error code (the return value from `send()`) you...

I can confirm that `EthernetUDP::send()` does just about the exact same thing as beginPacket()/write()/endPacket(). The difference being you're using less internal memory with `send()` (there's a `std::vector` allocated...

@sicco First, thanks for engaging. Concurrency is hard to get right and I appreciate the discussion. I'm open to be shown new details or flaws in my thinking I haven't thought of. Here's my view of the system; please...

I tried the `lwip-master` branch myself and I think I know why you're not getting an IP address. Try changing the `kDHCPTimeout` value to 15 or 20 seconds. 10 seconds may not be long enough. It was a little slower with...

@sicco I've looked at this some more and I don't think the lack of synchronization here is a problem. The library is not asynchronous, so a lock isn't needed. All the input processing happens from `Ethernet.loop()`, and...

I just realized there’s a spelling misunderstanding. :) “lwIP” stands for “Lightweight IP”. “LWIP” but with the first two letters in small case. Silly non-serif fonts…

@sicco good point. I’ll have a look at that more closely. Thanks for reviewing the code.

You’re welcome! :) Thanks for testing.

That’s great news! Sure, if you have the time to test the other branch, that would be great. Now that I know that the latest v0.19.0-snapshot works much better, I would love to build confidence that the latest lwIP...

I prepared another branch that uses the latest lwIP. Would you mind also trying the `lwip-master` branch? (In addition to `master`.) I want to see if maybe there've been some lwIP fixes since the 2.1.3 release that help.

Which version are you using? If you haven’t tried the latest from GitHub (0.19.0-snapshot), could you try that? There were a couple bugs I fixed since v0.18.0.

Hi! Welcome to the forum! This thread may help: https://forum.pjrc.com/threads/66076-Teensy-4-x-s-1062-MCU-has-16-bytes-of-NVRAM-on-RTC-unit

I'm glad it helped. Yeah, adding detail like that is always tricky because of the different experience levels of everyone (I try to write here so that there's enough context for newer people — it's also my hope (with a...

Happy to help. The PJRC forum is a very helpful and professional place. I think it's one of the things that makes the products here so amazing: they're well-designed, robust, _and_ there's a very helpful place to go...

(Pro tip: Wrap your code in "CODE" blocks so that it shows up as monospaced and properly formatted. The '#' button on the toolbar also does this for you.) May I suggest having a look at the 'ServerWithListeners'...

The latest QNEthernet push further reduces RAM1 usage by about 27KiB with the current configuration by moving lwIP's memory pools to RAM2, along with some other hundreds-of-bytes changes.

The latest QNEthernet push further reduces RAM1 usage by about 27KiB with the current configuration by moving lwIP's memory pools to RAM2, along with some other hundreds-of-bytes changes.

Thanks, Ward! That UDP receive queueing was added precisely because I needed it for receiving sACN reliably without skipping packets.

What I’m gathering from you is there’s no crash or hang. I’m not certain where your program is stopping. What does the current code look like, and where exactly is it apparently freezing? For example, if the program...

Some questions: Where exactly does it freeze? If it’s actually crashing, does the Teensy restart? What does printing the CrashReport show at program start?

Entirely possible. I’ll look more closely when I have a chance. Let me just clarify something: does it actually hang or is it just really slow?

I’m curious, is it possible that groups of packets come in immediately, one after the other? This is what I was seeing with pixel data (eg. sACN). It’s why I added a “queue size” parameter to another...

Have a look at QNEthernet. Keep in mind some extra conveniences with the library, for example, you don’t need to specify a MAC address.

See also this thread on how to add Teensyduino 1.58-beta3 to PlatformIO: https://forum.pjrc.com/threads/71730 Also this post for EHEX support:...

I added support (well, "non-support") for the Teensy 4.1 NE in the latest QNEthernet push. (See https://github.com/ssilverman/QNEthernet.)

Do you mean this link instead? Teensy 4.1 EEPROM Endurance

Have you tried grepping through all your code and libraries for the string “out_data”?

Do you have a link to the source code?

I'm hosting another today (right now, in fact) for the next hour or two. Same meeting link.

Does `if (!Serial)` work?

The chip the Teensy 4 uses includes 4 bullt-in quadrature decoders (i.MX RT1062). See the chip docs (https://www.pjrc.com/teensy/IMXRT1060RM_rev3.pdf) or this library:...

There's no recording. I'm going to hold another one from now until about 4pm (UTC-8) today (22-Feb-2023), or whenever I have to stop. Same meeting link. Update: I plan to be on here for another hour or so (until...

I'm holding another one now for about an hour (8pm UTC-8). I'm experimenting with the timing. Same meeting link.

It sounds like you need to configure your browser to use a proxy. In that case, I think you’d also need to write an HTTP proxy server for the Teensy.

You could just read from one stream and write to the other. For really high data rates, you could also optionally add some flow control on the serial side. I don’t think you really need to dive into PPP. Is your PC...

Are you trying to simply relay a TCP steam over serial?

I first looked at the existence of embedded JS when I learned that the PixelBlaze product can program LED patters in JS. I think the designer of that product wrote his own interpreter, but I think there’s systems that...

I'm not certain IPerfServer works with iperf3. See if you can get v2 working instead. To glean the protocol, I had to read a bunch of mystery code from different places. At the time I wrote that example, I couldn't find...

The IPerfServer example is designed to work with the `iperf` command. (I use a Mac, and used `brew` to install it. I currently have v2.1.8.) It's designed for a specific protocol; that's why you're seeing those strange...

I just released v0.18.0. The changes: ### Added * Added a "Notes on ordering and timing" section to the README. * Added a README section that discusses `EthernetClient::connect()` and its return values. *...

I think the C terminology you’re looking for is declarations and definitions. The declarations are often in a header file, and definitions are often in the C or C++ files.

Here’s another approach: use Teensy 4.1’s wired Ethernet (may I suggest the QNEthernet library) and then plug that into a little wireless bridge configured for your network. You’ll need to get and assemble an Ethernet...

You probably already saw this, but here’s a link directly to my last PR comment (I don’t want it to get lost in the shuffle since it fixes my original LTO “fix”), to make your life easier:...