topic LPC-Link connection problems in LPCXpresso IDE

LPC-Link connection problems

lpcware — Thu, 16 Jun 2016 00:59:33 GMT

Content originally posted in LPCWare by mbeale on Thu Apr 19 20:52:06 MST 2012
Environment: System Linux Ubuntu (Lucid) 10.04 (IA64), Debugging using Eclipse/Code-red (LPCXpresso_4.2.2_238_Linux-x86) with a LPC-Link JTAG interface pcb, Micro LPC1225.

Debugger reports following error:
No emulator/board available.
This could be because it is unpowered, disconnected or already in use

However am able to debug without problems while running as sudo (root). This problem has occurred with earlier versions of Code-red compilers. Appears to be an issue with permissions. Have tried other tip from the forum without success.

Any suggestions? Don't like running applications as super user unless I absolutely have to.

Thanks
malcolm

Re: LPC-Link connection problems

lpcware — Thu, 16 Jun 2016 00:59:34 GMT

Content originally posted in LPCWare by researchinnovation on Thu Apr 19 21:25:16 MST 2012
Hi....!!!

1.)Sometime for a board we use two USB cable connection, one for power and other one UART. So if we use single cable then it may not provide sufficient power to the board.
2.) Sometime we use different emulator and select different Emulator/hardware/processor/boardmodel(for example LPC1114/302) in the IDE(For example LPC1114/301) which does not match.
3.)Sometime we do not have Windows host/driver or FTDI driver or driver of right version according to PC(windows xp/vista, ubuntu etc.).
4.) Sometime if IDE is in running mode and want to run again then also it can show this error.
5.) Sometime Reset in the registers happen continuously .

Anyway..Just try. It might help you.

Thanks & Regards ...:)

Re: LPC-Link connection problems

lpcware — Thu, 16 Jun 2016 00:59:34 GMT

Content originally posted in LPCWare by CodeRedSupport on Fri Apr 20 00:15:11 MST 2012
This sounds like a permissions problem.

Accessing low-level USB drivers in Linux requires root access. When LPCXpresso is installed, it correctly sets the Debug drivers to run with root privileges. If these have been lost, then this explains your issue. To fix:

cd /usr/local/lpcxpresso<version>/lpcxpresso/bin
sudo chown root crt_emu* dfu-util
sudo chgrp root crt_emu* dfu-util
sudo chmod 6755 crt_emu* dfu-util

This will restore the Debug drivers to their installed state.

Re: LPC-Link connection problems

lpcware — Thu, 16 Jun 2016 00:59:35 GMT

Content originally posted in LPCWare by mbeale on Sun Apr 22 17:47:36 MST 2012

Quote: CodeRedSupport
This sounds like a permissions problem.

Accessing low-level USB drivers in Linux requires root access. When LPCXpresso is installed, it correctly sets the Debug drivers to run with root privileges. If these have been lost, then this explains your issue. To fix:

cd /usr/local/lpcxpresso<version>/lpcxpresso/bin
sudo chown root crt_emu* dfu-util
sudo chgrp root crt_emu* dfu-util
sudo chmod 6755 crt_emu* dfu-util

This will restore the Debug drivers to their installed state.

Hi SM,

Thanks for the feedback, tried your suggestion above but still same results (unable to find emulator). Please note I did check the file permissions for the dfu-util and crt_emu* (1 + 6 files) and they were all correctly set to 'root' privileges.

Reiterating, debug works fine when I run LPCXpresso as 'sudo'.

A point to note, after the initial installation of LPCXpresso_4.2.2_238_Linux-x86 I was able to run and debug without problems as a standard user. This issue occurred the next day after the machine had been shut down and rebooted. It appears some other file necessary for debug operation has been set with incorrect privileges.

Any suggestions?

Thanks
malcolm

Re: LPC-Link connection problems

lpcware — Thu, 16 Jun 2016 00:59:35 GMT

Content originally posted in LPCWare by gogamoga on Tue Apr 24 19:57:39 MST 2012
Unplug your LPCXpresso, plug it back,
Check permissions on usb device:

sudo lsusb | sed -n -e 's/bus \(.*\) device \(.*\):.*0471:df55.*/\/dev\/bus\/usb\/\1\/\2/Ip' | xargs ls -lha

Should read something like:

crw-rw-r-- 1 root usb 189, 4 Apr 25 05:40 /dev/bus/usb/001/005

You might need to add yourself to usb group to fix this issue

P.S just noticed you are on (IA64), might be and issue with 32bit libs.
check your libs with this:

ldconfig -p | sed -n -e 's/.* \(.*libusb\.so.*\)/\1/Ip' | xargs file -L

and if you dont see any 32bit libusb, possible solution might be in this thread: http://knowledgebase.nxp.com/showthread.php?t=3144

Re: LPC-Link connection problems

lpcware — Thu, 16 Jun 2016 00:59:36 GMT

Content originally posted in LPCWare by mbeale on Wed Apr 25 19:03:32 MST 2012

Quote: gogamoga
Unplug your LPCXpresso, plug it back,
Check permissions on usb device:

sudo lsusb | sed -n -e 's/bus \(.*\) device \(.*\):.*0471:df55.*/\/dev\/bus\/usb\/\1\/\2/Ip' | xargs ls -lha

Should read something like:

crw-rw-r-- 1 root usb 189, 4 Apr 25 05:40 /dev/bus/usb/001/005

You might need to add yourself to usb group to fix this issue

P.S just noticed you are on (IA64), might be and issue with 32bit libs.
check your libs with this:

ldconfig -p | sed -n -e 's/.* \(.*libusb\.so.*\)/\1/Ip' | xargs file -L

and if you dont see any 32bit libusb, possible solution might be in this thread: http://knowledgebase.nxp.com/showthread.php?t=3144

Hi Gogamoga,

First thanks for the feedback...

1. Ran the first long command string from your post and the results looked okay, they're listed below

crw-rw-r-- 1 root root 189, 132 2012-04-26 08:22 /dev/bus/usb/002/005

2. With reference to adding myself to the USB group - added myself to uucp group, and retired but no luck. Do I need to logout and back in order for uucp changes to be recognized by the system?

3. 2 command give an error but didn't explore further, the command string appeared to be correct though.

4. Looked at the 32bit libs reference towards end of your post, the libusb-1.0.so.0 is in the /lib directory, or rather a symlink to it is.

I did notice there was some discussion about using Ubuntu 12, I should be upgrading the system to the new 12.04 on 26 when the distribution is officially released and will try again, see what happens. Have read that lib hell is addressed in the new version.

Till then am continuing debug as sudo, if you have any other input I'll give it a go.

Again, your assistance is much appreciated.
malcolm

Re: LPC-Link connection problems

lpcware — Thu, 16 Jun 2016 00:59:37 GMT

Content originally posted in LPCWare by gogamoga on Wed Apr 25 23:37:00 MST 2012
Unplug, plug back, run this as normal user and post the results:

cd /usr/local/lpcxpresso<version>/lpcxpresso/bin
./dfu-util -d 0x471:0xdf55 -c 0 -t 2048 -R -D LPCXpressoWIN.enc

If the result reads something like that:

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

Opening USB Device 0x0471:0xdf55...
Claiming USB DFU Runtime Interface...
Cannot claim interface: could not claim interface 0: Operation not permitted

You are clearly dont have SUID on dfu-util, fix it with this:

sudo chmod +s dfu-util

If the output of dfu-util looks ok then try this:

./crt_emu_cm3_nxp -info-emu -wire=winusb

crt_emu_cm3_nxp output should read something like:

Ni: LPCXpresso Debug Driver v4.0 (Mar 25 2012 14:25:27)
1 Emulators available:
0. LPCLINK_1_1    LPC-Link Driver LINUX32 v1.1 (Code Red - LPCXpresso)

If you have this output there is no reason for lpcxpresso not to debug as normal user, but if it still doesnt work, then last solution - add udev rules:

First, make sure that you are in plugdev group, if not - add yourself :

 sudo usermod -a -G plugdev `whoami`

[COLOR=Red]
***Note: you need to restart X to make group addition take effect[/COLOR]

Then, run this:

sudo sh -c 'echo "# Rules for LPCXpresso DevBoard
SUBSYSTEM==\"usb\", ATTRS{idVendor}==\"0471\", ATTRS{idProduct}==\"df55\", MODE=\"0664\", GROUP=\"plugdev\"
SUBSYSTEM==\"usb\", ATTRS{idVendor}==\"1fc9\", ATTRS{idProduct}==\"0009\", MODE=\"0664\", GROUP=\"plugdev\"" > /etc/udev/rules.d/80-lpcxpresso.rules'
sudo restart udev

Unplug, Plug back and run:

sudo lsusb | sed -n -e 's/bus \(.*\) device \(.*\):.*0471:df55.*/\/dev\/bus\/usb\/\1\/\2/Ip' | xargs ls -lha

This should read something like:

crw-rw-r-- 1 root plugdev 189, 145 2012-04-26 17:35 /dev/bus/usb/002/018

[COLOR=Red]
***Notice the crw-rw-r-- permissions and plugdev group[/COLOR]

This should make it work, no matter if dfu-util is SUID or not
I cant think of anything else permission related that could go wrong there.

P.S
How many versions of LPCXpresso you have installed?

Re: LPC-Link connection problems

lpcware — Thu, 16 Jun 2016 00:59:38 GMT

Content originally posted in LPCWare by mbeale on Wed May 02 20:10:07 MST 2012

Quote: gogamoga
Unplug, plug back, run this as normal user and post the results:

cd /usr/local/lpcxpresso<version>/lpcxpresso/bin
./dfu-util -d 0x471:0xdf55 -c 0 -t 2048 -R -D LPCXpressoWIN.enc

If the result reads something like that:

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

Opening USB Device 0x0471:0xdf55...
Claiming USB DFU Runtime Interface...
Cannot claim interface: could not claim interface 0: Operation not permitted

You are clearly dont have SUID on dfu-util, fix it with this:

sudo chmod +s dfu-util

If the output of dfu-util looks ok then try this:

./crt_emu_cm3_nxp -info-emu -wire=winusb

crt_emu_cm3_nxp output should read something like:

Ni: LPCXpresso Debug Driver v4.0 (Mar 25 2012 14:25:27)
1 Emulators available:
0. LPCLINK_1_1    LPC-Link Driver LINUX32 v1.1 (Code Red - LPCXpresso)

 sudo usermod -a -G plugdev `whoami`

[COLOR=Red]
***Note: you need to restart X to make group addition take effect[/COLOR]

Then, run this:

sudo sh -c 'echo "# Rules for LPCXpresso DevBoard
SUBSYSTEM==\"usb\", ATTRS{idVendor}==\"0471\", ATTRS{idProduct}==\"df55\", MODE=\"0664\", GROUP=\"plugdev\"
SUBSYSTEM==\"usb\", ATTRS{idVendor}==\"1fc9\", ATTRS{idProduct}==\"0009\", MODE=\"0664\", GROUP=\"plugdev\"" > /etc/udev/rules.d/80-lpcxpresso.rules'
sudo restart udev

Unplug, Plug back and run:

sudo lsusb | sed -n -e 's/bus \(.*\) device \(.*\):.*0471:df55.*/\/dev\/bus\/usb\/\1\/\2/Ip' | xargs ls -lha

This should read something like:

crw-rw-r-- 1 root plugdev 189, 145 2012-04-26 17:35 /dev/bus/usb/002/018

Hi Gogamoga,

Ok, before I feedback on your suggestions, I've made some system changes but the results appear similar.

New OS Environment: Ubuntu Unity 12.04 LTS (64Bit)
Workstation Hardware: Dell Precision M6500 (unchanged from previous posts)

Clean install of Ubuntu Unity 12.04 LTS, installed LPCXpresso_4.2.2_238_Linux-X86, JTAG LPC-Link, target same as before.

After install debug works fine as normal user.

Reboot machine, unable to debug as user (same problem as earlier), works fine as 'sudo'.

With regard to your suggestions.
Closed LPCXpresso Eclipse, unplug LPC-Link and reconnected, output of first command follows:

cd /usr/local/lpcxpresso<version>/lpcxpresso/bin
./dfu-util -d 0x471:0xdf55 -c 0 -t 2048 -R -D LPCXpressoWIN.enc

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

Opening USB Device 0x0471:0xdf55...
Claiming USB DFU Runtime Interface...
Determining device status: state = dfuIDLE, status = 0
WARNING: Runtime device already in DFU state ?!?
Found Runtime: [0x0471:0xdf55] devnum=4, cfg=0, intf=0, alt=0, name="UNDEFINED"
Claiming USB DFU Interface...
Setting Alternate Setting ...
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
Transfer Size = 0x0800
LPCXpressoWin.enc: No such file or directory

Now if I startup LPCXpresso as standard user and attempt debug which fails as expected, I notice the USB ID of the device changed. The new ID is:

Running the same command as above produces the following results.

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

No DFU capable USB device found

Before I run the "sudo chmod +s dfu-util" command I check the permissions on dfu-util, they are correctly set to root, both the owner and group. Didn't run the command as I don't think it would have any effect.

Next command (note this is after attempting to debug in LPCXpresso, the result is the same if I unplug the LPC-Link and reconnect it, obviously the dfu-util was supposed to change the USB ID, so it no surprise)

./crt_emu_cm3_nxp -info-emu -wire=winusb
Ni: LPCXpresso Debug Driver v4.0 (Mar 25 2012 14:25:27)
0 Emulators available:

Next "sudo usermod -a -G plugdev `whoami`". Added myself to the plugdev group through Ubuntu's group management applet instead of using command line.

Okay, now the long shell command to create the "80-lpcxpresso.rules" file in the udev/rules.d directory. I took the short cut and running gedit under sudo created a file with the name and copied your strings to it, and restarted udev as indicated on the last line. Note - no file of this name existed in the directory, should there have been one?

Finally, unplugged the device and plugged it back in and ran:
sudo lsusb | sed -n -e 's/bus \(.*\) device \(.*\):.*0471:df55.*/\/dev\/bus\/usb\/\1\/\2/Ip' | xargs ls -lha

crw-rw-r-- 1 root root 189, 137 May 3 10:51 /dev/bus/usb/002/010

Restarted LPCXpresso as normal user and attempted debug but failed with same error.

I appreciate the time you've spent on looking at this problem. Just thought I'd provide the feedback so that anyone else with the same issue might find it helpful and if you're somehow connected with the LPCXpresso development project it might be useful feedback. I can continue embedded development using sudo until this is worked out.

I'm still not clear why debug always works fine the first time LPCXpresso is installed but fails thereafter when the machine is rebooted.

Thanx
Malcolm

Re: LPC-Link connection problems

lpcware — Thu, 16 Jun 2016 00:59:39 GMT

Content originally posted in LPCWare by gogamoga on Wed May 02 21:23:29 MST 2012

Quote: mbeale
...
cd /usr/local/lpcxpresso<version>/lpcxpresso/bin
./dfu-util -d 0x471:0xdf55 -c 0 -t 2048 -R -D LPCXpressoWIN.enc

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

Opening USB Device 0x0471:0xdf55...
Claiming USB DFU Runtime Interface...
Determining device status: state = dfuIDLE, status = 0
WARNING: Runtime device already in DFU state ?!?
Found Runtime: [0x0471:0xdf55] devnum=4, cfg=0, intf=0, alt=0, name="UNDEFINED"
Claiming USB DFU Interface...
Setting Alternate Setting ...
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
Transfer Size = 0x0800
LPCXpressoWin.enc: No such file or directory

my input reads: LPCXpresso[COLOR=Red]WIN[/COLOR].enc your input reads: LPCXpresso[COLOR=Red]Win[/COLOR].enc

notice the LOWERCASE part of LPCXpressoW[COLOR=Red]in[/COLOR].enc ???
Those things matter on linux - file names are case sensitive.

Quote:
...
Finally, unplugged the device and plugged it back in and ran:
sudo lsusb | sed -n -e 's/bus \(.*\) device \(.*\):.*0471:df55.*/\/dev\/bus\/usb\/\1\/\2/Ip' | xargs ls -lha

crw-rw-r-- 1 root [COLOR=Red]root[/COLOR] 189, 137 May 3 10:51 /dev/bus/usb/002/010

Again, part marked red is a group. It is clearly seen that its not plugdev but root
Which means - you have messed something with udev rules, which means again, you as a member of plugdev has no right to write to the device and here is your permission issue.

The reason is:

Quote:
...
Okay, now the long shell command to create the "80-lpcxpresso.rules" file in the udev/rules.d directory. I took the short cut and running gedit under sudo created a file with the name and copied your strings to it, and restarted udev as indicated on the last line. Note - no file of this name existed in the directory, should there have been one?

you either copy/paste the code that i gave, or edit with your editor, but!!!! remove the backslashes from quotes, which means, if you see '[COLOR=red]\"[/COLOR]' and edit the rules file with the editor you should replace it with '[COLOR=red]"[/COLOR]', or simplier copy/paste my input (this is the real shortcut lol)

Try again, fixing the issues i pointed out.

If you still want to use the gedit, put this into rules file: 80-lpcxpresso.rules

# Rules for LPCXpresso DevBoard
SUBSYSTEM=="usb", ATTRS{idVendor}=="0471", ATTRS{idProduct}=="df55", MODE="0664", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="1fc9", ATTRS{idProduct}=="0009", MODE="0664", GROUP="plugdev"

and dont forget to restart udev

PS.
The reason i wrote the commands i wrote in the previous post is to really give you a way to use console and not to rely on ubuntu gui.
Console is power. Do not rely on the gui. Read howtos and learn basic commands, this is linux after all, not windows. This is one of the things that annoys me in UBUNTU.

Re: LPC-Link connection problems

lpcware — Thu, 16 Jun 2016 00:59:39 GMT

Content originally posted in LPCWare by researchinnovation on Wed May 02 21:28:33 MST 2012
Excellent...!!!

Good work...!!!:)
Keep it up.

Re: LPC-Link connection problems

lpcware — Thu, 16 Jun 2016 00:59:40 GMT

Content originally posted in LPCWare by CodeRedSupport on Thu May 03 02:53:55 MST 2012
I can confirm that we have installed LPCXpresso on Ubuntu 12.04 in both 32-bit and 64-bit and have found no issues at all - everything works exactly as expected.

Note that running when on 64-bit version, you need to install the ia32 libraries:

sudo apt-get install ia32-libs-multiarch:i386

Apart from that, these were completely cleans installs with no other components added.

Re: LPC-Link connection problems

lpcware — Thu, 16 Jun 2016 00:59:40 GMT

Content originally posted in LPCWare by gogamoga on Thu May 03 03:08:02 MST 2012
He has it working as root so its not lib32 issues - its clearly permissions issue.
CodeRed should consider udev rules instead of suid root binaries in next release (IMHO)

Re: LPC-Link connection problems

lpcware — Thu, 16 Jun 2016 00:59:41 GMT

Content originally posted in LPCWare by CodeRedSupport on Thu May 03 04:31:59 MST 2012
This is something we have been investigating for a while and are currently testing. Perhaps you would like to beta test these rules?

[LIST]
[*]download and unzip the attachment
[*]copy the unzipped file to /etc/udev/rules.d
[*]restart the udev service (sudo service udev restart)
[/LIST]

These rules will make any of the supported devices world-write when attached. It will also automatically boot LPC-Link

Re: LPC-Link connection problems

lpcware — Thu, 16 Jun 2016 00:59:42 GMT

Content originally posted in LPCWare by gogamoga on Thu May 03 04:56:00 MST 2012
if you are going to use codered udev rules, make sure you remove the previous rule file you created

Re: LPC-Link connection problems

lpcware — Thu, 16 Jun 2016 00:59:42 GMT

Content originally posted in LPCWare by MacGyverQue on Thu May 03 08:14:21 MST 2012

Quote: CodeRedSupport
I can confirm that we have installed LPCXpresso on Ubuntu 12.04 in both 32-bit and 64-bit and have found no issues at all - everything works exactly as expected.

Note that running when on 64-bit version, you need to install the ia32 libraries:

sudo apt-get install ia32-libs-multiarch:i386

Apart from that, these were completely cleans installs with no other components added.

** Sorry to Thread Jack But.... **
I'm really happy to hear that there is hope for running LPCXpresso on Ubuntu 12, but I upgraded from 11 to 12 and am now running into licensing issues. Any suggestion? I posted a thread to the same effect.

Re: LPC-Link connection problems

lpcware — Thu, 16 Jun 2016 00:59:43 GMT

Content originally posted in LPCWare by CodeRedSupport on Thu May 03 09:21:52 MST 2012
Did you try deleting the license files and reactivating? /usr/share/LPCXpresso

We have found and fixed the issue you reported with the parse error, and that will be made available in the next release. However, is mentioned in your other post, Red Suite uses a completely different licensing system which is unaffected by this issue.

Re: LPC-Link connection problems

lpcware — Thu, 16 Jun 2016 00:59:43 GMT

Content originally posted in LPCWare by mbeale on Thu May 03 18:04:07 MST 2012

Quote: MacGyverQue
** Sorry to Thread Jack But.... **
I'm really happy to hear that there is hope for running LPCXpresso on Ubuntu 12, but I upgraded from 11 to 12 and am now running into licensing issues. Any suggestion? I posted a thread to the same effect.

Yes, I encountered the same debug license limit problem too, but did what CodeRedSupport suggested (delete license file and reactivate) and the issue cleared.

Re: LPC-Link connection problems

lpcware — Thu, 16 Jun 2016 00:59:44 GMT

Content originally posted in LPCWare by gogamoga on Fri May 04 01:34:05 MST 2012
Did you fix the permission issue?

Re: LPC-Link connection problems

lpcware — Thu, 16 Jun 2016 00:59:45 GMT

Content originally posted in LPCWare by mbeale on Fri May 04 02:55:23 MST 2012
Hi gogamoga

Quote: gogamoga
my input reads: LPCXpresso[COLOR=Red]WIN[/COLOR].enc your input reads: LPCXpresso[COLOR=Red]Win[/COLOR].enc

notice the LOWERCASE part of LPCXpressoW[COLOR=Red]in[/COLOR].enc ???
Those things matter on linux - file names are case sensitive.

Point taken, I appreciate the case sensitivity of Linux.

Quote:

Again, part marked red is a group. It is clearly seen that its not plugdev but root
Which means - you have messed something with udev rules, which means again, you as a member of plugdev has no right to write to the device and here is your permission issue.

I'm not sure how this was caused. I did modify the group settings for plugdev (added myself to it, but there's no reason it should have showed up as root)

Quote:

The reason is:
you either copy/paste the code that i gave, or edit with your editor, but!!!! remove the backslashes from quotes, which means, if you see '[COLOR=red]\"[/COLOR]' and edit the rules file with the editor you should replace it with '[COLOR=red]"[/COLOR]', or simplier copy/paste my input (this is the real shortcut lol)

Try again, fixing the issues i pointed out.

If you still want to use the gedit, put this into rules file: 80-lpcxpresso.rules

# Rules for LPCXpresso DevBoard
SUBSYSTEM=="usb", ATTRS{idVendor}=="0471", ATTRS{idProduct}=="df55", MODE="0664", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="1fc9", ATTRS{idProduct}=="0009", MODE="0664", GROUP="plugdev"

Again point taken, when I created the file using gedit I did take care to remove the unnecessary parts. The file was exactly as in your post.

Quote:

and dont forget to restart udev

Did that as you specified.

Quote:

PS.
The reason i wrote the commands i wrote in the previous post is to really give you a way to use console and not to rely on ubuntu gui.
Console is power. Do not rely on the gui. Read howtos and learn basic commands, this is linux after all, not windows. This is one of the things that annoys me in UBUNTU.

I appreciate your patience with someone not very familiar with Linux, I do come from a point-and-click background, but my command line skills are improving. I am also mid project and under pressure, the dev tool was giving me problems and therefore took the short cut. Some of the command line strings you sent me are quite long and typos can cause unforeseen errors as we see above.

Okay, now regarding feedback on current status; you may be able to understand what is taking place from events next.

I was encountering the code size limit error in debug as mentioned by other users. I un-installed LPCXpresso completely and reinstalled it, generated a new serial number and activation code, after which the code size errors were removed. However, I did notice that debug had started working again as a normal user.

At this point I needed to checkin some code to our svn repository, not having a suitable client I installed RapidSVN (via Ubuntu's software centre) and returned to LPCXpresso to continue working. At this point I found debug had quit operating and returned to its old behaviour.

Suspecting the installation of the new application had upset something, I un-installed LPCXpresso completely and reinstalled it as before. Again debug started working properly. To verify I did a complete system reboot and debug continued working.

I'm not sure how installing new software is handled by Ubuntu and its affects on LPCXpresso debug settings which seems to cause this trouble. As I had mentioned earlier it always worked the first time after installation, but since this is a new OS installation I had been adding other applications needed along the way.

I'm not saying this is the problem, but this is my observation at present.

Thanks again for all the assistance.
malcolm

PS: I did try the suggestion of the new rules file made by CodeRed support. But have removed it since and things are fine.

Re: LPC-Link connection problems

lpcware — Thu, 16 Jun 2016 00:59:45 GMT

Content originally posted in LPCWare by TheFallGuy on Fri May 04 03:17:22 MST 2012

Quote:

At this point I needed to checkin some code to our svn repository, not having a suitable client I installed RapidSVN (via Ubuntu's software centre) and returned to LPCXpresso to continue working.

Did you know that you can add Subversion directly into LPCXpresso, by installing the Subclipse plugin?
http://support.code-red-tech.com/CodeRedWiki/VersionControl