You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[Telink] Update Zephyr SDK references to tl_zephyr (#29)
* telink: update Zephyr SDK references to tl_zephyr
Prepare for the GitHub repo renames: update CI-critical
references (.github/workflows/examples-telink.yaml,
chip-build-telink Dockerfiles) and Telink documentation links
from telink-semi/zephyr to telink-semi/tl_zephyr.
Historical release notes (docs/platforms/telink/releases/) are
left unchanged (GitHub 301 redirects cover them)..
Also updates self references from telink-semi/connectedhomeip to
telink-semi/tl_matter.
* style: prettier-format markdown tables after repo rename
The zephyr -> tl_zephyr repository rename lengthened URLs in markdown
tables. Re-run prettier (same version and config as the Restyled
prettier-markdown restyler) on the markdown files touched by the rename
so table column widths are aligned again.
* workflows: update tl_zephyr and tl_ble_sdk
- update tl_zephyr from
6825a2f00ba6de9adce66f32f55c8b457c46948c
to
5cd959604f6ab5ff6af81c46b3a8b9324040f718
- update tl_ble_sdk from
53eb98b32ea79ed7ab38f5daabde0a78a7880cd9
to
9135c8eddb7caf72256c911b0ef113fb4037b1b4
Signed-off-by: Damien Ji <yinghao.ji@telink-semi.com>
* telink: fix getting-started clone directory after tl_matter rename
Address CodeRabbit review feedback on the repo rename.
- docs/platforms/telink/telink_getting_started.md: clone tl_matter into
the connectedhomeip directory so the subsequent
cd connectedhomeip step keeps working after the repository rename.
- scripts/tools/telink/update_zephyr.py: make the remote argument
optional nargs so its tl_zephyr default actually takes effect
when the argument is omitted.
Signed-off-by: Damien Ji <yinghao.ji@telink-semi.com>
---------
Signed-off-by: Damien Ji <yinghao.ji@telink-semi.com>
<!-- Telink provides the **BDT** (Burning Debug Tool) for flashing. On Windows use
265
265
the BDT GUI (`Telink BDT.exe`); on Linux use the `bdt` CLI. See the
266
-
[Telink Zephyr Getting Started — Flash the Firmware](https://github.com/telink-semi/zephyr/blob/develop/doc/telink/getting_started/index.md#flash-the-firmware)
266
+
[Telink Zephyr Getting Started — Flash the Firmware](https://github.com/telink-semi/tl_zephyr/blob/develop/doc/telink/getting_started/index.md#flash-the-firmware)
267
267
section for the chip-to-BDT name mapping and the unlock/erase/write flow.
268
268
269
269
A typical Linux BDT session:
@@ -280,7 +280,7 @@ A typical Linux BDT session:
280
280
281
281
Telink provides the **BDT** (Burning Debug Tool) for flashing. On Windows use
282
282
the BDT GUI (`Telink BDT.exe`). See the
283
-
[Telink Zephyr Getting Started — Flash the Firmware](https://github.com/telink-semi/zephyr/blob/release-v1.0-v4.1-branch/doc/telink/getting_started/index.md#Flash-the-Firmware)
283
+
[Telink Zephyr Getting Started — Flash the Firmware](https://github.com/telink-semi/tl_zephyr/blob/release-v1.0-v4.1-branch/doc/telink/getting_started/index.md#Flash-the-Firmware)
284
284
285
285
<!-- ### 4.3 UART console -->
286
286
@@ -374,7 +374,7 @@ To test OTA with a Linux OTA Provider, refer to the
374
374
375
375
-[Telink Release Notes](./releases/telink_release_notes.md) — version info,
376
376
chip/EVK versions, per-example support matrix, and resource usage tables.
0 commit comments