khadas A311D Andriod 64位移植踩坑

最新推荐文章于 2025-01-23 18:00:50 发布
最新推荐文章于 2025-01-23 18:00:50 发布
阅读量2.7k 收藏 7
点赞数 2

开始踩坑

android零基础开发，有些本来不是大问题的地方，因为对android不熟悉卡了很久。

**持续更新中。。。 **

初步计划参考
参考
ubuntu下开发

下载Android Studio 链接

相关工具下载网站网址

安装ADB

sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb

测试安装是否成功

adb --version

查看USB设备ID，首先运行lsusb指令查看现有的usb设备，然后插上Andriod板卡，再次运行lsusb查看增加了那个设备。

Bus 001 Device 009: ID 18d1:4e40 Google Inc. Nexus 7 (fastboot)

创建adb_usb.ini文件，写入id

echo 0x18d1 > ~/.android/adb_usb.ini

添加权限，创建对应的rules

sudo vim /etc/udev/rules.d/70-android.rules

输入如下信息

SUBSYSTEM=="usb", ATTRS{idVendor}=="18d1", ATTRS{idProduct}=="4e40", MODE="0666"

fastboot指令

adb reboot fastboot
fastboot flashing unlock
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flashing lock
fastboot reboot

adb指令

adb root
adb remount
adb shell

su

adb push xxx.jpg  /data

编译Android源码

最难的是下载！！！
khadas下载教程

百度网盘下载基版本代码（链接：https://pan.baidu.com/s/1xu8B3EJC-YitSZPZlmIf2w 提取码：wllx ）（里面有个说明），下载后的文件如下，包含readme：

khadas.tar.gz.00  khadas.tar.gz.04  khadas.tar.gz.08  khadas.tar.gz.12  khadas.tar.gz.16  khadas.tar.gz.20  khadas.tar.gz.24
khadas.tar.gz.01  khadas.tar.gz.05  khadas.tar.gz.09  khadas.tar.gz.13  khadas.tar.gz.17  khadas.tar.gz.21  readme.txt
khadas.tar.gz.02  khadas.tar.gz.06  khadas.tar.gz.10  khadas.tar.gz.14  khadas.tar.gz.18  khadas.tar.gz.22
khadas.tar.gz.03  khadas.tar.gz.07  khadas.tar.gz.11  khadas.tar.gz.15  khadas.tar.gz.19  khadas.tar.gz.23

下载完25个文件: khadas.tar.gz.00~khadas.tar.gz.24 并放在一个目录。  
将分割后的压缩包解压命令如下:cat khadas.tar.gz.* | tar -zxv
这只是一个基版本，只有一个目录：.repo。里面包含了所有项目（VIM1,VIM2,VIM3,Edge等等），没办法，repo sync会同步所有分支。大小总共大概100G。

比如要下载VIM3 android 9.0代码：

repo init -u https://github.com/khadas/android_manifest.git -b khadas-vims-pie

如果出现类似如下错误

fatal: unable to access 'https://github.com/khadas/android_manifest.git/': gnutls_handshake() failed: The TLS connection was non-properly terminated.

将https改为git重新同步试试。

为了解决sync时类似如下异常，可以看到error是找不到HAED的指向：

error.GitError: manifests rev-list (u'^0c25730......', 'HEAD', '--'): fatal: bad revision 'HEAD'

需要将HEAD指向应该指向的commit

cd .repo/manifests
git branch -av

  remotes/m/khadas-vims-pie         -> origin/khadas-vims-pie
  remotes/origin/Mmallow            856410c update download link of svox repository to google
  remotes/origin/Nougat             2f08215 Set function key adc value for VIM2 different versions
  remotes/origin/Oreo               b75302d fixup! Oreo: V171229
  remotes/origin/khadas-edge-Qt     5e743f6 Khadas: Edge_Qt_V210521
  remotes/origin/khadas-edge-nougat 402b195 update to Edge_Nougat_V191115
  remotes/origin/khadas-edge-pie    16f0d2b Fix compile error
  remotes/origin/khadas-vim3-pie    33144e9 fixup! Pie: V190823
  remotes/origin/khadas-vims-nougat 2f08215 Set function key adc value for VIM2 different versions
  remotes/origin/khadas-vims-pie    0c25730 fixup! Pie: V210128
  remotes/origin/master             f351208 fixup! update: V161211
  remotes/origin/test               3142359 fixup! Pie: V190704

git reset --hard remotes/origin/khadas-vims-pie

若修改清华源在这一步里，

vim .repo/manifests/default.xml

将 https://android.googlesource.com/ 全部使用 https://mirrors.tuna.tsinghua.edu.cn/git/AOSP/ 代替。

$ git diff
diff --git a/default.xml b/default.xml
index bd040d6..7456c40 100644
--- a/default.xml
+++ b/default.xml
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <manifest>
-  <remote fetch="https://android.googlesource.com/" name="aosp" review="https://android.googlesource.com/"/>
+  <remote fetch="https://aosp.tuna.tsinghua.edu.cn/" name="aosp" review="https://aosp.tuna.tsinghua.edu.cn/"/>
   <remote fetch="https://github.com/khadas/" name="github"/>
   <default remote="github" revision="refs/tags/Vims-Pie-V210128" sync-c="true" sync-j="4"/>

同步代码，清华源建议采用-j4

repo sync -j4

repo start khadas-vims-pie-local --all

其他异常问题参考解决方案参考链接
清华镜像Git Repo 镜像使用帮助、Android 镜像使用帮助

编译

export ANDROID_BUILD_TYPE=64
export KERNEL_A32_SUPPORT=false
export PATH=/opt/toolchains/gcc-arm-none-eabi-6-2017-q2-update/bin:/opt/toolchains/gcc-linaro-aarch64-none-elf-4.8-2013.11_linux/bin:$PATH
source build/envsetup.sh
lunch kvim3-eng

============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=9
TARGET_PRODUCT=kvim3
TARGET_BUILD_VARIANT=eng
TARGET_BUILD_TYPE=release
TARGET_ARCH=arm64
TARGET_ARCH_VARIANT=armv8-a
TARGET_CPU_VARIANT=generic
TARGET_2ND_ARCH=arm
TARGET_2ND_ARCH_VARIANT=armv7-a-neon
TARGET_2ND_CPU_VARIANT=cortex-a9
HOST_ARCH=x86_64
HOST_2ND_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-5.4.0-71-generic-x86_64-Ubuntu-18.04.5-LTS
HOST_CROSS_OS=windows
HOST_CROSS_ARCH=x86
HOST_CROSS_2ND_ARCH=x86_64
HOST_BUILD_TYPE=release
BUILD_ID=PPR1.180610.011
OUT_DIR=out
============================================

make -j16
编译bugs
  • 1 缺少依赖库
[946/954] including vendor/amlogic/common/prebuilt/Android.mk ...
"no bootaccelerate source code, add prebuilts"
"no exoplayer source code, add prebuilts"
vendor/amlogic/common/prebuilt/libmedia/libavenhancements/Android.mk: error: libamffmpegcodec: No source files specified 
build/make/core/prebuilt_internal.mk:35: error: done.
14:00:05 ckati failed with: exit status 1

措施

vendor/amlogic/common/prebuilt/libmedia/libavenhancements/Android.mk

48: LOCAL_MULTILIB := both --> LOCAL_MULTILIB := 32
  • 2 坑了好久，实际错误原因时缺少依赖库，导致指定的module编译不过去，从报错里完全看不出来
ninja: error: 'out/target/product/kvim3/obj_arm/SHARED_LIBRARIES/libjnivendorfont_intermediates/export_includes', needed by 'out/target/product/kvim3/obj_arm/SHARED_LIBRARIES/libjnifont_tv_intermediates/import_includes', missing and no known rule to make it
14:49:42 ninja failed with: exit status 1

rm vendor/amlogic/common/apps/SubTitle/Android.mk

rm vendor/amlogic/common/arm_isp/app/v4l2_test_android/Android.mk
rm vendor/amlogic/common/frameworks/av/libaudioeffect/Virtualsurround/Android.mk # only 32bit xxx.a
# rm hardware/amlogic/camera/Android.mk
# rm hardware/amlogic/camera/vircam/Android.mk
hardware/amlogic/camera/v3/Android.mk
74: + NEED_ISP=false
  • 3 不能把问题解决了，就把提出问题的人解决了。把报错的工具软件改掉，全返回正常。
VNDK library: android.hardware.configstore@1.0's ABI has INCOMPATIBLE CHANGES Please check compatiblity report at : out/soong/.intermediates/hardware/interfaces/configstore/1.0/android.hardware.configstore@1.0/android_arm64_armv8-a_vendor_shared/android.hardware.configstore@1.0.so.abidiff

参考Android 9 §版本解决VNDK library: XXX’s ABI has EXTENDING CHANGES

## modify development/vndk/tools/header-checker/header-abi-diff/src 中的 header_abi_diff.cpp

--- a/development/vndk/tools/header-checker/header-abi-diff/src/header_abi_diff.cpp
+++ b/development/vndk/tools/header-checker/header-abi-diff/src/header_abi_diff.cpp
@@ -182,21 +182,21 @@ int main(int argc, const char **argv) {
   
   
   
   bool should_emit_warning_message = ShouldEmitWarningMessage(status);
 
   if (should_emit_warning_message) {
   
   
   
-    llvm::errs() << "******************************************************\n"
-                 << error_or_warning_str
-                 << "VNDK library: "
-                 << lib_name
-                 << "'s ABI has "
-                 << status_str
-                 << unreferenced_change_str
-                 << " Please check compatiblity report at : "
-                 << compatibility_report << "\n"
-                 << "******************************************************\n";
+//    llvm::errs() << "******************************************************\n"
+//                 << error_or_warning_str
+//                 << "VNDK library: "
+//                 << lib_name
+//                 << "'s ABI has "
+//                 << status_str
+//                 << unreferenced_change_str
+//                 << " Please check compatiblity report at : "
+//                 << compatibility_report << "\n"
+//                 << "******************************************************\n";
   }
 
-  if (!advice_only && should_emit_warning_message) {
   
   
   
-    return status;
-  }

重新编译 development/vndk/tools/header-checker，编译命令如下:

mmm  development/vndk/tools/header-checker/ -j32
616+0 records in
616+0 records out
630784 bytes (631 kB, 616 KiB) copied, 0.0032836 s, 192 MB/s
[ 66% 2/3] glob .
[100% 5/5] Install: out/host/linux-x86/bin/header-abi-diff

复制 out/host/linux-x86/bin/header-abi-diff 到 prebuilts/clang-tools/linux-x86/bin 中覆盖，命令如下：

cp out/host/linux-x86/bin/header-abi-diff prebuilts/clang-tools/linux-x86/bin/header-abi-diff

重新souurce lunhcer，再执行你需要修改的so文件，譬如我们这里的是liblog，我们编译一把:

make  -j32 liblog

//编译结果

vendor/qcom/build/tasks/generate_extra_images.mk:558: warning: overriding commands for target `kernelclean'
device/qcom/common/generate_extra_images.mk:558: warning: ignoring old commands for target `kernelclean'
[100% 76/76] build out/host/linux-x86/obj32/SHARED_LIBRARIES/liblog_intermediates/liblog.so.toc

好了,大功告成可以愉快的修改VNDK的相关改动了。

  • 4 提供的64位依赖有问题
vendor/amlogic/common/npu/service/../applib/nnrt/file_map_memory.hpp:38: error: undefined reference to 'vtable for nnrt::Memory'
prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/aarch64-linux-android/bin/ld.gold: the vtable symbol may be undefined because the class is missing its key function
vendor/amlogic/common/npu/service/../applib/nnrt/file_map_memory.hpp:38: error: undefined reference to 'vtable for nnrt::Memory'
prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/aarch64-linux-android/bin/ld.gold: the vtable symbol may be undefined because the class is missing its key function
vendor/amlogic/common/npu/service/../applib/nnrt/file_map_memory.hpp:39: error: undefined reference to 'vtable for nnrt::Memory'
prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/aarch64-linux-android/bin/ld.gold: the vtable symbol may be undefined because the class is missing its key function
vendor/amlogic/common/npu/service/../applib/nnrt/file_map_memory.hpp:39: error: undefined reference to 'vtable for nnrt::Memory'
prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/aarch64-linux-android/bin/ld.gold: the vtable symbol may be undefined because the class is missing its key function
external/libcxx/include/memory:2137: error: undefined reference to 'nnrt::Model::Model()'
external/libcxx/include/memory:2131: error: undefined reference to 'nnrt::Model::~Model()'
external/libcxx/include/memory:2131: error: undefined reference to 'nnrt::Model::~Model()'
external/libcxx/include/memory:3704: error: undefined reference to 'nnrt::Model::~Model()'
vendor/amlogic/common/npu/service/VsiPreparedModel.cpp:252: error: undefined reference to 'nnrt::Model::setOperandValue(std::__1::shared_ptr<nnrt::op::Operand>, void const*, unsigned long)'
vendor/amlogic/common/npu/service/VsiPreparedModel.cpp:256: error: undefined reference to 'nnrt::Model::setOperandValue(std::__1::shared_ptr<nnrt::op::Operand>, void const*, unsigned long)'
vendor/amlogic/common/npu/service/VsiPreparedModel.cpp:269: error: undefined reference to 'nnrt::Model::setOperandValueFromMemory(std::__1::shared_ptr<nnrt::op::Operand>, nnrt::Memory const*, unsigned long, unsigned long)'
vendor/amlogic/common/npu/service/VsiPreparedModel.cpp:267: error: undefined reference to 'nnrt::Model::setOperandValue(std::__1::shared_ptr<nnrt::op::Operand>, void const*, unsigned long)'
vendor/amlogic/common/npu/service/VsiPreparedModel.cpp:329: error: undefined reference to 'nnrt::Model::addOperand(std::__1::shared_ptr<nnrt::op::Operand>, unsigned int*)'
vendor/amlogic/common/npu/service/VsiPreparedModel.cpp:354: error: undefined reference to 'nnrt::Model::addOperation(nnrt::OperationType, unsigned int const*, unsigned int, unsigned int const*, unsigned int, unsigned int*)'
vendor/amlogic/common/npu/service/VsiPreparedModel.cpp:365: error: undefined reference to 'nnrt::Model::relax(bool)'
vendor/amlogic/common/npu/service/VsiPreparedModel.cpp:370: error: undefined reference to 'nnrt::Model::identifyInputsAndOutputs(unsigned int const*, unsigned int, unsigned int const*, unsigned int)'
vendor/amlogic/common/npu/service/VsiPreparedModel.cpp:377: error: undefined reference to 'nnrt::Model::getOperands(std::__1::vector<unsigned int, std::__1::allocator<unsigned int> > const&)'
vendor/amlogic/common/npu/service/VsiPreparedModel.cpp:398: error: undefined reference to 'nnrt::Model::getOperands(std::__1::vector<unsigned int, std::__1::allocator<unsigned int> > const&)'
vendor/amlogic/common/npu/service/VsiPreparedModel.cpp:406: error: undefined reference to 'nnrt::Execution::setOutput(unsigned int, std::__1::shared_ptr<nnrt::op::Operand>, void*, unsigned long)'
vendor/amlogic/common/npu/service/VsiPreparedModel.cpp:404: error: undefined reference to 'nnrt::Execution::setInput(unsigned int, std::__1::shared_ptr<nnrt::op::Operand>, void const*, unsigned long)'
vendor/amlogic/common/npu/service/VsiPreparedModel.cpp:431: error: undefined reference to 'nnrt::Execution::setOutput(unsigned int, std::__1::shared_ptr<nnrt::op::Operand>, void*, unsigned long)'
vendor/amlogic/common/npu/service/VsiPreparedModel.cpp:439: error: undefined reference to 'nnrt::Execution::setOutputFromMemory(unsigned int, std::__1::shared_ptr<nnrt::op::Operand>, nnrt::Memory const*, unsigned long, unsigned long)'
vendor/amlogic/common/npu/service/VsiPreparedModel.cpp:429: error: undefined reference to 'nnrt::Execution::setInput(unsigned int, std::__1::shared_ptr<nnrt::op::Operand>, void const*, unsigned long)'
vendor/amlogic/common/npu/service/VsiPreparedModel.cpp:436: error: undefined reference to 'nnrt::Execution::setInputFromMemory(unsigned int, std::__1::shared_ptr<nnrt::op::Operand>, nnrt::Memory const*, unsigned long, unsigned long)'
external/libcxx/include/memory:2151: error: undefined reference to 'nnrt::Compilation::Compilation(nnrt::Model*)'
external/libcxx/include/memory:2151: error: undefined reference to 'nnrt::Execution::Execution(nnrt::Compilation*)'
external/libcxx/include/memory:2131: error: undefined reference to 'nnrt::Compilation::~Compilation()'
external/libcxx/include/memory:2131: error: undefined reference to 'nnrt::Compilation::~Compilation()'
external/libcxx/include/memory:2131: error: undefined reference to 'nnrt::Execution::~Execution()'
external/libcxx/include/memory:2131: error: undefined reference to 'nnrt::Execution::~Execution()'
clang-6.0: error: linker command failed with exit code 1 (use -v to see invocation)
  • 5 audio确实64位依赖库
hardware/amlogic/audio/audio_hal/audio_hw.c:4470: error: undefined reference to 'noise_evaluation'
hardware/amlogic/audio/audio_hal/audio_hw.c:11903: error: undefined reference to 'init_noise_gate'
hardware/amlogic/audio/audio_hal/audio_hw.c:11323: error: undefined reference to 'release_noise_gate'
clang-6.0: error: linker command failed with exit code 1 (use -v to see invocation)

rm hardware/amlogic/LibAudio
rm hardware/amlogic/audio/audio_hal
  • 6 编译过程中报错
******************************
You have tried to change the API from what has been previously approved.

To make these errors go away, you have two choices:
   1) You can add "@hide" javadoc comments to the methods, etc. listed in the
      errors above.

   2) You can update current.txt by executing the following command:
         make update-api

      To submit the revised current.txt to the main Android repository,
      you will need approval.
******************************

make update-api
  • 7 打包时报错
depmod: WARNING: could not open /home/test/khadas/out/target/product/kvim3/obj/PACKAGING/depmod_vendor_intermediates/lib/modules/0.0/modules.order: No such file or directory
depmod: WARNING: could not open /home/test/khadas/out/target/product/kvim3/obj/PACKAGING/depmod_vendor_intermediates/lib/modules/0.0/modules.builtin: No such file or directory
error: failed to build out/target/product/kvim3/vendor.img from out/target/product/kvim3/vendor
Error: '['mkuserimg_mke2fs.sh', '-s', 'out/target/product/kvim3/vendor', 'out/target/product/kvim3/vendor.img', 'ext4', 'vendor', '335544320', '-j', '0', '-D', 'out/target/product/kvim3/system', '-L', 'vendor', '-M', '0', 'out/target/product/kvim3/obj/ETC/file_contexts.bin_intermediates/file_contexts.bin']' failed with exit code 4:
MKE2FS_CONFIG=./system/extras/ext4_utils/mke2fs.conf mke2fs -O ^has_journal -L vendor -m 0 -E android_sparse -t ext4 -b 4096 out/target/product/kvim3/vendor.img 81920
mke2fs 1.43.3 (04-Sep-2016)
Creating filesystem with 81920 4k blocks and 81984 inodes
Filesystem UUID: ece343f7-9e47-4aad-9751-b524bafcc8b2
Superblock backups stored on blocks: 
        32768

Allocating group tables: done                            
Writing inode tables: done                            
Writing superblocks and filesystem accounting information: done

e2fsdroid -p out/target/product/kvim3/system -S out/target/product/kvim3/obj/ETC/file_contexts.bin_intermediates/file_contexts.bin -f out/target/product/kvim3/vendor -a /vendor out/target/product/kvim3/vendor.img
__populate_fs: Could not allocate block in ext2 filesystem while writing file "ge2d_chip_check"
e2fsdroid: Could not allocate block in ext2 filesystem while populating file system
  • 8 烧写镜像时错误
ID[16]
tplcmd[download store vendor sparse 341180564]
[MSG]flash LOGIC partCap 0x14000000B
ERR(../drivers/usb/gadget/v2_burning/v2_common/optimus_download.c)L709:imgSz 0x14560094 out of cap 0x14000000
ERR(../drivers/usb/gadget/v2_burning/v2_common/optimus_download.c)L1155:Fail in init download info
[info]failed:

修改设备树信息

common/arch/arm64/boot/dts/amlogic/partition_mbox_normal_P_64.dtsi

		vendor:vendor
		{
			pname = "vendor";
			size = <0x0 0x14000000>;
			mask = <1>;
		};
		-->
		vendor:vendor
		{
			pname = "vendor";
			size = <0x0 0x1C000000>;
			mask = <1>;
		};

未完待续。。。

Vincent_PHY
关注
A311D2,T982 软件刷机工具
09-02
A311D2,T982 软件刷机工具
A311D2 参考原理图设计
09-02
在处理A311D2参考原理图设计文档时，我们首先会注意到它所涉及的是一个集成了多种功能模块的复杂系统。A311D2可能是一个特定的系统级芯片（SoC）的型号，它被设计用于AIoT（人工智能物联网）领域，这些领域正迅速...
Amlogic A311D安卓板的TF卡
GHL445的博客
08-27 438
TF卡卡槽在板子背面处。 1、插入TF卡，观察串口打印 //串口有下面的打印 即识别tf卡成功 root@Apoidea:/# [ 5668.085995@2] meson-mmc: card IN 2、挂载TF卡 root@Apoidea:/# mount /dev/mmcblk1p1 /mnt/tf/ root@Apoidea:/# ls /mnt/tf/ configjdjq.wavjdjq.wav-1kernelro...
A311D2 Android11.0 SDK编译
kuosuoguang3325的博客
01-11 3050
A311D2 Android11.0 SDK编译 配置交叉编译工具链 $ export PATH=$PATH:/opt/gcc-linaro-6.3.1-2017.02-x86_64_aarch64-linux-gnu/bin:/opt/riscv-none-gcc/7.2.0-4-20180606-1631/bin $ export PATH=$PATH:/home/rpdzkj/second/tanzh/a311d2-android11.0/test2/android11.0/prebuilts/bui
ubuntu22.04 编译 A311D android9
cr1029的博客
01-23 319
编译报错提示flex异常：flex-2.5.39: loadlocale.c:130:_nl_intern_locale_data:?Aborted (core dumped)一开始通过repo下了3天没下下来，后面直接拉到最下用百度云下载。a311d khadas开发板。ubuntu22.04系统。
2.晶晨A311D-编译Ubuntu/Debian固件
Jun626的博客
02-20 3142
上面是我的微信和QQ群，欢迎新朋友的加入。 参考：https://docs.khadas.com/zh-cn/vim3/FenixScript.html 编译环境，我重新安装了ubuntu20 安装软件包，配置环境 sudo apt-get install git-core gnupg flex bison gperf build-essential zip sudo apt-get install curl zlib1g-dev gcc-multilib g++-multilib...
amlogic晶晨 A311D2 数据手册 V0.3版本
06-14
Amlogic 晶晨 A311D2 数据手册 V0.3 版本 -amlogic 晶晨 A311D2 是一款高性能的系统级芯片（SoC），用于各种智能设备的设计和制造。该芯片具有高性能的处理能力、低功耗、高速存储器接口等特点。 知识点 1：...
Amlogic A311D2芯片编译与烧录流程详解
10-28
内容概要：本文详细介绍了基于Amlogic A311D2芯片的开发板从编译到烧录的一系列步骤，涵盖Bootloader、Kernel、DTS、Android系统的编译命令以及烧录方法。特别强调了在遇到Windows环境下烧录不生效时的解决办法及...
Amlogic T400_A311D_LPDDR4_TEST_BOARD_SCH.pdf
06-02
晶晨半导体（Amlogic）推出的A311D是针对高性能计算需求而设计的系统级芯片（SoC），尤其适用于需要LPDDR4内存支持的应用。LPDDR4是一种高性能、低功耗的内存标准，适用于移动设备和嵌入式系统。在这份参考设计的...
晶晨Amlogic a311d khadas开发板学习——系统烧写
故事里的小可爱的博客
11-30 6554
文章目录khadas a311d系统烧写1.主机Ubuntu环境配置——通过Ubuntu升级固件2.VIM3进入升级模式3.烧录固件 khadas a311d系统烧写 1.主机Ubuntu环境配置——通过Ubuntu升级固件 $ sudo apt-get install libusb-dev git parted $ git clone https://github.com/khadas/utils $ cd /path/to/utils $ git pull $ ./INSTALL 如果成功安装你会看到
Amlogic_A311D_Buildroot_Preview_Release_Notes
07-27
This document provides the Openlinux notes for Amlogic Linux BSP reference source code release running on Amlogic reference hardware. To obtain Amlogic Linux BSP reference source code, you need to have an account to access Amlogic GIT source code repository.
A311D Quick Reference Manual V0.4
10-30
晶辰半导体Amlogic A311D 规格书 A311D is an advanced AI application processor designed for hybrid OTT/IP Set Top Box(STB) and highend media box applications. It integrates a powerful CPU, GPU and NPU optional (Neural Processing Unit) subsystem, a secured 4K video CODEC engine and a best-in-class HDR image
Amlogic A311D 驱动分析系列(二)-ADC键盘
hmorey的博客
02-17 1267
本系列文章基于Amlogic A311D SDK中的驱动，将我之前阅读代码的一些收获进行总结，算是学习笔记吧。 这一章分析adc键盘驱动 代码adc_keypad.c 1.dts配置 adc_keypad { compatible = "amlogic, adc_keypad"; status = "okay"; key_name = "vol-", "vol+", "enter";//键值名 key_num = <3>;//键值数量 io-channels =
xHiveAI-A311D：AI开发套件
danielyu_123456的专栏
11-11 3893
群蜂技术的xHiveAI开发套件采用Amlogic的A311D六核（Cortex-A73x4 +Cortex-A53x2) 64位处理器，集成了多核MaliTM-G52 GPU，计算能力达到5TOPS@int8, 12.8GFLOPS@FP16 or 6.4 GFLOPS@FP32的NPU AI Neural network accelerator (NNA)，性能优异。板载 HDMI接口，MIPI摄像头接口 ，WIFI/Bluetooth模块，声音相关接口。支持 Linux/Ubuntu 系统，开放源代.
Amlogic A311D 驱动分析系列(一)-看门狗驱动分析
hmorey的博客
02-16 1102
本系列文章基于A311D SDK对amlogic的驱动，将我之前阅读代码的一些收获进行总结，算是学习笔记吧。 1.代码位置 common\drivers\amlogic\watchdog meson_wdt.c meson_wdt_v3.c
Amlogic A311D芯片简介
热门推荐
GHL445的博客
09-02 1万+
Amlogic A311D芯片简介 Amlogic A311D 是一款先进的 AI 应用处理器，专为混合 OTT/IP 机顶盒 (STB) 和高端媒体盒应用而设计。它将强大的 CPU、GPU 和神经网络加速器子系统、安全的 4K 视频编解码器引擎和一流的 HDR 图像处理管道与所有主要外设集成在一起，形成终极高性能的 AI 多媒体 AP。总而言之，A311D = S922X + MIPI-CSI + NPU 主系统CPU基于Big.Little架构，集成四核ARM Cortex-A73 CPU集
xHiveAI-A311D：H264 Encoder的实现
danielyu_123456的专栏
11-11 682
A311D芯片集成了一个H.264/H.265 encoder，可以配置它的bit rate，frame rate等参数。 按照下面的步骤来实现你的第一个h264 encoder: 1) 请参考文章：开发环境准备 2）h264 encode的示例程序在目录 encoder下面 cdencoder/src make <正常编译后，会生成可执行文件：test_h264encode> scptest_h264encode root@&...
A311D项目开发总结
发呆健将的博客
10-24 6813
A311D项目有感 最近项目使用了Amlogic的A311D平台，这款芯片的功能跟性能相比于其他平台都比较优秀了，当然他的开发过程也是让自己感觉收获了很多，这里就稍微做下回顾吧 项目使用了荣品的A311D核心模块，硬件上内存相较于VIM3和odroid-n2存在差异，其他相差不大； 荣品提供的SDK使用的是Buildroot构建的方式，uboot、kernel、ramdisk、rootfs统统打包在一起，而且编译打包一次的时间非常长，这是不能接受的，所以后面很多工作都是在将这些部件拆分开来； 荣品SD
基于模糊控制理论的汽车EPS双层控制器设计及仿真优化研究 · 控制器设计 参考
最新发布
05-29
内容概要：本文探讨了如何设计一个基于模糊控制理论的双层控制器来优化汽车EPS（电动助力转向系统）的性能。EPS系统通过电子控制技术实现转向助力，提升驾驶的舒适性和操控性。文中详细介绍了PID控制算法的局限性以及引入模糊控制器的原因。模糊控制器作为双层控制器的上层，通过模糊推理机制处理不确定性问题并优化PID控制算法。最后，通过Simulink和MATLAB模型进行了仿真验证，证明了双层控制器的有效性。 适合人群：从事汽车工程、控制系统设计的研究人员和技术人员，特别是对模糊控制理论和EPS系统感兴趣的读者。 使用场景及目标：适用于希望深入了解EPS系统优化方法的研究人员和技术人员，旨在通过模糊控制理论改进现有控制算法，提高EPS系统的鲁棒性和适应性。 阅读建议：读者可以通过本文了解模糊控制理论在EPS系统中的应用，掌握双层控制器的设计思路，并通过提供的Simulink和MATLAB模型进行仿真实验，验证控制算法的效果。
评论 1
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值