Linux ... xmodem transfer ... has the annoying habit of dealing with fatal errors not just by quitting but by deleting the file that it was receiving first!
... at the very end of the transfer ... The hard drive image you spent many minutes downloading (all while wondering if the drive itself will survive!) is deleted immediately ... frustrating!
Ouch! Congrats figuring out a work-around!
There is a BLU bug report (from Ray) indicating that he saw some Linux xmodem transfers that didn't terminate properly, but it doesn't seem to be a popular problem, and his report was years after release.
Looking for info, I found this (may or may not be related): https://www.mattkeeter.com/blog/2022-05-31-xmodem/, which mentions an issue with an FTDI USB-to-serial module driver interfering with the xmodem packet timing. Apparently the driver's latency is/was easy to adjust on Windows and Linux, but not MacOS -- his MacOS fix referenced at https://openbci.com/forum/index.php?p=/discussion/comment/17915/#Comment_17915.
Can anyone confirm that the BLU xmodem issue is specifically an issue with compatibility with the Linux implementation or perhaps there are anecdotes with changing serial dongles fixing an xmodem problem?