Handle booting failure for u boot ( Debian )












0















I am working on OTA Update for a device.



I have an sd card with 3 Partitions. mmcblk0 is the disk and mmcblk0p1, mmcblk0p2 ,mmcblk0p3 are the 3 partitions.



Partition mmcblk0p1 has a uboot configuration ( uEnv.txt and other files required for booting ). Partitions mmcblk0p2 and mmcblk0p3 have a Debian OS.



Partition mmcblk0p2 and mmcblk0p3 are used as an active and inactive partition. When an update comes it is downloaded and installed to the inactive partition. Once it completes user reboots the device and the user is booted into the last inactive partition ( The partition on which update is performed )



I am using uEnv.txt to change the boot configuration i.e. If I want to boot from mmcblk0p2 I can give



mmcargs=setenv bootargs console=tty0 console=${console} ${optargs} ${cape_disable} ${cape_enable} root=/dev/mmcblk0p2 rootfstype=${mmcrootfstype} ${cmdline}


in the uEnv.txt



This works when the update is successful



But if uEnv.txt gets corrupt due to any failure or the partition gets corrupt then the device won't boot from either of the partitions. ( i.e. OS )



Is there any way to handle this issue? ( For example, if partition mmcblk0p3 is updated ( But it gets corrupted due to some reason ) and now it's trying to boot in that partition and fails to boot from that partition, in that case, is there any way I can boot back from mmcblk0p2 )










share|improve this question



























    0















    I am working on OTA Update for a device.



    I have an sd card with 3 Partitions. mmcblk0 is the disk and mmcblk0p1, mmcblk0p2 ,mmcblk0p3 are the 3 partitions.



    Partition mmcblk0p1 has a uboot configuration ( uEnv.txt and other files required for booting ). Partitions mmcblk0p2 and mmcblk0p3 have a Debian OS.



    Partition mmcblk0p2 and mmcblk0p3 are used as an active and inactive partition. When an update comes it is downloaded and installed to the inactive partition. Once it completes user reboots the device and the user is booted into the last inactive partition ( The partition on which update is performed )



    I am using uEnv.txt to change the boot configuration i.e. If I want to boot from mmcblk0p2 I can give



    mmcargs=setenv bootargs console=tty0 console=${console} ${optargs} ${cape_disable} ${cape_enable} root=/dev/mmcblk0p2 rootfstype=${mmcrootfstype} ${cmdline}


    in the uEnv.txt



    This works when the update is successful



    But if uEnv.txt gets corrupt due to any failure or the partition gets corrupt then the device won't boot from either of the partitions. ( i.e. OS )



    Is there any way to handle this issue? ( For example, if partition mmcblk0p3 is updated ( But it gets corrupted due to some reason ) and now it's trying to boot in that partition and fails to boot from that partition, in that case, is there any way I can boot back from mmcblk0p2 )










    share|improve this question

























      0












      0








      0








      I am working on OTA Update for a device.



      I have an sd card with 3 Partitions. mmcblk0 is the disk and mmcblk0p1, mmcblk0p2 ,mmcblk0p3 are the 3 partitions.



      Partition mmcblk0p1 has a uboot configuration ( uEnv.txt and other files required for booting ). Partitions mmcblk0p2 and mmcblk0p3 have a Debian OS.



      Partition mmcblk0p2 and mmcblk0p3 are used as an active and inactive partition. When an update comes it is downloaded and installed to the inactive partition. Once it completes user reboots the device and the user is booted into the last inactive partition ( The partition on which update is performed )



      I am using uEnv.txt to change the boot configuration i.e. If I want to boot from mmcblk0p2 I can give



      mmcargs=setenv bootargs console=tty0 console=${console} ${optargs} ${cape_disable} ${cape_enable} root=/dev/mmcblk0p2 rootfstype=${mmcrootfstype} ${cmdline}


      in the uEnv.txt



      This works when the update is successful



      But if uEnv.txt gets corrupt due to any failure or the partition gets corrupt then the device won't boot from either of the partitions. ( i.e. OS )



      Is there any way to handle this issue? ( For example, if partition mmcblk0p3 is updated ( But it gets corrupted due to some reason ) and now it's trying to boot in that partition and fails to boot from that partition, in that case, is there any way I can boot back from mmcblk0p2 )










      share|improve this question














      I am working on OTA Update for a device.



      I have an sd card with 3 Partitions. mmcblk0 is the disk and mmcblk0p1, mmcblk0p2 ,mmcblk0p3 are the 3 partitions.



      Partition mmcblk0p1 has a uboot configuration ( uEnv.txt and other files required for booting ). Partitions mmcblk0p2 and mmcblk0p3 have a Debian OS.



      Partition mmcblk0p2 and mmcblk0p3 are used as an active and inactive partition. When an update comes it is downloaded and installed to the inactive partition. Once it completes user reboots the device and the user is booted into the last inactive partition ( The partition on which update is performed )



      I am using uEnv.txt to change the boot configuration i.e. If I want to boot from mmcblk0p2 I can give



      mmcargs=setenv bootargs console=tty0 console=${console} ${optargs} ${cape_disable} ${cape_enable} root=/dev/mmcblk0p2 rootfstype=${mmcrootfstype} ${cmdline}


      in the uEnv.txt



      This works when the update is successful



      But if uEnv.txt gets corrupt due to any failure or the partition gets corrupt then the device won't boot from either of the partitions. ( i.e. OS )



      Is there any way to handle this issue? ( For example, if partition mmcblk0p3 is updated ( But it gets corrupted due to some reason ) and now it's trying to boot in that partition and fails to boot from that partition, in that case, is there any way I can boot back from mmcblk0p2 )







      debian boot partition dual-boot u-boot






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked 10 mins ago









      Sharvin ShahSharvin Shah

      12




      12






















          0






          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',
          autoActivateHeartbeat: false,
          convertImagesToLinks: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          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%2f505792%2fhandle-booting-failure-for-u-boot-debian%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Unix & Linux Stack Exchange!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f505792%2fhandle-booting-failure-for-u-boot-debian%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Accessing regular linux commands in Huawei's Dopra Linux

          Can't connect RFCOMM socket: Host is down

          Kernel panic - not syncing: Fatal Exception in Interrupt