I installed the device using the provided CD and the JTAG debugger
worked exactly once.
Now all I get is an error under Embedded GDB:
I posted this on the Sparkfun forum but haven't received a response.
It doesn't look good: another user posted the same question more than
a month ago without a response.
Anyone have any idea what's going on? I am using the provided Eclipse
3.2 and GNU toolchain. The program compiles and links and, in fact,
the first time the debugger worked, it downloaded the program properly.
Richard
Olimex ARM-USB-OCD Dongle
Started by ●September 18, 2007
Reply by ●September 18, 20072007-09-18
> -----Original Message-----
> From: l...
> [mailto:l...]On Behalf
> Of rtstofer
> Sent: Monday, September 17, 2007 9:34 PM
> To: l...
> Subject: [lpc2000] Olimex ARM-USB-OCD Dongle
> I installed the device using the provided CD and the JTAG debugger
> worked exactly once.
>
> Now all I get is an error under Embedded GDB:
> I posted this on the Sparkfun forum but haven't received a response.
> It doesn't look good: another user posted the same question more than
> a month ago without a response.
>
> Anyone have any idea what's going on? I am using the provided Eclipse
> 3.2 and GNU toolchain. The program compiles and links and, in fact,
> the first time the debugger worked, it downloaded the program
> properly.
>
> Richard
>
It is possible to disable the JTAG via software CRP protection. Is there
any chance you code does this? You might try to erase the part via the
serial ISP, and see if you can program via JTAG again.
Mike
> From: l...
> [mailto:l...]On Behalf
> Of rtstofer
> Sent: Monday, September 17, 2007 9:34 PM
> To: l...
> Subject: [lpc2000] Olimex ARM-USB-OCD Dongle
> I installed the device using the provided CD and the JTAG debugger
> worked exactly once.
>
> Now all I get is an error under Embedded GDB:
> I posted this on the Sparkfun forum but haven't received a response.
> It doesn't look good: another user posted the same question more than
> a month ago without a response.
>
> Anyone have any idea what's going on? I am using the provided Eclipse
> 3.2 and GNU toolchain. The program compiles and links and, in fact,
> the first time the debugger worked, it downloaded the program
> properly.
>
> Richard
>
It is possible to disable the JTAG via software CRP protection. Is there
any chance you code does this? You might try to erase the part via the
serial ISP, and see if you can program via JTAG again.
Mike
Reply by ●September 18, 20072007-09-18
Hiya-
I did the same thing with the Olimex Tiny JTAG debugger.
I am using an LPC2119, not the suggested 2148 chip. I had to change
the stack values of the linker file before I could get the debugger
to start working. My demo code did compile and link o.k. and I
think that it even loaded o.k. However, invoking the gdb requires
the stack be set up correctly (I think).
I believe that always did download the code to the micro (I'm using
the flash version of the demo), and that there was a fair amount of
FM (F#$King Magic), but the demo code does seem to start going
correctly.
If I might suggest, use the serial program code and load in a
different program (like blinking a different light) into the ARM. Get
it running.
Then try downloading the demo program and see if it indeed continues
to download the demo code to flash.
I have gotten my debugger to startup correctly with the demo fairly
reliably now that I made the mods to the linker file.
Interesting note that after powering down the evaluation board that
I'm using, removing the JTAG interface and powering up the evaluation
board, the demo program continues to run.
This is as of last Friday. I'll be continuing my efforts tomorrow!
Hope that this little bit from one ARM JTAG newbie to another helps.
If we can get the critters running, it certainly a low cost debug
toolchain.
Cheers,
Rich S.
--- In l..., "rtstofer" wrote:
>
> I installed the device using the provided CD and the JTAG debugger
> worked exactly once.
>
> Now all I get is an error under Embedded GDB:
> I posted this on the Sparkfun forum but haven't received a response.
> It doesn't look good: another user posted the same question more than
> a month ago without a response.
>
> Anyone have any idea what's going on? I am using the provided Eclipse
> 3.2 and GNU toolchain. The program compiles and links and, in fact,
> the first time the debugger worked, it downloaded the program properly.
>
> Richard
>
I did the same thing with the Olimex Tiny JTAG debugger.
I am using an LPC2119, not the suggested 2148 chip. I had to change
the stack values of the linker file before I could get the debugger
to start working. My demo code did compile and link o.k. and I
think that it even loaded o.k. However, invoking the gdb requires
the stack be set up correctly (I think).
I believe that always did download the code to the micro (I'm using
the flash version of the demo), and that there was a fair amount of
FM (F#$King Magic), but the demo code does seem to start going
correctly.
If I might suggest, use the serial program code and load in a
different program (like blinking a different light) into the ARM. Get
it running.
Then try downloading the demo program and see if it indeed continues
to download the demo code to flash.
I have gotten my debugger to startup correctly with the demo fairly
reliably now that I made the mods to the linker file.
Interesting note that after powering down the evaluation board that
I'm using, removing the JTAG interface and powering up the evaluation
board, the demo program continues to run.
This is as of last Friday. I'll be continuing my efforts tomorrow!
Hope that this little bit from one ARM JTAG newbie to another helps.
If we can get the critters running, it certainly a low cost debug
toolchain.
Cheers,
Rich S.
--- In l..., "rtstofer" wrote:
>
> I installed the device using the provided CD and the JTAG debugger
> worked exactly once.
>
> Now all I get is an error under Embedded GDB:
> I posted this on the Sparkfun forum but haven't received a response.
> It doesn't look good: another user posted the same question more than
> a month ago without a response.
>
> Anyone have any idea what's going on? I am using the provided Eclipse
> 3.2 and GNU toolchain. The program compiles and links and, in fact,
> the first time the debugger worked, it downloaded the program properly.
>
> Richard
>
Reply by ●September 18, 20072007-09-18
> I am using the provided Eclipse 3.2 and GNU
toolchain.
For what it's worth, the combination of Eclipse 3.2 / GDB 6.x /
OpenOCD-2007re141 was EXTREMELY unreliable for me; my research a month
ago found a number of people that agreed.
I fell back on the unlikely combination of Eclipse/YAGARTO as devel
and build tools, with a Keil uLink2 and an eval copy of uVision3 as
downloader and (raw memory image only) debugger. Using the -dS
options of arm-elf-objdump gave me a good disassembly listing to back
up the raw hexadecimal I get from the uLink2.
I haven't looked to see if anyone is focusing more on the
Eclipse/GDB/OpenOCD stability issues, but then, I don't really have
the time to, right now.
Regards,
Howard
For what it's worth, the combination of Eclipse 3.2 / GDB 6.x /
OpenOCD-2007re141 was EXTREMELY unreliable for me; my research a month
ago found a number of people that agreed.
I fell back on the unlikely combination of Eclipse/YAGARTO as devel
and build tools, with a Keil uLink2 and an eval copy of uVision3 as
downloader and (raw memory image only) debugger. Using the -dS
options of arm-elf-objdump gave me a good disassembly listing to back
up the raw hexadecimal I get from the uLink2.
I haven't looked to see if anyone is focusing more on the
Eclipse/GDB/OpenOCD stability issues, but then, I don't really have
the time to, right now.
Regards,
Howard
Reply by ●September 18, 20072007-09-18
--- In l..., "rtstofer" wrote:
>
> I installed the device using the provided CD and the JTAG debugger
> worked exactly once.
>
> Now all I get is an error under Embedded GDB:
> I posted this on the Sparkfun forum but haven't received a response.
> It doesn't look good: another user posted the same question more than
> a month ago without a response.
>
> Anyone have any idea what's going on? I am using the provided Eclipse
> 3.2 and GNU toolchain. The program compiles and links and, in fact,
> the first time the debugger worked, it downloaded the program properly.
>
> Richard
>
Thanks to Dominic, it is resolved under WinXP by installing the
provided drivers from the factory installation and then installing
YAGARTO. After everything was working with YAGARTO installation, I
deleted the Olimex GCCFD subdirectory.
My next adventure will be to get it working under Linux.
Richard
>
> I installed the device using the provided CD and the JTAG debugger
> worked exactly once.
>
> Now all I get is an error under Embedded GDB:
> I posted this on the Sparkfun forum but haven't received a response.
> It doesn't look good: another user posted the same question more than
> a month ago without a response.
>
> Anyone have any idea what's going on? I am using the provided Eclipse
> 3.2 and GNU toolchain. The program compiles and links and, in fact,
> the first time the debugger worked, it downloaded the program properly.
>
> Richard
>
Thanks to Dominic, it is resolved under WinXP by installing the
provided drivers from the factory installation and then installing
YAGARTO. After everything was working with YAGARTO installation, I
deleted the Olimex GCCFD subdirectory.
My next adventure will be to get it working under Linux.
Richard
Reply by ●September 19, 20072007-09-19
Hello,
You may be able to find a permanent and good solution to your problem
if you can have a look at the Eclipse based TRITON IDE and USB based
JTAG debugger provided at the following link.
You can opt for the eval. version of the IDE as well.
I found it pretty useful for all kinds of development and porting
purposes.
--- In l..., "zentiggr" wrote:
>
> > I am using the provided Eclipse 3.2 and GNU toolchain.
>
> For what it's worth, the combination of Eclipse 3.2 / GDB 6.x /
> OpenOCD-2007re141 was EXTREMELY unreliable for me; my research a month
> ago found a number of people that agreed.
>
> I fell back on the unlikely combination of Eclipse/YAGARTO as devel
> and build tools, with a Keil uLink2 and an eval copy of uVision3 as
> downloader and (raw memory image only) debugger. Using the -dS
> options of arm-elf-objdump gave me a good disassembly listing to back
> up the raw hexadecimal I get from the uLink2.
>
> I haven't looked to see if anyone is focusing more on the
> Eclipse/GDB/OpenOCD stability issues, but then, I don't really have
> the time to, right now.
>
> Regards,
> Howard
>
You may be able to find a permanent and good solution to your problem
if you can have a look at the Eclipse based TRITON IDE and USB based
JTAG debugger provided at the following link.
You can opt for the eval. version of the IDE as well.
I found it pretty useful for all kinds of development and porting
purposes.
--- In l..., "zentiggr" wrote:
>
> > I am using the provided Eclipse 3.2 and GNU toolchain.
>
> For what it's worth, the combination of Eclipse 3.2 / GDB 6.x /
> OpenOCD-2007re141 was EXTREMELY unreliable for me; my research a month
> ago found a number of people that agreed.
>
> I fell back on the unlikely combination of Eclipse/YAGARTO as devel
> and build tools, with a Keil uLink2 and an eval copy of uVision3 as
> downloader and (raw memory image only) debugger. Using the -dS
> options of arm-elf-objdump gave me a good disassembly listing to back
> up the raw hexadecimal I get from the uLink2.
>
> I haven't looked to see if anyone is focusing more on the
> Eclipse/GDB/OpenOCD stability issues, but then, I don't really have
> the time to, right now.
>
> Regards,
> Howard
>
Reply by ●September 19, 20072007-09-19
>
> Save yourself some time:
> http://www.openhardware.net/Embedded_ARM/OpenOCD_JTAG/
>
> TomW
>
Dominic put me on to your site yesterday. I got the dongle working
from Telnet and, apparently, from gdb. I think it even works from
Insight but I'm a little iffy on that.
I really want it to work from inside Eclipse using the zylin CDT
plug-in. Unfortunately, the instructions at the zylin site are not
helpful.
For a fresh install, the part where it says
"Delete previous CDT and Zylin Embedded CDT directories from
eclipse\features and eclipse\plugins directory."
would appear to not apply. But, no matter how I try to install the
gadgets, the project creation (File->New->Project) part of Eclipse
breaks. There is no way to create a new project.
The next instruction
"unzip embeddedcdt-200xmmdd.zip and zylincdt-200xmmdd.zip to the
Eclipse directory."
should probably be to put the .zip files IN the Eclipse directory and
THEN unzip to install the files.
Whether or not Embedded-gdb will work is pretty academic if a project
can't be created.
I am using the freshly installed Eclipse 3.3 without the plug-ins and
it works fine.
One approach I tried was to copy the directories from the YAGARTO
install to the Linux install - just the .jar files. No such luck!
The only positive thing to come of this is that the YAGARTO install
works properly.
There is always the possibility that the plug-ins won't work on a
x86-64. There are certainly other examples...
At the moment, I don't have the interest to chase this thing down a
rat hole. I'm working on other things.
Richard
> Save yourself some time:
> http://www.openhardware.net/Embedded_ARM/OpenOCD_JTAG/
>
> TomW
>
Dominic put me on to your site yesterday. I got the dongle working
from Telnet and, apparently, from gdb. I think it even works from
Insight but I'm a little iffy on that.
I really want it to work from inside Eclipse using the zylin CDT
plug-in. Unfortunately, the instructions at the zylin site are not
helpful.
For a fresh install, the part where it says
"Delete previous CDT and Zylin Embedded CDT directories from
eclipse\features and eclipse\plugins directory."
would appear to not apply. But, no matter how I try to install the
gadgets, the project creation (File->New->Project) part of Eclipse
breaks. There is no way to create a new project.
The next instruction
"unzip embeddedcdt-200xmmdd.zip and zylincdt-200xmmdd.zip to the
Eclipse directory."
should probably be to put the .zip files IN the Eclipse directory and
THEN unzip to install the files.
Whether or not Embedded-gdb will work is pretty academic if a project
can't be created.
I am using the freshly installed Eclipse 3.3 without the plug-ins and
it works fine.
One approach I tried was to copy the directories from the YAGARTO
install to the Linux install - just the .jar files. No such luck!
The only positive thing to come of this is that the YAGARTO install
works properly.
There is always the possibility that the plug-ins won't work on a
x86-64. There are certainly other examples...
At the moment, I don't have the interest to chase this thing down a
rat hole. I'm working on other things.
Richard
Reply by ●September 19, 20072007-09-19
rtstofer wrote:
>
> --- In lpc2000@yahoogroups .com ,
> "rtstofer" wrote:
> >
> > I installed the device using the provided CD and the JTAG debugger
> > worked exactly once.
> >
> > Now all I get is an error under Embedded GDB:
> >
> >
> > I posted this on the Sparkfun forum but haven't received a response.
> > It doesn't look good: another user posted the same question more than
> > a month ago without a response.
> >
> > Anyone have any idea what's going on? I am using the provided Eclipse
> > 3.2 and GNU toolchain. The program compiles and links and, in fact,
> > the first time the debugger worked, it downloaded the program properly.
> >
> > Richard
> > Thanks to Dominic, it is resolved under WinXP by installing the
> provided drivers from the factory installation and then installing
> YAGARTO. After everything was working with YAGARTO installation, I
> deleted the Olimex GCCFD subdirectory.
>
> My next adventure will be to get it working under Linux.
>
Save yourself some time:
http://www.openhardware.net/Embedded_ARM/OpenOCD_JTAG/
TomW
--
Tom Walsh - WN3L - Embedded Systems Consultant
http://openhardware.net http://cyberiansoftware.com http://openzipit.org
"Windows? No thanks, I have work to do..."
----------------
>
> --- In lpc2000@yahoogroups .com ,
> "rtstofer" wrote:
> >
> > I installed the device using the provided CD and the JTAG debugger
> > worked exactly once.
> >
> > Now all I get is an error under Embedded GDB:
> >
> >
> > I posted this on the Sparkfun forum but haven't received a response.
> > It doesn't look good: another user posted the same question more than
> > a month ago without a response.
> >
> > Anyone have any idea what's going on? I am using the provided Eclipse
> > 3.2 and GNU toolchain. The program compiles and links and, in fact,
> > the first time the debugger worked, it downloaded the program properly.
> >
> > Richard
> > Thanks to Dominic, it is resolved under WinXP by installing the
> provided drivers from the factory installation and then installing
> YAGARTO. After everything was working with YAGARTO installation, I
> deleted the Olimex GCCFD subdirectory.
>
> My next adventure will be to get it working under Linux.
>
Save yourself some time:
http://www.openhardware.net/Embedded_ARM/OpenOCD_JTAG/
TomW
--
Tom Walsh - WN3L - Embedded Systems Consultant
http://openhardware.net http://cyberiansoftware.com http://openzipit.org
"Windows? No thanks, I have work to do..."
----------------
