导航

    全志在线开发者论坛

    • 注册
    • 登录
    • 搜索
    • 版块
    • 话题
    • 在线文档
    • 社区主页
    1. 主页
    2. casojie
    3. 帖子
    C
    • 资料
    • 关注 0
    • 粉丝 1
    • 我的积分 1453
    • 主题 7
    • 帖子 27
    • 最佳 1
    • 群组 0

    casojie 发布的帖子

    • RTL的USB接口的WiFi驱动移植问题

      WiFi芯片 rtl8818FU,也是USB接口的WiFi芯片,但是移植编译加载后

      [   65.256086] 8188fu: loading out-of-tree module taints kernel.
      [   91.352280] RTW: module init start
      [   91.352292] RTW: rtl8188fu v5.11.5.4-0-g65b8f0aad.20220413
      [   91.352298] RTW: build time: Feb 28 2023 11:52:06
      [   91.352307] RTW: rtw_drv_entry: power on failed!!(-22)
      [   91.352312] RTW: module init ret=-1
      [  117.393206] RTW: module init start
      [  117.393217] RTW: rtl8188fu v5.11.5.4-0-g65b8f0aad.20220413
      [  117.393223] RTW: build time: Feb 28 2023 11:52:06
      [  117.393232] RTW: rtw_drv_entry: power on failed!!(-22)
      [  117.393237] RTW: module init ret=-1
      

      好像设备注册或者什么出了问题,导致有个变量没有初始化
      e6cdd489-00ac-472e-9ed5-c40c82d1bf3b-ad806a78464f808878442f5c65d42a8.jpg
      还有你们没有遇到驱动原本的platform_ARM_SUNxl_usb.c不能使用吗,我很好奇你们你们这个文件中的函数是怎么写的

      platform_wifi_power_on
      platform_wifi_power_off
      

      这是我的,大佬看看有问题吗

      /******************************************************************************
       *
       * Copyright(c) 2013 - 2017 Realtek Corporation.
       *
       * This program is free software; you can redistribute it and/or modify it
       * under the terms of version 2 of the GNU General Public License as
       * published by the Free Software Foundation.
       *
       * This program is distributed in the hope that it will be useful, but WITHOUT
       * ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
       * FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for
       * more details.
       *
       *****************************************************************************/
      /*
       * Description:
       *	This file can be applied to following platforms:
       *	CONFIG_PLATFORM_ARM_SUNXI Series platform
       *
       */
      
      #include <drv_types.h>
      
      extern int sunxi_usb_disable_hcd(__u32 usbc_no);
      extern int sunxi_usb_enable_hcd(__u32 usbc_no);
      extern int sunxi_wlan_get_bus_index(void);
      extern void sunxi_wlan_set_power(int on);
      
      int platform_wifi_power_on(void)
      {
          int ret = 0;
          int wlan_bus_index = sunxi_wlan_get_bus_index();
          if (wlan_bus_index < 0)
              return wlan_bus_index;
      
          sunxi_wlan_set_power(1);
          mdelay(100);
          sunxi_usb_enable_hcd(wlan_bus_index);
      
          return ret;
      }
      void platform_wifi_power_off(void)
      {
          int wlan_bus_index = sunxi_wlan_get_bus_index();
          if (wlan_bus_index < 0)
              return wlan_bus_index;
          sunxi_usb_disable_hcd(wlan_bus_index);
          sunxi_wlan_set_power(0);
      }
      

      就是platform_wifi_power_on报错才加载失败的,求指点

      发布在 MR Series
      C
      casojie
    • 回复: 【FAQ】全志D1芯片 如何移植 rtl8821cu wifi 驱动到 Linux-5.4内核?

      几乎是同类型的芯片 rtl8818FU,也是USB接口的WiFi芯片,但是移植编译加载后

      [   65.256086] 8188fu: loading out-of-tree module taints kernel.
      [   91.352280] RTW: module init start
      [   91.352292] RTW: rtl8188fu v5.11.5.4-0-g65b8f0aad.20220413
      [   91.352298] RTW: build time: Feb 28 2023 11:52:06
      [   91.352307] RTW: rtw_drv_entry: power on failed!!(-22)
      [   91.352312] RTW: module init ret=-1
      [  117.393206] RTW: module init start
      [  117.393217] RTW: rtl8188fu v5.11.5.4-0-g65b8f0aad.20220413
      [  117.393223] RTW: build time: Feb 28 2023 11:52:06
      [  117.393232] RTW: rtw_drv_entry: power on failed!!(-22)
      [  117.393237] RTW: module init ret=-1
      

      好像设备注册或者什么出了问题,导致有个变量没有初始化
      e6cdd489-00ac-472e-9ed5-c40c82d1bf3b-ad806a78464f808878442f5c65d42a8.jpg
      还有你们没有遇到驱动原本的platform_ARM_SUNxl_usb.c不能使用吗,我很好奇你们你们这个文件中的函数是怎么写的

      platform_wifi_power_on
      platform_wifi_power_off
      

      这是我的,大佬看看有问题吗

      /******************************************************************************
       *
       * Copyright(c) 2013 - 2017 Realtek Corporation.
       *
       * This program is free software; you can redistribute it and/or modify it
       * under the terms of version 2 of the GNU General Public License as
       * published by the Free Software Foundation.
       *
       * This program is distributed in the hope that it will be useful, but WITHOUT
       * ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
       * FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for
       * more details.
       *
       *****************************************************************************/
      /*
       * Description:
       *	This file can be applied to following platforms:
       *	CONFIG_PLATFORM_ARM_SUNXI Series platform
       *
       */
      
      #include <drv_types.h>
      
      extern int sunxi_usb_disable_hcd(__u32 usbc_no);
      extern int sunxi_usb_enable_hcd(__u32 usbc_no);
      extern int sunxi_wlan_get_bus_index(void);
      extern void sunxi_wlan_set_power(int on);
      
      int platform_wifi_power_on(void)
      {
          int ret = 0;
          int wlan_bus_index = sunxi_wlan_get_bus_index();
          if (wlan_bus_index < 0)
              return wlan_bus_index;
      
          sunxi_wlan_set_power(1);
          mdelay(100);
          sunxi_usb_enable_hcd(wlan_bus_index);
      
          return ret;
      }
      void platform_wifi_power_off(void)
      {
          int wlan_bus_index = sunxi_wlan_get_bus_index();
          if (wlan_bus_index < 0)
              return wlan_bus_index;
          sunxi_usb_disable_hcd(wlan_bus_index);
          sunxi_wlan_set_power(0);
      }
      

      就是platform_wifi_power_on报错才加载失败的,求指点

      发布在 其它全志芯片讨论区
      C
      casojie
    • 回复: A133 longan 平台 RT8723DS WIFI 测试

      @whycan 大哥,使用hostapd 开热点后,然后关闭杀掉hostapd,AP热点还是在,怎么通过正常途径关掉,有这样的问题吗,我使用的是RT8188FU

      发布在 其它全志芯片讨论区
      C
      casojie
    • inmod WiFi驱动执行时间过长(20+s),inmod xxx.ko执行时间过长
      [ 6222.224457] =======================================================
      [ 6222.224461] ==== Launching Wi-Fi driver! (Powered by Rockchip) ====
      [ 6222.224464] =======================================================
      [ 6222.224468] Realtek 8188FU USB WiFi driver (Powered by Rockchip) init.
      [ 6222.224472] RTL871X: module init start
      [ 6222.224477] RTL871X: rtl8188fu v4.3.23.6_20964.20170110
      [ 6222.224601] rtl8188fu 1-1:1.0: no of_node; not parsing pinctrl DT
      [ 6222.225028] RTL871X: 
      [ 6222.225028] usb_endpoint_descriptor(0):
      [ 6222.225035] RTL871X: bLength=7
      [ 6222.225039] RTL871X: bDescriptorType=5
      [ 6222.225043] RTL871X: bEndpointAddress=81
      [ 6222.225048] RTL871X: wMaxPacketSize=512
      [ 6222.225052] RTL871X: bInterval=0
      [ 6222.225056] RTL871X: RT_usb_endpoint_is_bulk_in = 1
      [ 6222.225060] RTL871X: 
      [ 6222.225060] usb_endpoint_descriptor(1):
      [ 6222.225065] RTL871X: bLength=7
      [ 6222.225069] RTL871X: bDescriptorType=5
      [ 6222.225072] RTL871X: bEndpointAddress=2
      [ 6222.225077] RTL871X: wMaxPacketSize=512
      [ 6222.225081] RTL871X: bInterval=0
      [ 6222.225086] RTL871X: RT_usb_endpoint_is_bulk_out = 2
      [ 6222.225090] RTL871X: 
      [ 6222.225090] usb_endpoint_descriptor(2):
      [ 6222.225093] RTL871X: bLength=7
      [ 6222.225097] RTL871X: bDescriptorType=5
      [ 6222.225101] RTL871X: bEndpointAddress=3
      [ 6222.225105] RTL871X: wMaxPacketSize=512
      [ 6222.225110] RTL871X: bInterval=0
      [ 6222.225114] RTL871X: RT_usb_endpoint_is_bulk_out = 3
      [ 6222.225119] RTL871X: nr_endpoint=3, in_num=1, out_num=2
      [ 6222.225119] 
      [ 6222.225122] RTL871X: USB_SPEED_HIGH
      [ 6222.225128] RTL871X: CHIP TYPE: RTL8188FU
      [ 6222.225563] RTL871X: rtw_hal_config_rftype RF_Type is 3 TotalTxPath is 1 
      [ 6222.225576] RTL871X: Chip Version Info: CHIP_8188F_Normal_Chip_SMIC_B_CUT_1T1R_RomVer(0)
      [ 6222.225587] RTL871X: _ConfigChipOutEP_8188F OutEpQueueSel(0x05), OutEpNumber(2)
      [ 6222.225758] RTL871X: EEPROM type is E-FUSE
      [ 6222.226262] RTL871X: Boot from EFUSE, Autoload OK !
      [ 6222.226885] RTL871X: hal_EfuseSwitchToBank: Efuse switch bank to 0
      [ 6222.386632] RTL871X: hal_ReadEFuse_WiFi: data end at address=0x6b
      [ 6222.386895] RTL871X: EEPROM VID = 0x bda
      [ 6222.386901] RTL871X: EEPROM PID = 0xf179
      [ 6222.386924] RTL871X: hal_com_config_channel_plan chplan:0x20
      [ 6222.386933] RTL871X: Hal_EfuseParsePowerSavingMode_8188F...bHWPwrPindetect(0)-bHWPowerdown(0) ,bSupportRemoteWakeup(1)
      [ 6222.386938] RTL871X: ### PS params=>  power_mgnt(2),usbss_enable(0) ###
      [ 6222.388888] RTL871X: kfree Pwr Trim flag:1
      [ 6222.388895] RTL871X: bb_gain:1
      [ 6222.393430] usb 1-1: request firmware rtlwifi/rtl8188fufw.bin
      [ 6222.393645] usb 1-1: request firmware rtlwifi/rtl8188fufw.bin loaded
      [ 6222.393659] RTL871X: rtl8188f_FirmwareDownload: fw_ver=4 fw_subver=0000 sig=0x88f1, Month=08, Date=22, Hour=17, Minute=36
      [ 6222.393664] RTL871X: rtl8188f_FirmwareDownload(): Shift for fw header!
      [ 6222.393670] RTL871X: rtl8188f_FirmwareDownload by IO write!
      [ 6222.455140] RTL871X: polling_fwdl_chksum: Checksum report OK! (1, 0ms), REG_MCUFWDL:0x0c050105
      [ 6222.456757] RTL871X: _8051Reset8188: Finish
      [ 6222.470257] RTL871X: _FWFreeToGo: Polling FW ready OK! (102, 20ms), REG_MCUFWDL:0x0c0501c6
      [ 6222.470265] RTL871X: rtl8188f_FirmwareDownload: DLFW OK !
      [ 6222.470273] RTL871X: rtl8188f_FirmwareDownload success. write_fw:1, 80ms
      [ 6222.470515] RTL871X:  <=== rtl8188f_FirmwareDownload()
      [ 6222.472507] RTL871X: CardDisableRTL8188FU
      [ 6222.477426] RTL871X: hal_read_mac_hidden_rpt OK! (1, 0ms), fwdl:1, id:0x19
      [ 6222.477436] RTL871X: InitAdapterVariablesByPROM_8188FU(): REPLACEMENT = 0
      [ 6222.477442] RTL871X: rtw_hal_read_chip_info in 250 ms
      [ 6222.477753] RTL871X: init_channel_set((null)) ChannelPlan ID:0x20, ch num:13
      [ 6222.478746] RTL871X: NR_RECVBUFF: 8
      [ 6222.478752] RTL871X: MAX_RECVBUF_SZ: 32768
      [ 6222.478783] RTL871X: NR_PREALLOC_RECV_SKB: 8
      [ 6222.479143] RTL871X: rtw_alloc_macid((null)) if1, hwaddr:ff:ff:ff:ff:ff:ff macid:1
      [ 6222.479177] RTL871X: Init_ODM_ComInfo_8188f(): fab_ver=0 cut_ver=1
      [ 6222.479219] RTL871X: phy_ConfigBBWithPgParaFile(): No File PHY_REG_PG.txt, Load from HWImg Array!
      [ 6222.479235] RTL871X: default power by rate loaded
      [ 6222.485192] RTL871X: pwrctrlpriv.bSupportRemoteWakeup~~~~~~
      [ 6222.485202] RTL871X: pwrctrlpriv.bSupportRemoteWakeup~~~[1]~~~
      [ 6222.485209] RTL871X: can't get autopm: 
      [ 6222.485222] RTL871X: rtw_macaddr_cfg mac addr:a0:67:20:b7:e0:1e
      [ 6222.485230] RTL871X: bDriverStopped:True, bSurpriseRemoved:False, bup:0, hw_init_completed:0
      [ 6222.485318] RTL871X: rtw_wiphy_alloc(phy5)
      [ 6222.485328] RTL871X: rtw_wdev_alloc(padapter=00000000a2e2199f)
      [ 6222.485339] RTL871X: rtw_wiphy_register(phy5)
      [ 6222.485503] RTL871X: _rtw_reg_notifier
      [ 6222.485513] RTL871X: _rtw_reg_notifier_apply: NL80211_REGDOM_SET_BY_CORE to DRV
      [ 6222.485659] RTL871X: rtw_ndev_init(wlan0) if1 mac_addr=a0:67:20:b7:e0:1e
      [ 6222.486689] RTL871X: cfg80211_rtw_get_txpower
      [ 6222.491553] usbcore: registered new interface driver rtl8188fu
      [ 6222.491562] RTL871X: module init ret=0
      

      这是执行inmod RTL8188fu.ko的dmege
      执行上诉命令,需要大概20多秒才能返回
      加载后wifi功能正常,看起来没什么明显的报错
      请问大佬给点思路

      发布在 MR Series
      C
      casojie
    • 移植RTL8188fu驱动编译报错,sw_usb_enable_hcd等函数未定义
      f133_plc/AllWinnerF133_Linux_pub/prebuilt/gcc/linux-x86/riscv/toolchain-thead-glibc/riscv64-glibc-gcc-thead_20200702/bin/riscv64-unknown-linux-gnu-ld: drivers/net/wireless/rtl8188fu/platform/platform_ARM_SUNxI_usb.o: in function `.L0 ':
      platform_ARM_SUNxI_usb.c:(.text+0x22): undefined reference to `script_parser_fetch'
      f133_plc/AllWinnerF133_Linux_pub/prebuilt/gcc/linux-x86/riscv/toolchain-thead-glibc/riscv64-glibc-gcc-thead_20200702/bin/riscv64-unknown-linux-gnu-ld: platform_ARM_SUNxI_usb.c:(.text+0x48): undefined reference to `sw_usb_enable_hcd'
      f133_plc/AllWinnerF133_Linux_pub/prebuilt/gcc/linux-x86/riscv/toolchain-thead-glibc/riscv64-glibc-gcc-thead_20200702/bin/riscv64-unknown-linux-gnu-ld: platform_ARM_SUNxI_usb.c:(.text+0xcc): undefined reference to `sw_usb_disable_hcd'
      

      移植WiFi驱动RTL8188FU,是使用USBWiFi芯片,但是上诉的几个函数一直找不到定义,搜索了全部的代码,都没有发现这些函数的定义,求大佬指点
      sw_usb_enable_hcd
      sw_usb_disable_hcd
      script_parser_fetch
      D1S(F133-A)Tina

      发布在 编译和烧写问题专区
      C
      casojie
    • 回复: Tina Linus,make时重定义multiple definition of `aes_encrypt'?

      @everyoung 大哥,这个问题应该怎么解决的啊

      发布在 MR Series
      C
      casojie
    • 回复: F133A(D1s)如何使用GPIO:PG4 PG5?

      解决了,引脚占用问题,谢谢各位

      发布在 MR Series
      C
      casojie
    • 回复: F133A(D1s)如何使用GPIO:PG4 PG5?

      @yuzukitsuru

      configfs-gadget gadget: high-speed config #1: c
      android_work: sent uevent USB_STATE=CONFIGURED
      sun8iw20-pinctrl 2000000.pinctrl: pin PG4 already requested by 4021000.sdmmc; cannot claim for 2000000.pinctrl:196
      sun8iw20-pinctrl 2000000.pinctrl: pin-196 (2000000.pinctrl:196) status -22

      发布在 MR Series
      C
      casojie
    • 回复: F133A(D1s)如何使用GPIO:PG4 PG5?

      @dream 我在这路径下没有这个文件
      /proc/sys/debug/sunxi_pinctrl
      没有sunxi_pinctrl

      发布在 MR Series
      C
      casojie
    • 回复: F133A(D1s)如何使用GPIO:PG4 PG5?

      @whycan 是还需要设置什么东西吗,我这边显示无效参数

      发布在 MR Series
      C
      casojie
    • F133A(D1s)如何使用GPIO:PG4 PG5?

      按照计算,PG4 = 6*32+4 = 196

      root@TinaLinux:/sys/class/gpio# echo 196 > export 
      ash: write error: Invalid argument
      

      数字超过110+就不行了
      是还有一些东西需要配置的吗,比如设备树什么的
      小白萌新提问

      发布在 MR Series
      C
      casojie
    • 回复: d1s下的overlays挂载问题,提示“No such device”

      @tevet 前几天解决了,谢谢回复

      发布在 MR Series
      C
      casojie
    • 回复: d1s下的overlays挂载问题,提示“No such device”

      @suncw 抱歉,我还是不明白,我的设备是emmc存储,mkfs.ext4 在板子上是可以正常使用的,看完后我还是不知道应该怎么做,而且我使用的是busybox-init 对应的以下fsata文件都没有

      发布在 MR Series
      C
      casojie
    • 回复: d1s下的overlays挂载问题,提示“No such device”

      @suncw 我不是很明白,根目录下是有overlay文件夹的,它应该不需要创建文件夹了吧,而我也尝试手动挂载,也是提示

      root@TinaLinux:/# mount -t ext4 -o sync,data=journal /dev/by-name/rootfs_data /o
      verlay/
      mount: mounting /dev/by-name/rootfs_data on /overlay/ failed: No such device
      

      我也尝试执行

      root@TinaLinux:/# mkfs.ext4 /dev/by-name/rootfs_data 
      mke2fs 1.46.4 (18-Aug-2021)
      /dev/by-name/rootfs_data contains a ext4 file system
      	created on Thu Jan  1 08:07:28 1970
      Proceed anyway? (y,N) y
      Discarding device blocks: done                            
      Creating filesystem with 5120 1k blocks and 1280 inodes
      
      Allocating group tables: done                            
      Writing inode tables: done                            
      Creating journal (1024 blocks): done
      Writing superblocks and filesystem accounting information: done
      
      

      仍然不行,唉

      发布在 MR Series
      C
      casojie
    • d1s下的overlays挂载问题,提示“No such device”

      D1S 无法挂载overlays,开机打印如下

      Starting kernel ...
      
      [01.717][mmc]: mmc exit start
      [01.736][mmc]: mmc 2 exit ok
      mount: mounting none on /dev failed: Device or resource busy
      mount: mounting /dev/by-name/rootfs_data on /overlay failed: No such device
      Mount Failed: formating /dev/by-name/rootfs_data to ext4 ...
      mke2fs 1.46.4 (18-Aug-2021)
      mount: mounting /dev/by-name/rootfs_data on /overlay failed: No such device
      Didn't found ubi volume "env"
      Cannot open /dev/ubi0: No such file or directory
      Didn't found ubi volume "env-redund"
      Cannot open /dev/ubi0: No such file or directory
      mkdir: can't create directory '/overlay/upper': Read-only file system
      mkdir: can't create directory '/overlay/workdir': Read-only file system
      mount: mounting overlayfs:/overlay on /mnt failed: No such file or directory
      mount: mounting /proc on /mnt/proc failed: No such file or directory
      pivot_root: No such file or directory
      mount: mounting /rom/dev on /dev failed: No such file or directory
      mount: mounting /rom/tmp on /tmp failed: No such file or directory
      mount: mounting /rom/sys on /sys failed: No such file or directory
      mount: mounting /rom/overlay on /overlay failed: No such file or directory
      can't run '/etc/preinit': No such file or directory
      mount: mounting proc on /proc failed: Device or resource busy
      mount: mounting tmpfs on /run failed: No such file or directory
      hostname: can't open '/etc/hostname': No such file or directory
      ------run rc.preboot file-----
      mke2fs 1.46.4 (18-Aug-2021)
      ------run rc.modules file-----
      ------run rc.final file-----
      ifconfig: SIOCGIFFLAGS: No such device
      sh: write error: No such device
      host_chose finished!
      nice: can't execute '/usr/bin/story_ota_bin': No such file or directory
      device_chose finished!
      
      

      在贴吧也搜索到类似的问题,都是修改base-file里的文件,但是我是使用的busybox-init, 都找不到对应的fstat文件,感觉分区设置好像有问题,太蔡了,求大哥指点,以下pack的log

      
      jie.cao@umr940:~/f133A/f133$ pack
      --==========--
      PACK_CHIP         sun20iw1p1
      PACK_PLATFORM     tina
      PACK_BOARD        f133-evb1
      PACK_KERN        
      PACK_DEBUG        uart0
      PACK_SIG          none
      PACK_SECURE       none
      PACK_MODE         normal
      PACK_FUNC         android
      PACK_PROGRAMMER   none
      PACK_TAR_IMAGE    none
      PACK_TOPDIR       /homeB/jie.cao/f133A/f133
      --==========--
      No kernel param, parse it from f133
      copying tools file
      copying configs file
      storage_type value is 2
      rm /homeB/jie.cao/f133A/f133/out/f133-evb1/image/sys_partition_nor.fex
      rm /homeB/jie.cao/f133A/f133/out/f133-evb1/image/image_nor.cfg
      copying boot resource
      copying boot file
      make user resource for : /homeB/jie.cao/f133A/f133/out/f133-evb1/image/sys_partition.fex
      handle partition user-res
      no user resource partitions
      APP_PART_DOWNLOAD_FILE = /homeB/jie.cao/f133A/f133/out/f133-evb1/image/app.fex
      Need size of filesystem
      no data resource partitions
      don't build dtbo ...
      update_chip
      
      sboot file Path=/homeB/jie.cao/f133A/f133/out/f133-evb1/image/sboot.bin
      script file Path=/homeB/jie.cao/f133A/f133/out/f133-evb1/image/sys_config.bin
      
      update:unable to open sboot file
      script update sboot ok
      pack boot package
      GetPrivateProfileSection read to end
      content_count=3
      LICHEE_REDUNDANT_ENV_SIZE config in BoardConfig.mk
      --mkenvimage create redundant env data!--
      ---redundant env data size 0x20000---
      packing for tina linux
      normal
      mbr count = 4
      
      partitation file Path=/homeB/jie.cao/f133A/f133/out/f133-evb1/image/sys_partition.bin
      mbr_name file Path=/homeB/jie.cao/f133A/f133/out/f133-evb1/image/sunxi_mbr.fex
      download_name file Path=/homeB/jie.cao/f133A/f133/out/f133-evb1/image/dlinfo.fex
      
      mbr size = 16384
      mbr magic softw411
      disk name=boot-resource
      disk name=env
      disk name=env-redund
      disk name=boot
      disk name=rootfs
      disk name=recovery
      disk name=rootfs_data
      this is not a partition key
      update_for_part_info 0
      crc 0 = 9632c2e2
      crc 1 = 38f93bf
      crc 2 = 66396619
      crc 3 = f3843744
      gpt_head->header_crc32 = 0xac1db3f8
      GPT----part num 8---
      gpt_entry: 128
      gpt_header: 92
      GPT:boot-resource: 12000         121f7       
      GPT:env         : 121f8         123ef       
      GPT:env-redund  : 123f0         125e7       
      GPT:boot        : 125e8         157e7       
      GPT:rootfs      : 157e8         229e7       
      GPT:recovery    : 229e8         27767       
      GPT:rootfs_data : 27768         29f67       
      GPT:UDISK       : 29f68         ffffffde    
      update gpt file ok
      update mbr file ok
      temp = 20
      mbr count = 4 total_sectors = 15269888 logic_offset = 40960
      
      partitation file Path=/homeB/jie.cao/f133A/f133/out/f133-evb1/image/sys_partition.bin
      mbr_name file Path=/homeB/jie.cao/f133A/f133/out/f133-evb1/image/sunxi_mbr.fex
      download_name file Path=/homeB/jie.cao/f133A/f133/out/f133-evb1/image/dlinfo.fex
      
      mbr size = 16384
      mbr magic softw411
      disk name=boot-resource
      disk name=env
      disk name=env-redund
      disk name=boot
      disk name=rootfs
      disk name=recovery
      disk name=rootfs_data
      this is not a partition key
      update_for_part_info 0
      crc 0 = 9632c2e2
      crc 1 = 38f93bf
      crc 2 = 66396619
      crc 3 = f3843744
      gpt_head->header_crc32 = 0x36191a6a
      GPT----part num 8---
      gpt_entry: 128
      gpt_header: 92
      GPT:boot-resource: 12000         121f7       
      GPT:env         : 121f8         123ef       
      GPT:env-redund  : 123f0         125e7       
      GPT:boot        : 125e8         157e7       
      GPT:rootfs      : 157e8         229e7       
      GPT:recovery    : 229e8         27767       
      GPT:rootfs_data : 27768         29f67       
      GPT:UDISK       : 29f68         e8ffde      
      update gpt file ok
      update mbr file ok
      ====================================
      show "sys_partition_for_dragon.fex" message
      ------------------------------------
        [mbr]
        mbr_size  : 16384 Kbyte
      ------------------------------------
        partition_name  : boot-resource
        partition_size  : 504
        downloadfile  : boot-resource.fex
        boot-resource.fex size : 80K byte
      ------------------------------------
        partition_name  : env
        partition_size  : 504
        downloadfile  : env.fex
        env.fex size : 128K byte
      ------------------------------------
        partition_name  : env-redund
        partition_size  : 504
        downloadfile  : env.fex
        env.fex size : 128K byte
      ------------------------------------
        partition_name  : boot
        partition_size  : 12800
        downloadfile  : boot.fex
        boot.fex -> /homeB/jie.cao/f133A/f133/out/f133-evb1/boot.img
        boot.img size : 5.8M byte
      ------------------------------------
        partition_name  : rootfs
        partition_size  : 53760
        downloadfile  : rootfs.fex
        rootfs.fex -> /homeB/jie.cao/f133A/f133/out/f133-evb1/rootfs.img
        rootfs.img size : 16M byte
      ------------------------------------
        partition_name  : recovery
        partition_size  : 19840
      ------------------------------------
        partition_name  : rootfs_data
        partition_size  : 10240
      ------------------------------------
      /homeB/jie.cao/f133A/f133/out/host/bin/
      /homeB/jie.cao/f133A/f133/out/f133-evb1/image
      Begin Parse sys_partion.fex
      Add partion boot-resource.fex BOOT-RESOURCE_FEX
      Add partion very boot-resource.fex BOOT-RESOURCE_FEX
      FilePath: boot-resource.fex
      FileLength=14000Add partion env.fex ENV_FEX000000000
      Add partion very env.fex ENV_FEX000000000
      FilePath: env.fex
      FileLength=20000Add partion env.fex ENV_FEX000000000
      Add partion very env.fex ENV_FEX000000000
      FilePath: env.fex
      FileLength=20000Add partion boot.fex BOOT_FEX00000000
      Add partion very boot.fex BOOT_FEX00000000
      FilePath: boot.fex
      FileLength=5b4800Add partion rootfs.fex ROOTFS_FEX000000
      Add partion very rootfs.fex ROOTFS_FEX000000
      FilePath: rootfs.fex
      FileLength=fc0000BuildImg 0
      Dragon execute image.cfg SUCCESS !
      ----------image is for nand/emmc----------
      ----------image is at----------
      
      
      发布在 MR Series
      C
      casojie
    • 回复: MQ-Pro overlay挂载的问题

      @lbuque 大哥,这个pack要怎么打,不会啊,全部下载放到SDK根目录下吗

      发布在 MR Series
      C
      casojie
    • 回复: F133A烧录时大概率卡住失败

      @yteraa emmc, 谢谢

      发布在 MR Series
      C
      casojie
    • F133A烧录时大概率卡住失败

      背景:开始时使用F133B芯片,编译了镜像烧录,几乎没怎么遇到烧录失败的情况
      现在做了一款新的PCB板子,贴的是F133A芯片,就大概率出现卡0%,卡10%,卡55%,卡70%,但也有大约10%的概率成功,据之前有个大哥说,代码软件层面上不用区分F133A和F133B,但是同样的镜像对F133B和F133A烧录情况不一致(当然PCB的电路也不一样),现在就不知道是我代码编译出的镜像有问题,还是后面的F133A电路硬件上有问题,请大佬指点,烧录卡住时的打印如下
      10%

      tfs 5, d200, 8000
      recovery 6, 4d80, 8000
      rootfs_data 7, 2800, 8000
      UDISK 8, 0, 0
      [09.637]erase all part start
      need erase flash: 18
      [09.643][mmc]: erase from: 0, to: 7634943, cnt: 7634944, erase_group: 1024
      [09.678][mmc]: sunxi_mmc_do_send_cmd_common: cmd 38 wait rsp busy 0x1c ms 
      [09.685]read item0 copy0
      [09.687]Item0 (Map) magic is bad
      [09.690]the secure storage item0 copy0 magic is bad
      [09.695]Item0 (Map) magic is bad
      [09.698]the secure storage item0 copy1 magic is bad
      [09.702]Item0 (Map) magic is bad
      [09.705]the secure storage map is empty
      [09.710]erase secure storage: 0 ok
      SUNXI_EFEX_MBR_TAG
      mbr size = 0x10000
      write primary GPT success
      write Backup GPT success
      [09.727]update partition map
      FEX_CMD_fes_verify_status
      FEX_CMD_fes_verify last err=0
      ******Has init
      

      卡50%

      common1(partition3) need it, here is a weak func
      total part: 9
      mbr 0, 8000, 8000
      boot-resource 1, 1f8, 8000
      env 2, 1f8, 8000
      env-redund 3, 1f8, 8000
      boot 4, 3200, 8000
      rootfs 5, d200, 8000
      recovery 6, 4d80, 8000
      rootfs_data 7, 2800, 8000
      UDISK 8, 0, 0
      [09.491]erase all part start
      need erase flash: 18
      [09.497][mmc]: erase from: 0, to: 7634943, cnt: 7634944, erase_group: 1024
      [09.513][mmc]: sunxi_mmc_do_send_cmd_common: cmd 38 wait rsp busy 0xa ms 
      [09.520]read item0 copy0
      [09.522]Item0 (Map) magic is bad
      [09.525]the secure storage item0 copy0 magic is bad
      [09.530]Item0 (Map) magic is bad
      [09.533]the secure storage item0 copy1 magic is bad
      [09.537]Item0 (Map) magic is bad
      [09.540]the secure storage map is empty
      [09.545]erase secure storage: 0 ok
      SUNXI_EFEX_MBR_TAG
      mbr size = 0x10000
      write primary GPT success
      write Backup GPT success
      [09.562]update partition map
      FEX_CMD_fes_verify_status
      FEX_CMD_fes_verify last err=0
      ******Has init
      FEX_CMD_fes_verify_value, start 0x8000, size high 0x0:low 0x14000
      FEX_CMD_fes_verify_value 0xe6f75b5c
      FEX_CMD_fes_verify_value, start 0x81f8, size high 0x0:low 0x20000
      FEX_CMD_fes_verify_value 0xa0bf6d78
      FEX_CMD_fes_verify_value, start 0x83f0, size high 0x0:low 0x20000
      FEX_CMD_fes_verify_value 0xa0bf6d78
      

      卡79%

      DISK 8, 0, 0
      [09.584]erase all part start
      need erase flash: 18
      [09.590][mmc]: erase from: 0, to: 7634943, cnt: 7634944, erase_group: 1024
      [09.606][mmc]: sunxi_mmc_do_send_cmd_common: cmd 38 wait rsp busy 0xa ms 
      [09.613]read item0 copy0
      [09.615]Item0 (Map) magic is bad
      [09.618]the secure storage item0 copy0 magic is bad
      [09.623]Item0 (Map) magic is bad
      [09.626]the secure storage item0 copy1 magic is bad
      [09.630]Item0 (Map) magic is bad
      [09.633]the secure storage map is empty
      [09.638]erase secure storage: 0 ok
      SUNXI_EFEX_MBR_TAG
      mbr size = 0x10000
      write primary GPT success
      write Backup GPT success
      [09.655]update partition map
      FEX_CMD_fes_verify_status
      FEX_CMD_fes_verify last err=0
      ******Has init
      FEX_CMD_fes_verify_value, start 0x8000, size high 0x0:low 0x14000
      FEX_CMD_fes_verify_value 0xe6f75b5c
      FEX_CMD_fes_verify_value, start 0x81f8, size high 0x0:low 0x20000
      FEX_CMD_fes_verify_value 0x882de1bc
      FEX_CMD_fes_verify_value, start 0x83f0, size high 0x0:low 0x20000
      FEX_CMD_fes_verify_value 0x882de1bc
      FEX_CMD_fes_verify_value, start 0x85e8, size high 0x0:low 0x5fc000
      FEX_CMD_fes_verify_value 0xd668265a
      
      发布在 MR Series
      C
      casojie
    • 回复: 哪吒开发板D1编译报错Cannot find lib ld-linux-riscv64-lp64.so.1

      @yteraa 也有卡10%的

      common1(partition3) need it, here is a weak func
      total part: 9
      mbr 0, 8000, 8000
      boot-resource 1, 1f8, 8000
      env 2, 1f8, 8000
      env-redund 3, 1f8, 8000
      boot 4, 3200, 8000
      rootfs 5, 100000, 8000
      recovery 6, 4d80, 8000
      rootfs_data 7, 2800, 8000
      UDISK 8, 0, 0
      [09.694]erase all part start
      need erase flash: 18
      [09.700][mmc]: erase from: 0, to: 7634943, cnt: 7634944, erase_group: 1024
      [09.719][mmc]: sunxi_mmc_do_send_cmd_common: cmd 38 wait rsp busy 0xd ms 
      [09.725]read item0 copy0
      [09.728]Item0 (Map) magic is bad
      [09.731]the secure storage item0 copy0 magic is bad
      [09.736]Item0 (Map) magic is bad
      [09.738]the secure storage item0 copy1 magic is bad
      [09.743]Item0 (Map) magic is bad
      [09.746]the secure storage map is empty
      [09.751]erase secure storage: 0 ok
      SUNXI_EFEX_MBR_TAG
      mbr size = 0x10000
      write primary GPT success
      write Backup GPT success
      [09.768]update partition map
      FEX_CMD_fes_verify_status
      FEX_CMD_fes_verify last err=0
      ******Has init
      
      
      发布在 MR Series
      C
      casojie
    • 回复: 哪吒开发板D1编译报错Cannot find lib ld-linux-riscv64-lp64.so.1

      @yteraa 也就是说,在编译时,都无需关心是A还是B是吗,现在遇到一个问题,原先的开发板F133B烧录正常,而同样的镜像到F133A大概率失败(也可能成功10%),F133A是我们做的另一款板子,现在不知道问题出在硬件上,还是镜像上
      卡55%

      ```bash
      common1(partition3) need it, here is a weak func
      total part: 9
      mbr 0, 8000, 8000
      boot-resource 1, 1f8, 8000
      env 2, 1f8, 8000
      env-redund 3, 1f8, 8000
      boot 4, 3200, 8000
      rootfs 5, 100000, 8000
      recovery 6, 4d80, 8000
      rootfs_data 7, 2800, 8000
      UDISK 8, 0, 0
      [09.584]erase all part start
      need erase flash: 18
      [09.590][mmc]: erase from: 0, to: 7634943, cnt: 7634944, erase_group: 1024
      [09.606][mmc]: sunxi_mmc_do_send_cmd_common: cmd 38 wait rsp busy 0xa ms 
      [09.613]read item0 copy0
      [09.615]Item0 (Map) magic is bad
      [09.618]the secure storage item0 copy0 magic is bad
      [09.623]Item0 (Map) magic is bad
      [09.626]the secure storage item0 copy1 magic is bad
      [09.630]Item0 (Map) magic is bad
      [09.633]the secure storage map is empty
      [09.638]erase secure storage: 0 ok
      SUNXI_EFEX_MBR_TAG
      mbr size = 0x10000
      write primary GPT success
      write Backup GPT success
      [09.655]update partition map
      FEX_CMD_fes_verify_status
      FEX_CMD_fes_verify last err=0
      ******Has init
      FEX_CMD_fes_verify_value, start 0x8000, size high 0x0:low 0x14000
      FEX_CMD_fes_verify_value 0xe6f75b5c
      FEX_CMD_fes_verify_value, start 0x81f8, size high 0x0:low 0x20000
      FEX_CMD_fes_verify_value 0x882de1bc
      FEX_CMD_fes_verify_value, start 0x83f0, size high 0x0:low 0x20000
      FEX_CMD_fes_verify_value 0x882de1bc
      FEX_CMD_fes_verify_value, start 0x85e8, size high 0x0:low 0x5fc000
      FEX_CMD_fes_verify_value 0xd668265a
      

      也有卡79%的

      [09.584]erase all part start
      need erase flash: 18
      [09.590][mmc]: erase from: 0, to: 7634943, cnt: 7634944, erase_group: 1024
      [09.606][mmc]: sunxi_mmc_do_send_cmd_common: cmd 38 wait rsp busy 0xa ms 
      [09.613]read item0 copy0
      [09.615]Item0 (Map) magic is bad
      [09.618]the secure storage item0 copy0 magic is bad
      [09.623]Item0 (Map) magic is bad
      [09.626]the secure storage item0 copy1 magic is bad
      [09.630]Item0 (Map) magic is bad
      [09.633]the secure storage map is empty
      [09.638]erase secure storage: 0 ok
      SUNXI_EFEX_MBR_TAG
      mbr size = 0x10000
      write primary GPT success
      write Backup GPT success
      [09.655]update partition map
      FEX_CMD_fes_verify_status
      FEX_CMD_fes_verify last err=0
      ******Has init
      FEX_CMD_fes_verify_value, start 0x8000, size high 0x0:low 0x14000
      FEX_CMD_fes_verify_value 0xe6f75b5c
      FEX_CMD_fes_verify_value, start 0x81f8, size high 0x0:low 0x20000
      FEX_CMD_fes_verify_value 0x882de1bc
      FEX_CMD_fes_verify_value, start 0x83f0, size high 0x0:low 0x20000
      FEX_CMD_fes_verify_value 0x882de1bc
      FEX_CMD_fes_verify_value, start 0x85e8, size high 0x0:low 0x5fc000
      FEX_CMD_fes_verify_value 0xd668265a
      
      发布在 MR Series
      C
      casojie
    • 回复: 哪吒开发板D1编译报错Cannot find lib ld-linux-riscv64-lp64.so.1

      @whycan 抱歉,我在论坛和资料网站上没有找到相关的芯片区别表,F133就是D1-S是吗,F133还区分F133-A/B我是F133B
      而且D1-H和D1-S(F133A/B)都是公用一份SDK的话,如果我想编译F133B
      1. d1-h_nezha_min-tina
      2. d1-h_nezha-tina
      3. d1s_nezha-tina
      下面我就该选择3是吗 SDK上我不用区分A与B吗?

      发布在 MR Series
      C
      casojie
    • 回复: 哪吒开发板D1编译报错Cannot find lib ld-linux-riscv64-lp64.so.1

      @xiaowenge 现在项目是用F133做,然后给了我D1的开发板熟悉下,这两款芯片有什么区别吗?SDK能通用吗?F133的SDK只能从FTP拉取吗?

      发布在 MR Series
      C
      casojie
    • 回复: 哪吒开发板D1编译报错Cannot find lib ld-linux-riscv64-lp64.so.1

      @yuzukitsuru 怎么都是D1-H或者是D1-S,我的是D1开发板,没有后缀型号。。。怎么在分类里也找不到D1的分类的呢

      发布在 MR Series
      C
      casojie
    • 回复: 哪吒开发板D1编译报错Cannot find lib ld-linux-riscv64-lp64.so.1

      @xiaowenge 是的,现在在重新拉官网推荐的repo说的那个,尝试中

      发布在 MR Series
      C
      casojie
    • 回复: 哪吒开发板D1编译报错Cannot find lib ld-linux-riscv64-lp64.so.1

      @mangogeek 这个我也百度到了,但是不明白其意思,不勾选这个,是指哪里不勾选呢

      发布在 MR Series
      C
      casojie
    • 回复: 哪吒开发板D1编译报错Cannot find lib ld-linux-riscv64-lp64.so.1

      @yuzukitsuru 好的,我尝试下,谢谢

      发布在 MR Series
      C
      casojie
    • 哪吒开发板D1编译报错Cannot find lib ld-linux-riscv64-lp64.so.1

      没有经过什么特殊操作
      从官方ftp服务器下载的代码

      -rwxr-xr-x  1 root root 1073741824 7月   5 18:06 f133-v0.8-log-2632def.tar.gzaa
      -rwxr-xr-x  1 root root 1073741824 7月   5 18:06 f133-v0.8-log-2632def.tar.gzab
      -rwxr-xr-x  1 root root 1073741824 7月   5 18:07 f133-v0.8-log-2632def.tar.gzac
      -rwxr-xr-x  1 root root 1073741824 7月   5 18:07 f133-v0.8-log-2632def.tar.gzad
      -rwxr-xr-x  1 root root 1073741824 7月   5 18:07 f133-v0.8-log-2632def.tar.gzae
      -rwxr-xr-x  1 root root 1073741824 7月   5 18:07 f133-v0.8-log-2632def.tar.gzaf
      -rwxr-xr-x  1 root root 1073741824 7月   5 18:07 f133-v0.8-log-2632def.tar.gzag
      -rwxr-xr-x  1 root root  109289472 7月   5 18:07 f133-v0.8-log-2632def.tar.gzah```
      按要求解压后git restore
      接着就是source,lunch,最后就是make,make报错
      也考虑过缺失某些依赖,也安装了sudo apt-get install gcc-riscv64-linux-gnu
      但其实实际上,在对应的目录中存在ld-linux-riscv64-lp64.so.1
      
      ./out/f133-evb1/staging_dir/target/rootfs/lib/ld-linux-riscv64-lp64.so.1
      ./out/f133-evb1/compile_dir/target/rootfs/lib/ld-linux-riscv64-lp64.so.1
      ./out/f133-evb1/compile_dir/target/toolchain/ipkg-sunxi/libc/lib/ld-linux-riscv64-lp64.so.1
      help me!Thank !
      [1.114-temp_2022-07-05_19-17-46.log](/assets/uploads/files/1657020012733-1.114-temp_2022-07-05_19-17-46.log)
      
      发布在 MR Series
      C
      casojie
    • 1 / 1