public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Ilija Kocho <ilijak@siva.com.mk>
To: Lukas Riezler <lukas.riezler@gmx.net>
Cc: Edgar Grimberg <edgar.grimberg@gmail.com>,  ecos-discuss@sourceware.org
Subject: Re: Aw: Re:  Re: Re: [ECOS] Debugging via JTAG - problems?
Date: Thu, 02 May 2013 19:36:00 -0000	[thread overview]
Message-ID: <5182C00C.3040804@siva.com.mk> (raw)
In-Reply-To: <trinity-c31ca60c-87cb-457f-86d8-d5c6e079fdcc-1366981211319@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

  reply	other threads:[~2013-05-02 19:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-25  0:13 Lukas Riezler
2013-04-25  8:03 ` Ilija Kocho
2013-04-25 13:00   ` Aw: " Lukas Riezler
2013-04-25 13:03   ` Lukas Riezler
     [not found]     ` <CAPrjMDBTTL3K=jw8bN=u0D3qL-K kbqraFgS4e2vL pTrN3mNw@mail.gmail.com>
     [not found]     ` <CAPrjMDBTTL3K=jw8bN=u0D3qL-K_kbqraFgS4e2vL_pTrN3mNw@mail.gmail.com>
2013-04-25 13:38       ` Edgar Grimberg
2013-04-25 14:19         ` Aw: " Lukas Riezler
2013-04-25 15:31           ` Ilija Kocho
2013-04-26 13:00             ` Aw: " Lukas Riezler
2013-05-02 19:36               ` Ilija Kocho [this message]
2013-05-07 19:16                 ` Aw: " Lukas Riezler
2013-05-07 21:58                   ` Lukas Riezler
2013-05-07 23:24                     ` Lukas Riezler
2013-05-08  6:45                       ` Ilija Kocho
2013-05-08 15:10                         ` Aw: " Lukas Riezler
2013-05-02 19:05             ` Aw: " Lukas Riezler

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5182C00C.3040804@siva.com.mk \
    --to=ilijak@siva.com.mk \
    --cc=ecos-discuss@sourceware.org \
    --cc=edgar.grimberg@gmail.com \
    --cc=lukas.riezler@gmx.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).