Navigation

    全志在线开发者论坛

    • Register
    • Login
    • Search
    • Categories
    • Tags
    • 在线文档
    • 社区主页
    1. Home
    2. a1314258
    A
    • Profile
    • Following 0
    • Followers 0
    • my integral 297
    • Topics 1
    • Posts 8
    • Best 0
    • Groups 0

    a1314258LV 3

    @a1314258

    297
    integral
    0
    Reputation
    1
    Profile views
    8
    Posts
    0
    Followers
    0
    Following
    Joined Last Online

    a1314258 Unfollow Follow

    Latest posts made by a1314258

    • Reply: 全志SecureBoot无法正常启用

      @a1314258
      同样的方法使用在r329的key_burn.c
      编译成功了,无语

      posted in 其它全志芯片讨论区
      A
      a1314258
    • Reply: 全志SecureBoot无法正常启用

      @mengxp 在 全志SecureBoot无法正常启用 中说:

      efuse_read

      请教一下,我是这样在key_burn.c加的

      #include <common.h>
      #include <command.h>
      #include <sys_config.h>
      #include <securestorage.h>
      #include <private_uboot.h>
      #include <smc.h>
      #include <efuse_map.h>
      #include <sunxi_board.h>
      
      int do_efuse_read(cmd_tbl_t *cmdtp, int flag, int argc, char * const argv[])
      {
      	char *efuse_name;
      	char buffer[32];
      	int  ret;
      
      	if(argc != 2)
      	{
      		printf("the efuse item name is empty\n");
      
      		return -1;
      	}
      	efuse_name = argv[1];
      	printf("try to read %s\n", efuse_name);
      	memset(buffer, 0, 32);
      	//change
      	//printf("buffer addr=0x%x\n", (u32)buffer);
      	printf("buffer addr=0x\n");
      	ret = arm_svc_efuse_read(efuse_name, buffer);
      	if(ret)
      	{
      		printf("read efuse key [%s] failed\n", efuse_name);
      	}
      	else
      	{
      		printf("read efuse key [%s] successed\n", efuse_name);
      		sunxi_dump(buffer, 32);
      	}
      
      	return 0;
      }
      
      U_BOOT_CMD(
      	efuse_read, 3, 0, do_efuse_read,
      	"read efuse key",
      	"usage: efuse_read efusename"
      );
      

      muboot 编译失败了。

      ./../tools/toolchain/riscv64-linux-x86_64-20200528/bin/riscv64-unknown-linux-gnu-ld.bfd: board/sunxi/built-in.o: in function `do_efuse_read':
      /home/user/tina-d1-h/lichee/brandy-2.0/u-boot-2018/board/sunxi/key_burn.c:96: undefined reference to `arm_svc_efuse_read'
      Makefile:1480: recipe for target 'u-boot' failed
      make: *** [u-boot] Error 1
      muboot stop for build error in brandy, Please check!
      
      
      posted in 其它全志芯片讨论区
      A
      a1314258
    • Reply: 因为喜欢用ADB,因为不喜欢插拔TF卡,所以D1直接用PhoenixSuit烧录TF(SDNAND)

      @tevet

      [37.465]workmode = 16,storage type = 0
      try card 0
      set card number 0
      get card number 0
      [37.473][mmc]: mmc driver ver uboot2018:2021-11-19 15:38:00
      [37.481][mmc]: get sdc_type fail and use default host:tm1.
      [37.507][mmc]: can't find node "mmc0",will add new node
      [37.512][mmc]: fdt err returned <no error>
      [37.516][mmc]: Using default timing para
      [37.519][mmc]: SUNXI SDMMC Controller Version:0x50310
      [37.537][mmc]: card_caps:0x3000000a
      [37.540][mmc]: host_caps:0x3000003f
      [37.548]Loading Environment from SUNXI_FLASH... OK
      [37.559]try to burn key
      [37.562]out of usb burn from boot: not need burn key
      [37.566]Net:   [37.568]No ethernet found.
      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 0x1d
      set address 0x1d ok
      

      卡在 set address 0x1d ok 这里就不动了。

      posted in D1系列-RISC-V
      A
      a1314258
    • Reply: d1-h的安全启动固件打包失败

      @yuzukitsuru
      tina_d1-h-nezha_uart0.img 用 PhoenixCard 成功

      tina_d1-h-nezha_uart0_secure_v0.img 失败了,reset之后串口什么都没显示 😖

      posted in 编译和烧写问题专区
      A
      a1314258
    • Reply: d1-h的安全启动固件打包失败

      @yuzukitsuru
      再送佛送到西吧。怎么把这种固件写到的d1的sd卡里面?尝试了 因为喜欢用ADB,因为不喜欢插拔TF卡,所以D1直接用PhoenixSuit烧录TF(SDNAND) 没有成功

      posted in 编译和烧写问题专区
      A
      a1314258
    • Reply: d1-h的安全启动固件打包失败

      @yuzukitsuru
      works like a charm.
      Danke

      posted in 编译和烧写问题专区
      A
      a1314258
    • Reply: 请问 根据这个文档 D1_Tina_Linux_安全_开发指南.pdf,为什么不能编译出 sboot?

      请问解决了吗?我也想试一下d1的安全启动。

      posted in D1系列-RISC-V
      A
      a1314258
    • d1-h的安全启动固件打包失败

      打包普通的可以,pack -s失败。

      sboot bin=/home/user/tina-d1-h/out/d1-h-nezha/image/sboot.bin
      file /home/user/tina-d1-h/out/d1-h-nezha/image/sboot.bin cant be open to calc hash
      dragoncreate_toc0_certif err in calchash
      create cert failed
      ERROR: dragon toc0 run error
      

      并没有发现有sboot.bin文件。

      posted in 编译和烧写问题专区
      A
      a1314258