Retrieve file over serial without kermit and lrzszSerial File Transfer without lrzszno menu entry for...

Don’t seats that recline flat defeat the purpose of having seatbelts?

Israeli soda type drink

std::unique_ptr of base class holding reference of derived class does not show warning in gcc compiler while naked pointer shows it. Why?

"My boss was furious with me and I have been fired" vs. "My boss was furious with me and I was fired"

How do I reattach a shelf to the wall when it ripped out of the wall?

How to be good at coming up with counter example in Topology

Why do games have consumables?

What does "function" actually mean in music?

I preordered a game on my Xbox while on the home screen of my friend's account. Which of us owns the game?

How to pronounce 'c++' in Spanish

An array in a equation with curly braces in both sides

Check if a string is entirely made of the same substring

Which big number is bigger?

Is there metaphorical meaning of "aus der Haft entlassen"?

What was Apollo 13's "Little Jolt" after MECO?

How to not starve gigantic beasts

Could moose/elk survive in the Amazon forest?

Find the identical rows in a matrix

Older movie/show about humans on derelict alien warship which refuels by passing through a star

Why must Chinese maps be obfuscated?

Philosophical question on logistic regression: why isn't the optimal threshold value trained?

How to have a sharp product image?

Retract an already submitted recommendation letter (written for an undergrad student)

Why did Rep. Omar conclude her criticism of US troops with the phrase "NotTodaySatan"?



Retrieve file over serial without kermit and lrzsz


Serial File Transfer without lrzszno menu entry for /dev/ttyusb0 failing to uploadSerial port's modem lights up, but can't communicateWhy `minicom` append the `0xOD` character to serial text message?Transfer file to pc from embedded linux device via serial communicationsSerial File Transfer without lrzszSend a file over serial port with XMODEM protocolserial port via minicom: can minicom use line-editing (i.e. readline functionality)?Serial console using ttyS5 for EFI bootDebian not recognizing my ttyS0 / console redirection not workingSerial port program to write file/read to file from tty?






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







1















I have an embedded Linux on a custom board and I would like to send and receive file over its serial port.



The only way to communicate with this device is over serial and the device offers a console on this serial port.



This board doesn't have kermit neither busybox rx nor lrzsz.



- Sending file to remote



I was able to send file to the board following this thread.



Host side                              Remote side

cat file | base64 > file_b64
cat > file_b64
minicom's ctrlA-S => send 'file_b64'
cat file_b64 | base64 --decode > file


- Getting file from remote



Now I would like to retrieve a file from remote system.



Minicom has a tool for receiving files but as I only have the serial port's console using minicom to issue commands on remote side, I can't find how to do it.



I have tried using kermit on host side but it seems that I also needs to have kermit on the remote side.





EDIT:



I have also tried to reverse the sending method but with no success as i receive nothing from serial port on host side.



Host side                              Remote side

cat file | base64 > file_b64
(sleep 10; cat file_b64 > /dev/ttyS0) &
minicom's ctrlA-X => exit minicom
cat /dev/ttyUSB0 > file_b64


Can't use minicom's receive tool cause it only support xmodem, ymodem, zmodem and kermit tranfers and not ascii.





Is there a way to retrieve files from remote without having to type commands into its console?










share|improve this question




















  • 2





    Why don't you use the slip module to build a tcp/ip connection? tldp.org/LDP/nag2/x-087-2-slip.operation.html

    – Ipor Sircer
    Aug 3 '18 at 14:30











  • Didn't know this module, however slattach is not available on remote side

    – Arkaik
    Aug 3 '18 at 14:37


















1















I have an embedded Linux on a custom board and I would like to send and receive file over its serial port.



The only way to communicate with this device is over serial and the device offers a console on this serial port.



This board doesn't have kermit neither busybox rx nor lrzsz.



- Sending file to remote



I was able to send file to the board following this thread.



Host side                              Remote side

cat file | base64 > file_b64
cat > file_b64
minicom's ctrlA-S => send 'file_b64'
cat file_b64 | base64 --decode > file


- Getting file from remote



Now I would like to retrieve a file from remote system.



Minicom has a tool for receiving files but as I only have the serial port's console using minicom to issue commands on remote side, I can't find how to do it.



I have tried using kermit on host side but it seems that I also needs to have kermit on the remote side.





EDIT:



I have also tried to reverse the sending method but with no success as i receive nothing from serial port on host side.



Host side                              Remote side

cat file | base64 > file_b64
(sleep 10; cat file_b64 > /dev/ttyS0) &
minicom's ctrlA-X => exit minicom
cat /dev/ttyUSB0 > file_b64


Can't use minicom's receive tool cause it only support xmodem, ymodem, zmodem and kermit tranfers and not ascii.





Is there a way to retrieve files from remote without having to type commands into its console?










share|improve this question




















  • 2





    Why don't you use the slip module to build a tcp/ip connection? tldp.org/LDP/nag2/x-087-2-slip.operation.html

    – Ipor Sircer
    Aug 3 '18 at 14:30











  • Didn't know this module, however slattach is not available on remote side

    – Arkaik
    Aug 3 '18 at 14:37














1












1








1








I have an embedded Linux on a custom board and I would like to send and receive file over its serial port.



The only way to communicate with this device is over serial and the device offers a console on this serial port.



This board doesn't have kermit neither busybox rx nor lrzsz.



- Sending file to remote



I was able to send file to the board following this thread.



Host side                              Remote side

cat file | base64 > file_b64
cat > file_b64
minicom's ctrlA-S => send 'file_b64'
cat file_b64 | base64 --decode > file


- Getting file from remote



Now I would like to retrieve a file from remote system.



Minicom has a tool for receiving files but as I only have the serial port's console using minicom to issue commands on remote side, I can't find how to do it.



I have tried using kermit on host side but it seems that I also needs to have kermit on the remote side.





EDIT:



I have also tried to reverse the sending method but with no success as i receive nothing from serial port on host side.



Host side                              Remote side

cat file | base64 > file_b64
(sleep 10; cat file_b64 > /dev/ttyS0) &
minicom's ctrlA-X => exit minicom
cat /dev/ttyUSB0 > file_b64


Can't use minicom's receive tool cause it only support xmodem, ymodem, zmodem and kermit tranfers and not ascii.





Is there a way to retrieve files from remote without having to type commands into its console?










share|improve this question
















I have an embedded Linux on a custom board and I would like to send and receive file over its serial port.



The only way to communicate with this device is over serial and the device offers a console on this serial port.



This board doesn't have kermit neither busybox rx nor lrzsz.



- Sending file to remote



I was able to send file to the board following this thread.



Host side                              Remote side

cat file | base64 > file_b64
cat > file_b64
minicom's ctrlA-S => send 'file_b64'
cat file_b64 | base64 --decode > file


- Getting file from remote



Now I would like to retrieve a file from remote system.



Minicom has a tool for receiving files but as I only have the serial port's console using minicom to issue commands on remote side, I can't find how to do it.



I have tried using kermit on host side but it seems that I also needs to have kermit on the remote side.





EDIT:



I have also tried to reverse the sending method but with no success as i receive nothing from serial port on host side.



Host side                              Remote side

cat file | base64 > file_b64
(sleep 10; cat file_b64 > /dev/ttyS0) &
minicom's ctrlA-X => exit minicom
cat /dev/ttyUSB0 > file_b64


Can't use minicom's receive tool cause it only support xmodem, ymodem, zmodem and kermit tranfers and not ascii.





Is there a way to retrieve files from remote without having to type commands into its console?







serial-port file-transfer serial-console minicom uart






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Aug 3 '18 at 15:14







Arkaik

















asked Aug 3 '18 at 14:25









ArkaikArkaik

408422




408422








  • 2





    Why don't you use the slip module to build a tcp/ip connection? tldp.org/LDP/nag2/x-087-2-slip.operation.html

    – Ipor Sircer
    Aug 3 '18 at 14:30











  • Didn't know this module, however slattach is not available on remote side

    – Arkaik
    Aug 3 '18 at 14:37














  • 2





    Why don't you use the slip module to build a tcp/ip connection? tldp.org/LDP/nag2/x-087-2-slip.operation.html

    – Ipor Sircer
    Aug 3 '18 at 14:30











  • Didn't know this module, however slattach is not available on remote side

    – Arkaik
    Aug 3 '18 at 14:37








2




2





Why don't you use the slip module to build a tcp/ip connection? tldp.org/LDP/nag2/x-087-2-slip.operation.html

– Ipor Sircer
Aug 3 '18 at 14:30





Why don't you use the slip module to build a tcp/ip connection? tldp.org/LDP/nag2/x-087-2-slip.operation.html

– Ipor Sircer
Aug 3 '18 at 14:30













Didn't know this module, however slattach is not available on remote side

– Arkaik
Aug 3 '18 at 14:37





Didn't know this module, however slattach is not available on remote side

– Arkaik
Aug 3 '18 at 14:37










2 Answers
2






active

oldest

votes


















2














Finally found out that I was issuing the wrong command on receiver's side.



Receive command shall be : cat < /dev/ttyUSB0 > file_b64



Summary



To receive from remote :



          Host side                |             Remote side
|
| #Encode to base64
| cat file | base64 > file_b64
|
| #Send after timeout
| (sleep 10; cat file_b64 > /dev/ttyS0) &
|
#############################################################
### Exit minicom but keep configuration (ctrlA-Z, then Q) ###
#############################################################
|
#Receive file |
cat < /dev/ttyUSB0 > file_b64 |
|
#Decode file |
cat file_b64 | base64 -di > file |





share|improve this answer

































    1














    Summarizing above posts i found something like this:



    Sending.



    Start receiving on target:



    cat | base64 -d > filetotarget.bin


    Exit minicom with Ctrl-A + Q and then run on host machine:



    cat filetotarget.bin | base64 > /dev/ttyUSB0


    Return to minicom and press Ctrl-D to finish receive process.



    Receiving.



    Start delayed send on target:



    sleep 10 ; cat filefromtarget.bin | base64


    Exit minicom with Ctrl-A + Q. Then start receiving on host:



    cat < /dev/ttyUSB0 | base64 -di > filefromtarget.bin





    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%2f460342%2fretrieve-file-over-serial-without-kermit-and-lrzsz%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









      2














      Finally found out that I was issuing the wrong command on receiver's side.



      Receive command shall be : cat < /dev/ttyUSB0 > file_b64



      Summary



      To receive from remote :



                Host side                |             Remote side
      |
      | #Encode to base64
      | cat file | base64 > file_b64
      |
      | #Send after timeout
      | (sleep 10; cat file_b64 > /dev/ttyS0) &
      |
      #############################################################
      ### Exit minicom but keep configuration (ctrlA-Z, then Q) ###
      #############################################################
      |
      #Receive file |
      cat < /dev/ttyUSB0 > file_b64 |
      |
      #Decode file |
      cat file_b64 | base64 -di > file |





      share|improve this answer






























        2














        Finally found out that I was issuing the wrong command on receiver's side.



        Receive command shall be : cat < /dev/ttyUSB0 > file_b64



        Summary



        To receive from remote :



                  Host side                |             Remote side
        |
        | #Encode to base64
        | cat file | base64 > file_b64
        |
        | #Send after timeout
        | (sleep 10; cat file_b64 > /dev/ttyS0) &
        |
        #############################################################
        ### Exit minicom but keep configuration (ctrlA-Z, then Q) ###
        #############################################################
        |
        #Receive file |
        cat < /dev/ttyUSB0 > file_b64 |
        |
        #Decode file |
        cat file_b64 | base64 -di > file |





        share|improve this answer




























          2












          2








          2







          Finally found out that I was issuing the wrong command on receiver's side.



          Receive command shall be : cat < /dev/ttyUSB0 > file_b64



          Summary



          To receive from remote :



                    Host side                |             Remote side
          |
          | #Encode to base64
          | cat file | base64 > file_b64
          |
          | #Send after timeout
          | (sleep 10; cat file_b64 > /dev/ttyS0) &
          |
          #############################################################
          ### Exit minicom but keep configuration (ctrlA-Z, then Q) ###
          #############################################################
          |
          #Receive file |
          cat < /dev/ttyUSB0 > file_b64 |
          |
          #Decode file |
          cat file_b64 | base64 -di > file |





          share|improve this answer















          Finally found out that I was issuing the wrong command on receiver's side.



          Receive command shall be : cat < /dev/ttyUSB0 > file_b64



          Summary



          To receive from remote :



                    Host side                |             Remote side
          |
          | #Encode to base64
          | cat file | base64 > file_b64
          |
          | #Send after timeout
          | (sleep 10; cat file_b64 > /dev/ttyS0) &
          |
          #############################################################
          ### Exit minicom but keep configuration (ctrlA-Z, then Q) ###
          #############################################################
          |
          #Receive file |
          cat < /dev/ttyUSB0 > file_b64 |
          |
          #Decode file |
          cat file_b64 | base64 -di > file |






          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Sep 17 '18 at 8:21

























          answered Aug 3 '18 at 15:14









          ArkaikArkaik

          408422




          408422

























              1














              Summarizing above posts i found something like this:



              Sending.



              Start receiving on target:



              cat | base64 -d > filetotarget.bin


              Exit minicom with Ctrl-A + Q and then run on host machine:



              cat filetotarget.bin | base64 > /dev/ttyUSB0


              Return to minicom and press Ctrl-D to finish receive process.



              Receiving.



              Start delayed send on target:



              sleep 10 ; cat filefromtarget.bin | base64


              Exit minicom with Ctrl-A + Q. Then start receiving on host:



              cat < /dev/ttyUSB0 | base64 -di > filefromtarget.bin





              share|improve this answer






























                1














                Summarizing above posts i found something like this:



                Sending.



                Start receiving on target:



                cat | base64 -d > filetotarget.bin


                Exit minicom with Ctrl-A + Q and then run on host machine:



                cat filetotarget.bin | base64 > /dev/ttyUSB0


                Return to minicom and press Ctrl-D to finish receive process.



                Receiving.



                Start delayed send on target:



                sleep 10 ; cat filefromtarget.bin | base64


                Exit minicom with Ctrl-A + Q. Then start receiving on host:



                cat < /dev/ttyUSB0 | base64 -di > filefromtarget.bin





                share|improve this answer




























                  1












                  1








                  1







                  Summarizing above posts i found something like this:



                  Sending.



                  Start receiving on target:



                  cat | base64 -d > filetotarget.bin


                  Exit minicom with Ctrl-A + Q and then run on host machine:



                  cat filetotarget.bin | base64 > /dev/ttyUSB0


                  Return to minicom and press Ctrl-D to finish receive process.



                  Receiving.



                  Start delayed send on target:



                  sleep 10 ; cat filefromtarget.bin | base64


                  Exit minicom with Ctrl-A + Q. Then start receiving on host:



                  cat < /dev/ttyUSB0 | base64 -di > filefromtarget.bin





                  share|improve this answer















                  Summarizing above posts i found something like this:



                  Sending.



                  Start receiving on target:



                  cat | base64 -d > filetotarget.bin


                  Exit minicom with Ctrl-A + Q and then run on host machine:



                  cat filetotarget.bin | base64 > /dev/ttyUSB0


                  Return to minicom and press Ctrl-D to finish receive process.



                  Receiving.



                  Start delayed send on target:



                  sleep 10 ; cat filefromtarget.bin | base64


                  Exit minicom with Ctrl-A + Q. Then start receiving on host:



                  cat < /dev/ttyUSB0 | base64 -di > filefromtarget.bin






                  share|improve this answer














                  share|improve this answer



                  share|improve this answer








                  edited 24 mins ago

























                  answered Dec 7 '18 at 13:54









                  Serg StetsukSerg Stetsuk

                  666




                  666






























                      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%2f460342%2fretrieve-file-over-serial-without-kermit-and-lrzsz%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

                      Taj Mahal Inhaltsverzeichnis Aufbau | Geschichte | 350-Jahr-Feier | Heutige Bedeutung | Siehe auch |...

                      Baia Sprie Cuprins Etimologie | Istorie | Demografie | Politică și administrație | Arii naturale...

                      Nicolae Petrescu-Găină Cuprins Biografie | Opera | In memoriam | Varia | Controverse, incertitudini...