@whycanservice 在 求助，触摸事件上报导致内核崩溃 中说：

崩溃的log有吗

我放弃了，因为我发现在中断中上报可以，在delay_work中调用上报就会有问题，不知道为什么

@whycanservice 谢谢 发完后没多久 就搞定了

@sw123456 win下用cygwin也一样的

D1-H 超频 1.68GHz 测试，提升 67% CoreMark 跑分，ncnn 增速 24%：https://bbs.aw-ol.com/topic/1941/

@haaland 在 我们拆了一款将ChatGPT“落地”的AI语音交互机器人，八核A7全志R58主控 中说：

这玩意能刷个机不

可以刷，但是只有R58的原厂固件，功能应用就没有了

@abcdef
是不是这个效果？
编辑界面挺正常的
qt编辑.png

仿真也正常
qt仿真界面 .png

上板子就字体超大
qt实拍.png

@whycan 在 为什么我的板子复位重启后按上键，没有历史命令了 中说：

@mysteryli

tina默认没有开启cmd history功能，

make menuconfig 搜索 HIST，开启对应的设置，然后重新编译打包烧录，应该就可以了。

好用 还愿

在软件中没有做好千兆网和百兆网的同时适配，只单独支持了千兆网

使能board.dts 的gmac0和gmac1的配置，即同时配置千兆网和百兆网 gmac0: eth@05020000 { phy-mode = "rgmii"; phy-rst = <&pio PI 6 1 0xffffffff 0xffffffff 0>; status = "okay"; }; gmac1: eth@05030000 { phy-mode = "rmii"; status = "okay"; }; 使能sun50iw9p1.dtsi 的gmac0和gmac1的配置 gmac0: eth@05020000 { compatible = "allwinner,sunxi-gmac"; reg = <0x0 0x05020000 0x0 0x10000>, <0x0 0x03000030 0x0 0x4>; interrupts = <GIC_SPI 14 IRQ_TYPE_LEVEL_HIGH>; interrupt-names = "gmacirq"; clocks = <&clk_gmac0>, <&clk_ephy_25m>; clock-names = "gmac", "ephy"; device_type = "gmac0"; pinctrl-0 = <&gmac_pins_a>; pinctrl-1 = <&gmac_pins_b>; pinctrl-names = "default", "sleep"; phy-mode; tx-delay = <7>; rx-delay = <31>; phy-rst; gmac-power0; gmac-power1; gmac-power2; status = "okay"; compatible = "allwinner,sunxi-gmac"; reg = <0x0 0x05030000 0x0 0x1000>, <0x0 0x03000034 0x0 0x4>; interrupts = <GIC_SPI 15 IRQ_TYPE_LEVEL_HIGH>; interrupt-names = "gmacirq"; clocks = <&clk_gmac1>; clock-names = "gmac"; device_type = "gmac1"; pinctrl-0 = <&gmac1_pins_a>; pinctrl-1 = <&gmac1_pins_b>; pinctrl-names = "default", "sleep"; phy-mode; tx-delay = <7>; rx-delay = <31>; phy-rst; gmac-power0; gmac-power1; gmac-power2; status = "okay"; }; 内核配置 1.打开GMAC 配置：搜索SUNXI_GMAC │ Symbol: SUNXI_GMAC [=y] │ │ Type : tristate │ │ Prompt: Allwinner GMAC support │ │ Location: │ │ -> Device Drivers │ │ -> Network device support (NETDEVICES [=y]) │ │ -> Ethernet driver support (ETHERNET [=y]) │ │ (1) -> Allwinner devices (NET_VENDOR_ALLWINNER [=y]) │ │ Defined at drivers/net/ethernet/allwinner/Kconfig:36 │ │ Depends on: NETDEVICES [=y] && ETHERNET [=y] && NET_VENDOR_ALLWINNER [=y] && ARCH_SUNXI [=y] && OF [=y] │ │ Selects: CRC32 [=y] && MII [=y] && PHYLIB [=y] && MDIO_SUNXI 2.打开外部PHY配置：搜索SUNXI_EXT_PHY │ Symbol: SUNXI_EXT_PHY [=y] │ │ Type : boolean │ │ Prompt: Use extern phy │ │ Location: │ │ -> Device Drivers │ │ -> Network device support (NETDEVICES [=y]) │ │ -> Ethernet driver support (ETHERNET [=y]) │ │ -> Allwinner devices (NET_VENDOR_ALLWINNER [=y]) │ │ (1) -> Allwinner GMAC support (SUNXI_GMAC [=y]) │ │ Defined at drivers/net/ethernet/allwinner/Kconfig:50 │ │ Depends on: NETDEVICES [=y] && ETHERNET [=y] && NET_VENDOR_ALLWINNER [=y] && SUNXI_GMAC [=y] 3.打开内部百兆phy的配置：搜索SUNXI_EPHY │ Symbol: SUNXI_EPHY [=y] │ │ Type : tristate │ │ Prompt: Drivers for Allwinnertech EPHY │ │ Location: │ │ -> Device Drivers │ │ -> Network device support (NETDEVICES [=y]) │ │ (1) -> PHY Device support and infrastructure (PHYLIB [=y]) │ │ Defined at drivers/net/phy/Kconfig:152 │ │ Depends on: NETDEVICES [=y] && PHYLIB [=y] && MFD_ACX00 [=y] 打开ACX00的配置：搜索MFD_ACX00 │ Symbol: MFD_ACX00 [=y] │ │ Type : boolean │ │ Prompt: Support Allwinnertech ACX00 │ │ Location: │ │ -> Device Drivers │ │ (1) -> Multifunction device drivers │ │ Defined at drivers/mfd/Kconfig:21 │ │ Depends on: HAS_IOMEM [=y] && I2C [=y]=y │ │ Selects: MFD_CORE [=y] && REGMAP_I2C [=y] && REGMAP_IRQ [=y] │ │ Selected by: SND_SOC_ACX00 [=n] && SOUND [=y] && !M68K && !UML && SND [=y] && SND_SOC [=y] && ARCH_SUN50IW6 [=n]

大佬，能贴下你的配置跟应用程序不，我这跟其他贴子的一样都是32个灯限制

@benlypan 对的。我是忽略了，818是64位cpu，但是寄存器是32位，应该使用4字节访问😬

@whycan 好的，谢谢，是否知道，我运行qt程序在tina系统内置的默认自动动程序sdvcam运行情况下可以运行qt程序，在kill掉tina内置默认应用程序sdvcam后qt无法启动，然后显示显示主题的信息或者什么log都不显示

请问，这个问题解决了吗？
有大神解决了该问题吗？

@whycanservice 请问：目前我用两个线程，一个线程拍照，一个线程gpio 输出控制电机，但是电机转的断断续续（如果只有一个线程跑电机是正常的），看起来好像是调度问题，这种情况怎么解决？

@whycanservice 安装相关依赖后，pack能正常打包，谢谢！

查看硬件电路是否有问题

@q1215200171 请问一下我们在100ASK-V853-Pro上查看内存，发现运行网络前后的内存占用情况是一模一样的，请问一下这个情况正常吗？8b0f56d5-0ac8-49e0-9739-8db5b65f756e-image.png

@whycan 重新烧录固件也还是一样的问题吗？
要是还是一样的问题的话，建议使用TigerDump把分区dump出来看看，目前初步怀疑，有可能是掉电导致的flash误操作

@ddrddr 大佬，这里你是把这一行注释掉吗？还是说做了其它判断？

观察了一下，偶尔有些控件不会凝固，但是文字类的控件（QLabel）就容易凝固（不刷新）。
在 Ubuntu 都没有问题。

@whycan 谢谢！！

@aozima
Xuantie-900 elf newlib gcc Toolchain V2.6.1 B-20220906
Xuantie-900 elf newlib gcc Toolchain V2.4.0 B-20220427

这个比较难复现。也许加一个打印就没这个bug了

原来是室内信号受干扰了，放到室外就正常了

@anruliu 那CS脚是接到GND吗

@gaowei15537316965 66447d1b-3309-4b53-8e17-444e4afc7380-微信图片_20230615161618.png

为啥log只有报错之后的，其余log还有吗

@lucky123456 在 t113的emmc启动，挂载文件系统失败 中说：

@lucky123456 已解决

是怎么回事呢？

@ddrddr
可能是换了晶圆厂或者封装厂，再披一层马甲标识符。

@whycan 哦哦，没说明白，用来传输数据的，我现在用的是DSI-D0P，DSI-D0N，DSI-D1P，DSI-D1N，想改为DSI-D2P，DSI-D2N，DSI-D3P，DSI-D3N，不知道是否可行

非常感谢您的回复。 因此，它们是相同的，只是温度范围不同。 那么，您能指出在哪里可以找到 A133/R818 核心模块的 PCB 文件（布局数据）吗？

echo on > /proc/sys/kernel/printk_devkmsg 后重新运行
aec72faa-fd45-4fe4-9242-7d521eff644e-企业微信截图_16879315471293.png

在make kernel_menuconfig打开inotify即可

79e1c0de-2369-4b6f-b04e-74b248eaa107-企业微信截图_16879354611368.png

重新烧录，可以看到有多个守护进程， 怎么把多余的关掉呢？

@huerli 大佬解决了吗 我也遇到这个问题

@bigfly

换阿里的试一试

@whycan 这个贴我也有看，但是似乎都是基于烧了rotpk.bin的情况分析的。所以这个rotpk.bin是一定要烧才能启动吗，不烧的话跑不下去是吗？上面文档的描述，又好像是不烧可以启动。还望指点一下

@whycanservice
全部的loglevel=7打印的log

U-Boot 2018.07-config-dirty (Jun 16 2023 - 10:30:39 +0800) Allwinner Technology [00.261]DRAM: 64 MiB [00.261]Relocation Offset is: 01f05000 [00.263]secure enable bit: 0 can't support chip type 24064 [00.263]CPU=1008 MHz,PLL6=600 Mhz,AHB=200 Mhz, APB1=100Mhz MBus=300Mhz sunxi flash map init SPI ALL: ready [00.265]flash init start [00.265]workmode = 0,storage type = 1 [00.266][mmc]: mmc driver ver uboot2018:2021-12-20 13:35:00 [00.266][mmc]: get sdc_type fail and use default host:tm1. [00.268][mmc]: can't find node "mmc0",will add new node [00.268][mmc]: fdt err returned <no error> [00.269][mmc]: Using default timing para [00.269][mmc]: SUNXI SDMMC Controller Version:0x50310 [00.282][mmc]: card_caps:0x3000000a [00.282][mmc]: host_caps:0x3000003f [00.283]sunxi flash init ok [00.283]line:703 init_clocks [00.284]drv_disp_init request pwm success, pwm7:pwm7:0x2000c00. [00.294]drv_disp_init finish [00.300]Loading Environment from SUNXI_FLASH... OK [00.316]boot_gui_init:start [00.316]set disp.dev2_output_type fail. using defval=0 [00.703]set disp.fb0_rot_used fail. using defval=0 [00.703]set disp.fb0_rot_degree fail. using defval=0 [00.706]boot_gui_init:finish partno erro : can't find partition bootloader [00.708]bmp_name=bootlogo.bmp size 38454 [00.715]out of usb burn from boot: not need burn key [00.724]LCD open finish [00.738]Item0 (Map) magic is bad [00.739]the secure storage item0 copy0 magic is bad [00.761]Item0 (Map) magic is bad [00.761]the secure storage item0 copy1 magic is bad [00.761]Item0 (Map) magic is bad partno erro : can't find partition private root_partition is rootfs set root to /dev/mmcblk0p5 [00.764]update part info [00.765]update bootcmd [00.766]change working_fdt 0x42ac4da0 to 0x42aa4da0 disable nand error: FDT_ERR_BADPATH [00.768]The storage not support sample function No reserved memory region found in source FDT [00.788]update dts Hit any key to stop autoboot: 0 [01.993]no vendor_boot partition is found Android's image name: d1s-nezha_sd Detect comp none [02.002] Starting kernel ... [02.002][mmc]: MMC Device 2 not found [02.002][mmc]: mmc 2 not find, so not exit ** 1 printk messages dropped ** Zone ranges: DMA32 [mem 0x0000000040000000-0x0000000043ffffff] Normal empty Movable zone start for each node Early memory node ranges node 0: [mem 0x0000000040000000-0x0000000043ffffff] Initmem setup node 0 [mem 0x0000000040000000-0x0000000043ffffff] On node 0 totalpages: 16384 DMA32 zone: 224 pages used for memmap DMA32 zone: 0 pages reserved DMA32 zone: 16384 pages, LIFO batch:3 elf_hwcap is 0x20112d pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768 pcpu-alloc: [0] 0 Built 1 zonelists, mobility grouping on. Total pages: 16160 Kernel command line: earlyprintk=sunxi-uart,0x02500c00 clk_ignore_unused initcall_debug=0 console=ttyS3,1500000 loglevel=8 root=/dev/mmcblk0p5 init=/pseudo_init partitions=boot-resource@mmcblk0p1:env@mmcblk0p2:env-redund@mmcblk0p3:boot@mmcblk0p4:rootfs@mmcblk0p5:recovery@mmcblk0p6:rootfs_data@mmcblk0p7:UDISK@mmcblk0p8 cma=0M snum= mac_addr= wifi_mac= bt_mac= specialstr= gpt=1 androidboot.mode=normal androidboot.hardware=sun20iw1p1 boot_type=1 androidboot.boot_type=1 gpt=1 uboot_message=2018.07-config-dirty(06/16/2023-10:30:39) mbr_offset=1556480 disp_reserve=3686400,0x0000000042b54000 androidboot.dramsize=64 Dentry cache hash table entries: 8192 (order: 4, 65536 bytes, linear) Inode-cache hash table entries: 4096 (order: 3, 32768 bytes, linear) Sorting __ex_table... mem auto-init: stack:off, heap alloc:off, heap free:off Memory: 55728K/65536K available (2902K kernel code, 327K rwdata, 1132K rodata, 116K init, 176K bss, 9808K reserved, 0K cma-reserved) SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 rcu: Preemptible hierarchical RCU implementation. Tasks RCU enabled. rcu: RCU calculated value of scheduler-enlistment delay is 100 jiffies. NR_IRQS: 0, nr_irqs: 0, preallocated irqs: 0 plic: mapped 200 interrupts with 1 handlers for 2 contexts. riscv_timer_init_dt: Registering clocksource cpuid [0] hartid [0] clocksource: riscv_clocksource: mask: 0xffffffffffffffff max_cycles: 0x588fe9dc0, max_idle_ns: 440795202592 ns sched_clock: 64 bits at 24MHz, resolution 41ns, wraps every 4398046511097ns riscv_timer_clockevent depends on broadcast, but no broadcast function available clocksource: timer: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 79635851949 ns Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=24000) pid_max: default: 32768 minimum: 301 Mount-cache hash table entries: 512 (order: 0, 4096 bytes, linear) Mountpoint-cache hash table entries: 512 (order: 0, 4096 bytes, linear) ASID allocator initialised with 65536 entries rcu: Hierarchical SRCU implementation. devtmpfs: initialized random: get_random_u32 called from bucket_table_alloc.isra.27+0x102/0x124 with crng_init=0 clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1911260446275000 ns futex hash table entries: 256 (order: 0, 6144 bytes, linear) pinctrl core: initialized pinctrl subsystem DMA: preallocated 256 KiB pool for atomic allocations cpuidle: using governor menu rtc_ccu: sunxi ccu init OK clock: sunxi ccu init OK clock: sunxi ccu init OK sun6i-dma 3002000.dma-controller: sunxi dma probed iommu: Default domain type: Translated sunxi iommu: irq = 4 SCSI subsystem initialized usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb pwm module init! g2d 5410000.g2d: Adding to iommu group 0 G2D: rcq version initialized.major:252 clocksource: Switched to clocksource riscv_clocksource sun8iw20-pinctrl 2000000.pinctrl: initialized sunXi PIO driver sun8iw20-pinctrl 2000000.pinctrl: 2000000.pinctrl supply vcc-pc not found, using dummy regulator spi spi0: spi0 supply spi not found, using dummy regulator sunxi_spi_resource_get()2438 - [spi0] SPI MASTER MODE sunxi_spi_resource_get()2476 - Failed to get sample mode sunxi_spi_resource_get()2481 - Failed to get sample delay sunxi_spi_resource_get()2485 - sample_mode:-1431633921 sample_delay:-1431633921 sunxi_spi_clk_init()2527 - [spi0] mclk 100000000 sunxi_spi_probe()2978 - [spi0]: driver probe succeed, base ffffffd004058000, irq 31 workingset: timestamp_bits=62 max_order=14 bucket_order=0 squashfs: version 4.0 (2009/01/31) Phillip Lougher ntfs: driver 2.1.32 [Flags: R/W]. io scheduler mq-deadline registered io scheduler kyber registered [DISP]disp_module_init disp 5000000.disp: Adding to iommu group 0 [DISP] disp_init,line:2387: smooth display screen:0 type:1 mode:4 display_fb_request,fb_id:0 [DISP]disp_module_init finish sunxi_sid_init()783 - insmod ok pwm-regulator: supplied by regulator-dummy disp_al_manager_apply ouput_type:1 [DISP] lcd_clk_config,line:774: disp 0, clk: pll(378000000),clk(378000000),dclk(63000000) dsi_rate(63000000) clk real:pll(372000000),clk(372000000),dclk(93000000) dsi_rate(150000000) sun8iw20-pinctrl 2000000.pinctrl: 2000000.pinctrl supply vcc-pd not found, using dummy regulator sun8iw20-pinctrl 2000000.pinctrl: 2000000.pinctrl supply vcc-pg not found, using dummy regulator uart uart1: uart1 supply uart not found, using dummy regulator uart1: ttyS1 at MMIO 0x2500400 (irq = 19, base_baud = 1500000) is a SUNXI sun8iw20-pinctrl 2000000.pinctrl: 2000000.pinctrl supply vcc-pe not found, using dummy regulator uart uart2: uart2 supply uart not found, using dummy regulator uart2: ttyS2 at MMIO 0x2500800 (irq = 20, base_baud = 1500000) is a SUNXI sun8iw20-pinctrl 2000000.pinctrl: 2000000.pinctrl supply vcc-pb not found, using dummy regulator uart uart3: uart3 supply uart not found, using dummy regulator uart3: ttyS3 at MMIO 0x2500c00 (irq = 21, base_baud = 1500000) is a SUNXI sw_console_setup()1807 - console setup baud 1500000 parity n bits 8, flow n printk: console [ttyS3] enabled uart uart4: uart4 supply uart not found, using dummy regulator uart4: ttyS4 at MMIO 0x2501000 (irq = 22, base_baud = 1500000) is a SUNXI uart uart5: uart5 supply uart not found, using dummy regulator uart5: ttyS5 at MMIO 0x2501400 (irq = 23, base_baud = 1500000) is a SUNXI misc dump reg init ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver sunxi-ehci: EHCI SUNXI driver get ehci1-controller wakeup-source is fail. sunxi ehci1-controller don't init wakeup source [sunxi-ehci1]: probe, pdev->name: 4200000.ehci1-controller, sunxi_ehci: 0xffffffe000487ed0, 0x:ffffffd004075000, irq_no:31 sunxi-ehci 4200000.ehci1-controller: 4200000.ehci1-controller supply drvvbus not found, using dummy regulator sunxi-ehci 4200000.ehci1-controller: 4200000.ehci1-controller supply hci not found, using dummy regulator sunxi-ehci 4200000.ehci1-controller: EHCI Host Controller sunxi-ehci 4200000.ehci1-controller: new USB bus registered, assigned bus number 1 sunxi-ehci 4200000.ehci1-controller: irq 49, io mem 0x04200000 Freeing logo buffer memory: 3600K sunxi-ehci 4200000.ehci1-controller: USB 2.0 started, EHCI 1.00 sunxi-ehci 4200000.ehci1-controller: ehci_irq: highspeed device connect hub 1-0:1.0: USB hub found hub 1-0:1.0: 1 port detected ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver sunxi-ohci: OHCI SUNXI driver get ohci1-controller wakeup-source is fail. sunxi ohci1-controller don't init wakeup source [sunxi-ohci1]: probe, pdev->name: 4200400.ohci1-controller, sunxi_ohci: 0xffffffe000488298 sunxi-ohci 4200400.ohci1-controller: 4200400.ohci1-controller supply drvvbus not found, using dummy regulator sunxi-ohci 4200400.ohci1-controller: 4200400.ohci1-controller supply hci not found, using dummy regulator sunxi-ohci 4200400.ohci1-controller: OHCI Host Controller sunxi-ohci 4200400.ohci1-controller: new USB bus registered, assigned bus number 2 sunxi-ohci 4200400.ohci1-controller: irq 50, io mem 0x04200400 hub 2-0:1.0: USB hub found hub 2-0:1.0: 1 port detected sunxi-rtc 7090000.rtc: registered as rtc0 sunxi-rtc 7090000.rtc: setting system clock to 1970-01-01T00:00:29 UTC (29) sunxi-rtc 7090000.rtc: sunxi rtc probed i2c /dev entries driver IR NEC protocol handler initialized sunxi cedar version 1.1 sunxi-cedar 1c0e000.ve: Adding to iommu group 0 VE: install start!!! VE: cedar-ve the get irq is 6 VE: install end!!! VE: sunxi_cedar_probe ashmem: initialized exFAT: Version 1.3.0 get ehci0-controller wakeup-source is fail. sunxi ehci0-controller don't init wakeup source [sunxi-ehci0]: probe, pdev->name: 4101000.ehci0-controller, sunxi_ehci: 0xffffffe000487740, 0x:ffffffd0040d7000, irq_no:2e [sunxi-ehci0]: Not init ehci0 get ohci0-controller wakeup-source is fail. sunxi ohci0-controller don't init wakeup source [sunxi-ohci0]: probe, pdev->name: 4101400.ohci0-controller, sunxi_ohci: 0xffffffe000487b08 [sunxi-ohci0]: Not init ohci0 otg manager soc@3000000:usbc0@0: soc@3000000:usbc0@0 supply usbc not found, using dummy regulator clk: Not disabling unused clocks alloc_fd: slot 0 not NULL! VFS: Cannot open root device "mmcblk0p5" or unknown-block(0,0): error -6 Please append a correct "root=" boot option; here are the available partitions: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) CPU: 0 PID: 1 Comm: swapper Not tainted 5.4.61 #133 Call Trace: [<ffffffe00001f164>] walk_stackframe+0x0/0x98 [<ffffffe00001f31c>] show_stack+0x2a/0x34 [<ffffffe0002dea0a>] dump_stack+0x20/0x28 [<ffffffe000023724>] panic+0xec/0x272 [<ffffffe000000ef2>] mount_block_root+0x214/0x27a [<ffffffe000000fde>] mount_root+0x86/0x90 [<ffffffe000001130>] prepare_namespace+0x148/0x152 [<ffffffe000000b54>] kernel_init_freeable+0x166/0x198 [<ffffffe0002ef170>] kernel_init+0x12/0xee [<ffffffe00001ded0>] ret_from_exception+0x0/0xc ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---

没有看到有sdc的设备号，我用的是SD卡启动

没有遇到哎。可以贴下log看看

@wupaul2001 换个6.1.0的内核好了

d4f0c2b4-9d2b-4283-9f1c-1a9a7b676e37-w.png

配置两个okay

参考：

D1-H （MQ-Pro）驱动 OV5640 摄像头
https://bbs.aw-ol.com/topic/4017/share/1

一. 问题原因：
github上释放的镜像并没有开启TF卡的读写功能！需要自行更改board.dts并编译打包烧录！

二. 解决方法

修改board.dts如下位置 sdc0_pins_a: sdc0@0 { allwinner,pins = "PF0", "PF1", "PF2", "PF3", "PF4", "PF5"; allwinner,function = "sdc0"; allwinner,muxsel = <2>; - allwinner,drive = <1>; + allwinner,drive = <3>; - allwinner,pull = <0>; + allwinner,pull = <1>; }; &sdc0 { - /*cd-gpios = <&pio PF 6 6 1 3 0xffffffff>;*/ + cd-gpios = <&pio PF 6 6 1 3 0xffffffff>; - /*cd-used-24M;*/ + cd-used-24M; }; 检查Kernel Configuration是否设置正确，这些选项已在docker镜像中默认配置好
i. 确认Device Drivers的设置下的MMC/SD/SDIO card support设置为开启
ii. 设置 MMC/SD/SDIO card support ——> Number of minors per block device 为 8
iii. 确认MMC/SD/SDIO card support ——> MMC block device driver 和 Allwinner sunxi SD/MMC Host Controller support设置为开启
iv. 确认File systems下开启对ext4文件系统和VFAT文件系统的支持

三. 仍存在问题

tf卡不支持热插拔，一但拔出需要重启系统 sdc1仍然报错，但是wifi部分正常 tf卡时不时就报以下错误 [ 45.129171] sunxi-mmc sdc0: smc 0 p0 err, cmd 24, WR EBE !! [ 45.135471] sunxi-mmc sdc0: retry:start [ 45.139819] sunxi-mmc sdc0: retry:stop [ 45.144066] sunxi-mmc sdc0: retry:stop recover [ 45.149076] sunxi-mmc sdc0: send manual stop command failed 100 [ 45.155839] sunxi-mmc sdc0: REG_DRV_DL: 0x00030000 [ 45.161253] sunxi-mmc sdc0: REG_SD_NTSR: 0x81710110 [ 45.166717] sunxi-mmc sdc0: REG_NTDL_HS400: 0x20000110 [ 45.172514] sunxi-mmc sdc0: *****retry:re-send cmd***** [ 45.178362] 1,end

6263c42c-52a4-4842-b3a1-cfc288b71345-26311bbacc203beb07c1bdcada48e7c.jpg

@whycanservicem 这个没有被linux占用哦，dts相关引脚配置都被删除，另外特意在E907下单独输出方波都是可以的。

@whycanservice T扩展是什么...

没有人遇到过吗，我源码都没动过

dmesg 有什么信息？驱动正常吗？

@livpo 怎么能做到两秒啊，有资料吗，谢谢

@bayche
buildroot使用指定的gcc单独编译Qt

2.0了 HS兼容FS，LS

@memory
实际操作得结合码率，分辨率，剩余内存等参数，建议先录个文件到本地测试。

@whycan 在 V853-pro开发板4寸屏，运行framebuffer的应用程序，显示不正常 中说：

雪花测试正常吗？

cat /dev/urandom > /dev/fb0

如果雪花测试正常，那么应该是alpha通道的问题，把alpha通道都改成0xFF就可以了。

@whycan 谢谢大佬

怎么降低呢？哪里可以设置？@whycanservice

@daizebin 在 DragonSN烧写PN后可以在哪里可以读出来？ 中说：

@hnjztyx private分区挂载上就可以了

博主这个怎么挂啊 我mount不行

init: Service 'exec 3 (/system/bin/vdc --wait cryptfs enablefilecrypto)' (pid 1753) exited with status 0 waiting took 59.882000 seconds

我最近也遇到了类似启动开机慢的问题，可以跟一下这里的代码，应该是data的文件加密花了59秒导致耗时太长了，源码在android/system/core/init/builtins.cpp 中的 installkey命令，init.rc调用了这个命令去加密data/目录。
不过这个时间可以优化嘛？大佬这么长时间过去了，有没有解决。参考最新的android12代码，我发现android没有做加密/data 目录的动作了（分区表没有配置加密选项）。

要替换几个库文件才正常，可以先试试换个输入法

按照这个文档试一下

03【正点原子】ATK-DLRV1126Qt开发环境搭建V1.0.pdf

@axw_fae make包括了mboot

@whycanservice 感谢，换个版本的内核就找到了

@whycan 谢谢

@whycanservice 那引脚速度有多少

@whycanservice 不好意思，解决了解决了，原来是spi1的设置和rgb冲突了

一般只要修改板级目录下面的 config.xml 就可以了：

device/softwinner/xxxx-yyyyy/overlay/frameworks/base/core/res/res/values/config.xml

<!-- Indicates that connected MAC randomization is supported on this device --> <bool translatable="false" name="config_wifi_connected_mac_randomization_supported">false</bool>

/root/tina-v853-open/kernel/linux-4.9/scripts/dtc
找到文件 dtc-lexer.lex.c_shipped
搜索YYLTYPE yylloc
修订为 extern YYLTYPE yylloc

问题就解决了

@whycanservice
所以目前来看应该只有两个办法了
1、PC交叉编译，install到rootfs中
2、PC交叉编译一个能用的gcc，install到rootfs中，再编译所需要的应用，再install？
感觉第二个方法可以玩一下试试👶 👶

@newcastle 好几种可能，先看https://blog.csdn.net/weixin_43094346/article/details/132017068

如果这里面和你的问题不一样，有可能是你的引脚配置问题，比如我的拿到了emmc的板子用了nand的源码，会导致引脚错误，配置sdc2用到了一系列PC引脚，而nand原本应用的SPI0也是PC引脚，不把SPI关掉会导致引脚冲突，从而导致sdc无法调用引脚而无法调用emmc。此错误也会提示无法打开root device，但是实际的原因在上一页，会提示你该引脚已经被调用。

请问您会开启矢量指令的支持了吗？我也正在尝试解决这方面的问题

@zznzzn
话说199G还压榨什么，我的4T硬盘都不分区的。

152b28d5-b37f-4aac-aa8e-a260c89695bb-image.png

378434f3-402c-4523-ae83-a0554f0f4fe5-image.png

需要重新配置 config，表示当前kernel中不存在.config配置文件，或者该配置文件与配置的arch不匹配

@whycanservice 你好 该问题已解决。
sudo dpkg --add-architecture i386
sudo apt-get update
sudo apt install gcc-multilib
sudo apt install libc6:i386 libstdc++6:i386 lib32z1

谢谢

@whycanservice 好的，另外还想请教个问题，我这边profile debug的时候，带宽什么的是0？这是什么情况
1b4ce826-43dc-4859-80ee-c5dc43a0201e-图片.png

@whycanservice 非常感谢！

@whycanservice 感谢，非常感谢！

@whycanservice 谢谢
应该是相关依赖没有打开，因传文件需要，后来发现用WIFI ADB更简单，就直接不用NFS了。

v８５１ｓ 板子［ｔｉｎａ５．０］服务器端运行如下命令【可以设置启动时加载】：
killall adbd
** adbd -D tcpip:5555 >/dev/null&** ; 5555是监听端口号

开发机Win10，ａｄｂ工具下载google的Version 30.0.5-6877874：
adb disconnect
adb connect 192.168.0.110:5555　；192.168.0.110　板子WIFI的IP地址
运行adb shell 或者文件传输

通过WIFI连接ａｄｂ很容易连接［USB adb 连接网上发现很多问题］，对开发应用程序用起来很方便，局限是WIFI必须先调通。

@fawen 请问如何解决呢，感谢！

@whycanservice

解压出来了，谢谢

7a9f98d5-adc2-4f6a-a024-18bf1291305d-image.png

@a1064038953

要不要试一试我这里面的纯净版ubuntu18.04虚拟机：下载链接

编译Android10/Android12都没问题。

@ant1423 lvgl也能实现，一般吧，这几个图看起来不是特别复杂

@memory Android日志会有 I/WindowManager( 2046): SAFE MODE ENABLED (menu=0 s=0 dpad=-1 trackball=-1)报错，然后根据括号内容的值提示，就能找到原因。

强硬去除安全模式的修改，可做参考

diff --git a/services/core/java/com/android/server/power/ShutdownThread.java b/services/core/java/com/android/server/power/ShutdownThread.java index bdb5d3f0..c11d555c 100644 --- a/services/core/java/com/android/server/power/ShutdownThread.java +++ b/services/core/java/com/android/server/power/ShutdownThread.java @@ -255,7 +255,7 @@ public final class ShutdownThread extends Thread { } mReboot = true; - mRebootSafeMode = true; + mRebootSafeMode = false; mRebootHasProgressBar = false; mReason = null; shutdownInner(context, confirm); diff --git a/services/core/java/com/android/server/wm/WindowManagerService.java b/services/core/java/com/android/server/wm/WindowManagerService.java index d8bb8d86..8193de92 100644 --- a/services/core/java/com/android/server/wm/WindowManagerService.java +++ b/services/core/java/com/android/server/wm/WindowManagerService.java @@ -4500,7 +4500,7 @@ public class WindowManagerService extends IWindowManager.Stub Log.i(TAG_WM, "SAFE MODE not enabled"); } mPolicy.setSafeMode(mSafeMode); - return mSafeMode; + return false; } public void displayReady() {

问题已解决，没下载工具busybox

@chrisvista
请问解决没？我和你遇到相同的问题，能指教一下？谢谢！

@xiaowenge 明白了，谢谢！

@newcastle 多了个"/"应该是“make kernel_menuconfig”（不含引号）

@whycanservice 你好，这个源码应该是做UVC解码显示的吧，我想要的是USB的摄像头接入后可以实时显示采集到的图像视频，并且同步把数据编码封装成MP4进行存储

uboot也需要配置对应的波特率，因为UART是boot0初始化的，进入UBOOT所计算的时钟如果没有修改就会出现乱码

@awwwwa 感谢感谢，翻手册的时候没注意到这一段，下次看手册要仔细点了49ad5c58-e407-4fe3-b775-a823ad8ce477-40e311d4-9b3b-4bf8-842a-3eec031002b7.png

@awwwwa 感谢您的帮助，我看一下

@whycan 在 T113-S3 配置横屏显示系统跑不起来问题 中说：

横屏没有问题的，现在正常竖屏可以了吗？
因为这个驱动芯片自带GRAM，所以不需要soc参与也很容易各种旋转。

目前竖屏能显示了，但是有这种竖纹阴影显示，你看下图片，这种问题怎么解决？
屏幕异常.png

你所说的ST7701S自带GRAM，不需要soc参与也很容易各种旋转。那是不是在初始化代码里配置，
我把屏幕厂商给的初始化代码发出来，帮忙看看怎么修改的。多谢~~

SPI_WriteComm(0xFF); SPI_WriteData(0x77); SPI_WriteData(0x01); SPI_WriteData(0x00); SPI_WriteData(0x00); SPI_WriteData(0x13); SPI_WriteComm(0xEF); SPI_WriteData(0x08); SPI_WriteComm(0xFF); SPI_WriteData(0x77); SPI_WriteData(0x01); SPI_WriteData(0x00); SPI_WriteData(0x00); SPI_WriteData(0x10); SPI_WriteComm(0xC0); SPI_WriteData(0x77); SPI_WriteData(0x00); SPI_WriteComm(0xC1); SPI_WriteData(0x0C); SPI_WriteData(0x0C); SPI_WriteComm(0xC2); SPI_WriteData(0x07); SPI_WriteData(0x02); SPI_WriteComm(0xCC); SPI_WriteData(0x10); SPI_WriteComm(0xB0); SPI_WriteData(0x00); SPI_WriteData(0x0C); SPI_WriteData(0x19); SPI_WriteData(0x0B); SPI_WriteData(0x0F); SPI_WriteData(0x06); SPI_WriteData(0x05); SPI_WriteData(0x08); SPI_WriteData(0x08); SPI_WriteData(0x1F); SPI_WriteData(0x04); SPI_WriteData(0x11); SPI_WriteData(0x0F); SPI_WriteData(0x26); SPI_WriteData(0x2F); SPI_WriteData(0x1D); SPI_WriteComm(0xB1); SPI_WriteData(0x00); SPI_WriteData(0x17); SPI_WriteData(0x19); SPI_WriteData(0x0F); SPI_WriteData(0x12); SPI_WriteData(0x05); SPI_WriteData(0x05); SPI_WriteData(0x08); SPI_WriteData(0x07); SPI_WriteData(0x1F); SPI_WriteData(0x03); SPI_WriteData(0x10); SPI_WriteData(0x10); SPI_WriteData(0x27); SPI_WriteData(0x2F); SPI_WriteData(0x1D); SPI_WriteComm(0xFF); SPI_WriteData(0x77); SPI_WriteData(0x01); SPI_WriteData(0x00); SPI_WriteData(0x00); SPI_WriteData(0x11); SPI_WriteComm(0xB0); SPI_WriteData(0x4D); SPI_WriteComm(0xB1); SPI_WriteData(0x4F); SPI_WriteComm(0xB2); SPI_WriteData(0x82); SPI_WriteComm(0xB3); SPI_WriteData(0x80); SPI_WriteComm(0xB5); SPI_WriteData(0x4E); SPI_WriteComm(0xB7); SPI_WriteData(0x85); SPI_WriteComm(0xB8); SPI_WriteData(0x20); SPI_WriteComm(0xC1); SPI_WriteData(0x78); SPI_WriteComm(0xC2); SPI_WriteData(0x78); SPI_WriteComm(0xD0); SPI_WriteData(0x88); SPI_WriteComm(0xE0); SPI_WriteData(0x00); SPI_WriteData(0x00); SPI_WriteData(0x02); SPI_WriteData(0x00); SPI_WriteData(0x00); SPI_WriteData(0x0C); SPI_WriteComm(0xE1); SPI_WriteData(0x02); SPI_WriteData(0x8C); SPI_WriteData(0x04); SPI_WriteData(0x8C); SPI_WriteData(0x01); SPI_WriteData(0x8C); SPI_WriteData(0x03); SPI_WriteData(0x8C); SPI_WriteData(0x00); SPI_WriteData(0x44); SPI_WriteData(0x44); SPI_WriteComm(0xE2); SPI_WriteData(0x03); SPI_WriteData(0x03); SPI_WriteData(0x03); SPI_WriteData(0x03); SPI_WriteData(0x00); SPI_WriteData(0x00); SPI_WriteData(0xD4); SPI_WriteData(0x00); SPI_WriteData(0x00); SPI_WriteData(0x00); SPI_WriteData(0xD4); SPI_WriteData(0x00); SPI_WriteComm(0xE3); SPI_WriteData(0x00); SPI_WriteData(0x00); SPI_WriteData(0x33); SPI_WriteData(0x33); SPI_WriteComm(0xE4); SPI_WriteData(0x44); SPI_WriteData(0x44); SPI_WriteComm(0xE5); SPI_WriteData(0x09); SPI_WriteData(0xD2); SPI_WriteData(0x35); SPI_WriteData(0x8C); SPI_WriteData(0x0B); SPI_WriteData(0xD4); SPI_WriteData(0x35); SPI_WriteData(0x8C); SPI_WriteData(0x05); SPI_WriteData(0xCE); SPI_WriteData(0x35); SPI_WriteData(0x8C); SPI_WriteData(0x07); SPI_WriteData(0xD0); SPI_WriteData(0x35); SPI_WriteData(0x8C); SPI_WriteComm(0xE6); SPI_WriteData(0x00); SPI_WriteData(0x00); SPI_WriteData(0x33); SPI_WriteData(0x33); SPI_WriteComm(0xE7); SPI_WriteData(0x44); SPI_WriteData(0x44); SPI_WriteComm(0xE8); SPI_WriteData(0x08); SPI_WriteData(0xD1); SPI_WriteData(0x35); SPI_WriteData(0x8C); SPI_WriteData(0x0A); SPI_WriteData(0xD3); SPI_WriteData(0x35); SPI_WriteData(0x8C); SPI_WriteData(0x04); SPI_WriteData(0xCD); SPI_WriteData(0x35); SPI_WriteData(0x8C); SPI_WriteData(0x06); SPI_WriteData(0xCF); SPI_WriteData(0x35); SPI_WriteData(0x8C); SPI_WriteComm(0xEB); SPI_WriteData(0x00); SPI_WriteData(0x01); SPI_WriteData(0xE4); SPI_WriteData(0xE4); SPI_WriteData(0x44); SPI_WriteData(0x33); SPI_WriteComm(0xED); SPI_WriteData(0xFF); SPI_WriteData(0xFF); SPI_WriteData(0xF7); SPI_WriteData(0x65); SPI_WriteData(0x4A); SPI_WriteData(0x10); SPI_WriteData(0x3B); SPI_WriteData(0xFF); SPI_WriteData(0xFF); SPI_WriteData(0xB3); SPI_WriteData(0x01); SPI_WriteData(0xA4); SPI_WriteData(0x56); SPI_WriteData(0x7F); SPI_WriteData(0xFF); SPI_WriteData(0xFF); SPI_WriteComm(0xEF); SPI_WriteData(0x10); SPI_WriteData(0x0D); SPI_WriteData(0x04); SPI_WriteData(0x08); SPI_WriteData(0x3F); SPI_WriteData(0x1F); SPI_WriteComm(0xFF); SPI_WriteData(0x77); SPI_WriteData(0x01); SPI_WriteData(0x00); SPI_WriteData(0x00); SPI_WriteData(0x00); SPI_WriteComm(0x3A); SPI_WriteData(0x55); SPI_WriteComm(0x11); Delay(120); SPI_WriteComm(0x29); //自检模式 /* SPI_WriteComm(0xFF); SPI_WriteData(0x77); SPI_WriteData(0x01); SPI_WriteData(0x00); SPI_WriteData(0x00); SPI_WriteData(0x12); SPI_WriteComm(0xD1); SPI_WriteData(0x81); SPI_WriteComm(0xD2); SPI_WriteData(0x08); */

@whycan 在 d1-h sdk编译版本 中说：

--来自百度网盘超级会员V4的分享
hi，这是我用百度网盘分享的内容~复制这段内容打开「百度网盘」APP即可获取 
链接:https://pan.baidu.com/s/1tADvigD1xtOWqieJmcuPkA?pwd=awol 
提取码:awol

这里面的Ubuntu18.04编译tina,Android10,Android12都没问题。

@wordiansom 还没有试过呢

最好还是详细描述下修改的步骤以及详细的烧录、启动log，才好分析

@lancer 指的是预置自己的程序到rootfs分区吧？
如果是的话，参考package下面找个简单的工程自己添加并编译打包到文件系统。

进入lichee->brandy-2.0->u-boot-2018->configs
修改文件sun8iw20p1_uart3_defconfig
这个可以参考D1S的文件修改，其实这个文件就是少了屏幕，logo一段，从D1S上复制过去就可以了

62249702-9aef-4b3f-bdf0-ead755db0466-ea652dc4364bfb541a5e74e37255305.png

搞定搞定，谢谢。

你好，请问下你解决了吗

@whycan 韦老师这个板子学习视频更了3个就停了，停更了几个月，纠结啊

用的是哪个linux版本呢？

@awwwwa Tina 的SDK不是还能编译buildroot吗，文件系统咋buildroot上编译的

@zzz123 还是编译iproute2，有一些头文件重复定义的去把编译器里的改掉就好了，不用全部编译完，能把ip命令编译出来就好

是个不错的思路，V851s我也要试试

@zznzzn 您好，可以屏蔽/etc/init.d/rcS脚本中对应代码

@awwwwa 多谢指导，已经解决，整个clean以后重编就生效了，搞不懂之前咋回事，好在最后解决了

看了一下是NES模拟器吧，应该设置RGB555的画布试试看

src.zip

@aw2022 自己写用户代码，调用MPP的muxer模块的API