LPCXpresso IDEのトピックRe: LPCXpresso v7.3.0 problem on OS X???

LPCXpresso v7.3.0 problem on OS X???

lpcware — Wed, 15 Jun 2016 22:03:05 GMT

Content originally posted in LPCWare by s1d on Fri Jul 25 15:50:51 MST 2014
Hi

I recently installed v7.3.0 on my Mac. Since I can not connect to the hardware anymore.

The error message says:
Redlink Server not found.
This could be because it is disconnected, not powered, or already in use.

In v7.2 everything still works as expected.

Did I miss something to port???

I am using Mac OSX 10.9.4

Greetings
Juergen

Re: LPCXpresso v7.3.0 problem on OS X???

lpcware — Wed, 15 Jun 2016 22:03:06 GMT

Content originally posted in LPCWare by lpcxpresso-support on Sat Jul 26 01:44:48 MST 2014
I do not recognise that as an error message. Please post the EXACT text of the message, and also explain what you target is and how you are connecting it.

Re: LPCXpresso v7.3.0 problem on OS X???

lpcware — Wed, 15 Jun 2016 22:03:07 GMT

Content originally posted in LPCWare by s1d on Sat Jul 26 16:10:15 MST 2014
Hi

thanks for the quick reply.

I have got two LPC11U68 Xpresso V2 Rev B boards. Using the LPCXpresso v7.2 works perfectly on my Mac OSX.

I installed v7.3.0 in parallel (different directory) and used the same workspace as for the old SDK. The new one simply does not find the probe.
On clicking on "debug" the SDK compiles the code and starts the redlink server. After a while a window pops up stating the text above. It is the same window as I would have forgotten to plug the board into the USB port of my Mac. Except the hardware is plugged in correctly and clicking the "Search for Redlink Server again" button has no effect.

Thanks
Juergen

Re: LPCXpresso v7.3.0 problem on OS X???

lpcware — Wed, 15 Jun 2016 22:03:07 GMT

Content originally posted in LPCWare by lpcxpresso-support on Sun Jul 27 11:08:54 MST 2014
As far as LPC-Link2 debug drivers and Redlink is concerned, v7.3.0 is almost identical to v7.2.0.
When you are unable to connect to Link2 with v7.3.0, what happens when you try v7.2 - without touching ANY hardware?
Please can you post the Debug Log and Redlink Server consoles for working and non-working system.
Debug log info can be found here:
http://www.lpcware.com/content/faq/lpcxpresso/debug-log
Also, see this FAQ:
http://www.lpcware.com/content/faq/lpcxpresso/booting-lpc-link2

Re: LPCXpresso v7.3.0 problem on OS X???

lpcware — Wed, 15 Jun 2016 22:03:08 GMT

Content originally posted in LPCWare by lpcxpresso-support on Mon Jul 28 03:01:37 MST 2014
One other thing to note is that the Redlink server and firmware are specific to a particular version of LPCXpresso IDE. This is generally not a problem, but if you are switching between two different versions of the IDE, make sure that after stopping the debug session from one IDE version and before starting a debug session from the other version - you should power down the Link2 hardware, and also ensure that any redlinkserv processes are killed.

Regards,
LPCXpresso Support

Re: LPCXpresso v7.3.0 problem on OS X???

lpcware — Wed, 15 Jun 2016 22:03:09 GMT

Content originally posted in LPCWare by s1d on Mon Jul 28 14:48:53 MST 2014
Hi,

Sorry for the delay... Currently I am quit busy...

Disconnecting everything before starting v7.3 did not change a thing.
Tomorrow I check the logs (as proposed in the post before) and report back to you ASAP.

Thanks
Juergen

Re: LPCXpresso v7.3.0 problem on OS X???

lpcware — Wed, 15 Jun 2016 22:03:09 GMT

Content originally posted in LPCWare by s1d on Tue Jul 29 13:54:03 MST 2014
Hi,

I did the following: I connected the hardware correctly and started the SDK v7.3.0. I got the following RedServer Log:
[Started server]
[Connected on port 3025]
redlink>
redlink>
redlink>
redlink>
redlink>
redlink>ProbeList
redlink>

After that, I closed the SDK and started the same project on v7.2.0 without touching any hardware. I got the following output and everything works:
[Started server]
[Connected on port 3025]
redlink>
redlink>
redlink>
redlink>
redlink>
redlink>
redlink>ProbeList
Index = 1
Manufacturer = NXP Semiconductors
Description = LPCLINK2 Redlink
VID = 21BD, PID=0006
Path = USB_21bd_0006_14110000
redlink>
redlink>ProbeStatus
Index = 1
Manufacturer = NXP Semiconductors
Description = LPCLINK2 Redlink
VID = 21BD, PID=0006
Path = USB_21bd_0006_14110000
IsOpen = FALSE
WireInitialized = FALSE
WireProtocol = JTAG
CoresConfigured = FALSE
PacketSize = 64
Probe Reference Count = 0
HasSWV = FALSE
HasETM = FALSE
HasJTAG = TRUE
HasSWD = TRUE
Probe Type = REDLINK
redlink>
redlink>
redlink>
redlink>
redlink>ProbeIsOpen 1
FALSE
redlink>ProbeOpenByIndex 1
Handle = 0x00000001 = 1
redlink>WireIsConnected 1
FALSE
redlink>WireSwdConnect 1
DpID = 0BC11477
redlink>CoresConfigured 1
FALSE
redlink>CoreConfig 1
Number of CORES/TAPs = 1, Fully recognized: True
redlink>
redlink>

Regards,
Juergen

Re: LPCXpresso v7.3.0 problem on OS X???

lpcware — Wed, 15 Jun 2016 22:03:10 GMT

Content originally posted in LPCWare by lpcxpresso-support on Wed Jul 30 02:00:48 MST 2014
First of all, let me assure you that we see no issues with running on Mac OS X here. In fact a large proportion of our team use a variety of Mac's, with OS versions from Lion onwards. We have never seen a case of LPCXpresso 7.2.0 working and 7.3.0 not in the manner you describe.

For our reference can you confirm what Mac model are you using, as displayed in the "About this Mac" menu entry - e.g Macbook Pro 15inch, Early 2011, 2.2HGhz Intel Core i7, 16 GB.

Anyway, I suggest that we try starting from first principles in order to try to track down the cause of your problems.

First of all reboot your Mac, ensuring that you have the bare minimum of devices connected to USB. Also don't have your LPCXpresso11U68 board connected at this point.

Once you Mac has started up, check the firewall settings. Both lpcxpresso.app and redlinkserv should be set to allow incoming connections. You will need to ensure this is the case for each LPCXpresso version that you have installed. Thus as you have 7.2.0 and 7.3.0 you should see two of each.

Now start LPCXpresso 7.3.0 with a fresh workspace.

From the IDE, open a terminal using the status bar shortcut

http://www.lpcware.com/content/faq/lpcxpresso/status-bar-shortcuts

In the terminal window, enter the following command to list the USB devices connected to your Mac:

system_profiler SPUSBDataType

At this point, connect an LPCXpresso11U68 board, and run the system_profiler command again.

You should see an extra device appear in the list of devices-

LPC:

Product ID: 0x000c
Vendor ID: 0x1fc9 (NXP Semiconductors)
Version: 1.00
Serial Number: ABCD
Speed: Up to 480 Mb/sec
Manufacturer: NXP
Location ID: 0xfd124400 / 7
Current Available (mA): 500
Current Required (mA): 100

Do you? Assuming that you do, boot it by typing the following command into the terminal

boot_link2
[For details - see http://www.lpcware.com/content/faq/lpcxpresso/booting-lpc-link2]

which should give output similar to:

Looking for DFU devices...
dfu-util -d 0x1fc9:0x000c -c 0 -i 0 -t 2048 -R -D /Applications/lpcxpresso_7.3.0_186/lpcxpresso/bin/LPC432x_Redlink_V4_46.bin.hdr
Booted LPC-Link2 (0x1fc9:0x000c) with LPC432x_Redlink_V4_46.bin.hdr

Now run the system_profiler command again. The LPC device previously shown should have been replaced with...

LPCLINK2 Redlink:

Product ID: 0x0006
Vendor ID: 0x21bd
Version: 1.00
Serial Number: ABCD123456789
Speed: Up to 480 Mb/sec
Manufacturer: NXP Semiconductors
Location ID: 0xfd124400 / 7
Current Available (mA): 500
Current Required (mA): 500

Now return to the IDE. Go to

Quickstart Panel - New Project - LPC11 / LPC12 - LPC11U6x - C project (Semihosted)

and create a new "hello world" project.

Use "Quickstart - Build" to build the project,

Go back to the terminal and enter the following command to list processes running:

ps -e

Now use "Quickstart - Debug" to start a debug session.

Does this debug session start successfully?

If not, then please run "ps -e" again in the terminal, and supply:

1) The full contents of your terminal (ie the commands given above, and the output they generated.

2) The debug log generated from the attempt to start the debug session:

http://www.lpcware.com/content/faq/lpcxpresso/debug-log

3) The redlink server log (available from another drop down in the Console view).

Regards,
LPCXpresso Support

Re: LPCXpresso v7.3.0 problem on OS X???

lpcware — Wed, 15 Jun 2016 22:03:11 GMT

Content originally posted in LPCWare by s1d on Wed Jul 30 14:57:41 MST 2014
Hi

first of all thank you very much for spending so much time on me!

Short story: I had no luck...

Long story:

I have an up to date iMac 27-inch, Late 2013 running on OSX 10.9.4
I have two more Macs (Macbook Air and Pro) lying around here. I can test them too, if you wish.

My firewall is turned off.

I did everything exactly as you asked for. Except, I installed the lpcopen_2_06_lpcxpresso_nxp_lpcxpresso_11u68.zip into the new workspace prior to starting the terminal.
Everything works correctly until I press the debug button. At this point, the hardware can not be found, as always on v7.3.0.

The console log is attached.

The redlink log (I tried it twice):
[Started server]
[Connected on port 3025]
redlink>
redlink>
redlink>
redlink>
redlink>
redlink>
redlink>ProbeList
redlink>
[Closed]
[Started server]
[Connected on port 3025]
redlink>ProbeList
redlink>
[Closed]
[Started server]
[Connected on port 3025]
redlink>
redlink>
redlink>
redlink>
redlink>
redlink>ProbeList
redlink>
[Closed]
[Started server]
[Connected on port 3025]
redlink>ProbeList
redlink>

Building:
23:45:02 **** Build of configuration Debug for project helloWorld ****
make all
Building file: ../src/aeabi_romdiv_patch.s
Invoking: MCU Assembler
arm-none-eabi-gcc -c -x assembler-with-cpp -D__REDLIB__ -DDEBUG -D__CODE_RED -D__USE_ROMDIVIDE -g3 -mcpu=cortex-m0 -mthumb -specs=redlib.specs -o "src/aeabi_romdiv_patch.o" "../src/aeabi_romdiv_patch.s"
Finished building: ../src/aeabi_romdiv_patch.s

Building file: ../src/cr_startup_lpc11u6x.c
Invoking: MCU C Compiler
arm-none-eabi-gcc -D__REDLIB__ -DDEBUG -D__CODE_RED -DCORE_M0PLUS -D__MTB_BUFFER_SIZE=256 -D__USE_ROMDIVIDE -D__LPC11U6X__ -Og -g3 -Wall -c -fmessage-length=0 -fno-builtin -ffunction-sections -fdata-sections -mcpu=cortex-m0 -mthumb -specs=redlib.specs -MMD -MP -MF"src/cr_startup_lpc11u6x.d" -MT"src/cr_startup_lpc11u6x.o" -MT"src/cr_startup_lpc11u6x.d" -o "src/cr_startup_lpc11u6x.o" "../src/cr_startup_lpc11u6x.c"
Finished building: ../src/cr_startup_lpc11u6x.c

Building file: ../src/crp.c
Invoking: MCU C Compiler
arm-none-eabi-gcc -D__REDLIB__ -DDEBUG -D__CODE_RED -DCORE_M0PLUS -D__MTB_BUFFER_SIZE=256 -D__USE_ROMDIVIDE -D__LPC11U6X__ -Og -g3 -Wall -c -fmessage-length=0 -fno-builtin -ffunction-sections -fdata-sections -mcpu=cortex-m0 -mthumb -specs=redlib.specs -MMD -MP -MF"src/crp.d" -MT"src/crp.o" -MT"src/crp.d" -o "src/crp.o" "../src/crp.c"
Finished building: ../src/crp.c

Building file: ../src/helloWorld.c
Invoking: MCU C Compiler
arm-none-eabi-gcc -D__REDLIB__ -DDEBUG -D__CODE_RED -DCORE_M0PLUS -D__MTB_BUFFER_SIZE=256 -D__USE_ROMDIVIDE -D__LPC11U6X__ -Og -g3 -Wall -c -fmessage-length=0 -fno-builtin -ffunction-sections -fdata-sections -mcpu=cortex-m0 -mthumb -specs=redlib.specs -MMD -MP -MF"src/helloWorld.d" -MT"src/helloWorld.o" -MT"src/helloWorld.d" -o "src/helloWorld.o" "../src/helloWorld.c"
Finished building: ../src/helloWorld.c

Building file: ../src/mtb.c
Invoking: MCU C Compiler
arm-none-eabi-gcc -D__REDLIB__ -DDEBUG -D__CODE_RED -DCORE_M0PLUS -D__MTB_BUFFER_SIZE=256 -D__USE_ROMDIVIDE -D__LPC11U6X__ -Og -g3 -Wall -c -fmessage-length=0 -fno-builtin -ffunction-sections -fdata-sections -mcpu=cortex-m0 -mthumb -specs=redlib.specs -MMD -MP -MF"src/mtb.d" -MT"src/mtb.o" -MT"src/mtb.d" -o "src/mtb.o" "../src/mtb.c"
Finished building: ../src/mtb.c

Building target: helloWorld.axf
Invoking: MCU Linker
arm-none-eabi-gcc -nostdlib -Xlinker -Map="helloWorld.map" -Xlinker --gc-sections -Xlinker --allow-multiple-definition -mcpu=cortex-m0 -mthumb -T "helloWorld_Debug.ld" -o "helloWorld.axf" ./src/aeabi_romdiv_patch.o ./src/cr_startup_lpc11u6x.o ./src/crp.o ./src/helloWorld.o ./src/mtb.o
Finished building target: helloWorld.axf

make --no-print-directory post-build
Performing post-build steps
arm-none-eabi-size "helloWorld.axf"; # arm-none-eabi-objcopy -v -O binary "helloWorld.axf" "helloWorld.bin" ; # checksum -p LPC11U68 -d "helloWorld.bin";
   text   data    bss    dec    hexfilename
11744      0    604 12348   303chelloWorld.axf

23:45:03 Build Finished (took 215ms)

The only other log I have is this:
710,376 2-gdb-exit
710,377 2^exit

I hope that helps.

Thanks
Juergen

Re: LPCXpresso v7.3.0 problem on OS X???

lpcware — Wed, 15 Jun 2016 22:03:11 GMT

Content originally posted in LPCWare by s1d on Wed Jul 30 15:27:32 MST 2014
I also have a LPC1769 board.
There, everything works fine on v7.3.0.

Debug message:
LPCXpresso Debug Driver v7.3 (Jul 2 2014 15:00:48 - crt_emu_cm3_nxp build 10)
Emu(0): Conn&Reset. DpID: 2BA01477. Info: LPCLINK
SWD Frequency: 3000 KHz. RTCK: False. Vector catch: False.
Packet delay: 0 Poll delay: 0.
Loaded LPC175x_6x_512.cfx: LPC175x_6x (512K) Jul 1 2014 11:51:13 On-chip Flash Memory
NXP: LPC1769 Part ID: 0x00000000
Connected: was_reset=false. was_stopped=false
v LPCXpresso Free License - Download limit is 256K
Writing 3580 bytes to address 0x00000000 in Flash
Erased/Wrote page 0-0 with 3580 bytes in 623msec
Flash Write Done
Flash Program Summary: 3580 bytes in 0.62 seconds (5.61 KB/sec)
nSRST assert (if available)
Executing in user flash.

Stopped: Breakpoint #1

But my two LPC11U68 refuse to work on v7.3

Juergen

Re: LPCXpresso v7.3.0 problem on OS X???

lpcware — Wed, 15 Jun 2016 22:03:12 GMT

Content originally posted in LPCWare by LessThanZero on Wed Jul 30 22:14:08 MST 2014

I run Maverick (i.e. 10.9.3), and I see no trouble. You mentioned your firewall is off, but double check. Have you tried running with the firewall on, and with a 7.3.0 redlinkserv entry set to allow incoming connections? It works either way for me. The probelist command returns a list of the enumerated devices it recognizes, or "No probes found". In your case, the server console shows probelist returned nothing, which I've never seen happen.

LessThanZero

Re: LPCXpresso v7.3.0 problem on OS X???

lpcware — Wed, 15 Jun 2016 22:03:13 GMT

Content originally posted in LPCWare by lpcxpresso-support on Wed Jul 30 23:24:00 MST 2014
Lets try something else.

Please try copying the redlinkserv executable from 7.2 to 7.3 and see if that makes any difference.

Re: LPCXpresso v7.3.0 problem on OS X???

lpcware — Wed, 15 Jun 2016 22:03:15 GMT

Content originally posted in LPCWare by s1d on Sun Aug 03 07:20:52 MST 2014
Hi

I found a working solution...

Let's sum things up:
-The LPC1769 works out of the box.
-Using the LPC11U68 board on v7.3 does not return anything when the device is probed ("redlink>ProbeList")

My workaround: I needed to copy the redlinkserv AND libredlink.dylib from v7.2 to v7.3.
As I have no source code I can not tell where things go wrong in the new version...

Regards
Juergen

Re: LPCXpresso v7.3.0 problem on OS X???

lpcware — Wed, 15 Jun 2016 22:03:15 GMT

Content originally posted in LPCWare by lpcxpresso-support on Sun Aug 03 09:56:49 MST 2014

Thanks for the feedback. We've so far been unable to reproduce your results on a number of Mac OS X machines, but we'll continue to investigate.

Regards,

LPCXpresso-Support

Re: LPCXpresso v7.3.0 problem on OS X???

lpcware — Wed, 15 Jun 2016 22:03:19 GMT

Content originally posted in LPCWare by mtb98 on Fri Aug 15 08:02:26 MST 2014
Exact same problem with Ubuntu 12.04 64 bit on desktop and laptop. Connects fine to probe Link2 on older versions but breaks with 7.3.0

Re: LPCXpresso v7.3.0 problem on OS X???

lpcware — Wed, 15 Jun 2016 22:03:19 GMT

Content originally posted in LPCWare by lpcxpresso-support on Fri Aug 15 08:17:55 MST 2014
Please explain exactly what you mean by "breaks". As we have said earlier in this thread, we are unable to reproduce any problems.

If you can, as well as describing the problem, please provide the output from lsusb.

Re: LPCXpresso v7.3.0 problem on OS X???

lpcware — Wed, 15 Jun 2016 22:03:20 GMT

Content originally posted in LPCWare by mtb98 on Fri Aug 15 19:09:11 MST 2014
Sorry for short description of problem. My system is
Ubuntu Release 12.04 (precise), 64-bit Kernel Linux 3.2.0-67-generic,

Thought the description above was pretty good. The probe looks good with the output of lsusb.
"Bus 002 Device 006: ID 1fc9:000c NXP Semiconductors" before attempt to connect. Then "Bus 002 Device 007: ID 21bd:0006" after attempt to connect.

Using LPCXpresso the message is "Redlink Server not found.
This could be because it is disconnected, not powered, or already in use." Looking at the Redlink server console with LPCXpresso see "[Started server]
[Closed]
[Started server]
[Closed]" with a single attempt to connect to target.

Re: LPCXpresso v7.3.0 problem on OS X???

lpcware — Wed, 15 Jun 2016 22:03:21 GMT

Content originally posted in LPCWare by lpcxpresso-support on Fri Aug 15 23:14:07 MST 2014
Sounds like you didn't follow all of the instruction for Linux...
http://www.lpcware.com/content/faq/lpcxpresso/linux-installation