MEC15xxEVB ASSY6853

Overview

The MEC15xxEVB_ASSY6853 kit is a future development platform to evaluate the Microchip MEC15XX series microcontrollers. This board needs to be mated with part number MEC1501 144WFBA SOLDER DC ASSY 6860(cpu board) in order to operate.

MEC15XX EVB ASSY 6853

Hardware

  • MEC1501HB0SZ ARM Cortex-M4 Processor
  • 256 KB RAM and 64 KB boot ROM
  • Keyboard interface
  • ADC & GPIO headers
  • UART0, UART1, and UART2
  • FAN0, FAN1, FAN2 headers
  • FAN PWM interface
  • JTAG/SWD, ETM and MCHP Trace ports
  • PECI interface 3.0
  • I2C voltage translator
  • 10 SMBUS headers
  • 4 SGPIO headers
  • VCI interface
  • 5 independent Hardware Driven PS/2 Ports
  • eSPI header
  • 3 Breathing/Blinking LEDs
  • 2 Sockets for SPI NOR chips
  • One reset and VCC_PWRDGD pushbuttons
  • One external PCA9555 I/O port with jumper selectable I2C address.
  • One external LTC2489 delta-sigma ADC with jumper selectable I2C address.
  • Board power jumper selectable from +5V 2.1mm/5.5mm barrel connector or USB Micro A connector.

For more information about the SOC please see the MEC1501 Reference Manual [1]

Supported Features

The mec15xxevb_assy6853 board configuration supports the following hardware features:

Interface Controller Driver/Component
NVIC on-chip nested vector interrupt controller
SYSTICK on-chip systick
UART on-chip serial port
GPIO on-chip gpio

Other hardware features are not currently supported by Zephyr (at the moment)

The default configuration can be found in the boards/arm/mec15xxevb_assy6853/mec15xxevb_assy6853_defconfig Kconfig file.

Connections and IOs

Microchip to provide the schematic for this board.

System Clock

The MEC1501 MCU is configured to use the 48Mhz internal oscillator with the on-chip PLL to generate a resulting EC clock rate of 12 MHz. See Processor clock control register in chapter 4 “4.0 POWER, CLOCKS, and RESETS” of the data sheet in the references at the end of this document.

Serial Port

UART0 is configured for serial logs.

Jumper settings

Please follow the jumper settings below to properly demo this board. Advanced users may deviate from this recommendation.

Jumper setting for MEC15xx EVB Assy 6853 Rev A1p0

Boot-ROM Straps.

These jumpers configure MEC1501 Boot-ROM straps.

+————-+———- -+————–+————-+ | JP93 | JP11 | JP46 | JP96 | | (CMP_STRAP) | (CR_STRAP) | (VTR2_STRAP) | (BSS_STRAP) | +=============+============+==============+=============+ | 2-3 | 1-2 | 2-3 | 1-2 | +————-+————+————–+————-+

JP96 1-2 pulls SHD SPI CS0# up to VTR2 MEC1501 Boot-ROM samples SHD SPI CS0# and if high loads from SHD SPI.

Peripheral Routing Jumpers

Each column of the following table illustrates how to enable UART0, JTAG, PVT SPI, SHD SPI and LED0-2 respectively.

JP68 (UART0) JP9 (JTAG) JP38 (PVT SPI) JP98 (SHD SPI) JP41 (LED0-2)
1-2 2-3 2-3 2-3 1-2
4-5 5-6 5-6 5-6 3-4
8-9 8-9 8-9 8-9 5-6
  11-12 11-12 11-12  
    14-15 14-15  
    17-18 20-21  

Jumper settings for MEC1501 144WFBGA Socket DC Assy 6883 Rev B1p0

The jumper configuration explained above covers the base board. The ASSY 6883 MEC1501 CPU board provides capability for an optional, external 32KHz clock source. The card includes a 32KHz crystal oscillator. The card can also be configured to use an external 50% duty cycle 32KHz source on the XTAL2/32KHZ_IN pin. Note, firmware must set the MEC15xx clock enable register to select the external source matching the jumper settings. If using the MEC15xx internal silicon oscillator then the 32K jumper settings are don’t cares. JP1 is for scoping test clock outputs. Please refer to the schematic in reference section below.

Parallel 32KHz crystal configuration

JP2 JP3
1-2 2-3

External 32KHz 50% duty cycle configuration

JP2 JP3
NC 1-2

Jumper settings for MEC1503 144WFBGA Socket DC Assy 6856 Rev B1p0

The MEC1503 ASSY 6856 CPU card does not include an onboard external 32K crystal or oscillator. The one jumper block JP1 is for scoping test clock outputs not for configuration. Please refer to schematic in reference section below.

Programming and Debugging

This board comes with a Cortex ETM port which facilitates tracing and debugging using a single physical connection. In addition, it comes with sockets for JTAG only sessions.

Flashing

  1. Connect the SPI Dongle ASSY 6791 to J36 (SPI dongle) in order to flash and boot from SHD SPI NOR. Then proceed to flash using Dediprog SF100 or a similar tool for flashing SPI chips.

    Note

    Remember that SPI MISO/MOSI are swapped on dediprog headers!

  2. Run your favorite terminal program to listen for output. Under Linux the terminal should be /dev/ttyACM0. For example:

    $ minicom -D /dev/ttyACM0 -o
    

    The -o option tells minicom not to send the modem initialization string. Connection should be configured as follows:

    • Speed: 115200
    • Data: 8 bits
    • Parity: None
    • Stop bits: 1
  3. Connect the MEC15xxEVB_ASSY_6853 board to your host computer using the UART0 port. Then build :ref: Hello World application. It is important to generate a binary with a new load address, for example do the following:

    ${OBJCOPY} --change-addresses -0xe0000 -O binary -S ${in_elf} ${out_bin}
    

    Once you obtain the binary, proceed to use the microchip tool mec15xx_spi_gen in order to create the final binary. This binary is what you need to flash in your spi nor.

    # On Linux/macOS
    cd $ZEPHYR_BASE/samples/hello_world
    mkdir build && cd build
    
    # On Windows
    cd %ZEPHYR_BASE%\samples\hello_world
    mkdir build & cd build
    
    # Use cmake to configure a Ninja-based build system:
    cmake -GNinja -DBOARD=mec15xxevb_assy6853 ..
    
    # Now run ninja on the generated build system:
    ninja
    ninja flash
    

    You should see “Hello World! mec15xxevb_assy6853” in your terminal.

Debugging

You can debug an application in the usual way. Here is an example for the Hello World application.

# On Linux/macOS
cd $ZEPHYR_BASE/samples/hello_world
# If you already made a build directory (build) and ran cmake, just 'cd build' instead.
mkdir build && cd build

# On Windows
cd %ZEPHYR_BASE%\samples\hello_world
# If you already made a build directory (build) and ran cmake, just 'cd build' instead.
mkdir build & cd build

# Use cmake to configure a Ninja-based build system:
cmake -GNinja -DBOARD=mec15xxevb_assy6853 ..

# Now run ninja on the generated build system:
ninja debug