jczic / ESP32-MPY-Jama

v1.2 - UI tool for manage Espressif ESP32 microcontrollers with embedded MicroPython for MacOS, Windows and Linux: mini IDE, files manager, REPL, real time dashboards (sys/net), advanced features (gpio/mp3/leds/...)
https://github.com/jczic/ESP32-MPY-Jama
MIT License
424 stars 25 forks source link

Unable to connect to device on Macbook M1 Pro: Port is not compatible #52

Open shahrukh-alizai opened 1 year ago

shahrukh-alizai commented 1 year ago

Screenshot:

I'm getting this error on Macbook M1 Pro.

image

However, it works fine using esptool on terminal.

image
ghvau commented 1 year ago

In your installation the error is correct -> because esp32 (-> tool name) is unequal esp8266 !

https://github.com/micropython/micropython/issues/2709 "... in Built-in Functions there is a 'compile()' function that hasn't been implemented on the esp8266..."

The ESP32 Jama based on (use) this function.

Einariux commented 1 year ago

Same problem with ESP32 Nodemcu,but firmware flash and erase.MacbookAir M1. All work with firmware v1.20.0 (2023-04-26).

FabianClemenz commented 9 months ago

UPDATE: it works now - i needed to remove the jumper, so it was not in bootloader mode

I have the same Problem with my M2 Pro Macbook.

I was able to flash the firmware with MPY-Jama and with esptool directly. But it can't connect to the board.

Screenshot 2024-01-12 at 10 38 28

Screenshot 2024-01-12 at 10 38 58

I'm using the WT32-ETH0 Board over a USB-to-TTL Connector

The Version of MPY-Jama is 1.2.0

i Tried it with ESP Firmware 1.19.1 and 1.22.1

marksull commented 8 months ago

Maybe this will help others if you see the same issue and might help lead to a root cause. On the same M2 with the same ESP32-S3: 1) If I clone this repo and start the app from the repo, I get the "port is not compatible" error when trying to connect to the ESP32-S3 2) If I download the pre-built MacOS app and run it, I can communicate with the ESP32-S3 fine

I can switch between the two installation styles, and the issue is consistent. I suspect a MacOS security issue is causing the problem, but looking through the console logs I couldn't identify a reason.

mwalimu commented 3 weeks ago

I found that in order to get the board to connect it had to have micropython already installed on the device.