From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29715 invoked by alias); 6 Jul 2007 10:44:02 -0000 Received: (qmail 29704 invoked by uid 22791); 6 Jul 2007 10:44:02 -0000 X-Spam-Check-By: sourceware.org Received: from stelecom.gomel.by (HELO stelecom.gomel.by) (82.209.213.61) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 06 Jul 2007 10:43:57 +0000 Received: from localhost (localhost [127.0.0.1]) by stelecom.gomel.by (Postfix) with ESMTP id 67932B01D4C8; Fri, 6 Jul 2007 13:43:53 +0300 (EEST) Received: from stelecom.gomel.by ([127.0.0.1]) by localhost (stelecom.gomel.by [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 14502-11; Fri, 6 Jul 2007 13:43:52 +0300 (EEST) Received: from [192.168.0.33] (unknown [82.209.212.146]) by stelecom.gomel.by (Postfix) with ESMTP id AA894B01D0F8; Fri, 6 Jul 2007 13:42:56 +0300 (EEST) From: Sergei Gavrikov To: thekyz@gmail.com Cc: ecos-discuss In-Reply-To: References: <20070705205321.GA10274@ubuntu> Content-Type: text/plain Date: Fri, 06 Jul 2007 10:44:00 -0000 Message-Id: <1183718456.13495.20.camel@sg-ubuntu> Mime-Version: 1.0 X-Mailer: Evolution 2.8.1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Subject: Re: [ECOS] Re: eCos invalidating JTAG on ARM architecture ? X-SW-Source: 2007-07/txt/msg00061.txt.bz2 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