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.

FC Tourmaline firmware differs from Magnetite in two principal ways when it
comes to Mot C139 target support:

* C139 LCD support is implemented in a more forward-looking manner: instead of
  emulating TI's C-Sample at the lowest R2D driver level and therefore being
  forever limited to 84x48 pixel display size, Tourmaline implements a new
  96x64 pixel framebuffer, matching the native LCD size of C1xx phones.  The UI
  configuration is still black&white only though - the Mother of FreeCalypso
  has no current plans to support color UI on smaller LCD sizes than TI's
  original 176x220 pix.

* Our aftermarket FFS configuration has been changed from 64x3 at 0x3C0000 to
  64x7 at 0x300000.  Our earlier 64x3 config was chosen back in 2015, at that
  time we didn't know how much room we would end up needing for the firmware
  image vs. how much FFS content we would eventually have, and this 64x3 config
  is now deemed to be too small, allowing only one 64 KiB sector for FFS
  content.  Our new FC Tourmaline aftermarket FFS config supports up to 320 KiB
  of FFS content, matches what we use on other platforms with 4 MiB flash chips,
  leaves 3 MiB for the firmware image (our current smallbw UI fw is only 2 MiB),
  and still avoids intersection with Motorola's (or rather Compal's) original
  FFS, which is important for avoiding problems in converting C139 phones back
  and forth between Motorola and FreeCalypso firmwares.