Pycom and Damien George join forces for the ESP32

[daniel]

@Roosted we are a bit delayed on this but it's definitely going to happen. Last week we were completely overloaded with Sigfox. The PR's will start appearing this coming week.

Cheers,
Daniel

[Roosted]

@daniel Awesome! I'm looking forward to it!

[Roosted]

@daniel said in Pycom and Damien George join forces for the ESP32:

The PR's will start appearing this coming week.

Any progress here? I have not seen a single PR..

[daniel]

Any progress here? I have not seen a single PR..

I know... we are delayed :-(
We plan to send a burst of PR's over the weekend.

Cheers,
Daniel

[Jeck]

Great news! Thank you for bringing uPy forward!

[daniel]

OK, we have started the process. The first step is to add some changes to the IDF:

https://github.com/espressif/esp-idf/pull/358
https://github.com/espressif/esp-idf/pull/359
https://github.com/espressif/esp-idf/pull/361

Now the next immediate step is to create PRs in micropython-esp32 for the following:

• Refactor the socket module to allow multiple NICs (WiFi, LoRa, Sigfox, LTE, ...)
• Add support to build different boards (WiPy, LoPy, SiPy, ...)

We expect to be able to submit those 2 PRs tomorrow.

Cheers,
Daniel

[crankshaft]

@daniel - so it appears that more than 2 months has passed and the various promises to submit these pull requests have still not been carried out ?

...starting early next week.

...The PR's will start appearing this coming week.

...We expect to be able to submit those 2 PRs tomorrow.

...We plan to send a burst of PR's over the weekend.

[robert-hh]

@crankshaft If you compare the two MicroPython ports for esp32 and the Pycom family, you'll notice that they are quite different, not only in matters of implementation, but also in the various classes. That looked like a lot of decisions to be made on which port is changed and how, and all of that while Pycom still piles up a lot of other challenges. And so I was surprised about the short time line announced.
Maybe, the '2 to 3 weeks' are to be understood like the Singaporean 'in 6 Months'. I'll be glad when it comes.

[jmarcelino]

@crankshaft
It seems to be already going?

https://github.com/micropython/micropython-esp32/pull/69

[daniel]

Well, we were too optimistic with the timelines. There are 2 things happening:

1. The transition is a lot more complex than we initially thought.
2. We are also working on several other things in parallel which limits the amount of time than we can dedicate to the merge.

Anyway, it's already happening:

https://github.com/micropython/micropython-esp32/commit/dc82def1f482c17517e5bcaeae4191787623fa0e

https://github.com/micropython/micropython-esp32/commit/f704375b2083863866502a5e3b67bfb6480af8b5

https://github.com/micropython/micropython-esp32/commit/ff0ca1e782b3e6f3640b7ea2019f9ea716b2a52a

Next thing will be Bluetooth, but I expect a lot of discussion around the API before it's approved to be merged.

[Roosted]

Such a shame there have been very little upstream PR's in the past months... Pycom's micropython version has grown a lot, and has become very nice.

The upcoming event SHA2017 is a non profit outdoor Hacker camp taking place in The Netherlands in 2017 on August 4th to 8th. The first 4500 people that buy a ticket will receive a free electronic badge with a ESP32, e-ink display and touch sensor. We want our badge to be more than a namecard: a hackable piece of hardware, and thus we would like to run the upstream micropython on our badge. More information on our badge is available on Hackaday and our blog.

Is there any progress in the pipeline for the upstreaming of your micropython Pycom?
And would you be interested in Pycom promotion via our badge?

[daniel]

@Roosted thanks for your message. I agree we should have made lots more progress by now, but lack of resources and time has slowed us down. We have contributed with the multi-threading part, and also BLE which is still pending to be merged.

You can still use Pycom's ESP32 port, its GPLV3 license allows you to do anything you want with the code as long as it remains open source. Isn't that what open source is all about ;-)?

What do you suggest we could do in order to help the SHA2017 badge be a success?

Cheers,
Daniel

[livius]

Hi @daniel,

Is the work still in progress or have been abandoned?