wwatson
Well-known member
So I've got all the endpoints working, and it is sending and receiving ethernet packets. I haven't setup a way to change the mac address from what's already stored in the chip, but it is possible and I will work out a way to do that later on. But so far this is certainly promising, as long as it's faster than using a SPI ethernet device I'll be happy and it'll be worth it. Besides from anything complicated because of the lack of a tcp/ip stack it at least sends and receives raw frames. Most of what you see in the serial monitor is from broadcast messages because I have the filter set on the ASIX to allow them through and I believe multicast messages are not currently allowed through besides the one specified for all since the filter on the ASIX is not currently setup for any specific ones to flow through.
View attachment 17655
@vjmuzik - Good job with this. I took a break from working with my old USB2LAN adapter to spend the day checking out some of my wireless adapters. They all seem to be using versions of the Reltek WIFI chips. RTL81XXXX style. I spent a lot of time searching the Internet for generic driver source code, datasheets, programming reference manuals with no luck. The closet sources for information is with Linux kernel source code downloaded from GitHub. This stuff is heavily intertwined with the Linux kernel. The most common wireless Reltek chip version used seems to be the RTL8192CU chip. This is used by my CIsco and wifiN usb WIFI dongles. I have a Ralink wireless dongle that uses the RTL2800 chip.
So for me this may be out of my time available programming (playing) skill level.
@Forum - Has anybody else done any work with generic RTL8192CU drivers?
Going back to USB2LAN for now