From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28261 invoked by alias); 5 Jul 2007 08:38:49 -0000 Received: (qmail 28223 invoked by uid 22791); 5 Jul 2007 08:38:48 -0000 X-Spam-Check-By: sourceware.org Received: from nz-out-0506.google.com (HELO nz-out-0506.google.com) (64.233.162.227) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 05 Jul 2007 08:38:42 +0000 Received: by nz-out-0506.google.com with SMTP id f1so1654945nzc for ; Thu, 05 Jul 2007 01:38:40 -0700 (PDT) Received: by 10.114.56.1 with SMTP id e1mr7908118waa.1183624720053; Thu, 05 Jul 2007 01:38:40 -0700 (PDT) Received: by 10.115.109.10 with HTTP; Thu, 5 Jul 2007 01:38:40 -0700 (PDT) Message-ID: Date: Thu, 05 Jul 2007 08:38:00 -0000 From: Alexandre Reply-To: thekyz@gmail.com To: ecos-discuss MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline 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: [ECOS] eCos invalidating JTAG on ARM architecture ? X-SW-Source: 2007-07/txt/msg00050.txt.bz2 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