cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
3,128 Views
Registered: ‎03-31-2017

Minicom file transmission error

Jump to solution

Hello all you good people !

 

I am having an issue while transferring an ASCII coded file from my host PC to the Zedboard running open source linux (OSL) over UART interface using minicom. I get "short file" error while trying to decode the file on linux running on Zedboard. Having checked the checksum, I realized that there is transmission error. What can I do about it? What I did is the following:

 

PC side - ascii encoded the file to be sent using uuencode

Target side (Zedboard) - cat > received_file.txt 

ctrl+a, s and navigate to the file to be sent.

uudecode received_file.txt -> this gives me "short file" error

Also checksum for the sent and received files are different. Sent and received files are in the attachment.

 

Any heads up will be highly appreciated!!!

 

 

 

0 Kudos
1 Solution

Accepted Solutions
timduffy
Explorer
Explorer
4,538 Views
Registered: ‎04-05-2016
Any chance you can send the data over Ethernet? scp or ftp?

This page says you may need to decode it using a unicode decoder ( which I do not believe is included in the OSL ram disk )

http://k.japko.eu/serial-transfers.html

Some interesting points on this page as well. Might be worth it.

http://www.emcraft.com/stm32f429discovery/loading-application-files-via-uart

If uudecode isn't in the OSL ramdisk, you could compile it and put it on your sdcard via the source:

http://numerical.recipes/utils/uudecode.c.txt

View solution in original post

6 Replies
timduffy
Explorer
Explorer
3,107 Views
Registered: ‎04-05-2016
Looks like there are 80 spaces between each line of the file that don't belong. I suspect this is a minicom configuration issue, but what that issue is I don't know. This script looks promising though:

http://www.dannysung.com/wmain/linux/tips/sending-binary-files-via-minicom/
0 Kudos
3,092 Views
Registered: ‎03-31-2017

Thanks @timduffy for the link but that did not work either for me...I get this error "Failure executing protocol." I also tired as Potion mentioned in the comment as well but that too did not work ...:( . Any other way around is appreciated!!!

0 Kudos
timduffy
Explorer
Explorer
4,539 Views
Registered: ‎04-05-2016
Any chance you can send the data over Ethernet? scp or ftp?

This page says you may need to decode it using a unicode decoder ( which I do not believe is included in the OSL ram disk )

http://k.japko.eu/serial-transfers.html

Some interesting points on this page as well. Might be worth it.

http://www.emcraft.com/stm32f429discovery/loading-application-files-via-uart

If uudecode isn't in the OSL ramdisk, you could compile it and put it on your sdcard via the source:

http://numerical.recipes/utils/uudecode.c.txt

View solution in original post

2,958 Views
Registered: ‎03-31-2017

Sorry for the late response...I am out for few days...I will have a look at the links you posted @timduffy and keep you updated...:) Thanks for your concern. Much appreciated!!!

0 Kudos
2,874 Views
Registered: ‎03-31-2017

Hello @timduffy and all other good people

I could see that there is uuencode/uudecode in OSL in /usr/bin. When I try uudecode in the target (Zynq) side, it tries decoding but finds that the file is short. So I believe there is already uuencode included in the OSL. I am trying to get this way around via ethernet. SSH, ftp...if you have any comprehensive tutorial, please feel free to share....:)

0 Kudos
2,844 Views
Registered: ‎03-31-2017

@timduffy Managed to solve the issue with ftp...however still could not figure out why it is not working with UART transfer....

0 Kudos