Yeah. A 1980s era Microsoft DOS computer capability running on a $1.75 microcontroller is exactly what I want, on one hand. I'm not greedy or needy, after all. A microcontroller with WiFi connectivity built in (or easily attached, imported, or included) for building a networked system of these smart little computers and hardware part controllers too. Like, a washing machine that sends a "done washing" message to a headless server sitting in the home.
But I do kinda need them to be expendable. So designs that are priced at less than $5 is kinda a requirement for me. Because I sincerely believe I'm stepping into new and unexplored territory. A lot of experiments will be done with this information technology system. Which means there needs to be a massively productive facility for having a swarm of microcontrollers. Hence, the need for turning any microcontroller encountered in the wild into a controlled and compliant robot brain for my heterogeneity of devices and home appliances.
I don't mind thinking about how to not bust open a stack that can only fit three variables on it or something. In comparison to the simple architecture which includes parsimonious memory modules or only two registers total, for example, what's complex will be the total assembly and combinations of Turing machine based codes made possible by teeny microcontrollers/computers doing simple things. Like receiving temperature levels and then relaying or sending packets of temperature or heat data to a server. Acquiring x86 instruction sets is definitely unnecessary here. Or, rather, I only need x86 code execution for not re-inventing things like WiFi. ARM or x86, for example, then, should be seen as just an imported (think Python) or included (think C) module.
> Yeah. A 1980s era Microsoft DOS computer capability running on a $1.75 microcontroller is exactly what I want, on one hand. I'm not greedy or needy, after all. A microcontroller with WiFi connectivity built in (or easily attached, imported, or included) for building a networked system of these smart little computers and hardware part controllers too. Like, a washing machine that sends a "done washing" message to a headless server sitting in the home.
OK, that's an ESP8266, then. Here's a module for $2.11.
That's the starting point. If you want to design boards, you can put down ESP8266 castellated modules (easy) or the ESP8266 chip itself (somewhat harder).
Because of issues with electronics supply chains, often complete boards are cheaper than you can buy the modules and chips at low quantities (things are really optimized to sell a thousand units or more). Even buying blank keycaps at low quantities was very expensive compared to finished products of printed sets of keys.
> A microcontroller with WiFi connectivity built in
ESP32 modules are $2 on LCSC and come with a built-in wifi antenna
> So designs that are priced at less than $5 is kinda a requirement for me. Because I sincerely believe I'm stepping into new and unexplored territory
No, your requirements are the same ones that every cheap IoT device has. Open up a $5 smart switch and see how they manufactured it for $1
> simple architecture which includes parsimonious memory modules or only two registers total, for example
What are you on about? Using an unusual instruction set will increase NRC, cost per MCU, and power consumption. Low power ISAs are a scam. Race to sleep if you wanna save resources
But I do kinda need them to be expendable. So designs that are priced at less than $5 is kinda a requirement for me. Because I sincerely believe I'm stepping into new and unexplored territory. A lot of experiments will be done with this information technology system. Which means there needs to be a massively productive facility for having a swarm of microcontrollers. Hence, the need for turning any microcontroller encountered in the wild into a controlled and compliant robot brain for my heterogeneity of devices and home appliances.
I don't mind thinking about how to not bust open a stack that can only fit three variables on it or something. In comparison to the simple architecture which includes parsimonious memory modules or only two registers total, for example, what's complex will be the total assembly and combinations of Turing machine based codes made possible by teeny microcontrollers/computers doing simple things. Like receiving temperature levels and then relaying or sending packets of temperature or heat data to a server. Acquiring x86 instruction sets is definitely unnecessary here. Or, rather, I only need x86 code execution for not re-inventing things like WiFi. ARM or x86, for example, then, should be seen as just an imported (think Python) or included (think C) module.