u-boot booting problem: IMAGE_FORMAT_INVALID insiede FIT flat device tree

Multi tool use
Multi tool use

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
0
down vote

favorite












I'm trying to boot a kernel starting from a FIT image and using the bootm command and I have the following issue. This is the last part of the FIT image configuration where are specified kernel node name and also fdt node name



conf@1 
description = "Boot Linux kernel with FDT blob";
kernel = "kernel@1";
fdt= "fdt@1";
;


if I extract image (e.g. imxtract 83000000 fdt@1 81000000 imxtract 83000000 kernel@1 82000000) and then run "bootm 82000000 - 81000000" the kernel starts



then if I run directly "bootm 83000000#conf@1" it starts because the image is a FIT image.



BUT if I try "bootm 83000000:kernel@1 - 83000000:fdt@1" then noting is working because the image that is read has a format invalid (value zero = IMAGE_FORMAT_INVALID)



I don't understand why using the format with ":" the format read is invalid. This mode of boot is explained in /u-boot/doc/uImage.FIT/command_syntax_extensions.txt



This problem can be linked with the fact that I'm using a zImage for the kernel? Thanks







share|improve this question
























    up vote
    0
    down vote

    favorite












    I'm trying to boot a kernel starting from a FIT image and using the bootm command and I have the following issue. This is the last part of the FIT image configuration where are specified kernel node name and also fdt node name



    conf@1 
    description = "Boot Linux kernel with FDT blob";
    kernel = "kernel@1";
    fdt= "fdt@1";
    ;


    if I extract image (e.g. imxtract 83000000 fdt@1 81000000 imxtract 83000000 kernel@1 82000000) and then run "bootm 82000000 - 81000000" the kernel starts



    then if I run directly "bootm 83000000#conf@1" it starts because the image is a FIT image.



    BUT if I try "bootm 83000000:kernel@1 - 83000000:fdt@1" then noting is working because the image that is read has a format invalid (value zero = IMAGE_FORMAT_INVALID)



    I don't understand why using the format with ":" the format read is invalid. This mode of boot is explained in /u-boot/doc/uImage.FIT/command_syntax_extensions.txt



    This problem can be linked with the fact that I'm using a zImage for the kernel? Thanks







    share|improve this question






















      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      I'm trying to boot a kernel starting from a FIT image and using the bootm command and I have the following issue. This is the last part of the FIT image configuration where are specified kernel node name and also fdt node name



      conf@1 
      description = "Boot Linux kernel with FDT blob";
      kernel = "kernel@1";
      fdt= "fdt@1";
      ;


      if I extract image (e.g. imxtract 83000000 fdt@1 81000000 imxtract 83000000 kernel@1 82000000) and then run "bootm 82000000 - 81000000" the kernel starts



      then if I run directly "bootm 83000000#conf@1" it starts because the image is a FIT image.



      BUT if I try "bootm 83000000:kernel@1 - 83000000:fdt@1" then noting is working because the image that is read has a format invalid (value zero = IMAGE_FORMAT_INVALID)



      I don't understand why using the format with ":" the format read is invalid. This mode of boot is explained in /u-boot/doc/uImage.FIT/command_syntax_extensions.txt



      This problem can be linked with the fact that I'm using a zImage for the kernel? Thanks







      share|improve this question












      I'm trying to boot a kernel starting from a FIT image and using the bootm command and I have the following issue. This is the last part of the FIT image configuration where are specified kernel node name and also fdt node name



      conf@1 
      description = "Boot Linux kernel with FDT blob";
      kernel = "kernel@1";
      fdt= "fdt@1";
      ;


      if I extract image (e.g. imxtract 83000000 fdt@1 81000000 imxtract 83000000 kernel@1 82000000) and then run "bootm 82000000 - 81000000" the kernel starts



      then if I run directly "bootm 83000000#conf@1" it starts because the image is a FIT image.



      BUT if I try "bootm 83000000:kernel@1 - 83000000:fdt@1" then noting is working because the image that is read has a format invalid (value zero = IMAGE_FORMAT_INVALID)



      I don't understand why using the format with ":" the format read is invalid. This mode of boot is explained in /u-boot/doc/uImage.FIT/command_syntax_extensions.txt



      This problem can be linked with the fact that I'm using a zImage for the kernel? Thanks









      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 9 '17 at 16:03









      G.D.

      204




      204

























          active

          oldest

          votes











          Your Answer







          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "106"
          ;
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function()
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled)
          StackExchange.using("snippets", function()
          createEditor();
          );

          else
          createEditor();

          );

          function createEditor()
          StackExchange.prepareEditor(
          heartbeatType: 'answer',
          convertImagesToLinks: false,
          noModals: false,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );













           

          draft saved


          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f403550%2fu-boot-booting-problem-image-format-invalid-insiede-fit-flat-device-tree%23new-answer', 'question_page');

          );

          Post as a guest



































          active

          oldest

          votes













          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes















           

          draft saved


          draft discarded















































           


          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f403550%2fu-boot-booting-problem-image-format-invalid-insiede-fit-flat-device-tree%23new-answer', 'question_page');

          );

          Post as a guest













































































          t3M RQF0BFYktEh5s5BY
          DSX7FaFVMRgovS2SRRz,l m733j CtQ6Eh,37lr2C aP

          Popular posts from this blog

          How to check contact read email or not when send email to Individual?

          How many registers does an x86_64 CPU actually have?

          Displaying single band from multi-band raster using QGIS