Navigation

    M5Stack Community

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

    puzznic

    @puzznic

    0
    Reputation
    4
    Posts
    141
    Profile views
    0
    Followers
    0
    Following
    Joined Last Online

    puzznic Follow

    Posts made by puzznic

    • RE: UIFlow doesn't start on new Core2

      hello Felix,

      just to be clear, when you run the Factory Test the screen in your M5Core2 works, correct? correct. here's a screenshot of the test running:

      ![alt text](0_1609747947765_IMG-2857 (Small).jpg image url)

      After burning UIFlow, have you tried to reset your M5Stack with the reset button?
      Also have you tried to fully shutdown your M5Stack by pressing and holding the power button, then power it on again?

      the device has been reset and turned off and on multiple times indeed.
      so weir, I reckon...

      posted in Core 2
      P
      puzznic
    • RE: UIFlow doesn't start on new Core2

      thank you for your reply Felix.
      I indeed erased and burnt UIFlow mutlitpl times from different Windows laptops with the same (bad) results :(
      could it be a faulty unit then? even if the FactoryTest reports total success?

      • =================
        Erase now
        =================
        esptool.py v2.5.0
        Serial port COM5
        Connecting....
        Detecting chip type... ESP32
        Chip is ESP32D0WDQ6 (revision 1)
        Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse
        MAC: b8:f0:09:c5:b1:34
        Uploading stub...
        Running stub...
        Stub running...
        Erasing flash (this may take a while)...
        Chip erase completed successfully in 35.7s
        Hard resetting via RTS pin...
        =================
        Erase Successfully
        =================~~~~
      posted in Core 2
      P
      puzznic
    • UIFlow doesn't start on new Core2

      hello,
      my new Core2 has just been delivered and I believe my Win10 install is working fine (I can successfully burn and run other downloadable apps such as draw_by_touch or Core2FactoryTest) but burning UIFlow_Core2 v1.7.1-core2 (or any other previous version actually) doesn't work :

      the device turns on, screen turns on too but only displays an empty black screen (not the expected UIFlow logo or anything)

      (please find below the M5Burner log that reports it was successfully burnt -- please see log below)

      could you think of something critical I am missing here?
      many thanks,

      • =================
        Start Burn
        =================
        --chip esp32 --port COM5 --baud 1500000 --before default_reset write_flash -z --flash_mode dio --flash_freq 80m --flash_size detect 0x7ff000 C:\Users\vpennel\Downloads\M5Burner\packages\fw\other\wifi.bin 0x1000 C:\Users\vpennel\Downloads\M5Burner\packages\fw\core\UIFlow_Core2-v1.7.1-core2.bin
        =================
        esptool.py v2.5.0
        Serial port COM5
        Connecting...
        .
        Chip is ESP32D0WDQ6 (revision 1)
        Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse
        MAC: b8:f0:09:c5:b1:34
        Uploading stub...
        Running stub...
        Stub running...
        Changing baud rate to 1500000
        Changed.
        Configuring flash size...
        Auto-detected Flash size: 16MB
        Compressed 100 bytes to 24...
        Writing at 0x007ff000... (100 %)
        Wrote 100 bytes (24 compressed) at 0x007ff000 in 0.0 seconds (effective 230.2 kbit/s)...
        Hash of data verified.
        Compressed 8376320 bytes to 3457107...
        Writing at 0x00001000... (0 %)
        [...]
        Writing at 0x00349000... (99 %)
        Writing at 0x0034d000... (100 %)
        Wrote 8376320 bytes (3457107 compressed) at 0x00001000 in 55.3 seconds (effective 1210.9 kbit/s)...
        Hash of data verified.
        Leaving...
        Hard resetting via RTS pin...
        =================
        Burn Successfully
        =================
      posted in Core 2
      P
      puzznic
    • new Core2 user - unable to run UIFlow

      hello,
      I just received my new Core2 and, after following the excellent UIFlow Quick Start I was able to successfully install the Win10 driver, and run the M5Burner.
      however, while burning the UIFlow_Core2 v1.7.1-core2 (or any other previous version actually) successfully completes, after the device resets I only see an on but empty screen - no UIFlow logo or the expected mainpage is displayed.

      this is especially puzzling to me as I can successfully burn and run other apps, such as the downloadable Core2FactoryTest or draw_by_touch for example, without any issue.
      am I missing something here ?
      thanks a grand for your help.

      • =================
        Start Burn
        =================
        --chip esp32 --port COM5 --baud 1500000 --before default_reset write_flash -z --flash_mode dio --flash_freq 80m --flash_size detect 0x7ff000 C:\Users\vpennel\Downloads\M5Burner\packages\fw\other\wifi.bin 0x1000 C:\Users\vpennel\Downloads\M5Burner\packages\fw\core\UIFlow_Core2-v1.7.1-core2.bin
        =================
        esptool.py v2.5.0
        Serial port COM5
        Connecting...
        Chip is ESP32D0WDQ6 (revision 1)
        Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse
        MAC: b8:f0:09:c5:b1:34
        Uploading stub...
        Running stub...
        Stub running...
        Changing baud rate to 1500000
        Changed.
        Configuring flash size...
        Auto-detected Flash size: 16MB
        Compressed 100 bytes to 24...
        Writing at 0x007ff000... (100 %)
        Wrote 100 bytes (24 compressed) at 0x007ff000 in 0.0 seconds (effective 267.3 kbit/s)...
        Hash of data verified.
        Compressed 8376320 bytes to 3457107...
        Writing at 0x00001000... (0 %)
        [...]
        Writing at 0x0034d000... (100 %)
        Wrote 8376320 bytes (3457107 compressed) at 0x00001000 in 55.2 seconds (effective 1213.3 kbit/s)...
        Hash of data verified.
        Leaving...
        Hard resetting via RTS pin...
        =================
        Burn Successfully
        =================
      posted in Bug Report
      P
      puzznic