X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
Date:	Sat, 2 Sep 2017 13:10:21 +0000
From:	"Peter Stuge (peter AT stuge DOT se) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To:	geda-user AT delorie DOT com
Subject:	Re: [geda-user] OT: wifi (802.11) embedded implementation
Message-ID:	<20170902131021.GW22159@stuge.se>
References:	<b4007158-ec3c-b843-79ec-53f9647c751f AT iae DOT nl>
MIME-Version:	1.0
In-Reply-To:	<b4007158-ec3c-b843-79ec-53f9647c751f@iae.nl>
Reply-To:	geda-user AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	geda-user AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

myken wrote:
> I would like to implement a wifi connection on an embedded application 
> using the applications own MPU + an additional MAC/PHY.
> Is this a very silly thing to do?

Short answer: Yes.

Instead of MAC/PHY just use an ESP8266 or ESP32. Bare chips are ~¤1,
SMT modules are ~¤2-3 if you can wait for shipping from China.

I like to use the ESP-12-E or ESP-12-F, which have the ESP8266.

ESP32 is dual core double clock (2x 160 MHz cores) compared to ESP8266.

ESP8266 being single core with Wi-Fi on same core having highest
priority means that it is not good for low-latency tasks, but will do
fine as "WiFi-connector".


> Am I missing something why this approach is just not done (besides
> the SW-stack needed)?

It just isn't cost effective for an MCU system. If you have a Linux
kernel then you'll have Wi-Fi software in there, and a Wi-Fi adapter
either on a SoC local bus or on USB. Several USB Wi-Fi adapters are
quite poor, but one or two are fine.


//Peter

- Raw text -