3 ms·
> MicroPython does require a fairly biggish ARM Cortex M3, though. What do you mean? I run it on an ESP8266 just fine, the tooling isn't great (it launches a R
by StavrosK 10y ago
> MicroPython does require a fairly biggish ARM Cortex M3, though.
What do you mean? I run it on an ESP8266 just fine, the tooling isn't great (it launches a REPL and takes up your serial port with no way to stop that), but other than that it's fantastic.
- dbcurtis 10y agoYes, but the ESP8266 is a bit of a squeeze. It's a more comfortable fit on larger processors. As to the serial port/repl issue, can't you build your own image to do something else that you like better? Micropython is pretty easy to build, in general.
- StavrosK 10y agoI imagine I could, but I'm very bad with C :( The REPL is fantastic when you want to prototype stuff, but it's not great when you want to actually deploy things. I'm sure there's going to be some way to avoid launching it in the future, though, such as having a main.py file that has a `repl.run()` you can take out when deploying your own code.
- dbcurtis 10y agoThe code for Micropython is very well structured. The toolchain is pretty easy to set up, just apt-get and go. The configuration things like I/O pin assignments and such are all on pretty simple definition files. I'd be very surprised if the repl loop takes more than flipping a #define to turn off. No C wizardry needed.
- StavrosK 10y agoHmm, I'll have a look, but currently you need the repl to be able to write files (otherwise I'd have to include my files in the firmware and copy the entire thing every time). That's not really so bad, as it's what you do for the C++ version, but it would be nice if there were a way to update the code somehow. Maybe I'll write some code to fetch a file from an HTTP server and unpack it, though.