Hello @anruliu 大佬， 我们换成了 Qt 5.12.9 ，eglfs 渲染还是会出现这种情况。 我们试过，旋转不旋转还是一样会跳帧（回跳）。

🤝 🤝 🤝

@chengwei_peng dmesg命令之后输出得都是控制台已经printk得内容，看不出问题

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

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

主线，主线😊

用的是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 我要是不回复感谢一下，我都觉得对不起你…

@whycan 你好，我现在按照这个方式出现如下报错：
root@TinaLinux:/# cat /sys/devices/platform/soc@3000000/soc@3000000:usbc0@0/usb
_device
[ 593.130091]
[ 593.130091] rmmod_device_driver
[ 593.130091]
[ 593.136883] rmmod_device_driver()222 WARN: get power supply failed
[ 593.143937] android_work: sent uevent USB_STATE=DISCONNECTED
[ 593.150587]
[ 593.150587] insmod_device_driver
[ 593.150587]
device_chose finished!
root@TinaLinux:/# [ 593.320672] sunxi_set_cur_vol_work()489 WARN: get power supply failed
[ 593.357447] android_work: sent uevent USB_STATE=CONNECTED
[ 593.370148] sunxi_set_cur_vol_work()489 WARN: get power supply failed
[ 593.429780] configfs-gadget gadget: high-speed config #1: c
[ 593.436336] android_work: sent uevent USB_STATE=CONFIGURED

root@TinaLinux:/# adb
adb_shell adbd
root@TinaLinux:/# adb
adb_shell adbd
root@TinaLinux:/# adbd
init adb main
[adbd D]qemu_pipe_open: Could not open /dev/qemu_pipe: No such file or directory[adbd D]Handling main()
Handling main()
[adbd D]Warning: ADB_EXTERNAL_STORAGE is not set. Leaving EXTERNAL_STORAGE unchanged.
cannot bind 'tcp:5037'
root@TinaLinux:/# adbd
init adb main
[adbd D]qemu_pipe_open: Could not open /dev/qemu_pipe: No such file or directory[adbd D]Handling main()
Handling main()
[adbd D]Warning: ADB_EXTERNAL_STORAGE is not set. Leaving EXTERNAL_STORAGE unchanged.
cannot bind 'tcp:5037'
root@TinaLinux:/# adbd -D
init adb main
[adbd D]qemu_pipe_open: Could not open /dev/qemu_pipe: No such file or directory[adbd D]Handling main()
Handling main()
[adbd D]Warning: ADB_EXTERNAL_STORAGE is not set. Leaving EXTERNAL_STORAGE unchanged.
cannot bind 'tcp:5037'

@rayzhang G2D？

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

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

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

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

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

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

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

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

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

@y97788 这啥原理？

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

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

@yuzukitsuru 看漏了，谢谢大佬

@yixiuge 在 开发板报错 中说：

fsck.ext4 /dev/mmcblk0p7

root@inomec:/# fsck.ext4 /dev/mmcblk0p7 e2fsck 1.42.12 (29-Aug-2014) /dev/mmcblk0p7 is mounted. e2fsck: Cannot continue, aborting.

@yuzukitsuru 都烧不进去，是不是要改什么配置？

现在好了，可以访问了。

@masterlu
random: Trying to read entropy from /dev/random
Configuration file: /etc/hostapd.conf
nl80211: Supported cipher 00-0f-ac:1
nl80211: Supported cipher 00-0f-ac:5
nl80211: Supported cipher 00-0f-ac:2
nl80211: Supported cipher 00-0f-ac:4
nl80211: Using driver-based off-channel TX
nl80211: key_mgmt=0xd0f enc=0xf auth=0x7 flags=0x800d8c0 rrm_flags=0x0 probe_resp_offloads=0x0 max_stations=0 max_remain_on_chan=5000 max_scan_ssids=9
nl80211: interface wlan0 in phy phy0
nl80211: Set mode ifindex 7 iftype 3 (AP)
nl80211: Setup AP(wlan0) - device_ap_sme=1 use_monitor=0
nl80211: Subscribe to mgmt frames with AP handle 0x1dfbdd0 (device SME)
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1dfbdd0 match=04 multicast=0
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1dfbdd0 match=0501 multicast=0
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1dfbdd0 match=0503 multicast=0
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1dfbdd0 match=0504 multicast=0
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1dfbdd0 match=06 multicast=0
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1dfbdd0 match=08 multicast=0
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1dfbdd0 match=09 multicast=0
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1dfbdd0 match=0a multicast=0
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1dfbdd0 match=11 multicast=0
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1dfbdd0 match=7f multicast=0
nl80211: Register frame type=0xb0 (WLAN_FC_STYPE_AUTH) nl_handle=0x1dfbdd0 match= multicast=0
nl80211: Enable Probe Request reporting nl_preq=0x1e00ea0
nl80211: Register frame type=0x40 (WLAN_FC_STYPE_PROBE_REQ) nl_handle=0x1e00ea0 match= multicast=0
rfkill: Cannot open RFKILL control device
nl80211: RFKILL status not available
nl80211: Add own interface ifindex 7 (ifidx_reason -1)
nl80211: if_indices[16]: 7(-1)
phy: phy0
BSS count 1, BSSID mask 00:00:00:00:00:00 (0 bits)
nl80211: No channel number found for frequency 5920 MHz
nl80211: No channel number found for frequency 5940 MHz
nl80211: Regulatory information - country=00
nl80211: 2402-2472 @ 40 MHz 20 mBm
nl80211: 2457-2482 @ 40 MHz 20 mBm (no IR)
nl80211: 2474-2494 @ 20 MHz 20 mBm (no OFDM) (no IR)
nl80211: 5170-5250 @ 80 MHz 20 mBm (no IR)
nl80211: 5735-5835 @ 80 MHz 20 mBm (no IR)
nl80211: 57240-63720 @ 2160 MHz 0 mBm
nl80211: Added 802.11b mode based on 802.11g information
nl80211: Mode IEEE 802.11g: 2412 2417 2422 2427 2432 2437 2442 2447 2452 2457 2462 2467[NO_IR] 2472[NO_IR] 2484[DISABLED]
nl80211: Mode IEEE 802.11a: 5170[DISABLED] 5180[DISABLED] 5190[DISABLED] 5200[DISABLED] 5210[DISABLED] 5220[DISABLED] 5230[DISABLED] 5240[DISABLED] 5260[DISABLED] 5280[DISABLED] 5300[DISABLED] 5320[DISABLED] 5500[DISABLED]
nl80211: Mode IEEE 802.11b: 2412 2417 2422 2427 2432 2437 2442 2447 2452 2457 2462 2467[NO_IR] 2472[NO_IR] 2484[DISABLED]
Allowed channel: mode=1 chan=1 freq=2412 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=2 freq=2417 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=3 freq=2422 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=4 freq=2427 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=5 freq=2432 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=6 freq=2437 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=7 freq=2442 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=8 freq=2447 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=9 freq=2452 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=10 freq=2457 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=11 freq=2462 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=1 freq=2412 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=2 freq=2417 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=3 freq=2422 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=4 freq=2427 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=5 freq=2432 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=6 freq=2437 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=7 freq=2442 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=8 freq=2447 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=9 freq=2452 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=10 freq=2457 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=11 freq=2462 MHz max_tx_power=20 dBm
Completing interface initialization
Mode: IEEE 802.11g Channel: 3 Frequency: 2422 MHz
DFS 0 channels required radar detection
nl80211: Set freq 2422 (ht_enabled=0, vht_enabled=0, he_enabled=0, bandwidth=20 MHz, cf1=2422 MHz, cf2=0 MHz)

freq=2422 he_enabled=0 vht_enabled=0 ht_enabled=0 channel_type=0
RATE[0] rate=10 flags=0x1
RATE[1] rate=20 flags=0x1
RATE[2] rate=55 flags=0x1
RATE[3] rate=110 flags=0x1
RATE[4] rate=60 flags=0x0
RATE[5] rate=90 flags=0x0
RATE[6] rate=120 flags=0x0
RATE[7] rate=180 flags=0x0
RATE[8] rate=240 flags=0x0
RATE[9] rate=360 flags=0x0
RATE[10] rate=480 flags=0x0
RATE[11] rate=540 flags=0x0
hostapd_setup_bss(hapd=0x1dfb060 (wlan0), first=1)
nl80211: flush -> DEL_STATION wlan0 (all)
Using interface wlan0 with hwaddr f0:c8:14:7b:5a:4b and ssid "hostapd_test"
Deriving WPA PSK based on passphrase
SSID - hexdump_ascii(len=12):
68 6f 73 74 61 70 64 5f 74 65 73 74 hostapd_test
PSK (ASCII passphrase) - hexdump_ascii(len=8): [REMOVED]
PSK (from passphrase) - hexdump(len=32): [REMOVED]
random: Got 20/20 random bytes
Get randomness: len=32 entropy=0
GMK - hexdump(len=32): [REMOVED]
Get randomness: len=32 entropy=0
Key Counter - hexdump(len=32): [REMOVED]
WPA: Delay group state machine start until Beacon frames have been configured
nl80211: Set beacon (beacon_set=0)
nl80211: Beacon head - hexdump(len=63): 80 00 00 00 ff ff ff ff ff ff f0 c8 14 7b 5a 4b f0 c8 14 7b 5a 4b 00 00 00 00 00 00 00 00 00 00 64 00 11 04 00 0c 68 6f 73 74 61 70 64 5f 74 65 73 74 01 08 82 84 8b 96 0c 12 18 24 03 01 03
nl80211: Beacon tail - hexdump(len=35): 2a 01 04 32 04 30 48 60 6c 30 18 01 00 00 0f ac 02 02 00 00 0f ac 04 00 0f ac 02 01 00 00 0f ac 02 00 00
nl80211: ifindex=7
nl80211: beacon_int=100
nl80211: beacon_rate=0
nl80211: rate_type=0
nl80211: dtim_period=2
nl80211: ssid=hostapd_test beacon_int=100 dtim_period=2
nl80211: hidden SSID not in use
nl80211: privacy=2
nl80211: auth_algs=0x3
nl80211: wpa_version=0x2
nl80211: key_mgmt_suites=0x2
nl80211: pairwise_ciphers=0x18
nl80211: group_cipher=0x8
wlan0: Deauthenticate all stations at BSS start
nl80211: sta_remove -> DEL_STATION wlan0 ff:ff:ff:ff:ff:ff --> -22 (Invalid argument)
WPA: Start group state machine to set initial keys
WPA: group state machine entering state GTK_INIT (VLAN-ID 0)
Get randomness: len=32 entropy=0
GTK - hexdump(len=32): [REMOVED]
WPA: group state machine entering state SETKEYSDONE (VLAN-ID 0)
wpa_driver_nl80211_set_key: ifindex=7 (wlan0) alg=2 addr=0x8560c key_idx=1 set_tx=1 seq_len=0 key_len=32 key_flag=0x1a
nl80211: NEW_KEY
nl80211: KEY_DATA - hexdump(len=32): [REMOVED]
broadcast key
nl80211: NL80211_CMD_SET_KEY - default key
nl80211: Set wlan0 operstate 0->1 (UP)
netlink: Operstate: ifindex=7 linkmode=-1 (no change), operstate=6 (IF_OPER_UP)
nl80211: TX queue param set: queue=0 aifs=1 cw_min=3 cw_max=7 burst_time=15 --> res=-95
Failed to set TX queue parameters for queue 0.
nl80211: TX queue param set: queue=1 aifs=1 cw_min=7 cw_max=15 burst_time=30 --> res=-95
Failed to set TX queue parameters for queue 1.
nl80211: TX queue param set: queue=2 aifs=3 cw_min=15 cw_max=63 burst_time=0 --> res=-95
Failed to set TX queue parameters for queue 2.
nl80211: TX queue param set: queue=3 aifs=7 cw_min=15 cw_max=1023 burst_time=0 --> res=-95
Failed to set TX queue parameters for queue 3.
wlan0: interface state UNINITIALIZED->ENABLED
wlan0: AP-ENABLED
wlan0: Setup of interface done.
ctrl_iface not configured!
RTM_NEWLINK: ifi_index=7 ifname=wlan0 operstate=6 linkmode=0 ifi_family=0 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
nl80211: Event message available
nl80211: Drv Event 19 (NL80211_CMD_NEW_STATION) received for wlan0
nl80211: New station 78:62:56:c1:26:31
nl80211: Assoc Req IEs - hexdump(len=0): [NULL]
wlan0: Event ASSOC (0) received
wlan0: STA 78:62:56:c1:26:31 IEEE 802.11: associated
STA did not include WPS/RSN/WPA IE in (Re)AssocReq
New STA
ap_sta_add: register ap_handle_timer timeout for 78:62:56:c1:26:31 (300 seconds - ap_max_inactivity)
No WPA/RSN IE from STA
nl80211: sta_remove -> DEL_STATION wlan0 78:62:56:c1:26:31 --> 0 (Success)
nl80211: Set STA flags - ifname=wlan0 addr=78:62:56:c1:26:31 total_flags=0x0 flags_or=0x0 flags_and=0xfffffff1 authorized=0
nl80211: sta_remove -> DEL_STATION wlan0 78:62:56:c1:26:31 --> 0 (Success)
ap_free_sta: cancel ap_handle_timer for 78:62:56:c1:26:31
nl80211: Event message available
nl80211: Drv Event 20 (NL80211_CMD_DEL_STATION) received for wlan0
nl80211: Delete station 78:62:56:c1:26:31
wlan0: Event DISASSOC (1) received
wlan0: STA 78:62:56:c1:26:31 IEEE 802.11: disassociated
Disassociation notification for unknown STA 78:62:56:c1:26:31
nl80211: Event message available
nl80211: Drv Event 19 (NL80211_CMD_NEW_STATION) received for wlan0
nl80211: New station 78:62:56:c1:26:31
nl80211: Assoc Req IEs - hexdump(len=0): [NULL]
wlan0: Event ASSOC (0) received
wlan0: STA 78:62:56:c1:26:31 IEEE 802.11: associated
STA did not include WPS/RSN/WPA IE in (Re)AssocReq
New STA
ap_sta_add: register ap_handle_timer timeout for 78:62:56:c1:26:31 (300 seconds - ap_max_inactivity)
No WPA/RSN IE from STA
nl80211: sta_remove -> DEL_STATION wlan0 78:62:56:c1:26:31 --> 0 (Success)
nl80211: Set STA flags - ifname=wlan0 addr=78:62:56:c1:26:31 total_flags=0x0 flags_or=0x0 flags_and=0xfffffff1 authorized=0
nl80211: sta_remove -> DEL_STATION wlan0 78:62:56:c1:26:31 --> 0 (Success)
ap_free_sta: cancel ap_handle_timer for 78:62:56:c1:26:31
nl80211: Event message available
nl80211: Drv Event 20 (NL80211_CMD_DEL_STATION) received for wlan0
nl80211: Delete station 78:62:56:c1:26:31
wlan0: Event DISASSOC (1) received
wlan0: STA 78:62:56:c1:26:31 IEEE 802.11: disassociated
Disassociation notification for unknown STA 78:62:56:c1:26:31
nl80211: Event message available
nl80211: Drv Event 19 (NL80211_CMD_NEW_STATION) received for wlan0
nl80211: New station 78:62:56:c1:26:31
nl80211: Assoc Req IEs - hexdump(len=0): [NULL]
wlan0: Event ASSOC (0) received
wlan0: STA 78:62:56:c1:26:31 IEEE 802.11: associated
STA did not include WPS/RSN/WPA IE in (Re)AssocReq
New STA
ap_sta_add: register ap_handle_timer timeout for 78:62:56:c1:26:31 (300 seconds - ap_max_inactivity)
No WPA/RSN IE from STA
nl80211: sta_remove -> DEL_STATION wlan0 78:62:56:c1:26:31 --> 0 (Success)
nl80211: Set STA flags - ifname=wlan0 addr=78:62:56:c1:26:31 total_flags=0x0 flags_or=0x0 flags_and=0xfffffff1 authorized=0
nl80211: sta_remove -> DEL_STATION wlan0 78:62:56:c1:26:31 --> 0 (Success)
ap_free_sta: cancel ap_handle_timer for 78:62:56:c1:26:31
nl80211: Event message available
nl80211: Drv Event 20 (NL80211_CMD_DEL_STATION) received for wlan0
nl80211: Delete station 78:62:56:c1:26:31
wlan0: Event DISASSOC (1) received
wlan0: STA 78:62:56:c1:26:31 IEEE 802.11: disassociated
Disassociation notification for unknown STA 78:62:56:c1:26:31
nl80211: Event message available
nl80211: Drv Event 19 (NL80211_CMD_NEW_STATION) received for wlan0
nl80211: New station 78:62:56:c1:26:31
nl80211: Assoc Req IEs - hexdump(len=0): [NULL]
wlan0: Event ASSOC (0) received
wlan0: STA 78:62:56:c1:26:31 IEEE 802.11: associated
STA did not include WPS/RSN/WPA IE in (Re)AssocReq
New STA
ap_sta_add: register ap_handle_timer timeout for 78:62:56:c1:26:31 (300 seconds - ap_max_inactivity)
No WPA/RSN IE from STA
nl80211: sta_remove -> DEL_STATION wlan0 78:62:56:c1:26:31 --> 0 (Success)
nl80211: Set STA flags - ifname=wlan0 addr=78:62:56:c1:26:31 total_flags=0x0 flags_or=0x0 flags_and=0xfffffff1 authorized=0
nl80211: sta_remove -> DEL_STATION wlan0 78:62:56:c1:26:31 --> 0 (Success)
ap_free_sta: cancel ap_handle_timer for 78:62:56:c1:26:31
nl80211: Event message available
nl80211: Drv Event 20 (NL80211_CMD_DEL_STATION) received for wlan0
nl80211: Delete station 78:62:56:c1:26:31
wlan0: Event DISASSOC (1) received
wlan0: STA 78:62:56:c1:26:31 IEEE 802.11: disassociated
Disassociation notification for unknown STA 78:62:56:c1:26:31

@yuzukitsuru 感谢大佬，我想一下别的方法😥

@dream 在 【分析笔记】Linux I2C-Tools 使用踩坑笔记 中说：

@daizebin sht41 的器件地址是 0x44，就决定了在自动模式下，是以写方式检测，所以可以识别到，但是 sgp41 的器件地址是 0x59，落在了以读方式检测的范围，所以无法识别到。具体看本文 scan_i2c_bus() 的源码截图就能看出来。

再补充一下，不是所有的 I2C 器件都必须要以写的方式才能检测出来，只有少部分，如 sht41\sgp41 这类器件比较特别，需要先写再读才有应答，正因为大部分 I2C 器件无论是读写都会有应答，所以才会因惯性思维，导致踩坑。

@kurt_z 这个不太清楚了，如果个人想弄可以试试简单便宜的daplink+openocd

@duanzhh 👏 👏

@steve 主线的hdmi似乎需要播放一段预加载音频初始化snd设备才能使用，具体可以搜索一下github上的issue

有ethtool工具吗？

@waterworld

find . -name "*.o" |xargs rm

@lgkgkfg https://v853.docs.aw-ol.com/soft/dev_gpio/

@yuzukitsuru 开启了，图像内部的一些轮廓位置一直抖动，好奇怪，其他文件又是正常的

@yuzukitsuru 谢谢大佬的解答

@chinazhangdj 不是，是uboot和kernel的

ld记得链接linux/gpio

换一片，有坏块，NAND 有坏块

@allwinnertech 是的就是想在uboot 中配置好，但是没有成功。

@steve-xu

那建议 用GPIO片选，这个是基于硬件SPI，速率可以满足你的需求。

@xiaowenge 谢谢大佬😊

@waterworld

iot@server-211:~/jkangli/f1c100s/tina$ pack No kernel param, parse it from c200s copying tools file copying configs file image/arisc.fex image/aultls32.fex image/aultools.fex image/bootlogo.fex image/boot_package.cfg image/boot_package.fex image/boot_package_nor.cfg image/cardscript.fex image/cardscript_secure.fex image/cardtool.fex image/diskfs.fex image/env-3.10.cfg image/env_burn.cfg image/esm.fex image/image_crashdump.cfg renamed 'image/image_linux.cfg' -> 'image/image.cfg' image/image_nor.cfg image/split_xxxx.fex image/sunxi.fex image/sw-subimgs-ab.cfg image/sw-subimgs.cfg image/sw-subimgs-secure.cfg image/sys_config.fex image/sys_partition_dump.fex image/sys_partition.fex image/sys_partition_nor.fex image/sys_partition_private.fex image/toc0.fex image/toc1.fex image/usbtool_crash.fex image/usbtool.fex image/usbtool_test.fex image/writable.fex /home/iot/jkangli/f1c100s/tina storage_type value is 5 rm /home/iot/jkangli/f1c100s/tina/out/c200s-F1C200s/image/sys_partition_nor.fex rm /home/iot/jkangli/f1c100s/tina/out/c200s-F1C200s/image/image_nor.cfg copying boot resource LZMA 4.65 : Igor Pavlov : Public domain : 2009-02-03 copying boot file make user resource for : /home/iot/jkangli/f1c100s/tina/out/c200s-F1C200s/image/sys_partition.fex handle partition user-res no user resource partitions unable to find key partition_start ERROR: update mbr file fail no app resource partitions /home/iot/jkangli/f1c100s/tina unable to find key partition_start ERROR: update mbr file fail /home/iot/jkangli/f1c100s/tina/scripts/pack_img.sh: line 722: let: DATA_PART_SIZE_IN_K=/2: syntax error: operand expected (error token is "/2") DATA_PART_DOWNLOAD_FILE = /home/iot/jkangli/f1c100s/tina/out/c200s-F1C200s/image/data.fex Need size of filesystem /home/iot/jkangli/f1c100s/tina/out/c200s-F1C200s/image/data.fex is not ext4 img /home/iot/jkangli/f1c100s/tina/out/c200s-F1C200s/image/data.fex: cannot open `/home/iot/jkangli/f1c100s/tina/out/c200s-F1C200s/image/data.fex' (No such file or directory) /home/iot/jkangli/f1c100s/tina unable to find key partition_start ERROR: update mbr file fail sys_config exist Multiconfig num:0 copying tools file copying configs file image/arisc.fex image/aultls32.fex image/aultools.fex image/boot0_nand.fex image/boot0_sdcard.fex image/boot0_spinor.fex image/bootlogo.fex image/boot_package.cfg image/boot_package.fex image/boot_package_nor.cfg image/cardscript.fex image/cardscript_secure.fex image/cardtool.fex image/diskfs.fex image/env-3.10.cfg image/env_bk.cfg image/env_burn.cfg image/env.cfg image/esm.fex image/fes1.fex image/image.cfg image/image_crashdump.cfg renamed 'image/image_linux.cfg' -> 'image/image.cfg' image/image_nor.cfg image/split_xxxx.fex image/sunxi.fex image/sw-subimgs-ab.cfg image/sw-subimgs.cfg image/sw-subimgs-secure.cfg image/sys_config.fex image/sys_partition_dump.fex image/sys_partition.fex image/sys_partition_nor.fex image/sys_partition_private.fex image/sys_partition_tmp_app.fex image/sys_partition_tmp_data.fex image/toc0.fex image/toc1.fex image/u-boot.fex image/u-boot-spinor.fex image/usbtool_crash.fex image/usbtool.fex image/usbtool_test.fex image/writable.fex /home/iot/jkangli/f1c100s/tina storage_type value is 5 rm /home/iot/jkangli/f1c100s/tina/out/c200s-F1C200s/image/sys_partition_nor.fex rm /home/iot/jkangli/f1c100s/tina/out/c200s-F1C200s/image/image_nor.cfg copying boot resource LZMA 4.65 : Igor Pavlov : Public domain : 2009-02-03 copying boot file make user resource for : /home/iot/jkangli/f1c100s/tina/out/c200s-F1C200s/image/sys_partition.fex handle partition user-res no user resource partitions unable to find key partition_start ERROR: update mbr file fail no app resource partitions /home/iot/jkangli/f1c100s/tina unable to find key partition_start ERROR: update mbr file fail /home/iot/jkangli/f1c100s/tina/scripts/pack_img.sh: line 722: let: DATA_PART_SIZE_IN_K=/2: syntax error: operand expected (error token is "/2") DATA_PART_DOWNLOAD_FILE = /home/iot/jkangli/f1c100s/tina/out/c200s-F1C200s/image/data.fex Need size of filesystem /home/iot/jkangli/f1c100s/tina/out/c200s-F1C200s/image/data.fex is not ext4 img /home/iot/jkangli/f1c100s/tina/out/c200s-F1C200s/image/data.fex: cannot open `/home/iot/jkangli/f1c100s/tina/out/c200s-F1C200s/image/data.fex' (No such file or directory) /home/iot/jkangli/f1c100s/tina unable to find key partition_start ERROR: update mbr file fail p=soc c=product state=0 p=soc c=platform state=0 p=soc c=target state=0 p=soc c=norflash state=0 p=soc c=power_sply state=0 p=soc c=pwr_ctrl state=0 p=soc c=card_boot state=0 p=soc c=pm_para state=0 p=soc c=card0_boot_para state=0 p=soc c=card2_boot_para state=0 p=soc c=card1_boot_para state=0 p=soc c=twi_para state=0 p=soc c=uart_para state=0 p=soc c=jtag_para state=0 p=soc c=dram state=0 p=soc c=twi0 state=0 p=soc c=twi1 state=0 p=soc c=twi2 state=0 p=soc c=uart0 state=0 p=soc c=uart1 state=0 p=soc c=uart2 state=0 p=soc c=spi0 state=0 p=soc c=spi1 state=0 p=soc c=rtp_para state=0 p=soc c=ctp state=0 p=twi0 c=goodix_ts state=0 p=soc c=tkey_para state=0 p=soc c=motor_para state=0 p=soc c=nand0 state=0 p=soc c=disp state=0 p=soc c=lcd0 state=0 p=soc c=pwm0_para state=0 p=soc c=pwm1_para state=0 p=soc c=vip0 state=0 p=soc c=tvout_para state=0 p=soc c=tvin_para state=0 p=soc c=di state=0 p=soc c=sdc0 state=0 p=soc c=sdc1 state=0 p=soc c=smc state=0 p=soc c=usbc0 state=0 p=soc c=gsensor_para state=0 p=soc c=gps_para state=0 p=soc c=wlan state=0 p=soc c=gy_para state=0 p=soc c=ls_para state=0 p=soc c=compass_para state=0 p=soc c=bt_para state=0 p=soc c=audiospdif state=0 p=soc c=spdif_machine state=0 p=soc c=audiohdmi state=0 p=soc c=hdmi_machine state=0 p=soc c=pmu0 state=0 p=soc c=pmu0_regu state=0 p=soc c=dvfs_table state=0 p=soc c=Vdevice state=0 p=soc c=fel_key state=0 p=soc c=partitions state=0 Conver script to dts ok. pack boot package GetPrivateProfileSection read to end content_count=3 toc1 file Path=/home/iot/jkangli/f1c100s/tina/out/c200s-F1C200s/image/boot_package.fex script file Path=/home/iot/jkangli/f1c100s/tina/out/c200s-F1C200s/image/sys_config.bin cant get board_id_enable script update toc1 ok packing for tina linux normal unable to find key partition_start ERROR: update mbr file fail ERROR: update_mbr failed

@wyljkl 可以看下引用的sunxi_display2.h 是不是跟内核 include文件夹下的内容一致。

@evler 我试试

@hyg1688

log太少了，麻烦多粘贴一些

@waterworld 就是修改这个h文件

@waterworld

读spi nor flash(W25Q128/MX25L256)的唯一Id(UID),

支持的，不过这个不是tina linux的功能，是linux的功能

看了一下手册，与f1c100s基本没关系，通过 uart/spi/uart 把这个rfid基站芯片调试成功就可以了．

@yuzukitsuru 可以通过vnc登录到 ubuntu界面的，屏有背光，通过示波器看dclk hsync vync de 的波形频率 是与配置值是一样的，data脚也有方波输出。调试命令可以控制输出使能与去使能。

@inomec 是的，可以看看linux的video框架

@yteraa 好的

@memory 谢谢提醒
我们做了一下实验，把vio提高到2v，50M的时钟现在能识别wifi了，但是70M以上就还是不行。

然后我们空载的情况下测试了clk的幅度，T113 在120M时，明显幅度是不够的。作为对比，imx6ull 带载wifi 时，135M还能有2v 的幅度。

请问这个可能是什么问题？ 涉及寄存器设置？

50M时钟：
T113-50M.jpg
120M时钟
T113-120M.jpg

imx6ull 135M时钟：
imx6-135M.jpg

@jinxiangwzh 在VIN增加一个ioctl，操作到sensor驱动即可。本身VIN也是支持裁剪的，只是说不能动态变化，只能使用之前初始化好，需要修改分辨率则关掉再重新配置。

board/allwinner/suniv-f1c100s/genimage-nand.cfg

flash nand-128M { pebsize = 128K numpebs = 1024 minimum-io-unit-size = 2048 } image sysimage-nand.img { flash { } flashtype = "nand-128M" partition u-boot { image = "u-boot-sunxi-with-nand-spl.bin" size = 512K } partition dtb { offset = 0x80000 image = "devicetree.dtb" size = 128K } partition kernel { offset = 0x100000 image = "zImage" size = 7M } partition rom { offset = 0x800000 image = "rootfs.squashfs" } }

@bedrock 那用到的时候怎么办？全部当整数处理吗

@memory

11307b18-f0ec-46e5-b7af-6e3ef5741576-image.png

（1）如果ramdisk_execute_command变量指定了要运行的程序，则启动它。 ramdisk_execute_command的取值分三种情况， 1）如果命令行参数指定了“rdinit=xxx”，则ramdisk_execute_command等于这个参数指定的程序 2）否则，如果/init程序存在，ramdisk_execute_command就等于“/init”。 3）否则，ramdisk__execute_command为空 （2）如果execute_command变量指定了要运行的程序，启动它。 如果命令行参数指定了"init=..."，则execute_command等于这个参数指定的程序，否则为空 （3）如果ramdisk_execute_command和execute_command参数都没有指定，则依次执行”/sbin/init、/etc/init、/bin/init、/bin/sh“ 在tina系统中，我们可以通过去修改env.cfg文件”rdinit=xxx“或”init=xxx“参数来指定启动的第一个用户进程

@yuzukitsuru 在 ARM Cortex A7 NEON 指令加速 中说：

ここで足し算

@captain 在 T113 MQ-R板子用tina 无法进入系统 中说：

@mhcsoft
能不能贴一下具体的选项呀！全局搜索了一下uboot 下面的 .config ,没发现打开OPTEE的选项被选中。

同问

@honey130602 解决了，忘了复制lichee/linux-4.9/arch/arm/boot/dts/sun8iw16p1-v536-Inomec_SBC.dts

@masterlu 多次收发123的结果是这样的，似乎每一次收发的时间都会比之前的要长一些。。。。
发送：
sh-4.2# echo 123 > /dev/ttysWK0
sh-4.2# echo 123 > /dev/ttysWK0
sh-4.2# echo 123 > /dev/ttysWK0
sh-4.2# echo 123 > /dev/ttysWK0
sh-4.2# echo 123 > /dev/ttysWK0
sh-4.2# echo 123 > /dev/ttysWK0
sh-4.2# echo 123 > /dev/ttysWK0
sh-4.2# echo 123 > /dev/ttysWK0
sh-4.2# echo 123 > /dev/ttysWK0
sh-4.2# echo 123 > /dev/ttysWK0
sh-4.2# echo 123 > /dev/ttysWK0
sh-4.2# echo 123 > /dev/ttysWK0
sh-4.2# echo 123 > /dev/ttysWK0
sh-4.2# echo 123 > /dev/ttysWK0

接收：
sh-4.2# cat /dev/ttysWK0
123

123

123

123

123

123

123

123

123

123

123

123

123

123

123

123

123

123

123

123

123

123

123

123

123

123

123

123

123

123

123

123

123

123

123

123

123

123

123

123

123

123

123

123

@fans168168 是的，rgb bit0->bit7，bit1->bit6.。。。就会显示成这样。

找晕哥请教（白嫖）后，发现是wifi芯片挂了，换了一颗一切正常。已经在自闭了

------run rc.preboot file----- [ 5.242012] EXT4-fs (mmcblk0p7): mounted filesystem with ordered data mode. Opts: (null) ------run rc.modules file----- [ 5.301522] ======== XRADIO WIFI OPEN ======== [ 5.306522] [XRADIO] Driver Label:XR_V02.16.91 _HT40_01.33 Jun 28 2022 09:26:33 [ 5.315096] [XRADIO] Allocated hw_priv @ dec4cc80 [ 5.320607] [XRADIO_ERR] Access_file failed, path:/data/misc/wifi/xr_wifi.conf! [ 5.329635] sunxi-wlan soc@03000000:wlan@0: bus_index: 1 [ 5.336981] sunxi-wlan soc@03000000:wlan@0: check wlan wlan_power voltage: 3300000 [ 5.346911] sunxi-wlan soc@03000000:wlan@0: check wlan io_regulator voltage: 3300000 [ 5.465771] sunxi-mmc sdc1: sdc set ios:clk 0Hz bm PP pm UP vdd 21 width 1 timing LEGACY(SDR12) dt B [ 5.476046] [XRADIO] Detect SDIO card 1 [ 5.517987] sunxi-mmc sdc1: sdc set ios:clk 400000Hz bm PP pm ON vdd 21 width 1 timing LEGACY(SDR12) dt B [ 5.558594] sunxi-mmc sdc1: sdc set ios:clk 400000Hz bm PP pm ON vdd 21 width 1 timing LEGACY(SDR12) dt B [ 5.571806] sunxi-mmc sdc1: sdc set ios:clk 400000Hz bm PP pm ON vdd 21 width 1 timing LEGACY(SDR12) dt B [ 5.592863] sunxi-mmc sdc1: sdc set ios:clk 400000Hz bm PP pm ON vdd 21 width 1 timing SD-HS(SDR25) dt B [ 5.603608] sunxi-mmc sdc1: sdc set ios:clk 50000000Hz bm PP pm ON vdd 21 width 1 timing SD-HS(SDR25) dt B [ 5.614635] sunxi-mmc sdc1: sdc set ios:clk 50000000Hz bm PP pm ON vdd 21 width 4 timing SD-HS(SDR25) dt B [ 5.626154] mmc2: new high speed SDIO card at address 0001 [ 5.633028] [SBUS] XRadio Device:sdio clk=50000000 [ 5.639277] [XRADIO] XRADIO_HW_REV 1.0 detected. [ 5.698281] [XRADIO] xradio_update_dpllctrl: DPLL_CTRL Sync=0x00c00000. [ 5.737650] [XRADIO] Bootloader complete [ 5.825759] [XRADIO] Firmware completed. [ 5.831596] [WSM] Firmware Label:XR_C09.08.52.73_DBG_02.122 2GHZ HT40 May 18 2021 13:36:09 [ 5.849071] [XRADIO] Firmware Startup Done. [ 5.854067] [XRADIO_WRN] enable Multi-Rx! [ 5.872665] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' ------run rc.final file----- Load mpp modules [ 5.938575] [VIN_WARN]sensor_helper_probe: cannot get sensor0_cameravdd supply, setting it to NULL! [ 5.949803] [VIN_WARN]sensor_helper_probe: cannot get sensor1_cameravdd supply, setting it to NULL! [ 5.960159] [VIN_WARN]sensor_helper_probe: cannot get sensor1_avdd supply, setting it to NULL! [ 5.969949] [VIN_WARN]sensor_helper_probe: cannot get sensor1_dvdd supply, setting it to NULL! [ 6.015629] [VIN_ERR]gc2053_mipi request i2c1 adapter failed! [ 6.022373] [VIN_ERR]tp9953 request i2c0 adapter failed! insmod: can't insert '/lib/modules/4.9)ʊz▒չ▒}▒▒▒▒ko': No such file or direct