mirror of
https://github.com/RIOT-OS/RIOT.git
synced 2024-12-29 04:50:03 +01:00
cpu/esp8266: toolchain renamed
To make the migration progress to the new RTOS SDK easier, the new toolchain was renamed to xtensa-esp8266-elf. This makes it possible to have the new and the old toolchain installed in parallel.
This commit is contained in:
parent
b15d7df6dc
commit
2c7b9b4fb4
@ -41,7 +41,7 @@ endif
|
|||||||
|
|
||||||
# regular Makefile
|
# regular Makefile
|
||||||
|
|
||||||
export TARGET_ARCH ?= xtensa-lx106-elf
|
export TARGET_ARCH ?= xtensa-esp8266-elf
|
||||||
|
|
||||||
# ESP8266 pseudomodules
|
# ESP8266 pseudomodules
|
||||||
PSEUDOMODULES += esp_gdb
|
PSEUDOMODULES += esp_gdb
|
||||||
|
@ -211,7 +211,7 @@ git checkout esp8266_only_rtos_sdk
|
|||||||
docker build -t riotbuild .
|
docker build -t riotbuild .
|
||||||
```
|
```
|
||||||
|
|
||||||
A `riotdocker` version that contains toolchains for all plattforms supported
|
A `riotdocker` version that contains toolchains for all platforms supported
|
||||||
by RIOT can be found at [GitHub](https://github.com/RIOT-OS/riotdocker).
|
by RIOT can be found at [GitHub](https://github.com/RIOT-OS/riotdocker).
|
||||||
However, the Docker image generated from the this Docker file has a size of
|
However, the Docker image generated from the this Docker file has a size of
|
||||||
about 1.5 GByte.
|
about 1.5 GByte.
|
||||||
@ -299,19 +299,19 @@ Furthermore, the following packages (Debian/Ubuntu) have to be installed:<br>
|
|||||||
|
|
||||||
The Xtensa GCC compiler for ESP8266 configured for use with RIOT-OS can
|
The Xtensa GCC compiler for ESP8266 configured for use with RIOT-OS can
|
||||||
be downloaded and installed as precompiled binary archive from
|
be downloaded and installed as precompiled binary archive from
|
||||||
[GitHub](https://github.com/gschorcht/xtensa-lx106-elf):
|
[GitHub](https://github.com/gschorcht/xtensa-esp8266-elf):
|
||||||
|
|
||||||
```
|
```
|
||||||
mkdir -p $HOME/esp
|
mkdir -p $HOME/esp
|
||||||
cd $HOME/esp
|
cd $HOME/esp
|
||||||
git clone https://github.com/gschorcht/xtensa-lx106-elf
|
git clone https://github.com/gschorcht/xtensa-esp8266-elf
|
||||||
```
|
```
|
||||||
|
|
||||||
Once the compiler is installed, you have to expand your `PATH` variable by
|
Once the compiler is installed, you have to expand your `PATH` variable by
|
||||||
the directory with Xtensa GCC binaries:
|
the directory with Xtensa GCC binaries:
|
||||||
|
|
||||||
```
|
```
|
||||||
export PATH=$HOME/esp/xtensa-lx106-elf/bin:$PATH
|
export PATH=$HOME/esp/xtensa-esp8266-elf/bin:$PATH
|
||||||
```
|
```
|
||||||
|
|
||||||
### <a name="esp8266_installation_of_esp_idf"> Installation of the ESP8266 RTOS SDK</a> [[TOC](#esp8266_toc)]
|
### <a name="esp8266_installation_of_esp_idf"> Installation of the ESP8266 RTOS SDK</a> [[TOC](#esp8266_toc)]
|
||||||
@ -383,7 +383,7 @@ Once you have installed all required components, you should have the following
|
|||||||
directories.
|
directories.
|
||||||
|
|
||||||
```
|
```
|
||||||
/path/to/esp/xtensa-lx106-elf
|
/path/to/esp/xtensa-esp8266-elf
|
||||||
/path/to/esp/ESP8266_RTOS_SDK
|
/path/to/esp/ESP8266_RTOS_SDK
|
||||||
/path/to/esp/esptool-esp8266-rtos-sdk-v3
|
/path/to/esp/esptool-esp8266-rtos-sdk-v3
|
||||||
```
|
```
|
||||||
@ -392,7 +392,7 @@ To use the toolchain, please check that your environment variables are set
|
|||||||
correctly to
|
correctly to
|
||||||
|
|
||||||
```
|
```
|
||||||
export PATH=/path/to/esp/esptool-esp8266-rtos-sdk-v3:/path/to/esp/xtensa-lx106-elf/bin:$PATH
|
export PATH=/path/to/esp/esptool-esp8266-rtos-sdk-v3:/path/to/esp/xtensa-esp8266-elf/bin:$PATH
|
||||||
export ESP8266_RTOS_SDK_DIR=/path/to/esp/ESP8266_RTOS_SDK
|
export ESP8266_RTOS_SDK_DIR=/path/to/esp/ESP8266_RTOS_SDK
|
||||||
```
|
```
|
||||||
|
|
||||||
@ -742,7 +742,7 @@ its SoftAP WiFi interface. The driver periodically scans all visible ESP8266
|
|||||||
nodes.
|
nodes.
|
||||||
|
|
||||||
The following parameters are defined for ESP-NOW nodes. These parameters can
|
The following parameters are defined for ESP-NOW nodes. These parameters can
|
||||||
be overriden by [application-specific board configurations](#esp8266_application_specific_board_configuration).
|
be overridden by [application-specific board configurations](#esp8266_application_specific_board_configuration).
|
||||||
|
|
||||||
<center>
|
<center>
|
||||||
|
|
||||||
@ -941,7 +941,7 @@ line as the <b>first</b> line to the application makefile `$APPDIR/Makefile`.
|
|||||||
INCLUDES += -I$(APPDIR)
|
INCLUDES += -I$(APPDIR)
|
||||||
```
|
```
|
||||||
|
|
||||||
**Pleae note:** To make such application-specific board configurations
|
**Please note:** To make such application-specific board configurations
|
||||||
dependent on the ESP8266 MCU or a particular ESP8266 board, you should
|
dependent on the ESP8266 MCU or a particular ESP8266 board, you should
|
||||||
always enclose these definitions in the following constructs:
|
always enclose these definitions in the following constructs:
|
||||||
```
|
```
|
||||||
@ -1053,7 +1053,7 @@ where `/path/to/build/dir` is the path to the application build directory
|
|||||||
start `GDB` in second terminal window using command:
|
start `GDB` in second terminal window using command:
|
||||||
|
|
||||||
```
|
```
|
||||||
term2> xtensa-lx106-elf-gdb /path/to/build/dir/image.elf
|
term2> xtensa-esp8266-elf-gdb /path/to/build/dir/image.elf
|
||||||
```
|
```
|
||||||
|
|
||||||
To start debugging, you have to connect to `QEMU` from `GDB` with command:
|
To start debugging, you have to connect to `QEMU` from `GDB` with command:
|
||||||
@ -1102,7 +1102,7 @@ e.g., `/dev/ttyUSB0`.
|
|||||||
|
|
||||||
2. Start GDB with the application in a second terminal window:
|
2. Start GDB with the application in a second terminal window:
|
||||||
```
|
```
|
||||||
term2> xtensa-lx106-elf-gdb /path/to/the/build/dir/image.elf
|
term2> xtensa-esp8266-elf-gdb /path/to/the/build/dir/image.elf
|
||||||
```
|
```
|
||||||
where `/path/to/build/dir` is the path to the application build directory
|
where `/path/to/build/dir` is the path to the application build directory
|
||||||
`$(BINDIR)` where `$ELFFILE.bin` is generated by the `make` command, for example
|
`$(BINDIR)` where `$ELFFILE.bin` is generated by the `make` command, for example
|
||||||
|
Loading…
Reference in New Issue
Block a user