4. Cannot Upload UIFlow 2.0 beta 14 to new CoreS3: "Error - Invalid Chip"

Cannot Upload UIFlow 2.0 beta 14 to new CoreS3: "Error - Invalid Chip"


  • I’m running esptool3.3.2-dev on mine

    When the coreS3 is in boot loader mode, the port is called usb modem, when in UIFlow mode the port is called uiflow

    On my computer it does take a while for the CoreS3 to be erased before flashing

    0
  • F

    I am able to flash the demo app on the CoreS3

    I am able to set the config on the CoreS3
    I am able to erase the CoreS3, prior to the step of flashing
    but then,
    I am not able to flash UIFLow on the CoreS3, and get just at beginning of process, before even getting the log window, a message "Error - Invalid Chip"

    when I flash "CoreS3 Touch Panel Hot-Fix firmware", I get:
    M5CoreS3 TP FW Information
    regA1 Lib Version: 0x3008
    regA3 ChipVendorID: 0x64
    regA6 Firmware ID : 0x05
    regA8 CTPMVendorID: 0x02

    0
  • F

    my port on the core, prior flashing is:
    tty.usbmodem14101

    0
  • F

    which log do you have when flashing?

    maybe I can try to flash through the terminal...

    0
  • F

    Hi,

    I just thought also that I was not requested, at the flashing step of UIFlow, to bind my Core3S with my account, but just got that message "Error - invalid chip"...

    Could it be related to the binding step?

    0
  • F

    After investigations through terminal and esptool.py:

    • what I thought as successful the Erase and Flash of the demo app and the config prior to flashing UIFlow2, wasn't in fact successful:
      log windows were confusing in those case,
      but not when step of flashing UIFlow2, as more tests are done I am getting the message "Error Invalid Chip".

    It seems that the CoreS3 is DOA for flashing and can just run the demo app....

    0

  • @flex

    Sorry for this happening, I believe that this problem may be caused by our failure to update the mac records of the database in time, we are optimizing our process, and I am very sorry again.

    If has any problem you can send the e-mail to me :-)

    0
  • F

    @IAMLIUBO
    yes it is solved now that MAC address was correctly registered in your server, and the binding process went through correctly, and therefore the burning or UIFLow...

    That takes me to a question:

    How could I unbind an S3 M5Stack device registered with an account, if I want another person with another account to take on it?

    Thanks

    0 1 Reply

  • @flex just delete it in UIFlow to unbind it. I tried this out while writing the guide

    1
  • F

    Thanks, I'll give it a try to unbind, and then will try a rebind

    0