From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27512 invoked by alias); 5 Oct 2012 10:21:44 -0000 Received: (qmail 27504 invoked by uid 22791); 5 Oct 2012 10:21:43 -0000 X-SWARE-Spam-Status: No, hits=-1.1 required=5.0 tests=AWL,BAYES_50,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 10:21:39 +0000 Received: from [195.189.206.101] (port=49350 helo=[192.168.209.11]) by tirion.supremecenter202.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from ) id 1TK52F-0007i1-1D; Fri, 05 Oct 2012 10:21:35 +0000 Message-ID: <506EB4AA.3040407@siva.com.mk> Date: Fri, 05 Oct 2012 10:21: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: <20121004214326.27851@web003.roc2.bluetie.com> In-Reply-To: <20121004214326.27851@web003.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/msg00004.txt.bz2 On 05.10.2012 03:43, Ken Yee wrote: > Ilija Kocho wrote: >> This may be example you are looking for: >> http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001623 > Got decently far with this angle of changes. > We created a new startup type, and fiddled with most of the options for RAM/ROM in the .cdl file. But from doing this, it's glaringly obvious that eCos does *NOT* support this setup; a ROM app run from Redboot, at least on the AT91, has to do a hybrid of the ROM and RAM startup types. The Redboot documentation should clearly state that only apps built in the RAM startup type are supported IMHO. True, you won't find for ROM startup in standard RedBoot. FLASH startup is [my] experiment for testing the concept. It seems to work, but it's still experimental. Your tests are valuable, thanks. > > Anyways, simple test apps seem to run, but one this we hit was that anything that does diag_printf gets stuck in the IF_IN_PUTC call...it just deep spaces (runs until it hits that) there in the debugger. Single stepping into assembly doesn't even work if you put a breakpoint before that so we can't see where that goes (whether it's to a bad driver, etc.). The simplest app like this: 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. > void cyg_user_start(void) > { > diag_printf("\r\nHello world!\r\n"); > } > does the hang when compiled as an APPROM (that's what we called it instead of Flash as yours is called...maybe RBROMAPP for RedBootROMApp might be a better acronym?). > > Did you hit this problem in your setup at all? i.e., did you try diag_printf on your kinetis board? Yes I have. Try the real (instead of diagnostic) serial driver. 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