update

I am still working on the module integration - got one answers to my help issue on github repo from loboris

• https://github.com/vrubel/MicroPython_ESP32_psRAM_LoBo/commit/57227919ffa93f426fb21212a5d949ea92f2d9f5

• Add a define NEW_MODULE to menuconfig (MicroPython_BUILD/components/micropython/Kconfig.projbuild)

• Add a ifdef guard with your DEFINE NEW_MODULE to the micropython makefile ( MicroPython_BUILD/components/micropython/component.mk)

• write your sourcecode (MicroPython_BUILD/components/micropython/esp32/new_module.c)

Kconfig.projbuild

   config MICROPY_USE_NEW_MODULE 
            bool "Use NEW_MODULE "
            default y
            help
                Include source from new_model.c into build 

component.mk

ifdef MICROPY_USE_NEW_MODULE 
SRC_C += esp32/new_module.c
endif

mpconfigport.h

#ifdef MICROPY_USE_NEW_MODULE 
extern const struct _mp_obj_module_t mp_module_new_module;
#define BUILTIN_MODULE_NEW_MODULE { MP_OBJ_NEW_QSTR(MP_QSTR_indicator), (mp_obj_t)&mp_module_new_module},
#else
#define BUILTIN_MODULE_NEW_MODULE
#endif
...

#define MICROPY_PORT_BUILTIN_MODULES \
...
      BUILTIN_MODULE_NEW_MODULE \

Step 1: Build Micropython on Windows 10 DONE

• GIVEN Ubuntu Linux Subsystem

• AND dependent packages / python /pip (see wiki by loboris)

• AND M5fire serial port connected on COM1 (/dev/ttyS1)

• AND user has access to serial port

• AND git repositories from loboris (optional) and M5Stack

• WHEN ./BUILD.sh menuconfig

• AND ./BUILD.sh -j4

• AND ./BUILD.sh --port /dev/ttyS1 flash

• AND reset M5fire

• AND ./BUILD.sh --port /dev/ttyS1 monitor

• THEN bootup messages (TODO)

• AND python REPL active

• AND M5stack module (via help(modules)

OPEN:

• startup errors (boot.py/main.py?)
• no ui with menu config

Step 2: Add a simple C/INO module with python access OPEN

 and comments welcome

Looks great.

Sounds great! Where do you write it.

@ajb2k3:

• OK, I did not know that arduino was not fully supported. thanks.
• is m5go and m5fire a different product? I do not think so.
• where are the sources of the versions located if they are open source? or do you mean the binaries are free (I found them in the M5burner replease)

The espressif idf is a topic which I have too look deeper into.

Internally or in a special thread?

there is a small mistake in the last commands:

ampy put boot.py

that is

ampy put {{local_file_path}} # implicit remote path and name with json

and the JSON-File

ampy is a great console script implemented in Python to conntect to the M5/Micropython Devices via serial terminal

NOTE: so this will not work if another tool (like putty) already using the serial port!

The following command (in windows style) would print the content of the file boot.py from the system on the command line

ampy -p COM1 get /flash/boot.py

Use the following to write a new file

ampy -p COM1 get /flash/boot.py  boot.py

that is

ampy -p {{port}} get  {{remote_file_path}}  {{local_file_path}}

To put a file on the device you have to write

ampy -p COM1 put boot.py /flash/boot.py

that is

ampy -p {{port}}  put {{local_file_path}} {{remote_file_path}}

There are some ideas for improvement of the process of ampy:

1. the serial port would better be read from a configuration file, hence it often the same entry

you may use the environment variable AMPY_PORT, AMPY_BAUD... but this is a little bit too static
you can find my test code on the forked repository https://github.com/ahaeberle/ampy

2. add default path for local files and write them without giving the name on a second parameter

from the system on the command line to write a new file.

remember to put the an ampy.json in the folder or use a --json {{filename}}

ampy -p COM1 get /flash/boot.py

Use the following to write a new file

ampy get /flash/boot.py  # with implicit filename

3. add default path for remote files to put them with a simpler command

new command to get a file with an ampy.json in the calling directory

ampy get /flash/boot.py   

that is

ampy get  {{remote_file_path}}  # implicit name and path with json

and the JSON-File

{
    "AMPY_PORT": "COM1",
    "AMPY_DELAY":     0.0,
    "AMPY_BAUD": 115200,
    "REMOTE_PATH": "/flash/",
    "LOCAL_PATH": "./"
}

Hi, might it be helpful to create a bit more structure in this forum? It is often hard to find the articles matching the right product.
I would really like to see groups like M5fire, MicroPython. Maybe even language based groups like German ;-) to help our younger m5-developers to place their questions.
What do you think?
Sincerely Felix

I do suggest the following:

1. M5cloud was the first version of the cloud app now replaced with Flow/UI.Flow
2. M5GO was the second version of the cloud app now replaced with Flow/UI.Flow
3. UI.Flow is compatible with all ESP32 systems (M5core and M5fire, sometimes called M5GO)
4. M5Cam is based on M5Stick
5. M5Bala will use ESP32