├── resources ├── beaglev.jpeg ├── licheepi4a.png ├── beaglev_aosp.png ├── beaglev_connect.png ├── licheepi4a_aosp.png └── licheepi4a_connect.png ├── LICENSE └── README.md /resources/beaglev.jpeg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/XUANTIE-RV/riscv-aosp/HEAD/resources/beaglev.jpeg -------------------------------------------------------------------------------- /resources/licheepi4a.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/XUANTIE-RV/riscv-aosp/HEAD/resources/licheepi4a.png -------------------------------------------------------------------------------- /resources/beaglev_aosp.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/XUANTIE-RV/riscv-aosp/HEAD/resources/beaglev_aosp.png -------------------------------------------------------------------------------- /resources/beaglev_connect.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/XUANTIE-RV/riscv-aosp/HEAD/resources/beaglev_connect.png -------------------------------------------------------------------------------- /resources/licheepi4a_aosp.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/XUANTIE-RV/riscv-aosp/HEAD/resources/licheepi4a_aosp.png -------------------------------------------------------------------------------- /resources/licheepi4a_connect.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/XUANTIE-RV/riscv-aosp/HEAD/resources/licheepi4a_connect.png -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | Apache License 2 | -------------- 3 | 4 | Version 2.0, January 2004 5 | http://www.apache.org/licenses/ 6 | 7 | TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 8 | 9 | 1. Definitions. 10 | 11 | "License" shall mean the terms and conditions for use, reproduction, 12 | and distribution as defined by Sections 1 through 9 of this document. 13 | 14 | "Licensor" shall mean the copyright owner or entity authorized by 15 | the copyright owner that is granting the License. 16 | 17 | "Legal Entity" shall mean the union of the acting entity and all 18 | other entities that control, are controlled by, or are under common 19 | control with that entity. For the purposes of this definition, 20 | "control" means (i) the power, direct or indirect, to cause the 21 | direction or management of such entity, whether by contract or 22 | otherwise, or (ii) ownership of fifty percent (50%) or more of the 23 | outstanding shares, or (iii) beneficial ownership of such entity. 24 | 25 | "You" (or "Your") shall mean an individual or Legal Entity 26 | exercising permissions granted by this License. 27 | 28 | "Source" form shall mean the preferred form for making modifications, 29 | including but not limited to software source code, documentation 30 | source, and configuration files. 31 | 32 | "Object" form shall mean any form resulting from mechanical 33 | transformation or translation of a Source form, including but 34 | not limited to compiled object code, generated documentation, 35 | and conversions to other media types. 36 | 37 | "Work" shall mean the work of authorship, whether in Source or 38 | Object form, made available under the License, as indicated by a 39 | copyright notice that is included in or attached to the work 40 | (an example is provided in the Appendix below). 41 | 42 | "Derivative Works" shall mean any work, whether in Source or Object 43 | form, that is based on (or derived from) the Work and for which the 44 | editorial revisions, annotations, elaborations, or other modifications 45 | represent, as a whole, an original work of authorship. For the purposes 46 | of this License, Derivative Works shall not include works that remain 47 | separable from, or merely link (or bind by name) to the interfaces of, 48 | the Work and Derivative Works thereof. 49 | 50 | "Contribution" shall mean any work of authorship, including 51 | the original version of the Work and any modifications or additions 52 | to that Work or Derivative Works thereof, that is intentionally 53 | submitted to Licensor for inclusion in the Work by the copyright owner 54 | or by an individual or Legal Entity authorized to submit on behalf of 55 | the copyright owner. For the purposes of this definition, "submitted" 56 | means any form of electronic, verbal, or written communication sent 57 | to the Licensor or its representatives, including but not limited to 58 | communication on electronic mailing lists, source code control systems, 59 | and issue tracking systems that are managed by, or on behalf of, the 60 | Licensor for the purpose of discussing and improving the Work, but 61 | excluding communication that is conspicuously marked or otherwise 62 | designated in writing by the copyright owner as "Not a Contribution." 63 | 64 | "Contributor" shall mean Licensor and any individual or Legal Entity 65 | on behalf of whom a Contribution has been received by Licensor and 66 | subsequently incorporated within the Work. 67 | 68 | 2. Grant of Copyright License. Subject to the terms and conditions of 69 | this License, each Contributor hereby grants to You a perpetual, 70 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 71 | copyright license to reproduce, prepare Derivative Works of, 72 | publicly display, publicly perform, sublicense, and distribute the 73 | Work and such Derivative Works in Source or Object form. 74 | 75 | 3. Grant of Patent License. Subject to the terms and conditions of 76 | this License, each Contributor hereby grants to You a perpetual, 77 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 78 | (except as stated in this section) patent license to make, have made, 79 | use, offer to sell, sell, import, and otherwise transfer the Work, 80 | where such license applies only to those patent claims licensable 81 | by such Contributor that are necessarily infringed by their 82 | Contribution(s) alone or by combination of their Contribution(s) 83 | with the Work to which such Contribution(s) was submitted. If You 84 | institute patent litigation against any entity (including a 85 | cross-claim or counterclaim in a lawsuit) alleging that the Work 86 | or a Contribution incorporated within the Work constitutes direct 87 | or contributory patent infringement, then any patent licenses 88 | granted to You under this License for that Work shall terminate 89 | as of the date such litigation is filed. 90 | 91 | 4. Redistribution. You may reproduce and distribute copies of the 92 | Work or Derivative Works thereof in any medium, with or without 93 | modifications, and in Source or Object form, provided that You 94 | meet the following conditions: 95 | 96 | (a) You must give any other recipients of the Work or 97 | Derivative Works a copy of this License; and 98 | 99 | (b) You must cause any modified files to carry prominent notices 100 | stating that You changed the files; and 101 | 102 | (c) You must retain, in the Source form of any Derivative Works 103 | that You distribute, all copyright, patent, trademark, and 104 | attribution notices from the Source form of the Work, 105 | excluding those notices that do not pertain to any part of 106 | the Derivative Works; and 107 | 108 | (d) If the Work includes a "NOTICE" text file as part of its 109 | distribution, then any Derivative Works that You distribute must 110 | include a readable copy of the attribution notices contained 111 | within such NOTICE file, excluding those notices that do not 112 | pertain to any part of the Derivative Works, in at least one 113 | of the following places: within a NOTICE text file distributed 114 | as part of the Derivative Works; within the Source form or 115 | documentation, if provided along with the Derivative Works; or, 116 | within a display generated by the Derivative Works, if and 117 | wherever such third-party notices normally appear. The contents 118 | of the NOTICE file are for informational purposes only and 119 | do not modify the License. You may add Your own attribution 120 | notices within Derivative Works that You distribute, alongside 121 | or as an addendum to the NOTICE text from the Work, provided 122 | that such additional attribution notices cannot be construed 123 | as modifying the License. 124 | 125 | You may add Your own copyright statement to Your modifications and 126 | may provide additional or different license terms and conditions 127 | for use, reproduction, or distribution of Your modifications, or 128 | for any such Derivative Works as a whole, provided Your use, 129 | reproduction, and distribution of the Work otherwise complies with 130 | the conditions stated in this License. 131 | 132 | 5. Submission of Contributions. Unless You explicitly state otherwise, 133 | any Contribution intentionally submitted for inclusion in the Work 134 | by You to the Licensor shall be under the terms and conditions of 135 | this License, without any additional terms or conditions. 136 | Notwithstanding the above, nothing herein shall supersede or modify 137 | the terms of any separate license agreement you may have executed 138 | with Licensor regarding such Contributions. 139 | 140 | 6. Trademarks. This License does not grant permission to use the trade 141 | names, trademarks, service marks, or product names of the Licensor, 142 | except as required for reasonable and customary use in describing the 143 | origin of the Work and reproducing the content of the NOTICE file. 144 | 145 | 7. Disclaimer of Warranty. Unless required by applicable law or 146 | agreed to in writing, Licensor provides the Work (and each 147 | Contributor provides its Contributions) on an "AS IS" BASIS, 148 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or 149 | implied, including, without limitation, any warranties or conditions 150 | of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A 151 | PARTICULAR PURPOSE. You are solely responsible for determining the 152 | appropriateness of using or redistributing the Work and assume any 153 | risks associated with Your exercise of permissions under this License. 154 | 155 | 8. Limitation of Liability. In no event and under no legal theory, 156 | whether in tort (including negligence), contract, or otherwise, 157 | unless required by applicable law (such as deliberate and grossly 158 | negligent acts) or agreed to in writing, shall any Contributor be 159 | liable to You for damages, including any direct, indirect, special, 160 | incidental, or consequential damages of any character arising as a 161 | result of this License or out of the use or inability to use the 162 | Work (including but not limited to damages for loss of goodwill, 163 | work stoppage, computer failure or malfunction, or any and all 164 | other commercial damages or losses), even if such Contributor 165 | has been advised of the possibility of such damages. 166 | 167 | 9. Accepting Warranty or Additional Liability. While redistributing 168 | the Work or Derivative Works thereof, You may choose to offer, 169 | and charge a fee for, acceptance of support, warranty, indemnity, 170 | or other liability obligations and/or rights consistent with this 171 | License. However, in accepting such obligations, You may act only 172 | on Your own behalf and on Your sole responsibility, not on behalf 173 | of any other Contributor, and only if You agree to indemnify, 174 | defend, and hold each Contributor harmless for any liability 175 | incurred by, or claims asserted against, such Contributor by reason 176 | of your accepting any such warranty or additional liability. 177 | 178 | END OF TERMS AND CONDITIONS 179 | 180 | APPENDIX: How to apply the Apache License to your work. 181 | 182 | To apply the Apache License to your work, attach the following 183 | boilerplate notice, with the fields enclosed by brackets "{}" 184 | replaced with your own identifying information. (Don't include 185 | the brackets!) The text should be enclosed in the appropriate 186 | comment syntax for the file format. We also recommend that a 187 | file or class name and description of purpose be included on the 188 | same "printed page" as the copyright notice for easier 189 | identification within third-party archives. 190 | 191 | Copyright {yyyy} {name of copyright owner} 192 | 193 | Licensed under the Apache License, Version 2.0 (the "License"); 194 | you may not use this file except in compliance with the License. 195 | You may obtain a copy of the License at 196 | 197 | http://www.apache.org/licenses/LICENSE-2.0 198 | 199 | Unless required by applicable law or agreed to in writing, software 200 | distributed under the License is distributed on an "AS IS" BASIS, 201 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 202 | See the License for the specific language governing permissions and 203 | limitations under the License. -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # XuanTie Android 2 | 3 | This repository is maintained by Damo Academy Xuantie Team for the support of the Android Open Source Project (AOSP) on XuanTie CPU based development boards. It mainly includes BSP configuration, peripheral HAL layer, kernel, u-boot, and pre-compiled component support for the development boards. Other components can be directly pulled from the upstream AOSP repository. Currently, the repository maintains the relevant support for BeagleV Ahead and Lichee Pi 4A development boards based on the [TH1520](https://xrvm.com/soc-details?id=4095189586886594560) SoC prototype. 4 | 5 | Chinese page: 6 | 7 | https://gitee.com/thead-android/thead-android/blob/master/README.md 8 | 9 | The historical versions (RVB-ICE support) of this repository have been backed up to the branch: 10 | 11 | https://github.com/XUANTIE-RV/riscv-aosp/tree/back_up 12 | 13 | ## Development boards 14 | ### BeagleV Ahead 15 | BeagleV Ahead is a development board product launched by Beagle board, which supports multiple operating systems such as Android, Debian, Ubuntu, etc. The development board integrates TH1520 SoC, which includes a quad-core Xuan Tie C910 processor running at 1.85G and an NPU with 4TOPS computing power. It has a built-in GPU that supports OpenGL ES, OpenCL, and Vulkan, and features various device interfaces such as USB, Wi-Fi/BT, Ethernet, HDMI, MIPI CSI/DSI, etc. It can be used in AI edge computing applications such as video conferencing all-in-one machines, face recognition attendance access control, medical imaging, etc. 16 | ![beaglev](https://github.com/T-head-Semi/riscv-aosp/blob/main/resources/beaglev.jpeg?raw=true) 17 | 18 | Figure 1. BeagleV Ahead 19 | 20 | For more information, please visit the Beagleboard documentation page: 21 | 22 | https://beaglev-ahead.beagleboard.io/docs/latest/boards/beaglev/ahead/index.html 23 | 24 | ### Lichee Pi 4A EVB 25 | Lichee Pi 4A is a development board product launched by Sipeed, which supports multiple operating systems such as Android, Debian, OpenWrt, etc. The development board integrates TH1520 SoC, which includes a quad-core Xuan Tie C910 processor running at 1.85G and an NPU with 4TOPS computing power. It has a built-in GPU that supports OpenGL ES, OpenCL, and Vulkan, and features various device interfaces such as USB, Wi-Fi/BT, Ethernet, HDMI, MIPI CSI/DSI, etc. It can be used in AI edge computing applications such as video conferencing all-in-one machines, face recognition attendance access control, medical imaging, etc. 26 | ![licheepi4a](https://github.com/XUANTIE-RV/riscv-aosp/blob/main/resources/licheepi4a.png?raw=true) 27 | 28 | Figure 2. Lichee Pi 4A EVB 29 | 30 | For more information, please visit the Sipeed Wiki page: 31 | https://wiki.sipeed.com/licheepi4a 32 | 33 | ## Quick start 34 | Before downloading the Android Open Source Project source code, please check your working environment. It is recommended to use a Linux system with at least 250G disk space and 16GB+ memory (Ubuntu 20.04 or above is recommended). The compilation time is related to the number of processor cores on the host, so it is recommended to use a host with more cores. 35 | 36 | Download the Android Open Source Project (mainline version) and the development board support source code to your working directory. 37 | ``` 38 | mkdir riscv-android-src && cd riscv-android-src 39 | repo init -u https://android.googlesource.com/platform/manifest -b master 40 | git clone https://gitee.com/XUANTIE-RV/local_manifests.git .repo/local_manifests -b thead-android_dev 41 | repo sync 42 | ``` 43 | 44 | ### BeagleV Ahead 45 | After downloading, you can build the system using the following commands: 46 | ``` 47 | source build/envsetup.sh 48 | lunch beaglev_ahead-userdebug 49 | m -j 50 | ``` 51 | 52 | The compiled files are shown below, and the required files can be copied for use with Fastboot: 53 | ``` 54 | $ ls out/target/product/beaglev_ahead/*img 55 | out/target/product/beaglev_ahead/boot.img out/target/product/beaglev_ahead/super_empty.img out/target/product/beaglev_ahead/vendor_boot-debug.img 56 | out/target/product/beaglev_ahead/cache.img out/target/product/beaglev_ahead/system.img out/target/product/beaglev_ahead/vendor_boot-test-harness.img 57 | out/target/product/beaglev_ahead/dtb.img out/target/product/beaglev_ahead/system_ext.img out/target/product/beaglev_ahead/vendor_boot.img 58 | out/target/product/beaglev_ahead/dtbo-unsigned.img out/target/product/beaglev_ahead/userdata.img out/target/product/beaglev_ahead/vendor_ramdisk-debug.img 59 | out/target/product/beaglev_ahead/dtbo.img out/target/product/beaglev_ahead/vbmeta.img out/target/product/beaglev_ahead/vendor_ramdisk-test-harness.img 60 | out/target/product/beaglev_ahead/product.img out/target/product/beaglev_ahead/vbmeta_system.img out/target/product/beaglev_ahead/vendor_ramdisk.img 61 | out/target/product/beaglev_ahead/ramdisk.img out/target/product/beaglev_ahead/vendor-bootconfig.img 62 | out/target/product/beaglev_ahead/super.img out/target/product/beaglev_ahead/vendor.img 63 | 64 | $ mkdir fastboot 65 | $ cd out/target/product/beaglev_ahead/ 66 | $ cp u-boot-with-spl.bin bootpart.ext4 boot.img super.img userdata.img vbmeta.img vbmeta_system.img vendor_boot.img ../../../../../fastboot/ 67 | ``` 68 | 69 | ![beaglev_connect](https://github.com/XUANTIE-RV/riscv-aosp/blob/main/resources/beaglev_connect.png?raw=true) 70 | 71 | Figure 3. BeagleV Ahead Connection. 72 | 73 | The main connections required to use the development board include power, serial port, USB, and display: 74 | - The serial port is mainly used for command interaction in U-boot and the kernel, and can be connected through the Debug RX and TX on the bottom of the board, with a baud rate of 115200. 75 | - The USB Device interface is mainly used for the connection of fastboot and adb tools. 76 | - The MIPI DSI/HDMI interface can be used to connect the screen to display the UI interface. 77 | 78 | To perform a full system write, press the USB button on the development board and simultaneously press the reset button to enter the boot write mode. 79 | 80 | Then use fastboot to write the system image. ADB and fastboot tools can be downloaded from the Android developer website: 81 | https://developer.android.com/tools/releases/platform-tools 82 | 83 | ``` 84 | #Program U-boot and initialize boot environment variables 85 | fastboot flash ram u-boot-with-spl.bin 86 | fastboot reboot 87 | fastboot flash uboot u-boot-with-spl.bin 88 | 89 | #Program various partitions 90 | #In non-boot write mode, you can enter the command fastboot usb 0 on the uboot command line to write individual partitions separately. 91 | fastboot flash bootpart bootpart.ext4 92 | fastboot flash boot boot.img 93 | fastboot flash vendor_boot vendor_boot.img 94 | fastboot flash super super.img 95 | fastboot flash userdata userdata.img 96 | fastboot flash vbmeta vbmeta.img 97 | fastboot flash vbmeta_system vbmeta_system.img 98 | 99 | #Initialize metadata and misc partitions 100 | fastboot erase metadata 101 | fastboot erase misc 102 | ``` 103 | After writing, reset and power on the board to enter the system boot mode. You can access the system command line through the serial port/ADB and interact with the system image interface through the touch screen or external HDMI display. 104 | 105 | ![beaglev_aosp](https://github.com/XUANTIE-RV/riscv-aosp/blob/main/resources/beaglev_aosp.png?raw=true) 106 | 107 | Figure 4. Running AOSP main branch on BeagleV Ahead. 108 | 109 | ### Lichee Pi 4A EVB 110 | After downloading, you can build the system using the following commands: 111 | ``` 112 | source build/envsetup.sh 113 | lunch lichee_pi_4a-userdebug 114 | m -j 115 | ``` 116 | 117 | The compiled files are shown below, and the required files can be copied for use with Fastboot: 118 | ``` 119 | $ ls out/target/product/lichee_pi_4a/*img 120 | out/target/product/lichee_pi_4a/boot.img out/target/product/lichee_pi_4a/super_empty.img out/target/product/lichee_pi_4a/vendor_boot-debug.img 121 | out/target/product/lichee_pi_4a/cache.img out/target/product/lichee_pi_4a/system.img out/target/product/lichee_pi_4a/vendor_boot-test-harness.img 122 | out/target/product/lichee_pi_4a/dtb.img out/target/product/lichee_pi_4a/system_ext.img out/target/product/lichee_pi_4a/vendor_boot.img 123 | out/target/product/lichee_pi_4a/dtbo-unsigned.img out/target/product/lichee_pi_4a/userdata.img out/target/product/lichee_pi_4a/vendor_ramdisk-debug.img 124 | out/target/product/lichee_pi_4a/dtbo.img out/target/product/lichee_pi_4a/vbmeta.img out/target/product/lichee_pi_4a/vendor_ramdisk-test-harness.img 125 | out/target/product/lichee_pi_4a/product.img out/target/product/lichee_pi_4a/vbmeta_system.img out/target/product/lichee_pi_4a/vendor_ramdisk.img 126 | out/target/product/lichee_pi_4a/ramdisk.img out/target/product/lichee_pi_4a/vendor-bootconfig.img 127 | out/target/product/lichee_pi_4a/super.img out/target/product/lichee_pi_4a/vendor.img 128 | 129 | $ mkdir fastboot 130 | $ cd out/target/product/lichee_pi_4a/ 131 | $ mkdir fastboot 132 | $ cp bootpart.ext4 boot.img super.img userdata.img vbmeta.img vbmeta_system.img vendor_boot.img ../../../../../fastboot/ 133 | ``` 134 | 135 | ![licheepi4a_connect](https://github.com/XUANTIE-RV/riscv-aosp/blob/main/resources/licheepi4a_connect.png?raw=true) 136 | 137 | Figure 5. Lichee Pi 4A EVB connect 138 | 139 | The main connections required to use the development board include power, serial port, USB, and display: 140 | 141 | - The serial port is mainly used for command interaction in U-boot and the kernel, and can be connected through the U0-RX and U0-TX GPIO on the bottom of the board, with a baud rate of 115200. 142 | - The USB Device interface is mainly used for the connection of fastboot and adb tools. 143 | - The MIPI DSI/HDMI interface can be used to connect the screen to display the UI interface. 144 | 145 | To perform a full system write, press the boot button on the development board and simultaneously press the reset button to enter the boot write mode. 146 | 147 | Then use fastboot to write the system image. ADB and fastboot tools can be downloaded from the Android developer website: 148 | https://developer.android.com/tools/releases/platform-tools 149 | 150 | ``` 151 | #Program U-boot and initialize boot environment variables 152 | fastboot flash ram u-boot-with-spl.bin 153 | fastboot reboot 154 | fastboot flash uboot u-boot-with-spl.bin 155 | 156 | #Program various partitions 157 | #In non-boot write mode, you can enter the command fastboot usb 0 on the uboot command line to write individual partitions separately. 158 | fastboot flash bootpart bootpart.ext4 159 | fastboot flash boot boot.img 160 | fastboot flash vendor_boot vendor_boot.img 161 | fastboot flash super super.img 162 | fastboot flash userdata userdata.img 163 | fastboot flash vbmeta vbmeta.img 164 | fastboot flash vbmeta_system vbmeta_system.img 165 | 166 | #Initialize metadata and misc partitions 167 | fastboot erase metadata 168 | fastboot erase misc 169 | ``` 170 | After writing, reset and power on the board to enter the system boot mode. You can access the system command line through the serial port/ADB and interact with the system image interface through the touch screen or external HDMI display. 171 | 172 | ![licheepi4a_aosp](https://github.com/XUANTIE-RV/riscv-aosp/blob/main/resources/licheepi4a_aosp.png?raw=true) 173 | 174 | Figure 6. Running AOSP Mainline on Lichee Pi 4A 175 | 176 | (If you need more optimized and stable system support, please contact us to obtain Android 12 version support. This version has a more complete system components and peripheral HAL support, adapted for GPU, VPU, Camera, Audio, NPU and other peripheral hardware, and has undergone more comprehensive XTS testing and stress testing. 177 | You can obtain relevant support through the "work order system" in the "About Us" section.) 178 | 179 | ## Change list 180 | 2023/07/06 181 | 182 | - Release BeagleV Ahead development board Alpha support 183 | - Release Lichee Pi 4A EVB Alpha support 184 | 185 | ## Contribute 186 | This project accepts external contributions through Pull Requests. The following process can be referred to: 187 | 188 | 1. Fork the modified repository into a personal account. 189 | 2. Create a development branch named suitably for your work. 190 | 3. Replace the project remote and revision with your own repository: 191 | ``` 192 | - 193 | + 194 | ``` 195 | 4. All new work should be based on the corresponding development branch. 196 | 5. When creating a submission, ensure that the changes are as independent and complete as possible, and provide appropriate submission messages. 197 | 6. It is recommended to include relevant unit test results when making changes. 198 | 7. Push the development branch to your personal repository fork on Github. 199 | 8. Create a Github Pull Request for the corresponding development branch. If the submission is for a bug fix, link it to the issue in the issue tracker. 200 | 201 | ## Releated link 202 | 203 | The issue tracker for this project (for Android related issues on the Development Board, please submit to this tracker): 204 | 205 | https://gitee.com/thead-android/thead-android/issues 206 | 207 | Other open source software projects by Flathead Brother can be accessed through the following links: 208 | 209 | XuanTie Yocto Linux: https://gitee.com/thead-yocto 210 | 211 | YoC Open: https://gitee.com/yocop 212 | 213 | If you want to learn more about TH1520 and Wujian 600 platform, please visit: 214 | 215 | https://www.xrvm.cn/product/wujian/600 216 | 217 | If you want to learn more about the dynamic support of RISC-V architecture on Android, you can subscribe to the RISC-V Android SIG mailing list and participate in community discussions: 218 | 219 | https://lists.riscv.org/g/sig-android 220 | 221 | If you have any questions about Android support for RISC-V architecture, you can submit them to the generic issue tracker for Android-riscv64: 222 | 223 | https://github.com/google/android-riscv64/issues 224 | 225 | ## License 226 | 227 | We do not require any formal copyright assignment or contributor license agreement. Any contributions intentionally sent upstream are presumed to be offered under terms of the OSI-approved Apache License 2.0. See LICENSE file for details. 228 | 229 | ## About Us 230 | This repository is maintained by Alibaba Damo Academy Xuantie Team. 231 | 232 | If you need technical support, you can submit a work order through OCC: 233 | https://www.xrvm.cn/people/workorder-submit 234 | 235 | You can also contact us through the following ways: 236 | E-mail: xuantie@service.alibaba.com 237 | --------------------------------------------------------------------------------