How to read string as hex number in bash?












3















I have the bash line:



expr substr $SUPERBLOCK 64 8


Which is return to me string line:



00080000


I know that this is, actually, a 0x00080000 in little-endian. Is there a way to create integer-variable from it in bash in big-endian like 0x80000?






bash numeric-data hex expr







share|improve this question





























    3















    I have the bash line:



    expr substr $SUPERBLOCK 64 8


    Which is return to me string line:



    00080000


    I know that this is, actually, a 0x00080000 in little-endian. Is there a way to create integer-variable from it in bash in big-endian like 0x80000?






    bash numeric-data hex expr







    share|improve this question



























      3












      3








      3








      I have the bash line:



      expr substr $SUPERBLOCK 64 8


      Which is return to me string line:



      00080000


      I know that this is, actually, a 0x00080000 in little-endian. Is there a way to create integer-variable from it in bash in big-endian like 0x80000?






      bash numeric-data hex expr







      share|improve this question
















      I have the bash line:



      expr substr $SUPERBLOCK 64 8


      Which is return to me string line:



      00080000


      I know that this is, actually, a 0x00080000 in little-endian. Is there a way to create integer-variable from it in bash in big-endian like 0x80000?






      bash numeric-data hex expr




      bash numeric-data hex expr






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited 4 hours ago









      Jesse_b

      13.7k23471




      13.7k23471










      asked 5 hours ago









      DenisNovacDenisNovac

      186




      186






















          2 Answers
          2






          active

          oldest

          votes


















          4














          Probably a better way to do this but I've come up with this solution which converts the number to decimal and then back to hex (and manually adds the 0x):



          printf '0x%xn' "$((16#00080000))"


          Which you could write as:



          printf '0x%xn' "$((16#$(expr substr "$SUPERBLOCK" 64 8)))"





          share|improve this answer
























          • Thank you! I actually added |rev inside to convert to big-endian: printf "$((16#$(expr substr $SUPERBLOCK 64 8|rev)))"

            – DenisNovac
            4 hours ago








          • 5





            @DenisNovac I'm not sure if you use big/little endian correctly (maybe you have something else on mind, but I'm doing some assembly programming for fun, so for me endianness is per bytes), but 0x12345678 is in other endianness 0x78563412, not 0x87654321. (and the value in your question 00080000 is after byte swap 00000800, i.e. 2048 decimal)

            – Ped7g
            4 hours ago













          • Oh, you are right. I just got the right answer by wrong way. I am rewriting some code from python to bash, so i know all answers before i got them.

            – DenisNovac
            4 hours ago











          • @DenisNovac: You didn't have the right answer FYI. 0x8000 was originally in your question which is not the same as 0x80000 or 0x00080000

            – Jesse_b
            4 hours ago













          • Yes, but i needed to get exactly 0x8000, so i've made mistake somewhere before. This is offset or something.

            – DenisNovac
            4 hours ago



















          0














          There are two more or less standard (and ancient) command-line unix tools that offer very easy ways to convert numbers between different bases:



          $ { echo '16'; echo i; echo 00080000; echo p; } | dc
          
524288
          
$ { echo 'ibase=16'; echo 00080000; } | bc  
          
524288


          For normal human use I very much prefer bc, but when writing a program that generates code, especially from a parser of some sort, a stack-based tool like dc may be easier to deal with (and indeed the original version of bc was a front-end parser for dc).






          share|improve this answer























            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%2f507044%2fhow-to-read-string-as-hex-number-in-bash%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            2 Answers
            2






            active

            oldest

            votes








            2 Answers
            2






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            4














            Probably a better way to do this but I've come up with this solution which converts the number to decimal and then back to hex (and manually adds the 0x):



            printf '0x%xn' "$((16#00080000))"


            Which you could write as:



            printf '0x%xn' "$((16#$(expr substr "$SUPERBLOCK" 64 8)))"





            share|improve this answer
























            • Thank you! I actually added |rev inside to convert to big-endian: printf "$((16#$(expr substr $SUPERBLOCK 64 8|rev)))"

              – DenisNovac
              4 hours ago








            • 5





              @DenisNovac I'm not sure if you use big/little endian correctly (maybe you have something else on mind, but I'm doing some assembly programming for fun, so for me endianness is per bytes), but 0x12345678 is in other endianness 0x78563412, not 0x87654321. (and the value in your question 00080000 is after byte swap 00000800, i.e. 2048 decimal)

              – Ped7g
              4 hours ago













            • Oh, you are right. I just got the right answer by wrong way. I am rewriting some code from python to bash, so i know all answers before i got them.

              – DenisNovac
              4 hours ago











            • @DenisNovac: You didn't have the right answer FYI. 0x8000 was originally in your question which is not the same as 0x80000 or 0x00080000

              – Jesse_b
              4 hours ago













            • Yes, but i needed to get exactly 0x8000, so i've made mistake somewhere before. This is offset or something.

              – DenisNovac
              4 hours ago
















            4














            Probably a better way to do this but I've come up with this solution which converts the number to decimal and then back to hex (and manually adds the 0x):



            printf '0x%xn' "$((16#00080000))"


            Which you could write as:



            printf '0x%xn' "$((16#$(expr substr "$SUPERBLOCK" 64 8)))"





            share|improve this answer
























            • Thank you! I actually added |rev inside to convert to big-endian: printf "$((16#$(expr substr $SUPERBLOCK 64 8|rev)))"

              – DenisNovac
              4 hours ago








            • 5





              @DenisNovac I'm not sure if you use big/little endian correctly (maybe you have something else on mind, but I'm doing some assembly programming for fun, so for me endianness is per bytes), but 0x12345678 is in other endianness 0x78563412, not 0x87654321. (and the value in your question 00080000 is after byte swap 00000800, i.e. 2048 decimal)

              – Ped7g
              4 hours ago













            • Oh, you are right. I just got the right answer by wrong way. I am rewriting some code from python to bash, so i know all answers before i got them.

              – DenisNovac
              4 hours ago











            • @DenisNovac: You didn't have the right answer FYI. 0x8000 was originally in your question which is not the same as 0x80000 or 0x00080000

              – Jesse_b
              4 hours ago













            • Yes, but i needed to get exactly 0x8000, so i've made mistake somewhere before. This is offset or something.

              – DenisNovac
              4 hours ago














            4












            4








            4







            Probably a better way to do this but I've come up with this solution which converts the number to decimal and then back to hex (and manually adds the 0x):



            printf '0x%xn' "$((16#00080000))"


            Which you could write as:



            printf '0x%xn' "$((16#$(expr substr "$SUPERBLOCK" 64 8)))"





            share|improve this answer













            Probably a better way to do this but I've come up with this solution which converts the number to decimal and then back to hex (and manually adds the 0x):



            printf '0x%xn' "$((16#00080000))"


            Which you could write as:



            printf '0x%xn' "$((16#$(expr substr "$SUPERBLOCK" 64 8)))"






            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered 4 hours ago









            Jesse_bJesse_b

            13.7k23471




            13.7k23471













            • Thank you! I actually added |rev inside to convert to big-endian: printf "$((16#$(expr substr $SUPERBLOCK 64 8|rev)))"

              – DenisNovac
              4 hours ago








            • 5





              @DenisNovac I'm not sure if you use big/little endian correctly (maybe you have something else on mind, but I'm doing some assembly programming for fun, so for me endianness is per bytes), but 0x12345678 is in other endianness 0x78563412, not 0x87654321. (and the value in your question 00080000 is after byte swap 00000800, i.e. 2048 decimal)

              – Ped7g
              4 hours ago













            • Oh, you are right. I just got the right answer by wrong way. I am rewriting some code from python to bash, so i know all answers before i got them.

              – DenisNovac
              4 hours ago











            • @DenisNovac: You didn't have the right answer FYI. 0x8000 was originally in your question which is not the same as 0x80000 or 0x00080000

              – Jesse_b
              4 hours ago













            • Yes, but i needed to get exactly 0x8000, so i've made mistake somewhere before. This is offset or something.

              – DenisNovac
              4 hours ago



















            • Thank you! I actually added |rev inside to convert to big-endian: printf "$((16#$(expr substr $SUPERBLOCK 64 8|rev)))"

              – DenisNovac
              4 hours ago








            • 5





              @DenisNovac I'm not sure if you use big/little endian correctly (maybe you have something else on mind, but I'm doing some assembly programming for fun, so for me endianness is per bytes), but 0x12345678 is in other endianness 0x78563412, not 0x87654321. (and the value in your question 00080000 is after byte swap 00000800, i.e. 2048 decimal)

              – Ped7g
              4 hours ago













            • Oh, you are right. I just got the right answer by wrong way. I am rewriting some code from python to bash, so i know all answers before i got them.

              – DenisNovac
              4 hours ago











            • @DenisNovac: You didn't have the right answer FYI. 0x8000 was originally in your question which is not the same as 0x80000 or 0x00080000

              – Jesse_b
              4 hours ago













            • Yes, but i needed to get exactly 0x8000, so i've made mistake somewhere before. This is offset or something.

              – DenisNovac
              4 hours ago

















            Thank you! I actually added |rev inside to convert to big-endian: printf "$((16#$(expr substr $SUPERBLOCK 64 8|rev)))"

            – DenisNovac
            4 hours ago







            Thank you! I actually added |rev inside to convert to big-endian: printf "$((16#$(expr substr $SUPERBLOCK 64 8|rev)))"

            – DenisNovac
            4 hours ago






            5




            5





            @DenisNovac I'm not sure if you use big/little endian correctly (maybe you have something else on mind, but I'm doing some assembly programming for fun, so for me endianness is per bytes), but 0x12345678 is in other endianness 0x78563412, not 0x87654321. (and the value in your question 00080000 is after byte swap 00000800, i.e. 2048 decimal)

            – Ped7g
            4 hours ago







            @DenisNovac I'm not sure if you use big/little endian correctly (maybe you have something else on mind, but I'm doing some assembly programming for fun, so for me endianness is per bytes), but 0x12345678 is in other endianness 0x78563412, not 0x87654321. (and the value in your question 00080000 is after byte swap 00000800, i.e. 2048 decimal)

            – Ped7g
            4 hours ago















            Oh, you are right. I just got the right answer by wrong way. I am rewriting some code from python to bash, so i know all answers before i got them.

            – DenisNovac
            4 hours ago





            Oh, you are right. I just got the right answer by wrong way. I am rewriting some code from python to bash, so i know all answers before i got them.

            – DenisNovac
            4 hours ago













            @DenisNovac: You didn't have the right answer FYI. 0x8000 was originally in your question which is not the same as 0x80000 or 0x00080000

            – Jesse_b
            4 hours ago







            @DenisNovac: You didn't have the right answer FYI. 0x8000 was originally in your question which is not the same as 0x80000 or 0x00080000

            – Jesse_b
            4 hours ago















            Yes, but i needed to get exactly 0x8000, so i've made mistake somewhere before. This is offset or something.

            – DenisNovac
            4 hours ago





            Yes, but i needed to get exactly 0x8000, so i've made mistake somewhere before. This is offset or something.

            – DenisNovac
            4 hours ago













            0














            There are two more or less standard (and ancient) command-line unix tools that offer very easy ways to convert numbers between different bases:



            $ { echo '16'; echo i; echo 00080000; echo p; } | dc
            
524288
            
$ { echo 'ibase=16'; echo 00080000; } | bc  
            
524288


            For normal human use I very much prefer bc, but when writing a program that generates code, especially from a parser of some sort, a stack-based tool like dc may be easier to deal with (and indeed the original version of bc was a front-end parser for dc).






            share|improve this answer




























              0














              There are two more or less standard (and ancient) command-line unix tools that offer very easy ways to convert numbers between different bases:



              $ { echo '16'; echo i; echo 00080000; echo p; } | dc
              
524288
              
$ { echo 'ibase=16'; echo 00080000; } | bc  
              
524288


              For normal human use I very much prefer bc, but when writing a program that generates code, especially from a parser of some sort, a stack-based tool like dc may be easier to deal with (and indeed the original version of bc was a front-end parser for dc).






              share|improve this answer


























                0












                0








                0







                There are two more or less standard (and ancient) command-line unix tools that offer very easy ways to convert numbers between different bases:



                $ { echo '16'; echo i; echo 00080000; echo p; } | dc
                
524288
                
$ { echo 'ibase=16'; echo 00080000; } | bc  
                
524288


                For normal human use I very much prefer bc, but when writing a program that generates code, especially from a parser of some sort, a stack-based tool like dc may be easier to deal with (and indeed the original version of bc was a front-end parser for dc).






                share|improve this answer













                There are two more or less standard (and ancient) command-line unix tools that offer very easy ways to convert numbers between different bases:



                $ { echo '16'; echo i; echo 00080000; echo p; } | dc
                
524288
                
$ { echo 'ibase=16'; echo 00080000; } | bc  
                
524288


                For normal human use I very much prefer bc, but when writing a program that generates code, especially from a parser of some sort, a stack-based tool like dc may be easier to deal with (and indeed the original version of bc was a front-end parser for dc).







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered 10 mins ago









                Greg A. WoodsGreg A. Woods

                50248




                50248






























                    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%2f507044%2fhow-to-read-string-as-hex-number-in-bash%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

                    How to label and detect the document text images

                    Image
                    1 $begingroup$ This is what I mean as document text image: I want to label the texts in image as separate blocks and my model should detect these labels as classes. NOTE: This is how the end result should be like: The labels like Block 1, Block 2, Block 3,.. should be Logo, Title, Date,.. Others, etc. Work done: First approach : I tried to implement this method via Object Detection, it didn't work. It didn't even detect any text. Second approach : Then I tried it using PixelLink. As this model is build for scene text detection, it detected each and every text in the image. But this method can detect multiple lines of text if the threshold values are increased. But I have no idea how do I add labels to the text blocks. PIXEL_CLS_WEIGHT_all_ones = 'PIXEL_CLS_WEIGHT_all_ones' PIXEL_C...
                    Read more

                    Vallis Paradisi

                    Image
                    Coordinata: .mw-parser-output .geo-default,.mw-parser-output .geo-dms,.mw-parser-output .geo-dec{display:inline}.mw-parser-output .geo-nondefault,.mw-parser-output .geo-multi-punct{display:none}.mw-parser-output .longitude,.mw-parser-output .latitude{white-space:nowrap} 33°03′S 71°37′W  /  33.05°S 71.617°W  / -33.05; -71.617 Vallis Paradisi Res apud Vicidata repertae: Civitas : Chilia Numerus incolarum : 296 655 Zona horaria : UTC-4 Situs interretialis Nomen officiale : Valparaíso Gubernium Consilium : municipal council of Valparaíso Geographia Superficies : 401 600 000 Metrum quadratum Coniunctiones urbium Urbes gemellae : Ovetum , Badalona , Santa Fe , Ora longa , Sciamhaevum , Quantunia , Callao , Bat Yam , Melaka , Novorossiysk , Busan , Corduba , Odessa , Rosario , Malacca , Barcino , Soteropolis , Franciscopolis (California) , Guanajuato, Silao Tabula aut despectus Despectus in portum sinumque et urbem Vallis Paradisi Vallis Para...
                    Read more

                    Tabula Rosettana

                    Image
                    Tabula multilinguis Rosettana in Museo Britannico ostenditur. Tabula Rosettana, [1] etiam titulo OGIS 90 agnita, est stela decreto de rebus sacris in Aegypto anno 196 a.C.n. lato inscripta. Tabula iuxta Rosettam Aegypti, urbem in delta Nili et ad oram maris Mediterranei iacentem, anno 1799 a milite Francico reperta est. Inventio stelae, linguis duabus scripturisque tribus inscriptae, eruditis Instituti Aegypti statim nuntiata est; ibi enim iussu imperatoris Napoleonis eruditi omnium scientiarum (sub aegide Commissionis Scientiarum et Artium) properaverant cum expeditione Francica. Qua a Britannis mox debellata, tabula Rosettana Londinium missa hodie apud Museum Britannicum iacet. Textus Graecus cito lectus interpretationi textuum Aegyptiorum (in formis hieroglyphica et demotica expressorum) gradatim adiuvit. Denique textum plene interpretatus est Ioannes Franciscus Champollion. Ab opere eruditorum cumulativo coepit hodiernus scripturae hieroglyphicae linguaeque Aegyptiae a...
                    Read more