DSP2803x_SysCtrl.c, InitSysCtrl, and DELAY_US

tom prohaszka

Other Parts Discussed in Thread: CONTROLSUITE

The F2803x common files has an issue when running from flash. Depending on call order of InitSysCtrl, and MemCopy(&RamfuncsLoadStart, &RamfuncsLoadEnd, &RamfuncsRunStart), the DELAY_US in InitSysCtrl will cause an exception. In practice, the InitSysCtrl is called first to get the clock up and running fast, before time is spent copying code into RAM at a slower clock.

Suggest you change this or add big warning so PEOPLE DON"T GET BURNED.

over 14 years ago

0 Trey German289 over 14 years ago

TI__Mastermind 22025 points

Tom,

I fully understand and empathize with your frustration. I can't tell you how many times I've gotten burned by similar problems like this.

Thanks for calling this to our attention, as I'm sure you aren't the only one who has run into this problem. In the next release of controlSUITE we are including a note in the F280XX_sysctl.c file requiring users of the InitSysCtrl function to first copy the DELAY_US function to RAM. In this case, it is OK to copy the DELAY_US function to RAM before the PLL is setup because the function is so small.

Trey German

C2000 Applications

0 Tim King61612 over 14 years ago in reply to Trey German289

Expert 2355 points

Trey,

Could you also add InitAdc() to that warning. Although it may be generally called after the RAM copy, I have known people to call it prior causing unexpected results. It too has a call to DELAY_US.

Tim