Shield Testing Instructions

  1. Confirm shorting jumpers are installed on shield
    1. On JP6 to power shield from FRDM’s P3V3 supply rail
    2. On J11 between VIN and 5V to power buck converter
  2. Confirm solder jumpers are shorted: JP1, JP2, JP7, JP8
  3. Confirm LCD is installed on J3.
  4. Program FRDM-KL25Z with test code. This takes two steps because our free tools are limited to a 32 kB object file size.
    1. Open the Overlay project (Tools/TestCode/Overlay), build and download to MCU. This will program text font information into the MCU’s flash memory.
    2. Close the Overlay project.
    3. Open the Shield_Base_v14 project (Tools/TestCode/Shield_Base_v14), build and download to MCU. This will program a test program onto the MCU. It won’t erase the the text font information (which is located elsewhere in flash memory) because the Debug->Settings->Flash Download Erase Sectors selection tells the downloader to erase only the flash sectors used by this project. Both this and the Overlay project have this option selected to retain these memory contents when programming.
  5. Run the program by resetting the MCU. It will (try to) do the following:
    1. Initialize debug signals and RGB LED.
    2. Light the blue RGB LED.
    3. Initialize the sound system and test it by playing a short chirp.
    4. Initialize the ADC and white HBLED.
    5. Light the white LED briefly, and measure its current (I_HBLED). This also tests the buck converter, the ADC, and the current sense feedback path.
    6. Dim or turn off the white LED.
    7. Initialize the LCD subsystem and text fonts. If text font initialization fails, program lights red LED and stops here.
    8. Test LCD: draw colored lines to fill screen, erase, write “Test Code” on LCD.
    9. Display I_HBLED from the test above. It depends on voltage input to buck converter, selected by J11. Should be 54-56 mA if VIN = 5V, and about 4 mA if VIN = 3.3V.
    10. Initialize I2C and accelerometer. If initialization fails, program lights red LED and stops here.
    11. Initialize RTOS and start kernel.
    12. Application program threads start running:
      1. Accelerometer testing: Thread_Read_Accelerometer reads accelerometer and displays calculated roll and pitch values.
      2. Touchscreen testing: Thread_Read_TS reads touchscreen. Based on position of touch, may draw lines on screen or may mute/unmute sound system.
      3. Audio testing: Press Unmute on screen. Thread_Sound_Manager and Thread_Refill_Sound_Buffer generate random sounds on speaker. Signal may be monitored on TP8 (DAC output).
      4. Thread_Update_Screen moves/colors paddle at bottom of screen based on accelerometer readings.