From: Ilija Kocho <ilijak@siva.com.mk>
To: Michael Jones <mjones@linear.com>
Cc: ecos <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] Re: Problem setting up an ISR for a K60 PORT
Date: Tue, 19 Feb 2013 19:30:00 -0000 [thread overview]
Message-ID: <5123D2AF.4000101@siva.com.mk> (raw)
In-Reply-To: <5ED098DC-1719-4A66-82DA-2599E0489743@linear.com>
Mike
There isn't a general interrupt enable in Kinetis HAL. Actually there's
no GPIO interrupt support yet.
Just one note regarding interrupt priority numbering. Kinetis implements
4 bits, and by Cortex-M interrupt priority arbitration scheme it's 4
most significant bits (out of 8). Therefore your interrupt priority
should be something like 0x30. Priority 3 effectively is same as 0. For
relevant Kinetis priority numbers look for /Interrupt Priority Scheme/
in configtool.
Ilija
On 19.02.2013 15:51, Michael Jones wrote:
>>>
>> After our 'interrupt_create', we also have those calls (we use IRQ2
>> instead of your PORTA):
>> cyg_interrupt_attach(t_intrhandle);
>> cyg_interrupt_configure(CYGNUM_HAL_INTERRUPT_IRQ2, TLV_FALSE, TLV_FALSE);
>> cyg_interrupt_acknowledge(CYGNUM_HAL_INTERRUPT_IRQ2);
>> cyg_interrupt_unmask(CYGNUM_HAL_INTERRUPT_IRQ2);
>>
>> Why do you call 'cyg_thread_suspend...' ? I do not see code that creates
>> a thread. And when I create a thread, I do cyg_thread_create(...);
>> cyg_thread_resume(..);.
>>
>> Why do you need a thread when your code is run by interrupts?
>
> Seeing your code, brought something to mind. I had assumed that the interrupt was enabled in the Kinetis HAL and all I had to do was configure the port. Perhaps that is not the case. I'll try to use your example and see what happens.
Indeed, there isn't a general interrupt enable in Kinetis HAL.
>
> Thanks
>
>
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2013-02-19 19:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <A60E30AB-6F4C-4A0E-8B39-BC76435B33D2@linear.com>
2013-02-19 8:34 ` Lambrecht Jürgen
2013-02-19 14:51 ` Michael Jones
2013-02-19 19:30 ` Ilija Kocho [this message]
2013-02-20 5:19 ` [ECOS] " Michael Jones
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=5123D2AF.4000101@siva.com.mk \
--to=ilijak@siva.com.mk \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=mjones@linear.com \
/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).