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
Copy file name to clipboardExpand all lines: README.md
+10-7Lines changed: 10 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
# DJI Onboard SDK (OSDK) 4.0.0
1
+
# DJI Onboard SDK (OSDK) 4.0.1
2
2
3
3
[](https://gitter.im/dji-sdk/Onboard-SDK?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
4
4
@@ -7,6 +7,9 @@
7
7
The DJI Onboard SDK allows you to connect your own Onboard Computer to a [supported](https://developer.dji.com/onboard-sdk/documentation/purchaseguide/hardware.html) DJI vehicle or flight controller using a serial port (TTL UART). For full documentation, please visit the [DJI Developer Documentation](https://developer.dji.com/onboard-sdk/documentation/). Documentation regarding the code can be found in the [OSDK API Reference](https://developer.dji.com/onboard-api-reference/index.html) section of the developer's website.
8
8
9
9
## Latest Release
10
+
OSDK 4.0.1 was released on 21 August 2020. This version mainly fixes OSDK 4.0.0 issues, such as camera stream related problems, download function optimization, MOP optimization, waypoint 2.0 problems repair, etc. At the same time, we also add an automatic code porting script to assist the porting of FreeRTOS.
11
+
12
+
## Last Major Release
10
13
OSDK 4.0.0 was released on 8 May 2019. New APIs about flight controller such as home point setting, confirm landing, some function switches are supported in the version. For the payload device, more APIs about camera functions and parameters are added in the version. Please see the [release notes](https://developer.dji.com/onboard-sdk/downloads/) for more information.
11
14
12
15
## Firmware Compatibility
@@ -22,18 +25,18 @@ This chart shows the latest firmware that were available and are supported at th
Copy file name to clipboardExpand all lines: debian/README.md
+10-5Lines changed: 10 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,9 +1,11 @@
1
-
3# Packaging Onboard-SDK-4.0
1
+
# Packaging Onboard-SDK-4.0
2
2
3
3
* The goal is to make as few custom changes to this repository as possible.
4
4
* Consider making custom changes to one of our repos that extends this library.
5
5
* We forked this repository so we could provide debian binary packages for easy and consistent distributions.
6
6
7
+
Updating from DJI's origin is encouraged. Branch from our master, then pull from their tag that you wish to merge.
8
+
7
9
Changes are currently found under two directories introduced by AM:
8
10
9
11
* debian/
@@ -25,13 +27,16 @@ Let's keep it that way.
25
27
26
28
### ARM 64 Builder
27
29
28
-
We provide self hosted runners to build our ARM binaries, however, this can cause a [security threat](https://help.github.com/en/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories).
30
+
We provide self hosted runners to build our AMD and ARM binaries, however, this can cause a [security threat](https://help.github.com/en/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories).
29
31
For this reason, we only bring up the self hosted runner manually when builds need to happen, which should be rare.
30
32
Organization action runners will not satisfy requirements since Github restricts such from the Org level, but allows at the repo level where we can apply granualar control.
1. You should see `√ Connected to GitHub` and `Listening for Jobs`
35
-
1. You should see `arm-builder` available in the [repo's actions](https://github.com/AutoModality/Onboard-SDK-4.0/settings/actions)
37
+
1. You should see `flops2` available in the [repo's actions](https://github.com/AutoModality/Onboard-SDK-4.0/settings/actions)
36
38
1. Any queues actions should be processed.
37
39
40
+
Repeat the steps above with `arm-builder-2`.
41
+
42
+
See [Github Actions Wiki](https://automodality.atlassian.net/wiki/spaces/AMROS/pages/758382915/Continuous+Integration+with+Github+Actions#FLOPS-AMD-Builders) for more information about builders.
0 commit comments