[xxxx]: doc/configure fixed

Author: SzigetiJ

README.md

@@ -33,11 +33,11 @@ I cannot understand, how and why driving LED strip became a 'get-started' level
 
 * Install required tools (see Requirements below).
 
-* Set your environment variables (`$PATH` for `xtensa-esp32-elf` and `$IDF_TOOLS_PATH`(?) for `esptool.py`)
+* Set your environment variables (`$PATH` for `xtensa-esp-elf` and `$IDF_TOOLS_PATH`(?) for `esptool.py`)
 
 * Follow [installation instruction](INSTALL) until `make` (`make install` is not reuqired).
 Personally, I always do multiple `VPATH` builds with different configuration settings.
-In order to use the `xtensa-esp32-elf` toolchain, you have to call the configure script with option
+In order to use the `xtensa-esp-elf` toolchain, you have to call the configure script with option
 `--host=xtensa-esp32-elf`.
 
 * Hopefully, the build runs without any error, and
@@ -83,7 +83,7 @@ THis list is supposed to grow longer and longer.
 * Low level peripheral access (via registers).
 * Peripheral controller drivers
   * I2C
-  * _TODO_ RMT
+  * RMT (TODO: example on RX)
   * _TODO_ SPI
   * _TODO_ etc.
 * Device drivers
@@ -97,13 +97,18 @@ THis list is supposed to grow longer and longer.
 * No HAL.
 * Most of the peripheral drivers are not implemented yet.
 * I know it is a big gap, but currently interrupts are not masked in during critical system routines.
-* As far as I know, the list of of ROM functions in the [linker file](esp32.ld) is incomplete.
+* Memory layout and sections defined in the [linker file](ld/esp32.ld) are very simple.
 
 ### Requirements
 
- * [Autotools](https://www.gnu.org/software/automake/), since Bilis ESP32 Basic is an automake project.
- * [xtensa-esp32-elf](https://docs.espressif.com/projects/esp-idf/en/stable/esp32/api-guides/tools/idf-tools.html) toolchain (compiler, linker, etc.).
+ * [Autotools](https://www.gnu.org/software/automake/), since Bilis ESP32 Basic is an automake project
+(suggested versions: automake:1.16.1, autoconf:2.69).
+
+ * [xtensa-esp-elf](https://docs.espressif.com/projects/esp-idf/en/stable/esp32/api-guides/tools/idf-tools.html) toolchain (compiler, linker, etc.)
+(suggested versions: 13.2.0).
+
  * [esptool](https://github.com/espressif/esptool) Currently, the flash tools (see scripts) rely on `esptool.py`
+(suggested versions: v4.7.0).
 
 ## Contribution
 

configure.ac

@@ -1,7 +1,7 @@
 AC_PREREQ([2.69])
 AC_INIT([esp32basic],[1.0.0])
 AM_INIT_AUTOMAKE
-: ${CFLAGS="-g -Os -Wall -nostdlib -mlongcalls" LDFLAGS="-specs=nano.specs"}
+: ${CFLAGS="-g -Os -Wall -nostdlib -mlongcalls"} ${LDFLAGS="-specs=nano.specs"}
 AC_PROG_CC
 AC_PROG_CC_STDC
 AC_DEFUN([AC_PROG_AR], [AC_CHECK_TOOL(AR, ar, :)])

examples/1rmtmorse/README.md

@@ -46,8 +46,8 @@ This entries are derived from input entries of ms resolution using the *stretch
 * But the *MorsePhase To Entry* generator relies on the *MorsePhase Generator*,
  which produces sequence of Morse-phases out of a text character [mphgen.c](mphgen.c).
 
-* The text charactes are provided by the *Character generator*,
-and this generator is the beginning of the chain [chargen.c](chargen.c).
+* The text charactes are provided by the *Byte generator*,
+and this generator is the beginning of the chain [generators.c](../../src/utils/generators.c).
 It takes a text message as parameter to iterate on.
 
 #### Hardware components

examples/3prog1/README.md

@@ -13,6 +13,7 @@ A simple pattern is being written to the OLED display from left to right.
 * I2C_SLAVE#1: BME280 temperature/pressure/humidity sensor
 * I2C_SLAVE#2: BH1750FVI light sensor
 * I2C_SLAVE#3: 32x128 OLED display
+* [NODE0 .. NODE4]: 5 nodes (maybe on breadboard) as connection nodes of multiple wires.
 
 #### Connections
 

src/utils/uartutils.c

@@ -9,6 +9,11 @@
 #include <stdio.h>
 #ifdef __XTENSA__
 #include <sys/reent.h>
+#if __GNUC__ >= 13
+#define IMPURE_PTR _impure_ptr
+#else
+#define IMPURE_PTR _global_impure_ptr
+#endif
 #else
 #define _impure_ptr NULL
 #define _vsnprintf_r(X,Y1,Y2,Y3,Y4) vsnprintf(Y1,Y2,Y3,Y4)
@@ -21,7 +26,7 @@ int uart_printf(UART_Type *psUART, const char *pcFormat, ...) {
   char acBuf[100];
   va_list va;
   va_start(va, pcFormat);
-  int iLen = _vsnprintf_r(_impure_ptr, acBuf, ARRAY_SIZE(acBuf), pcFormat, va);
+  int iLen = _vsnprintf_r(IMPURE_PTR, acBuf, ARRAY_SIZE(acBuf), pcFormat, va);
   va_end(va);
   for (int i = 0; i < iLen; ++i) {
     psUART->FIFO = acBuf[i];