1 Reply Latest reply on Jan 15, 2016 7:39 PM by tushar panda

    unable to read file boot.scr

    almarto

      Dear all,

      I am able to bitbake a core-image-sato with yocto 1.8 for my riotboard and I am able to copy it to an sd card and connect normally with the terminal.

      However, I can not make the video output work for the HDMI.

      I have tested SVN_3000 image and it works perfectly and I can visualize the graphical environment in my monitor, so that I guess that hardware is ok!

      I have modified u-boot by setting:

      bootargs=console=ttymxc1,115200 nosmp video=mxcfb0:dev=hdmi,1280x720@60m, bpp=32 video=mxcfb1:off fbmem=10M

      as it is in the SVN_3000 image, but unfortunately it does not work.

      I don't know what's going on, I just don't know if the error "Unable to read file boot.scr" has something to do with it

       

      I am stuck at this for two days now and any feedback is completely welcome.

      Thank you very much in advance!

       

      U-Boot 2015.04+fslc+g5d9ffd2 (Oct 10 2015 - 04:00:11)

       

      CPU:   Freescale i.MX6SOLO rev1.1 996 MHz (running at 792 MHz)

      CPU:   Commercial temperature grade (0C to 95C) at 43C

      Reset cause: POR

      Board: RIoTboard

      I2C:   ready

      DRAM:  1 GiB

      MMC:   FSL_SDHC: 0, FSL_SDHC: 1, FSL_SDHC: 2

      auto-detected panel HDMI

      Display: HDMI (1024x768)

      In:    serial

      Out:   serial

      Err:   serial

      Net:   FEC [PRIME]

      Error: FEC address not set.

       

      Hit any key to stop autoboot:  0

      switch to partitions #0, OK

      mmc0 is current device

      reading boot.scr

      ** Unable to read file boot.scr **

      reading zImage

      6219248 bytes read in 338 ms (17.5 MiB/s)

      Booting from mmc ...

      reading imx6dl-riotboard.dtb

      30758 bytes read in 18 ms (1.6 MiB/s)

      Kernel image @ 0x12000000 [ 0x000000 - 0x5ee5f0 ]

      ## Flattened Device Tree blob at 18000000

         Booting using the fdt blob at 0x18000000

         Using Device Tree in place at 18000000, end 1800a825

       

      Starting kernel ...