From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16616 invoked by alias); 2 Dec 2012 07:13:34 -0000 Received: (qmail 16605 invoked by uid 22791); 2 Dec 2012 07:13:34 -0000 X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_00,KHOP_SPAMHAUS_DROP,KHOP_THREADED,RCVD_IN_HOSTKARMA_NO,RCVD_IN_HOSTKARMA_YE,TW_XF X-Spam-Check-By: sourceware.org Received: from p02c11o141.mxlogic.net (HELO p02c11o141.mxlogic.net) (208.65.144.74) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 02 Dec 2012 07:13:29 +0000 Received: from unknown [12.218.215.72] (EHLO smtpauth1.linear.com) by p02c11o141.mxlogic.net(mxl_mta-6.16.0-0) with ESMTP id 89ffab05.0.156950.00-2342.326721.p02c11o141.mxlogic.net (envelope-from ); Sun, 02 Dec 2012 00:13:29 -0700 (MST) X-MXL-Hash: 50baff997bcd5000-d51c7e7d538bae4e7f3c27d5e1e93f5fb96c9f36 Received: from smtpauth1.linear.com (localhost [127.0.0.1]) by smtpauth1.linear.com (Postfix) with ESMTP id 27A01740A3 for ; Sat, 1 Dec 2012 23:13:28 -0800 (PST) Received: from [192.168.0.119] (75-163-186-131.clsp.qwest.net [75.163.186.131]) by smtpauth1.linear.com (Postfix) with ESMTPSA id DFC06740A0 for ; Sat, 1 Dec 2012 23:13:27 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) From: Michael Jones In-Reply-To: <88A5F92E-1AE1-4246-B566-3EFE5DEA360B@linear.com> Date: Sun, 02 Dec 2012 07:13:00 -0000 Content-Transfer-Encoding: quoted-printable Message-Id: References: <88A5F92E-1AE1-4246-B566-3EFE5DEA360B@linear.com> To: eCos Discussion X-AnalysisOut: [v=2.0 cv=OfYv+GvY c=1 sm=1 a=glloKNylpeYNumXQcclYyA==:17 a] X-AnalysisOut: [=gTASQVg5WCMA:10 a=D2_GN2MmYMYA:10 a=BLceEmwcHowA:10 a=kj9] X-AnalysisOut: [zAlcOel0A:10 a=MqDINYqSAAAA:8 a=l9cmVeDug7kA:10 a=CCpqsmhA] X-AnalysisOut: [AAAA:8 a=5p-j7yPTBBr-jAy9AGEA:9 a=CjuIK1q_8ugA:10 a=xLpt9-] X-AnalysisOut: [x9cSEA:10 a=T-cDpESlCwU3wYks:21 a=ozclFS5hOk6auxRl:21] X-MAIL-FROM: 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] Kinetis CYG_HAL_STARTUP_VAR conflict X-SW-Source: 2012-12/txt/msg00003.txt.bz2 I have a little more info on this... I ignored the conflict and with some pain finally got an SREC file built an= d ready to load. I failed to get kermit and ymodem to work. If anyone knows a way of loading= with ymodem from linux using telnet or similar application over IP, I coul= d use a recipe. TFTP is hard to make work with VMs when you have ethernet a= nd wireless. I finally was able to load via TFTP, and I get an error from the loader say= ing the address was not a valid address. The image tries to load at 0x1FFF = 0400. This seems to be the address in the image. Using version, the valid range starts at 0x1FFF CC70. So I load specificall= y to that address and use "go" with the specified entry point of 0x1FFF CC8= 9. The result: no output from printf. telnet 192.168.0.10 9000 RedBoot> load -v -h 192.168.0.2 -b 0x1fffcc70 hello.srec Address offset =3D 0xffffc890 Entry point: 0x1fffcc89, address range: 0x1fffcc79-0x20007bec RedBoot> go 0x1fffcc89 The app is nothing more than: #include int main(void) { printf("Hello, eCos world!\n"); return 0; } I still have the same original questions about SRAM vs RAM and the conflict= I ignored. I have no idea if the image will work with this conflict. Now I have more questions: 1) Why is the range of valid addresses in RedBoot different than the starti= ng address in the image? Is RedBoot using some RAM? Am I supposed to manual= ly set the start address to a safe place? 2) Is it valid to load at a different address and use the new entry point a= s I showed above? Meaning, is the image relocatable? 3) Should the printf have printed on the RedBoot console? 4) What is the effect of the return 0 on the RedBoot prompt? Should it rele= ase control so you can type? Mike On Dec 1, 2012, at 2:07 PM, Michael Jones wrote: > BACKGROUND > ---------------------- >=20 > I am having a little bit of trouble trying to get my first hello world ap= p on a K60 Tower Board. >=20 > I have RedBoot running from ROM and I can ping the ethernet port, so pres= umably I will eventually get GDB to talk to it. >=20 > I am having trouble building an initial app that uses the ROM monitor. Fo= llowing the example in the eCos book, I went hunting for CYGSEM_HAL_USE_ROM= _MONITOR, enabled it and then set startup to SRAM. This seems the obvious w= ay to run and debug. >=20 > PROBLEM > -------------- >=20 > I am getting a conflict I don't know how to resolve. I have set CYG_HAL_S= TARTUP_VAR =3D SRAM. This results in CYG_HAL_STARTUP =3D SRAM by calculatio= n. >=20 > But I get a conflict from CYGSEM_HAL_USE_ROM_MONITOR that wants CYG_HAL_S= TARTUP =3D=3D RAM >=20 > QUESTIONS > ----------------- >=20 > 1) Can I ignore this conflict and get the monitor and app to work? >=20 > 2) Is there a better approach? >=20 > 3) Has anyone succeeded to use RedBoot on the K60 and can you supply an e= xample config project that works that I can look at? >=20 > Thanks, >=20 > Mike >=20 > -- > Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos > and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss >=20 -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss