0 Replies Latest reply on Aug 4, 2016 7:56 PM by ctan94x_intel

    Deployment of MI3.1 OS image to eMMC on Quark takes too long (~1 hour)

    ctan94x_intel

      Issue description

       

      We are trying to deploy MI3.1 image to eMMC on our Quark-based device by the following steps:

       

      1. Create USB with MI3.1 image:

      # sudo ./deploytool -f export/intel-quark-idp-idp-dist.tar.bz2 -y -u -F -d /dev/sde

      2. Plug above USB into the device and boot into Wind River IDP OS. Then execute the following command to install the OS into the eMMC:

      # tgt=/dev/mmcblk0 /sbin/reset_media

       

      But the deployment took so long, about 1 hour. The same deployment steps in MI2.0 didn't take that long.

       

      Config.log

      /home/ust/WindRiver/wrlinux-7/wrlinux/configure --enable-reconfig --enable-addons=wr-idp --enable-board=intel-quark --enable-bootimage=ext3,hdd --enable-internet-download=yes --enable-kernel=idp --enable-patchresolve=noop --enable-rootfs=idp --enable-test=no --with-layer=wr-exegin-zigbee-ia,wr-hac-agent,wr-kernel/kernel-dev,wr-ma,wr-mcafee,wr-prosyst-mbs-smarthome-sdk-ia,wr-wks-oneagent-oma-dm-ia,wr-wks-oneagent-tr069 --with-package=autoconf,automake,conntrack-tools,curl,fuse,gdb,git,iasl,igmpproxy,iperf,ipset,less,libcli,libtool,make,mipv6-daemon-umip,netcat,ntfs-3g,ntfsprogs,perl,ruby,screen,sshfs-fuse,subversion,swig,tcpdump,tftp-hpa,tftp-hpa-server,vim --with-template=feature/backports,feature/bluetooth,feature/haccmds,feature/ipsec_vpn,feature/non-grsec,feature/odm/aiot-x1000,feature/odm/cse-e100,feature/odm/ecs-gen2,feature/odm/kbox-a201,feature/odm/reliagate,feature/online_updates,feature/openjdk-bin,feature/pptp_vpn,feature/recovery,feature/self-hosted,feature/target-toolchain,feature/vlan --with-rcpl-version=0016

       

       

      Solution

      A fix has been checked into RCPL 18. It will be available around September 2016 time frame.