public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: jjp jjp <jackoaway@hotmail.com>
To: <ecos-discuss@ecos.sourceware.org>
Subject: RE: [ECOS] Kinetis TWR-K60N512-KIT questions
Date: Thu, 05 May 2011 14:30:00 -0000	[thread overview]
Message-ID: <SNT122-w4199AA5BC8A8B742190D06AD800@phx.gbl> (raw)
In-Reply-To: <4DC1D4D0.2070205@siva.com.mk>


Hi,
I test unified RAM configuration and it works for me with some modifications.
   -. Replace SRAM by RAM hal_cortexm_kinetis_twr_k60n512.cdl to disable execution of SWI in
hal_reset_vsr (line 187). Execution of this part reset tower and flash code runs again.

   -. Lookup /dev/ser3 and make cyg_io_write instead of printf. Code with printf reset tower and
flash code runs again.

I also try to use cortexm exception support but it fails.
I install an exception handler with cyg_exception_set_handler for CYGNUM_HAL_VECTOR_SERVICE
(vector 11 -> SVCall). I make a SWI call an I expect it to modify execution flow to call my exception handler.
SWI calls hal_default_svc_vsr and R3 get a dummy value not a function address value.

Why software interrupt doesn't call hal_default_exception_vsr?
Regards.

----------------------------------------
> Date: Thu, 5 May 2011 00:36:00 +0200
> From: ilijak@siva.com.mk
> To: ecos-discuss@ecos.sourceware.org
> Subject: Re: [ECOS] Kinetis TWR-K60N512-KIT questions
>
> On 04.05.2011 12:46, jjp jjp wrote:
> > Hi,
> > It works with ecos toolchain and gcc-4.6 with -mcpu=cortex-m4!
> > Great job Ilija.
>
> Thanks for good words.
> I am testing some integer DFT code with gcc-4.6 / Cortex-M4. Shows
> performance improvement over M3 code even for plain C code.
>
> > My miktake was to put optimization flag to -O0 in global flags.
> > I will test your RAM configuration and give you feedbacks.
>
> I appreciate.
>
> Regards
> 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
>
 		 	   		  

--
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:[~2011-05-05 14:30 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-27 17:24 jjp jjp
2011-01-28 16:05 ` Ilija Kocho
     [not found]   ` <SNT129-W29DA08015F0442D154694DADA70@phx.gbl>
2011-04-08 20:16     ` Ilija Kocho
     [not found]     ` <4D9F6B61.705@siva.com.mk>
2011-04-11  7:42       ` jjp jjp
2011-04-12 18:09         ` Ilija Kocho
2011-04-13  8:01           ` jjp jjp
2011-04-13 15:55             ` Ilija Kocho
2011-04-14  7:29               ` jjp jjp
2011-04-14 10:53                 ` Ilija Kocho
2011-04-14 11:11                   ` Drasko DRASKOVIC
2011-04-14 13:09                     ` Ilija Kocho
2011-04-14 15:05                       ` Drasko DRASKOVIC
2011-04-15  9:56                         ` Ilija Kocho
2011-04-15 10:21                           ` Ross Younger
2011-04-14 12:14                   ` jjp jjp
2011-04-14 13:18                     ` Edgar Grimberg
2011-04-14 14:11                       ` jjp jjp
2011-05-03 15:07                         ` jjp jjp
2011-05-03 17:10                           ` Ilija Kocho
2011-05-04 10:47                             ` jjp jjp
2011-05-04 22:36                               ` Ilija Kocho
2011-05-05 14:30                                 ` jjp jjp [this message]
2011-05-06  7:36                                   ` Ilija Kocho
2011-05-11  8:47                                     ` jjp jjp
2011-05-11 17:13                                       ` Ilija Kocho
2011-04-14 13:50                     ` Ilija Kocho

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=SNT122-w4199AA5BC8A8B742190D06AD800@phx.gbl \
    --to=jackoaway@hotmail.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    /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).