public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Andy Jackson" <list@xylanta.com>
To: "Alexandre" <thekyz@gmail.com>
Cc: <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] Re: eCos invalidating JTAG on ARM architecture ?
Date: Tue, 10 Jul 2007 15:52:00 -0000	[thread overview]
Message-ID: <003c01c7c30a$40480720$7101a8c0@Kimbara> (raw)
In-Reply-To: <20070710151420.GC10830@lunn.ch>

Have you tried the CDL option

CYGHWR_HAL_ARM_LPC2XXX_IDLE_PWRSAVE

Here is the description. I put it in when I was having problems with the 
JTAG dropping out.

           Select this option when it is desired to save power by
           stoping the processor clock in the idle loop. This is
           controlled by the PCON register. Generally this is a good
           thing, but it may be necessary to disable this when
           debugging via JTAG, as stopping the clock can prevent the
           debugger getting control of the system."

Hope that helps,

    Andy..

----- Original Message ----- 
From: "Andrew Lunn" <andrew@lunn.ch>
To: "Alexandre" <thekyz@gmail.com>
Cc: "Sergei Gavrikov" <w3sg@softhome.net>; 
<ecos-discuss@ecos.sourceware.org>
Sent: Tuesday, July 10, 2007 4:14 PM
Subject: Re: [ECOS] Re: eCos invalidating JTAG on ARM architecture ?


> On Tue, Jul 10, 2007 at 05:02:12PM +0200, Alexandre wrote:
>> Okay i seem to have identified the problem and narrowed it down again.
>> The modification on the PINSEL1 register init now enables me to debug
>> eCos properly IF i don't use the function cyg_thread_delay().
>> For some obscure reason this particular function seems to deactivate
>> the JTAG definitely (JTAG1 and 2) on my controller.
>>
>> Should it be expected ?
>
> No.
>
> cyg_thread_delay() does nothing with hardware. It just waits until the
> correct number of timer ticks have gone off and then brings sleeping
> process back to running state.
>
> Does the system continue to run even though JTAG has stopped?
>
> Im just wondering if JTAG stops working with the system crashes?  It
> could be your stack is too small, which sometimes causes crashes in
> cyg_thread_delay().
>
> What test programs are you using? All the standard tests should work
> without problems, so i would use them for the moment until you get a
> stable system.
>
>    Andrew
>
> -- 
> 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

  reply	other threads:[~2007-07-10 15:52 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-05  8:38 [ECOS] " Alexandre
2007-07-05 14:33 ` [ECOS] " Alexandre
2007-07-05 20:54   ` Sergei Gavrikov
2007-07-05 21:00     ` Alexandre
2007-07-06 10:44       ` Sergei Gavrikov
     [not found]         ` <d5aafeec0707060446s14079f3crfa90914e187833a3@mail.gmail.com>
2007-07-06 16:49           ` Sergei Gavrikov
2007-07-06 17:24             ` Sergei Gavrikov
2007-07-10  9:56               ` Alexandre
2007-07-10 10:15                 ` Andrew Lunn
2007-07-10 15:02                   ` Alexandre
2007-07-10 15:14                     ` Andrew Lunn
2007-07-10 15:52                       ` Andy Jackson [this message]
2007-07-10 18:25                         ` Alexandre
2007-07-11 11:12                           ` [ECOS] IPMI driver for KCS interface jerzy dyrda
2007-07-11 11:38                             ` Laurie Gellatly
2007-07-11 12:33                               ` jerzy dyrda
2007-07-12  7:16                                 ` David Fernandez
2007-07-11 11:46                             ` Andrew Lunn
2007-07-10 15:59                       ` [ECOS] Re: eCos invalidating JTAG on ARM architecture ? Alexandre
2007-07-05 16:04 ` [ECOS] " Paul D. DeRocco
2007-07-05 16:25   ` Andrew Lunn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='003c01c7c30a$40480720$7101a8c0@Kimbara' \
    --to=list@xylanta.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=thekyz@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).