Hi All,
I met a fatal error during the filesystem flashing process of netstix.
I restrictly follow the instruction of kermit set up, unfortunately I got a fatal error :
SEND-class command failed.
 Packets sent: 5
 Retransmissions: 11
 Timeouts: 0
 Damaged packets: 0
 Fatal Kermit Protocol Error: Too many retries
The following is the detailed report:     Could some one give me a hint?    Thank you so much.     (song guo)
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
(/root/gumstix-buildroot/) C-Kermit>set speed 115200
/dev/ttyS0, 115200 bps
(/root/gumstix-buildroot/) C-Kermit>set reliable
(/root/gumstix-buildroot/) C-Kermit>fast
(/root/gumstix-buildroot/) C-Kermit>set carrier-watch off
(/root/gumstix-buildroot/) C-Kermit>set flow-control none
(/root/gumstix-buildroot/) C-Kermit>set prefixing all
(/root/gumstix-buildroot/) C-Kermit>set file type bin
(/root/gumstix-buildroot/) C-Kermit>set rec pack 4096
(/root/gumstix-buildroot/) C-Kermit>set send pack 4096
(/root/gumstix-buildroot/) C-Kermit>set window 5
(/root/gumstix-buildroot/) C-Kermit>connect
Connecting to /dev/ttyS0, speed 115200
 Escape character: Ctrl-\ (ASCII 28, FS): enabled
Type the escape character followed by C to get back,
or followed by ? to see other options.
----------------------------------------------------


U-Boot 1.1.4 (Nov  6 2006 - 11:39:27) - 200 MHz - 1161

*** Welcome to Gumstix ***

U-Boot code: A3F00000 -> A3F25DE4  BSS: -> A3F5AF00
RAM Configuration:
Bank #0: a0000000 64 MB
Flash: 16 MB
Using default environment

SMC91C1111-0
Net:   SMC91C1111-0
Hit any key to stop autoboot:  0
GUM> loadb a2000000
## Ready for binary (kermit) download to 0xA2000000 at 115200 bps...

(Back at localhost.localdomain)
----------------------------------------------------
(/root/gumstix-buildroot/) C-Kermit>send rootfs.arm_nofpu.jffs2

*************************
SEND-class command failed.
 Packets sent: 5
 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.)