public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: jjp jjp <jackoaway@hotmail.com>
To: <ilijak@siva.com.mk>, <ecos-discuss@ecos.sourceware.org>
Subject: RE: [ECOS] Kinetis TWR-K60N512-KIT questions
Date: Mon, 11 Apr 2011 07:42:00 -0000	[thread overview]
Message-ID: <SNT129-W5405CAB49945C350910B32ADA80@phx.gbl> (raw)
In-Reply-To: <4D9F6B61.705@siva.com.mk>


Hi Ilija,
I can't test it before wednesday.
I will give you feedbacks as soon as possible.
Regards.


Date: Fri, 8 Apr 2011 22:09:05 +0200
From: ilijak@siva.com.mk
To: ecos-discuss@ecos.sourceware.org
CC: jackoaway@hotmail.com
Subject: Re: [ECOS] Kinetis TWR-K60N512-KIT questions



  


    
  
  
    Hi jjp

    

    Thank for question, you are coming in right time, A week ago I
    placed Kinetis port on Bugzilla. 

    http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001187

    I'll appreciate if you try it and come with feedback.

    Note:You need to commit latest version from CVS as it has bugs
    1001184, 1001186 integrated.

    

    I am using official eCos 3.0 tools (-m3 of course) in order to
    maintain compatibility, but I am keen to try gcc 4.6.

    

    Regards

    Ilija

    

    On 08.04.2011 16:42, jjp jjp wrote:
    
      
.ExternalClass .ecxhmmessage P
{padding:0px;}
.ExternalClass body.ecxhmmessage
{font-size:10pt;font-family:Tahoma;}


      Hi list,

      I am doing some tiny tests with k60 and I have some troubles to
      make SVC call running properly.

      Vector table is set at 0x20000000 in register SCB_VTOR, psp and
      msp have different adresses in RAM.

      I always get an HardFault after __asm__("svc 0");

    
    Check if VTOR setting is as desired, 0x20000000 should work. Also
    stack, what do you have in mlt files?

    Ilija, is it working properly for you?

      I'm using :

         -. gcc-4.6.0

    
       -. binutils-2.21.51 (patched snaphot with OS
      support for cortex-m4)

         -. zylin zy1000 (revB 1.66)

    
    Nice to see that Zylin supports Kinetis too.

    Regards

      

      > Date: Thu, 27 Jan 2011 23:01:15 +0100

      > From: ilijak@siva.com.mk

      > To: ecos-discuss@ecos.sourceware.org

      > Subject: Re: [ECOS] Kinetis TWR-K60N512-KIT questions

      > 

      > 

      > On 27.01.2011 10:09, jjp jjp wrote:

      > > Hi,

      > > I follow very closely the port of Ilija Kocho on Kinetis
      TWR-K60N512-KIT and

      > > I have some questions about your development methods :

      > Hello, and thanks for your interest.

      > > What cross compiler tools are you using (arm-eabi-gcc
      v-4.3 with patchs for cortex-m4)?

      > > What kind of debugging tools are you using?

      > Cortex-M4 is binary and backward compatible with M3 so, for
      the time

      > being you can use current compiler, of course you can't use
      Cortex-M4

      > specific features. Or you can try forthcoming 4.6.

      > 

      > > I don't see debug tools (except libSWD with OpenOCD) in
      Free and Open Source Software community trying

      > > to get debug by Serial Wire Debug.

      > 

      > Kinetis is very new, not yet in regular production so many
      tools are not

      > yet prepared. I don't know if OpenOCD supports Kinetis. In
      our lab we

      > have Ronetix PEEDI that is just getting Kinetis support. In
      meantime we

      > are working "dry" :(

      > 

      > 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

  parent reply	other threads:[~2011-04-11  7:42 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 [this message]
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
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=SNT129-W5405CAB49945C350910B32ADA80@phx.gbl \
    --to=jackoaway@hotmail.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=ilijak@siva.com.mk \
    /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).