@wyljkl
evtest 出来的是adc值，不是触摸屏坐标．

想要触摸屏坐标：https://cn.bing.com/search?q=ts_uinput

后来是怎么处理的。

@weichengjie 我使用的是TINA， 有修改的部分已经全部在帖子里了。
你直接下载个TINA即可，whycan或者 芒果的都可以

@ubuntu

https://blog.51cto.com/u_15899439/5909239

根据提示信息，directfb貌似依赖/dev/tty0或者/dev/vc/*设备节点，根据提示，打开/dev/vt/*使能配置

CONFIG_VT选项将会打开内核对Virtual Terminal的支持，CONFIG_VT 打开后，内核才会支持带显示和键盘的终端设备，由于这类终端设备上通常可以打开多个virtual termial,类似于gnome console，所以叫做virtual terminal,配置上讲：

用 wpa_cli 命令，或者 基于 libwpa_client 库编程。

问题已解决。不用虚拟机，而是用台式电脑安装ubuntu系统，之后重做一次，编译就能通过。程序下载到板子上启动有日志输出

@shz18877605430

参考这个： V3s 驱动 RTL8723DS 蓝牙，出了这个问题，请问怎么解决呢

8723ds的wlan0是能正常使用的，已经连接网络，能ping通。

问题已解决。其实不需要复位USB。它会自动检测USB设备的拔插。原来检测 不到，原因是USB线电路有问题。

4M是CMA内存，在env.cfg里配置大小

@weichengjie T113 上同时开启CAN0,CAN1,及4G通信。都是正常的。原来使用CAN0就影响到4G模块的原因找到了。是在设备树文件上，USB的节点里有PB3的定义。去掉就正常。
U.png

@jinxiangwzh 有个通过 ADC 检测按键的 ADC，加颗上拉电阻。 不然只能修改 BOOT0

在docker(ubuntu:20.04)中编译时, facebuildercmd出现段错误;
换成了一台Ubuntu 22.04.2 LTS(Linux tao 5.15.0-58 x86_64 GNU/Linux)物理机编译成功;
原因待查

@yixintai 可以裁剪的视频编码都已经裁剪了，64M内存还是很紧张，经常出现OOM问题，我们的音频解码不需要4M的，因为观察解码出来的PCM缓存，只有300多K，音频解码的StreamBuffer在我们的场景下，128K就够了的，还是麻烦尽快提供下修改方法，感谢。

@waterworld 在 LVGL8打开G2D报错 中说：

问题已解决，解决方式参考：
https://bbs.aw-ol.com/topic/1681

修改package\gui\littlevgl-8\lv_drivers\display\g2d_driver_enh.h，是由于头文件不一致导致的

对，我也发现了。

@qingqingxiaozi 好的，感谢

看下分区表，感觉分区表有问题

bmp图片使用16/24/32位测试下

@yteraa 老师您好，各位大神们好，请教下按你的教程从nor切换到nand后启动找不到文件系统，是哪方面问题？谢谢。1676633152331.jpg-------------- 1676633142829.jpg

@baiwen 大佬，有弄出来吗？我用你们百问网的板子也是这个问题，启动不了内核？nand型号是MX35LF1GE4AB

@chengwei_peng inittab文件内容如下：

::sysinit:/etc/init.d/rcS S boot ::shutdown:/etc/init.d/rcS K shutdown ::askconsole:/bin/ash --login

@fantasya 在 T113 Tina 自带的LVGL8 G2D Test运行报错 中说：

Segmentation fault

我的也出现一样的问题，请问楼主解决了吗？

@whycan 能用，目前没发现有啥影响

@whycan 在 F1C200s类似正点原子驱动开发指南的资料？ 中说：

@kashine

这个代码风格和正点原子接近: https://item.taobao.com/item.htm?id=589639202997 (没有PY关系, 三思再下手)

里面有教程吗？比如说某个驱动，有没有对应的教程文档，分析驱动原理与代码？谢谢晕哥

@wyljkl
刚刚我也出现这个问题，发现 adb_socketpair() 无法执行，检查发现内核里面把CONFIG_NET选项屏蔽了，把这个选购开起来就正常了．

@whycan 好的，感谢晕哥🤙🤙🤙

@chengwei_peng
做了这样的改动:

sunxi_udc.h
df76c165-957f-4d5d-8341-aafe8a26f735-image.png sunxi_udc.c
64dab9f1-9a50-4281-a6e0-59b5e2378e95-image.png

问题还是存在，改动应该没问题吧？

@uuuuid
晕, 可能不是模块原因, 而是用错驱动了, 明明是 RTL8723BS, 驱动用成了RTL8723DS

@whycan 🐧 🐧 🐧

@jinxiangwzh 对，头文件也更新一下。

@whycan 好吧，只能到这了，谢晕哥

@whycan 好的晕哥。

@jinxiangwzh 意思是你得花钱找原厂

https://mariadb.com/kb/en/operating-system-error-codes/

error 2 ENOENT No such file or directory

@duanzhh 抱歉我到现在也没有解决这个问题

@jinxiangwzh
把eMMC频率降下来试一试，board.dts

@jinxiangwzh
eMMC接sdc0，还是sdc1？dts配置有没有冲突？

@alibabafa 没

@migu_ 大佬，虽然你这个我不知道
但是还是想请教一下，编译ubuntu后，烧写成功后，板子依旧进入的是forlink桌面，没有进入到ubuntu

@zhangheyang 你用的哪个工具烧录的，我刚开始研究，换个SPI NOR FLASH

@whycan 谢谢大佬，我把内核初始化的busybox init 改成procd init方式后也可以编译了，没搞懂是因为什么

@anruliu 嗯嗯之前尝试过在 Tina 2.0 环境下重新迁移驱动等，不过遇到一些问题（比如 https://bbs.aw-ol.com/topic/2674/lcd-kernel-亮屏后立马黑屏 以及 触控驱动问题）

现在还是在 0.2 的环境下 使用了 2.0 的 linux-4.9/modules/gpu package/kernel/gpu-km package/libs/libgpu 现在用 eglfs 不跳帧了 ，不过性能好像和 linuxfb 差不是太多 o(╯□╰)o 我再试试 APP 方面能不能再优化优化…… 如果GPU优化方面还有其他思路的话也非常感谢提示更多信息 🤝 🤝 🤝 再次感谢大佬支持

牛逼👶

获取mp3文件封面：

ffmpeg -i "0376.梅艳芳 - 心肝宝贝.mp3" -vcodec copy -an cover封面.jpg

参考： https://stackoverflow.com/questions/13592709/retrieve-album-art-using-ffmpeg

@waterworld 凡是没有编译的，进入内核执行 make clean命令，然后再次重新编译。

如果还是不行的，确认内核目录下的.config是否已经选上这个配置了。

@konstantint You can try

[lcd0] lcd_rb_swap = <1>;

用的是Melis？

@yuzukitsuru 大佬，那这个问题修复了吗

hello @anruliu , 请教一下整个显示流程哪个步骤会拉低RESET呢？ 我们现在是手头上没有示波器这些硬件调试手段 😧 😧 😧
PS1: 现在 uboot 阶段偶尔不亮屏幕
PS2: 休眠唤醒lcd 一定能够亮起屏幕
PS3: 我们现在手头上的源码(tina 2.0) 信息如下，应该不会有问题吧？

# repo forall -c "pwd; git log --oneline;echo;echo" /works/to-download/build 9677096 smartx-r818-tina-v2.0-release release 11276aa smartx-r818-tina-v1.0.0-release release 0aee083 smartx-r818-tina-v0.2.0-release release /r818/config b9b4e3e smartx-r818-tina-v1.0.0-release release c265e5d smartx-r818-tina-v0.2.0-release release /r818/device/config/chips/r818 961a3d9 [fix] 适配产品，可以 烧写并 adb shell 7667829 smartx-r818-tina-v2.0-release release /r818/device/config/common d3d5e39 smartx-r818-tina-v1.0.0-release release a76bf10 smartx-r818-tina-v0.2.0-release release /r818/dl 6b687c4 remove unused package 1819cd9 smartx-r818-tina-v1.0.0-release release 0e5a144 smartx-r818-tina-v0.2.0-release release /r818/docs e4127ef smartx-r818-tina-v0.2.0-release release /r818/lichee/arisc c357572 smartx-r818-tina-v2.0-release release 589bc39 smartx-r818-tina-v1.0.0-release release bfc598f smartx-r818-tina-v0.2.0-release release /r818/lichee/brandy-2.0/spl 0ca0957 smartx-r818-tina-v2.0-release release 0f2b788 smartx-r818-tina-v1.0.0-release release 9ab7078 smartx-r818-tina-v0.2.0-release release /r818/lichee/brandy-2.0/tools 3f0f997 smartx-r818-tina-v1.0.0-release release 77e0592 smartx-r818-tina-v0.2.0-release release /r818/lichee/brandy-2.0/u-boot-2018 5ec57ef [fix] 勾选 LCD_SUPPORT_K101IM2BYL02L e568104 smartx-r818-tina-v2.0-release release 9b56363 smartx-r818-tina-v1.0.0-release release 44e5477 smartx-r818-tina-v0.2.0-release release /r818/lichee/linux-4.9 8a99727f0 [feature]添加 k101im2byl02l 屏幕显示驱动 8b9cb8723 smartx-r818-tina-v2.0-release release 352550f19 smartx-r818-tina-v1.0.0-release release 842f0db32 smartx-r818-tina-v0.2.0-release release /r818/package 38e46ac3 smartx-r818-tina-v2.0-release release 04e65073 remove unused package 667cc61e smartx-r818-tina-v1.0.0-release release 047ce9bd smartx-r818-tina-v0.2.0-release release /r818/prebuilt d771fad smartx-r818-tina-v0.2.0-release release /r818/scripts 37ecb36 smartx-r818-tina-v2.0-release release 984d79d smartx-r818-tina-v1.0.0-release release 1c87d6c smartx-r818-tina-v0.2.0-release release /r818/target 50cf978 smartx-r818-tina-v2.0-release release b804823 defconfig:remove unused info 7a1879a smartx-r818-tina-v1.0.0-release release 8582b0c smartx-r818-tina-v0.2.0-release release /r818/toolchain 9f90325 smartx-r818-tina-v0.2.0-release release /r818/tools 48b4556 smartx-r818-tina-v2.0-release release 936113f smartx-r818-tina-v1.0.0-release release a4745b7 smartx-r818-tina-v0.2.0-release release

@techxie123
https://github.com/lvgl/lvgl/issues/500

kisvegabor commented on Nov 28, 2018

Yes, LittlevGL doesn't support multi touch because there is nothing to use it for. Zoom and rotate could be a good purpose but they are not implemented.

是的，LittlevGL 不支持多点触控，因为没有什么用。缩放和旋转可能是一个很好的目的，但它们没有实现。

@chengwei_peng 我们后来找代理厂商拿到了最新的SDK后， 能够cat 该节点~

多谢各位大佬支持 ✌ ✌ ✌ ✌ ✌ ✌

@yuzukitsuru 我要是不回复感谢一下，我都觉得对不起你…

@chinazhangdj 在 Tina linux spi lcd无法刷屏 中说：
大佬有调试通过了吗？能否请教一下怎么调

主线使用的是drm驱动，建议参考kernel的doc

https://www.kernel.org/doc/html/latest/

@wyljkl 起作用了！ 多谢多谢！

@uuuuid 在 换了四台电脑，终于让我悟出来NXP GUI Guider 为啥不能正常显示出设计界面的原因了 中说：

装上 jre-8u341-windows-x64.exe 之后，一切就正常了。

成功搞定！

cat 一下图层看看图层对不对

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

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

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

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

@whycan

修改了一下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) -- --

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

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

@whycanservice 谢谢回复。
我已经在clk驱动中将module_platform_driver(clk_driver);
改成了
static int __init clk_init(void)
{
return platform_driver_register(&clk_driver);
}
arch_initcall(clk_init);//arch_initcall 等级为3
我通过kernel log 看，clk_driver 执行probe的时间确实有提前，但是有的使用module_init的驱动还是会在clk_driver之前执行probe。这让我感觉很疑惑。
我想过将驱动编译为module,但是clk涉及到很多功能，像是gpio，lcd，audio等，如果将上述的驱动都使用module，那就涉及到这些部分的驱动可能都需要编译成module，这样做是否会很奇怪。

问题已解决，DNS解析顺序的问题，优先读了/etc/resolv.conf（软链接），注释或者删掉/tmp/resolv.conf的配置，系统就能自动读到/etc/hosts里的配置了

@jinxiangwzh 在 关于TinaLinux4.9中的sys_config.fex的pwm配置 中说：

@whycanservice 感谢回复 这个看明白了

我另一组按键的配置为啥在这个文件中找不到 无论是搜索gpiokey还是PD19都没有？

[gpiokey] compatible = "gpio-keys" autorepeat = 1 label = "capture_key" gpios = port:PD19<6><default><default><default> linux,input-type = <1> linux,code = 0x1ba

建议在board.dts中增加，linux4.9不需要再sys_config.fex中配置，而gpio-keys的配置，可以看看内核代码，这个是内核原生的，看看代码解析哪些字段信息，从而增加即可。

安装相关软件包：

sudo dpkg --add-architecture i386 sudo apt-get update sudo apt-get install gcc-multilib libc6:i386 libncurses5:i386 libstdc++6:i386 libasound2*:i386

编译x64版本可执行程序：

gcc -o test test.c

编译i386版本可执行程序：

gcc -o test -m32 test.c

@ivan_wan LVGL，插TF卡就播

@y97788 这啥原理？

@masterlu 目前发现单独编译出来的8723bu.ko文件安装上去能够正常使用ap，整体编译内核输出在output/lib/modules/3.10.65下的8723bu.ko文件无法使用ap，会报No WPA/RSN IE from STA的错误。

@YterAA 帮我看下我的这个问题哦 链接文本