This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

RTX : EX1 doesn't run using LPC2368

I have tested Keils RTX Program EX1.c using Lpc2124 using the Debugger and everthing ran OK.

So I modifed the EX1.c Prog for the LPC 2368.
1) Used LPC23xx.h through-out.
2) Removed Startup.s and used lpc2300.s and modifies the SWI Handler
as described by Keil.
3) set T1TCR to 0 before os_init.

Started the Debugger and displayed OS-Support-> rtx-kernel it shows:
task 1 wait_or " " 0000 0004 36% (ie no delay is shown, wait for event)
task 2 wait_delay 2 " " " " 32% (ie no events expected)
idle_os_demon 0%

There is no task switching going on.

Looking at Clock dividers the CCLK regularly changes from 48 to 2 MHz
and back again...and this appears to me ti be wrong, but cannot find out why. I have a suspicion that the reset handler is being called.

I'm using the Keil Demo V4 uVision on Win XP.

Can any one help me out to locate the problem?

Bonzadog

Parents
  • RE-DO : Auto-Translator problem..My apologies!
    ==============================================

    No i don't believe that. If you read further you would have seen that the two tasks in EX1 do get initialied and started so very obviously there is a startup there.

    In fact I used the lpc2300.s and modified it for the SWI Handler, as described in the RTX Doc. startup.s doesn't work as well. I had tried that too.

    I have seen with the Bebugger that the system seems to go to the reset_handler - perhaps from the timer. I think that the os_wait(2) is the problem area.

Reply
  • RE-DO : Auto-Translator problem..My apologies!
    ==============================================

    No i don't believe that. If you read further you would have seen that the two tasks in EX1 do get initialied and started so very obviously there is a startup there.

    In fact I used the lpc2300.s and modified it for the SWI Handler, as described in the RTX Doc. startup.s doesn't work as well. I had tried that too.

    I have seen with the Bebugger that the system seems to go to the reset_handler - perhaps from the timer. I think that the os_wait(2) is the problem area.

Children