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: 1300 bytes --]

Iliya wrote:
> Yes, enable the respective tty<n> driver and set it as a console
> (default is ttydiag).
> But, actually you may have hardware problem (does it print barebone?).

Yes, it prints barebone (i.e., run as RAM startup type w/ Redboot).  These are only issues w/ trying to get it to run as a Redboot Flash app (the new Redboot ROM app startup type instead of the existing eCos ROM startup type).

FYI, for the diag_printf issue of it going into space on the IF_COMM_PUTC, the problem was the app didn't have "claim comms virtual vectors" checked under the configtool under eCos HAL, the ROM monitor support.  We got a lot further after checking off "claim virtual vector table entries by default", "claim reset virtual vectors", "claim delay_us virtual vectors", "claim data virtual vectors", and "claim comms virtual vectors".  It's interesting that the app's ecos config had to be set to do that instead of letting it use the Redboot vectors automatically, so it seems like we missed a section define somewhere that tells the RAM startup type to use the redboot virtual vector table...

So next issue we've hit is JFFS doesn't read the Redboot FIS table properly so it can't figure out where the internal flash partition is that it's supposed to use...it's progress at least :-)

[-- Attachment #2: 0riginal_message --]
[-- Type: message/rfc822, Size: 3330 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 inbound002.roc2.bluetie.com (inbound002.roc2.bluetie.com [10.200.2.202])
	by mas002.roc2.bluetie.com (Postfix) with ESMTP id 4DB85B38007
	for <kenkyee.excite@masc002.roc2.bluetie.com>; Fri,  5 Oct 2012 15:40:43 -0400 (EDT)
Received: from tirion.supremecenter202.com ([209.25.195.243])
	by inbound002.roc2.bluetie.com with inbound001
	id 7Xgg1k00E5FZZmx01XggHv; Fri, 05 Oct 2012 15:40:42 -0400
X-BT-Recipient: kenkyee@excite.com
X-CMAE-Score: 0.00
X-CMAE-Analysis: v=2.0 cv=CZaKFcXl c=1 sm=1 a=jB7ylJp7uIqs30VHNsO8IQ==:17
 a=GAXz5j0BEEwA:10 a=7hC59kJEqXIA:10 a=8nJEP1OIZ-IA:10 a=O8eIFpr9AAAA:8
 a=y69n1UwRan8A:10 a=89VEpfl-e8GPwN6kzNYA: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 [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 <ilijak@siva.com.mk>)
	id 1TKD57-0002wL-LD; Fri, 05 Oct 2012 18:57:06 +0000
Message-ID: <506F2D7F.5080102@siva.com.mk>
Date: Fri, 05 Oct 2012 20:57:03 +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: <20121005141943.18945@web007.roc2.bluetie.com>
In-Reply-To: <20121005141943.18945@web007.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 15:40:43 -0400 (EDT)
Content-length: 1174

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

IChYMTE7I!!

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 20:57:03 +0200
Message-ID: <506F2D7F.5080102@siva.com.mk>

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

IChYMTE7I!!

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