Re: [ECOS] Re: eCos invalidating JTAG on ARM architecture ?

[Sergei Gavrikov <w3sg at SoftHome dot net>]

On Thu, Jul 05, 2007 at 04:33:48PM +0200, Alexandre wrote:
> A little update on that, the problem does not occur if i use
> cyg_usr_start instead of main as an entry point.
> 

Hm, this your notice quite blocked all my suggestions for you :). Has
your evaluation board something like an ISP/RUN DIP switch? If it has,
try to connect to the board in ISP mode (so, the LPC bootloader isn't
eCos application) using OpenOCD/GDB and then set halt at 0 address or
just return that switch in RUN mode and do a reset. Do you use the
latest OpenOCD SVN build? Do you use the latest eCos CVS? Since 2007/02
hal/arm/arch/current/src/vectors.S had been fixed, that was a LPC
related fix (hal/arm/arch/current/ChangeLog). If you use any faked
binaries of OpenOCD for Windows, it's possible that stuff is obsolete.
Check it.  With 64K RAM you are needed in the JTAG so much. Try to look
through out the OpenOCD discuss lists: ask OpenOCD guys about your
issue. It looks like your problem isn't eCos related problem.

Happy eCosing,

	Sergei


> On 7/5/07, Alexandre <thekyz@gmail.com> wrote:
> >Hi everyone,
> >
> >I finally manage to run eCos on my eval board (yipee!) thanks to all
> >of you guys but i have a slight debugging problem (again i know, I'm a
> >problem maker -.-).
> >
> >After I upload my eCos code to my board via JTAG (code which is fully
> >functioning by the way), I can't by any mean reach it again via JTAG.
> >OpenOCD just says it can't communicate with my board. Seems like eCos
> >just disable my JTAG. The only way I can access my micro controller
> >again is by UART, erasing the flash using ISP, and then reflashing it
> >by JTAG works anew. So it works, but I can't debug the thing.
> >
> >I lurked through the mailing list to see if anything like that
> >happened to someone and couldn't find anything so my first guess is I
> >did something wrong (I'm a pessimistic person).
> >
> >There are two JTAGs available on my micro controller, one is supposed
> >to be always enabled when a definite input is pulled to LOW by
> >hardware means (which I've done, this is the way I manage to upload
> >the eCos code in the first ways). The second JTAG is enabled by
> >registry means.
> >
> >I tried to upload a dummy code without ecos and the first JTAG (the
> >hardware enabled) works perfectly without any init. The second one
> >(the software enabled) works also if I input the correct init (which I
> >did, I mean I managed to make it work ^^).
> >
> >But with eCos, neither works :(
> >I tried to put my init code from the dummy software in the eCos init
> >but I can't make the second JTAG work and the first one isn't working
> >either.
> >
> >I was guessing maybe eCos init for ARM (or maybe the olimex lpc2106
> >port) may have a thing which disable JTAG. Is it possible or did I do
> >something wrong and JTAG should work with eCos ?
> >
> >For reference I use an LPC2106 ARM7 micro controller.
> >
> 
> -- 
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss