[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [microblaze-uclinux] Fwd: SREC File Upload Issues



Here's some additional debug info.  I wanted to mention that I'm running uCLinux on a CentOS VM using VirtualBox, not natively.  I have a feeling that the serial buffer is corrupting the transfers by dropping data.  For example, if I plug in a serial loopback and then issue the following commands in 2 terminals:

cat u-boot.srec > /dev/ttyS0

cat /dev/ttyS0 > output

My output looks like this:

S00E0000752D626F6F742E73726563C0


S31527FC00009400C001B00027F4202000002021FFFC2B


S31527FC0010B00027FD20A09AD0B00027FD2080ED2C2C


S31527FC002014C52001BC060014F805000020A5000480016432003BE52002457


S31527FC006010E00000B00027FDE8609AD41644180378


S31527FC0070BC52001010E60000B00027FDF8809AD885


S31527FC0080B60F000810670000B00027FD30A04B000003021FFD010BF000066


S31527FC00C0FA610020F9E10000FAC10024FAE10028D0


S31527FC00D0FB01002CB00027FD32608E18B000000112


S31527FC00E0B9F405B410C00000B00027FDE8608E18EF

9F4C6B4800000000C


S31527FC0120B00027FD30A04B44B0000000B9F4C6A0B0


S31527FC013080000000B0000000B9F4047C80000000B9

etc...

When in fact u-boot.srec looks like this:

S00E0000752D626F6F742E73726563C0
S31527FC00009400C001B00027F4202000002021FFFC2B
S31527FC0010B00027FD20A09AD0B00027FD2080ED2C2C
S31527FC002014C52001BC060014F805000020A5000411
S31527FC003014C52001BC26FFF4B00027FCB80800A88D
S31527FC0040B8000000B00027FDE8C09AD8B00027FD0D
S31527FC0050E8609AD01086280016432003BE52002457
S31527FC006010E00000B00027FDE8609AD41644180378
S31527FC0070BC52001010E60000B00027FDF8809AD885
S31527FC0080B60F000810670000B00027FD30A04B0C08
S31527FC00903021FFE4F9E10000B0000000B9F4C730D5
S31527FC00A080000000B8000000B00027F433E0000011
S31527FC00B0B000000230E000003021FFD010BF000066
S31527FC00C0FA610020F9E10000FAC10024FAE10028D0
S31527FC00D0FB01002CB00027FD32608E18B000000112
S31527FC00E0B9F405B410C00000B00027FDE8608E18EF
S31527FC00F0BC03001CE873000099FC1800327300044B
S31527FC0100BC23021CE8730000B800FFE8B00027FDFB
etc...

I will post on the VirtualBox forum as well.

Thanks.

Matt

On Tue, Jan 27, 2009 at 20:29, Matt Staniszewski <matt.staniszewski@xxxxxxxxx> wrote:
Just to give an update, I have tried moving on to the section where the U-boot script is transferred to the board:

U-Boot> loadb 0x24000000
## Ready for binary (kermit) download to 0x24000000 at 115200 bps...

(Back at localhost.localdomain)
----------------------------------------------------
C-Kermit 8.0.211, 10 Apr 2004, for Linux
 Copyright (C) 1985, 2004,
  Trustees of Columbia University in the City of New York.
Type ? or HELP for help.
(/home/mstanisz/petalinux-v0.30-rc1/software/petalinux-dist/) C-Kermit>send /bin
?Filename required but not given
(/home/mstanisz/petalinux-v0.30-rc1/software/petalinux-dist/) C-Kermit>send /bin /tftpboot/ub.config.img

*************************
SEND-class command failed.
 Packets sent: 2
 Retransmissions: 11
 Timeouts: 0
 Damaged packets: 0
 Fatal Kermit Protocol Error: Too many retries

HINTS... If the preceding error message does not explain the failure:
 . Try changing the remote Kermit's FLOW-CONTROL setting.
 . Increase the retry limit (see HELP SET RETRY).
 . Try it again with SET STREAMING OFF.
 . Try it again with SET PARITY SPACE.
 . As a last resort, give a ROBUST command and try again.
Also:
 . Be sure the source file has read permission.
 . Be sure the target directory has write permission.
(Use SET HINTS OFF to suppress hints.)
*************************

(/home/mstanisz/petalinux-v0.30-rc1/software/petalinux-dist/) C-Kermit>

I've tried all the hints given.

I'm sure it is related to me not being able to send files via the cat command, but I'm still at a loss.

Thanks.

Matt