Lines Matching refs:value

249 	  original UBaseType_t return value.
308 	  the raw run time counter value, the new function returns the percentage of
343 	  (configMAX_PRIORITIES - 1) should it be set to a value above that priority.
387 	  vTaskDelayUntil(), with the addition of returning a value to
466 	  configISR_STACK_SIZE_WORDS is defined to a non zero value, which causes
488 	+ Added xTaskCatchUpTicks(), which corrects the tick count value after the
704 	+ Only fill the stack of a newly created task with a known value if stack
727 	  value of than than 0 when the system boots.  This can be useful for
1132 	  incorrect value being written to the basepri register.  This only effects
1169 	  returning a value in every possible path through the respective functions.
1216 	  ensure the alarm value (compare match value) cannot be set to zero when a
1353 	  returns a value).
1492 	  mask value.  The restore macro now uses the previous mask value.  These
1711 	+ The value passed into tracePRIORITY_SET() has been corrected for the case
1830 	  what its value is (within the valid range set by the microcontroller
1880 	  with an incorrect	value.  This has been fixed.
2103 	  value of -1.
2378 	  stated a maximum block time, and the return value of the function needed
2394 	  tick count value.
2395 	+ Bug fix:  The 'value' of the event list item is updated when the priority
2440 	+ Corrected the value passed to the WDG_PeriodValueConfig() library
2448 	  DOS tick back to its proper value when the scheduler exits.  Thanks
2452 	  BP value would never get used so this did not cause a problem, but it has
2519 	+ The compare match load value on LPC2000 ports now has 1 added to correct
2520 	  the value used.
2547 	  prescale value was written to T0_PC instead of T0_PR.  This would have
2548 	  no effect unless a prescale value was actually required.  This has been
2567 	+ Both PIC18 ports now initialise the TBLPTRU to 0 as this is the value
2882 	+ Changed odd calculation of initial pxTopOfStack value when
2923 	  value (see the API documentation).
2980 	  port was also calculating a register value incorrectly resulting in the
3088 	  the higher original value.