Fix the CI pipeline

Author: imarkov

README.md

@@ -43,7 +43,7 @@ Highlights:
   - (Only if you happen to have an [ESP32-S3-USB-OTG](https://www.espressif.com/en/products/devkits)): Build with `native` and the ESP-IDF master branch and add `esp32s3_usb_otg` to the `--features` build flags above (as in `export ESP_IDF_VERSION=master; cargo build --features native,esp32s3_usb_otg`) to be greeted with a `Hello Rust!` message on the board's LED screen
   - (Only if you happen to have an [Ethernet-to-SPI board based on the W5500 chip](https://www.wiznet.io/product-item/w5500/)): Build with `native` and the ESP-IDF master branch and add `w5500` to the `--features` build flags above (as in `export ESP_IDF_VERSION=master; cargo build --features native,w5500`) to have Ethernet connectivity as part of the demo
     - Note that other Ethernet-to-SPI boards might work just fine as well, but you'll have to change the chip from `SpiEthDriver::W5500` to whatever chip your SPI board is using, in the demo code itself.
-  - (**NOTE**: Untested; Only if you happen to have an [ESP32 board with an onboard IP101 LAN chip and/or a stock ESP32 board connected to an IP101 Ethernet board via RMII](https://docs.espressif.com/projects/esp-idf/en/latest/esp32/hw-reference/esp32/get-started-ethernet-kit.html)): Build with `native` and the ESP-IDF master branch and add `ip101` to the `--features` build flags above (as in `export ESP_IDF_VERSION=master; cargo build --features native,ip101`) to have Ethernet connectivity as part of the demo
+  - (Only if you happen to have an [ESP32 board with an onboard IP101 LAN chip and/or a stock ESP32 board connected to an IP101 Ethernet board via RMII](https://docs.espressif.com/projects/esp-idf/en/latest/esp32/hw-reference/esp32/get-started-ethernet-kit.html)): Build with `native` and the ESP-IDF master branch and add `ip101` to the `--features` build flags above (as in `export ESP_IDF_VERSION=master; cargo build --features native,ip101`) to have Ethernet connectivity as part of the demo
     - Note that other RMII Ethernet boards might work just fine as well, but you'll have to change the chip from `RmiiEthDriver::IP101` to whatever chip your board is using, in the demo code itself.
 - (Only if you happen to have an ESP32-S2 board and can connect a LED to GPIO Pin 04 and GND): Try accessing `http://<dhcp-ip-of-the-board>>/ulp` once build is flashed on the MCU
 

src/main.rs

@@ -180,13 +180,13 @@ fn main() -> Result<()> {
             rmii_rdx0: pins.gpio25,
             rmii_rdx1: pins.gpio26,
             rmii_crs_dv: pins.gpio27,
-            rmii_mdc: pins.gpio12,
+            rmii_mdc: pins.gpio23,
             rmii_txd1: pins.gpio22,
             rmii_tx_en: pins.gpio21,
             rmii_txd0: pins.gpio19,
-            rmii_mdio: pins.gpio13,
+            rmii_mdio: pins.gpio18,
             rmii_ref_clk: pins.gpio0,
-            rst: Some(pins.gpio14),
+            rst: Some(pins.gpio5),
         },
         RmiiEthChipset::IP101,
         None,
@@ -971,3 +971,17 @@ impl ili9341::Mode for KalugaOrientation {
         matches!(self, Self::Landscape | Self::LandscapeFlipped)
     }
 }
+
+// TODO: This is coming from the panic_abort crate (but only when panic_immediate_abort is NOT enabled),
+// because it calls fs::canonicalize() here: https://github.com/rust-lang/backtrace-rs/blob/master/src/symbolize/gimli/elf.rs#L353
+//
+// It is unclear what the long-term fix would be:
+// - Option A: Implement `realpath` for the ESP-IDF similarly to this implementation: https://sourceware.org/legacy-ml/newlib/2016/msg00498.html
+//             and assuming that the current directory is `/`
+// - Option B1: Implement `realpath` for the ESP-IDF with a stub that always fails with ENOSYS
+// - Option B2: Implement a special version of fs::canonicalize() in Rust STD which fails with ENOSYS
+// - Option C: Implement a special version of fs::canonicalize() in Rust STD which panics <- this is what OS-es like Hermit & others do
+#[no_mangle]
+extern "C" fn realpath(path: *const std::os::raw::c_void, wat: *const std::os::raw::c_void) {
+    panic!("Not implemented");
+}