Dogbone06

@wwatson - Thanks for the detailed breakdown and history of this project. It is and will be a great help for our team at SparkFun! While we can't be sure of all the details in the final product, starting with something that is working and can...

HI All - First - this is a awesome project with great results. Not the easiest hardware/software problems to solve! We were contacted recently by @Dogbone06 about this project and if SparkFun would be interested. Our answer is absolutely...

The BT pins were never routed but that an easy task for Sparkfun to do on their design. From what we saw the 1DX and 1YN are identical at least for the WiFi pins. I made the chips with both of them and they seem to work the same. It's truly...

I was testing an FTP driver for the TEENSY41 with QNEthernet_WIFI I was getting intermittent crash reports for a null pointer. I add code to the SDIO driver "cyw43_T4_SDIO.cpp" at about line# 372. An update...

I'm not following. I seem to be missing context.

@shawn - I was getting intermittent crashes when I was testing some buggy FTP software for the Teensy41. Turns out that it was sending a null pointer to the SDIO driver "cardCMD53()" which did not catch it. I added a test for it. It returns a...

@wwatson you've inspired me to add a note to the SNTPClient example with alternative hosts.

Ok, thanks...

It's often the case that local routers have a time server. Some do not. This might be the reason.

@shawn - I could not get the SNTPClient sketch to work on either WIFI or native Ethernet. If I change: udp.send(Ethernet.gatewayIP(), kNTPPort, buf, 48)) to: const char timeServer[] = "time.nist.gov"; udp.send(timeServer, kNTPPort, buf, 48) It...

Also on my mind is multi-interface support, but that's later. (No promises and no target dates.)

Just noticed that in simplePing.ino and ping.ino I did not change the ping destinations back to arduino.cc. Now fixed. simplePing.ino line#33 should be: constexpr char kHostname[]{"arduino.cc"}; and ping.ino line #38 should be: constexpr char...

Updated from github - cyw43_ping working: > note: the code checked in with ..\QNEthernet_WIFI\src\qnethernet_opts.h :: ARDUINO_TEENSY41_CYW4343W 1 Looking up "arduino.cc"... IP = 18.238.238.4 Round-trip time 18.6 ms Round-trip time 6.5 ms...

Glad to see you have it working. No, secret.h really does not have to be that far into the depths of QNEthernet:) I just had not got around to moving it yet. A person could also add the contents to the beginning of each sketch except the file is...

There's some stuff I need to refactor, design-wise, so that Wi-Fi fits in better. I intend to start with a new "WiFi" class (or similar) for Wi-Fi-only things. I'm currently in the process of working on converting everything to C++ plus...

I am going to leave everything alone for now until you are finished with refactoring. That will minimize any confusion that might happen...

One other thing I forgot to mention is that cyw43_scan.ino has issues still. It will perform one or maybe two scans perfectly but will intermittently fail after that. I am looking into it. It has something to do with not resetting after each...

Just saw that secrets.h is manually included in sketch - so local copy could replace that. NOTE: FAIL :: "\libraries\QNEthernet_WIFI\examples\cyw43_scan\cyw43_scan.ino" Setup/begin Code of scan not the same as in ping? Code starts and seems...

Okay - kudos to @shawn for that on QNEthernet then - that explains not seeing any hardware connect or details specific to 1DX :) Yes, See link in p#96 that hardware is here and was used for early testing Mar 19, 2026. Hoping the pins/names...

@defragster - The ReadMe is @shawns ReadMe. I just added info at the top on how to use the WIFI portion and the warnings. He did all the work on the ReadMe

You also have a WiFi chip right? Would be nice if you could test it out. It will take weeks before I have one to test myself.

Very cool @wwatson and @Dogbone06 !!! The ReadMe alone looks like an LARGE amount of work! Indeed, hardware in short supply. @PaulStoffregen collected a series of commercial variants, not sure where that is in the queue, Connections documented...

Months of work you mention, that is amazing. I am so happy to see that this now works, I need to order WiFi chips, I sent all off to you guys. But I still have 1DX and 1YN in stock so I'll order in a few PCB's so I can test this out myself...

Well, with the help of @shawn I have an initial working version of QNEthernet for the CYW4343x:) I only have the 1DX version of the chip to test with so it will be interesting to see if the 1YN? version works as well. I found the the QNEthernet...

Not sure what you mean by "ports"? Do mean pins? As far as top speed usage, that depends on the application and is subjective. The pico is using one SPI port and the Teensy 4.1 is using one SDIO port out of two;)

SDIO has 6 pins - 4 data line, a clock line and a command line. Two additional GPIOs are needed to control the sleep state and an interrupt trigger. IIRC, the murata chip variant that was used for this project does not support SPI. Those that do...

Yes, @KurtE pulled DOCS and wrote code for 2nd SDIO usage as noted in p#79 - available WiFi chips are no longer SPI but SDIO. An adapter placed into the SDIO SD card socket could also be used.

Looking forward to what Shawn finds since he's the QNEthernet guy. Maybe we'll finally have true WiFi for the Teensy this summer! o_O

I had a version of this board that plugged into the SDcard slot on the T4.1. I can't recall correctly, but I think the INT GPIO might be optional, so that setup would only require a single additional GPIO pin, although obviously you can't insert...

One note is that I'm in the process of poking around to C++-ize the QNEthernet driver so that it's easier to change driver hardware on the fly without having to change #defined options. Having said that, the core functions a driver needs to...

Now we really just need someone smart than me ( :rolleyes: ) to implement this into a proper networking library like QNEthernet. I really hope it can be done!

Decided to quit staring at the @Dogbone06 WIFI adapter that had been sitting on one of my desks for months and at least try to get most or all of the picowi documentation example working with the T4.1. After months of learning and experimenting I...

From all the posts the recent day here, I'm very happy the project is alive again. Very well done!!! :D:D:D:D

Fixed. Thanks! :) Two is absolutely twice as good as only 1 chip.

Yes, you can have two. Whether it’s any good is kinda up to you!

Is this any good? Wonder if we can now have 2x 16MB PSRAM's to get a total of 32MB :rolleyes: