导航

    全志在线开发者论坛

    • 注册
    • 登录
    • 搜索
    • 版块
    • 话题
    • 在线文档
    • 社区主页
    1. 主页
    2. awwwwa
    3. 帖子
    A
    • 资料
    • 关注 0
    • 粉丝 18
    • 我的积分 14191
    • 主题 11
    • 帖子 550
    • 最佳 148
    • 群组 1

    awwwwa 发布的帖子

    • 回复: V853我们来了!!!

      Tina 4.0:
      tina_v851se-tinyvision_uart0.zip

      Tina 4.0 摄像头测试:
      e8ce3a5d-7cbf-40a3-b16a-1989ce206407-tina_v851se-tinyvision_uart0.zip

      Tina 5.0:
      v851se_linux_tinyvision_uart0_SDNand.zip

      Patch:
      e4350d20-eda5-4ff5-b708-5901f5469aa9-tinyvision_patch.tar.gz

      tinyvision_syterboot.zip

      tinyvision_e907_boot.zip

      71d8a58c-6fe2-4a93-96ee-b12bb883b2e1-摄像头测试固件.img

      d0ef81d9-3893-4c2c-8903-711cf397a3bb-tinyvision.tgz

      CONFIG_ARM=y
      CONFIG_ARCH_SUNXI=y
      CONFIG_MACH_SUN8IW21=y
      CONFIG_SUNXI_GPIO_V2=y
      #CONFIG_AXP_GPIO=y
      CONFIG_SYS_CONFIG_NAME="sun8iw21p1"
      CONFIG_DEFAULT_DEVICE_TREE="sun8iw21p1-soc-system"
      # CONFIG_SYS_MALLOC_CLEAR_ON_INIT is not set
      CONFIG_CONSOLE_MUX=y
      CONFIG_SUNXI_NECESSARY_REPLACE_FDT=y
      CONFIG_RESERVE_FDT_SIZE=0x20000
      CONFIG_PRE_CONSOLE_BUFFER=n
      # CONFIG_OF_BOARD=y
      CONFIG_OF_SEPARATE=y
      CONFIG_SYS_TEXT_BASE=0x42000000
      CONFIG_SUNXI_FDT_ADDR=0x41800000
      CONFIG_SUNXI_MALLOC_LEN=0x1400000
      # Environment
      # CONFIG_ENV_IS_IN_SUNXI_FLASH=y
      # CONFIG_SYS_MAXARGS=64
      # CONFIG_SUNXI_REDUNDAND_ENVIRONMENT=y
      # CONFIG_SYS_REDUNDAND_ENVIRONMENT=y
      # CONFIG_SUNXI_ENV_PARTITION="env"
      CONFIG_SUNXI_ENV_BACKUP=y
      # CONFIG_SUNXI_ENV_REDUNDAND_PARTITION="env-redund"
      # CONFIG_ENV_SIZE=0x20000
      
      #system
      CONFIG_ARM_SMCCC=y
      CONFIG_SUNXI_DMA=y
      CONFIG_CLK_SUNXI=y
      #SPI
      CONFIG_SPI=y
      CONFIG_SUNXI_SPI=y
      CONFIG_SPI_USE_DMA=y
      CONFIG_SPI_FLASH=y
      CONFIG_SPI_FLASH_WINBOND=y
      CONFIG_SPI_FLASH_EON=y
      CONFIG_SPI_FLASH_GIGADEVICE=y
      CONFIG_SPI_FLASH_ISSI=y
      CONFIG_SPI_FLASH_MACRONIX=y
      CONFIG_SPI_FLASH_SPANSION=y
      CONFIG_SPI_FLASH_ATMEL=y
      CONFIG_SPI_FLASH_STMICRO=y
      CONFIG_SPI_FLASH_SST=y
      CONFIG_SPI_FLASH_PUYA=y
      CONFIG_SPI_FLASH_FM=y
      CONFIG_SPI_FLASH_XT=y
      CONFIG_SPI_FLASH_ADESTO=y
      CONFIG_SPI_FLASH_XMC=y
      CONFIG_SPI_SAMP_DL_EN=y
      
      CONFIG_SF_DEFAULT_SPEED=50000000
      # BIT(12) BIT(13) (SPI_RX_DUAL|SPI_RX_QUAD)
      CONFIG_SF_DEFAULT_MODE=0x3000
      CONFIG_SPINOR_UBOOT_OFFSET=128
      CONFIG_SPINOR_LOGICAL_OFFSET=2016
      CONFIG_SPINOR_UBOOT_SECURE_OFFSET=128
      CONFIG_SPINOR_LOGICAL_SECURE_OFFSET=2200
      
      
      #axp
      CONFIG_SYS_I2C_SUNXI=y
      CONFIG_I2C4_ENABLE=y
      CONFIG_SYS_SUNXI_I2C4_SLAVE=0x34
      CONFIG_SYS_SUNXI_I2C4_SPEED=400000
      CONFIG_SUNXI_POWER=y
      CONFIG_SUNXI_PMU=y
      CONFIG_SUNXI_BMU=y
      CONFIG_AXP2101_POWER=y
      CONFIG_AXP2101_SUNXI_I2C_SLAVE=0x34
      
      
      #key
      #CONFIG_SUNXI_PHY_KEY=y
      #CONFIG_SUNXI_LRADC_KEY=y
      
      
      #crypto driver
      CONFIG_SUNXI_CE_DRIVER=y
      CONFIG_SUNXI_CE_23=y
      
      #CONFIG_SF_DEFAULT_SPEED=50000000
      # BIT(12) BIT(13) (SPI_RX_DUAL|SPI_RX_QUAD)
      #CONFIG_SF_DEFAULT_MODE=0x3000
      
      #
      # PWM_SUNXI
      #
      CONFIG_PWM_SUNXI=y
      # CONFIG_PWM_SUNXI_NEW is not set
      
      #CONFIG_SPINOR_UBOOT_OFFSET=128
      #CONFIG_SPINOR_LOGICAL_OFFSET=2016
      
      # flash
      CONFIG_SUNXI_SDMMC=y
      CONFIG_MMC=y
      CONFIG_SUNXI_FLASH=y
      CONFIG_SUNXI_NAND=y
      CONFIG_SUNXI_UBIFS=y
      CONFIG_SUNXI_COMM_NAND_V1=y
      CONFIG_SUNXI_SPINOR=y
      
      #usb otg config
      CONFIG_SUNXI_USB=y
      CONFIG_SUNXI_EFEX=y
      CONFIG_SUNXI_BURN=y
      CONFIG_SUNXI_FASTBOOT=y
      #partition
      CONFIG_EFI_PARTITION=y
      
      #image
      CONFIG_ANDROID_BOOT_IMAGE=y
      
      #sprite
      CONFIG_SUNXI_SPRITE=y
      CONFIG_SUNXI_SECURE_STORAGE=y
      CONFIG_SUNXI_SPRITE_CARTOON=y
      
      #secure feature
      CONFIG_SUNXI_SECURE_BOOT=y
      CONFIG_SUNXI_IMAGE_VERIFIER=y
      CONFIG_SUNXI_KEYBOX=y
      CONFIG_SUNXI_DRM_SUPPORT=y
      CONFIG_SUNXI_EXTERN_SECURE_MM_LAYOUT=y
      
      
      CONFIG_SUNXI_HOMLET=y
      CONFIG_SUNXI_HDCP_HASH=y
      CONFIG_SUNXI_HDCP_IN_SECURESTORAGE=y
      
      #cmd
      CONFIG_CMD_SUNXI_TIMER=y
      CONFIG_CMD_SUNXI_SPRITE=y
      CONFIG_CMD_SUNXI_EFEX=y
      CONFIG_CMD_SUNXI_BURN=y
      CONFIG_CMD_GPT=y
      CONFIG_CMD_FAT=y
      CONFIG_CMD_FASTBOOT=y
      CONFIG_CMD_SUNXI_DMA=y
      CONFIG_CMD_SUNXI_CLK=y
      CONFIG_CMD_SUNXI_MEMTEST=y
      CONFIG_CMD_PART=y
      CONFIG_CMD_SUNXI_AUTO_FEL=n
      CONFIG_CMD_SUNXI_BOOTR=y
      #arisc
      #CONFIG_SUNXI_ARISC_EXIST=y
      
      # CONFIG_SUNXI_INITRD_ROUTINE is not set
      #dsp
      #CONFIG_XTENSA_DSP=y
      #riscv
      #CONFIG_RISCV_E907=y
      
      CONFIG_SUNXI_ARM_SOFT_FP=y
      CONFIG_USE_PRIVATE_LIBGCC=y
      #
      # BOOT GUI
      #
      CONFIG_BOOT_GUI=y
      # CONFIG_UPDATE_DISPLAY_MODE is not set
      # CONFIG_CONFIG_LCD_CHECK_SKIP_OPEN is not set
      # CONFIG_BOOT_GUI_DOUBLE_BUF is not set
      # CONFIG_BOOT_GUI_TEST is not set
      
      #
      # SUNXI LOGO DISPLAY
      #
      CONFIG_CMD_SUNXI_BMP=y
      # CONFIG_SUNXI_SPINOR_BMP is not set
      # CONFIG_ENABLE_ADVERT_PICTURE is not set
      # CONFIG_SUNXI_SPINOR_JPEG is not set
      # CONFIG_CMD_SUNXI_JPEG is not set
      CONFIG_DISP2_SUNXI=y
      # CONFIG_HDMI_DISP2_SUNXI is not set
      # CONFIG_HDMI2_DISP2_SUNXI is not set
      # CONFIG_VDPO_DISP2_SUNXI is not set
      # CONFIG_TV_DISP2_SUNXI is not set
      # CONFIG_EDP_DISP2_SUNXI is not set
      # CONFIG_EINK200_SUNXI is not set
      
      #
      # LCD panels select
      #
      # CONFIG_LCD_SUPPORT_GG1P4062UTSW is not set
      # CONFIG_LCD_SUPPORT_DX0960BE40A1 is not set
      # CONFIG_LCD_SUPPORT_TFT720X1280 is not set
      # CONFIG_LCD_SUPPORT_FD055HD003S is not set
      # CONFIG_LCD_SUPPORT_HE0801A068 is not set
      # CONFIG_LCD_SUPPORT_ILI9341 is not set
      # CONFIG_LCD_SUPPORT_LH219WQ1 is not set
      # CONFIG_LCD_SUPPORT_LS029B3SX02 is not set
      # CONFIG_LCD_SUPPORT_LT070ME05000 is not set
      # CONFIG_LCD_SUPPORT_S6D7AA0X01 is not set
      # CONFIG_LCD_SUPPORT_T27P06 is not set
      # CONFIG_LCD_SUPPORT_TFT720x1280 is not set
      # CONFIG_LCD_SUPPORT_WTQ05027D01 is not set
      # CONFIG_LCD_SUPPORT_H245QBN02 is not set
      # CONFIG_LCD_SUPPORT_ST7789V is not set
      # CONFIG_LCD_SUPPORT_ST7796S is not set
      # CONFIG_LCD_SUPPORT_ST7701S is not set
      # CONFIG_LCD_SUPPORT_T30P106 is not set
      # CONFIG_LCD_SUPPORT_TO20T20000 is not set
      # CONFIG_LCD_SUPPORT_FRD450H40014 is not set
      # CONFIG_LCD_SUPPORT_S2003T46G is not set
      # CONFIG_LCD_SUPPORT_WILLIAMLCD is not set
      # CONFIG_LCD_SUPPORT_LQ101R1SX03 is not set
      # CONFIG_LCD_SUPPORT_INET_DSI_PANEL is not set
      # CONFIG_LCD_SUPPORT_WTL096601G03 is not set
      # CONFIG_LCD_SUPPORT_BP101WX1 is not set
      # CONFIG_LCD_SUPPORT_M133X56 is not set
      # CONFIG_LCD_SUPPORT_K101IM2QA04 is not set
      # CONFIG_LCD_SUPPORT_K101IM2BYL02L is not set
      # CONFIG_LCD_SUPPORT_FX070 is not set
      # CONFIG_LCD_SUPPORT_M101B31 is not set
      # CONFIG_LCD_SUPPORT_CC08021801_310_800X1280 is not set
      # CONFIG_LCD_SUPPORT_KD101NA5 is not set
      # CONFIG_LCD_SUPPORT_KD070D57 is not set
      # CONFIG_LCD_SUPPORT_ZS080NI4003E7H3H_A is not set
      # CONFIG_LCD_SUPPORT_K080_IM2HYL802R_800X1280 is not set
      # CONFIG_LCD_SUPPORT_K101_IM2BYL02_L_800X1280 is not set
      # CONFIG_LCD_SUPPORT_JD9366AB_3 is not set
      # CONFIG_LCD_SUPPORT_TFT08006 is not set
      CONFIG_LCD_SUPPORT_ST7701S_G5=y
      CONFIG_LCD_SUPPORT_T050K589=y
      CONFIG_LCD_SUPPORT_JD9161Z_MIPI=y
      CONFIG_LCD_SUPPORT_ICN6202=y
      
      #
      # Display engine feature select
      #
      # CONFIG_DISP2_SUNXI_SUPPORT_SMBL is not set
      # CONFIG_DISP2_SUNXI_SUPPORT_ENAHNCE is not set
      # CONFIG_SUNXI_TV_FASTLOGO is not set
      # CONFIG_SUNXI_FASTLOGO_JPEG is not set
      
      发布在 V Series
      A
      awwwwa
    • 回复: A133 Linux GPU 测试例程

      @liangzhicheng 可以用glmark2测试

      发布在 Linux
      A
      awwwwa
    • 回复: V853移植rk628成功出图,但是图片颜色异常,求个排查思路

      @xjy_5 一般2M摄像头都是1920*1088的,可能就按这个来处理了

      发布在 V Series
      A
      awwwwa
    • T527 使用 DRM 驱动 edp 屏幕

      进入 menuconfig 勾选 drm 驱动

      ./build.sh menuconfig
      

      先勾选 DRM

      cb61de74-4427-4634-ad9a-7fb0355f0c2c-image.png

      再勾选 DRM 驱动

      d5bfe0b4-9c31-4685-9f5a-edf9a314ecc8-image.png

      选择驱动的phy

      cd43edeb-294c-4e54-bca2-02fcd83870d6-image.png

      选择屏幕

      3296da2b-cc7e-4440-9379-c538a52c59e1-image.png

      选择 general 屏幕面板驱动

      c6048ab0-44cc-4889-a0b4-8c6ef4d76cb3-image.png

      关闭原来的 disp2 fbdev 驱动

      f8db1009-4b34-4d8e-839d-3c7a358126d6-image.png

      配置设备树

      	edp_panel_backlight: edp_backlight {
      		compatible = "pwm-backlight";
      		status = "okay";
      		brightness-levels = <
      			  0   1   2   3   4   5   6   7
      			  8   9  10  11  12  13  14  15
      			 16  17  18  19  20  21  22  23
      			 24  25  26  27  28  29  30  31
      			 32  33  34  35  36  37  38  39
      			 40  41  42  43  44  45  46  47
      			 48  49  50  51  52  53  54  55
      			 56  57  58  59  60  61  62  63
      			 64  65  66  67  68  69  70  71
      			 72  73  74  75  76  77  78  79
      			 80  81  82  83  84  85  86  87
      			 88  89  90  91  92  93  94  95
      			 96  97  98  99 100 101 102 103
      			104 105 106 107 108 109 110 111
      			112 113 114 115 116 117 118 119
      			120 121 122 123 124 125 126 127
      			128 129 130 131 132 133 134 135
      			136 137 138 139 140 141 142 143
      			144 145 146 147 148 149 150 151
      			152 153 154 155 156 157 158 159
      			160 161 162 163 164 165 166 167
      			168 169 170 171 172 173 174 175
      			176 177 178 179 180 181 182 183
      			184 185 186 187 188 189 190 191
      			192 193 194 195 196 197 198 199
      			200 201 202 203 204 205 206 207
      			208 209 210 211 212 213 214 215
      			216 217 218 219 220 221 222 223
      			224 225 226 227 228 229 230 231
      			232 233 234 235 236 237 238 239
      			240 241 242 243 244 245 246 247
      			248 249 250 251 252 253 254 255>;
      		default-brightness-level = <200>;
      		enable-gpios = <&pio PI 5 GPIO_ACTIVE_HIGH>;
      		/* power-supply = <&reg_backlight_12v>; */
      		pwms = <&a_pwm 5 5000000 0>;
      	};
      
      	edp_panel: edp_panel {
      		compatible = "edp-general-panel";
      		status = "okay";
      		power0-supply = <&reg_dcdc4>;
      
      		backlight = <&edp_panel_backlight>;
      
      		panel-timing {
      			clock-frequency = <348577920>; /* pixel clock */
      			hactive = <2560>;
      			hback-porch = <120>;
      			hfront-porch = <88>;
      			hsync-len = <32>;
      			vactive = <1600>;
      			vback-porch = <71>;
      			vfront-porch = <28>;
      			vsync-len = <5>;
      			/* hor_sync_polarity */
      			hsync-active = <1>;
      			/* ver_sync_polarity */
      			vsync-active = <1>;
      
      			// unused now
      			/*
      			de-active = <1>;
      			pixelclk-active = <1>;
      			syncclk-active = <0>;
      			interlaced;
      			doublescan;
      			doubleclk;
      			*/
      		};
      		ports {
      			#address-cells = <1>;
      			#size-cells = <0>;
      			panel_in: port@0 {
      				#address-cells = <1>;
      				#size-cells = <0>;
      				reg = <0>;
      				edp_panel_in: endpoint@0 {
      					reg = <0>;
      					remote-endpoint = <&edp_panel_out>;
      				};
      			};
      		};
      	};
      

      和 drm_edp 的配置

      &drm_edp {
      	status = "okay";
      
      	edp_ssc_en = <0>;
      	edp_ssc_mode = <0>;
      	edp_psr_support = <0>;
      	edp_colordepth = <8>; /* 6/8/10/12/16 */
      	edp_color_fmt = <0>; /* 0:RGB  1: YUV444  2: YUV422 */
      
      	lane1_sw = <0>;
      	lane1_pre = <0>;
      	lane2_sw = <0>;
      	lane2_pre = <0>;
      	lane3_sw = <0>;
      	lane3_pre = <0>;
      	efficient_training = <0>;
      
      	sink_capacity_prefer = <1>;
      	edid_timings_prefer = <1>;
      	timings_fixed = <1>;
      
      	vcc-edp-supply = <&reg_bldo3>;
      	vdd-edp-supply = <&reg_dcdc2>;
      	panel = <&edp_panel>;
      	ports {
      		edp_out: port@1 {
      			edp_panel_out: endpoint@0 {
      				reg = <0>;
      				remote-endpoint = <&edp_panel_in>;
      			};
      		};
      	};
      };
      发布在 T Series
      A
      awwwwa
    • 回复: T113-S3TF卡启动稳定

      @zm12138 在 T113-S3TF卡启动稳定 中说:

      [00.593]sunxi flash init ok

      MMC已经正常启动了,内核没有输出可以先检查uart配置是否正确

      发布在 MR Series
      A
      awwwwa
    • 回复: V853使用MIPI CSI接口是否只支持RAW格式像素?

      @xjy_5 这个不太清楚了,没有调试过这款芯片。我这边是T507+TC358743实现的

      发布在 V Series
      A
      awwwwa
    • 回复: PhoenixSuit

      https://www.aw-ol.com/downloads?cat=5

      78327439-2d58-4851-a15b-99b299fcfc92-image.png

      发布在 编译和烧写问题专区
      A
      awwwwa
    • 把 D1-H T113 的 LVGL 8.1.0 升级到 8.3.2 并适配 G2D 加速

      打入以下补丁即可

      cd package
      git apply *.patch
      

      lvgl8-update-version-from-8.1.0-to-8.3.2.zip

      发布在 MR Series
      A
      awwwwa
    • 回复: V853使用MIPI CSI接口是否只支持RAW格式像素?

      @xjy_5 一般来说配置sensor0_isp_used = <0>; 就不会调用ISP,虽然会配置但是不会处理。需要再跟踪一下调用

      发布在 V Series
      A
      awwwwa
    • 回复: V853使用MIPI CSI接口是否只支持RAW格式像素?

      @awwwwa

      sensor0:sensor@0 {                                      
            device_type = "sensor0";                        
            sensor0_mname = "gc2053_mipi";      /* 必须要和驱动的 SENSOR_NAME 一致 */   
            sensor0_twi_cci_id = <1>;           /* 所使用的twi id号,本例中使用的是twi1,故填写为1 */               
            sensor0_twi_addr = <0x6e>;          /* sensor 设备ID地址,必须与驱动中的I2C_ADDR一致 */                           
            sensor0_mclk_id = <0>;              /* 所使用的mclk id号,本例中使用的是MCLK0,故填写为0 */                        
            sensor0_pos = "rear";                           
            sensor0_isp_used = <1>;             /* 所使用的sensor为raw sensor,需要过ISP处理,故填写为1 */                      
            sensor0_fmt = <1>;                  /* sensor输出的图像格式,YUV:0,RAW:1 */            
            sensor0_stby_mode = <0>;                        
            sensor0_vflip = <0>;                /* VIPP 图像垂直翻转 */                
            sensor0_hflip = <0>;                /* VIPP 图像水平翻转 */                  
            sensor0_iovdd-supply = <&reg_aldo2>;/* sensor iovdd 连接的 ldo,根据硬件原理图的连接来决定(在硬件原理图中搜索aldo,然后找到CSI-iovdd对应的										   是哪一个aldo即可) */
            sensor0_iovdd_vol = <1800000>;	  /* iovdd的电压 */
            sensor0_avdd-supply = <&reg_bldo2>; /* sensor avdd连接的 ldo,根据硬件原理图的连接来决定 */
            sensor0_avdd_vol = <2800000>;		  /* 同上 */
            sensor0_dvdd-supply = <&reg_dldo2>;  /* 同上 */
            sensor0_dvdd_vol = <1200000>;        /* 同上 */                
            sensor0_power_en = <>;          										
            sensor0_reset = <&pio PA 11 1 0 1 0>; /* GPIO 信息配置:pio 端口 组内序号 功能分配 内部电阻状态 驱动能力 输出电平状态,本例中使用的是PA11*/   
            sensor0_pwdn = <&pio PA 9 1 0 1 0>;   /* GPIO 信息配置:pio 端口 组内序号 功能分配 内部电阻状态 驱动能力 输出电平状态,本例中使用的是PA9*/   
            flash_handle = <&flash0>;                       
            act_handle = <&actuator0>;                      
            status  = "okay";                               
      };       
      

      填写Sensor输出图像格式

      ​ sensor输出图像格式定义在sensor_format_struct结构体中,vin v4l2驱动框架通过获取sensor_format_struct结构体成员信息来获取当前sensor输出图像格式,sensor_formats结构体中需要填写的成员是.desc和 .mbus_code。

      ​ .desc是描述sensor输出的图像格式,本例中gc2053是RGB Raw sensor,故.desc成员填写为"Raw RGB Bayer" 。.mbus_code 为sensor图像数据输出顺序,sensor RAW图像是以Bayer格式传输的(每个像素只表示RGB其中一个分量),常见的Bayer格式为:RGGB、BGGR、GRBG、GBRG,这个可以询问一下sensor原厂或者翻阅sensor datasheet进行查找。.mbus_code 若填错, 会导致色彩偏紫红和出现网格状纹理。

      ​ 本例中gc2053图像输出格式为RGGB,且当前的配置是10bit mipi接口,故.mbus_code填写为
      MEDIA_BUS_FMT_SRGGB10_1X10,若当前调试的sensor配置是8bit输出,
      则.mbus_code填写为MEDIA_BUS_FMT_SRGGB8_1X8,按照这种规则进行填写。

      static struct sensor_format_struct sensor_formats[] = {
          {
              .desc      = "Raw RGB Bayer", 
              /* 填写 Sensor 初始化时默认的 Bayer 格式,目的是告知主控端ISP当前图像的 Bayer 格式,ISP需要以同样的格式来接收和处理图像数据 */
              .mbus_code = MEDIA_BUS_FMT_SRGGB10_1X10,
              .regs      = sensor_fmt_raw,		
              .regs_size = ARRAY_SIZE(sensor_fmt_raw),		
              .bpp       = 1
          },
      };
      

      ​ 如果sensor输出图像格式是YUV的话,则需要根据sensor图像数据输出顺序选择YUYV/VYUY/UYVY/YVYU 其中一种,如下:

      static struct sensor_format_struct sensor_formats[] = {
      	{
      		.desc = "YUYV 4:2:2",
      		.mbus_code = MEDIA_BUS_FMT_YUYV8_2X8,
      		.regs = sensor_fmt_raw,
      		.regs_size = ARRAY_SIZE(sensor_fmt_raw),
      		.bpp = 2,
      	},
      };
      

      ​ 同时,sensor_get_fmt_mbus_core函数也要将当前sensor的图像输出格式赋值给函数参数*code,有些sensor在翻转后RGB顺序不会自动进行调整,需要主控端ISP需要按照当前sensor翻转后的图像格式更新RGB顺序,避免翻转后出现图像色彩异常的问题,如下,gc2053支持翻转后sensor内部自动调整RGB顺序,所以函数参数*code仍赋值为MEDIA_BUS_FMT_SRGGB10_1X10。

      static int sensor_get_fmt_mbus_core(struct v4l2_subdev *sd, int *code)
      {
      	*code = MEDIA_BUS_FMT_SRGGB10_1X10; // gc2053 support change the rgb format by itself
      }
      
      static long sensor_ioctl(struct v4l2_subdev *sd, unsigned int cmd, void *arg)
      {
          int ret = 0;
          struct sensor_info *info = to_state(sd);
      	switch (cmd) { 
              case VIDIOC_VIN_GET_SENSOR_CODE:    /* vin v4l2框架层在sensor翻转接口被调用后,
              								    通过VIDIOC_VIN_GET_SENSOR_CODE获取当前sensor的RGB顺序 */
                  sensor_get_fmt_mbus_core(sd, (int *)arg);  
                  break;
              default:
                  return -EINVAL;
      	}
      	return ret;
      }
      
      发布在 V Series
      A
      awwwwa
    • 回复: V853使用MIPI CSI接口是否只支持RAW格式像素?

      @xjy_5 驱动都不用ISP,ISP是上层用户程序定义的,可以用camerademo抓图测试绕过ISP

      发布在 V Series
      A
      awwwwa
    • 回复: V851S SPI2 死机

      对照手册:

      • SPI2 地址 0x04027000, 没问题
        0f2f1b97-2298-4112-923a-c25db5428943-image.png

      • SPI2 中断号 49,配置时需要减掉SIG和PPI的数量32,也就是17
        eeb6838d-b14f-441f-870b-badb6672796a-lQLPJxe-6SonLpDM2s0B87B4X1hs1FJTtAUq12ehL88A_499_218.png

      中断号配置错误,应该为17不是18

      		spi2: spi@04027000 {
      			#address-cells = <1>;
      			#size-cells = <0>;
      			compatible = "allwinner,sun8i-spi";
      			device_type = "spi2";
      			reg = <0x0 0x04027000 0x0 0x1000>;
      			interrupts = <GIC_SPI 17 IRQ_TYPE_LEVEL_HIGH>;
      			clocks = <&clk_pll_periph0300m>, <&clk_spi2>;
      			status = "disabled";
      		};
      
      发布在 V Series
      A
      awwwwa
    • 回复: V853使用MIPI CSI接口是否只支持RAW格式像素?

      重新确认了一下,MIPI 接受的数据格式与MIPI无关,也就是MIPI也可以接收YUV这类数据。

      是否是因为后端配置的问题。参考T507的TC358743驱动配置的是MEDIA_BUS_FMT_UYVY8_2X8

      发布在 V Series
      A
      awwwwa
    • 回复: V853使用MIPI CSI接口是否只支持RAW格式像素?

      @xjy_5 RGB888_1X24 我感觉是直出RGB信号的吧

      这个DTSI是在T507上配置的,可以参考一下

      		vind0:vind@0 {
      			compatible = "allwinner,sunxi-vin-media", "simple-bus";
      			#address-cells = <2>;
      			#size-cells = <2>;
      			ranges;
      			device_id = <0>;
      			vind0_clk = <384000000>;
      			reg = <0x0 0x06600800 0x0 0x200>,
      				<0x0 0x06600000 0x0 0x800>;
      			clocks = <&clk_csi_top>, <&clk_pll_csi>,
      				 <&clk_csi_master0>, <&clk_hosc>, <&clk_pll_csi>,
      				 <&clk_csi_master1>, <&clk_hosc>, <&clk_pll_csi>;
      			pinctrl-names = "mclk0-default","mclk0-sleep","mclk1-default","mclk1-sleep";
      			pinctrl-0 = <&csi_mclk0_pins_a>;
      			pinctrl-1 = <&csi_mclk0_pins_b>;
      			pinctrl-2 = <&csi_mclk1_pins_a>;
      			pinctrl-3 = <&csi_mclk1_pins_b>;
      			status = "okay";
      
      
      			csi_cci0:cci@0 {
      				compatible = "allwinner,sunxi-csi_cci";
      				reg = <0x0 0x06614000 0x0 0x400>;
      				interrupts = <GIC_SPI 75 IRQ_TYPE_LEVEL_HIGH>;
      				pinctrl-names = "default","sleep";
      				pinctrl-0 = <&csi_cci0_pins_a>;
      				pinctrl-1 = <&csi_cci0_pins_b>;
      				device_id = <0>;
      				status = "okay";
      			};
      			csi_cci1:cci@1 {
      				compatible = "allwinner,sunxi-csi_cci";
      				reg = <0x0 0x06614400 0x0 0x400>;
      				interrupts = <GIC_SPI 76 IRQ_TYPE_LEVEL_HIGH>;
      				pinctrl-names = "default","sleep";
      				pinctrl-0 = <&csi_cci1_pins_a>;
      				pinctrl-1 = <&csi_cci1_pins_b>;
      				device_id = <1>;
      				status = "okay";
      			};
      			csi0:csi@0 {
      				device_type = "csi0";
      				compatible = "allwinner,sunxi-csi";
      				reg = <0x0 0x06601000 0x0 0x1000>;
      				interrupts = <GIC_SPI 73 IRQ_TYPE_LEVEL_HIGH>;
      				device_id = <0>;
      				iommus = <&mmu_aw 4 1>;
      				status = "okay";
      			};
      			csi1:csi@1 {
      				device_type = "csi1";
      				compatible = "allwinner,sunxi-csi";
      				reg = <0x0 0x06602000 0x0 0x1000>;
      				interrupts = <GIC_SPI 74 IRQ_TYPE_LEVEL_HIGH>;
      				pinctrl-names = "default","sleep";
      				pinctrl-0 = <&csi1_pins_a>;
      				pinctrl-1 = <&csi1_pins_b>;
      				device_id = <1>;
      				iommus = <&mmu_aw 4 1>;
      				status = "okay";
      			};
      			mipi0:mipi@0 {
      				compatible = "allwinner,sunxi-mipi";
      				reg = <0x0 0x0660C000 0x0 0x1000>;
      				interrupts = <GIC_SPI 77 IRQ_TYPE_LEVEL_HIGH>;
      				device_id = <0>;
      				status = "okay";
      			};
      			isp0:isp@0 {
      				compatible = "allwinner,sunxi-isp";
      				device_id = <0>;
      				status = "okay";
      			};
      			isp1:isp@1 {
      				compatible = "allwinner,sunxi-isp";
      				device_id = <1>;
      				status = "okay";
      			};
      			scaler0:scaler@0 {
      				compatible = "allwinner,sunxi-scaler";
      				device_id = <0>;
      				iommus = <&mmu_aw 4 1>;
      				status = "okay";
      			};
      			scaler1:scaler@1 {
      				compatible = "allwinner,sunxi-scaler";
      				device_id = <1>;
      				iommus = <&mmu_aw 4 1>;
      				status = "okay";
      			};
      			scaler2:scaler@2 {
      				compatible = "allwinner,sunxi-scaler";
      				device_id = <2>;
      				iommus = <&mmu_aw 4 1>;
      				status = "okay";
      			};
      			scaler3:scaler@3 {
      				compatible = "allwinner,sunxi-scaler";
      				device_id = <3>;
      				iommus = <&mmu_aw 4 1>;
      				status = "okay";
      			};
      			scaler4:scaler@4 {
      				compatible = "allwinner,sunxi-scaler";
      				device_id = <4>;
      				iommus = <&mmu_aw 4 1>;
      				status = "okay";
      			};
      			scaler5:scaler@5 {
      				compatible = "allwinner,sunxi-scaler";
      				device_id = <5>;
      				iommus = <&mmu_aw 4 1>;
      				status = "okay";
      			};
      			actuator0:actuator@0 {
      				device_type = "actuator0";
      				compatible = "allwinner,sunxi-actuator";
      				actuator0_name = "ad5820_act";
      				actuator0_slave = <0x18>;
      				actuator0_af_pwdn = <>;
      				actuator0_afvdd = "afvcc-csi";
      				actuator0_afvdd_vol = <2800000>;
      				status = "disabled";
      			};
      			flash0:flash@0 {
      				device_type = "flash0";
      				compatible = "allwinner,sunxi-flash";
      				flash0_type = <2>;
      				flash0_en = <>;
      				flash0_mode = <>;
      				flash0_flvdd = "";
      				flash0_flvdd_vol = <>;
      				device_id = <0>;
      				status = "disabled";
      			};
      			sensor0:sensor@0 {
      				device_type = "sensor0";
      				compatible = "allwinner,sunxi-sensor";
      				sensor0_mname = "tc358743_mipi";
      				sensor0_twi_cci_id = <2>;
      				sensor0_twi_addr = <0x1f>;
      				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_cameravdd-supply = <>;
      				sensor0_cameravdd_vol = <2800000>;
      				sensor0_iovdd-supply = <&reg_cldo4>;
      				sensor0_iovdd_vol = <1800000>;
      				sensor0_avdd-supply = <>;
      				sensor0_avdd_vol = <>;
      				sensor0_dvdd-supply = <>;
      				sensor0_dvdd_vol = <>;
      				sensor0_power_en = <>;
      				sensor0_reset = <&pio PI 8 1 0 1 0>;
      				sensor0_pwdn = <>;
      				sensor0_sm_vs = <>;
      				flash_handle = <&flash0>;
      				act_handle = <&actuator0>;
      				device_id = <0>;
      				status	= "okay";
      			};
      			sensor1:sensor@1 {
      				device_type = "sensor1";
      				compatible = "allwinner,sunxi-sensor";
      				sensor1_mname = "ov5647";
      				sensor1_twi_cci_id = <1>;
      				sensor1_twi_addr = <0x6c>;
      				sensor1_mclk_id = <1>;
      				sensor1_pos = "front";
      				sensor1_isp_used = <0>;
      				sensor1_fmt = <0>;
      				sensor1_stby_mode = <0>;
      				sensor1_vflip = <0>;
      				sensor1_hflip = <0>;
      				sensor1_cameravdd-supply = <>;
      				sensor1_cameravdd_vol = <2800000>;
      				sensor1_iovdd-supply = <>;
      				sensor1_iovdd_vol = <2800000>;
      				sensor1_avdd-supply = <>;
      				sensor1_avdd_vol = <2800000>;
      				sensor1_dvdd-supply = <>;
      				sensor1_dvdd_vol = <1500000>;
      				sensor1_power_en = <>;
      				sensor1_reset = <&pio PE 14 1 0 1 0>;
      				sensor1_pwdn = <&pio PE 15 1 0 1 0>;
      				sensor1_sm_vs = <>;
      				flash_handle = <>;
      				act_handle = <>;
      				device_id = <1>;
      				status	= "disable";
      			};
      			vinc0:vinc@0 {
      				device_type = "vinc0";
      				compatible = "allwinner,sunxi-vin-core";
      				reg = <0x0 0x06609000 0x0 0x200>;
      				interrupts = <GIC_SPI 69 IRQ_TYPE_LEVEL_HIGH>;
      				vinc0_csi_sel = <0>;
      				vinc0_mipi_sel = <0>;
      				vinc0_isp_sel = <0>;
      				vinc0_isp_tx_ch = <0>;
      				vinc0_rear_sensor_sel = <0>;
      				vinc0_front_sensor_sel = <0>;
      				vinc0_sensor_list = <0>;
      				device_id = <0>;
      				iommus = <&mmu_aw 4 1>;
      				status = "okay";
      			};
      			vinc1:vinc@1 {
      				device_type = "vinc1";
      				compatible = "allwinner,sunxi-vin-core";
      				reg = <0x0 0x06609200 0x0 0x200>;
      				interrupts = <GIC_SPI 70 IRQ_TYPE_LEVEL_HIGH>;
      				vinc1_csi_sel = <0>;
      				vinc1_mipi_sel = <0>;
      				vinc1_isp_sel = <0>;
      				vinc1_isp_tx_ch = <0>;
      				vinc1_rear_sensor_sel = <0>;
      				vinc1_front_sensor_sel = <0>;
      				vinc1_sensor_list = <0>;
      				device_id = <1>;
      				iommus = <&mmu_aw 4 1>;
      				status = "okay";
      			};
      			vinc2:vinc@2 {
      				device_type = "vinc2";
      				compatible = "allwinner,sunxi-vin-core";
      				reg = <0x0 0x06609400 0x0 0x200>;
      				interrupts = <GIC_SPI 71 IRQ_TYPE_LEVEL_HIGH>;
      				vinc2_csi_sel = <0>;
      				vinc2_mipi_sel = <0>;
      				vinc2_isp_sel = <0>;
      				vinc2_isp_tx_ch = <0>;
      				vinc2_rear_sensor_sel = <0>;
      				vinc2_front_sensor_sel = <0>;
      				vinc2_sensor_list = <0>;
      				device_id = <2>;
      				iommus = <&mmu_aw 4 1>;
      				status = "disabled";
      			};
      			vinc3:vinc@3 {
      				device_type = "vinc3";
      				compatible = "allwinner,sunxi-vin-core";
      				reg = <0x0 0x06609600 0x0 0x200>;
      				interrupts = <GIC_SPI 72 IRQ_TYPE_LEVEL_HIGH>;
      				vinc3_csi_sel = <0>;
      				vinc3_mipi_sel = <0>;
      				vinc3_isp_sel = <0>;
      				vinc3_isp_tx_ch = <0>;
      				vinc3_rear_sensor_sel = <0>;
      				vinc3_front_sensor_sel = <0>;
      				vinc3_sensor_list = <0>;
      				device_id = <3>;
      				iommus = <&mmu_aw 4 1>;
      				status = "disabled";
      			};
      			vinc4:vinc@4 {
      				device_type = "vinc4";
      				compatible = "allwinner,sunxi-vin-core";
      				reg = <0x0 0x06609800 0x0 0x200>;
      				interrupts = <GIC_SPI 79 IRQ_TYPE_LEVEL_HIGH>;
      				vinc4_csi_sel = <1>;
      				vinc4_mipi_sel = <0xff>;
      				vinc4_isp_sel = <1>;
      				vinc4_isp_tx_ch = <0>;
      				vinc4_rear_sensor_sel = <1>;
      				vinc4_front_sensor_sel = <1>;
      				vinc4_sensor_list = <0>;
      				device_id = <4>;
      				iommus = <&mmu_aw 5 1>;
      				status = "disabled";
      			};
      			vinc5:vinc@5 {
      				device_type = "vinc5";
      				compatible = "allwinner,sunxi-vin-core";
      				reg = <0x0 0x06609A00 0x0 0x200>;
      				interrupts = <GIC_SPI 80 IRQ_TYPE_LEVEL_HIGH>;
      				vinc5_csi_sel = <1>;
      				vinc5_mipi_sel = <0xff>;
      				vinc5_isp_sel = <1>;
      				vinc5_isp_tx_ch = <0>;
      				vinc5_rear_sensor_sel = <1>;
      				vinc5_front_sensor_sel = <1>;
      				vinc5_sensor_list = <0>;
      				device_id = <5>;
      				iommus = <&mmu_aw 5 1>;
      				status = "disabled";
      			};
      		};
      
      发布在 V Series
      A
      awwwwa
    • 回复: 【资料】V853 硬件设计指南

      【资料汇总】V853资料汇总
      https://bbs.aw-ol.com/topic/1560/share/1

      发布在 V Series
      A
      awwwwa
    • 回复: 【资料汇总】V853资料汇总

      在线文档:https://v853.docs.aw-ol.com/

      发布在 V Series
      A
      awwwwa
    • 回复: V853使用MIPI CSI接口是否只支持RAW格式像素?

      @xjy_5 MIPI CSI接收的是RAW数据,不支持YUV这样的

      发布在 V Series
      A
      awwwwa
    • 回复: t113i执行./build.sh编译出现很多[Y/N]的选项

      kernel有修改,或者kernel配置文件错误

      发布在 创龙科技专区
      A
      awwwwa
    • 回复: SDK文件夹移动位置后编译出来的img 烧录到板子上,报硬件检查错误,怎么回事?

      @hy123456 移动位置后需要删除out文件夹,因为SDK生成的设备的认证信息变化了但是由于SDK移动没有重新生成新的认证

      发布在 编译和烧写问题专区
      A
      awwwwa
    • 回复: V853 DDR原理图问题

      AW平台的DRAM控制器支持地址线REMAP,可以通过REMAP简化外部不同种类的DRAM的连接。

      这个REAMP是固定在芯片里的不能自己修改,在电路原理图可以看到REMAP的引脚。

      如图,如果需要挂DDR3内存,需要接DDR3的REAMP,如果需要接DDR2,可以接默认的REMAP

      07d2327d-bde1-4367-97e2-5b4b770b35e7-image.png

      举个其他平台的例子:
      这里接的是 LPDDR4,使用LPDDR4的REMAP
      84281c99-eb73-4892-b50d-bf3132389541-image.png

      这里接的是DDR4,使用DDR4的REMAP
      b14dfa2e-9a5f-4ba1-98bb-8f7d8541fc3b-image.png

      发布在 V Series
      A
      awwwwa
    • 回复: 請問大大誰有usb驅動程式能下載?

      @abc16883
      下载工具:
      AllwinnertechPhoeniSuitRelease20230905.zip

      下载驱动:
      全志USB烧录驱动20201229

      发布在 爱搞机专区
      A
      awwwwa
    • 回复: DshanMCU-R128s2-EVT 最全最强最丰富的企业评估套件来啦!!!
      • 测试固件
        rtos_freertos_r128s2_evt_uart0_16Mnor.img
      发布在 A Series
      A
      awwwwa
    • 回复: 搞不定R128的ST7789驱动

      jlt35031c.h
      jlt35031c.c

      发布在 A Series
      A
      awwwwa
    • 回复: Waiting for root device /dev/mmcblk0p0 后面就不动了

      @yxfzz mmc引导到了mmcblk0boot0,rootfs挂载不上

      发布在 Linux
      A
      awwwwa
    • 回复: 摄像头无法获取图像

      @lynnl4

      Out of memory 没有内存了,camerademo走的拍摄路径是v4l2不是mpp的vipp路径,需要的内存较大,可以尝试拍摄小分辨率的图片测试

      @lynnl4 在 摄像头无法获取图像 中说:

      [CAMERA] Resolution size : 1920 * 1088

      发布在 V Series
      A
      awwwwa
    • 回复: 想给R128移植上LVGL按照教程结果失败
      1. 出现重复定义,请问是不是同时勾选了 lv_examples 和 lv_g2d_test
      2. 分区表配置的空间过小,FAQ有解决方法:https://r128.docs.aw-ol.com/others/faq/
      发布在 A Series
      A
      awwwwa
    • 回复: R128 FreeRTOS编译提示/bin/bash: /usr/bin/python: 没有那个文件或目录

      请按照文档操作:
      7601324e-9aa3-4541-9b82-e19ed317a19b-image.png

      https://r128.docs.aw-ol.com/r128/prepare_dev_env/

      发布在 A Series
      A
      awwwwa
    • 回复: T113输出日志,是不是片子坏了啊

      @huerli 在 T113输出日志,是不是片子坏了啊 中说:

      BUG: Bad page map in process S10mdev pte:40cdf59f pmd:41bb1835

      主线驱动缺陷导致mdev申请出现NULL pointer。可以尝试使用新内核

      发布在 其它全志芯片讨论区
      A
      awwwwa
    • 回复: T527烧写安全固件后无法启动

      烧写安全固件和rotpk.bin之后就再也无法烧录非安全固件了,似乎是KeystoreService未能正常启动

      发布在 T Series
      A
      awwwwa
    • 回复: 求高人指点! ISP通路测试 sample_vin_isp_test 报错

      @xjy_5 检查下twi的配置

      发布在 V Series
      A
      awwwwa
    • 回复: R128驱动SD卡失败
      1. SanDisk HIGH ENDURABCE 32G SDHC Pass
        2de030a1-3af1-4162-aafb-9e3c0cefccbe-lQDPJxJhkub77WzNC9DND8Cw_DFJWqmDlV4FGf0i2yQiAA_4032_3024.jpg

      b5eb9273-5fc2-42fe-a393-ab64460f5998-image.png

      1. SanDisk Ultra 128G SDXC Pass

      aa836015-5015-433a-8fcf-b110d8aad425-lQDPJxwUfonqhSzNC9DND8Cw3YpYNr7PIvMFGf2NzIsWAA_4032_3024.jpg

      4dfecef4-96bd-4882-bb00-c1e38a58a18d-image.png

      1. NOKIA 2.0G Fail

      e9978cf7-11d3-4d72-b080-4b485a4f1fee-lQDPJw0WbTybFQzNC9DND8Cw_sjdrS3On-0FGf3S3bqCAA_4032_3024.jpg

      94d4568f-c050-4084-b8a7-52878f884849-image.png

      1. Unknow SD 120M SDHC Pass

      99d79225-90fc-4963-a4e8-c53836447681-lQDPJwkbyvUvqgzNC9DND8CwTxXeh2GBmKoFGf4htgwzAA_4032_3024.jpg

      7cd8c7b5-6b89-4524-b807-68b8b6dcd0de-image.png

      1. Kingston 4G SDHC Pass

      25db9121-3b65-4523-baca-fb299910d539-lQDPJx5swtaqoEzNC9DND8Cwbnudxv-Wiy8FGf5w0ZbSAA_4032_3024.jpg

      f4ad8fe9-c401-40d8-be94-d12480cbe699-image.png

      1. Micro SD 512M SDHC Pass

      4ed933d1-0c6d-4ad3-ab43-f85ffbf93c81-lQDPJwp-fvN_I4zNC9DND8CwRPg_yovkkykFGf7TGPjhAA_4032_3024.jpg

      659a4b84-77e7-4399-9d19-2dd752ecc382-image.png

      1. ADATA Micro SD 2G SDHC Pass

      0dcd4a3d-9815-4922-8698-68bdb6f881f9-lQDPJxXl-VCwb0zNC9DND8CweJX-mL5KIgQFGf8rVdIHAA_4032_3024.jpg

      458ebc60-49d9-4945-aab5-8536422b9130-image.png

      1. Kioxia exceria 32G SDHC Pass

      13dc558f-b4f1-4fb6-8d6a-e937d83edca9-lQDPJyDgT8wOfwzNC9DND8CwlWZLh8H4PJUFGf-NqUscAA_4032_3024.jpg

      172dc9db-b060-4efa-808c-ae0fa95b87ff-image.png

      1. SanDisk Ultra 16GB SDHC Pass

      d5eafdb8-71d4-4d62-863a-c49cb41498c2-lQDPJwGl2naexszNC9DND8CwHiiibxpT2ssFGgCz44-bAA_4032_3024.jpg

      5ac99948-8a33-47c9-a08a-8ecf894ccc56-image.png

      发布在 A Series
      A
      awwwwa
    • 回复: R128驱动SD卡失败

      @biubiu 闪迪128G SDXC 和无标山寨卡 SDHC 都测试通过

      发布在 A Series
      A
      awwwwa
    • 回复: R128驱动SD卡失败

      @biubiu 试试换一张卡看看,可能是不支持这个卡的型号

      发布在 A Series
      A
      awwwwa
    • 回复: R128驱动SD卡失败
      [sdc0]
      card_ctrl       = 0
      card_high_speed = 0
      card_line       = 4
      sdc_d1          = port:PA27<2><1><3><default>
      sdc_d0          = port:PA26<2><1><3><default>
      sdc_clk         = port:PA29<2><1><3><default>
      sdc_cmd         = port:PA25<2><1><3><default>
      sdc_d3          = port:PA24<2><1><3><default>
      sdc_d2          = port:PA28<2><1><3><default>
      
      [sdc0det_para]
      sdc0_det        = port:PA23<0><1><3><1>
      

      适配 EVT 的测试镜像:
      be810818-4bc0-447f-8705-d5d70abd8813-rtos_freertos_r128s2_evt_uart0_16Mnor.img

      发布在 A Series
      A
      awwwwa
    • 回复: 新 SDK 平台下载 XR806 SDK

      @zhoudaxia3000 目前最新的是1.2.2

      发布在 Wireless & Analog Series
      A
      awwwwa
    • 回复: 按照R128文档教程操作为啥显示框架LCD_open_flow一直没调用?

      @abcdef menuconfig勾选驱动编译了吗

      发布在 MR Series
      A
      awwwwa
    • 回复: R128的屏幕颜色显示异常时怎么回事?

      jlt35031c是比较少见的小端屏,但是大部分的SPI屏都是大端屏,所以用jlt35031c时,需要修改sys_config.fex里面的配置项lcd_rgb_order为9.

      unsigned char color[4] = {0xff,0x0,0xff,0x0};

      这个数组决定颜色,颜色顺序是R(红) G(绿) B(蓝) A(亮度)。

      所以红色 + 蓝色,应该是紫色

      但是这里由于使用的是SPI接口驱动这个屏幕,并不支持lcd_rgb_order的参数配置。所以在屏幕初始化的时候通过写寄存器配置为对应的接口以支持LVGL的正确显示输出。但是测试命令可能会出现反色的情况。

      发布在 A Series
      A
      awwwwa
    • 回复: 烧录固件时报错 init dram fail

      固件适配板子吗?1.2V电压是DDR4的电压是不是烧录到LPDDR4的板子上了

      发布在 Linux
      A
      awwwwa
    • 回复: R128-S2 驱动 1024x600 RGB 显示屏 并运行 LVGL

      屏参改一下

      lcd_driver_name     = "default_lcd"
      lcd_backlight       = 150
      lcd_if              = 0
      lcd_x               = 1024
      lcd_y               = 600
      lcd_width           = 150
      lcd_height          = 94
      lcd_rb_swap         = 0
      lcd_dclk_freq       = 48
      lcd_pwm_used        = 1
      lcd_pwm_ch          = 7
      lcd_pwm_freq        = 500000
      lcd_pwm_pol         = 1
      lcd_hbp             = 160
      lcd_ht              = 1344
      lcd_hspw            = 20
      lcd_vbp             = 20
      lcd_vt              = 635
      lcd_vspw            = 3
      lcd_lvds_if         = 0
      lcd_lvds_colordepth = 1
      lcd_lvds_mode       = 0
      lcd_frm             = 0
      lcd_io_phase        = 0x0000
      lcd_gamma_en        = 0
      lcd_bright_curve_en = 0
      lcd_cmap_en         = 0
      
      发布在 A Series
      A
      awwwwa
    • 回复: Android13编译不过

      @masterlu 64G内存,本地磁盘500G

      发布在 编译和烧写问题专区
      A
      awwwwa
    • 回复: Android13编译不过

      @masterlu
      测试复现过程:
      出现错误

      6fe9beb8-bfec-4049-a140-c2a7570554b0-lQLPJwPZvYRS0EzM9c0GRrC4cenRP12kzwUGwWzH_DgA_1606_245.png

      重开终端清除编译环境和之前编译输出后重新编译正常

      ebfb30be-07e8-4ab3-b7d8-cfcd4be83444-image.png

      发布在 编译和烧写问题专区
      A
      awwwwa
    • 回复: Android13编译不过

      感觉是环境配置有问题
      试试:

      1. 重开一个终端
      2. 重新 source build/envsetup.sh
      3. 重新 ./longan/build.sh config
      4. ./longan/build.sh distclean
      5. make installclean
      6. lunch
      发布在 编译和烧写问题专区
      A
      awwwwa
    • 回复: 请教拉取sdk问题

      @huangyuhan 没有配置默认保存用户名密码,需要多次输入

      发布在 MR Series
      A
      awwwwa
    • 回复: 新 SDK 平台下载 D1-H/D1s SDK

      @zhouyuan369 删除文件夹内的.repo隐藏文件夹重新拉取

      发布在 MR Series
      A
      awwwwa
    • 回复: tina编译demo失败

      @sunxi source后 mkmpp,你的环境变量没有导入,不能直接make mk文件

      发布在 V Series
      A
      awwwwa
    • 回复: 新 SDK 平台下载 D1-H/D1s SDK

      @zhouyuan369 网盘要怎么接收后续更新呢,重新下载25G的压缩包吗?

      发布在 MR Series
      A
      awwwwa
    • 回复: 寻求tina的display 官方文档说明,感谢

      可以看 《Linux_Display_开发指南.pdf》 不过这个也没有设备树的配置描述,更多是源码描述

      发布在 V Series
      A
      awwwwa
    • R128-S2 驱动 1024x600 RGB 显示屏 并运行 LVGL

      由于屏幕较大首先精简系统内存,关闭DSP核心,并将 RV 核心移到 HSPSRAM 上提高带宽。配置 LV_COLOR_DEPTH 16 提高帧率降低内存占用

      patch 如下,增加了新方案r128-devkit-rgb:161ca91b-f759-4108-8bfc-85114394da0c-r128-devkit-rgb.tar.gz

      编译打包即可

      700ms启动 LVGL:

      发布在 A Series
      A
      awwwwa
    • 回复: 全志 DDR初始化 v3s

      @casdfxx 这个代码是u-boot提供的,具体问题可以访问 https://lists.denx.de/listinfo/u-boot 寻求帮助。

      裸机工程:https://github.com/xboot/xboot/tree/master/src/arch/arm32/mach-v3s

      发布在 其它全志芯片讨论区
      A
      awwwwa
    • 回复: 全志 DDR初始化 v3s

      @casdfxx 这不就是除法,启用编译器除法选项就行了

      发布在 其它全志芯片讨论区
      A
      awwwwa
    • 回复: 寻求tina的display 官方文档说明,感谢
      disp init configuration
      
      disp_mode             (0:screen0<screen0,fb0>)
      screenx_output_type   (0:none; 1:lcd; 2:tv; 3:hdmi;5:vdpo)
      screenx_output_mode   (used for hdmi output, 0:480i 1:576i 2:480p 3:576p 4:720p50)
                            (5:720p60 6:1080i50 7:1080i60 8:1080p24 9:1080p50 10:1080p60)
      screenx_output_format (for hdmi, 0:RGB 1:yuv444 2:yuv422 3:yuv420)
      screenx_output_bits   (for hdmi, 0:8bit 1:10bit 2:12bit 2:16bit)
      screenx_output_eotf   (for hdmi, 0:reserve 4:SDR 16:HDR10 18:HLG)
      screenx_output_cs     (for hdmi, 0:undefined  257:BT709 260:BT601  263:BT2020)
      screenx_output_dvi_hdmi (for hdmi, 0:undefined 1:dvi mode 2:hdmi mode)
      screen0_output_range   (for hdmi, 0:default 1:full 2:limited)
      screen0_output_scan    (for hdmi, 0:no data 1:overscan 2:underscan)
      screen0_output_aspect_ratio  (for hdmi, 8-same as original picture 9-4:3 10-16:9 11-14:9)
      fbx format            (4:RGB655 5:RGB565 6:RGB556 7:ARGB1555 8:RGBA5551 9:RGB888 10:ARGB8888 12:ARGB4444)
      fbx pixel sequence    (0:ARGB 1:BGRA 2:ABGR 3:RGBA)
      fb0_scaler_mode_enable(scaler mode enable, used FE)
      fbx_width,fbx_height  (framebuffer horizontal/vertical pixels, fix to output resolution while equal 0)
      lcdx_backlight        (lcd init backlight,the range:[0,256],default:197
      lcdx_yy               (lcd init screen bright/contrast/saturation/hue, value:0~100, default:50/50/57/50)
      lcd0_contrast         (LCD contrast, 0~100)
      lcd0_saturation       (LCD saturation, 0~100)
      lcd0_hue              (LCD hue, 0~100)
      framebuffer software rotation setting:
      disp_rotation_used:   (0:disable; 1:enable,you must set fbX_width to lcd_y,
      set fbX_height to lcd_x)
      degreeX:              (X:screen index; 0:0 degree; 1:90 degree; 3:270 degree)
      degreeX_Y:            (X:screen index; Y:layer index 0~15; 0:0 degree; 1:90 degree; 3:270 degree)
      devX_output_type : config output type in bootGUI framework in UBOOT-2018.
      				   (0:none; 1:lcd; 2:tv; 4:hdmi;)
      devX_output_mode : config output resolution(see include/video/sunxi_display2.h) of bootGUI framework in UBOOT-2018
      devX_screen_id   : config display index of bootGUI framework in UBOOT-2018
      devX_do_hpd      : whether do hpd detectation or not in UBOOT-2018
      chn_cfg_mode     : Hardware DE channel allocation config. 0:single display with 6
      				   channel, 1:dual display with 4 channel in main display and 2 channel in second
                         display, 2:dual display with 3 channel in main display and 3 channel in second
                         in display.
      
      发布在 V Series
      A
      awwwwa
    • 回复: 需要全志在线开发者论坛LV2等级以上用户才有权限拉取 SDK

      @quincy e2c5b2ed-64a3-472e-aef4-0b85617eb437-image.png

      发布在 Wireless & Analog Series
      A
      awwwwa
    • 回复: 求v853使用OpenCL对图片和视频编解码例子

      @sunxi 是独立的视频引擎编码,不使用CPU也不使用NPU

      发布在 V Series
      A
      awwwwa
    • 回复: 求v853使用OpenCL对图片和视频编解码例子

      @sunxi

      https://github.com/YuzukiHD/Yuzukilizard/tree/master/Software/sunxi-mpp/sample/sample_venc

      发布在 V Series
      A
      awwwwa
    • 回复: 求v853使用OpenCL对图片和视频编解码例子

      @sunxi 硬解码调用VE解码,不使用OpenCL

      发布在 V Series
      A
      awwwwa
    • 回复: 求v853使用OpenCL对图片和视频编解码例子

      @sunxi V853的NPU运行的是VIPLite驱动模式,不支持OpenCL。Unify驱动暂未支持

      发布在 V Series
      A
      awwwwa
    • 回复: 求高人指点! ISP通路测试 sample_vin_isp_test 报错

      @xjy_5 tc358743有现成的驱动,可以试一下

      tc358743_sunxi_vin.zip

      sensor0:sensor@0 {
      	device_type = "sensor0";
      	compatible = "allwinner,sunxi-sensor";
      	sensor0_mname = "tc358743_mipi";
      	sensor0_twi_cci_id = <2>;
      	sensor0_twi_addr = <0x1f>;
      	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_cameravdd-supply = <>;
      	sensor0_cameravdd_vol = <2800000>;
      	sensor0_iovdd-supply = <&reg_cldo4>;
      	sensor0_iovdd_vol = <1800000>;
      	sensor0_avdd-supply = <>;
      	sensor0_avdd_vol = <>;
      	sensor0_dvdd-supply = <>;
      	sensor0_dvdd_vol = <>;
      	sensor0_power_en = <>;
      	sensor0_reset = <&pio PI 8 1 0 1 0>;
      	sensor0_pwdn = <>;
      	sensor0_sm_vs = <>;
      	flash_handle = <&flash0>;
      	act_handle = <&actuator0>;
      	device_id = <0>;
      	status	= "okay";
      };
      

      sensor0_isp_used 配置了不使用 ISP

      sensor0_isp_used = <0>;
      
      发布在 V Series
      A
      awwwwa
    • 回复: 求助全志大佬,有没有XR806的windows环境下的开发指导手册

      @rookie 但是没有unix编译环境,另外cygwin如果之前没有用过坑比linux下还大

      发布在 Wireless & Analog Series
      A
      awwwwa
    • 回复: 求高人指点! ISP通路测试 sample_vin_isp_test 报错

      可以在设备树把isp关闭

      发布在 V Series
      A
      awwwwa
    • 回复: 求助全志大佬,有没有XR806的windows环境下的开发指导手册

      @rookie xr806不支持Windows下开发编译

      发布在 Wireless & Analog Series
      A
      awwwwa
    • 回复: v853能不能集成gps模块

      GPS模块一般通过UART通讯,4G模块走USB

      发布在 V Series
      A
      awwwwa
    • 回复: V851s VIP lite有无多模型的示例?
      创建模型
      vip_create_network(&network1);
      vip_prepare_network(network1);
      vip_create_network(&network2);
      vip_prepare_network(network2);
      设置模型输入输出
      // set network input/output buffer
      创建执行组
      vip_create_group(max, &group); // max = 2
      vip_add_network(group, network1);
      vip_add_network(group, network2);
      执行
      vip_run_group(group, max);
      获取输出结果
      销毁
      vip_finish_network(network1);
      vip_finish_network(network2);
      vip_destroy_buffer // 销毁input/output
      vip_destroy_group(group);
      
      发布在 V Series
      A
      awwwwa
    • 回复: UDSIK分区表的大小和实际系统挂载的大小不对应

      UDISK属性写错了

      发布在 Linux
      A
      awwwwa
    • 回复: V853显示屏无法直接显示图片

      @ddrddr 看一下图层的设置,是否有图层覆盖

      发布在 V Series
      A
      awwwwa
    • Tina Linux 使用 adb dump、修改设备的 rootfs

      adb 可用时可以直接读取 /dev/by-name/rootfs 将rootfs导出来

      adb pull /dev/by-name/rootfs rootfs.img
      

      也可以push到tmp文件夹然后dd写入

      adb push rootfs.img /tmp
      dd if=/tmp/rootfs.img of=/dev/by-name/rootfs
      
      发布在 MR Series
      A
      awwwwa
    • 回复: 为什么添加Gstreamer后会报这个错误

      @uccccc 在 为什么添加Gstreamer后会报这个错误 中说:

      @awwwwa 麻烦问一下这个应该怎麼添加,有没有相关的资料亚

      https://openwrt.org/docs/guide-developer/packages

      发布在 MR Series
      A
      awwwwa
    • 回复: t113-i开启CONFIG_CAN_SUN8I=y配置后编译报错

      内核配置去掉宏:CONFIG_STACKPROTECTOR和CONFIG_STACKPROTECTOR_STRONG。

      发布在 其它全志芯片讨论区
      A
      awwwwa
    • 回复: Ubuntu 22.04 Server SDK下载报错

      @fantasya git command failure

      没安装git

      发布在 MR Series
      A
      awwwwa
    • R128 打包出现 ERROR: update_mbr failed
      24993+0 records in
      24993+0 records out
      6398208 bytes (6.4 MB) copied, 0.0271082 s, 236 MB/s
      ERROR: dl file rtos_riscv.fex size too large
      ERROR: filename = rtos_riscv.fex
      ERROR: dl_file_size = 1579 sector
      ERROR: part_size = 1000 sector
      ERROR: update mbr file fail
      ERROR: update_mbr failed
      

      这是因为 rootfs.fex 太大了,分区容量设置过小。

      解决方法

      • 确定打包使用的分区表

      运行打包命令,找到打包使用发分区表。例如这里使用的是 sys_partition_xip.fex

      • 编辑分区表

      使用 cconfigs 命令进入目录,找到打包使用的分区表,编辑修改

      • 找到上面报错的行,修改 size 选项,单位是扇区。对于 NOR 方案请对齐。这里我们修改到 7000

      • 重新打包,正常通过

      发布在 A Series
      A
      awwwwa
    • 回复: 为什么添加Gstreamer后会报这个错误

      没有交叉编译,gstreamer没有配置交叉编译工具

      发布在 MR Series
      A
      awwwwa
    • 回复: losetup 无法设置循环设备:没有这样的文件或目录

      @xjy_5 kernel启用loop device了吗

      发布在 V Series
      A
      awwwwa
    • 回复: losetup 无法设置循环设备:没有这样的文件或目录

      单独勾选这个命令编译

      发布在 V Series
      A
      awwwwa
    • 回复: 使用ffmpeg网络推流,用usb摄像头能正常使用,用mipi摄像头同样的操作下返回找不到设备的错误,实际上我/dev/下是有videox生成的

      @vincent1 需要修改ffmpeg从vipp获取数据,或者使用mpp推流不使用ffmpeg

      发布在 V Series
      A
      awwwwa
    • 回复: 使用ffmpeg网络推流,用usb摄像头能正常使用,用mipi摄像头同样的操作下返回找不到设备的错误,实际上我/dev/下是有videox生成的

      mipi摄像头需要走vipp通路,video0只有一个很基础的v4l2设备,上层需要更多的处理,例如isp,3a等,usb走uvc直接对接v4l2提供全部功能

      发布在 V Series
      A
      awwwwa
    • 回复: R329 tina 启动卡死问题

      @kkkcxf 在 R329 tina 启动卡死问题 中说:

      Waiting for root device /dev/mmcblk0p4...

      rootfs配置问题,不是卡死了而是等待挂载ROOTFS

      发布在 A Series
      A
      awwwwa
    • 回复: Gaviar Handheld (小志掌機)

      @yofa2008 img不是磁盘镜像文件,是专有的压缩格式,不带分区表。可以用OpenixCard转换为dd可以写入的带分区表的镜像

      发布在 爱搞机专区
      A
      awwwwa
    • 回复: R329编译libAWIspApi错误是什么原因如何解决呢?

      R329不支持libAWIspApi,需要取消选择这个包

      发布在 编译和烧写问题专区
      A
      awwwwa
    • 回复: 新 SDK 平台下载 XR806 SDK

      @woxow 把你的proxy代理关了

      发布在 Wireless & Analog Series
      A
      awwwwa
    • 回复: OpenixCard - 在 Linux 系统刷写全志镜像到 SD 卡

      @uccccc
      你的分区有两个name,怎么能正确识别呢

      0560a17a-5a01-4717-b030-76e8f36485a3-image.png

      发布在 编译和烧写问题专区
      A
      awwwwa
    • 给 Gaviar Handheld (小志掌机) 适配了一个固件,魂斗罗游戏机

      先上固件:

      9724ff03-b4bc-4a07-8bac-05431383d983-gaviarhandhelda.img

      发布在 爱搞机专区
      A
      awwwwa
    • 回复: 100ask-t113pro lvds调试问题

      @bigfly colorbar正常吗

      发布在 其它全志芯片讨论区
      A
      awwwwa
    • Qt 驅動 RGB 565 顔色不對

      源碼如下:

      src.zip

      发布在 爱搞机专区
      A
      awwwwa
    • 回复: camerademo.c修改后编译打包的camerademo不变

      @mysteryli 可以到 out/v853/xxxx/openwrt/build_dir/target/camerademo/ipkg-install/usr

      发布在 V Series
      A
      awwwwa
    • 回复: 抓图报错[VIN_ERR]isp0 width error,求给个排查思路

      @xjy_5 在 抓图报错[VIN_ERR]isp0 width error,求给个排查思路 中说:

      首先,isp配置错误

      [VIN_ERR]isp0 configuration error

      isp fifo为空

      [VIN_ERR]isp0 internal fifo full

      isp 帧错误

      [VIN_ERR]isp0 frame lost!

      如果不需要使用isp,可以修改sample的源码删除isp处理部分,并且修改设备树禁用isp

      发布在 V Series
      A
      awwwwa
    • 回复: 请教T113S3串口2(PD1和PD2)和LCD引脚冲突

      @yelong98 mkernel 强制重新编译内核试试看

      发布在 MR Series
      A
      awwwwa
    • 回复: camerademo.c修改后编译打包的camerademo不变

      mmo camerademo -B

      发布在 V Series
      A
      awwwwa
    • 回复: T113-s3使用PhoenixSuit的一键刷机功能USB更新EMMC固件400M,一个小时刷成功一次正常吗?

      @liefyuan

      这里下载这个版本:https://www.aw-ol.com/downloads?cat=5

      20120ad6-47cb-463b-a8e2-9ebae6c9995f-image.png

      发布在 其它全志芯片讨论区
      A
      awwwwa
    • 回复: 有没有大佬知道这个f1c100s和stm32去通信,配置好烧到板子上串口走不下去了

      @gaowei15537316965 SPI驱动参考 Linux 编写spidev驱动即可

      发布在 Linux
      A
      awwwwa
    • 回复: 有没有大佬知道这个f1c100s和stm32去通信,配置好烧到板子上串口走不下去了

      F1C100s 与 STM32 通讯是需要通过外设接口,例如UART,SPI,IIC,SDIO来通讯,你看到的这个 DMA 控制器驱动是给STM32MP用的,不是给F1C100s用的

      发布在 Linux
      A
      awwwwa
    • 回复: 有没有大佬知道这个f1c100s和stm32去通信,配置好烧到板子上串口走不下去了

      为什么F1C100s的DMA控制器驱动需要使用 st,stm32-dma 而不是 allwinner,sunxi-dma

      发布在 Linux
      A
      awwwwa
    • 回复: 有没有大佬知道这个f1c100s和stm32去通信,配置好烧到板子上串口走不下去了

      Linux都没启动,先检查为什么Linux没启动

      发布在 Linux
      A
      awwwwa
    • 回复: v853板子做为usb device通过usb接入pc,有没推荐好的方案或者开源的库和案例来传输私有音视频.

      @sofia USB 2.0 的速率,大约为 34MByte/s

      发布在 V Series
      A
      awwwwa
    • 回复: T113-s3使用PhoenixSuit的一键刷机功能USB更新EMMC固件400M,一个小时刷成功一次正常吗?

      不正常,进行了如下实验:

      • 准备开发板:T113-S3 EVB1,eMMC 型号:FEMDRW008G-88A39

      1df73a75-f9b3-4ef0-b865-6f91d031ae3a-image.png

      • 1.1GByte 固件一份,

      eafb933d-5bc7-464f-847e-25afa53aaac3-image.png

      刷写时间,5分17秒:

      b436ed20-e3fe-4d70-bb18-c08d0072fc0e-image.png

      刷写 LOG 如下:

      [858]fes begin commit:fccdad5de4-dirty
      [861]set pll start
      [867]periph0 has been enabled
      [870]set pll end
      [872][pmu]: bus read error
      [874]board init ok
      [876]beign to init dram
      [878]ZQ value = 0x30
      [880]get_pmu_exist() = -1
      [883]ddr_efuse_type: 0xa
      [885]trefi:7.8ms
      [888][AUTO DEBUG] single rank and full DQ!
      [892]ddr_efuse_type: 0xa
      [894]trefi:7.8ms
      [896][AUTO DEBUG] rank 0 row = 13
      [899][AUTO DEBUG] rank 0 bank = 8
      [903][AUTO DEBUG] rank 0 page size = 2 KB
      [907]DRAM BOOT DRIVE INFO: V0.34
      [910]DRAM CLK = 792 MHz
      [912]DRAM Type = 3 (2:DDR2,3:DDR3)
      [915]DRAMC read ODT  off.
      [918]DRAM ODT value: 0x42.
      [920]ddr_efuse_type: 0xa
      [923]DRAM SIZE = 128 MB
      [927]DRAM simple test OK.
      [929]rtc standby flag is 0x0, super standby flag is 0x0
      [935]init dram ok
      
      
      U-Boot 2018.07-00006-g65ea3f1459 (Aug 31 2023 - 08:08:04 +0000) Allwinner Technology
      
      [03.646]CPU:   Allwinner Family
      [03.649]Model: sun8iw20
      [03.651]DRAM:  0 Bytes
      [03.654]Relocation Offset is: 04eaf000
      [03.683]secure enable bit: 0
      [03.690]CPU=1008 MHz,PLL6=600 Mhz,AHB=200 Mhz, APB1=100Mhz  MBus=300Mhz
      [03.697]gic: normal mode
      [03.700]sunxi flash map init
      SPI ALL:   ready
      [03.745]line:703 init_clocks
      [03.765]init_clocks:finish
      [03.767]flash init start
      [03.769]workmode = 16,storage type = 0
      try card 2
      set card number 2
      get card number 2
      [03.777][mmc]: mmc driver ver uboot2018:2023-07-4 16:18:00
      [03.823][mmc]: Is not Boot mode!
      [03.826][mmc]: SUNXI SDMMC Controller Version:0x50310
      [03.838][mmc]: ************Try SD card 2************
      [03.843][mmc]: mmc 2 cmd timeout 100 status 100
      [03.847][mmc]: smc 2 err, cmd 8,  RTO
      [03.851][mmc]: mmc 2 close bus gating and reset
      [03.856][mmc]: mmc 2 cmd timeout 100 status 100
      [03.860][mmc]: smc 2 err, cmd 55,  RTO
      [03.863][mmc]: mmc 2 close bus gating and reset
      [03.868][mmc]: ************Try MMC card 2************
      [03.890][mmc]: mmc 2 cmd timeout 100 status 100
      [03.894][mmc]: smc 2 err, cmd 8,  RTO
      [03.898][mmc]: mmc 2 close bus gating and reset
      [03.903][mmc]: mmc 2 cmd timeout 100 status 100
      [03.907][mmc]: smc 2 err, cmd 55,  RTO
      [03.910][mmc]: mmc 2 close bus gating and reset
      [03.927][mmc]: gen_tuning_blk_bus8: total blk 10
      [03.933][mmc]: gen_tuning_blk_bus4: total blk 6
      [03.938][mmc]: Using 4 bit tuning now
      [03.941][mmc]: write_tuning_try_freq: write ok
      [03.947][mmc]: Pattern compare ok
      [03.950][mmc]: Write tuning pattern ok
      [03.954][mmc]: ================== HSSDR52_SDR25...
      [03.958][mmc]: skip freq 400000
      [03.961][mmc]: skip freq 25000000
      [03.964][mmc]: freq: 2-50000000-64-4
      [05.493][mmc]: [0-63|64]
      [05.495][mmc]: ================== HSDDR52_DDR50...
      [05.499][mmc]: skip freq 400000
      [05.502][mmc]: freq: 1-25000000-64-4
      [06.658][mmc]: freq: 2-50000000-64-4
      [07.766][mmc]: [0-48|49]
      [07.768][mmc]: [0-48|49]
      [07.771][mmc]: DS26/SDR12: 0xffffffff 0xffffffff
      [07.775][mmc]: HSSDR52/SDR25: 0xff20ffff 0xffffffff
      [07.780][mmc]: HSDDR52/DDR50: 0xff1818ff 0xffffffff
      [07.784][mmc]: HS200/SDR104: 0xffffffff 0xffffffff
      [07.789][mmc]: HS400: 0xffffffff 0xffffffff
      [07.793][mmc]: HS400: 0xffffffff 0xffffffff
      [07.797][mmc]: Best spd md: 2-HSDDR52/DDR50, freq: 2-50000000, Bus width: 4
      [07.810]Loading Environment from SUNXI_FLASH... OK
      [07.821]try to burn key
      [07.826]out of usb burn from boot: not boot mode
      Hit any key to stop autoboot:  0
      sunxi work mode=0x10
      run usb efex
      delay time 2500
      weak:otg_phy_config
      usb init ok
      set address 0xf
      set address 0xf ok
      SUNXI_EFEX_ERASE_TAG
      erase_flag = 0x12
      origin_erase_flag = 0x1
      FEX_CMD_fes_verify_status
      FEX_CMD_fes_verify last err=0
      the 0 mbr table is ok
      the 1 mbr table is ok
      the 2 mbr table is ok
      the 3 mbr table is ok
      *************MBR DUMP***************
      total mbr part 8
      
      part[0] name      :boot-resource
      part[0] classname :DISK
      part[0] addrlo    :0x1f8
      part[0] lenlo     :0x1f8
      part[0] user_type :32768
      part[0] keydata   :0
      part[0] ro        :0
      
      part[1] name      :env
      part[1] classname :DISK
      part[1] addrlo    :0x3f0
      part[1] lenlo     :0x1f8
      part[1] user_type :32768
      part[1] keydata   :0
      part[1] ro        :0
      
      part[2] name      :env-redund
      part[2] classname :DISK
      part[2] addrlo    :0x5e8
      part[2] lenlo     :0x1f8
      part[2] user_type :32768
      part[2] keydata   :0
      part[2] ro        :0
      
      part[3] name      :boot
      part[3] classname :DISK
      part[3] addrlo    :0x7e0
      part[3] lenlo     :0x4ec0
      part[3] user_type :32768
      part[3] keydata   :0
      part[3] ro        :0
      
      part[4] name      :rootfs
      part[4] classname :DISK
      part[4] addrlo    :0x56a0
      part[4] lenlo     :0x2329a0
      part[4] user_type :32768
      part[4] keydata   :0
      part[4] ro        :0
      
      part[5] name      :private
      part[5] classname :DISK
      part[5] addrlo    :0x238040
      part[5] lenlo     :0x2760
      part[5] user_type :32768
      part[5] keydata   :0
      part[5] ro        :0
      
      part[6] name      :recovery
      part[6] classname :DISK
      part[6] addrlo    :0x23a7a0
      part[6] lenlo     :0x5a90
      part[6] user_type :32768
      part[6] keydata   :0
      part[6] ro        :0
      
      part[7] name      :UDISK
      part[7] classname :DISK
      part[7] addrlo    :0x240230
      part[7] lenlo     :0x0
      part[7] user_type :0
      part[7] keydata   :0
      part[7] ro        :0
      
      total part: 9
      mbr 0, 1f8, 8000
      boot-resource 1, 1f8, 8000
      env 2, 1f8, 8000
      env-redund 3, 1f8, 8000
      boot 4, 4ec0, 8000
      rootfs 5, 2329a0, 8000
      private 6, 2760, 8000
      recovery 7, 5a90, 8000
      UDISK 8, 0, 0
      [10.886]erase all part start
      need erase flash: 18
      [10.893][mmc]: erase from: 0, to: 15269887, cnt: 15269888, erase_group: 1024
      [10.971][mmc]: sunxi_mmc_do_send_cmd_common: cmd 38 wait rsp busy 0x46 ms
      [10.977]read item0 copy0
      [11.016]Item0 (Map) magic is bad
      [11.019]the secure storage item0 copy0 magic is bad
      [11.060]Item0 (Map) magic is bad
      [11.063]the secure storage item0 copy1 magic is bad
      [11.068]Item0 (Map) magic is bad
      [11.071]the secure storage map is empty
      [11.147]erase secure storage: 0 ok
      SUNXI_EFEX_MBR_TAG
      mbr size = 0x10000
      write primary GPT success
      write Backup GPT success
      [11.163]update partition map
      FEX_CMD_fes_verify_status
      FEX_CMD_fes_verify last err=0
      ******Has init
      FEX_CMD_fes_verify_value, start 0x1f8, size high 0x0:low 0x14000
      FEX_CMD_fes_verify_value 0xe6f75b5c
      FEX_CMD_fes_verify_value, start 0x3f0, size high 0x0:low 0x20000
      FEX_CMD_fes_verify_value 0xa367d787
      FEX_CMD_fes_verify_value, start 0x5e8, size high 0x0:low 0x20000
      FEX_CMD_fes_verify_value 0xa367d787
      FEX_CMD_fes_verify_value, start 0x7e0, size high 0x0:low 0x429800
      FEX_CMD_fes_verify_value 0x97662167
      FEX_CMD_fes_verify_value, start 0x56a0, size high 0x0:low 0x43460000
      FEX_CMD_fes_verify_value 0x3fee63cb
      bootfile_mode=4
      SUNXI_EFEX_BOOT1_TAG
      boot1 size = 0x15c000, max size = 0x200000
      uboot size = 0x15c000
      storage type = 2
      FEX_CMD_fes_verify_status
      FEX_CMD_fes_verify last err=0
      bootfile_mode=4
      SUNXI_EFEX_BOOT0_TAG
      boot0 size = 0xa000
      [327.990][mmc]: write mmc 2 info ok
      dram para[0] = 318
      dram para[1] = 3
      dram para[2] = 7b7bfb
      dram para[3] = 0
      dram para[4] = 10d2
      dram para[5] = 800000
      dram para[6] = 1c70
      dram para[7] = 42
      dram para[8] = 18
      dram para[9] = 0
      dram para[10] = 4a2195
      dram para[11] = 2423190
      dram para[12] = 8b061
      dram para[13] = b4787896
      dram para[14] = 0
      dram para[15] = 48484848
      dram para[16] = 48
      dram para[17] = 1620121e
      dram para[18] = 0
      dram para[19] = 0
      dram para[20] = 0
      dram para[21] = 340000
      dram para[22] = 46
      dram para[23] = b4006103
      dram para[24] = 0
      dram para[25] = 0
      dram para[26] = 0
      dram para[27] = 0
      dram para[28] = 0
      dram para[29] = 0
      dram para[30] = 0
      dram para[31] = 0
      storage type = 2
      FEX_CMD_fes_verify_status
      FEX_CMD_fes_verify last err=0
      sunxi_efex_next_action=2
      exit usb
      next work 2
      
      [28]HELLO! BOOT0 is starting!
      [30]BOOT0 commit : fccdad5de4-dirty
      [34]set pll start
      [40]periph0 has been enabled
      [43]set pll end
      [44][pmu]: bus read error
      [47]board init ok
      [49]enable_jtag
      [50]ZQ value = 0x2f
      [52]get_pmu_exist() = -1
      [54]DRAM BOOT DRIVE INFO: V0.34
      [57]DRAM CLK = 792 MHz
      [60]DRAM Type = 3 (2:DDR2,3:DDR3)
      [63]DRAMC read ODT  off.
      [65]DRAM ODT value: 0x42.
      [68]ddr_efuse_type: 0xa
      [71]DRAM SIZE = 128 MB
      [77]DRAM simple test OK.
      [79]rtc standby flag is 0x0, super standby flag is 0x0
      [85]dram size =128
      [87]card no is 2
      [89]sdcard 2 line count 4
      [91][mmc]: mmc driver ver 2021-05-21 14:47
      [100][mmc]: Wrong media type 0x0, but host sdc2, try mmc first
      [106][mmc]: ***Try MMC card 2***
      [130][mmc]: RMCA OK!
      [132][mmc]: mmc 2 bias 0
      [136][mmc]: MMC 5.1
      [138][mmc]: HSSDR52/SDR25 4 bit
      [141][mmc]: 50000000 Hz
      [143][mmc]: 7456 MB
      [145][mmc]: ***SD/MMC 2 init OK!!!***
      [243]Loading boot-pkg Succeed(index=0).
      [247]Entry_name        = u-boot
      [254]Entry_name        = optee
      [258]Entry_name        = dtb
      [261]tunning data addr:0x430003e8
      [264]Jump to second Boot.
      M/TC: OP-TEE version: 8b49ce62-dirty (gcc version 5.3.1 20160412 (Linaro GCC 5.3-2016.05)) #1 Fri Aug 12 08:24:15 UTC 2022 arm
      
      
      U-Boot 2018.07-00006-g65ea3f1459 (Aug 31 2023 - 08:08:04 +0000) Allwinner Technology
      
      [00.316]CPU:   Allwinner Family
      [00.319]Model: sun8iw20
      [00.321]DRAM:  128 MiB
      [00.325]Relocation Offset is: ffeaf000
      [00.354]secure enable bit: 0
      E/TC:0   fdt_getprop_u32:343 prop trace_level not found
      [00.367]CPU=1008 MHz,PLL6=600 Mhz,AHB=200 Mhz, APB1=100Mhz  MBus=300Mhz
      [00.374]gic: sec monitor mode
      SPI ALL:   ready
      [00.379]line:703 init_clocks
      [00.382]flash init start
      [00.384]workmode = 0,storage type = 2
      [00.387][mmc]: mmc driver ver uboot2018:2023-07-4 16:18:00
      [00.394][mmc]: SUNXI SDMMC Controller Version:0x50310
      [00.418][mmc]: Best spd md: 2-HSDDR52/DDR50, freq: 2-50000000, Bus width: 4
      [00.424]sunxi flash init ok
      [00.427]drv_disp_init
      partno erro : can't find partition bootloader
      ** Unable to read file lcd_compatible_index.txt **
      [00.447]disp_fat_load for lcd config failed
      [00.474]boot_hdmi20: [info] hdmi_init start
      [00.479]boot_hdmi20: [info] hdmi use aw phy!
      [00.483]boot_hdmi20: [info] hdmi_init finish
      [00.487]drv_disp_init finish
      [00.492]Loading Environment from SUNXI_FLASH... OK
      [00.505]boot_gui_init:start
      partno erro : can't find partition Reserve0
      bad fb1_cfg[w=0,h=0,bpp=32,format=0]
      [00.520]boot_gui_init:finish
      partno erro : can't find partition bootloader
      [00.527]bmp_name=bootlogo.bmp size 38454
      [00.536]Item0 (Map) magic is bad
      [00.539]the secure storage item0 copy0 magic is bad
      [00.547]Item0 (Map) magic is bad
      [00.549]the secure storage item0 copy1 magic is bad
      [00.554]Item0 (Map) magic is bad
      [00.557]usb burn from boot
      delay time 0
      weak:otg_phy_config
      [00.568]usb prepare ok
      [00.698]LCD open finish
      [00.775]usb sof ok
      [00.776]usb probe ok
      [00.778]usb setup ok
      set address 0x10
      set address 0x10 ok
      try to update
      [01.183]do_burn_from_boot usb : have no handshake
      List file under ULI/factory
      ** Unrecognized filesystem type **
      root_partition is rootfs
      set root to /dev/mmcblk0p5
      [01.199]update part info
      [01.202]update bootcmd
      [01.205]change working_fdt 0x40e6ee68 to 0x40e4ee68
      [01.210][mmc]: can't find node "sunxi-mmc2" try "mmc"
      [01.215][mmc]: no mmc-hs400-1_8v!
      [01.218][mmc]: delete mmc-hs200-1_8v from dtb
      [01.222][mmc]: get max-frequency ok 50000000 Hz
      [01.227][mmc]: get sunxi-mmc2 string failed
      [01.231]The storage not support sample function
      partno erro : can't find partition bootloader
      ** Unable to read file lcd_compatible_index.txt **
      [01.257]disp_fat_load for lcd config failed
      partno erro : can't find partition bootloader
      writing lcd_compatible_index.txt
      16 bytes written
      save lcd compatible disp0 index 0 to flash
      partno erro : can't find partition bootloader
      [01.281]update dts
      Hit any key to stop autoboot:  0
      input addr exceed dram scope
      [01.385]no vendor_boot partition is found
      Android's image name: sun8i_arm
      [01.480]Starting kernel ...
      
      [01.483][mmc]: mmc exit start
      [01.500][mmc]: mmc 2 exit ok
      [    0.000000] Booting Linux on physical CPU 0x0
      [    0.000000] Linux version 5.4.61 (kunyao@AwExdroid89) (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) #1 SMP PREEMPT Wed Sep 6 10:23:35 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
      [    0.000000] OF: fdt: Machine model: sun8iw20
      [    0.000000] Memory policy: Data cache writealloc
      [    0.000000] Reserved memory: created DMA memory pool at 0x42200000, size 0 MiB
      [    0.000000] OF: reserved mem: initialized node vdev0buffer@42200000, compatible id shared-dma-pool
      [    0.000000] Reserved memory: created DMA memory pool at 0x42244000, size 0 MiB
      [    0.000000] OF: reserved mem: initialized node dsp0_rpbuf@42244000, compatible id shared-dma-pool
      [    0.000000] cma: Reserved 4 MiB at 0x47c00000
      [    0.000000] On node 0 totalpages: 32420
      [    0.000000]   Normal zone: 256 pages used for memmap
      [    0.000000]   Normal zone: 0 pages reserved
      [    0.000000]   Normal zone: 32420 pages, LIFO batch:7
      [    0.000000] psci: probing for conduit method from DT.
      [    0.000000] psci: PSCIv1.0 detected in firmware.
      [    0.000000] psci: Using standard PSCI v0.2 function IDs
      [    0.000000] psci: MIGRATE_INFO_TYPE not supported.
      [    0.000000] psci: SMC Calling Convention v1.0
      [    0.000000] percpu: Embedded 15 pages/cpu s30784 r8192 d22464 u61440
      [    0.000000] pcpu-alloc: s30784 r8192 d22464 u61440 alloc=15*4096
      [    0.000000] pcpu-alloc: [0] 0 [0] 1
      [    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 32164
      [    0.000000] Kernel command line: earlyprintk=sunxi-uart,0x02500000 clk_ignore_unused initcall_debug=0 console=ttyS0,115200 loglevel=8 root=/dev/mmcblk0p5 init=/init rdinit=/rdinit partitions=boot-resource@mmcblk0p1:env@mmcblk0p2:env-redund@mmcblk0p3:boot@mmcblk0p4:rootfs@mmcblk0p5:private@mmcblk0p6:recovery@mmcblk0p7:UDISK@mmcblk0p8 cma=4M snum= mac_addr= wifi_mac= bt_mac= specialstr= gpt=1 androidboot.mode=normal androidboot.hardware=sun8iw20p1 boot_type=2 androidboot.boot_type=2 gpt=1 uboot_message=2018.07-00006-g65ea3f1459(08/31/2023-08:08:04) mbr_offset=1032192 disp_reserve=1536000,0x40efb000 androidboot.dramfreq=792 androidboot.dramsize=128 mtdparts=<NULL>
      [    0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes, linear)
      [    0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes, linear)
      [    0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
      [    0.000000] Memory: 103624K/129680K available (6144K kernel code, 303K rwdata, 2200K rodata, 1024K init, 1166K bss, 21960K reserved, 4096K cma-reserved)
      [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
      [    0.000000] rcu: Preemptible hierarchical RCU implementation.
      [    0.000000]  Tasks RCU enabled.
      [    0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
      [    0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
      [    0.000000] random: get_random_bytes called from start_kernel+0x25c/0x3dc with crng_init=0
      [    0.000000] arch_timer: cp15 timer(s) running at 24.00MHz (phys).
      [    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x588fe9dc0, max_idle_ns: 440795202592 ns
      [    0.000006] sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every 4398046511097ns
      [    0.000017] Switching to timer-based delay loop, resolution 41ns
      [    0.000190] clocksource: timer: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 79635851949 ns
      [    0.000836] Console: colour dummy device 80x30
      [    0.000875] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=240000)
      [    0.000887] pid_max: default: 32768 minimum: 301
      [    0.001015] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
      [    0.001027] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
      [    0.001620] CPU: Testing write buffer coherency: ok
      [    0.001944] /cpus/cpu@0 missing clock-frequency property
      [    0.001963] /cpus/cpu@1 missing clock-frequency property
      [    0.001974] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
      [    0.002490] Setting up static identity map for 0x40100000 - 0x40100060
      [    0.002593] rcu: Hierarchical SRCU implementation.
      [    0.003017] smp: Bringing up secondary CPUs ...
      [    0.004175] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
      [    0.004303] smp: Brought up 1 node, 2 CPUs
      [    0.004317] SMP: Total of 2 processors activated (96.00 BogoMIPS).
      [    0.004323] CPU: All CPU(s) started in SVC mode.
      [    0.004775] devtmpfs: initialized
      [    0.016429] VFP support v0.3: implementor 41 architecture 2 part 30 variant 7 rev 5
      [    0.017002] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
      [    0.017028] futex hash table entries: 512 (order: 3, 32768 bytes, linear)
      [    0.017372] pinctrl core: initialized pinctrl subsystem
      [    0.018649] NET: Registered protocol family 16
      [    0.020217] DMA: preallocated 256 KiB pool for atomic coherent allocations
      [    0.058181] rtc_ccu: sunxi ccu init OK
      [    0.060672] ccu: sunxi ccu init OK
      [    0.061209] r_ccu: sunxi ccu init OK
      [    0.092454] sun6i-dma 3002000.dma-controller: sunxi dma probed
      [    0.097123] iommu: Default domain type: Translated
      [    0.097336] sunxi iommu: irq = 24
      [    0.098409] SCSI subsystem initialized
      [    0.098800] usbcore: registered new interface driver usbfs
      [    0.098879] usbcore: registered new interface driver hub
      [    0.098996] usbcore: registered new device driver usb
      [    0.099231] videodev: Linux video capture interface: v2.00
      [    0.101776] Advanced Linux Sound Architecture Driver Initialized.
      [    0.102463] Bluetooth: Core ver 2.22
      [    0.102547] NET: Registered protocol family 31
      [    0.102556] Bluetooth: HCI device and connection manager initialized
      下略
      

      考虑可能的问题:

      1. 使用USB HUB进行刷写,影响速率
      2. 使用的 eMMC 速度较慢
      3. USB 连接不稳定,出现断连情况
      4. 供电不足,cpu 在烧写状态下缺电
      5. eMMC 布局走线不合理
      6. 选择全盘擦除升级而不是分区擦除升级

      d9c7827d-1dfa-4a27-bc61-b60f9c3d5a51-image.png

      发布在 其它全志芯片讨论区
      A
      awwwwa
    • 回复: v853板子做为usb device通过usb接入pc,有没推荐好的方案或者开源的库和案例来传输私有音视频.

      可以走UAC协议,adb forward

      发布在 V Series
      A
      awwwwa
    • 回复: RotatePictureHw函数使用

      ls /dev 看一下输出

      发布在 GUI
      A
      awwwwa
    • 回复: D1s芯片烧录melis固件启动报错,大家帮我看看咋回事

      @liu11372650 在 D1s芯片烧录melis固件启动报错,大家帮我看看咋回事 中说:

      0x000000004003049c

      根据这个地址,objdump出来elf去找一下是哪一个函数报错

      发布在 MR Series
      A
      awwwwa
    • 回复: 韦东山的v853板子作为uvc设备通过usb0 接到到pc上,PC不能识别问题.

      @sofia 我记得需要在小机运行一个uvc的程序,因为vin框架和isp通路与nxp的不一样,nxp是软件isp这个是硬件isp,可能有些地方需要适配

      发布在 V Series
      A
      awwwwa
    • 回复: 全志芯片选型求推荐

      @jinxiangwzh 不需要,USB3.0支持OTG

      发布在 其它全志芯片讨论区
      A
      awwwwa
    • 回复: 全志芯片选型求推荐

      A523,CSI规格16M不过ISP是8M的

      发布在 其它全志芯片讨论区
      A
      awwwwa
    • 回复: 韦东山的v853板子作为uvc设备通过usb0 接到到pc上,PC不能识别问题.

      这个UVC需要本地运行一个UVC的服务端调用摄像头通路才可建立,否则不会上报为UVC设备而是复合设备

      发布在 V Series
      A
      awwwwa
    • 1
    • 2
    • 3
    • 4
    • 5
    • 6
    • 5 / 6