What is basic hardware requirements for micropython

[pfalcon]

I refactored "unix" port modules to use static initialization, so now startup memory requirements can be easily seen in unix port:

Code: Select all

$ ./micropython
Micro Python build 4abaa1b-dirty on 2014-04-18; UNIX version
>>> mem_info()
mem: total=1663, current=443, peak=1346
GC: total: 128000, used: 560, free: 127440
 No. of 1-blocks: 11, 2-blocks: 4, max blk sz: 6

(Note that these with "test" objects/functions in unix/main.c disabled - with default build you'll get ~800 bytes allocated after startup).

[dnhkng]

Hi pfalcon,

You mentioned earlier in the thread that you thought Micropython could run with less RAM. Do you think it could run on this particular 32 bit microcontroller, info here: https://github.com/esp8266/esp8266-wiki/wiki and here: https://nurdspace.nl/ESP8266

A $3, 32 bit,WiFi connected, Python Interpreting SoC seems nice to me

[dhylands]

Hi pfalcon,

You mentioned earlier in the thread that you thought Micropython could run with less RAM. Do you think it could run on this particular 32 bit microcontroller, info here: https://github.com/esp8266/esp8266-wiki/wiki and here: https://nurdspace.nl/ESP8266

A $3, 32 bit,WiFi connected, Python Interpreting SoC seems nice to me

How much RAM/ROM does this device have?

So far the smallest device that micropython has actually been ported to is the Teensy 3.1 which has 256K flash and 64K RAM. I think that slightly smaller devices may be possible. Somebody is apparently working on getting micropython running on the TI cc3200 which has 256K RAM and no flash and I think that this should be possible,

[dnhkng]

I'm having a hard times figuring that out

There is a discussion about that here: http://www.esp8266.com/viewtopic.php?f=5&t=9

[Turbinenreiter]

there is no documentation of that chip whatsoever, it's dead in the water. some people will try to reverse engineer it, and if they like that, let them have fun, but i don't think this chip will see actual usage anytime soon. everyone using it right now is just in for the fun of figuring it out.

if your goal is to build something, never touch anything where you can't find tons and tons of documentation.
if you want to pull awesome reverse engineering hacks - go for this obscure piece.

[blmorris]

there is no documentation of that chip whatsoever, it's dead in the water. some people will try to reverse engineer it, and if they like that, let them have fun, but i don't think this chip will see actual usage anytime soon. everyone using it right now is just in for the fun of figuring it out.

if your goal is to build something, never touch anything where you can't find tons and tons of documentation.
if you want to pull awesome reverse engineering hacks - go for this obscure piece.

+1, quoted for truth. As for me, unless there is truly no choice I won't even bother with products that require an NDA to get at the documentation. I acknowledge that there are perfectly good products that I am missing out on. However, if I need to make something that works, then life is too short to go chasing down documentation from a company that won't publish it openly. It might be a different matter if I were working with a big company - then you probably have vendors falling over themselves to give you this information - but I'm not in that situation, and I imagine most micropython developers aren't either.

[nuraciti]

Just out of curiosity: Is it currently possible/intended to run the code on any other stm32 board (discovery with a f401, nucleo with a f407) or are the requirements strictly a f405?

Here is a initial porting on a nucleof401/4x1RE: https://github.com/nuraci/micropython

if you are interested , here is a open discussion: http://forum.micropython.org/viewtopic.php?f=3&t=422

[dnhkng]

Thanks Damien!

This port for the ESP8266 you recently added is the one I'm super interested in. I'm hoping to have micropython-enabled IoT's covering my house soon!