Re: [ECOS] not possible to have a ROM app that's started by system w/ Redboot?

["Ken Yee" <kenkyee@excite.com>]

[-- Attachment #1: Type: text/plain, Size: 1007 bytes --]

> 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.


> 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.
I can't remove all the diag_printf calls in the networking stack in configtool...tried turning off all the debug stuff but on startup, the networking code seems to always print out those "Init: %s[%d]" lines.  I guess I could just change all the ecos code that does this and recompile...

 thanks,

ken

[-- Attachment #2: 0riginal_message --]
[-- Type: message/rfc822, Size: 3974 bytes --]

Return-Path: <ilijak@siva.com.mk>
X-Original-To: kenkyee.excite@masc002.roc2.bluetie.com
Delivered-To: kenkyee.excite@masc002.roc2.bluetie.com
Received: from inbound005.roc2.bluetie.com (inbound005.roc2.bluetie.com [10.200.2.205])
	by mas002.roc2.bluetie.com (Postfix) with ESMTP id 8B98DB38003
	for <kenkyee.excite@masc002.roc2.bluetie.com>; Fri,  5 Oct 2012 07:05:40 -0400 (EDT)
Received: from tirion.supremecenter202.com ([209.25.195.243])
	by inbound005.roc2.bluetie.com with inbound001
	id 7P5Z1k08n5FZZmx01P5atv; Fri, 05 Oct 2012 07:05:35 -0400
X-BT-Recipient: kenkyee@excite.com
X-CMAE-Score: 0.00
X-CMAE-Analysis: v=1.1 cv=PGG7cChdi0r4ojYnd+8oAk3EPXHLHoeHz39qXFqHhH8= c=1
 sm=1 a=GAXz5j0BEEwA:10 a=7hC59kJEqXIA:10 a=8nJEP1OIZ-IA:10
 a=jB7ylJp7uIqs30VHNsO8IQ==:17 a=CCpqsmhAAAAA:8 a=aRQOuzRV6FQwLxOdXegA:9
 a=wPNLvfGTeEIA:10 a=jB7ylJp7uIqs30VHNsO8IQ==:117
Received-SPF: spf=NONE ( siva.com.mk has no opinion concerning 209.25.195.243
 as a permitted sender)
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 <ilijak@siva.com.mk>)
	id 1TK52F-0007i1-1D; Fri, 05 Oct 2012 10:21:35 +0000
Message-ID: <506EB4AA.3040407@siva.com.mk>
Date: Fri, 05 Oct 2012 12:21:30 +0200
From: Ilija Kocho <ilijak@siva.com.mk>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:15.0) Gecko/20120827 Thunderbird/15.0
MIME-Version: 1.0
To: Ken Yee <kenkyee@excite.com>
CC: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] not possible to have a ROM app that's started by system
 w/ Redboot?
References: <20121004214326.27851@web003.roc2.bluetie.com>
In-Reply-To: <20121004214326.27851@web003.roc2.bluetie.com>
X-Enigmail-Version: 1.4.4
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - tirion.supremecenter202.com
X-AntiAbuse: Original Domain - excite.com
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - siva.com.mk
X-BtMT: Fri, 05 Oct 2012 07:05:40 -0400 (EDT)
Content-length: 1797

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



From: Ilija Kocho <ilijak@siva.com.mk>
To: Ken Yee <kenkyee@excite.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] not possible to have a ROM app that's started by system w/ Redboot?
Date: Fri, 05 Oct 2012 12:21:30 +0200
Message-ID: <506EB4AA.3040407@siva.com.mk>

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



[-- Attachment #3: Type: text/plain, Size: 148 bytes --]

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss