This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

pheripheral initialisation in SYS/BIOS

Other Parts Discussed in Thread: CONTROLSUITE, TMS320F28069

Hello,

i am evaluating to use SYS/BIOS on a project i'm working on. At the moment we use a TMS320F28069 mcu and the code we are using was build up on one of the controlsuite piccolo stick examples. I wrote my own simple scheduler and moved on from there.

I want to port this code to the SYS/BIOS structure to have access to the preemptive scheduler and debugging tools. 

My question now is regarding to the hardware initialisation of my board.

The SYS/BIOS examples do not include any of the hardware configuration (as far as i know off). Is it wise to copy paste the files from my previous project (so the GlobalVariableDefs.c, Headers_BIOS.cmd and DevInit_f2806x.c). Or is there a better way to do this (also regarding protability, we'll most likely switch to a different mcu in the near future)

My second question is regarding memory space:

i see that the RTOS project import also creates a .CMD linker file for program memory configuration as i am used too. But from the tutorials i understand i also have to define a platform on witch i am debugging. When i do this i see i have to define the program memory again. So witch one is used for RTOS projects ? Does one overwrite the other ?

And finally, on the platform i also define the platform clock frequency. Does this mean i can configure some clock routine on a direct timebase (say this routine has to be called every ms) or do i still need to take the clockcycles to ms into account when i write my code ? (do the conversion myself, this routine has to be called every 1500 cycles)

Thanks in advance

Regards,

Jan