µTasker Forum
µTasker Forum => NXPTM M522XX, KINETIS and i.MX RT => Topic started by: neil on September 18, 2008, 09:27:37 AM
-
Hi mark,
I am about to start a fresh project (just for testing), on my own board. Is there any I/Os that are used (for demo and eval boards) in utasker that I have to be aware of,as I use varoius pins on my own board.
Thanks
Neil
-
Hi Neil
The demo uses quite a number of ports but these are all defined in app_hw_m5223x.h.
By removing USE_MAINTENANCE a lot of this is removed, including the call to fnInitialisePorts(); from application.c
The port use is probably easiest to see by running the simulator. It is quite easy to move the ports around (defines in app_hw_m5223x.h) or remove them and quickly verify that they have really been freed.
Regards
Mark
-
Hi Mark,
I have removed the USE_MAINTENANCE, and all the LED outputs, apart from the ethernet ones.
Can the below be removed? :
INIT_WATCHDOG_DISABLE() ;// ensure IRQ4 is an input
#define CONFIG_TEST_OUTPUT() PORTTC |= PORT_TC_BIT3; DDRTC |= PORT_TC_BIT3; // {27}
#define TOGGLE_TEST_OUTPUT() PORTTC ^= PORT_TC_BIT3;
WATCHDOG_DISABLE()// pull this input down to disable watchdog (enable debugging) {3}
Regards
Neil
-
Neil
INIT_WATCHDOG_DISABLE(); is used to configure an input to decide whether the watchdog is to be activated or deactivated (useful for debugging). You can set
#define INIT_WATCHDOG_DISABLE() // do nothing
and then also
#define WATCHDOG_DISABLE() 0 // always activate the watchdog
or
#define WATCHDOG_DISABLE() 1 // always deactivate the watchdog
The others can be removed by setting
#define CONFIG_TEST_OUTPUT() // dummy
#define TOGGLE_TEST_OUTPUT() // dummy
These are some LED outputs used during some of the demo tests (or for measuring program execution times etc.)
regards
Mark