GL GPS Integration verification

Code review

Review the implementation of the PAL code for you platform. Verify that at least the following functionalities are implemented:

  1. The Diagnostic output API GpsHalDiagLine()
  2. The NVSTORAGE APIs.

Don't proceed to further testing unless you have these functionalities in place. The results would be quite disappointing and make your boss quite unhappy.

Platform test

Platform test hardware

To perform the platform test you will need to have access to strong GPS signals.

  • Calibrated GPS simulator might seems like a best option, but indeed they are expensive and quite difficult to use properly.
  • The roof top antenna is a very convenient option. Make sure you have active antenna with enough gain to compensate the signal loss in the drop down cable.
  • If none of above is available, just go outside to some open space with your platform. Hopefully you have something portable.

Platform test procedure

Very simple indeed.

  • Run the glgpsapp for 10 minutes while logging the data.
  • Look at the very last $PGLOR,PFM message in the log file.
    • If the message reads: $PGLOR,PFM,HAL,P,..,RF,P,...,RTC,C,STO,C,LTO,C... you successfully passed the platform test
    • If you see any 'F' or '-' characters in it - platform failed the test.
      • PAL,F, means that PAL performance is not meeting the requirements.
      • RF,F, means that Antenna/RF performance is not meeting the requirements.
      • RTC,- means that RTC feature of the chip was not exercised
      • STO,- means that Non volatile storage feature of GLCT/PAL of was not confirmed
      • LTO,- means that LTO feature of GLCT/PAL of was not confirmed

Once you successfully passed the platform test proceed to the system test.

Otherwise you need to modify the platform SW or HW before proceeding any further.

What to do if the PAL test failed.

  • Review the way how you implemented communication with serial driver.
  • If you believe that PAL functions GpsHalWaitForEvent() and GpsHalChipsetWrite() are implemented properly you need to review the implementation of the serial driver.

What to do if the RF test failed.

  • Consult your RF guru.

What to do if the RTC test failed.

  • Make sure that 32 KHz clock is connected to GL ASIC
  • Make sure that RESET pin of the GL ASIC is not toggled unless the complete platform reset is performed.

What to do if the STO or LTO tests are failed.

  • Review the implementation of the corresponding PAL APIs

System test

The first system you wan to do is the series of autonomous starts. Again for that sort of tests you don't need an expensive GPS simulator. Roof to antenna or you platform on a parking lot will do just good.

  • Run the glgpsapp with "auton-test" job selected.
  • Run the glstat "logfilename.txt"

The results should be as good as in the table below:

                                     Acc(m)                     TTF(s)
Test Case     Total  Valid Yield    Max    95%    67%  50%  Max   95%   67%   50%
Cold Starts    5       5   100%    26.1  22.8   10.3  8.9  52.9 44.9  39.9  34.9
Factory Starts 5       5   100%    20.7  13.4    9.4  7.8  47.9 45.9  40.9  39.9
Warm Starts    5       5   100%    10.1   9.4    8.6  5.2  28.9 28.9  28.9  28.9
Hot Starts     5       5   100%    40.3  25.6   13.4   10  18.9 1.0   1.0    1.0
 All Classes Files Functions Variables Typedefs Enumerations Enumerator Defines