Skip to main content
Unix & Linux

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • Try without -b option? Commented Aug 23, 2021 at 4:26
  • I get the exact same result without the -b option. It seems like it's something with the fifo, like it's not opening correctly, is empty, is not in the working directory. Perhaps if I wrote a script, so I have more control over the environment. I'm going to try Windows Terminal, on a lappy with a real serial port. Commented Aug 23, 2021 at 16:21
  • Hit Enter before selecting S for send. Choose the protocol the firmware is expecting. Don’t try to run sz in another window, minicom should run it if configured correctly (that’s what S does). Commented Aug 24, 2021 at 5:37
  • minicom just runs sz in the background ... run minicom -s as root, select File transfer protocols, then define a protocol for Xmodem-1K (called xmodem1k I would suggest), which calls the sx command with the -k option (plus probably -vv) i.e. command will be /usr/bin/sz -k -vv. I would suggest U/D should be U, FullScr should be N, IO-Red. should be Y and Multi should be N. Not sure about Name - probably should be Y (does this mean it provides the file name?). After doing this, when you do a Ctrl-Z S, xmodem1k should appear in the list of protocols. Commented Aug 26, 2021 at 8:45
  • I'm leaving this problem here. I followed your advice, which probably would work in any other situation. I think these embedded cards are just ultra finicky! Thanks a bunch. Can't win them all. Commented Sep 7, 2021 at 5:50