Differences between Micropython ports for ESP32 and ESP8266

[OutoftheBOTS_]

If TouchPad was instantiated on a platform without cap touch features - like STM - then either the API shouldn't exist for that port or, better, an exception ("Capacitive touch not present for this port") should be raised.

I like the idea of an exception being raised if the feature doesn't exist on that port. That way code is portable and if u try to use a feature the hardware doesn't have then u get an exception. The big advantage is 1 standard docs for all ports. although MP seems to be able to get contributors to write code getting contributors to write docs seems a little harder

[pythoncoder]

...But I don't see any good reason to leave methods in pyb that already have equivalents...

I do. It would break almost all of my code.

For all that there may be an "equivalent" in machine, they often differ in detail. Sufficiently to cause a major headache if you have a lot of code to maintain.

I'd fight any removal of features from pyb. Judging by Damien's comments on GitHub I think it's unlikely to happen.

The ideal outcome would be one where machine improves to the point where pyb can be deprecated for all but a few special STM-specific purposes.

[mattyt]

...But I don't see any good reason to leave methods in pyb that already have equivalents...

I do. It would break almost all of my code.

I don't want to break anyone's code. I'm not suggesting removing anything, at least not in any short timeframe. The order should be: ensure there are appropriate replacement methods, mark 'old' ones as deprecated, sometime later (or maybe never) remove the old methods.

For all that there may be an "equivalent" in machine, they often differ in detail. Sufficiently to cause a major headache if you have a lot of code to maintain.

I'd fight any removal of features from pyb. Judging by Damien's comments on GitHub I think it's unlikely to happen.

OK, maybe I need to let go of the idea of ever removing them. I certainly don't want to fight you. I'm ok with leaving them in - my main concern is to a) provide new users clear guidance what to use and b) figure out how to better handle when port must diverge.

The ideal outcome would be one where machine improves to the point where pyb can be deprecated for all but a few special STM-specific purposes.

Agree completely.

I like the idea of an exception being raised if the feature doesn't exist on that port. That way code is portable and if u try to use a feature the hardware doesn't have then u get an exception.

I think this makes sense too. Peter, do you have an opinion?

The big advantage is 1 standard docs for all ports. although MP seems to be able to get contributors to write code getting contributors to write docs seems a little harder

I have a strong desire to at least create ESP32 docs based on the current documentation system, even if it is for the most part duplicates of ESP8266. This shouldn't take a huge amount of effort; it's writing and updating the docs to describe the ESP32 differences that will take more of an effort. But if I can at least put in place the stubs we can build on it...

Looking further out I would like to think we could have common documentation for all the ports with callouts where specific ports differ from the generic implementation. However this will take some time and is beyond my current commitment level.

[pythoncoder]

...

I like the idea of an exception being raised if the feature doesn't exist on that port. That way code is portable and if u try to use a feature the hardware doesn't have then u get an exception.

I think this makes sense too. Peter, do you have an opinion?
...

It's a good idea.

As is documenting ESP32.

As for ESP32 I can't take it seriously (in official or Loboris form) until this is fixed. I fail to see any practical application for a device which can't handle a WiFi outage.

[danielm]

Hi all, based on the fact that Pycom team tends to move their focus from dev/OEM module development to consumer products (PyGo/PyLife) we are considering to build FW stack of our products on micropython.org ESP32 port. I did not follow this forum very often for more than a year. Looking at the github there are some esp32-related commits from time to time.

My questions is what is current perception of regular forum members and code contributors regarding maturity and long-term development of micropython.org ESP32 port?

[mattyt]

There are a couple of key issues with it but, for me, it's clear that the ESP32 port is of tremendous importance. Almost all of my 'side project' time will be spent using and, hopefully increasingly, contributing to that port.

[danielm]

I am glad to hear that the ESP32 port will be developed and maintained. I will start testing soon. I want to use Pycom WiPy 3.0 as a hardware because it contains very good switching regulator (LM3281) and I want to test deep-sleep currents as well. Should micropython.org port work on this board or should I expect some issues?
I also have ESP32-WROOM based devkit but I am not sure if there are some peripherals which might affect deep-sleep current measurement.

[jdcrunchman]

Hi, I'm wondering if Anyone has ever thought about the idea of being able to SSH into the ESP32 board using it's builtin Wifi network.
Although I'm having to deal with the only way I've been able to find, by using REPL.

It would be really nice if I can connect my iPad running Pythonista3 then moving the files via an SSH client I have for my Mac, or using a client with my iPad.

I'm anticipating the need for field testing an App Im working on using the ESP32 and an SX1276 LoRa transceiver.

I'm not been able to find a simple way I can SSH into my ESP32 from my iPad. I know people have tried to use a Web Based REPL, but I find it very difficult to use with my iPad. Most of my Pythonista3 files I hope would be saved in my ICloud or Google Docs. But how can I move these files into my ESP32 via SSH? Is it even possible?

The ESP32 uses MicroPython of course, so has anyone ever bothered to write an SSH server that runs on Micropython? If not, how can I recruit volunteer programmers to help me write one. I'm not a very experienced programmer, and I KNOW there is a need for developers to be able to SSH into an ESP32. I know Arduino has one, but why not the ESP32. I mean, it's been around for over 2 years, wouldn't you think that someone out there might have throught about the need to be able to SSH into the ESP32?


John
jdcrunchman@gmail.com

[OutoftheBOTS_]

If you google you should find a number of FTP servers for micropython that run on ESP32 and ESP8266 that are great for transferring files to the micropython board.

[jdcrunchman]

Can I be so bold as to ask you for some URL's that can lead me to an SSH server? All I get from Google is what I need to buy, and not information, so I started using DuckDuckGo... You haven't even shared your search phrase.... I haven't gotten much from Google, or DuckDuckGo search engine.

I could find NOTHING using my search phrase.