LPC2388 Ethernet: Command-Line "Connection failed: comms error"

Started by thomas, July 08, 2013, 02:19:16 AM

Previous topic - Next topic

thomas

Hi everybody,

I am trying to program the LPC2388 by using the build-in command line functions. However this is not working properly.

QuoteFlash Magic Version 7.50.3174
8051/XA Driver Version 3.03.3043
ARM UART Driver Version 3.04.3043
ARM Cortex UART Driver Version 4.56.3174
ARM Ethernet Driver Version 2.04.3043
ARM Cortex Ethernet Driver Version 2.06.3043
ARM CAN Driver Version 2.07.3134
(C) Embedded Systems Academy 2000-2013 All rights reserved
NON PRODUCTION USE ONLY
Connection failed: comms error

Directives:
ETHERNET(192.168.0.2, 4a-45-30-30-31-35, 0)
DEVICE(LPC2388ETH, 0, 0)
ERASE(0, PROTECTISP)
ERASE(1, PROTECTISP)
ERASE(2, PROTECTISP)
ERASE(3, PROTECTISP)
ERASE(4, PROTECTISP)
ERASE(5, PROTECTISP)
ERASE(6, PROTECTISP)
ERASE(7, PROTECTISP)
ERASE(8, PROTECTISP)
ERASE(9, PROTECTISP)
ERASE(10, PROTECTISP)
ERASE(11, PROTECTISP)
ERASE(12, PROTECTISP)
ERASE(13, PROTECTISP)
ERASE(14, PROTECTISP)
ERASE(15, PROTECTISP)
ERASE(16, PROTECTISP)
ERASE(17, PROTECTISP)
ERASE(18, PROTECTISP)
ERASE(19, PROTECTISP)
ERASE(20, PROTECTISP)
ERASE(21, PROTECTISP)
ERASE(22, PROTECTISP)
ERASE(23, PROTECTISP)
ERASE(24, PROTECTISP)
HEXFILE(C:\Users\rth3fe\Desktop\ELU_V186_C1_ETH_iptest.hex, NOCHECKSUMS, FILL, PROTECTISP)
VERIFY(C:\Users\rth3fe\Desktop\ELU_V186_C1_ETH_iptest.hex, NOCHECKSUMS)



The command file was directly saved from option "File > Save Command Line Directives" after a successful programming of the device through the gui.



Please give me some advice on how to handle this.

Thanks!

Thomas

Andy Ayre

Please double-check that the settings in the command line match exactly the settings in the GUI and nothing is missing.

Check the output from Flash Magic using Wireshark to compare the GUI with the command line and let us know what the difference is.

Andy
Embedded Systems Academy, Inc.
support at esacademy dot com

thomas

Hi Andy,

my computer uses two Ethernet Cards. There is a "Interface" option on GUI but it seems there is no equivalent option for the command line tool. The rest of the settings are matching to the GUI's.
I analyzed the communication using Wireshark, too. There are broadcasts (3 to be exact) to the LPC2388. After the third broadcast, the tool exits with said error.
QuoteConnection failed: comms error

Edit:
Some specs of my system may help:
OS: Windows 7 Pro
Network card: Realtek RTL8169/8110 Family PCI Gigabit Ethernet

Andy Ayre

The command line will use the first Ethernet interface found - choosing an interface is currently not supported, mostly due to them having painfully long names.

You need to compare the wireshark output from the GUI working with the command line not working to see what the difference is.

Andy
Embedded Systems Academy, Inc.
support at esacademy dot com