This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: Aw: Re: Re: Debugging via JTAG - problems?
- From: Ilija Kocho <ilijak at siva dot com dot mk>
- To: Lukas Riezler <lukas dot riezler at gmx dot net>
- Cc: Edgar Grimberg <edgar dot grimberg at gmail dot com>, ecos-discuss at sourceware dot org
- Date: Thu, 25 Apr 2013 17:31:34 +0200
- Subject: Re: Aw: Re: Re: Debugging via JTAG - problems?
- References: <trinity-f282db46-eac2-47d3-8bb1-13e21542ba72-1366848816388 at 3capp-gmx-bs55> <5178E338 dot 3090307 at siva dot com dot mk> <trinity-ba72444c-8db1-461a-b4d5-1651ed21f6d2-1366894983433 at 3capp-gmx-bs14> <CAPrjMDBTTL3K=jw8bN=u0D3qL-K kbqraFgS4e2vL pTrN3mNw at mail dot gmail dot com>, <CAPrjMDBhM1YJEjsW9KE0AK5 U6YUmTa77zXBRDW41iQv-VV1 g at mail dot gmail dot com> <trinity-10f2c11b-1ef6-45c3-a766-d4e6770a2ac3-1366899590535 at 3capp-gmx-bs13>
On 25.04.2013 16:19, Lukas Riezler wrote:
> Hi Edgar!
>
>> - Be sure everything is compiled with -O0 (no optimization).
> So I have to add this flag at the global build options in the configuration tool?
>
>> - Be sure you have compiled the latest version of the source code.
> I have ecos installed like it is described here: http://ecos.sourceware.org/getstart.html
> Is this ecos source code the latest one? I know about the CVS but I thougt the only difference is that there are more ports listed.
I strongly advise you to switch to CVS. Although it is not a release it
is pretty much stable. eCos CVS is not a development repository but
rather a rolling release.
>> - Be sure you have loaded the elf file to the target (I assume it's a RAM application, isn't it?)
> Yes, it is a RAM application. But I selected JTAG as startup type in the configuration tool.
> But how can I get sure the elf file is loaded to the target? Sorry for my silly question :/
It would be best to start with configuration that only employs on-chip
memory. I do not know your configuration (CDL, memory layout) so I shall
talk in terms of Kinetis and STM32 port. They have SRAM startup type
that is intended for usage with JTAG. Provided that your controller has
enough internal RAM this is the simplest way to bring system to life and
JTAG should work from scratch. ROM startup that uses only on-chip ROM
ans RAM is almost equally easy provided that you have a tool to program
controller's flash.
To sum up try to build system with on-chip memory first.
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