Navigation

    M5Stack Community

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    1. Home
    2. rhumbertgz
    R
    • Continue chat with rhumbertgz
    • Start new chat with rhumbertgz
    • Flag Profile
    • Profile
    • Following
    • Followers
    • Blocks
    • Topics
    • Posts
    • Best
    • Groups
    Save
    Saving

    rhumbertgz

    @rhumbertgz

    0
    Reputation
    2
    Posts
    167
    Profile views
    0
    Followers
    0
    Following
    Joined Last Online

    rhumbertgz Follow

    Posts made by rhumbertgz

    • RE: Problems flashing and connecting ATOM Lite on Catalina 10.15.5 (19F101)

      Hi @m5stack

      you could pip install a pyserial module to solve it.

      I tried that but the problem persists. As a quick fix, I just flashed it using a window virtual machine.

      the LED always RED? which program are you use?

      Yes, but after I flashed the new firmware everything is behaving well.

      which program are you use?

      It turned RED, after I tried to flash it with the newer esptool (2.8) as I showed in my initial topic

      we will fix this bug in next version.

      🤞🏻

      Have a nice day

      posted in Cores
      R
      rhumbertgz
    • Problems flashing and connecting ATOM Lite on Catalina 10.15.5 (19F101)

      Hello,

      I'm having problems setting up my Atom Lite. I'm new to M5 hardware but I have some experience as developer. Following the M5 documentation, I tried to flash the new firmware UIFlow v1.5.3 but I get the following error:

      0_1591340699120_Screenshot 2020-06-05 at 09.04.31.png

      I found some related topics of other users having a similar issue in the past, however, none of their solutions worked for me.

      I noticed that the esptool.py (2.5) bundled in the M5Burner electron app was the root of my issue, so I tried a newer version 2.8. Using this new version I had no issues importing the module named serial.tools.list_ports.

      As the M5Burner wraps the esptool I tried to flash my Atom Lite with the latest esptool version (2.8) reusing the command shown on the above screenshot.

      ////////////////////
      esptool.py v2.8
      Serial port /dev/tty.usbserial-1D52D60BA5
      Connecting....
      Chip is ESP32-PICO-D4 (revision 1)
      Features: WiFi, BT, Dual Core, 240MHz, Embedded Flash, VRef calibration in efuse, Coding Scheme None
      Crystal is 40MHz
      MAC: d8:a0:1d:5c:96:40
      Uploading stub...
      Running stub...
      Stub running...
      Changing baud rate to 750000
      Changed.
      Configuring flash size...
      Auto-detected Flash size: 4MB
      Compressed 100 bytes to 43...
      Wrote 100 bytes (43 compressed) at 0x003ff000 in 0.0 seconds (effective 213.7 kbit/s)...
      Hash of data verified.
      Compressed 4182016 bytes to 1548805...
      Wrote 4182016 bytes (1548805 compressed) at 0x00001000 in 32.9 seconds (effective 1017.6 kbit/s)...
      Hash of data verified.

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

      Based on the above output I think that the flashing was ok, but still, I can't connect my Atom Lite to the UIFlow IDE (Online/Desktop)

      I get this error in both cases:
      Upload code failed, maybe your device is offline check it and retry

      After I reset the device I got the following output from the M5Burner COM Monitor

      ////////////////////////////////////////////////////////////////////////
      /dev/tty.usbserial-1D52D60BA5
      //////////////////////////////////////////////////////////////////
      I (10842) network: event 3
      ets Jun 8 2016 00:22:57

      rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
      configsip: 188777542, SPIWP:0xee
      clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
      mode:DIO, clock div:1
      load:0x3fff0018,len:4
      load:0x3fff001c,len:5100
      load:0x40078000,len:10596
      load:0x40080400,len:5744
      entry 0x400806c0
      I (586) cpu_start: Pro cpu up.
      I (586) cpu_start: Application information:
      I (586) cpu_start: Compile time: Jun 2 2020 15:09:32
      I (589) cpu_start: ELF file SHA256: 0000000000000000...
      I (595) cpu_start: ESP-IDF: v3.3.2-3-ge185be0ce3
      I (601) cpu_start: Starting app cpu, entry point is 0x40083e94
      I (0) cpu_start: App cpu up.
      I (612) heap_init: Initializing. RAM available for dynamic allocation:
      I (619) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAM
      I (625) heap_init: At 3FFBABF8 len 00025408 (149 KiB): DRAM
      I (631) heap_init: At 3FFE0440 len 00003AE0 (14 KiB): D/IRAM
      I (637) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
      I (644) heap_init: At 40097364 len 00008C9C (35 KiB): IRAM
      I (650) cpu_start: Pro cpu start user code
      I (220) cpu_start: Starting scheduler on PRO CPU.
      I (0) cpu_start: Starting scheduler on APP CPU.
      [ M5 ] node id:d8a01d5c9640, api key:MY_ATOM_KEY
      I (677) system_api: Base MAC address is not set, read default base MAC address from BLK0 of EFUSE
      I (678) system_api: Base MAC address is not set, read default base MAC address from BLK0 of EFUSE
      I (811) phy: phy_version: 4180, cb3948e, Sep 12 2019, 16:39:13, 0, 0
      I (10821) network: event 3
      ////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

      Right now the atom's led is always RED

      Any suggestions on how to solve this problem?

      Thanks in advanced,
      Humberto

      posted in Cores
      R
      rhumbertgz