Changes for page Armbian OS instruction

Last modified by Kilight Cao on 2023/09/25 09:20
<
From version < 95.3 >
edited by Xiaoling
on 2023/03/28 08:47
To version < 83.1 >
edited by Xiaoye
on 2022/11/12 15:47
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Xiaoye
Content
... ... @@ -15,9 +15,6 @@
15 15  * LPS8v2
16 16  * MS20
17 17  
18 -(% style="display:none" %)
19 -
20 -
21 21  = 2.  Development Guide =
22 22  
23 23  
... ... @@ -24,9 +24,11 @@
24 24  For advanced users to develop Driver/ Linux etc.
25 25  
26 26  
24 +
27 27  == 2.1  How to recompile LoRaWAN Concentrator Driver ( dragino-fwd package). ==
28 28  
29 29  
28 +
30 30  === (% style="color:blue" %)**Step 1. Clone dragino-fwd package**(%%) ===
31 31  
32 32  
... ... @@ -43,6 +43,7 @@
43 43  [[image:image-20220527151010-1.png]]
44 44  
45 45  
45 +
46 46  === (% style="color:blue" %)**Step 2. Compile dragino_fwd**(%%) ===
47 47  
48 48  
... ... @@ -62,6 +62,7 @@
62 62  [[image:image-20220527154311-4.png||height="385" width="773"]]
63 63  
64 64  
65 +
65 65  === (% style="color:blue" %)**Step 3. Install the dragino_fwd**(%%) ===
66 66  
67 67  
... ... @@ -73,6 +73,7 @@
73 73  [[image:image-20220527154811-5.png]]
74 74  
75 75  
77 +
76 76  === (% style="color:blue" %)**Step 4. Test**(%%) ===
77 77  
78 78  
... ... @@ -91,10 +91,13 @@
91 91  (% style="background-color:yellow; color:green" %)**systemctl stop draginofwd**
92 92  
93 93  
96 +
94 94  == 2.2  How to clone Complete OS on the EMMC to SD card ==
95 95  
99 +
96 96  == 2.3  How to flash SD card to (eMMC) device's built-in Memory ==
97 97  
102 +
98 98  === 2.3.1 Prepare an SD card with OS ===
99 99  
100 100  
... ... @@ -158,6 +158,7 @@
158 158  (% style="color:red" %)**Note: After the flash is complete, power off the device and then remove the SD card.**
159 159  
160 160  
166 +
161 161  == 2.4 Default Built Version ==
162 162  
163 163  
... ... @@ -164,9 +164,10 @@
164 164  [[image:image-20220902155621-1.png]]
165 165  
166 166  
167 -== 2.5 How to upgrade the nodejs version to the latest. ==
168 168  
174 +== 2.5: How to upgrade the nodejs version to the latest. ==
169 169  
176 +
170 170  By default, the nodejs uses the pre-install version v12 which is due to Debian the ultra-stable via ultra-old.
171 171  
172 172  [[image:image-20221112145029-2.png]]
... ... @@ -220,203 +220,12 @@
220 220  )))
221 221  
222 222  
223 -== 2.6 How to install Grafana and influxdb ==
230 += 3. Package Maintain Note =
224 224  
225 225  
226 -=== **Grafana:** ===
227 -
228 -
229 -(% class="box infomessage" %)
230 -(((
231 -curl https:~/~/packages.grafana.com/gpg.key | gpg ~-~-dearmor | sudo tee /usr/share/keyrings/grafana-archive-keyrings.gpg >/dev/null
232 -echo "deb [signed-by=/usr/share/keyrings/grafana-archive-keyrings.gpg] https:~/~/packages.grafana.com/oss/deb stable main" | sudo tee /etc/apt/sources.list.d/grafana.list
233 -apt update && apt install grafana
234 -)))
235 -
236 -
237 -Check the running status:
238 -
239 -
240 -(% class="box infomessage" %)
241 -(((
242 -systemctl status grafana-server
243 -)))
244 -
245 -
246 -configuration path:
247 -
248 -
249 -(% class="box infomessage" %)
250 -(((
251 -/etc/grafana/grafana.ini
252 -)))
253 -
254 -
255 -=== **Influxdb:** ===
256 -
257 -
258 -(% class="box infomessage" %)
259 -(((
260 -curl https:~/~/repos.influxdata.com/influxdb.key | gpg ~-~-dearmor | sudo tee /usr/share/keyrings/influxdb-archive-keyring.gpg >/dev/null
261 -echo "deb [signed-by=/usr/share/keyrings/influxdb-archive-keyring.gpg] https:~/~/repos.influxdata.com/debian $(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/influxdb.list
262 -apt update && apt install influxdb
263 -)))
264 -
265 -
266 -Check the running status:
267 -
268 -
269 -(% class="box infomessage" %)
270 -(((
271 -systemctl status influxdb
272 -)))
273 -
274 -
275 -configuration path:
276 -
277 -
278 -(% class="box infomessage" %)
279 -(((
280 -/etc/influxdb/influxdb.conf
281 -)))
282 -
283 -
284 -== 2.7 How to install BACnet ==
285 -
286 -
287 -(% class="box infomessage" %)
288 -(((
289 -wget [[http:~~/~~/dragino.vicp.io:6080/bacnet/dragino-bacnet-apps-hp0c-2023-03-01.deb>>url:http://dragino.vicp.io:6080/bacnet/dragino-bacnet-apps-hp0c-2023-03-01.deb]]
290 -dpkg -i dragino-bacnet-apps-hp0c-2023-03-01.deb
291 -)))
292 -
293 -[[image:image-20230327152105-1.png||height="163" width="933"]]
294 -
295 -
296 -=== 2.7.1 Configure BACnet ===
297 -
298 -
299 -After BACnet is installed, run commands to modify BACnet configurations
300 -
301 -(% style="color:red" %)**Note: device_port and bacnet_ip_port are not set to the same**
302 -
303 -(% class="box infomessage" %)
304 -(((
305 -nano /etc/config/bacnet
306 -)))
307 -
308 -Examples:
309 -
310 -(% class="box infomessage" %)
311 -(((
312 -config settings 'general'
313 - option bacnet_ip '10.130.2.80'  #The IP address of the BACnetIP network, here basically the same IP as the bbmd address below
314 - option bacnet_ip_port '47808'  #As with bbmd_port, the purpose of this is to register a Bacnet Server application as a bbmd registration server
315 - option bbmd_address '10.130.2.80'  #bbmd is the BACnet registration server. Only one bbmd server is required in the same ip network
316 - option bbmd_port '47808'  #In general, 47808 is used as the default port
317 - option bacnet_dev_count '2'  #Here is the number of BACnet devices that need to be simulated, if the number is 2, then the following settings must have 2, which are bacdev_1, bacdev_2
318 -
319 -config settings 'bacdev_1'
320 - option device_name 'LHT65N-1'  #The identification name of the bacnet device
321 - option device_id '10001'  #The unique identification code in the same network segment of BACnet,Scope is(1 - 4194302)
322 - option device_port '47912'  #The IP port occupied by Bacnet when it starts, Scope is (1024 - 65535)
323 -
324 -config settings 'bacdev_2'
325 - option device_name 'LHT65N-2'
326 - option device_id '10002'
327 - option device_port '47913'  
328 -)))
329 -
330 -
331 -=== 2.7.2 Run BACnet ===
332 -
333 -
334 -After the configuration is complete, run the following command to start BACnet, The following are two ways to run BACnet:
335 -
336 -(1)With /etc/config/bacnet configuration, and to run the registration server on the current machine, start it with the following command (configure the /etc/config/bacnet file correctly):
337 -
338 -(% class="box infomessage" %)
339 -(((
340 -bacserver -c -s
341 -)))
342 -
343 -(2)Without /etc/config/bacnet, and to run the registration server on the current machine, start it with the following command:
344 -
345 -(% class="box infomessage" %)
346 -(((
347 -bacserver -s -a 10.130.2.80 -p 47808
348 -)))
349 -
350 -This command simulates two devices, with device IDs 47910 and 47911
351 -
352 -Enter bacserver -h to output help
353 -
354 -(% class="box infomessage" %)
355 -(((
356 -bacserver -h
357 -)))
358 -
359 -[[image:image-20230327154700-3.png]]
360 -
361 -
362 -=== 2.7.3 Read devices and modify devices ===
363 -
364 -
365 -Enter baccli -h to output help
366 -
367 -(% class="box infomessage" %)
368 -(((
369 -baccli -h
370 -)))
371 -
372 -[[image:image-20230327165836-1.png]]
373 -
374 -Examples:
375 -
376 -(1)List the current Bacnet devices:
377 -
378 -(% class="box infomessage" %)
379 -(((
380 -baccli -l -a
381 -)))
382 -
383 -[[image:image-20230327174537-3.png]]
384 -
385 -(2)List device information based on device ID:
386 -
387 -(% class="box infomessage" %)
388 -(((
389 -baccli -l -i id
390 -)))
391 -
392 -[[image:image-20230327174556-4.png]]
393 -
394 -(3)List the device details by device ID:
395 -
396 -(% class="box infomessage" %)
397 -(((
398 -baccli -l -v -i id
399 -)))
400 -
401 -(4) Modify the specified attribute value based on the device ID:
402 -
403 -(% class="box infomessage" %)
404 -(((
405 -baccli -i id -p prop -w value
406 -)))
407 -
408 -[[image:image-20230327174853-5.png]]
409 -
410 -
411 -The user can check the data of the device by using the **[[yabe BACnet tool>>https://sourceforge.net/projects/yetanotherbacnetexplorer/]]**
412 -
413 -[[image:image-20230327171824-2.png]]
414 -
415 -= =
416 -
417 -
418 418  == 3.1 Default Package Maintain System ==
419 419  
235 +
420 420  === 3.1.1 How Package-Auto-Update works? ===
421 421  
422 422  
... ... @@ -464,6 +464,7 @@
464 464  [[image:1661305258501-636.png]]
465 465  
466 466  
283 +
467 467  === 3.1.2 How to manually update core packages? ===
468 468  
469 469  
... ... @@ -473,6 +473,7 @@
473 473  [[image:1661305328295-218.png]]
474 474  
475 475  
293 +
476 476  === 3.1.3 How to manually update other packages? ===
477 477  
478 478  
... ... @@ -479,8 +479,10 @@
479 479  For the other packages, you have to access the device's CLI to do it via the apt command.
480 480  
481 481  
300 +
482 482  == 3.2 Set up a 3^^rd^^ party package maintain server ==
483 483  
303 +
484 484  === 3.2.1 Overview ===
485 485  
486 486  
... ... @@ -487,6 +487,7 @@
487 487  Customers can use their own package maintenance system instead of using the default one from Dragino. They need to set up a package maintenance system for Debian. Lots of instructions are available in Internet, below is a reference instruction.
488 488  
489 489  
310 +
490 490  === 3.2.2 Install Apache2 HTTP server ===
491 491  
492 492  
... ... @@ -493,6 +493,7 @@
493 493  (% style="background-color:yellow; color:green" %)**apt install apache2**
494 494  
495 495  
317 +
496 496  === 3.2.3 Creating Package Directories ===
497 497  
498 498  
... ... @@ -529,6 +529,7 @@
529 529   └── dragino   ~-~-> (% style="background-color:yellow; color:green" %)**This is the directory to store the packages. User can change it to other name.**
530 530  
531 531  
354 +
532 532  === 3.2.4 Get deb packages ===
533 533  
534 534  
... ... @@ -542,6 +542,7 @@
542 542  **~ (% style="background-color:yellow; color:green" %)cp ./testing-0808.deb /var/www/html/debian/release/pool/main/d/dragino/(%%)**
543 543  
544 544  
368 +
545 545  === 3.2.5 Generate Package Index file ===
546 546  
547 547  
... ... @@ -555,6 +555,7 @@
555 555  (% style="color:red" %)**Note: Every time a package has been update, above comments need to be executed in the server to get the up-to-date package list.**
556 556  
557 557  
382 +
558 558  === 3.2.6 Generate Release file ===
559 559  
560 560  
... ... @@ -571,9 +571,11 @@
571 571  (% style="background-color:yellow; color:green" %)**./generate-release.sh > Release**
572 572  
573 573  
399 +
574 574  === 3.2.7 Sign the Release file with gpg and generating Inrelease file ===
575 575  
576 576  
403 +
577 577  ==== (% style="color:blue" %)**Make sure auto-update server has gnupg**(%%) ====
578 578  
579 579  
... ... @@ -656,6 +656,7 @@
656 656  [[image:1661306420449-569.png]]
657 657  
658 658  
486 +
659 659  === 3.2.9 Configure the gateway's auto-upgrade rules ===
660 660  
661 661  
... ... @@ -681,6 +681,3 @@
681 681  
682 682  
683 683  [[image:1661306487761-768.png]]
684 -
685 -
686 -
image-20230327152105-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -27.5 KB
Content
image-20230327152431-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -47.5 KB
Content
image-20230327154700-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -26.7 KB
Content
image-20230327165836-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -17.1 KB
Content
image-20230327171824-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -46.1 KB
Content
image-20230327174537-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -8.8 KB
Content
image-20230327174556-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -16.0 KB
Content
image-20230327174853-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -20.0 KB
Content

Applications

Navigation

Copyright ©2010-2022 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0