The MAC address code you are using doesn’t support a Teensy 4.1 so all your Teensy’s are trying to communicate with the same address(0XDEADBEEFFEED).
The code you want for a Teensy 4.1 is this:
uint8_t mac;
void...
The hard part is really the lack of documentation like you get from the standard Ethernet library. I’ve talked directly to MACs already using FNET because of a protocol I had to reverse engineer. Though I did have to...
If you don’t need full networking capability then you could talk directly to a MAC address (such as broadcast) without the need for UDP, but NativeEthernet doesn’t have any functions to do that for you. FNET has those...
If by Broadcast you are actually referring to Multicast then yes there is support, both in Paul’s Ethernet library and my NativeEthernet library.
/* Start EthernetUDP socket, listening at local port PORT */
uint8_t...
Honestly I’m not sure about why the delay is needed, also flush for UDP has never done anything. I’m curious if it’s actually not sending out the packet or if the receiving Teensy is just missing it, I’ll admit I’ve...
If the LEDs on the Teensy socket aren’t on then something is wrong, only one of the two LEDs are connected and it’s setup to show activity when you call Ethernet.begin().
When you provide a static IP there is no return function, therefore when you try to != 0 it throws an error since there is no value to compare. When you only give it a MAC address it does provide a return value because...
The boot loader does not support the 2nd USB port, but on the T4.1 there are pads on the bottom to access the 1st USB port's D+ and D- pins so that you can add your own connector. Though it's not immediately clear how...
Please verify you have the latest download for NativeEthernet, there used to be a problem with client not returning an IP address until client.available() was called. I remember fixing that, but I may not have updated...
In my case I’m more interested in getting the most performance out of WiFi while still using a Teensy that I can. It’s certainly more cost effective to go with an ESP, but serial can only handle so much and I’m stuck in...
I’m curious how viable this could be on a Teensy 4.1, if I’m not mistaken enough of the pins for SDIO2 are available to use a SDIO based WiFi chip. Other options include using SDIO1 via a micro SD card breakout or...
As a shot in the dark I would think either other interrupts could be causing it or just the nature of how NativeEthernet is working. If you work direct with FNET you don’t have to poll for the packet like you used to...
Due to the nature of this wrapper library the performance will never be fully optimal. If you need more precision over what’s going on you will have to learn FNET and make a service for what you want to do. FNET...
Admittedly that is a draw back with the NativeEthernet library, but I’ve tried to keep its functionality as close to how the W5500 works as I can remember. Being that it is blocking in nature I strongly suggest anyone...
If your going to be soldering it down to a production board I would suggest taking a look at this for a more permanent solution than pogo pins.
https://forum.pjrc.com/threads/65633-T4-1-External-USB-C-Connector
It’s definitely better to make sure you have the differential pair length and impedance matched just to be compliant with spec. However, there is a some wiggle room allowed and even with running the signals over hookup...
Find latest posts