From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28382 invoked by alias); 8 Oct 2012 22:40:42 -0000 Received: (qmail 28371 invoked by uid 22791); 8 Oct 2012 22:40:40 -0000 X-SWARE-Spam-Status: No, hits=-1.6 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,KHOP_SPAMHAUS_DROP,MIME_QP_LONG_LINE,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_NO,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org Received: from outbound003.roc2.bluetie.com (HELO outbound003.roc2.bluetie.com) (208.89.132.143) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 08 Oct 2012 22:40:35 +0000 Received: from web006.roc2.bluetie.com ([10.200.2.100]) by outbound003.roc2.bluetie.com with outbound003 id 8mgS1k00329U4Qi01mgSB1; Mon, 08 Oct 2012 18:40:27 -0400 X-CMAE-OUT-Analysis: v=2.0 cv=K7+g7lqI c=1 sm=1 a=mbNHNI8rG5QA:10 a=i-wQWBNYtOgA:10 a=FmX3VfpdAAAA:8 a=QoHJ8kPOAAAA:8 a=y69n1UwRan8A:10 a=eKWu4CZ9nlTfy9vPD_8A:9 a=QEXdDO2ut3YA:10 a=AD-LgEP5VvkFCvax:21 a=LV8RUlCfm1V3etEd:21 a=89VEpfl-e8GPwN6kzNYA:9 a=wPNLvfGTeEIA:10 a=L9C/gGIz1Vpswtb6eSrjaQ==:117 X-CMAE-OUT-Score: 0.00 Received: from web006.roc2.bluetie.com (localhost.localdomain [127.0.0.1]) by web006.roc2.bluetie.com (Postfix) with ESMTP id AC425AE01EE for ; Mon, 8 Oct 2012 18:40:25 -0400 (EDT) Message-ID: <20121008184025.14616@web006.roc2.bluetie.com> X-HTTP-Received: from kenkyee.excite [64.145.41.116] by web006.roc2.bluetie.com (BlueTie WebMail ); Mon, 08 Oct 2012 18:40:25 -0400 Date: Mon, 08 Oct 2012 22:40:00 -0000 Cc: To: ecos-discuss@ecos.sourceware.org From: "Ken Yee" Content-Type: multipart/mixed; boundary="651413023-1349736025=:14616" MIME-Version: 1.0 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/msg00007.txt.bz2 --651413023-1349736025=:14616 Content-transfer-encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Content-length: 1316 Iliya wrote: > 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?). 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 u= nder 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 da= ta virtual vectors", and "claim comms virtual vectors". It's interesting t= hat the app's ecos config had to be set to do that instead of letting it us= e the Redboot vectors automatically, so it seems like we missed a section d= efine 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 sup= posed to use...it's progress at least :-) --651413023-1349736025=:14616 Content-Type: message/rfc822; charset=UTF-8; name="0riginal_message" Content-Disposition: attachment; filename="0riginal_message" x-btFieldFwd: Yes Content-length: 3309 Return-Path: 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 ; 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 ) 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 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 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 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!! --651413023-1349736025=:14616 Content-Type: text/plain; charset=us-ascii Content-length: 148 -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss --651413023-1349736025=:14616--