• State
  • Locked Locked
  • Replies 0 replies
  • Subscribers 83 subscribers
  • Views 215 views
  • Users 0 members are here
Support feedback
Options
Options

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.

Original question:

TMS320F28335: SFO function causing floating point exception due to computing 0/0

TMS320F28379D: Using the SFO routine pm F28379D causes the FPU overflow/underflow flags to latch

Eric Sullivan
Prodigy 20 points
Part Number: TMS320F28379D
Other Parts Discussed in Thread: C2000WARE

Tool/software:

The part I have is the TMS320F28379D, using version 12.1.0.00007, and using version 4.02 of C2000Ware.

When running the SFO library function, the floating-point overflow and underflow flags latch. This appears to happen right when we first start using the SFO function, in which we call the SFO function a while loop until it returns a "SFO_COMPLETE" result (as suggested by documentation). Its hard to tell why this is happening because the source code for SFO is not available in C2000Ware, but stepping through the assembly instructions for SFO shows they get latched on "DIVF32" instructions, which I have captured here.

I imagine this isn't expected behavior, so I was wondering if anybody had an idea on what could be going on? As I said, this appears to happen just before the SFO finishes its initial calibration. We appear to be doing everything required for using SFO (linking the correct SFO library, defining the necessary variables, calling it before we initialize of HPWM channels).  If I need to provide any more information, please let me know, as I am sure I am leaving out some necessary context that I can't think of right now.

Thanks,

- Eric