[U-Boot] Transfer file using loadb
HI all,
I am working on OMAP3 based SoC. I am trying to send uImage over serial port using kermit. I have followed folowing:
1. issued a loadb command on u-boot prompt. 2. On c-termit> send /bin uImage
Every time after this transfer get started but then aborted automatically with following error message: ************************* SEND-class command failed. Packets sent: 193 Retransmissions: 135 Timeouts: 10 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.) *************************
But if I try to send a small file then it get transfered successfully. What could be the cause of this issue.
~cnanda
Dear Chetan Nanda,
In message 7f245da81001300735x6d0727f8s2f530d6a3540e2b5@mail.gmail.com you wrote:
Every time after this transfer get started but then aborted automatically with following error message:
...
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.
So - have you tried any of these hints?
The kermit developer tried the best they could do to help you by providing valuable hints for configuration settings that might help to solve your problem - and did you follow their advice?
Also, did you RTFM? The manual contains a section on how to configure kermit for reliable work:
http://www.denx.de/wiki/view/DULG/SystemSetup#Section_4.3.
Did you really adapt your ~/.kermrc as recommended?
Best regards,
Wolfgang Denk
Tried with loady command in u-boot and ymodem option from minicom. With this combination I am able to transfer and run uImage.
~cnanda
On Sat, Jan 30, 2010 at 10:02 PM, Wolfgang Denk wd@denx.de wrote:
Dear Chetan Nanda,
In message 7f245da81001300735x6d0727f8s2f530d6a3540e2b5@mail.gmail.com you wrote:
Every time after this transfer get started but then aborted automatically with following error message:
...
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.
So - have you tried any of these hints?
The kermit developer tried the best they could do to help you by providing valuable hints for configuration settings that might help to solve your problem - and did you follow their advice?
Also, did you RTFM? The manual contains a section on how to configure kermit for reliable work:
http://www.denx.de/wiki/view/DULG/SystemSetup#Section_4.3.
Did you really adapt your ~/.kermrc as recommended?
Best regards,
Wolfgang Denk
-- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de "Bureaucracy is the enemy of innovation." - Mark Shepherd, former President and CEO of Texas Instruments
Dear Chetan Nanda,
In message 7f245da81001310646x12451ac8s5ac9bda0fd6ac37c@mail.gmail.com you wrote:
Tried with loady command in u-boot and ymodem option from minicom. With this combination I am able to transfer and run uImage.
I tested this again on OMAP3 systems (including Beagle):
OMAP3 beagleboard.org # loadb ${uimage_addr} ## Ready for binary (kermit) download to 0x80300000 at 115200 bps...
(Back at pollux.denx.de) ---------------------------------------------------- Kermit>send /bin /tftpboot/beagle/uImage ... C-Kermit 8.0.211, 10 Apr 2004, pollux.denx.de [192.168.1.1]
Current Directory: /home/wd Network Host: ts0:513 Network Type: TCP/IP Parity: none RTT/Timeout: 01 / 02 SENDING: /tftpboot/beagle/uImage => uImage File Type: BINARY File Size: 1962820 Percent Done: 99 /////////////////////////////////////////////////- ...10...20...30...40...50...60...70...80...90..100 Estimated Time Left: 00:00:02 Transfer Rate, CPS: 4748 Window Slots: 1 of 1 Packet Type: D Packet Count: 2459 Packet Length: 1000 Error Count: 0 Last Error: Last Message:
X to cancel file, Z to cancel group, <CR> to resend last packet, E to send Error packet, ^C to quit immediately, ^L to refresh screen. ... Kermit>c Connecting to host ts0:513 Escape character: Ctrl-\ (ASCII 28, FS): enabled Type the escape character followed by C to get back, or followed by ? to see other options. ---------------------------------------------------- ## Total Size = 0x001df344 = 1962820 Bytes ## Start Addr = 0x80300000 OMAP3 beagleboard.org # imi 0x80300000
## Checking Image at 80300000 ... Legacy image found Image Name: Linux-2.6.33-rc5-07168-gc48807a Created: 2010-01-25 14:58:56 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 1962756 Bytes = 1.9 MB Load Address: 80008000 Entry Point: 80008000 Verifying Checksum ... OK OMAP3 beagleboard.org #
As you can see, this is working without any problems.
So either your host systems is still misconfigured (which I consoder most likely), or your target system hast issues (instable RAM and.or serial port, etc.), or you have been doing something wrong.
I don't think there is a problem in the mainline U-Boot code.
Best regards,
Wolfgang Denk
Hi Wolfgang
I tried with kermit again. Following is the console log when file is getting transfered.
################################### C-Kermit 8.0.211, 10 Apr 2004, chetan-laptop
Current Directory: /media/DISK_VOL2/Work/beagleboard/sw/code/testApp Communication Device: /dev/ttyUSB0 Communication Speed: 115200 Parity: none RTT/Timeout: 01 / 02 SENDING: uImage => uImage File Type: BINARY File Size: 1911160 Percent Done: 2 / ...10...20...30...40...50...60...70...80...90..100 Estimated Time Left: 00:05:38 Transfer Rate, CPS: 5512 Window Slots: 1 of 1 Packet Type: D Packet Count: 79 Packet Length: 609 Error Count: 32 Last Error: (resend) Last Message:
X to cancel file, Z to cancel group, <CR> to resend last packet, ############################
As there is considerable difference between the logs I am getting and logs you have provided in you last mail.
e.g Communication device is /dev/ttyUSB0 (in my logs)
But in your case it look like: Network Host: ts0:513 Network Type: TCP/IP
I am not sure about these differences.
~cnanda
On Sun, Jan 31, 2010 at 8:43 PM, Wolfgang Denk wd@denx.de wrote:
Dear Chetan Nanda,
In message 7f245da81001310646x12451ac8s5ac9bda0fd6ac37c@mail.gmail.com you wrote:
Tried with loady command in u-boot and ymodem option from minicom. With this combination I am able to transfer and run uImage.
I tested this again on OMAP3 systems (including Beagle):
OMAP3 beagleboard.org # loadb ${uimage_addr} ## Ready for binary (kermit) download to 0x80300000 at 115200 bps...
(Back at pollux.denx.de)
Kermit>send /bin /tftpboot/beagle/uImage ... C-Kermit 8.0.211, 10 Apr 2004, pollux.denx.de [192.168.1.1]
Current Directory: /home/wd Network Host: ts0:513 Network Type: TCP/IP Parity: none RTT/Timeout: 01 / 02 SENDING: /tftpboot/beagle/uImage => uImage File Type: BINARY File Size: 1962820 Percent Done: 99 /////////////////////////////////////////////////- ...10...20...30...40...50...60...70...80...90..100 Estimated Time Left: 00:00:02 Transfer Rate, CPS: 4748 Window Slots: 1 of 1 Packet Type: D Packet Count: 2459 Packet Length: 1000 Error Count: 0 Last Error: Last Message:
X to cancel file, Z to cancel group, <CR> to resend last packet, E to send Error packet, ^C to quit immediately, ^L to refresh screen. ... Kermit>c Connecting to host ts0:513 Escape character: Ctrl-\ (ASCII 28, FS): enabled Type the escape character followed by C to get back, or followed by ? to see other options.
## Total Size = 0x001df344 = 1962820 Bytes ## Start Addr = 0x80300000 OMAP3 beagleboard.org # imi 0x80300000
## Checking Image at 80300000 ... Legacy image found Image Name: Linux-2.6.33-rc5-07168-gc48807a Created: 2010-01-25 14:58:56 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 1962756 Bytes = 1.9 MB Load Address: 80008000 Entry Point: 80008000 Verifying Checksum ... OK OMAP3 beagleboard.org #
As you can see, this is working without any problems.
So either your host systems is still misconfigured (which I consoder most likely), or your target system hast issues (instable RAM and.or serial port, etc.), or you have been doing something wrong.
I don't think there is a problem in the mainline U-Boot code.
Best regards,
Wolfgang Denk
-- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de If I can have honesty, it's easier to overlook mistakes. -- Kirk, "Space Seed", stardate 3141.9
Dear Chetan Nanda,
In message 7f245da81001310745i8e54f9dr95cb4c0af0a744ec@mail.gmail.com you wrote:
As there is considerable difference between the logs I am getting and logs you have provided in you last mail.
e.g Communication device is /dev/ttyUSB0 (in my logs)
But in your case it look like: Network Host: ts0:513 Network Type: TCP/IP
I am not sure about these differences.
This is just because I connect to the device's serial port through a terminal server, while you seem to be using a USB serial adapter.
Of course chances are that your USB serial adapter and/or the drivers for it are broken, too.
On Sun, Jan 31, 2010 at 8:43 PM, Wolfgang Denk wd@denx.de wrote:
Full quote deleted.
Please do not top-post / full quote.
Make sure to read http://www.netmeister.org/news/learn2quote.html
Best regards,
Wolfgang Denk
Hi Wolfgang,
On Sun, Jan 31, 2010 at 9:27 PM, Wolfgang Denk wd@denx.de wrote:
Dear Chetan Nanda,
In message 7f245da81001310745i8e54f9dr95cb4c0af0a744ec@mail.gmail.com you wrote:
As there is considerable difference between the logs I am getting and
logs
you have provided in you last mail.
e.g Communication device is /dev/ttyUSB0 (in my logs)
But in your case it look like: Network Host: ts0:513 Network Type: TCP/IP
I am not sure about these differences.
This is just because I connect to the device's serial port through a terminal server, while you seem to be using a USB serial adapter.
Of course chances are that your USB serial adapter and/or the drivers
for it are broken, too.
May be this is the case. I am using 'Prolific Technology, Inc. PL2303 Serial Port' as USB serial adapter.
I will try with different one to make sure whether its a driver issue or not.
On Sun, Jan 31, 2010 at 8:43 PM, Wolfgang Denk wd@denx.de wrote:
Full quote deleted.
Please do not top-post / full quote.
Sorry for top posting
Make sure to read http://www.netmeister.org/news/learn2quote.html
Best regards,
Wolfgang Denk
-- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de We, the unwilling, led by the unknowing, are doing the impossible for the ungrateful. We have done so much, for so long, with so little, we are now qualified to do anything with nothing.
~cnanda
On Sun, Jan 31, 2010 at 10:10 AM, Chetan Nanda chetannanda@gmail.com wrote:
Hi Wolfgang,
On Sun, Jan 31, 2010 at 9:27 PM, Wolfgang Denk wd@denx.de wrote:
Dear Chetan Nanda,
In message 7f245da81001310745i8e54f9dr95cb4c0af0a744ec@mail.gmail.com you wrote:
Of course chances are that your USB serial adapter and/or the drivers
for it are broken, too.
May be this is the case. I am using 'Prolific Technology, Inc. PL2303 Serial Port' as USB serial adapter.
I will try with different one to make sure whether its a driver issue or not.
My experience with the Prolific USB serial chip is that it doesn't work very well (under windows or linux). I have had much better luck with Silicon Labs CP2103 (? number is from memory) chips.
participants (3)
-
Andrew Dyer -
Chetan Nanda -
Wolfgang Denk