top level while loop

ken ho1

Intellectual 600 points

Hi,

In the main top level, can I still use a while loop or I have to remove it so that the bios_start scheduler can start?

If I do have to remove the top level while loop, will the idle loop take run repeatly over and over?

Ken

over 8 years ago

0 Tom Kopriva over 8 years ago

TI__Mastermind 20480 points

It'd take a look at a TI-RTOS example. There is no while(1) loop in main(). BIOS_start() does not return unless you call BIOS_exit(); which stops the scheduler, interrupts, etc...

If no higher priority task ready to run then the idle task (the lowest priority) will run - forever.

0 ken ho1 over 8 years ago in reply to Tom Kopriva

Intellectual 600 points

Tom,

So I try to conclude what you have said.

Three will be no while loop on top level, it will have bios_start at the end. It will not have bios_exit since it need to run forever with the scheduler. When all the tasks, swi, hwi finish, the idle loop will run. Then the tasks, swi, hwi may repeat again when the required event happen.

Ken

0 Tom Kopriva over 8 years ago in reply to ken ho1

TI__Mastermind 20480 points

In simplified terms, yes. Each task can (usally) be written with its own while(1) loop inside.

0 ken ho1 over 8 years ago in reply to Tom Kopriva

Intellectual 600 points

Tom,

Thanks for more details

Ken

0 ken ho1 over 8 years ago in reply to ken ho1

Intellectual 600 points

Hi Tom,

I have used a new RTOS bios_6_37_05_35 xdctools_3_31_--_24_core and ccs 6.1
I come accross a compilation problem as the following

<Linking>

undefined first referenced
symbol in file

--------- ----------------
>> Compilation failure
_main C:\ti\ccsv6\tools\compiler\ti-cgt-c2000_6.4.2\lib\rts2800_fpu32.lib<args_main.obj>

error #10234-D: unresolved symbols remain
error #10010: errors encountered during linking; "EvReceiver.out" not built

I check the lib C:\ti\ccsv6\tools\compiler\ti-cgt-c2000_6.4.2\lib\rts2800_fpu32 is there.
Please advise.

Ken