|
|
Discussion Forum
RTX porting to 3.40
Next Thread | Thread List | Previous Thread
Start a Thread | Settings
| Details |
Message |
|
Read-Only
Author Marco Carini
Posted 27-Feb-2009 12:49 GMT
Toolset ARM
|
 RTX porting to 3.40
Marco Carini
Hi All,
I'm upgrading a firmware using RTX OS from 3.24 to 3.40.
As expected, there are many problems with functions, definitions
and so on.
I found that "the os_clock_demon() task scheduler has been
removed and replaced with system function calls" but I can't
understand what system function calls are intended and how do they
will substitute the scheduler.
Thanks to everyone,
Marco
|
|
|
Read-Only
Author Franc Urbanc
Posted 27-Feb-2009 13:34 GMT
Toolset ARM
|
 RE: RTX porting to 3.40
Franc Urbanc
The scheduler still exists, but it is not implemented as a task,
but rather as protected system functions. The benefit is faster
reaction on isr_xxx events and less ram for the kernel. From
the user's point of view, this is just a change in the library, while
the usage is the same as before v3.40
The main difference is the __task keyword location. You
have to change this in your project:
__task void io_control (void) {
And you have to replace the RTX_Config.c with a new one.
No other changes are required.
|
|
|
Read-Only
Author Marco Carini
Posted 4-Mar-2009 07:39 GMT
Toolset ARM
|
 RE: RTX porting to 3.40
Marco Carini
Hi, I followed your instruction and got a zero compile error for
my firmware.
I've taken my Rtx_Config.c configuration and reported it to the
new one, taken from the updated Rtx Blinky example.
I updated the used .lib and other .c files..
The system goes to pAbt_handler if I run it without
breakpoint.
Following the creation of tasks using breakpoint I got a "normal"
run, even if the OS is always in the Idle task..
With 3.24 this was ok, I can't understand what's wrong..
Thanks for help,
Marco
|
|
|
Read-Only
Author Franc Urbanc
Posted 4-Mar-2009 08:47 GMT
Toolset ARM
|
 RE: RTX porting to 3.40
Franc Urbanc
Did you install MDK 3.40?
Are you sure that you are using the correct libraries?
You can check the location of abort from the debugger.
LR-8 is the address that caused abort. Is this address from the RTX
library?
|
|
|
Read-Only
Author Marco Carini
Posted 11-Mar-2009 09:35 GMT
Toolset ARM
|
 RE: RTX porting to 3.40
Marco Carini
I found that my problem is related to the new FS_ARM_L.lib. Using
the old .lib my Rtx is 80% functional, replacing the file with the
new .lib it goes to Abort.
I'm using the 3.40 Mdk and RL version, when RTX calls functions
like fclose() it goes to abort..
Thanks for help, I know it's quite difficult to understand what's
happening..
Marco
|
|
Next Thread | Thread List | Previous Thread
Start a Thread | Settings
|
|
|