Search results

I just released v0.32.0. Here's the changelog: ## [0.32.0] ### Added * Added `qnethernet_hal_micros()`. * Added secure TCP initial sequence numbers (ISNs), enabled with the new `QNETHERNET_ENABLE_SECURE_TCP_ISN` macro. The default is enabled. ### Changed * Changed some functions to take a...

Are you referring to the six-part sequence of longer and shorter lines next to the micro USB connector? If so, I was wondering what they’re for?

I heard that they have all the parts on-hand but they’re still ramping up production. They told me about 10 days ago that it’d possibly be another 4-6 weeks.

Yes. See https://github.com/ssilverman/QNEthernet/blob/master/README.md#ip-header-values-1.

You’d need to change that core file if you want the built-in pin access functions to work correctly. Or, if you didn’t want to modify the core at all, you could just copy the functionality from the pin functions you need into your own functions. That’s the kind of approach I usually take to...

I believe you don’t need to change startup.c; just write the registers yourself, say, in setup(). Then there’s no reliance on a modified SDK.

Which headers are you including? I’m asking because your capitalization of “Native Ethernet” suggests to me that you’re also trying to use the NativeEthernet library, and your mention of the Ethernet library suggests you’re trying to use that as well. But I wanted to clarify.

Is this a Teensy 4 or 3 or…? I tested the QNEthernet library to work with the W5500 chip, if you’d like to give that a try instead of the “Ethernet” library. You’ll need to change the driver in qnethernet_opts.h by uncommenting the QNETHERNET_DRIVER_W5500 line.

I pushed a new QNEthernet branch, "teensymm", that contains a driver for the hardware Paul mentioned in this thread. I consider it still experimental until the hardware design is more decided-upon. It should just work out of the box with all the examples and any existing networking code, for...

Couple of points: 1. You don’t need the code that uses the kTXPin; you can remove or comment it out. That’s meant for enabling the transmitter if the hardware needs that. It looks like there’s no “enable transmitter” pin on the Grove device; it’s already enabled because the DE line is tied to...

One of my current projects does logging over Serial, but if you connect via TCP to a specific port, it redirects stdout to the TCP connection until disconnect, at which point stdout goes back to Serial. Just some thoughts. I also use web pages for command and control. Makes life easy on the...

What about sending some logging data over Ethernet? I’m responding to the fact that you don’t want your laptop nearby. The same restrictions apply about sending data over a transport during an ISR. (I.e. don’t — buffer it somehow and send it in a non-ISR function.)

Thanks, Ken; I just ordered some. I'm still interested in learning how to obtain more of these, or if they were made custom for PJRC. (@PaulStoffregen)

@PaulStoffregen do you know of a place online where I can buy those double-insulator pins? Or were those custom made for you or something?

I like the double insulator pins too. I hope they become available again.

I updated the Mbed TLS install section of the Readme (tlsclient QNEthernet branch). You need branch v3.6.3 of mbedtls. There's no config.h; it's mbedtls_config.h.

Hmm. Let me come up with a set of instructions as if I was doing this from scratch. Perhaps there’s a step I don’t realize is missing. It won’t be right away, however. Next time I’m near my computational instruments. I might be incorrect, but “config.h” doesn’t sound like the right file.

Did you copy the config from the MbedTLS example into your MbedTLS install?

To use MbedTLSClient, you need to use the tlsclient branch of the QNEthernet library. Is this the version you’re using?

The Teensy’s MCU has four built-in quadrature encoders/decoders that may be useful to you. That could take some interrupt load off.

I believe all custom Teensys are lockable-capable.

I’m curious how this does step debugging. Does it use that software debugging library by @ftrias? Update: I noticed the “breakpoints” link and discovered more information via that location.

I’m glad you got it working! :) I don’t love much of the Arduino-style coding (eg. badly-initialized global objects, and global variables in general) and Arduino-provided functionality. I personally do my best to avoid it if I can, and only use what I really have to. With the QNEthernet...

What happens if you use read(buf, size) instead of readBytes() — and also managing when to repeat the read() call if it reads less than expected (or timeout)? Also, what happens when you check the value returned from readBytes()? That would indicate whether there was a timeout. In my...

You could also use the EthernetFrame interface if you just want to work with raw frames. No need to dive into the driver code for this.

Did you change to use -std=c++20 or -std=gnu++20? If the former, try the latter. I’m able to compile Teensy projects just fine as C++20 projects.

To add more details, in the QNEthernet library, there are 5 frame buffers for RX and TX, and each buffer is 1536 bytes. I haven’t done any tuning for that number (5).

My first guess is that they’re probably using different libraries.

Where are you seeing size_t being equivalent to a uint16_t?

I’d like to see your platformio.ini file. Size_t does not resolve to uint16_t with PIO’s Teensyduino.

I’ve got a build of the QNEthernet library that works with IPv6, but I haven’t released it publicly; I consider the API still experimental. But, in short, yes, it’s possible.

This is my favourite approach (parts 1 & 2): https://hackaday.com/2015/12/09/embed-with-elliot-debounce-your-noisy-buttons-part-i/ https://hackaday.com/2015/12/10/embed-with-elliot-debounce-your-noisy-buttons-part-ii/

I implemented a layer over MbedTLS, but I haven’t completed things like unit tests or additions to the Readme or how-to instructions for install and use. If you’re interested in the code, it’s here in this branch: https://github.com/ssilverman/QNEthernet/tree/tlsclient Basically, install...

I’m really curious if you had more luck with the QNEthernet library? Here’s a link to the code and a Readme (but it’s also downloadable from inside the Arduino IDE; it’s just not obvious where to find the docs): https://github.com/ssilverman/QNEthernet

(Forum side tip to make code blocks easier: you can use the “</>” button to put all your code in one block.)

The Ethernet version is practically identical, just with the PHY populated.

I just released v0.31.0. Here's the changelog: ## [0.31.0] ### Added * Added `qnethernet_hal_fill_entropy(buf, size)` for filling a buffer with random values. * Added `EthernetClient::setConnectionTimeoutEnabled(flag)` to enable or disable blocking with calls to `connect(...)` and...

They won’t work unless you also modify platform.txt per the instructions in that link.

See this: https://github.com/ssilverman/QNEthernet/blob/master/README.md#configuring-macros-using-the-arduino-ide

One last-ish note: One of the pages has three buttons that point to three links. One points to the flex version, the client points to allrigs, and the server also points to allrigs. That allrigs file seems to contain both the client and server. I thought it was an error because I would think...

Note that there seems to be an error with the file names: client and server both share a file name: MORCONI-ALLRIGS.zip

Is there a GitHub repo I could browse? If not, which download is best? Are they all for the Teensy?

I’d be interested in attempting to help solve this if you’re willing. What are the symptoms? Are you calling flush() when you need to send data right away? Are you sure you’re not including both libraries? (I’ve seen this last one cause issues.)

Try the QNEthernet library instead of NativeEthernet. It uses a different approach under the hood, and works much better with other libraries.

I could integrate it into the library (subject to my time), if anyone could provide some test hardware.

Call flush() when you want data to be sent immediately, otherwise it buffers a little bit. Some related info: * Post in thread 'QNEthernet and SimpleFTPServer modification' https://forum.pjrc.com/index.php?threads/qnethernet-and-simpleftpserver-modification.76108/post-351998 * Post in thread...

I’m curious, what about its presence will break the build when using the Arduino IDE?

One more thing I forgot about. There’s no need to use or include the DNSClient class. There’s an Ethernet.hostByName(host, ip) function that returns a bool indicating success. See the Readme for the library. (https://github.com/ssilverman/QNEthernet)

You also need to include "DNSClient.h" (soon to be "qnethernet/DNSClient.h"). That’s one of the very few extras you need to include beyond "QNEthernet.h".

Use Ethernet.begin(MyIP, MyMask, MyGateway, MyDNS). No need to set your own MAC. The QNEthernet library uses the Teensy’s built-in one.