This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: Aw: Re: 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, 02 May 2013 21:35:40 +0200
- Subject: Re: Aw: Re: 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>, <51794C56 dot 2070108 at siva dot com dot mk> <trinity-c31ca60c-87cb-457f-86d8-d5c6e079fdcc-1366981211319 at 3capp-gmx-bs42>
On 26.04.2013 15:00, Lukas Riezler wrote:
> Hello Ilja & Edgar!
>
>> 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.
>
> Okay, I'll switch to the CVS source during this weekend :)
>
>> 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.
>
> I've changed the startup type to SRAM.
>
> Now it looks a little bit better: I reach hal_reset_vsr() in the architecture HAL.
> The problem I have now is that I hang at the line
>
> __asm__ volatile("swi");
This exception should pass without problems, but your debugger may have
problem stepping through it while continual run may pass. Have tried to
put breakpoint(s) after this line?
>
> Does this indicates a specific matter I have not attended to?
>
> Please don't get me wrong - I'm not too lazy for researching solutions for my problems. But in this theme I don't really know how I could handle my problems. So thank you very much for all your previous answers!
>
> Have a nice weekend, Lukas
>
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss