@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) -- --

@whycanservice 原理图.png
这是我的原理图

真的好想要芒果派呀

@georgelzh d1s

另外请问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

@yixiuge 在 试一试用 全志 A133 LCD0 PD0-PD9 驱动 15寸的LVDS电脑显示屏 中说：

1d5190b2-490b-4787-aff5-967611f42344-8bde19c807a83ced16911a920caf8b3.jpg

双屏显示 OK

大佬，最近也在搞A133的双屏显示，MIPI+单8LVDS，单个屏幕都可以了，双屏怎么都没配好，能分享一下这个双屏显示的dts文件不？
谢谢！

@whycanservice 很奏效，药到病除😊

看一下配置的VIPP通路

@lijinfeng xfel把JTAG打开，应该就可以连接得上了吧，你试试。

最近在研究一个核心跑 RT-Thread，另外一个核跑 linux 。
AMP通信配合工作

@gsd_zcm 在 希望全志的大神出一个D1s tina APP怎么引用其他库文件的教程 中说：

@chengwei_peng 谢谢前辈，讲解的好详细，按照前辈的方法，代码可以正常编译了，下面是我的makefile，可能有些地方不够好，伙伴们可以参考下。

注释好详细，感谢分享！

@chengwei_peng 好的，谢谢前辈，我去看看

@chengwei_peng
export后查看引脚属性，依旧是spi3功能没变，我再检查一下是不是我的测波形的方法不对，感谢指导。谢谢

QQ截图20221114131915.png

不大，单纯驱动摄像头不用啥电，主要看摄像头本身的功耗，还有就是图像进来之后要不要做复杂的图像处理。

@chris98 你要先确认lcd7789是什么协议驱动的lcd，r328没有disp模块，不能驱动rgb,lvds,mipi dsi等协议的lcd

@theoldfisherman 在 添加库 中说：

@jr_online 谢谢你，又多了一个解决方法

得谢谢大佬@WhycanService

@yuzukitsuru

7930b498-20a8-4988-ad72-37e483f1a0b1-image.png

发现2/5/6 没有上拉.

@lijinlin001 是不是IO的电压没有设置或者是IO耐压值没有配置正确，IO耐压值一般有1.8V和3.3V

@whycanservice 好的，多谢！

@yuzukitsuru 问题点找到了

1> jffs2 CRC的问题
由于内核 SLAB allocator选择错误[SLOB]导致，改回SLUB正常。不知道上一个项目的人出于什么目的调整了。具体是否允许改该配置，或者改了为什么会导致spi-mem读数据异常，当前还不知道。

2> 挂载异常问题
mkfs.jffs2工具需要sdk buildroot中自带编译出的，否者换其他版本会挂载异常。

3> 向文件系统写入数据重启挂载异常
如果内核开启了jffs2 summary选项，需要使用sumtool工具处理mkfs.jffs2做好的文件。

@gsd_zcm 问题解决，需要在顶层文件夹先
source build/envsetup.sh
lunch
最后在make menuconfig

@kelsey
1、针对于rootfs：target/allwinner/d1-h-nezha/defconfig=> .config

fb95fa8a-211d-409b-956a-ded916afa5f9-图片.png

2、针对于kernel：device/config/chips/d1-h/configs/nezha/linux-5.4/config-5.4=> lichee/linux-5.4/.config

8b805478-dd51-4ad2-8584-5d27a6f6056f-图片.png

@zhujun19790920 直接可以用，直接替换pin2pin的

@null037 有没有完整的输出

@fanfan 看一下configs/default/image.cfg对不对

@q1215200171 收到，感谢，可以了

@thepresent ok 谢谢！！

这个问题是openssl版本问题，因为我不是按照建议的ubuntu14.04而是wsl2 ubuntu20.04环境编译的，所以遇到的这个问题可能大家一般不会遇到，后来各种搜索资料解决了，这里说一下方法了结这个问题。
查看openssl版本，通过apt降级到1.1.0版本（SDK里是1.1.0.i），之后手动删除out目录下之前openssl的编译输出，然后重新编译就好了。
3cadb9fe-ed9f-4590-96e9-cca7a001dd8b-image.png

@ming899 官方的视频教程提到tina sdk uboot 开启lcd的显示，内核就不走开屏流程了，进内核后可以休眠唤醒打开屏

赶紧啃一啃摄像头相关，没有大佬带，完全玩不转~

恭喜恭喜👏 👏

@chunzhang
查询./scripts/pack_img.sh发现./tools/pack-bintools/src/fsbuild这个程序是32位的, 所以安装以下组件可解决问题:

apt-get install lib32z1 lib32z1-dev

@sdshanlei201314 我没有用SDK，kernel 应该tina复制出来的，设备树文件自己做了一点修改，最终镜像是用buildroot制作的

@whycanservice 大佬，请问有没有摄像头的购买链接

@taoyang 在 D1 两个wdog 的作用是一样的吗？ 中说：

wdog0 和wdog1 都是不喂狗时触发硬件reset 信号吗？

会，都可以通过寄存器配置决定是否产生中断活复位系统。

@kelsey Tina是基于openWRT构建的，而target则是openWRT的方案配置，比如说，我的根文件系统包含哪些包， 用什么启动方式（busybox/procd），开机启动脚本，使用的是哪个平台，内核版本等。而device则是板端的一些配置，和硬件相关的，比如描述板端信息的board.dts，内核的config配置，分区信息等。

@kelsey
搞定啦，flash上拉电阻补焊搞定。

&lcd0 { lcd_used = <1>; lcd_driver_name = "whycanpi_lcd_620"; lcd_backlight = <255>; lcd_if = <4>; lcd_x = <480>; lcd_y = <1920>; lcd_width = <52>; lcd_height = <52>; lcd_dclk_freq = <66>; lcd_pwm_used = <1>; lcd_pwm_ch = <7>; lcd_pwm_freq = <50000>; lcd_pwm_pol = <0>; lcd_pwm_max_limit = <255>; lcd_bright_curve_en = <0>; lcd_backlight = <255>; lcd_hbp = <60>; lcd_ht = <570>; lcd_hspw = <30>; lcd_vbp = <12>; lcd_vt = <1938>; lcd_vspw = <6>; lcd_dsi_if = <0>; lcd_dsi_lane = <4>; lcd_lvds_if = <0>; lcd_lvds_colordepth = <0>; lcd_lvds_mode = <0>; lcd_frm = <0>; lcd_hv_clk_phase = <0>; lcd_hv_sync_polarity= <0>; lcd_io_phase = <0x0000>; lcd_gamma_en = <0>; lcd_bright_curve_en = <0>; lcd_cmap_en = <0>; lcd_fsync_en = <0>; lcd_fsync_act_time = <1000>; lcd_fsync_dis_time = <1000>; lcd_fsync_pol = <0>; deu_mode = <0>; lcdgamma4iep = <22>; smart_color = <90>; lcd_gpio_0 = <&pio PD 20 GPIO_ACTIVE_HIGH>; pinctrl-0 = <&dsi4lane_pins_a>; pinctrl-1 = <&dsi4lane_pins_b>; }

@laocai 在 V3S 硬解h264，基于tina还是主线linux开发？ 中说：

@xiaowenge 在线申请，还是要联系sales？

联系sales

@whycanservice 感谢 确实发现设备了

@xiaoliu 内核里找一下有没有pwm的fs驱动，默认的没有文件系统接口

@yuzukitsuru 我没有按照教程安装repo 才导致这个错误