Messages

16

µTasker general / Re: How to read/write the digital I/O

« on: June 10, 2010, 05:19:46 PM »

Hi Mark
I have one more question.
I followed your advice, and have the NQ pins 1 and 5 triggering my handlers. Both are set to trigger on RISING_EDGE.
But for production code I would need the handler be called on both edges, but being able to know which of them was the awakener.
I was diving in the code, and I am guessing that it's not posible, at least in target code.
Is it correct? In other words, to know the edge I would need two handlers?
TIA
Regards
Marcelo

17

µTasker general / Re: How to read/write the digital I/O

« on: June 08, 2010, 10:13:14 AM »

Thank you again, Mark
I will try what you told me.
Regards
Marcelo

18

µTasker general / Re: How to read/write the digital I/O

« on: June 07, 2010, 11:49:39 PM »

Hi Mark

Sorry about my new questions, but this is the most obscure part of microcontrollers for me.

After recompiling with input's interrupts enabled, I was following the relevant demo code ( under simulation ) and cannot understand some things.
Beforehand, I must tell you that I'm interested in the NQ port, specifically in the pins 1 and 5, because these are connected to buttons in the 52259 demo board.

But when I change "input state" on the "NQ port" window representation, only the bit 7 ( pin 7? ) goes through the test_nmi_7() handler. And I cannot see when the bit mask is set when executing fnInitIRQ(), so only this "bit" awakes the expected path.

Is't needed to associate a distinct IRQ to every distinct input pin I am interested in? Or can I have a unique handler for the IRQ and get from it which of the pins was triggered? If this were the case, how?

Sorry again the bunch of questions, but I am a little confused.

TIA, again

Regards
Marcelo

19

µTasker general / Re: How to read/write the digital I/O

« on: June 07, 2010, 12:36:47 PM »

Hi, Mark!
Thank you again!
Marcelo

20

µTasker general / How to read/write the digital I/O

« on: June 06, 2010, 02:52:21 PM »

Hi all
I was searching the demo project ( V 1.4 ) for the 5225 demo board and cannot find the place where the led is toggled on/off, to learn by example.

Also, I would like to wake up a task whenever some input is present. How can I do that?

Thank you in advance

Regards

Marcelo

21

µTasker general / Re: CW refuses to flash the uTasker demo

« on: May 31, 2010, 10:25:20 PM »

Hi Mark

All the guilt is of mine.
But CW have his big part also.
I never mind that I would need to configure separately the debugging settings for the target, when I'm giving near all info in the programming tool.
It succeeded.

But I would like to get the cfg files to us CF Flasher.

TIA

Marcelo

22

µTasker general / Re: CW refuses to flash the uTasker demo

« on: May 31, 2010, 08:13:43 PM »

Hi Mark, is me again

I downloaded and installed the Cf Flasher, as a last resource. Could you please, send me the config file?

TIA

Regards

Marcelo

23

µTasker general / Re: CW refuses to flash the uTasker demo

« on: May 31, 2010, 07:57:28 PM »

Hi Mark:

CW Special Edition also refuses to flash the uTasker demo.
May be I'm using 7.2 ...

Regards

Marcelo

24

µTasker general / Re: CW refuses to flash the uTasker demo

« on: May 31, 2010, 07:13:32 PM »

Hi Mark

To begin with, thank you by your fast answer. But trust me that I'm doing things the way they would.

I'm programming for the M52259DEMO board from two months ago.
So I learned some things, like figth with te "Connect failed" error when trying to erase / program the board's flash.
This error was getting me mad until I learned that at every flash cycle, I must to disconnect the board's OSBDM port, wait a few seconds and reconnect it.
And, of course, at every CW session start I followed the recipe to configure the flash programmer adequately. This way, I flashed the board not less than 100 times.

But last saturday the trick did not work anymore: after five or six cycles where once and again CW's Flash Programmer reported this condition ( also after a Windows reboot ) I gave up and ask in the Freescale forum.

Today, after a cold restar of everything, I tried two times again, at no luck.
While searching the net to know why and how an USB port suddenly cannot communicate anymore with the OSBDM device, but can happily connect a pen drive ... I suspected that CW was fooling me regarding the true reason behind the "error".

In the same CW session that refused to flash the uTasker demo ( recall? two times today ) I closed the uTasker project and opened and opened a MQX based one ( of my own ).
And guess what? It flashed without comments.

Moral: when CW dont like something it pretends a flash error.

To me, that is strong evidence. I'm installing the special edition, following your kind advice.

Regards

Marcelo

25

µTasker general / CW refuses to flash the uTasker demo

« on: May 31, 2010, 03:08:05 PM »

I'm trying to program a Freescale's M52259DEMO board.
After some pitfalls with the Freescale / MQX code base, I decided to get uTasker a new and deep look.
I liked what I learned from the docs, so I tried it. First, of course, with the simulator.
When I tried to burn the demo project to the board from the Code Warrior IDE, CW complained regarding USB connection error.
And it was six times in a row, including a Windows restart.

I spent some hours searching the net regarding sudden USB errors, until I decided to test the port I was using with a pen drive, which of course went ok.
Again loaded CW and tried to burn the flash, two times, at no luck.
Suspecting some fooling, in the same CW session I closed the uTasker project, and opened another of mine, which uses the MQX code base.
Hard to believe, CW flashed it without any comment. It's obvious to me, that CW is not "seeing" some MQX signature, and refuses to flash, but pretending an error, not telling the truth.

My question is now: how to burn an uTasker project?