@gao459459 怎么刷知道吗有固件吗

我也在找H618的固件包，这个芯片的资源确实很少

@raphael 请问问题解决了吗？

黑金颜色 真的 酷！

@forlinx 在 FET113i-S核心板已支持RISC-V，打造国产化降本的更优解 中说：

T113-i的RISC-V核（玄铁C906）资料

layer[0]我用来做全屏了，可以忽略，layer[1]-layer[4]做不同区域，就是不知道如何单独控制着4个区域

可以的 改个配置切换启动默认存储介质即可

那不就是OTA吗，看下OTA说明文档搞一下，好像是有一个XXXXupdate的框架的

感谢你的分享 太有意思了 很荣幸可以帮助学校

@qq2451465243 USBDriver_64.zip 安装这个驱动试试

same issue !
123.png

是基于tensorflow

我来帮你上图

bf1c7c61-f168-4c58-9475-a4cf169eeb9c-image.png

1d5822a8-e4ca-411c-9d46-7737983aa617-image.png

d96e6d5a-1ace-4f39-99f5-c94a05df0cdb-image.png

0e798492-01ea-405f-b6a7-2bac632eec9e-image.png

如果设备是nor储存介质，那一定是squashfs

需要修改QT编译Makefile，加入opencv引用

@quincy

执行命令设置全局保存密码 git config --global credential.helper store 执行命令输入密码 git clone https://sdk.aw-ol.com/git_repo/V853Tina_Open/manifest.git 使用repo拉取sdk repo init -u https://sdk.aw-ol.com/git_repo/V853Tina_Open/manifest.git -b master -m tina-v853-open.xml

由于repo更新，目前不支持通过repo输入密码，请先使用git命令输入保存密码

@lozenyin 编译环境安装mkimage android-tools-mkbootimg

Tina-Linux的github并非全志维护，是第三方维护，具体原因需要联系维护的作者。

@nimadibaj
[ISP_ERR]isp_ctx_save_exit, line: 109,open /mnt/isp0_1920_1088_30_0_ctx_saved.bin failed, err:Read-only file system.
这个是暂存isp参数，由于没有文件所以打开失败。可以无视。

真正的问题是Got signal 11, exiting ...，程序出现段错误，请检查指针使用

@harddream 需要配置一下设备树

@sunxi 板上要有电池给RTC供电, 上电后把RTC的时间同步到系统.

内核配置里面有一个配置开起来：

CONFIG_SUNXI_ADDR_MGT

同时设备树也需要加点东西，&soc节点里面加：

addr_mgt: addr_mgt@0 { compatible = "allwinner,sunxi-addr_mgt"; type_addr_wifi = <0x0>; type_addr_bt = <0x0>; type_addr_eth = <0x0>; status = "okay"; };

重新编译固件看看，看上去是固件问题

看硬件设计，Avaota系列板子设计网卡常量，Active时灭，BPI 设计网卡灯常灭，Avtive时亮

docker 没有正确安装配置

播放是只读操作，检查是否哪里有误，在进行写操作。
如果确实没有写也会坏，那就是EMMC的问题了，可以尝试换个型号对比。

@embfly 具体是怎么不对？xy反转了？还是xy镜像了？
反转交换，改这几个参数
d4be1979-a58d-49ea-a1fe-ed05833a0094-image.png

用的wifi 模组是8822cs，sdio注册probe都没有跑，这有大佬知道吗

@dingzhen make -j1 V=s 打开debug信息再重新上传错误log

这是多大算力的阿，看着还不错

@ttthbbb 553和853一样的，区别只是砍掉了npu

@qw348313 在device/softwinner下搜下有没有sys_partition.fex文件。感觉是SDK包不完整，问代理商再拿一份吧

问题已解决。参照
SDK_DIR/buildroot/package/auto下有sdk_demo。
SDK_DIR下执行.buildconfig后，执行./buildroot/package/auto/build.sh可以编译demo。
但是demo上的解码器如指导文档所说，解码出图滞后。所以解单帧h264时，demo不会出图。建议参照demo里的stopAndGetLeftFrame函数做修改，把滞后的图像取出。测试可行。

int stopAndGetLeftFrame() { int nRet; int leftFrame = VideoStreamFrameNum(pVideoDec, 0); ALOGD("VideoStreamFrameNum:%d", leftFrame); if (leftFrame > 0) { int waitLoop = 0; while (leftFrame > 0) { nRet = DecodeVideoStream(pVideoDec, 1 /*eos*/, 0/*key frame only*/, 0/*drop b frame*/, 0/*current time*/); ALOGD("DecodeVideoStream:%d", nRet); if ((nRet == VDECODE_RESULT_NO_FRAME_BUFFER) || (nRet == VDECODE_RESULT_NO_BITSTREAM)) { break; } usleep(200); waitLoop++; leftFrame--; if (waitLoop > 50) { ALOGW("decode eos time out > 10 ms!"); break; } } } else { ALOGD("There is no left fream to decode!"); } int nValidPicNum = ValidPictureNum(pVideoDec, 0); ALOGD("ValidPictureNum:%d", nValidPicNum); if (nValidPicNum <= 0) { nRet = -2; ALOGW("nValidPicNum:%d, no pic left.", nValidPicNum); return nRet; } while(nValidPicNum > 0) { pPicture = RequestPicture(pVideoDec, 0/*the major stream*/); //VdecH264:step6 if (pPicture != NULL) { AVPacket outPacket; outPacket.id = pPicture->nID; outPacket.pts = pPicture->nPts; outPacket.pAddrPhy0 = (unsigned char*)pPicture->phyYBufAddr; outPacket.pAddrVir0 = (unsigned char*)pPicture->pData0; outPacket.dataLen0 = pPicture->nWidth * pPicture->nHeight; outPacket.pAddrPhy1 = (unsigned char*)pPicture->phyCBufAddr; outPacket.pAddrVir1 = (unsigned char*)pPicture->pData1; outPacket.dataLen1 = outPacket.dataLen0 / 2; if (NULL != mDataCbk) { mDataCbk->decoderDataReady(&outPacket); } ReturnPicture(pVideoDec, pPicture); nValidPicNum--; } else { ALOGW("pPicture == NULL."); return -2; } } return nRet; }

@ts_123456789 在 飞凌T113-i核心板+自制底板 mcp2515驱动失败 中说：
79d371d9-c568-4b3e-ae18-3138d8d8a4a8-image.png
c8e76249-a186-4f87-9fbc-35578f9f29e4-image.png
这个报错是mcp驱动返回的错误码，请检查时钟。要求范围在1M~25M之间

在编译的时候可以看到确实已经编译出bin文件了，而且也复制到target/usr/bin文件夹里面去了，但是貌似打包的时候没有放进去
a875cd30-ac0d-42c2-9914-7d25a6d0c487-1734936238909.png
023f776e-e8e4-4e9b-aea6-2dc1a2b7053c-1734936270736.png
请教一下大家，这种情况应该检查那些东西。

@f8999823 现象2.png 有时候会出现一个这样的。 这种uboot到底拷贝进去ddr没有呀？打印uboot字眼，是不是证明uboot已经拷贝进去ddr了，然后执行的时候出问题了？？还是是边copy边打印？

@lozenyin
不要使用root用户编译

就是一直在boot0这里循环，我看boot0初始化也没有错误，就是不加载uboot，有大佬知道怎么解决吗

老哥，解决没？我也碰到了，不过解法很简单🙄

diff --git a/scripts/dtc/updatetree.c b/scripts/dtc/updatetree.c index 74c621e1..e2159bf6 100644 --- a/scripts/dtc/updatetree.c +++ b/scripts/dtc/updatetree.c @@ -432,7 +432,7 @@ void create_pinconf_node(const char *section_name, phandle = sunxi_dt_add_new_node_to_pinctrl(pinctrl, section_name, ep->name, gpio_name, value, dti); if (phandle) { d_pinctrl_x = data_append_cell(prop->val, phandle); - propname = malloc(strlen(prop->name)); + propname = malloc(strlen(prop->name) + 1); strcpy(propname, prop->name); delete_property(prop); pinctrl_x = build_property(propname, d_pinctrl_x);

@jjssz 建议使用厂家提供的 SDK，下载的方式不太好弄

@wangzx 2 lane试过440x1920，算下来应该没问题，4 lane试过1920x1200， 哦，都在R528上试的。

@laizh950 用内存泄露的方法去排查

@tivon sunxi represents the family of ARM SoCs from Allwinner Technology, a Chinese fabless semiconductor company. Their best known products are the sunxi SoC series, such as the A10 (sun4i), A13 (sun5i) and A20 (sun7i) chips, which were very successful in the low-budget tablet market. See Allwinner SoC Family for more information on the different Allwinner chips.

@bynce 没有选这款芯片，坐等大佬开源。

新版的Tina好像是集成了RTOS方面。但是用RTOS，功能不一定全哦。用RTOS的很多都折腾F1C200那些。其他都比较适合跑Linux。资料也没F1C200开放。

@li_jintao 可以提供下连接打印前面部分信息看下吗

文档中有介绍，《Tina Linux 系统裁剪开发指南》

@yubeer 解决是，原因是Busybox-Makefile手动改过，编译时有问题，未生成init~

处理器是什么，飞牛只能装X86

是的，需要升级驱动，不过NBG是哪里获取的为什么会对不上

工业级看T开头的芯片

@brightgys dts配置发出来

新手获取不了，需要升级带LV2，使用repo下载

如果想从SD/TF卡启动，记得选择启动卡
想将其转换为标准镜像？用其他软件烧录？
可以参考这里
https://bbs.aw-ol.com/topic/1365/openixcard-在-linux-系统刷写全志镜像到-sd-卡
https://github.com/YuzukiTsuru/OpenixCard

可以在APST下载

@ylyamin 在 R-01 library for small OS 中说：

requests

Since LCD RGB is working, DE probably working fine. So what is left could be LCD MIPI part.

Allwinner tends to use the same code everywhere, so there could be a problem to find alternatives. Mainline Linux kernel maybe the only place to look at. Also logic analyzer maybe needed for this kind of task.

Another reference could be xboot project: https://github.com/xboot/xboot , but seems main activities goes into LCD RGB.

设备树是正确的吗

@helloa 参考pack脚本，制作对应分区

@yubeer 本地swupdate_cmd.sh执行upgrade_kernel后，重启日志，彻底挂了~

[217]Entry_name = u-boot [224]Entry_name = optee [228]Entry_name = dtb [231]Jump to second Boot. M/TC: OP-TEE version: 6aef7bb2-dirty (gcc version 5.3.1 20160412 (Linaro GCC 5.3-2016.05)) #1 Fri Jul 23 09:25:11 UTC 2021 arm U-Boot 2018.05-g2a1965a-dirty (Jul 10 2022 - 02:50:57 +0000) Allwinner Technology [00.284]CPU: Allwinner Family [00.287]Model: sun8iw20 [00.289]DRAM: 128 MiB [00.292]Relocation Offset is: 04ec1000 [00.317]secure enable bit: 0 [00.320]smc_tee_inform_fdt failed with: -65526[00.324]CPU=1008 MHz,PLL6=600 Mhz,AHB=200 Mhz, APB1=100Mhz MBus=300Mhz [00.330]gic: sec monitor mode [00.333]flash init start [00.335]workmode = 0,storage type = 0 device nand0 <nand>, # parts = 4 #: name size offset mask_flags 0: boot0 0x00100000 0x00000000 1 1: uboot 0x00300000 0x00100000 1 2: secure_storage 0x00100000 0x00400000 1 3: sys 0x0fb00000 0x00500000 0 active partition: nand0,0 - (boot0) 0x00100000 @ 0x00000000 defaults: mtdids : nand0=nand mtdparts: mtdparts=nand:1024k@0(boot0)ro,3072k@1048576(uboot)ro,1024k@4194304(secure_storage)ro,-(sys) [00.512]ubi0: attaching mtd4 [00.713]ubi0: scanning is finished [00.720]ubi0: attached mtd4 (name "sys", size 251 MiB) [00.725]ubi0: PEB size: 262144 bytes (256 KiB), LEB size: 258048 bytes [00.731]ubi0: min./max. I/O unit sizes: 4096/4096, sub-page size 2048 [00.737]ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096 [00.743]ubi0: good PEBs: 1004, bad PEBs: 0, corrupted PEBs: 0 [00.749]ubi0: user volume: 10, internal volumes: 1, max. volumes count: 128 [00.755]ubi0: max/mean erase counter: 2/1, WL threshold: 4096, image sequence number: 0 [00.763]ubi0: available PEBs: 0, total reserved PEBs: 1004, PEBs reserved for bad PEB handling: 40 [00.772]sunxi flash init ok [00.774]line:703 init_clocks [00.777]drv_disp_init fdt get node offset faill: hdmi [00.787]unable to map hdmi registers [00.790]drv_disp_init finish [00.895]Loading Environment from SUNXI_FLASH... OK [00.915]boot_gui_init:start [00.918]set disp.dev2_output_type fail. using defval=0 drv_lcd_open_callback lcd open flow is NULL! LCD enable fail! [00.929]boot_gui_init:finish partno erro : can't find partition bootloader 54 bytes read in 0 ms [00.948]bmp_name=bootlogo.bmp size 38454 38454 bytes read in 2 ms (18.3 MiB/s) [00.960]Item0 (Map) magic is bad [00.962]out of usb burn from boot: not need burn key List file under ULI/factory ** Unrecognized filesystem type ** [00.983]update bootcmd damaged volume, update marker is set[00.998]change working_fdt 0x44880e70 to 0x44860e70 [01.020]update dts Hit any key to stop autoboot: 0 damaged volume, update marker is set[02.041]no vendor_boot partition is found Wrong Image Format for bootm command ERROR: can't get kernel image!

@m_xiaotao
移植了一个ffmpeg 但是使用ffmpeg 不能进行播放

Unable to handle kernel paging request at virtual address 0000000000040008

看看内核代码rb_next附近，有非法地址访问

论坛逛了一圈，成功进入系统。
主要修改点：
1.uboot里面menuconfig使能etx4
2.kernel里面menuconfig使能ext4，取消squashfs
3.SDK/device/config/chips/d1s/configs/default/env.cfg里面将rootfstype=squashfs改为rootfstype=ext4
4.如果make成功，pack失败就修改SDK/device/config/chips/d1s/configs/nezha_sd/sys_partition.fex的相应分区大小，一般都是rootfs分区大小不够，需要多大才够可以看pack的报错有显示

还没编译为啥会有

@goodwill1945 前几次烧录成功让我以为win10会自动安装在win11安装好的烧录驱动，而且重装系统后保留了WIN11的启动选项，WIN10升级WIN11也不需要重新安装烧录驱动，就有迷惑性 = = 实际上烧录驱动仍然需要重新安装

fe59d7d1-804a-44cb-9e26-8dde380128ac-企业微信截图_17404543338194.png [图片]

现在可以升级，kernel 是正常的，但是rootfs 不显示进度。

@laoliu 还没拨号吧

【已解决】 步骤一

捕获.JPG

先将btmanager整个复制到项目中

步骤二

捕获.JPG

在项目中新建out_lib和out2_lib目录
然后将这段复制到pro文件里最下边（截图的不完整，用下面的代码）

LIB_PATH = $$PWD/btmanager/out_lib LIB_PATH2 = $$PWD/btmanager/out2_lib unix:!macx: LIBS += -L$$LIB_PATH2 -lpcre -lffi ## 在 Unix 系统（非 macOS）下添加库 unix:!macx { LIBS += -L$$LIB_PATH -lbluetooth -lglib-2.0 -lsbc -ljson-c -lz -lgmodule-2.0 -lgio-2.0 -lgobject-2.0 -lasound -lbtmg -ldl -lm -lresolv LIBS += -lshared-mainloop -lbluetooth-internal -lshared-glib } INCLUDEPATH += $$PWD/btmanager/include DEPENDPATH += $$PWD/btmanager/include 步骤三

在你的sdk下找到类似这个路径Tina-SDK/out/t113-bingpi_m2/staging_dir/target/usr/lib下的所有文件复制到项目下的out_lib中，再找到类似这个路径Tina-SDK/out/t113-bingpi_m2/staging_dir/target/rootfs/lib下的所有文件复制到项目下的out2_lib中（out文件夹是要进行一次make && moob && pack后编译生成所产生的）
编译执行，就不会缺少依赖了

##总结
其实我这个是笨方法，就是缺少啥依赖就将生成的so文件放进去，实际上用到的就是这些-lbluetooth -lglib-2.0 -lsbc -ljson-c -lz -lgmodule-2.0 -lgio-2.0 -lgobject-2.0 -lasound -lbtmg -ldl -lm -lresolv -lshared-mainloop -lbluetooth-internal -lshared-glib，这些库的意思就是去掉lib和so前缀和后缀的，比如 -lbluetooth就是libbluetooth.so、-lglib-2.0就是libglib-2.0.so。这里是参考btmanager里面demo里的Makefile文件写的，-lbtmg引入的顺序必须与写的顺序一致，不然会提示缺少依赖，需要写好-lbtmg所需要的依赖后再引入。

串口信息如下：

# cat /sys/devices/platform/soc@3000000/2500000.uart/ctrl_info ier : 0x00 lcr : 0x00 mcr : 0x00 fcr : 0x00 dll : 0x4e dlh : 0x00 last baud : 19230 (dl = 78) TxRx Statistics: tx : 4443 rx : 3874 parity : 87 frame : 52 overrun: 0 throttled: 0 # cat /sys/devices/platform/soc@3000000/2500000.uart/dev_info id = 0 name = uart0 irq = 33 io_num = 2 port->mapbase = 0x02500000 port->membase = 0x2067c9f1 port->iobase = 0x00000000 port->fifosize = 64 pdata->regulator = 0x1d5654ac pdata->regulator_id = vcc-rs485 # # # cat /sys/devices/platform/soc@3000000/2500000.uart/ctrl_info ier : 0x05 lcr : 0x1b mcr : 0x03 fcr : 0xb1 dll : 0x08 dlh : 0x00 last baud : 187500 (dl = 8) TxRx Statistics: tx : 20313 rx : 15366 parity : 225 frame : 123 overrun: 0 throttled: 0 #

@laode123
1、ps看下sshd进程是否存在
2、which sshd看下此程序的路径
3、手动执行sshd看下运行情况

edp屏调试.log

disp-add-uboot-logo-to-kernel-logo-smooth-show.zip

t113的logo闪烁大概率不是这个补丁问题，你要自己找下原因了，补丁你也可以试下

18位模式到底要怎么驱动呢？

【已解决：可以显示渲染到屏幕中】

自己挖的坑还得自己解决😢

按照以上步骤配置好环境，引入该有的库文件

在main.cpp中，设置以下内容

#include "mainwindow.h" #include <QApplication> #include <QDebug> #include <tplayer.h> #include "User/tpmanager.h" #include <QLabel> int main(int argc, char *argv[]) { QApplication a(argc, argv); MainWindow w; //可以注释掉这个MainWindow w窗体，使它不可见。或者给他透明度，我这里给的是透明度 w.setWindowOpacity(0.5);//这句不起作用，冗余代码 w.show(); //绘制内容在tplayer视频上 QLabel* label = new QLabel(); label->setText("hello"); label->setStyleSheet("font-size:20px;color:#ff0000"); label->move(400,460); label->show(); qInfo() << "hello" ; TPlayer* tplayer = TPlayerCreate(CEDARX_PLAYER); TPlayerSetNotifyCallback(tplayer,myCallback,NULL); TPlayerSetDisplayRect(tplayer,0,0,800,640);//设置位置大小 if(TPlayerSetDataSource(tplayer,"http://192.168.0.123:9999/explorer?path=upload%2F2025-03%2F4.mp4",NULL) != 0) { printf("TPlayerSetDataSource() return fail.\n"); } else { printf("TPlayerSetDataSource() end\n"); } if(TPlayerPrepare(tplayer)!= 0) { printf("TPlayerPrepare return fail.\n"); }else{ printf("TPlayerPrepare end\n"); } if(TPlayerStart(tplayer) != 0) { printf("TPlayerStart() return fail.\n"); }else{ printf("started.\n"); } return a.exec(); }

效果图片:
捕获.JPG

我也想拉取329 的sdk ， 但是需要LV2， 请问你的SDK可以分享到百度网盘吗。谢谢。

@youyf 祝贺你

@frank2025 nnd
我自己改好了，多谢

&power_sply {
aldo1_vol = <1101800>;
aldo2_vol = <1101800>;
aldo4_vol = <1001800>;
bldo1_vol = <1800>;
bldo2_vol = <1001800>;
bldo4_vol = <1101800>;
cldo1_vol = <1001800>;
cldo3_vol = <1003300>;
cldo4_vol = <1103300>;
cpusldo_vol = <1000900>;
dcdc1_mode = <1>;
dcdc2_mode = <1>;
bc12_mode = <0>;
};

@youyf 去gittee下，很多人拉取了分支

@oct_linux 在 T113-S3 无法正常启动，之前一直报错 中说：

174560d9-760b-4daf-ae2d-91897aa24f3d-48ded797a915339da9466344dde2217.png

我遇到过类似现象，原因好像是改了调试串口，然后改得不太对导致UBOOT无打印日志，用NAND一直卡死，用TF卡启动等一段时间后进入系统了，不知道您是用什么启动？

9af45ef3-03da-4457-a2da-93ef85c964d1-image.png

找个做扫地机方案的公司，说你们要开案

@liufan301 A133是不是 就可以啊

@gegegeda 不一定需要网口，不过你要确认两点

这款USB的相机是否免驱 USB相机本身是否带私有适配协议，还是单独的USB摄像头
免驱，不带协议的摄像头的话，直接插入USB，会生成/dev/videoX，使用v4l2或者opencv库处理就可以了，如果有私有适配协议，去摄像头厂商那边申请驱动和应用demo，这个他们应该要给的。

@lyl20050926 用公司账户在全志客户服务平台上按流程注册就可以获取相关资料了

如果USB接口没有问题的话，需要换根线试试。

@fg_12933 会不会是硬件层没通

我也想知道……😊

> detect user environment: I0101 00:01:44.361453 1093 mpi_sys.c:1074] <MonitorEnvVarThread> /tmp/mpp_log_level I0101 00:01:44.361671 1093 mpi_sys.c:1075] <MonitorEnvVarThread> /tmp/mpp_venc_sei_config_param open /sys/class/sunxi_info/sys_info failed. I0101 00:01:44.407266 1082 ai_facekit.c:186] <ai_init> file:/mnt/extsd/pix_allwinner_facekit_v1.4.bin,size:2451836 load_file: /mnt/extsd/pix_allwinner_facekit_v1.4.bin **Fail to verify license key** E0101 00:01:44.465355 1082 ai_facekit.c:204] <ai_init> pix_init_facekit_model error status: -8888 open /sys/class/sunxi_info/sys_info failed. 0x000x000x000x000x000x000x000x000x040x000x000x000x2c0x000x000x000xd40xff0xff0x7f0x000x000x000x000x000x000x000x000x000x000x000x00 E0101 00:01:44.474221 1082 sample_facekit_demo.c:1520] <main> init error!

打开模型文件时提示验证license key错误，请问这个问题该怎么解决呢？

@sanchez https://whycan.com/t_8407.html

用ubuntu 16.04 安装好相关库就OK了。能留个连续方式吗。我的c200s tina 音视频方面编译报错，有没有大佬求助一下，还有gt911的驱动

@liaoxianze0804 可以通过代理商获取

@gegegeda 说法太宽泛，不能用的原因是什么，C库版本缺少接口，缺失动态库，还是直接执行报core segment异常，一句话不能使用，没法继续分析。

我已经在 linux-sunxi.org 网站找到了SD卡启动流程！！！
资料查找顺序：

linux-sunxi.org -> Community -> linux-sunxi community page -> Category:Community -> 2.1 Bring up your own hardware -> attempting to identify your hardware -> 3.1 Boards -> H5 Boards -> 根据自己的型号选择 -> Manual build -> Manual build howto ->Set up SD-Card for booting

```

dsi_panel: dsi_panel@0 {
compatible = "allwinner,panel-dsi";
status = "okay";
reg = <0>;

power0-supply = <&reg_cldo3>; power1-supply = <&reg_dcdc4>; power2-supply = <&reg_cldo1>; reset-gpios = <&pio PD 20 1 0 3 1>; reset-num = <1>;

// reset-delay-ms = <20>;
reset-on-sequence = <1 20>, <0 200>, <1 100>;

backlight = <&backlight0>; dsi,flags = <(MIPI_DSI_MODE_VIDEO | MIPI_DSI_MODE_VIDEO_BURST| MIPI_DSI_MODE_NO_EOT_PACKET)>;

// dsi,flags = <(MIPI_DSI_MODE_VIDEO)>;
dsi,lanes = <4>;
dsi,format = <0>;

panel-init-sequence = [ //Page0 15 00 02 E0 00 //--- PASSWORD ----// 15 00 02 E1 93 15 00 02 E2 65 15 00 02 E3 F8 15 00 02 80 03 //--- Sequence Ctrl ----// 15 00 02 70 10 15 00 02 71 13 15 00 02 72 06 15 00 02 75 03 //--- Page4 ----// 15 00 02 E0 04 15 00 02 2D 03 //--- Page1 ----// 15 00 02 E0 01 //--- BIST MODE ----// // 15 00 02 4A 35 //Set VCOM 15 00 02 00 00 15 00 02 01 5A //Set VCOM_Reverse 15 00 02 03 00 15 00 02 04 58 //Set Gamma Power 15 00 02 17 00 15 00 02 18 EF 15 00 02 19 01 15 00 02 1A 00 15 00 02 1B EF 15 00 02 1C 01 //Set Gate Power 15 00 02 1F 7A 15 00 02 20 24 15 00 02 21 24 15 00 02 22 4E // 15 00 02 24 F8 // 15 00 02 26 D3 //SetPanel 15 00 02 37 59 15 00 02 35 2C //SET RGBCYC 15 00 02 38 05 15 00 02 39 08 15 00 02 3A 10 15 00 02 3C 88 15 00 02 3D FF 15 00 02 3E FF 15 00 02 3F 7F //Set TCON 15 00 02 40 06 15 00 02 41 A0 15 00 02 43 14 15 00 02 44 0F 15 00 02 45 24 // 15 00 02 4A 80 //--- power voltage ----// 15 00 02 55 01 15 00 02 56 01 15 00 02 57 89 15 00 02 58 0A 15 00 02 59 0A //VCL = -2.5V 15 00 02 5A 39 //VGH = 18.4V 2D_VGH = 16V 15 00 02 5B 10 //VGL = -10.2V 15 00 02 5C 16 //--- Gamma ----// 15 00 02 5D 7A 15 00 02 5E 65 15 00 02 5F 56 15 00 02 60 49 15 00 02 61 43 15 00 02 62 33 15 00 02 63 35 15 00 02 64 1C 15 00 02 65 33 15 00 02 66 30 15 00 02 67 2E 15 00 02 68 4A 15 00 02 69 36 15 00 02 6A 3D 15 00 02 6B 2F 15 00 02 6C 2D 15 00 02 6D 23 15 00 02 6E 15 15 00 02 6F 04 15 00 02 70 7A 15 00 02 71 65 15 00 02 72 56 15 00 02 73 49 15 00 02 74 43 15 00 02 75 33 15 00 02 76 35 15 00 02 77 1C 15 00 02 78 33 15 00 02 79 30 15 00 02 7A 2E 15 00 02 7B 4A 15 00 02 7C 36 15 00 02 7D 3D 15 00 02 7E 2F 15 00 02 7F 2D 15 00 02 80 23 15 00 02 81 15 15 00 02 82 04 //Page2, for GIP 15 00 02 E0 02 //GIP_L Pin mapping 15 00 02 00 1E 15 00 02 01 1F 15 00 02 02 57 15 00 02 03 58 15 00 02 04 48 15 00 02 05 4A 15 00 02 06 44 15 00 02 07 46 15 00 02 08 40 15 00 02 09 1F 15 00 02 0A 1F 15 00 02 0B 1F 15 00 02 0C 1F 15 00 02 0D 1F 15 00 02 0E 1F 15 00 02 0F 42 15 00 02 10 1F 15 00 02 11 1F 15 00 02 12 1F 15 00 02 13 1F 15 00 02 14 1F 15 00 02 15 1F //GIP_R Pin mapping 15 00 02 16 1E 15 00 02 17 1F 15 00 02 18 57 15 00 02 19 58 15 00 02 1A 49 15 00 02 1B 4B 15 00 02 1C 45 15 00 02 1D 47 15 00 02 1E 41 15 00 02 1F 1F 15 00 02 20 1F 15 00 02 21 1F 15 00 02 22 1F 15 00 02 23 1F 15 00 02 24 1F 15 00 02 25 43 15 00 02 26 1F 15 00 02 27 1F 15 00 02 28 1F 15 00 02 29 1F 15 00 02 2A 1F 15 00 02 2B 1F //GIP_L_GS Pin mapping 15 00 02 2C 1F 15 00 02 2D 1E 15 00 02 2E 17 15 00 02 2F 18 15 00 02 30 07 15 00 02 31 05 15 00 02 32 0B 15 00 02 33 09 15 00 02 34 03 15 00 02 35 1F 15 00 02 36 1F 15 00 02 37 1F 15 00 02 38 1F 15 00 02 39 1F 15 00 02 3A 1F 15 00 02 3B 01 15 00 02 3C 1F 15 00 02 3D 1F 15 00 02 3E 1F 15 00 02 3F 1F 15 00 02 40 1F 15 00 02 41 1F //GIP_R_GS Pin mapping 15 00 02 42 1F 15 00 02 43 1E 15 00 02 44 17 15 00 02 45 18 15 00 02 46 06 15 00 02 47 04 15 00 02 48 0A 15 00 02 49 08 15 00 02 4A 02 15 00 02 4B 1F 15 00 02 4C 1F 15 00 02 4D 1F 15 00 02 4E 1F 15 00 02 4F 1F 15 00 02 50 1F 15 00 02 51 00 15 00 02 52 1F 15 00 02 53 1F 15 00 02 54 1F 15 00 02 55 1F 15 00 02 56 1F 15 00 02 57 1F //GIP Timing 15 00 02 58 40 15 00 02 59 00 15 00 02 5A 00 15 00 02 5B 30 15 00 02 5C 05 15 00 02 5D 30 15 00 02 5E 01 15 00 02 5F 02 15 00 02 60 30 15 00 02 61 03 15 00 02 62 04 15 00 02 63 6A 15 00 02 64 6A 15 00 02 65 75 15 00 02 66 0D 15 00 02 67 73 15 00 02 68 09 15 00 02 69 6A 15 00 02 6A 6A 15 00 02 6B 08 15 00 02 6C 00 15 00 02 6D 04 15 00 02 6E 00 15 00 02 6F 88 15 00 02 70 00 15 00 02 71 00 15 00 02 72 06 15 00 02 73 7B 15 00 02 74 00 15 00 02 75 BC 15 00 02 76 00 15 00 02 77 0D 15 00 02 78 23 15 00 02 79 00 15 00 02 7A 00 15 00 02 7B 00 15 00 02 7C 00 15 00 02 7D 03 15 00 02 7E 7B //Page4 15 00 02 E0 04 15 00 02 2B 2B 15 00 02 2E 44 //Page0 15 00 02 E0 00 15 00 02 E6 02 15 00 02 E7 02 05 78 01 11 05 05 01 29 // 15 00 02 35 00 ]; display-timings { native-mode = <&timing0>; timing0: timing0 { clock-frequency = <76800000>; hback-porch = <80>; hactive = <800>; hfront-porch = <80>; hsync-len = <20>; vback-porch = <12>; vactive = <1280>; vfront-porch = <20>; vsync-len = <4>; }; }; port { panel0_in: endpoint@0 { reg = <0>; remote-endpoint = <&panel_output_0>; }; }; };

};

&dsi0 {
status = "okay";
pinctrl-0 = <&dsi0_4lane_pins_a>;
pinctrl-1 = <&dsi0_4lane_pins_b>;
pinctrl-names = "active","sleep";

ports { dsi0_out: port@1{ dsi_out_panel: endpoint { remote-endpoint = <&panel_input>; }; }; }; panel: panel@0 { compatible = "allwinner,virtual-panel"; status = "okay"; reg = <0>; ports { panel_in: port@0 { reg = <0>; panel_input: endpoint@0 { reg = <0>; remote-endpoint = <&dsi_out_panel>; }; }; panel_out: port@1 { reg = <1>; panel_output_0: endpoint@0 { reg = <0>; remote-endpoint = <&panel0_in>; }; }; }; };

};
&sunxi_drm {
route {
disp0_dsi0 {
logo,uboot = "bootlogo.bmp";
status = "okay";
};
disp0_lvds0 {
status = "disabled";
};
disp0_lvds1 {
status = "disabled";
};
};
};

https://docs.aw-ol.com/docs/soc/v821/faq/sdk_debug#打包报错-error-update_mbr-failed