From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2444 invoked by alias); 5 Oct 2012 18:57:17 -0000 Received: (qmail 2367 invoked by uid 22791); 5 Oct 2012 18:57:15 -0000 X-SWARE-Spam-Status: No, hits=-2.7 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED X-Spam-Check-By: sourceware.org Received: from tirion.supremecenter202.com (HELO tirion.supremecenter202.com) (209.25.195.243) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 05 Oct 2012 18:57:10 +0000 Received: from [77.28.166.76] (port=59710 helo=[192.168.178.36]) by tirion.supremecenter202.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from ) id 1TKD57-0002wL-LD; Fri, 05 Oct 2012 18:57:06 +0000 Message-ID: <506F2D7F.5080102@siva.com.mk> Date: Fri, 05 Oct 2012 18:57:00 -0000 From: Ilija Kocho User-Agent: Mozilla/5.0 (X11; Linux i686; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: Ken Yee CC: ecos-discuss@ecos.sourceware.org References: <20121005141943.18945@web007.roc2.bluetie.com> In-Reply-To: <20121005141943.18945@web007.roc2.bluetie.com> Content-Type: text/plain; charset=ISO-8859-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] not possible to have a ROM app that's started by system w/ Redboot? X-SW-Source: 2012-10/txt/msg00006.txt.bz2 On 05.10.2012 20:19, Ken Yee wrote: >> It's true for break points. The target code being in Flash, rather than >> RAM, needs hardware break points that are not supported by RedBoor/eCos >> GDB stubs at present. > I'm actually using a Segger JLink for debugging...not using Redboot's gdb support. > That's why I'm puzzled...I should be able to look at the code behind that macro or single step through the assembly code but I can't do anything w/ that IF_PUTC function. Then I'm afraid I can't help you much. I would check whether the GDB server is set for hardware break points. > >> Try the real (instead of diagnostic) serial driver. > Is there a way to get "diag_printf" to use the real serial driver? Interesting that you hit the same issue...I always thought the diag_driver just used the same serial port but with interrupts disabled. Yes, enable the respective tty driver and set it as a console (default is ttydiag). But, actually you may have hardware problem (does it print barebone?). If you power Kwikstik from it's own USB connector there is a voltage drop on serial diode (I don't recal whether it was D6 or D7) that hinders RS232. Ilija -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss