public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Sergei Gavrikov <w3sg@SoftHome.net>
To: thekyz@gmail.com
Cc: ecos-discuss <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] Re: eCos invalidating JTAG on ARM architecture ?
Date: Fri, 06 Jul 2007 10:44:00 -0000	[thread overview]
Message-ID: <1183718456.13495.20.camel@sg-ubuntu> (raw)
In-Reply-To: <d5aafeec0707051400q709d03aaw701dc73e49dbb2b6@mail.gmail.com>

Alexandre writes:
> Well the problem came back earlier this evening :(
> I don't know how it is related to eCos but it is in some way because I
> do not have any problem when I run the same code without eCos (that is
> when I do the setup and vector init myself).

Well, and what about your own eCos startup file (hal_platform_setup.h)?
Did you manage the LPC PINSEL registers correctly? I see that Jani
Monoses, for example, didn't overload his own startup files by any extra
lines ;) Observe arm/lpc2xxx/*/current/hal/include/hal_platform_setup.h
files, for example. It's possible you have to force Debug/Trace pinouts
assignment in your own eCos platform startup file.

> I'll check to see if I have the post patch version but i downloaded my
> sources a week ago from the anonymous CVS.
         ^^^^^^^^^^^^^^^^
That already has contained that February fix.

> I indeed have a binary of openocd i found on the net, you think i
> should try and build it myself ?

At first, I would suggest to check your eCos startup code (platform
startup, certainly).

Sergei



-- 
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-06 10:44 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 [this message]
     [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
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=1183718456.13495.20.camel@sg-ubuntu \
    --to=w3sg@softhome.net \
    --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).