Search:

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...

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...

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...

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...

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...

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...

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....

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...

To me it seems like there would be more overhead using DR_TOGGLE and keeping track of which bits need to be toggled between each write, personally I would just stick to using SET and CLEAR which is...

As per the schematic D+ is on the ground side and D- is on the power side, I thought about designing a small board, but personally I probably won’t need it so I didn’t.

I haven’t made a pull request for T4.x so currently this only works for T3.x

Not sure if it's strictly related to the M1 Macs or just Big Sur, but I've had it say "Unable find Teensy Loader. (p) Is the Teensy Loader application running?" a couple of times and simply trying to...

Here's a quick write up for a permanent and relatively simple way for anyone wanting to add an external USB connector to a Teensy 4.1 based PCB.

First step is to make 2 solder balls on the D+ and...

As far as I remember Windows file explorer didn't automatically update any open folder and you always had to refresh an open window to see the changes that were made from somewhere else. Though I...

Happy Holidays to everyone as well and a Merry Christmas to those who celebrate it.

I’m using it almost like a texture map for drawing “realistic” controls on screen and drawing the color separately underneath it. With the color space conversion it makes it easy to use transparent...

Now that I got my test boards in I loaded this up again and thanks to your ShowPXP method I was able to determine that the manual has a slight error in the PXP_NEXT description that caused the issues...

This is a known “non-issue” since MacOS Catalina, reason being is that a separate download is already provided that has Teensyduino already preinstalled with Arduino.

Yeah that would be it, I overlooked the Audio Adapter microSD socket and just assumed he was using the bottom pins of the T4.0.

It looks like yours is using the new libraries so there shouldn’t be any difference, the T4.0 and 4.1 are functionally identical.

You may not be using the Teensy beta which has a wrapper for the SD library to use the SdFat-beta library instead which is a whole lot faster.

There isn’t any other dependencies, it’s already preconfigured for TLS to be active. So either it’s not using the new ones you downloaded or the fnet_user_config.h file was changed to disable TLS.

On a Mac this happens in one of two scenarios, either it’s simply using too much power or more than likely your power wires are shorted somewhere.

I can also confirm Big Sur works, I’ve had no issues so far.

Is there a difference between using WriteBufferingStream and WriteBufferingClient?

That would make sense but server.available() never returns a client if it doesn't have data available.

I'm curious why writeBuffer.available() would return 0 which as far as I can tell is calling client.available() which didn't return a 0 in the statement before that.

Try updating your libraries first, I know there was a problem at one time with availableForWrite not returning correctly, but after a quick test on my end I can verify that it is working now.
FNET:...

For my use case I’m going to be making multiple calls in succession so I preemptively added the support in for it. Most of the registers are 16 bytes apart except for the last 3, to me it also...

Based on the manual the only advantage of using the pxp_next is that you can queue up another command while one is already running so as soon as the previous one finishes it'll start the next one....

The USBHost_t36 library isn’t only for the Teensy 3.6 anymore though the name hasn’t changed. The reason why there isn’t any 5v on the Host port is because you aren’t using the library that will...

As for the displays the best way to connect them would be to make use of both SPI buses and have them update using DMA so they don't add any delay, though I'm not sure if anyone has made a DMA...

I forgot to look at this when Paul mentioned it, here's the fix: https://github.com/vjmuzik/NativeEthernet

I haven’t done too big of a benchmark so I can’t say for certain. I can say that adding a rotation or flip did not increase the number of cycles it took for the PXP to process. So if you are already...

I started working on adding support for the Pixel Pipeline built in to the T4.
So far I have the overlay and output stages working correctly, rotate/flip in the output stage also works.
I have...

Adafruit_GFX already has frame buffer/canvas objects that work with all their primitives.

As you know a Teensy only has a limited number of pins available, however the processor has more pins than the Teensy form factor allows. The pins made available to the end user are carefully...

I would recommend adding a #elif statement instead so that you can use the Teensy 4.0’s normal VID and PID. This way when you select the serial port in Arduino it shows up as a Teensy 4.0.

I'm a little confused by this, I'm not sure if you know this but on Amazon a product page isn't limited to one distributor, if you'll note on that product page there are 9 listings from different...

Definitely, that's what I planned to do.

Yeah DigiNet is a low level protocol not requiring an ethernet stack, the only common part between all the DigiNet consoles is the initial handshake, after that most of the consoles have their own...

Yeah I totally understand, Avid really needs to stop placing arbitrary limitations in there products, they love limiting everything to 32 where ever they can to squeeze more money from the end user...

At the moment in FNET there aren't separate names for each service, so every service would share the same name, I haven't thought to try multiple services of the same type so this issue never arose...

Use the “Adafruit_TinyUSB_Teensy_MSC_SD” example, it just uses the SD wrapper Paul made with the beta.

The IOMUX is responsible for routing internal registers to external signals, just turning on VSELECT will not change to 1.8v mode. VSELECT for SD0 can be routed to one of four pins through the IOMUX,...

It's not rocket science, the reference manual tells you you need external circuitry, so you need external circuitry:
22568

They are very much exposed pins and not just internal though the only one we have exposed is AD_B1_01 which is pin 18 on the Teensy 4.1. Like I said earlier that pin would be responsible for changing...

I don’t have plans to merge this or if I’ll continue it further than what it is now, like I said I only wanted see if it was feasible.

The pins for VSELECT can be found in the reference manual, which does show the external pins that it maps to, for SD0 it can be one of these 4 pins here:


USDHC1_VSELECT
GPIO_EMC_41 ALT6...

I see now it's not the SD cards power that needs to change it's the NVCC_SD voltage that has to change, which based on the Teensy 4 schematic is hardwired to 3.3v so currently we can't do anything...