Skip to content

Commit c5c95d1

Browse files
committed
Use runtime error detection
Rather than MBED_ASSERT, let's use error() function to detect out of range parameters during runtime execution
1 parent 731148e commit c5c95d1

File tree

1 file changed

+4
-2
lines changed
  • libraries/mbed/targets/hal/TARGET_STM/TARGET_STM32F3

1 file changed

+4
-2
lines changed

libraries/mbed/targets/hal/TARGET_STM/TARGET_STM32F3/pwmout_api.c

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -174,10 +174,12 @@ void pwmout_period_us(pwmout_t* obj, int us)
174174
}
175175
TimHandle.Init.Prescaler = ((SystemCoreClock / 1000000) * obj->prescaler) - 1;
176176

177-
MBED_ASSERT(TimHandle.Init.Prescaler < 0xFFFF);
177+
if (TimHandle.Init.Prescaler > 0xFFFF)
178+
error("PWM: out of range prescaler");
178179

179180
TimHandle.Init.Period = (us - 1) / obj->prescaler;
180-
MBED_ASSERT(TimHandle.Init.Period < 0xFFFF);
181+
if (TimHandle.Init.Period > 0xFFFF)
182+
error("PWM: out of range period");
181183

182184
TimHandle.Init.ClockDivision = 0;
183185
TimHandle.Init.CounterMode = TIM_COUNTERMODE_UP;

0 commit comments

Comments
 (0)