Trouble setting up the Eclipse development environment under Vista
PeterW
I'm trying to set up eclips'Project-Properties-e as outlined in the
instructions on the wiki, and I' can;t get vista to let me change the
setting under Project->Properties->....C/C++ Build->Settings...
I can't make changes to addr2line and c++filt.. I change them and say
apply and OK and then chaneck them again.. and they are un-changed...
The most infuriating thing is that I CAN change project->Properties-
>...Build->Discovery Optiojns to read and remeber 'arm-elf-gcc' for
the Compiler invocation command"
What the heck... is going on...
I HATE VISTA.
Peter
Dan Foisy
I'm sorry but I can't help here (I personally run XP and FC7)- maybe
someone else has some insight, perhaps on an Eclipse forum or FAQ? I
can tell you that all settings are stored in files, not on the registry
- is it possible those files are set as read-only?
Dan
--
Daniel Foisy
Virtual Cogs Embedded Systems Inc.
Unit 4, 5694 Highway 7 East, Suite 311
Markham, Ontario, Canada L3P 1B4
www.virtualcogs.com
416-238-2231
"Your future is modular"
PeterW
Appreciate the rapid response, and I tend to agree it looks like a
read only problem... but the fact that I can set some options and not
others is very odd... unless there are multiple files that these
configs get written to. Any idea where these might be ?
After looking into the read only aspect of the problem on various
Vista support forums nothing has worked, it looks like its likely to
be a problem with Vistas new permissions policies(directories
apparently don;t have a read only property, but it seems to be set on
most of the problem directories i look at and it can't be un-set...by
me anyway). I'm an admininstrator user on the box, and the eclipse and
projects are all stored in either c:\ or y:\ in directories created
during the install or specifically by me... there SHOULD be no
permissions problems ..
I'm a Solaris and Linux user myself so windows is a bit of a foreign
land to me... I'm struggling to find GUI equivalents to simple CLI
commands to change permissions and look at . files etc...
What OS setup do you use... where do you put the following parts of
the setup...and where can I get the parts from.. I'll build a systems
specifically to get this working if I have to... life should be ea
sier.
Specifically where do you put (and obtain ) the following components.
- USB drivers for Olimex Tiny USB JTAG device (had to change the .inf
files for correct VID/PID numbers/ to install)
- OpenOCD binaries
- arm-elf-**** associated tools
- cygwin (or native linux.. which versions and patches)
- Java JRE
- Eclipse
I notice that if I blindly use the install CD from olimex it installs
more or less all the parts required (and sometimes multiple copies)but
not in the way your installation wiki recommends, and its a nightmare
to get rid of all the bits and start over with a clean system.
Peter
>
> - Show quoted text -
Dan Foisy
PeterW wrote:
> Dan,
>
> Appreciate the rapid response, and I tend to agree it looks like a
> read only problem... but the fact that I can set some options and not
> others is very odd... unless there are multiple files that these
> configs get written to. Any idea where these might be ?
I believe in the workspace/.metadata directory, but I'm not an eclipse
expert
>
> After looking into the read only aspect of the problem on various
> Vista support forums nothing has worked, it looks like its likely to
> be a problem with Vistas new permissions policies(directories
> apparently don;t have a read only property, but it seems to be set on
> most of the problem directories i look at and it can't be un-set...by
> me anyway). I'm an admininstrator user on the box, and the eclipse and
> projects are all stored in either c:\ or y:\ in directories created
> during the install or specifically by me... there SHOULD be no
> permissions problems ..
>
> I'm a Solaris and Linux user myself so windows is a bit of a foreign
> land to me... I'm struggling to find GUI equivalents to simple CLI
> commands to change permissions and look at . files etc...
I have cygwin installed, which gives you many of those tools - I'm
hardpressed to say which are native windows and which are from Cygwin
(i.e. I can use "ls" in either case, don't believe that's Windows)
>
> What OS setup do you use... where do you put the following parts of
> the setup...and where can I get the parts from.. I'll build a systems
> specifically to get this working if I have to... life should be ea
> sier.
> Specifically where do you put (and obtain ) the following components.
>
> - USB drivers for Olimex Tiny USB JTAG device (had to change the .inf
> files for correct VID/PID numbers/ to install)
> - OpenOCD binaries
both are in c:\program files\openocd-r520
> - arm-elf-**** associated tools
f:\gnuarm
> - cygwin (or native linux.. which versions and patches)
f:\cygwin
> - Java JRE
c:\program files\java
> - Eclipse
That was on an old development machine - don't really use it for my own
dev work but it can be installed pretty much wherever. In Windows, I
use Notepad++
>
> I notice that if I blindly use the install CD from olimex it installs
> more or less all the parts required (and sometimes multiple copies)but
> not in the way your installation wiki recommends, and its a nightmare
> to get rid of all the bits and start over with a clean system.
>
We had thoughts of a VM or an installer at one point. Neither is ideal
for (say) half of our customers. The VM ends up being many GB
unfortunately. We're revisiting the situation for our next gen product
line as its build system requires Linux - don't believe Cygwin will work.
PeterW
instructions you need to add c:\gnuarm\arm-elf\bin to the path as well
as c:\gnuarm\bin, but I also noted that the install of CygWin had not
added itself to the path so had to add c:\cygwin\bin to the path...
this allows compilations to work and seems to allow me to get right to
the point of debugging the ledblink program which then fails with the
following error...
In the Debug window in the Debug Perspective..
- OpenOCD is running and happy(as far as I can tell)
- ledblink [Zylin Embedded debug (Cygwin)]
Embedded GDB(4/26/08 11:03 AM)(Suspended) <Don't know how to run.
Try "help target".>
And a dialogue pops us saying the same thing"
Any clues... ?
Dan Foisy
I'm not sure what may be going wrong but you might to look at this page:
http://www.makingthings.com/documentation/tutorial/debug-with-openocd/configure-eclipse
Dan
--
PeterW
I got Crossworks 1.7 working with the Olimex ARM-USB-TINY and the VC21
working on a PC running Ubuntu 8.04...
I'm using the following setup..
- Crossworks 1.7 (eval.. but I'll be buying it.)
- Olimex AMR-USB-TINY JTAG
- Virtual Cogs VC21 (VCMX212 board)
- on top of Ubuntu 8.04 (Hardy heron)
So here is what I had to do..
So that Crossworks can run as a user other than 'root', and yet still
have access to the USB debugger i had to give other users permission
to use USB devices, this involves adding a new file (as root) called /
etc/udev/rules.d/45-olimex.rules
this contains the following lines..
------------------------------------------------------------------------------
BUS!="usb", ACTION!="add", SUBSYSTEM!=="usb_device",
GOTO="olimex_rules_end"
SYSFS{idProduct}=="0003", SYSFS{idVendor}=="15ba", MODE="666",
GROUP="usb"
SYSFS{idProduct}=="0004", SYSFS{idVendor}=="15ba", MODE="666",
GROUP="usb"
LABEL="olimex_rules_end"
-------------------------------------------------------------------------------
This works for my ARM-USB-TINY, but I believe it will also work for
the ARM-USB-OCD.
Then... in the target config section for the 'Olimex ARM-USB-TINY' ->
JTAG section, set the following...
Fast Memory Access : NO
Identify Target : YES
JTAG Clock Divider : 4
nTRST open Drain : NO
...
Thats it.. :D
> I'm not sure what may be going wrong but you might to look at this page:http://www.makingthings.com/documentation/tutorial/debug-with-openocd...