Hi,

Given the risks of hacking IoT devices, could you please encrypt all of your subdomains - e.g. flow.m5stack.com and cloud.m5stack.com - so we're not sharing our credentials with the world whenever we access our code?

And forum.m5stack.com too, please?

Thanks,
Andrew

@ajb2k3 No worries, your reply (and support of the forum, thank you) helped me take another step in the right direction so I appreciate it.

The thing that bothered my about the UIFlow IDE when I tried it was that I had to push code from the web every time I booted the M5Stack (is there a way to store the code for the next time it boots?). MicroPython proper allows you to upload boot.py and main.py to permanently define the behaviour of the device.

So far I have used rshell (in place of ampy, etc.) and allows me to do everything else I want (the command 'rsync . /flash' is powerful - it syncs the M5Stack's flash folder with whatever files and directories are in your local directory).

I've run M5Burner previously, to install UIFlow. I didn't run it this time - I copied what I needed from the firmware/fw.json file.

Thank you both.

I have to say, however, that the advice to simply 'use M5Burner' is quite an unsatisfying answer as:
a) M5Burner is magic (aren't we supposed to be learning things here?), and
b) M5Burner isn't the magic I need yet, in that it has a very limited set of firmwares supported (and I wanted a particular flavour of MicroPython, not UIFlow).

Your answers did help me, however, to get to the answer I wanted thank you, because I was able to go to the directories inside M5Burner and find the correct commands/addresses for firmware components in the firmware/fw.json file.

To help anyone else reading this, I was able to burn this firmware:
https://github.com/m5stack/M5Stack_MicroPython/tree/master/MicroPython_BUILD/firmware/esp32_psram_all_bt

With this command:

>> esptool --chip esp32 --port COM5 --before default_reset --after no_reset write_flash -z --flash_mode dio --flash_freq 80m --flash_size detect 0x1000 bootloader/bootloader.bin 0xf000 phy_init_data.bin 0x10000 MicroPython.bin 0x8000 partitions_mpy.bin

Then using Putty or rshell, I could connect and confirm that it was working.

Then I pushed the python app I want with rshell - https://github.com/dhylands/rshell - and the rsync command within rshell.

So thanks for your help, I couldn't have understood the magic without being pointed to it.

Hi,

I'm having trouble getting up and running with MicroPython and would appreciate some help, please.

I have a M5Stack Fire (with psram) and I'm using a Windows 10 computer.

I'm trying M5Stack_MicroPython and have been successful at burning a couple of different MicroPython.bin files from various firmware builds (such as https://github.com/m5stack/M5Stack_MicroPython/blob/master/MicroPython_BUILD/firmware/esp32_psram_all_bt/MicroPython.bin)

>>esptool --chip esp32 --port COM5 erase_flash

Then:

>>esptool --chip esp32 --port COM5 --baud 460800 write_flash -z 0x1000 MicroPython.bin
esptool.py v2.6
Serial port COM5
Connecting....
Chip is ESP32D0WDQ6 (revision 1)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
MAC: 84:0d:nn:nn:nn:nn
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 460800
Changed.
Configuring flash size...
Auto-detected Flash size: 16MB
Flash params set to 0x0240
Compressed 2317264 bytes to 1477673...
Wrote 2317264 bytes (1477673 compressed) at 0x00001000 in 35.6 seconds (effective 521.0 kbit/s)...
Hash of data verified.

Leaving...
Hard resetting via RTS pin...

Then I try to connect with rshell or ampy and nothing happens. Connecting with putty, I see the following (over and over again):

rst:0x10 (RTCWDT_RTC_RESET),boot:0x17 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3f400020,len:462120
ets Jun  8 2016 00:22:57

Can anyone tell me what I'm doing wrong, please?

Thanks,
Andrew

Thank you @ajb2k3 and @watson, I'm up and running now and appreciate your help.

Hi,

Given the risks of hacking IoT devices, could you please encrypt all of your subdomains - e.g. flow.m5stack.com and cloud.m5stack.com - so we're not sharing our credentials with the world whenever we access our code?

And forum.m5stack.com too, please?

Thanks,
Andrew

Thanks for your quick reply. The link to the M5Burner executable for Windows - https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/software/M5Burner.zip - is dead. Is there another location to download this from, please?

Hi,

I'm following these instructions for setting up my M5Stack Fire for MicroPython:
http://forum.m5stack.com/topic/67/micropython-on-webide-1-prepare-and-hello-world

I have successfully erased the firmware and am attempting to burn m5cloud-20180516-v0.4.0.bin on the device. When I press 'Start', however, I see this in the logs:

main.py:96: wxPyDeprecationWarning: Using deprecated class PySimpleApp.
('self.chip: ', 'ESP32')
RF option applied...
======
CONNECT BAUD: 115200
============
.Efuse CONSOLE_DEBUG_DISABLE is already burned.
Uploading stub...
Running stub...
Stub running...
dl_list:
[]
[]
[]

![Here's a screenshot of my settings in the Espressif firmware tool:
![0_1552304181844_esp32_burn.jpg]

What can I do to get past this error and burn the new firmware to the device, please?