Debian Wheezy(AMD64): LPCXpresso/LPC-Link2/LPC4088 Dev. Kit - "FreeRTOS Blinky" failure.

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Debian Wheezy(AMD64): LPCXpresso/LPC-Link2/LPC4088 Dev. Kit - "FreeRTOS Blinky" failure.

324 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by paul.rcom-software.com on Sat May 17 11:51:34 MST 2014
Dear Staff:

I am currently unable to run the "FreeRtos Blinkly" example on the
4088 dev board and the problem appears to be a LPC-Link2 JTAG hardware
connectivity. (i.e. Both the board and JTAG hardware are connected to
my PC via USB ports.) The diagnostic clues are that Redlink probes
cannot be found and a mysterious "SAX ParseException" occurs.

What I consider the salient details follow this note in sections
organized as follows:

BASIC BEHAVIOR: Basic LPCXpresso and Redlink Server behavior and
failure symptoms.

ENVIRONMENT: Hardware/Software/OS environment.

BLINKY FAILURE DETAILS: Diagnostics displayed during a failure.

Best Regards,

Paul Romero

BASIC BEHAVIOR
---------------

* The Redlink Server works when started manually and a telnet
connection to it succeeds on TCP port 3025.

NOTES: GLIBC_2.14 compatibility has been established per LCP instructions
and the server is started with the following shell script:

LPCXPRESSO_ROOT_DIR=/usr/local/lpcxpresso_7.1.1_125
LPCXPRESSO_BIN_DIR="${LPCXPRESSO_ROOT_DIR}/lpcxpresso/bin"
GLIBC_DIR="${LPCXPRESSO_ROOT_DIR}/debian/glibc_import/lib/i386-linux-gnu"
export LD_LIBRARY_PATH="${LPCXPRESSO_BIN_DIR}:${GLIBC_DIR}:${LD_LIBRARY_PATH}"
exec "${LPCXPRESSO_BIN_DIR}"/redlinkserv.exe

* lsusb identifies the LPC-Link2 as follows:

Bus 002 Device 004: ID 1fc9:000c NXP Semiconductors

* Attempting to boot the Redlink server an a stand-alone
  basis--from the IDE GUI, fails as follows:

Timeout waiting for Redlink Server to initialize.

The following diagnostics are displayed on the console
if no is selected in response to the VM query and the
operation is cancelled via the GUI button.

[Started server]
[Connected on port 3025]

* Attempting to connect with the LPC-Link2 by starting the
  "FreeRtos Blinky" example fails as follows:

The following diagnostics are displayed on the console
if no is selected in response to the VM query and the
operation is cancelled via the GUI button--after SAX
ParseException diagnostics are displayed:

[Connected on port 3025]
redlink>
redlink>ProbeList
No probes found
redlink>ProbeList
No probes found
redlink>
redlink>ProbeStatus
redlink>exit
[Closed]

NOTES: See the BLINKY FAILURE DETAILS below for SAX ParseFailure diagnostics.
"Initialized Redlink Server with LPC432x_Redlink_V4_26.bin" is displayed during
the process. Also, after cancellation the following diagnostics are displayed:

Connect to emulator: NXP LCP40xx (SWD)

x No compatible emulators available
They may be disconnected, not powered, already in use or not compatible with this target.

ENVIRONMENT
-----------

Hardware
........
Board: LPC4088-32 Developers Kit. (OM13029,598)
JTAG: LPC-Link2  (OM13504)

Software
........
LPCXpresso(Free Edition Registered.): Version 7.1.1

OS
...
Debian Wheezy 7.5 Linux (AMD64)
Notes: Multi-architecture 32 bit compatibility
enabled.

BLINKY FAILURE DETAILS
----------------------
SAX ParseException
...................
Premature end of file.:null (Line:1, Col:1)
file=file:///home/paulr/./
line:1 col:1

Premature end of file.:null (Line:1, Col:1)
        at com.crt.utils.xmlparser.XMLParser.parse(Unknown Source)
        at com.crt.utils.xmlparser.XMLParser.processInput(Unknown Source)
        at com.crt.utils.general.ExecCommand.execCommand(Unknown Source)
        at com.crt.utils.general.ExecCommand.exec(Unknown Source)
        at com.crt.utils.xmlparser.XMLParser.parseXML(Unknown Source)
        at com.crt.debugcommon.emulator.EmulatorsDB.createFromCommand(Unknown Source)
        at com.crt.debugcommon.emulator.EmulatorsDB.oldStyleDiscovery(Unknown Source)
        at com.crt.debugcommon.emulator.EmulatorsDB.getEmus(Unknown Source)
        at com.crt.debugcommon.emulator.EmulatorsDB.getEmulatorInfo(Unknown Source)
        at com.crt.debugcommon.emulator.EmulatorsDB.getAvailableEmulators(Unknown Source)

        at com.crt.debugcommon.emulator.TargetDiscovery.probeDiscovery(Unknown Source)
        at com.crt.debugcommon.emulator.TargetDiscovery.probeDiscovery(Unknown Source)
        at com.crt.debugcommon.utils.LaunchScriptUtils.getEmulatorInfo(Unknown Source)
        at com.crt.debugcommon.utils.LaunchScriptUtils.init(Unknown Source)
        at com.crt.debugcommon.utils.LaunchScriptUtils.<init>(Unknown Source)
        at com.crt.debugcommon.utils.LaunchScriptUtils.<init>(Unknown Source)
        at com.crt.dsfdebug.dsf.services.TargetDiscoveryService.getTargetDiscovery(Unknown Source)
        at com.crt.dsfdebug.dsf.override.CRTFinalLaunchSequence$TargetDiscoveryJob.runInUIThread(Unknown Source)
        at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:95)
        at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
        at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
        at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3717)
        at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3366)
        at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
        at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
        at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
        at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:140)
        at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:611)
        at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
        at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
        at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
        at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
        at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
        at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
        at org.eclipse.equinox.launcher.Main.run(Main.java:1450)

0 Kudos
6 Replies

285 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by paul.rcom-software.com on Sun May 18 22:25:20 MST 2014
Hi Folks:

In order to get the Redlink Server and LPCXpresso to run correctly,
you need to do the following two things after plugging in the 4088 dev.
board and LPC-Link2 debugger into USB ports. After that you can start
LPCXpresso and run programs in the normal way. (i.e. Namely "FreeRtos Blinky.)
This seems to suggest something is configured wrong. Any ideas ?

Best Regards,

Paul R.

NOTE: Assume lsmod returns something like this to identify the LPC-Link2.

Bus 003 Device 005: ID 1fc9:000c NXP Semiconductors

1) As superuser you need to remove the following two modules
   as follows:

        rmmod ftdi_sio
        rmmod usbserial

2) Next run dfu-util manually as superuser to initialize the  LPC-Link2 debugger.

dfu-util -d 0x1fc9:0x000c -c 0 -t 2048 -R -D LPC432x_Redlink_V4_26.bin.hdr

The output should be as follows.

dfu-util - (C) 2007-2008 by OpenMoko Inc.
This program is Free Software and has ABSOLUTELY NO WARRANTY

Opening USB Device 0x1fc9:0x000c...
Claiming USB DFU Runtime Interface...
Determining device status: state = dfuIDLE, status = 0
WARNING: Runtime device already in DFU state ?!?
Found Runtime: [0x1fc9:0x000c] devnum=8, cfg=0, intf=0, alt=0, name="DFU"
Claiming USB DFU Interface...
Setting Alternate Setting ...
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
Transfer Size = 0x0800
bytes_per_hash=471
Starting download: [##################################################] finished!
unable to read DFU status

(i.e. The last line is a mystery.)
0 Kudos

285 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by paul.rcom-software.com on Sun May 18 20:37:33 MST 2014
Hi Folks:

A little more information about the LPC-Link2  USB status:

This is what dfu-util -ls produces but I am not sure
it is even relevant:

dfu-util - (C) 2007-2008 by OpenMoko Inc.
This program is Free Software and has ABSOLUTELY NO WARRANTY

Found Runtime: [0x1fc9:0x000c] devnum=0, cfg=0, intf=0, alt=0, name="UNDEFINED"

Best Regards,

Paul r.

~                                                       
0 Kudos

285 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by paul.rcom-software.com on Sun May 18 12:14:15 MST 2014
Hi Folks:

Per section 3n: The example project is webserver_freertos.

Is dfu-util mandatory and what does it do ?  Also, is there
some way to test or debug outside of the LPCXpresso GUI ?

Best Regards,

Paul R.
0 Kudos

285 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by lpcxpresso-support on Sun May 18 09:57:49 MST 2014
3b. Which exampleis this? It is not a missing file. It is an incorrect directory separator.

Issue. It is booting the firmware into lpclink2 and waiting for it to re enumerate. My guess is that dfu-util is not working due to a missing library dependency.

0 Kudos

285 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by paul.rcom-software.com on Sun May 18 08:37:08 MST 2014
Dear Staff:

Perhaps there is a non-OS problem we have overlooked.
A synopsis of the installation and operating procedures
I am using follows. Please look for the string "ISSUE"
as it identifies areas where I suspect a possible problem.

Best Regards,

Paul R.

0) Pre-Installation - Succeeded

* Install and test FTDI drivers for FT232RL USB chip on LPC4088 board.
(i.e. Installation packages libftd2xx1.1.12.tar.gz and libftd2xx_V125.zip)

1) Installation and Configuration - Succeeded without problems

* Download Version 7.1.1 of LpcXpresso
  (i.e. Installer_LPCXpresso_7.1.1_125_Linux-x86.tar.gz)

* Unpack tar.gz file.

* Run Installer program.

* Start up LPCXpresso and import software infrastructure and examples.
  (i.e. From lpcopen_2_10_lpcxpresso_ea_devkit_4088.zip)


2) Common starting procedure - Works

* Plug in LPC4088 board and LPC-Link2 JTAG hardware into PC USB ports.
  (i.e. Assume LPC4088 board LPC-Link2 are already connected correctly.)

* Start LPCXpresso GUI

3) Building Software - Works with a hitch.

3.a) Build "FreeRtos" Blink example - Works without problems.

3.b) Build all projects - Works with the following exception.
(i.e. It appears a file is missing.)

Invoking: MCU C Compiler

....

../example/src/webserver_freertos.c:49:36: fatal error: arch\lpc17xx_40xx_emac.h: No such file or directory
#include "arch\lpc17xx_40xx_emac.h"
                                    ^
compilation terminated.
make: *** [example/src/webserver_freertos.o] Error 1

08:07:27 Build Finished (took 216ms)

4) Boot the Redlink Server - Problem

* The following is displayed after the boot icon is selected.

"Initializing Redlink Server with LPC432x_Redlink_V4_26.bin"

* After a short time the following is displayed:

"Timeout waiting for Redlink Server to initialize" ...

If NO is selected the same thing will happen ad-infinitum.

* The console displays the following text if the operation is cancelled.

[Started server]
[Connected on port 3025]

ISSUE: Can you explain what is happening and what one should see
at this point ?

0 Kudos

285 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by lpcxpresso-support on Sat May 17 11:56:35 MST 2014
Sorry, but Debian is not a supported Linux distro. All I can suggest is that you read the Linux install instructions in the user manual to see if that offers some clues as to what you need to do to make it work on Debian.
0 Kudos