@daizebin 好的，谢谢。萌新小白感觉还有好多路要走。
S
sat1006 发布的最新帖子
-
t113 longan怎样进入U-boot并且打印信息发布在 Linux
1、查找资料将env.cfg中的bootdelay=0改为了bootdelay=4。编译下载后，在小机启动过程中按任意键没有反应。
使用uart5。sys_config.fex里串口的配置是这样的：
;---------------------------------------------------------------------------------- ;uart configuration ;uart_debug_port |Boot串口控制器编号 | ;uart_debug_tx |Boot串口发送的GPIO配置| ;uart_debug_rx |Boot串口接收的GPIO配置 | ;---------------------------------------------------------------------------------- [uart_para] uart_debug_port = 5 uart_debug_tx = port:PD05<5><1><default><default> uart_debug_rx = port:PD06<5><1><default><default>串口助手进入系统后是可以正常输入的，串口助手的配置是这样的
下面是启动过程的日志信息：
[158]HELLO! BOOT0 is starting! [161]BOOT0 commit : 5224261 [164]set pll start [166]fix vccio detect value:0xc0 [173]periph0 has been enabled [176]set pll end [178][pmu]: bus read error [180]board init ok [182]enable_jtag [184]ZQ value = 0x30 [186]get_pmu_exist() = -1 [188]DRAM BOOT DRIVE INFO: V0.32 [191]DRAM CLK = 360 MHz [194]DRAM Type = 3 (2:DDR2,3:DDR3) [197]DRAMC read ODT off. [200]DRAM ODT value: 0x42. [202]ddr_efuse_type: 0xa [205]mark_id: 0x60 [207]DRAM SIZE =128 M [209]PLL_DDR_CTRL_REG:0xf8001d00 [213]DRAM_CLK_REG:0xc0000000 [215][TIMING DEBUG] MR2= 0x18 [224]DRAM simple test OK. [226]rtc standby flag is 0x0, super standby flag is 0x0 [231]dram size =128 [234]card no is 0 [236]sdcard 0 line count 4 [238][mmc]: mmc driver ver 2021-05-21 14:47 [247][mmc]: Wrong media type 0x0 [250][mmc]: ***Try SD card 0*** [254][mmc]: mmc 0 cmd 8 timeout, err 100 [258][mmc]: mmc 0 cmd 8 err 100 [261][mmc]: mmc 0 send if cond failed [265][mmc]: mmc 0 cmd 55 timeout, err 100 [269][mmc]: mmc 0 cmd 55 err 100 [272][mmc]: mmc 0 send app cmd failed [275][mmc]: ***Try MMC card 0*** [299][mmc]: RMCA OK! [301][mmc]: sdc0 spd mode error, 2 [304][mmc]: force 25m [306][mmc]: mmc 0 bias 0 [310][mmc]: MMC 5.1 [312][mmc]: HSSDR52/SDR25 4 bit [315][mmc]: 25000000 Hz [317][mmc]: 7456 MB [319][mmc]: ***SD/MMC 0 init OK!!!*** [464]Loading boot-pkg Succeed(index=0). [467]Entry_name = u-boot [476]Entry_name = optee [481]Entry_name = dtb [484]tunning data addr:0x430003e8 [487]Jump to second Boot. M/TC: OP-TEE version: 53fe17e2-dirty (gcc version 5.3.1 20160412 (Linaro GCC 5.3-2016.05)) #6 Fri Feb 18 08:54:51 UTC 2022 arm [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 5.4.61+ (user@ubuntu) (arm-linux-gnueabi-gcc (Linaro GCC 5.3-2016.05) 5.3.1 20160412, GNU ld (Linaro_Binutils-2016.05) 2.25.0 Linaro 2016_02) #168 SMP PREEMPT Mon Nov 27 09:31:20 CST 2023 [ 0.000000] CPU: ARMv7 Processor [410fc075] revision 5 (ARMv7), cr=10c5387d [ 0.000000] CPU: div instructions available: patching division code [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache .....各位大佬，是我哪里还没有配置正确嘛？希望大佬们可以指点一下，谢谢！
-
buildroot重新编译的问题咨询发布在 编译和烧写问题专区
如果一开始使用buildroot构建了python3的包，我现在不想构建python3了，menuconfig取消python3选项后，这个包仍然会在target中，不会被主动删除。如果不通过make clean清除buildroot,我可以通过make <package>-dirclean 这条命令取消掉之前构建的python3相关的编译结果嘛？或者我应该通过什么方式可以删除掉之前编译的文件？希望大佬们不吝赐教！
-
回复: t113-s3安装XR829模块卡死发布在 Wireless & Analog Series
@whycanservice 您好。我现在将sdc2的速率降下来后，模块可以正常加载。不会出现死机现象。我对这里的知识不太了解，我现在有两个疑惑想请教您一下：1、我降低这个速率是否会有什么影响？2、我用另一块板子测试，不降低速率也可以进行加载，那会有什么原因导致发生这个问题呢？麻烦您了。
&sdc2 { bus-width = <4>; no-mmc; no-sd; cap-sd-highspeed; /*sd-uhs-sdr12*/ /*sd-uhs-sdr25;*/ /*sd-uhs-sdr50;*/ /*sd-uhs-ddr50;*/ /*sd-uhs-sdr104;*/ /*sunxi-power-save-mode;*/ /*sunxi-dis-signal-vol-sw;*/ cap-sdio-irq; keep-power-in-suspend; ignore-pm-notify; max-frequency = <10000000>; ctl-spec-caps = <0x8>; status = "okay"; }; -
回复: t113-s3安装XR829模块卡死发布在 Wireless & Analog Series
@whycanservice 感谢您的回复。我排查一下这个问题。刚刚接触这方面，知识储备还不够。
-
t113-s3安装XR829模块卡死发布在 Wireless & Analog Series
最近刚刚接触XR829，根据资料、论坛等进行了设备树的配置、编译等工作。使用的sdc2。我从论坛有看到需要sdc2需要改为v5p3x。
当我insmod xr829.ko时，就会卡死在安装过程中，每次卡死的位置不是一样的。如下为两次安装模块时的打印信息：
如下是我设备树相关的配置：
&sdc2 { bus-width = <4>; no-mmc; no-sd; cap-sd-highspeed; /*sd-uhs-sdr12*/ /*sd-uhs-sdr25;*/ /*sd-uhs-sdr50;*/ /*sd-uhs-ddr50;*/ /*sd-uhs-sdr104;*/ /*sunxi-power-save-mode;*/ /*sunxi-dis-signal-vol-sw;*/ cap-sdio-irq; keep-power-in-suspend; ignore-pm-notify; max-frequency = <50000000>; ctl-spec-caps = <0x8>; status = "okay"; }; rfkill: rfkill@0 { compatible = "allwinner,sunxi-rfkill"; chip_en; power_en; pinctrl-0 = <&wlan_pins_a>; pinctrl-names = "default"; status = "okay"; wlan: wlan@0 { compatible = "allwinner,sunxi-wlan"; clock-names = "32k-fanout1"; clocks = <&ccu CLK_FANOUT1_OUT>; wlan_busnum = <0x2>; wlan_regon = <&pio PG 4 GPIO_ACTIVE_HIGH>; wlan_hostwake = <&pio PG 10 GPIO_ACTIVE_HIGH>; /*wlan_power = "VCC-3V3";*/ /*wlan_power_vol = <3300000>;*/ /*interrupt-parent = <&pio>; interrupts = < PG 10 IRQ_TYPE_LEVEL_HIGH>;*/ wakeup-source; status = "okay"; }; }; sdc2_pins_a: sdc2@0 { allwinner,pins = "PC2", "PC3", "PC4", "PC5", "PC6", "PC7"; allwinner,function = "sdc2"; allwinner,muxsel = <3>; allwinner,drive = <3>; allwinner,pull = <1>; pins = "PC2", "PC3", "PC4", "PC5", "PC6", "PC7"; function = "sdc2"; drive-strength = <30>; bias-pull-up; }; sdc2_pins_b: sdc2@1 { pins = "PC2", "PC3", "PC4", "PC5", "PC6", "PC7"; function = "gpio_in"; }; wlan_pins_a:wlan@0 { pins = "PG11"; function = "clk_fanout1"; };sdc2: sdmmc@4022000 { compatible = "allwinner,sunxi-mmc-v5p3x"; device_type = "sdc2"; reg = <0x0 0x04022000 0x0 0x1000>; interrupts = <GIC_SPI 42 IRQ_TYPE_LEVEL_HIGH>; clocks = <&dcxo24M>, <&ccu CLK_PLL_PERIPH0_2X>, <&ccu CLK_MMC2>, <&ccu CLK_BUS_MMC2>; clock-names = "osc24m","pll_periph","mmc","ahb"; resets = <&ccu RST_BUS_MMC2>; reset-names = "rst"; pinctrl-names = "default","sleep"; pinctrl-0 = <&sdc2_pins_a>; pinctrl-1 = <&sdc2_pins_b>; max-frequency = <50000000>; bus-width = <4>; /*broken-cd;*/ /*cd-inverted*/ /*cd-gpios = <&pio PG 6 6 1 2 0>;*/ /* vmmc-supply = <®_3p3v>;*/ /* vqmc-supply = <®_3p3v>;*/ /* vdmc-supply = <®_3p3v>;*/ /*vmmc = "vcc-card";*/ /*vqmc = "";*/ /*vdmc = "";*/ cap-sd-highspeed; no-mmc; no-sd; /*sd-uhs-sdr50;*/ /*sd-uhs-ddr50;*/ /*sd-uhs-sdr104;*/ /*cap-sdio-irq;*/ keep-power-in-suspend; /*ignore-pm-notify;*/ /*sunxi-power-save-mode;*/ /*sunxi-dly-400k = <1 0 0 0 0>; */ /*sunxi-dly-26M = <1 0 0 0 0>;*/ /*sunxi-dly-52M = <1 0 0 0 0>;*/ //sunxi-dly-52M-ddr4 = <1 0 0 0 2>; /*sunxi-dly-52M-ddr8 = <1 0 0 0 0>;*/ //sunxi-dly-104M = <1 0 0 0 1>; /*sunxi-dly-208M = <1 1 0 0 0>;*/ //sunxi-dly-208M = <1 0 0 0 1>; /*sunxi-dly-104M-ddr = <1 0 0 0 0>;*/ /*sunxi-dly-208M-ddr = <1 0 0 0 0>;*/ status = "okay"; };请问是我设备树配置有问题嘛？我该怎样进行排查这个问题呢？