R328-S1有原厂的 FreeRTOS SDK，具体可以与FAE沟通开案

Linux_Audio_Development_Guide.pdf

@q2022

76ddd24c-2050-4390-bcff-f24e85a504a8-image.png

抱歉，看错了，PD10 是复用5

@whycanservice 哈喽，谢谢您的回复，我是想 win10 环境下编译的，需要如何配置编译环境呢？

@allwinnertech 你好，正在用100ask-T113-Pro开发板，百度网盘下载的Tina-SDK，然后按照你的方法修改配置使能以太网，编译运行后出现问题：
61ccbc39-0b4f-4095-8af4-5ea3deebc74d-image.png

查看log: PE10有冲突
93ac447c-9bf7-4dce-b13c-5c66a181c6e8-image.png

查看board.dts,PE10是 PHY_RST 脚，不知道为啥会冲突
26b90d48-9d3b-44d3-b55b-149fea0b4f5d-image.png
df453210-d622-46eb-adbc-2899ddb63c22-image.png

@whycanservice 是使用non-tunnel 模式进行组件的连接嘛？

/libexec/gcc/arm-linux-gnueabi/4.6.3/cc1: error while loading shared libraries: libz.so.1: cannot open shared object file: No such file or directory

感觉是不是系统太新了，Ubuntu 14.04可以吗

@anruliu 我搞定了，感谢感谢！！ 这样就可以了

static lv_style_t style_scr_act; lv_style_init(&style_scr_act); lv_style_set_bg_opa(&style_scr_act, LV_OPA_TRANSP); lv_obj_add_style(lv_scr_act(), &style_scr_act, 0); lv_disp_set_bg_opa(lv_scr_act(), LV_OPA_TRANSP);

@livpo 我也遇到类似的问题，还没解决😞

1b9e4c3b-722c-451e-9883-74aeb545e855-image.png

@yuwei 看看有没有这个 package/allwinner/tina_multimedia_demo/encodertest

@wyljkl 实际上就是reboot efex无效导致的，换上面介绍的方式操作吧

@rtqqq 可以试试先通过 mm -B命令进行编译

可以直接取代sbi的位置

@emperg VE还在解码，可其他模块把buf释放了？应该在解码的回调函数才可以释放buf吧

@yuwei 编码的问题，试试换种编码格式或者确认你的平台支持哪些编码格式

@qq354813374 你这个修改就是为了使用uart0作为串口输出吗？

@qinlinbin 在 一个补丁，让D1-H的SDK支持T113芯片 中说：

@jr_online 安装bison

好滴，谢谢大佬，我试试。

@lxs123 menuconfig里取消就行了

@xiaowenge 大家确实没拿到板子，哈哈哈

@whycanservice adb进去的终端 控制台。额我突然发现，我从串口进终端就行了。哈哈，傻了

@whycanservice 三剋有

按键可以用Linux内置的驱动gpio-keys，提供轮训中断等多种查询方式，而且直接对接了linux的event系统开发也很简单

v853 npu 模型转换后输出的模板代码，将其编译缺少相关库
https://bbs.aw-ol.com/topic/2586/share/4

@carpediem ovxlib目前不提供arm版本的库，还在适配中，由于版本更新新版本的模型运行可以参考vpm_run的代码，使用vpm_run来调用npu与模型。

@mengxp 是的读取chipid然后&0xffff就行了，具体对应关系需要自己试一下

@ceoifung @WhycanService 找到问题了，原来是改完之后，调试发现，程序进不去u-boot界面😵 所以也就没有办法进入LCD初始化那里，拉高相关的电平了

@xiaowenge 看了arm官方的M4介绍还以为M4内核默认都支持DSP指令了😳

你就理解为一个文件吧，反正Linux一切皆文件

@cruise33 在 qt5下怎么调用摄像头？ 中说：

@xiaowenge 在 qt5下怎么调用摄像头？ 中说：

要用摄像头可以试下这个：https://mp.weixin.qq.com/s?__biz=Mzg3OTc1NzU2Mg==&mid=2247486025&idx=1&sn=a02e256c60f9c70559780d42911ea524&chksm=cf7edbdcf80952ca07822cb4dac710b9e6c18413c20700089c1f1081869fb9c6f976cff0f740&token=748259646&lang=zh_CN#rd为啥
要用QT5？V853的性能 不适合QT5

是开发GUI程序的话，v853不建议用QT5的意思吗？

是的

@chris98 在 r328如何扩展内存 中说：

最近需要扩展r328的内存，请教各位大佬要怎么样才能扩展内存

你直接上ddr更大的版本吧，sip DDR的芯片物理扩内存机会是不可能的

@laocai 没有对应文档

@how0723 @whycan

@whycan
f50760bb-6fcc-4b8c-8cb5-65c2f872e968-image.png

sunxifb_init(rotated) 这个函数定义在lvgl,开机校准这个界面不能用这个函数，还是没法旋转这个校准界面，

@adaofu01 HIFI4 的DSP需要专用的编译器，这个编译器需要向Cadence 购买授权，也可以咨询全志FAE获得授权。目前暂无第三方编译器支持这个DSP。由于授权协议问题，需要连上授权服务器使用。

@whycan webwxgetmsgimg.jpg

@lyscut 要在哪里设置呢？

@dyd2022 请问一下，您uboot可以显示logo吗？ 我内核可以驱动lcd 并显示了，移植到uboot,设备树设置了跟内核一样，图片也换了相同分辨率的，但是uboot还是没有显示logo,大概是什么问题呢?大佬可以贴下您uboot 的设备树文件吗？

@whycanservice 好的，多谢！

@lijinlin001 将上面的补丁保存为一个文件并放在 tina/package/system/procd/patches 目录下就可以了，不是内核的修改，是应用包的补丁。

新人交流学习一下

7331f232-c39b-4bd4-ba12-1d12df8490c7-2c58a4f4c7790e648129a0bb0836d26.jpg

ce4a3905-259f-4378-8ac7-a8cac05bcd6f-0407d41316c3829055f6975bd0da0fa.jpg

谢谢百问网韦老师高老师，可以开始折腾了。

淘宝上面有免MCLK，免I2C配置的I2S模块，要不要先用这种试一试？

@anruliu 感谢回复！按照这个路径也没有找到这个文件，然后我就换了一种方法，挂载一个目录到boot-resource分区，然后换成我的logo但是开机之后也没有显示！

@null037 在 100ASK百问网 D1s/T113-s3开发板 适配ov5640 中说：

，插入电脑中，即可查看到刚刚在T113开发板上使用ov5640拍摄的5张照片

强烈建议光速适配下MQ-R😊

@yanmingjian 前辈你好，我用编译器版本为240的取编译，cmake的时候出现这样的问题，Test NCNN_COMPILER_USE_VFREDSUM - Failed

-- Check for working CXX compiler: /home/zcm/linux/tool/Xuantie-900-gcc-linux-5.10.4-glibc-x86_64-V2.4.0/bin/riscv64-unknown-linux-gnu-g++ - skipped -- Detecting CXX compile features -- Detecting CXX compile features - done -- Performing Test NCNN_COMPILER_SUPPORT_RVV -- Performing Test NCNN_COMPILER_SUPPORT_RVV - Success -- Performing Test NCNN_COMPILER_SUPPORT_RVV_ZFH -- Performing Test NCNN_COMPILER_SUPPORT_RVV_ZFH - Success -- Performing Test NCNN_COMPILER_USE_VFREDSUM -- Performing Test NCNN_COMPILER_USE_VFREDSUM - Failed -- Performing Test NCNN_COMPILER_USE_VFREDUSUM -- Performing Test NCNN_COMPILER_USE_VFREDUSUM - Success -- Performing Test NCNN_COMPILER_USE_RVV_PLAIN_SEG -- Performing Test NCNN_COMPILER_USE_RVV_PLAIN_SEG - Success -- Target arch: riscv

然后编译的时候，没办法正常通过，前辈知道是什么问题吗？

In file included from /home/zcm/linux/Open_lib/ncnn/src/layer/riscv/riscv_activation.h:22, from /home/zcm/linux/Open_lib/ncnn/src/layer/riscv/convolution_riscv.cpp:25: /home/zcm/linux/Open_lib/ncnn/src/layer/riscv/rvv_mathfun.h: In function 'vfloat32m1_t sigmoid_ps(vfloat32m1_t, size_t)': /home/zcm/linux/Open_lib/ncnn/src/layer/riscv/rvv_mathfun.h:362:43: error: 'vfrec7_v_f32m1' was not declared in this scope; did you mean 'vfneg_v_f32m1'? 362 | vfloat32m##LMUL##_t _reciprocal = vfrec7_v_f32m##LMUL(_v, vl); \ | ^~~~~~~~~~~~~ /home/zcm/linux/Open_lib/ncnn/src/layer/riscv/rvv_mathfun.h:368:1: note: in expansion of macro '_RVV_FLOAT32_SIGMOID_OP' 368 | _RVV_FLOAT32_SIGMOID_OP(1, 32) | ^~~~~~~~~~~~~~~~~~~~~~~ /home/zcm/linux/Open_lib/ncnn/src/layer/riscv/rvv_mathfun.h: In function 'vfloat32m2_t sigmoid_ps(vfloat32m2_t, size_t)': /home/zcm/linux/Open_lib/ncnn/src/layer/riscv/rvv_mathfun.h:362:43: error: 'vfrec7_v_f32m2' was not declared in this scope; did you mean 'vfneg_v_f32m2'? 362 | vfloat32m##LMUL##_t _reciprocal = vfrec7_v_f32m##LMUL(_v, vl); \ | ^~~~~~~~~~~~~ /home/zcm/linux/Open_lib/ncnn/src/layer/riscv/rvv_mathfun.h:369:1: note: in expansion of macro '_RVV_FLOAT32_SIGMOID_OP' 369 | _RVV_FLOAT32_SIGMOID_OP(2, 16) | ^~~~~~~~~~~~~~~~~~~~~~~ /usr/bin/cmake: /usr/local/lib/libcurl.so.4: no version information available (required by /usr/bin/cmake) [ 21%] Building CXX object src/CMakeFiles/ncnn.dir/layer/elu.cpp.o /home/zcm/linux/Open_lib/ncnn/src/layer/riscv/rvv_mathfun.h: In function 'vfloat32m4_t sigmoid_ps(vfloat32m4_t, size_t)': /home/zcm/linux/Open_lib/ncnn/src/layer/riscv/rvv_mathfun.h:362:43: error: 'vfrec7_v_f32m4' was not declared in this scope; did you mean 'vfneg_v_f32m4'? 362 | vfloat32m##LMUL##_t _reciprocal = vfrec7_v_f32m##LMUL(_v, vl); \ | ^~~~~~~~~~~~~ /home/zcm/linux/Open_lib/ncnn/src/layer/riscv/rvv_mathfun.h:370:1: note: in expansion of macro '_RVV_FLOAT32_SIGMOID_OP' 370 | _RVV_FLOAT32_SIGMOID_OP(4, 8) | ^~~~~~~~~~~~~~~~~~~~~~~ /home/zcm/linux/Open_lib/ncnn/src/layer/riscv/rvv_mathfun.h: In function 'vfloat32m8_t sigmoid_ps(vfloat32m8_t, size_t)': /home/zcm/linux/Open_lib/ncnn/src/layer/riscv/rvv_mathfun.h:362:43: error: 'vfrec7_v_f32m8' was not declared in this scope; did you mean 'vfneg_v_f32m8'? 362 | vfloat32m##LMUL##_t _reciprocal = vfrec7_v_f32m##LMUL(_v, vl); \ | ^~~~~~~~~~~~~ /home/zcm/linux/Open_lib/ncnn/src/layer/riscv/rvv_mathfun.h:371:1: note: in expansion of macro '_RVV_FLOAT32_SIGMOID_OP' 371 | _RVV_FLOAT32_SIGMOID_OP(8, 4) | ^~~~~~~~~~~~~~~~~~~~~~~ In file included from /home/zcm/linux/Open_lib/ncnn/src/layer/riscv/riscv_activation.h:23, from /home/zcm/linux/Open_lib/ncnn/src/layer/riscv/convolution_riscv.cpp:25: /home/zcm/linux/Open_lib/ncnn/src/layer/riscv/rvv_mathfun_fp16s.h: In function 'vfloat16m1_t sigmoid_ps(vfloat16m1_t, size_t)': /home/zcm/linux/Open_lib/ncnn/src/layer/riscv/rvv_mathfun_fp16s.h:362:43: error: 'vfrec7_v_f16m1' was not declared in this scope; did you mean 'vfneg_v_f16m1'? 362 | vfloat16m##LMUL##_t _reciprocal = vfrec7_v_f16m##LMUL(_v, vl); \ | ^~~~~~~~~~~~~ /home/zcm/linux/Open_lib/ncnn/src/layer/riscv/rvv_mathfun_fp16s.h:368:1: note: in expansion of macro '_RVV_FLOAT16_SIGMOID_OP' 368 | _RVV_FLOAT16_SIGMOID_OP(1, 16) | ^~~~~~~~~~~~~~~~~~~~~~~ /home/zcm/linux/Open_lib/ncnn/src/layer/riscv/rvv_mathfun_fp16s.h: In function 'vfloat16m2_t sigmoid_ps(vfloat16m2_t, size_t)': /home/zcm/linux/Open_lib/ncnn/src/layer/riscv/rvv_mathfun_fp16s.h:362:43: error: 'vfrec7_v_f16m2' was not declared in this scope; did you mean 'vfneg_v_f16m2'? 362 | vfloat16m##LMUL##_t _reciprocal = vfrec7_v_f16m##LMUL(_v, vl); \ | ^~~~~~~~~~~~~ /home/zcm/linux/Open_lib/ncnn/src/layer/riscv/rvv_mathfun_fp16s.h:369:1: note: in expansion of macro '_RVV_FLOAT16_SIGMOID_OP' 369 | _RVV_FLOAT16_SIGMOID_OP(2, 8) | ^~~~~~~~~~~~~~~~~~~~~~~ /home/zcm/linux/Open_lib/ncnn/src/layer/riscv/rvv_mathfun_fp16s.h: In function 'vfloat16m4_t sigmoid_ps(vfloat16m4_t, size_t)': /home/zcm/linux/Open_lib/ncnn/src/layer/riscv/rvv_mathfun_fp16s.h:362:43: error: 'vfrec7_v_f16m4' was not declared in this scope; did you mean 'vfneg_v_f16m4'? 362 | vfloat16m##LMUL##_t _reciprocal = vfrec7_v_f16m##LMUL(_v, vl); \ | ^~~~~~~~~~~~~ /home/zcm/linux/Open_lib/ncnn/src/layer/riscv/rvv_mathfun_fp16s.h:370:1: note: in expansion of macro '_RVV_FLOAT16_SIGMOID_OP' 370 | _RVV_FLOAT16_SIGMOID_OP(4, 4) | ^~~~~~~~~~~~~~~~~~~~~~~ /home/zcm/linux/Open_lib/ncnn/src/layer/riscv/rvv_mathfun_fp16s.h: In function 'vfloat16m8_t sigmoid_ps(vfloat16m8_t, size_t)': /home/zcm/linux/Open_lib/ncnn/src/layer/riscv/rvv_mathfun_fp16s.h:362:43: error: 'vfrec7_v_f16m8' was not declared in this scope; did you mean 'vfneg_v_f16m8'? 362 | vfloat16m##LMUL##_t _reciprocal = vfrec7_v_f16m##LMUL(_v, vl); \ | ^~~~~~~~~~~~~

@whycan

微信截图_20221118122207.png
DDR跑通了

@whycan 哈哈大哥用的就是你开源的那个板子（自己改造了一下），再请教你一个问题行吗？烧录不对会不会和固件有关系，用SD卡烧录的方法，直接识别不到SD存在。

@yixiuge 我是想在编译阶段，打包后就弄过去，这样生产后就不用每台设备都去设置了

@liefyuan 85116494-e99d-4520-bb94-fb7fde1d0510-image.png
在内核配置中选上这几项。

修改了一下board.dts文件中摄像头设备树：

&vind0 { csi_top = <378000000>; csi_isp = <327000000>; status = "okay"; /* enable twi and ver1 spi-nand max freq 30M */ sensor0: sensor@5809470 { reg = <0x0 0x05809470 0x0 0x10>; device_type = "sensor0"; compatible = "allwinner,sunxi-sensor"; sensor0_mname = "ov5640"; sensor0_twi_cci_id = <2>; sensor0_twi_addr = <0x78>; sensor0_mclk_id = <0>; sensor0_pos = "rear"; sensor0_isp_used = <0>; sensor0_fmt = <0>; sensor0_stby_mode = <0>; sensor0_vflip = <0>; sensor0_hflip = <0>; sensor0_iovdd-supply = <>; sensor0_iovdd_vol = <>; sensor0_avdd-supply = <>; sensor0_avdd_vol = <>; sensor0_dvdd-supply = <>; sensor0_dvdd_vol = <>; sensor0_power_en = <>; sensor0_reset = <&pio PB 5 GPIO_ACTIVE_LOW>; sensor0_pwdn = <&pio PB 4 GPIO_ACTIVE_LOW>; flash_handle = <&flash0>; act_handle = <&actuator0>; sensor0_sm_vs = <>; device_id = <0>; status = "okay"; }; vinc0: vinc@5809000 { compatible = "allwinner,sunxi-vin-core"; device_type = "vinc0"; reg = <0x0 0x05809000 0x0 0x200>; interrupts = <GIC_SPI 95 IRQ_TYPE_LEVEL_HIGH>; vinc0_csi_sel = <0>; vinc0_mipi_sel = <0xff>; vinc0_isp_sel = <0>; vinc0_tdm_rx_sel = <0xff>; vinc0_rear_sensor_sel = <0>; vinc0_front_sensor_sel = <0>; vinc0_sensor_list = <0>; device_id = <0>; iommus = <&mmu_aw 1 1>; status = "okay"; }; };

还是识别不出来：

[ 3.282172] get ctp_gesture_wakeup fail, no gesture wakeup [ 3.288343] gt9xxnew_ts 2-0014: 2-0014 supply ctp not found, using dummy regulator [ 3.481837] input: gt9xxnew_ts as /devices/virtual/input/input1 [ 3.489803] vin_csi 5801000.csi: Adding to iommu group 0 [ 3.496961] sunxi-vin-core 5809000.vinc: Adding to iommu group 0 [ 3.505032] [VIN_WARN]get csi isp clk fail [ 3.509630] [VIN_WARN]get csi isp src clk fail [ 3.514654] [VIN_WARN]get csi mipi clk fail [ 3.519368] [VIN_WARN]get csi mipi src clk fail [ 3.524528] [VIN_WARN]get csi isp clk fail [ 3.529139] [VIN_WARN]Get isp reset control fail [ 3.535348] ov5640 2-003c: endpoint node not found [ 3.540781] ov5640: probe of 2-003c failed with error -22 [ 3.547061] [VIN_ERR]registering ov5640, No such device! [ 3.553072] [VIN]vinc1 is null

检测一下twi2:

root@TinaLinux:/# i2cdetect -r -y 2 0 1 2 3 4 5 6 7 8 9 a b c d e f[ 54.824048] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x3) 00: [ 54.836025] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x4) -- [ 54.844682] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x5) -- [ 54.852541] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x6) -- [ 54.860239] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x7) -- [ 54.868087] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x8) -- [ 54.875834] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x9) -- [ 54.883681] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0xa) -- [ 54.891383] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0xb) -- [ 54.899259] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0xc) -- [ 54.906986] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0xd) -- [ 54.914835] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0xe) -- [ 54.922575] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0xf) -- [ 54.930413] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x10) -- 10: [ 54.938256] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x11) -- [ 54.946718] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x12) -- [ 54.954545] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x13) -- -- UU [ 54.962535] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x15) -- [ 54.970826] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x16) -- [ 54.978822] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x17) -- [ 54.986731] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x18) -- [ 54.994696] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x19) -- [ 55.002636] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x1a) -- [ 55.010581] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x1b) -- [ 55.018499] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x1c) -- [ 55.026460] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x1d) -- [ 55.034387] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x1e) -- [ 55.042367] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x1f) -- [ 55.050271] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x20) 20: [ 55.058255] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x21) -- [ 55.066336] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x22) -- [ 55.074257] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x23) -- [ 55.082110] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x24) -- [ 55.090020] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x25) -- [ 55.097940] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x26) -- [ 55.105815] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x27) -- [ 55.113658] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x28) -- [ 55.121588] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x29) -- [ 55.129446] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x2a) -- [ 55.137367] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x2b) -- [ 55.145219] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x2c) -- [ 55.153160] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x2d) -- [ 55.160974] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x2e) -- [ 55.168954] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x2f) -- [ 55.176780] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x30) -- 30: [ 55.184736] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x31) -- [ 55.193067] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x32) -- [ 55.200995] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x33) -- [ 55.208838] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x34) -- [ 55.216787] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x35) -- [ 55.224659] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x36) -- [ 55.232561] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x37) -- [ 55.240402] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x38) -- -- [ 55.249135] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x39) -- [ 55.257044] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x3a) -- [ 55.265065] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x3b) -- [ 55.272997] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x3c) -- [ 55.280979] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x3d) -- [ 55.288888] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x3e) -- [ 55.300106] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x3f) -- [ 55.308076] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x40) 40: [ 55.316033] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x41) -- [ 55.324132] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x42) -- [ 55.332082] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x43) -- [ 55.339879] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x44) -- -- [ 55.352152] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x45) -- [ 55.360282] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x46) -- [ 55.368419] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x47) -- [ 55.376354] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x48) -- [ 55.384355] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x49) -- [ 55.392276] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x4a) -- [ 55.400230] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x4b) -- [ 55.408181] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x4c) -- [ 55.416142] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x4d) -- [ 55.424060] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x4e) -- [ 55.432039] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x4f) -- [ 55.439945] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x50) 50: [ 55.447902] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x51) -- [ 55.455990] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x52) -- -- [ 55.463976] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x53) -- [ 55.472029] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x54) -- [ 55.479979] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x55) -- [ 55.487938] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x56) -- [ 55.495928] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x57) -- [ 55.503856] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x58) -- [ 55.511822] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x59) -- [ 55.519709] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x5a) -- [ 55.527702] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x5b) -- [ 55.535611] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x5c) -- [ 55.543571] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x5d) -- [ 55.551468] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x5e) -- [ 55.559440] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x5f) -- [ 55.567404] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x60) 60: [ 55.575348] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x61) -- [ 55.583464] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x62) -- [ 55.591380] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x63) -- [ 55.599221] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x64) -- [ 55.607176] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x65) -- [ 55.615037] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x66) -- [ 55.622938] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x67) -- [ 55.630767] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x68) -- [ 55.638706] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x69) -- [ 55.646597] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x6a) -- [ 55.654491] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x6b) -- [ 55.662334] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x6c) -- [ 55.670262] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x6d) -- [ 55.678121] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x6e) -- [ 55.686038] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x6f) -- [ 55.693914] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x70) -- 70: [ 55.701841] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x71) -- [ 55.710176] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x72) -- [ 55.718109] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x73) -- [ 55.725955] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x74) -- [ 55.733927] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x75) -- [ 55.741765] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x76) -- [ 55.749673] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x77) -- --

真的好想要芒果派呀

另外请问PD端口的VCC需要给1.8V吗？屏的IO电压是1.8V

@yuwei001 百问网淘宝店

@zxyuser 我也遇到过这个问题，已经解决，是线接触不良造成的，导致找不到芯片，重新接线或者换根线就可以解决。

相同板子，处理器是D1s, 继续测试RTL8189FS，却很稳定，没有出现问题

while true; do iperf3 -c 192.168.3.105; done

Connecting to host 192.168.3.105, port 5201
[ 5] local 192.168.3.118 port 50282 connected to 192.168.3.105 port 5201
Connecting to host 192.168.3.105, port 5201
[ 5] local 192.168.3.118 port 50286 connected to 192.168.3.105 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 2.83 MBytes 23.7 Mbits/sec 0 211 KBytes
[ 5] 1.00-2.00 sec 2.98 MBytes 25.0 Mbits/sec 0 211 KBytes
[ 5] 2.00-3.00 sec 2.67 MBytes 22.4 Mbits/sec 0 211 KBytes
[ 5] 3.00-4.00 sec 2.70 MBytes 22.7 Mbits/sec 0 211 KBytes
[ 5] 4.00-5.00 sec 2.69 MBytes 22.5 Mbits/sec 0 211 KBytes
[ 5] 5.00-6.00 sec 2.92 MBytes 24.4 Mbits/sec 0 211 KBytes
[ 5] 6.00-7.00 sec 3.00 MBytes 25.2 Mbits/sec 0 211 KBytes
[ 5] 7.00-8.00 sec 2.88 MBytes 24.2 Mbits/sec 0 211 KBytes
[ 5] 8.00-9.00 sec 2.79 MBytes 23.4 Mbits/sec 0 211 KBytes
[ 5] 9.00-10.00 sec 2.78 MBytes 23.3 Mbits/sec 0 211 KBytes

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 28.2 MBytes 23.7 Mbits/sec 0 sender
[ 5] 0.00-10.00 sec 28.0 MBytes 23.5 Mbits/sec receiver

iperf Done.
Connecting to host 192.168.3.105, port 5201
[ 5] local 192.168.3.118 port 50290 connected to 192.168.3.105 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.05 sec 3.23 MBytes 25.7 Mbits/sec 0 208 KBytes
[ 5] 1.05-2.00 sec 2.34 MBytes 20.8 Mbits/sec 0 222 KBytes
[ 5] 2.00-3.00 sec 2.94 MBytes 24.7 Mbits/sec 0 222 KBytes
[ 5] 3.00-4.00 sec 2.75 MBytes 23.0 Mbits/sec 0 222 KBytes
[ 5] 4.00-5.00 sec 2.92 MBytes 24.5 Mbits/sec 0 222 KBytes
[ 5] 5.00-6.00 sec 2.71 MBytes 22.7 Mbits/sec 0 222 KBytes
[ 5] 6.00-7.00 sec 2.74 MBytes 23.0 Mbits/sec 0 222 KBytes
[ 5] 7.00-8.00 sec 2.81 MBytes 23.6 Mbits/sec 0 222 KBytes
[ 5] 8.00-9.00 sec 2.66 MBytes 22.4 Mbits/sec 0 222 KBytes
[ 5] 9.00-10.00 sec 2.63 MBytes 22.1 Mbits/sec 0 222 KBytes

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 27.7 MBytes 23.3 Mbits/sec 0 sender
[ 5] 0.00-10.00 sec 27.7 MBytes 23.2 Mbits/sec receiver

iperf Done.

@xiaowenge 在 PnpFe|In： 非法ID 中说：

@rayzhang 在 PnpFe|In： 非法ID 中说：

@chengwei_peng hello 固件没问题。 现在不用说点击“烧录”，这些错误是已插入 USB 就出现的 😧

楼上说得对，接串口看吧，光看弹窗诊断肯定是解决不了问题的

破案了😧 机器没有彻底关机，后来强刷可以刷成功了。

总体来说，应该是之前设备刷机刷一半导致线刷报错（一插USB就报错），没有彻底关机成功

@q2022

提示错误bison not found，

执行apt-get install bison

https://oshwhub.com/GloomyGhost/84fd91f588d144bcbf3b3d343d0d8a4b

开源了一个R328的板子

@gsd_zcm 这个是d1的空间不够，在menuconfig的base system里配置下

感觉好厉害的样子哇！！

@whycanservice 在 【萌新】t113(tina)进入kernel时如何优先加载某个驱动？ 中说：

https://v853.docs.aw-ol.com/soft/soft_start/

可以手动配置wifi的执行顺序，wifi初始化完成后再开lvgl

好滴，谢谢大佬指点，我试一试。

@chengwei_peng 谢谢前辈，讲解的好详细

@gongweijie -J1看看

@null037 第三方的camera应用，在全志平台不一定可以用起来的，全志平台需要的一些必不可少的ioctl，在第三方应用不一定有支持，如果你一定需要使用第三方应用，可能需要给第三方应用打补丁了。具体参考camerademo。

@lyscut 代表后面的SDK更新它被人遗忘了，不影响，只要在SDK中的，肯定是有些平台验证过的。

可以的，但是那样裁剪后就没多少地方放东西了，6mb的kernel，1mb的rootfs太极限了

@wankle 我也遇到了这个问题，你解决了吗？

@xiaowenge 这个问题麻烦您了，帮忙看看

@litengos 在 D1-H v2.1 SDK问题 中说：

服务平台的V2.0版本和2.1的repo下载地址是一样的，我下载的是2.1还是2.0版本？2.1版本怎么下载？？

是一样的，同一个仓库，不同版本会在这个仓库基础上不断迭代。你随便进一个具体的git仓库，比如package啥的，git log就能看到v2.0的版本，切回去就是旧版本了

@msh410278586 解决了，按照你的方法可以了

@wyljkl
我找到问题了，这个引脚的配置不能这样配置，改成这样就可以了，感谢各位大佬！
74f85890-3719-4292-948b-e962aecf2f79-image.png