Skip to content

Commit 0c59baf

Browse files
s07641069s07641069
committed
[Telink] update readme files
1 parent cad4373 commit 0c59baf

File tree

15 files changed

+60
-60
lines changed

15 files changed

+60
-60
lines changed

‎examples/air-quality-sensor-app/telink/README.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -138,10 +138,10 @@ feature for another Telink example:
138138
139139
After build application with enabled OTA feature, use next binary files:
140140
141-
- zephyr.bin - main binary to flash PCB (Use at least 2MB PCB).
142-
- zephyr-ota.bin - binary for OTA Provider
141+
- merged.bin - main binary to flash PCB (Use at least 2MB PCB).
142+
- metter.ota - binary for OTA Provider
143143
144-
All binaries has the same SW version. To test OTA “zephyr-ota.bin” should have
144+
All binaries has the same SW version. To test OTA “metter.ota” should have
145145
higher SW version than base SW. Set CONFIG_CHIP_DEVICE_SOFTWARE_VERSION=2 in
146146
corresponding “prj.conf” configuration file.
147147
@@ -156,7 +156,7 @@ Usage of OTA:
156156
- Run the Linux OTA Provider with OTA image.
157157
158158
```
159-
./chip-ota-provider-app -f zephyr-ota.bin
159+
./chip-ota-provider-app -f metter.ota
160160
```
161161
162162
- Provision the Linux OTA Provider using chip-tool

‎examples/all-clusters-app/telink/README.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -140,10 +140,10 @@ feature for another Telink example:
140140
141141
After build application with enabled OTA feature, use next binary files:
142142
143-
- zephyr.bin - main binary to flash PCB (Use at least 2MB PCB).
144-
- zephyr-ota.bin - binary for OTA Provider
143+
- merged.bin - main binary to flash PCB (Use at least 2MB PCB).
144+
- metter.ota - binary for OTA Provider
145145
146-
All binaries has the same SW version. To test OTA “zephyr-ota.bin” should have
146+
All binaries has the same SW version. To test OTA “metter.ota” should have
147147
higher SW version than base SW. Set CONFIG_CHIP_DEVICE_SOFTWARE_VERSION=2 in
148148
corresponding “prj.conf” configuration file.
149149
@@ -158,7 +158,7 @@ Usage of OTA:
158158
- Run the Linux OTA Provider with OTA image.
159159
160160
```
161-
./chip-ota-provider-app -f zephyr-ota.bin
161+
./chip-ota-provider-app -f metter.ota
162162
```
163163
164164
- Provision the Linux OTA Provider using chip-tool

‎examples/all-clusters-minimal-app/telink/README.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -125,10 +125,10 @@ feature for another Telink example:
125125

126126
After build application with enabled OTA feature, use next binary files:
127127

128-
- zephyr.bin - main binary to flash PCB (Use at least 2MB PCB).
129-
- zephyr-ota.bin - binary for OTA Provider
128+
- merged.bin - main binary to flash PCB (Use at least 2MB PCB).
129+
- metter.ota - binary for OTA Provider
130130

131-
All binaries has the same SW version. To test OTA “zephyr-ota.bin” should have
131+
All binaries has the same SW version. To test OTA “metter.ota” should have
132132
higher SW version than base SW. Set CONFIG_CHIP_DEVICE_SOFTWARE_VERSION=2 in
133133
corresponding “prj.conf” configuration file.
134134

@@ -143,7 +143,7 @@ Usage of OTA:
143143
- Run the Linux OTA Provider with OTA image.
144144

145145
```
146-
./chip-ota-provider-app -f zephyr-ota.bin
146+
./chip-ota-provider-app -f metter.ota
147147
```
148148

149149
- Provision the Linux OTA Provider using chip-tool

‎examples/bridge-app/telink/README.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -285,10 +285,10 @@ feature for another Telink example:
285285
286286
After build application with enabled OTA feature, use next binary files:
287287
288-
- zephyr.bin - main binary to flash PCB (Use at least 2MB PCB).
289-
- zephyr-ota.bin - binary for OTA Provider
288+
- merged.bin - main binary to flash PCB (Use at least 2MB PCB).
289+
- metter.ota - binary for OTA Provider
290290
291-
All binaries has the same SW version. To test OTA “zephyr-ota.bin” should have
291+
All binaries has the same SW version. To test OTA “metter.ota” should have
292292
higher SW version than base SW. Set CONFIG_CHIP_DEVICE_SOFTWARE_VERSION=2 in
293293
corresponding “prj.conf” configuration file.
294294
@@ -303,7 +303,7 @@ Usage of OTA:
303303
- Run the Linux OTA Provider with OTA image.
304304
305305
```
306-
./chip-ota-provider-app -f zephyr-ota.bin
306+
./chip-ota-provider-app -f metter.ota
307307
```
308308
309309
- Provision the Linux OTA Provider using chip-tool

‎examples/contact-sensor-app/telink/README.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -142,10 +142,10 @@ feature for another Telink example:
142142
143143
After build application with enabled OTA feature, use next binary files:
144144
145-
- zephyr.bin - main binary to flash PCB (Use at least 2MB PCB).
146-
- zephyr-ota.bin - binary for OTA Provider
145+
- merged.bin - main binary to flash PCB (Use at least 2MB PCB).
146+
- metter.ota - binary for OTA Provider
147147
148-
All binaries has the same SW version. To test OTA “zephyr-ota.bin” should have
148+
All binaries has the same SW version. To test OTA “metter.ota” should have
149149
higher SW version than base SW. Set CONFIG_CHIP_DEVICE_SOFTWARE_VERSION=2 in
150150
corresponding “prj.conf” configuration file.
151151
@@ -160,7 +160,7 @@ Usage of OTA:
160160
- Run the Linux OTA Provider with OTA image.
161161
162162
```
163-
./chip-ota-provider-app -f zephyr-ota.bin
163+
./chip-ota-provider-app -f metter.ota
164164
```
165165
166166
- Provision the Linux OTA Provider using chip-tool

‎examples/light-switch-app/telink/README.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -263,10 +263,10 @@ feature for another Telink example:
263263

264264
After build application with enabled OTA feature, use next binary files:
265265

266-
- zephyr.bin - main binary to flash PCB (Use at least 2MB PCB).
267-
- zephyr-ota.bin - binary for OTA Provider
266+
- merged.bin - main binary to flash PCB (Use at least 2MB PCB).
267+
- metter.ota - binary for OTA Provider
268268

269-
All binaries has the same SW version. To test OTA “zephyr-ota.bin” should have
269+
All binaries has the same SW version. To test OTA “metter.ota” should have
270270
higher SW version than base SW. Set CONFIG_CHIP_DEVICE_SOFTWARE_VERSION=2 in
271271
corresponding “prj.conf” configuration file.
272272

@@ -281,7 +281,7 @@ Usage of OTA:
281281
- Run the Linux OTA Provider with OTA image.
282282

283283
```
284-
./chip-ota-provider-app -f zephyr-ota.bin
284+
./chip-ota-provider-app -f metter.ota
285285
```
286286

287287
- Provision the Linux OTA Provider using chip-tool

‎examples/lighting-app/telink/README.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -204,10 +204,10 @@ feature for another Telink example:
204204
205205
After build application with enabled OTA feature, use next binary files:
206206
207-
- zephyr.bin - main binary to flash PCB (Use at least 2MB PCB).
208-
- zephyr-ota.bin - binary for OTA Provider
207+
- merged.bin - main binary to flash PCB (Use at least 2MB PCB).
208+
- metter.ota - binary for OTA Provider
209209
210-
All binaries has the same SW version. To test OTA “zephyr-ota.bin” should have
210+
All binaries has the same SW version. To test OTA “metter.ota” should have
211211
higher SW version than base SW. Set CONFIG_CHIP_DEVICE_SOFTWARE_VERSION=2 in
212212
corresponding “prj.conf” configuration file.
213213
@@ -222,7 +222,7 @@ Usage of OTA:
222222
- Run the Linux OTA Provider with OTA image.
223223
224224
```
225-
./chip-ota-provider-app -f zephyr-ota.bin
225+
./chip-ota-provider-app -f metter.ota
226226
```
227227
228228
- Provision the Linux OTA Provider using chip-tool

‎examples/lock-app/telink/README.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -145,10 +145,10 @@ feature for another Telink example:
145145
146146
After build application with enabled OTA feature, use next binary files:
147147
148-
- zephyr.bin - main binary to flash PCB (Use at least 2MB PCB).
149-
- zephyr-ota.bin - binary for OTA Provider
148+
- merged.bin - main binary to flash PCB (Use at least 2MB PCB).
149+
- metter.ota - binary for OTA Provider
150150
151-
All binaries has the same SW version. To test OTA “zephyr-ota.bin” should have
151+
All binaries has the same SW version. To test OTA “metter.ota” should have
152152
higher SW version than base SW. Set CONFIG_CHIP_DEVICE_SOFTWARE_VERSION=2 in
153153
corresponding “prj.conf” configuration file.
154154
@@ -163,7 +163,7 @@ Usage of OTA:
163163
- Run the Linux OTA Provider with OTA image.
164164
165165
```
166-
./chip-ota-provider-app -f zephyr-ota.bin
166+
./chip-ota-provider-app -f metter.ota
167167
```
168168
169169
- Provision the Linux OTA Provider using chip-tool

‎examples/ota-requestor-app/telink/README.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -134,10 +134,10 @@ feature for another Telink example:
134134
135135
After build application with enabled OTA feature, use next binary files:
136136
137-
- zephyr.bin - main binary to flash PCB (Use at least 2MB PCB).
138-
- zephyr-ota.bin - binary for OTA Provider
137+
- merged.bin - main binary to flash PCB (Use at least 2MB PCB).
138+
- metter.ota - binary for OTA Provider
139139
140-
All binaries has the same SW version. To test OTA “zephyr-ota.bin” should have
140+
All binaries has the same SW version. To test OTA “metter.ota” should have
141141
higher SW version than base SW. Set CONFIG_CHIP_DEVICE_SOFTWARE_VERSION=2 in
142142
corresponding “prj.conf” configuration file.
143143
@@ -152,7 +152,7 @@ Usage of OTA:
152152
- Run the Linux OTA Provider with OTA image.
153153
154154
```
155-
./chip-ota-provider-app -f zephyr-ota.bin
155+
./chip-ota-provider-app -f metter.ota
156156
```
157157
158158
- Provision the Linux OTA Provider using chip-tool

‎examples/pump-app/telink/README.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -146,10 +146,10 @@ feature for another Telink example:
146146
147147
After build application with enabled OTA feature, use next binary files:
148148
149-
- zephyr.bin - main binary to flash PCB (Use at least 2MB PCB).
150-
- zephyr-ota.bin - binary for OTA Provider
149+
- merged.bin - main binary to flash PCB (Use at least 2MB PCB).
150+
- metter.ota - binary for OTA Provider
151151
152-
All binaries has the same SW version. To test OTA “zephyr-ota.bin” should have
152+
All binaries has the same SW version. To test OTA “metter.ota” should have
153153
higher SW version than base SW. Set CONFIG_CHIP_DEVICE_SOFTWARE_VERSION=2 in
154154
corresponding “prj.conf” configuration file.
155155
@@ -164,7 +164,7 @@ Usage of OTA:
164164
- Run the Linux OTA Provider with OTA image.
165165
166166
```
167-
./chip-ota-provider-app -f zephyr-ota.bin
167+
./chip-ota-provider-app -f metter.ota
168168
```
169169
170170
- Provision the Linux OTA Provider using chip-tool

‎examples/pump-controller-app/telink/README.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -147,10 +147,10 @@ feature for another Telink example:
147147
148148
After build application with enabled OTA feature, use next binary files:
149149
150-
- zephyr.bin - main binary to flash PCB (Use at least 2MB PCB).
151-
- zephyr-ota.bin - binary for OTA Provider
150+
- merged.bin - main binary to flash PCB (Use at least 2MB PCB).
151+
- metter.ota - binary for OTA Provider
152152
153-
All binaries has the same SW version. To test OTA “zephyr-ota.bin” should have
153+
All binaries has the same SW version. To test OTA “metter.ota” should have
154154
higher SW version than base SW. Set CONFIG_CHIP_DEVICE_SOFTWARE_VERSION=2 in
155155
corresponding “prj.conf” configuration file.
156156
@@ -165,7 +165,7 @@ Usage of OTA:
165165
- Run the Linux OTA Provider with OTA image.
166166
167167
```
168-
./chip-ota-provider-app -f zephyr-ota.bin
168+
./chip-ota-provider-app -f metter.ota
169169
```
170170
171171
- Provision the Linux OTA Provider using chip-tool

‎examples/smoke-co-alarm-app/telink/README.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -144,10 +144,10 @@ feature for another Telink example:
144144
145145
After build application with enabled OTA feature, use next binary files:
146146
147-
- zephyr.bin - main binary to flash PCB (Use at least 2MB PCB).
148-
- zephyr-ota.bin - binary for OTA Provider
147+
- merged.bin - main binary to flash PCB (Use at least 2MB PCB).
148+
- metter.ota - binary for OTA Provider
149149
150-
All binaries has the same SW version. To test OTA “zephyr-ota.bin” should have
150+
All binaries has the same SW version. To test OTA “metter.ota” should have
151151
higher SW version than base SW. Set CONFIG_CHIP_DEVICE_SOFTWARE_VERSION=2 in
152152
corresponding “prj.conf” configuration file.
153153
@@ -162,7 +162,7 @@ Usage of OTA:
162162
- Run the Linux OTA Provider with OTA image.
163163
164164
```
165-
./chip-ota-provider-app -f zephyr-ota.bin
165+
./chip-ota-provider-app -f metter.ota
166166
```
167167
168168
- Provision the Linux OTA Provider using chip-tool

‎examples/temperature-measurement-app/telink/README.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -127,10 +127,10 @@ feature for another Telink example:
127127

128128
After build application with enabled OTA feature, use next binary files:
129129

130-
- zephyr.bin - main binary to flash PCB (Use at least 2MB PCB).
131-
- zephyr-ota.bin - binary for OTA Provider
130+
- merged.bin - main binary to flash PCB (Use at least 2MB PCB).
131+
- metter.ota - binary for OTA Provider
132132

133-
All binaries has the same SW version. To test OTA “zephyr-ota.bin” should have
133+
All binaries has the same SW version. To test OTA “metter.ota” should have
134134
higher SW version than base SW. Set CONFIG_CHIP_DEVICE_SOFTWARE_VERSION=2 in
135135
corresponding “prj.conf” configuration file.
136136

@@ -145,7 +145,7 @@ Usage of OTA:
145145
- Run the Linux OTA Provider with OTA image.
146146

147147
```
148-
./chip-ota-provider-app -f zephyr-ota.bin
148+
./chip-ota-provider-app -f metter.ota
149149
```
150150

151151
- Provision the Linux OTA Provider using chip-tool

‎examples/thermostat/telink/README.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -138,10 +138,10 @@ feature for another Telink example:
138138
139139
After build application with enabled OTA feature, use next binary files:
140140
141-
- zephyr.bin - main binary to flash PCB (Use at least 2MB PCB).
142-
- zephyr-ota.bin - binary for OTA Provider
141+
- merged.bin - main binary to flash PCB (Use at least 2MB PCB).
142+
- metter.ota - binary for OTA Provider
143143
144-
All binaries has the same SW version. To test OTA “zephyr-ota.bin” should have
144+
All binaries has the same SW version. To test OTA “metter.ota” should have
145145
higher SW version than base SW. Set CONFIG_CHIP_DEVICE_SOFTWARE_VERSION=2 in
146146
corresponding “prj.conf” configuration file.
147147
@@ -156,7 +156,7 @@ Usage of OTA:
156156
- Run the Linux OTA Provider with OTA image.
157157
158158
```
159-
./chip-ota-provider-app -f zephyr-ota.bin
159+
./chip-ota-provider-app -f metter.ota
160160
```
161161
162162
- Provision the Linux OTA Provider using chip-tool

‎examples/window-app/telink/README.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -209,10 +209,10 @@ feature for another Telink example:
209209
210210
After build application with enabled OTA feature, use next binary files:
211211
212-
- zephyr.bin - main binary to flash PCB (Use at least 2MB PCB).
213-
- zephyr-ota.bin - binary for OTA Provider
212+
- merged.bin - main binary to flash PCB (Use at least 2MB PCB).
213+
- metter.ota - binary for OTA Provider
214214
215-
All binaries has the same SW version. To test OTA “zephyr-ota.bin” should have
215+
All binaries has the same SW version. To test OTA “metter.ota” should have
216216
higher SW version than base SW. Set CONFIG_CHIP_DEVICE_SOFTWARE_VERSION=2 in
217217
corresponding “prj.conf” configuration file.
218218
@@ -227,7 +227,7 @@ Usage of OTA:
227227
- Run the Linux OTA Provider with OTA image.
228228
229229
```
230-
./chip-ota-provider-app -f zephyr-ota.bin
230+
./chip-ota-provider-app -f metter.ota
231231
```
232232
233233
- Provision the Linux OTA Provider using chip-tool

0 commit comments

Comments
 (0)