Compiling firmware with pfalcon fork https://github.com/mongoose-os/esp-open-sdk

[hcet14]

Hi,

I would like to start with my ESP8266 after half a year not touching it.

But I do remember having a hard time to compile the firmware. Docker didn't work at all. https://github.com/pfalcon/esp-open-sdk was very hard.

My question now is, if someone here tried the pfalcon fork https://github.com/mongoose-os/esp-open-sdk? Looks like it is living and maintained.

Thanks.

hcet14

[mattyt]

Most people here will be using mainline MicroPython; what was difficult about it? Perhaps we can help if you explain the issues you were seeing...

[davef]

Same here and about 6 months ago. I had problems using esp-open-sdk but with 6 month experience building custom code for the ESP32 maybe I'd be able to work out where I was going wrong.

However, I would also be interested if there is another way to build code for the ESP8266. Is there a tutorial somewhere?

Thanks

[hcet14]

kevinscorpionfox stated here viewtopic.php?f=16&t=10617, that he got the toolchain running with ESP8266_RTOS_SDK. Since ESP8266_NONOS_SDK is not supported anymore, just bugfixes, i would like to use ESP8266_RTOS_SDK.

I just want to tell you guys, I just try the toolchain from esp-open-sdk, version=4.8.x , now it's working for me

The guys who support the fork went back to 2.2.x ESP8266_NONOS_SDK https://github.com/mongoose-os/esp-open ... 0b13112-r9

hcet14

[kevinkk525]

I have the esp8266 micropython build with the pfalcon esp-open-sdk working in this script: https://github.com/kevinkk525/pysmartno ... ository.sh

I should point out that this thread is only about the esp-open-sdk and has nothing to do with the pfalcon micropython fork!
Even for the main micropython the esp-open-sdk repository of pfalcon is being used.

And personally it also bothered me that that repository hasn't had any commits recently and I'd be interested in getting a more up to date esp-open-sdk working on the esp8266 (I would expect newer sdk versions to contain improvements, bugfixes, security fixes etc, but maybe my expectation is wrong).

[davef]

Hi Kevin,

Thank you for your script. One question ... line 22 <make axtls> is just to confirm everything is OK or is this step absolutely required?

[hcet14]

Most people here will be using mainline MicroPython; what was difficult about it? Perhaps we can help if you explain the issues you were seeing...

I can't remember anymore. I remember, that I was just one time successful compiling the firmware for my ESP8266. I was using https://github.com/dmascord/micropython since I need a UART. I tried again, but failed. Damien (dmascord) is going to help me with the UART, so I have to get that running again. I'm thinking about trying kevinkk525's script with https://github.com/mongoose-os/esp-open-sdk.

Thanks to all.

[kevinkk525]

One question ... line 22 <make axtls> is just to confirm everything is OK or is this step absolutely required?

Unless the dependencies changed, this line is required. It might be possible to not need it if all tls/ssl modules are disabled but I'm not sure about that.

[kevinkk525]

I was using https://github.com/dmascord/micropython since I need a UART. I tried again, but failed. Damien (dmascord) is going to help me with the UART, so I have to get that running again.

Can you explain the differences between this fork and the main micropython? The uart on the esp8266 is available too in main micropython?

[hcet14]

Can you explain the differences between this fork and the main micropython? The uart on the esp8266 is available too in main micropython?

If I remember right, ESP8266 has got 1,5 hard UARTs. One UART is used for the REPL. The 2nd (just TX) is usually used for debugging. Micropython supports the hard UARTs, the fork also supports a soft UART.

The soft UART from the fork is not working with my sensor. Communication is wrong, you may read my old posts for further information.