[core] Prepare for project name change
This commit is contained in:
@@ -41,7 +41,7 @@ Note that the download mode can only be activated when the flasher is running (t
|
||||
|
||||
## Auto-download-reboot
|
||||
|
||||
If you have a recent version of LibreTuya installed on the chip, you can use [Auto-download-reboot](../../flashing/tools/adr.md) to reboot the chip automatically. This is enabled by default, so you don't have to change anything.
|
||||
If you have a recent version of LibreTiny installed on the chip, you can use [Auto-download-reboot](../../flashing/tools/adr.md) to reboot the chip automatically. This is enabled by default, so you don't have to change anything.
|
||||
|
||||
## Single-adapter usage
|
||||
|
||||
|
||||
@@ -4,13 +4,13 @@ Debugging of Realtek Ameba chips is possible and was tested with OpenOCD running
|
||||
|
||||
*(the following is applicable to Arduino framework, and was not tested with SDK framework)*
|
||||
|
||||
LibreTuya has ready-to-use OpenOCD config files:
|
||||
LibreTiny has ready-to-use OpenOCD config files:
|
||||
|
||||
- [platform/realtek-ambz/openocd/amebaz.cfg](../../../cores/realtek-ambz/misc/amebaz.cfg)
|
||||
|
||||
## Local debugger
|
||||
|
||||
It should be possible to use PlatformIO's built-in debugging capabilities directly, when plugging an OpenOCD-compatible debugger into your PC. As there are no debugger interfaces built into Tuya boards, you need to specify your interface of choice in `platformio.ini`:
|
||||
It should be possible to use PlatformIO's built-in debugging capabilities directly, when plugging an OpenOCD-compatible debugger into your PC. As there are no debugger interfaces built into these IoT boards, you need to specify your interface of choice in `platformio.ini`:
|
||||
```ini
|
||||
[env:my_board]
|
||||
openocd_interface = <interface name>
|
||||
|
||||
Reference in New Issue
Block a user