shawn

Looks like you’ll need to update that Art-Net library. On Teensy 4.1, it looks like it’s always using NativeEthernet, which might not work well with the latest Teensyduino core. You can also remove the Ethernet includes from your main program...

Tip: you can make your code much more readable by putting them in a code block. See the “</>” button. Personally, I don’t often dive into long code snippets if they’re not formatted in an easy-to-read way.

Note that, other than the PHY initialization code, that Teensy41_AsyncTCP library doesn’t use QNEthernet. It only uses the included underlying lwIP stack.

Thanks all, I moved the T4.1 to the nearest slot on the board and I think it helped, thanks. Will finish the editing of the imxrt.h file and do PR of it... Also just installed a Protocol analyzer for SDIO to the Saleae setup...

I personally use a program called “Serial” from https://decisivetactics.com.

Sorry - not sure what happened but heres the link: https://forum.arduino.cc/t/new-release-of-library-for-obtaining-true-random-numbers/229511/2

Whats the link that’s supposed to be under the word “this”? It shows...

I wrote some raw TRNG (true random number generator) functions in the QNEthernet library. (They’re similar to what’s in the Entropy library.) Feel like giving those a try? You can see how they’re used in the library and in the unit tests. I’m not...

I think it’s perfectly reasonable to ask these questions here.

Thanks to @BriComp for the title which says it all :)

See this thread: https://forum.pjrc.com/index.php?threads/add-ethernet-to-a-micromod-format-teensy.67643/post-347244

The NTPClient library looks like it takes a UDP object. The WiFi in the example is just an example. You can pass an EthernetUDP object too. See: https://github.com/arduino-libraries/NTPClient/blob/master/NTPClient.h

The AppWithListenersTemplate and ServerWithListeners examples are TCP servers. Have a look at the SNTPClient example.

It looks like RAM1 increased when you lowered those values? I’m skeptical.

I see you have line 519. That’s supposed to be 549. Also, did you try lowering those PCB values? I’m interested in helping reduce the size.

So we’re still at about 43k bigger in RAM1… Some thoughts and questions: * Which version of QNEthernet are you using? * How do they compare when compiling with the “smallest size” option? * In lwipopts.h, what happens when you reduce...

I’m curious, in the interests of reducing size, what is too big? For example, how much bigger is your compiled code size (including FLASH and RAM1 usage) when comparing both builds? I’ve seen people accidentally include both libraries when switching.

Do you feel like giving the QNEthernet library a try? It should be just about a drop-in replacement. You can selectively disable all the features.

Solved the problem.

I can help. But first, which version of Teensyduino are you using? May I suggest updating to 1.59? That should fix the problem.

That code (line 225) is correct. Which version of the Arduino IDE are you using, and which version of Teensyduino? Older versions of Teensyduino don’t yet have support for casting a const IPAddress to a uint32_t. I removed the custom code that...

I’ll have a look at my code…

Show me the code? I know this works: uint32_t x = static_cast<uint32_t>(addr); Update: I re-read your post and I think you mean this? uint32_t x = 0; IPAddress y{x}; // Parentheses should also work IPAddress has a uint32_t constructor...

I released v0.30.1 about two weeks ago. Here's the Changelog: ## [0.30.1] ### Fixed * Fixed wait-for-close for non-altcp connections. Link: https://github.com/ssilverman/QNEthernet/releases/tag/v0.30.1

Let's put newlib rebuild off until at least 1.61. After we wrap up the Black Friday Sale tomorrow, I'm going to go on a sprint to get MTP merged, and then a series of beta releases leading up to 1.60 release with MTP. Might merge some other...

I figured out how to rebuild newlib and libstdc++ (and nano versions), and am working on a small write-up. @Paul, do you think you’d like to test this for 1.60 or wait for 1.61? If the latter, I won't prioritize the write-up, and we can take more...

Here is the link @devtanc is referring to: Post in thread 'T4.1 External USB C Connector' https://forum.pjrc.com/index.php?threads/t4-1-external-usb-c-connector.65633/post-352506

I know this is a few years old, but in case anyone wants to do something like this going forward, I have something that may help. As I tried to do this while prototyping I ran into a few times where efforts to swap from one prototype board to...

MAADS (MIDI Auatomated Acoustic Drumming System) is a controller and set of actuators that use MIDI to play real drums. This hobby project was developed using the Teensy LC and later controllers implemented the teensy bootloader with the ARM...

Hi there, Here is my latest project that I wanted to share : the minichord! For the full documentation of this fully open source project, first the Github (https://github.com/BenjaminPoilve/minichord/tree/main), then the website...

QNEthernet has support for Mbed TLS 2.x. There’s an MbedTLSDemo example. However, the use is a little complex, so I’m thinking about how to incorporate v3.x and how to simplify its use. No promises on any sort of timeline.

I just released v0.30.0. Here's the Changelog: ## [0.30.0] ### Added * Added a _SimpleHTTPClient_ example. * Added a way to get the driver capabilities: `EthernetClass::driverCapabilities()` and `driver_get_capabilities(dc)`. * Added a way...

I wonder if it’s because the function calls need to go through virtual lookup each time, for Serial*?

If you also find potential improvements for QNEthernet, by all means, let me know.

Note three: you must check return values from write() calls (and from all networking calls, for that matter). The writeFully() call hides the fact that not all bytes necessarily get written when write() is called.

One other note is that TCP data does not get sent immediately unless you call flush() on the connection. If you don’t call flush(), the data is buffered until either there’s enough to send or a timeout of about 250ms occurs.

The QNEthernet library can be used in a non-blocking way. Libraries or code that use it need to be written in a way that uses this. Is it possible the SimpleFTPServer library just isn’t written in a non-blocking style? Note: writeFully() isn’t a...

May I suggest formatting the code? It’s much easier to read when it’s formatted where everything doesn’t start at the start of the line.

Or this: constexpr uint8_t ROWS = 7; This is very similar to a compile-time literal, and is preferred for true constants.

Thinking about this some more, I suspect that calling that poll() function is not necessary with QNEthernet. Just delete or comment it out and see what happens.

A guy I follow on IG just released this PIO extension to view ELF files, Might be useful

A tip: with QNEthernet, you can access a UDP packet’s data and size directly from the object. You don’t need to read into an external array. Use udp.data() and udp.size() to access these. A note: VLAs (Variable Length Arrays), where you create...

There is a TLS example (note that I’m using “TLS” instead of “SSL” here because SSL is obsolete) that works for both clients and servers, but I admit getting it up and running for either a client or server is a little complex. See the MbedTLSDemo...

QNEthernet supports TLS via lwIP’s “altcp” scheme. There’s instructions in the Readme on how to wire this up. It’s a little complex at the moment, but there’s an Mbed TLS example, MbedTLSDemo. See...

You have to release the button before about 17 seconds, but after the lights flash a couple times after 13 seconds or so. Is it possible you held the button too long when trying the restore process? After this, you have to wait until the flash...

It’s not a problem to use the std namespace. It’s a problem when there’s using namespace std; somewhere that also uses byte.

Try using uint8_t instead of byte. It looks like the Arduino header-defined version is conflicting with std::byte.

Another thought: are you putting using namespace std; in your code? (I recommend against doing this.) If so, that might be another reason why byte is conflicting. One is defined by Arduino and another is std::byte.

I see where I messed up, I mistakenly thought the Teensy MicroMod featured a W25Q128JV flash chip in addition to the 8Mb flash chip that's usually included on Teensy 4.1. Thanks!

Is there a #include <Arduino.h> at the top?