- API access guide
- Common Error Codes
- FAQ
- User-related
- System control-related
- Screen control-related
- Receiving card-related
- Obtain receiving card connection information
- Obtain receiving card monitoring information
- Obtain basic information of the receiving card
- Configure the screen via receiving card configuration (send .rcfgx file)
- Configure the screen via receiving card configuration (send .scr file)
- Upgrade the receiving card
- Obtain the receiving card upgrade progress
- Send Card-related
- Obtain screen brightnessGET
- Set screen brightnessPOST
- Obtain screen statusGET
- Set screen statusPOST
- Obtain screen-on/off schedulesGET
- Set screen-on/off schedulesPOST
- Set brightness adjustment schedulesPOST
- Obtain brightness adjustment schedulesGET
- General capabilities
- Serial port control
- Board relays
Check local upgrade status
Developing
GET
/terminal/emergency/v1/device/upgrade/status
Last modified:2024-12-13 09:16:06
Request
Header Params
Authorization
string
optional
Default:
1724333189506EO5Zqpduu4+azwYYXMJJhg==
Request samples
Shell
JavaScript
Java
Swift
Go
PHP
Python
HTTP
C
C#
Objective-C
Ruby
OCaml
Dart
R
Request Request Example
Shell
JavaScript
Java
Swift
curl --location --request GET 'https://192.168.0.10:16674/terminal/emergency/v1/device/upgrade/status' \
--header 'Authorization: 1724333189506EO5Zqpduu4+azwYYXMJJhg=='
Responses
🟢200成功
application/json
Body
code
integer
required
0: Successful, Other: Failed
message
string
required
data
object
required
status
integer
required
0: The business is normal.
1001: Unsupported platform type
1002: Unsupported product
1003: Incorrect upgrade package version information: The format is incorrect or it cannot be parsed correctly.
1004: Incorrect FPGA upgrade path
1005: FPGA upgrade error
1006: During the upgrade of FPGA, the current device model is not supported.
1007: The upgrade version is too early.
1008: The upgrade package parameter information is missing.
1009: The upgrade package does not exist.
1010: An error occurred during decompression.
1012: Whether the upgrade name base64 and identifier values are consistent.
1013: Insufficient cache space
1015: Upgrade package decompression failed.
1016: The playload.bin file in the upgrade package cannot be found.
1017: Verify payload.bin file.
1018: Incorrect upgrade path
1019: Upgrade package download failed - general
1020: Upgrade package download failed - network error
1021: Upgrade in progress
1022: Upgrade package verification failed. In other cases, an error code is displayed.
1023: No matching upgrade package
2001: Upgrade failed
2004: Failed to copy the system file.
2005: Failed to set boot partition.
2006: Unmatched payload
2007: Unable to start upgrade.
2008: Unable to start kernel.
2009: Failed to obtain payload.
2010: payload hash does not match.
2011: payload size does not match.
2012: Failed to verify payload.
2051: payload timestamp verification failed.
2052: Update successful but (A/B) partition not activated.
2060: Insufficient remaining space
2061: payload corrupted
stage
integer
required
0: init;
1: download;
2: upgrade;
3: reboot;
4: recovery; //The last stage that can be found in Android 5.1.
5: verity //Verify the upgrade package.
Note: Three products (T1-4G, T2-4G and TCC70) based on Android 5.1+RK3128 platform do not support upgrade progress reporting. The last perceptible stage is recovery.
progress
integer
required
Example
{
"code": 0,
"message": "",
"data": {
"status": 0,
"stage": 2,
"progress": 50
}
}