ABB semaphore protection overhaul The ABB semaphone protection logic that came with TCS211 from TI was broken in several ways: * Some semaphore-protected functions were called from Application_Initialize() context. NU_Obtain_Semaphore() called with NU_SUSPEND fails with NU_INVALID_SUSPEND in this context, but the return value wasn't checked, and NU_Release_Semaphore() would be called unconditionally at the end. The latter call would increment the semaphore count past 1, making the semaphore no longer binary and thus no longer effective for resource protection. The fix is to check the return value from NU_Obtain_Semaphore() and skip the NU_Release_Semaphore() call if the semaphore wasn't properly obtained. * Some SPI hardware manipulation was being done before entering the semaphore- protected critical section. The fix is to reorder the code: first obtain the semaphore, then do everything else. * In the corner case of L1/DSP recovery, l1_abb_power_on() would call some non-semaphore-protected ABB & SPI init functions. The fix is to skip those calls in the case of recovery. * A few additional corner cases existed, all of which are fixed by making ABB semaphore protection 100% consistent for all ABB functions and code paths. There is still one remaining problem of priority inversion: suppose a low- priority task calls an ABB function, and some medium-priority task just happens to preempt right in the middle of that semaphore-protected ABB operation. Then the high-priority SPI task is locked out for a non-deterministic time until that medium-priority task finishes its work and goes back to sleep. This priority inversion problem remains outstanding for now.

;********************************************************************************
;*** File           : gmmaa.pdf
;*** Creation       : Wed Mar 11 09:58:03 CST 2009
;*** XSLT Processor : Apache Software Foundation / http://xml.apache.org/xalan-j / supports XSLT-Ver: 1
;*** Copyright      : (c) Texas Instruments AG, Berlin Germany 2002
;********************************************************************************
;*** Document Type  : Service Access Point Specification
;*** Document Name  : gmmaa
;*** Document No.   : 8441.107.99.001
;*** Document Date  : 1999-06-22
;*** Document Status: BEING_PROCESSED
;*** Document Author: ANS
;********************************************************************************



PRAGMA 	SRC_FILE_TIME 	"Thu Nov 29 09:41:58 2007"
PRAGMA 	LAST_MODIFIED 	"1999-06-22"
PRAGMA 	ID_AND_VERSION 	"8441.107.99.001"






VALTAB 	VAL_aa_timer
VAL 	DEF 	 	"value is incremented in multiples of 1 min"
VAL 	0 	GMMAA_TIMER_2_SEC 	"value is incremented in multiples of 2 sec"
VAL 	1 	GMMAA_TIMER_1_MIN 	"value is incremented in multiples of 1 min"
VAL 	2 	GMMAA_TIMER_1_DH 	"value is incremented in multiples of 1 decihour"
VAL 	7 	GMMAA_TIMER_DEACT 	"timer is deactivated"




VAR 	aa_timer 	"GPRS READY timer" 	B

VAL 	@p_gmmaa - VAL_aa_timer@ 	







; GMMAA_ESTABLISH_REQ 	0x2500
; GMMAA_RELEASE_IND 	0x6500
; GMMAA_ESTABLISH_REJ 	0x6501
; GMMAA_TIMER_REQ 	0x2501



PRIM 	GMMAA_ESTABLISH_REQ 	0x2500
{
}






PRIM 	GMMAA_RELEASE_IND 	0x6500
{
}






PRIM 	GMMAA_ESTABLISH_REJ 	0x6501
{
}






PRIM 	GMMAA_TIMER_REQ 	0x2501
{
 	aa_timer 	 ; GPRS AA-READY  timer
}