This is the mail archive of the
ecos-bugs@sourceware.org
mailing list for the eCos project.
[Bug 1000818] New: Unable to download VxWorks image to Arcom Vipervia Redboot TFTP
- From: bugzilla-daemon at ecoscentric dot com
- To: ecos-bugs at ecos dot sourceware dot org
- Date: Fri, 4 Sep 2009 17:08:12 +0100
- Subject: [Bug 1000818] New: Unable to download VxWorks image to Arcom Vipervia Redboot TFTP
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1000818
Summary: Unable to download VxWorks image to Arcom Viper via
Redboot TFTP
Product: eCos
Version: unknown
Platform: Other (please specify)
OS/Version: Other
Status: UNCONFIRMED
Severity: major
Priority: high
Component: RedBoot
AssignedTo: gary@mlbassoc.com
ReportedBy: jkanders@memphis.edu
QAContact: ecos-bugs@ecos.sourceware.org
Class: ---
Platform Information below:
RedBoot(tm) bootstrap and debug environment [ROM]
Non-certified release, version W468 V3I4 - built 09:58:14, Aug 3 2004
Platform: VIPER (XScale PXA255)
Copyright (C) 2000, 2001, 2002, Red Hat, Inc.
Problem Description:
We have an Arcom(Eurotech) Viper board. It uses redboot as a bootloader. We
are trying to load a new VxWorks image onto the board via TFTP using the
redboot command below:
load -b 0x00400000 -v -m tftp
C:\Tornado\target\proj\testViperIM\default\vxWorks
We start the TFTP server on our host workstation. Issue the redboot load
command. The transfer starts. At some point during the transfer the transfer
stops. The TFTP server reports an Error and indicates that it did not get an
acknowledge from the board. Redboot seems to think that the transfer has
successfully completed and reports the transfer results. However...the entire
image file has NOT been transfered.
We can ping the board from our host workstation. We can ping the host
workstation from the board using the redboot command below:
ping -v -n 4 -i 141.225.167.71 -h 141.225.166.245
The image file we are trying to download...was created in Tornado 2.2.1.
--
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.