how can I increase the CPU_CLOCK( processor speed ) to the maximum .
which are the registers to be configured with values?
in which file and how should I configure these registers
CPU_CLOCK to the maximum .
Re: CPU_CLOCK to the maximum .
So... short answer is 'no'. Long answer is 'NOOOOOOOOOOOOOOO'.
Longer answer is actually a question: What precisely are you trying to achieve? As a general rule, all our modules are running as close as possible to max frequency as their PLLs will allow.
-Dan
Longer answer is actually a question: What precisely are you trying to achieve? As a general rule, all our modules are running as close as possible to max frequency as their PLLs will allow.
-Dan
Dan Ciliske
Project Engineer
Netburner, Inc
Project Engineer
Netburner, Inc
Re: CPU_CLOCK to the maximum .
how can I find the processor usage for different tasks.
We have nearly 20tasks running on my project. These all tasks should
execute in every milliseconds.when but some are not being executed , what should I do ?
We have nearly 20tasks running on my project. These all tasks should
execute in every milliseconds.when but some are not being executed , what should I do ?
Re: CPU_CLOCK to the maximum .
Look at the UCOS_TIME functions. Enable the UCOS_TIME macro and recompile the system. There's a function that will dump the usage of all running tasks. Note: these functions do not take into account time spent in interrupts. It only examines when tasks are scheduled in and out.
-Dan
-Dan
Dan Ciliske
Project Engineer
Netburner, Inc
Project Engineer
Netburner, Inc
Re: CPU_CLOCK to the maximum .
Its not completely clear from your post what the situation really is. Do some of your tasks not execute at all, or are they all executing but not fast enough? There is a difference between a round robin and a real-time operating system. In a RTOS the highest priority task ready to run will run. If some tasks are written in such a way that they do not block on anything, the lower priority tasks will not run, or not run as often as you need them to. Are you expecting round robing or rtos behavior from the OS?
Re: CPU_CLOCK to the maximum .
Be careful if you're using a lot of tasks, there is a defined limit you have to modify if you go over 20
This crept up on me and the resulting problems did not make it obvious that this was the cause.
Code: Select all
#define OS_MAX_TASKS 20 // Max number of system tasks
Re: CPU_CLOCK to the maximum .
Good point. Also, if you have a lot of tasks that do a similar thing, such as checking network tcp sockets, a single task using the select() call could be much easier than having one task for each.