The Simplicity Command Line Syntax is as below. It flashes the image in the specified <filename> to the target device indicated by J-Link serial number <serial number>, starting at the specified <address>. The <serial number> can be absent if only one device connected.
commander flash <filename> --address <address> --serialno <serial number>

Also please find the KBA_BT_0908, it demonstrates how to access the Current Time characteristic. 

The SPI driver support the SPI capabilities of EFM32/EZR32/EFR32 USARTs. The driver is fully reentrant and several driver instances can coexist. It provide two kinds of transfer functions, synchronous and asynchronous. Synchronous transfer functions are blocking and will not return to caller before the transfer has completed. Asynchronous transfer functions report transfer completion with callback functions. All of the transfers are done using DMA.

Take EFM32PG1B as example to demonstrate how to initialize the USARTs as SPI mode. EFM32PG1B has two USARTs, the example show how to initialize USART0 as a SPI Slave, and initialize USART1 as a SPI Master with emdrv (SPIDRV), it's the easiest way to demonstrate the SPI without connecting any external components but just need to connect the corresponding port pins between SPI Slave and Master. Please refer to the SPIDRV_SLAVE_USART0 and SPIDRV_MASTER_USART1 config structure for the port pins location information.

After finishing the SPI initialization, SPI Slave will start a few bytes transmitting by calling an asynchronous function SPIDRV_STransmit() which will be returned soon, the callback function will be executed once the DMA finished the transfer. SPI Master will start the receiving transfer by calling an synchronous function SPIDRV_MReceiveB(), it will not return until received specified length of data from Slave.

For the SPI Slave receiving case, it will start the SPI slave receive transfer in non-blocking, and the data transmitting from the Master will caused the report of receiving transfer completion with callback function.

  // Start a SPI slave transmit transfer
  SPIDRV_STransmit( handleSlave, slaveTxBuffer, sizeof(slaveTxBuffer), slaveProcessTxDone, 0);
  // Receive data using a blocking receive transfer
  SPIDRV_MReceiveB(handleMaster, masterRxBuffer, sizeof(masterRxBuffer));

  // Start a SPI slave receive transfer.
  SPIDRV_SReceive( handleSlave, slaveRxBuffer, sizeof(slaveRxBuffer), slaveReceiveComplete, 0);
  // Transmit data using a blocking transmit function
  SPIDRV_MTransmitB(handleMaster, masterTxBuffer, sizeof(masterTxBuffer));

Attached is the example code of EFM32PG1B for the SPI Slave and Master transfer on emdrv (SPIDRV).

Below is the screenshot for illustrating the data transfer.

 

The SPI driver support the SPI capabilities of EFM32/EZR32/EFR32 USARTs. The driver is fully reentrant and several driver instances can coexist. It provide two kinds of transfer functions, synchronous and asynchronous. Synchronous transfer functions are blocking and will not return to caller before the transfer has completed. Asynchronous transfer functions report transfer completion with callback functions. All of the transfers are done using DMA.

Take EFM32PG1B as example to demonstrate how to initialize the USARTs as SPI mode. EFM32PG1B has two USARTs, the example show how to initialize USART0 as a SPI Slave, and initialize USART1 as a SPI Master with emdrv (SPIDRV), it's the easiest way to demonstrate the SPI without connecting any external components but just need to connect the corresponding port pins between SPI Slave and Master. Please refer to the SPIDRV_SLAVE_USART0 and SPIDRV_MASTER_USART1 config structure for the port pins location information.

After finishing the SPI initialization, SPI Slave will start a few bytes transmitting by calling an asynchronous function SPIDRV_STransmit() which will be returned soon, the callback function will be executed once the DMA finished the transfer. SPI Master will start the receiving transfer by calling an synchronous function SPIDRV_MReceiveB(), it will not return until received specified length of data from Slave.

For the SPI Slave receiving case, it will start the SPI slave receive transfer in non-blocking, and the data transmitting from the Master will caused the report of receiving transfer completion with callback function.

  // Start a SPI slave transmit transfer
  SPIDRV_STransmit( handleSlave, slaveTxBuffer, sizeof(slaveTxBuffer), slaveProcessTxDone, 0);
  // Receive data using a blocking receive transfer
  SPIDRV_MReceiveB(handleMaster, masterRxBuffer, sizeof(masterRxBuffer));

  // Start a SPI slave receive transfer.
  SPIDRV_SReceive( handleSlave, slaveRxBuffer, sizeof(slaveRxBuffer), slaveReceiveComplete, 0);
  // Transmit data using a blocking transmit function
  SPIDRV_MTransmitB(handleMaster, masterTxBuffer, sizeof(masterTxBuffer));

Attached is the example code of EFM32PG1B for the SPI Slave and Master transfer on emdrv (SPIDRV).

 

The SPI driver support the SPI capabilities of EFM32/EZR32/EFR32 USARTs. The driver is fully reentrant and several driver instances can coexist. It provide two kinds of transfer functions, synchronous and asynchronous. Synchronous transfer functions are blocking and will not return to caller before the transfer has completed. Asynchronous transfer functions report transfer completion with callback functions. All of the transfers are done using DMA.

Take EFM32PG1B as example to demonstrate how to initialize the USARTs as SPI mode. EFM32PG1B has two USARTs, the example show how to initialize USART0 as a SPI Slave, and initialize USART1 as a SPI Master with emdrv (SPIDRV), it's the easiest way to demonstrate the SPI without connecting any external components but just need to connect the corresponding port pins between SPI Slave and Master. Please refer to the SPIDRV_SLAVE_USART0 and SPIDRV_MASTER_USART1 config structure for the port pins location information.

After finishing the SPI initialization, SPI Slave will start a few bytes transmitting by calling an asynchronous function SPIDRV_STransmit() which will be returned soon, the callback function will be executed once the DMA finished the transfer. SPI Master will start the receiving transfer by calling an synchronous function SPIDRV_MReceiveB(), it will not return until received specified length of data from Slave.

For the SPI Slave receiving case, it will start the SPI slave receive transfer in non-blocking, and the data transmitting from the Master will caused the report of receiving transfer completion with callback function.

  // Start a SPI slave transmit transfer
  SPIDRV_STransmit( handleSlave, slaveTxBuffer, sizeof(slaveTxBuffer), slaveProcessTxDone, 0);
  // Receive data using a blocking receive transfer
  SPIDRV_MReceiveB(handleMaster, masterRxBuffer, sizeof(masterRxBuffer));

  // Start a SPI slave receive transfer.
  SPIDRV_SReceive( handleSlave, slaveRxBuffer, sizeof(slaveRxBuffer), slaveReceiveComplete, 0);
  // Transmit data using a blocking transmit function
  SPIDRV_MTransmitB(handleMaster, masterTxBuffer, sizeof(masterTxBuffer));

Attached is the example code of EFM32PG1B for the SPI Slave and Master transfer on emdrv (SPIDRV).

 

I have updated the example based on the latest MCU SDK v5.8.3.0

@Avid,

If you need to change the master CS pin to LOC20, you should modify the structure of SPIDRV_MASTER_USART1.

The SPI driver support the SPI capabilities of EFM32/EZR32/EFR32 USARTs. The driver is fully reentrant and several driver instances can coexist. It provide two kinds of transfer functions, synchronous and asynchronous. Synchronous transfer functions are blocking and will not return to caller before the transfer has completed. Asynchronous transfer functions report transfer completion with callback functions. All of the transfers are done using DMA.

Take EFM32PG1B as example to demonstrate how to initialize the USARTs as SPI mode. EFM32PG1B has two USARTs, the example show how to initialize USART0 as a SPI Slave, and initialize USART1 as a SPI Master with emdrv (SPIDRV), it's the easiest way to demonstrate the SPI without connecting any external components but just need to connect the corresponding port pins between SPI Slave and Master. Please refer to the SPIDRV_SLAVE_USART0 and SPIDRV_MASTER_USART1 config structure for the port pins location information.

After finishing the SPI initialization, SPI Slave will start a few bytes transmitting by calling an asynchronous function SPIDRV_STransmit() which will be returned soon, the callback function will be executed once the DMA finished the transfer. SPI Master will start the receiving transfer by calling an synchronous function SPIDRV_MReceiveB(), it will not return until received specified length of data from Slave.

For the SPI Slave receiving case, it will start the SPI slave receive transfer in non-blocking, and the data transmitting from the Master will caused the report of receiving transfer completion with callback function.

  // Start a SPI slave transmit transfer
  SPIDRV_STransmit( handleSlave, slaveTxBuffer, sizeof(slaveTxBuffer), slaveProcessTxDone, 0);
  // Receive data using a blocking receive transfer
  SPIDRV_MReceiveB(handleMaster, masterRxBuffer, sizeof(masterRxBuffer));

  // Start a SPI slave receive transfer.
  SPIDRV_SReceive( handleSlave, slaveRxBuffer, sizeof(slaveRxBuffer), slaveReceiveComplete, 0);
  // Transmit data using a blocking transmit function
  SPIDRV_MTransmitB(handleMaster, masterTxBuffer, sizeof(masterTxBuffer));

Attached is the example code of EFM32PG1B for the SPI Slave and Master transfer on emdrv (SPIDRV).

 

The SPI driver support the SPI capabilities of EFM32/EZR32/EFR32 USARTs. The driver is fully reentrant and several driver instances can coexist. It provide two kinds of transfer functions, synchronous and asynchronous. Synchronous transfer functions are blocking and will not return to caller before the transfer has completed. Asynchronous transfer functions report transfer completion with callback functions. All of the transfers are done using DMA.

Take EFM32PG1B as example to demonstrate how to initialize the USARTs as SPI mode. EFM32PG1B has two USARTs, the example show how to initialize USART0 as a SPI Slave, and initialize USART1 as a SPI Master with emdrv (SPIDRV), it's the easiest way to demonstrate the SPI without connecting any external components but just need to connect the corresponding port pins between SPI Slave and Master. Please refer to the SPIDRV_SLAVE_USART0 and SPIDRV_MASTER_USART1 config structure for the port pins location information.

After finishing the SPI initialization, SPI Slave will start a few bytes transmitting by calling an asynchronous function SPIDRV_STransmit() which will be returned soon, the callback function will be executed once the DMA finished the transfer. SPI Master will start the receiving transfer by calling an synchronous function SPIDRV_MReceiveB(), it will not return until received specified length of data from Slave.

For the SPI Slave receiving case, it will start the SPI slave receive transfer in non-blocking, and the data transmitting from the Master will caused the report of receiving transfer completion with callback function.

  // Start a SPI slave transmit transfer
  SPIDRV_STransmit( handleSlave, slaveTxBuffer, sizeof(slaveTxBuffer), slaveProcessTxDone, 0);
  // Receive data using a blocking receive transfer
  SPIDRV_MReceiveB(handleMaster, masterRxBuffer, sizeof(masterRxBuffer));

  // Start a SPI slave receive transfer.
  SPIDRV_SReceive( handleSlave, slaveRxBuffer, sizeof(slaveRxBuffer), slaveReceiveComplete, 0);
  // Transmit data using a blocking transmit function
  SPIDRV_MTransmitB(handleMaster, masterTxBuffer, sizeof(masterTxBuffer));

Attached is the example code of EFM32PG1B for the SPI Slave and Master transfer on emdrv (SPIDRV).

 

hi Gerhard,

For EFR32, the reset state of the IO pins is disabled: high impedance, no pull resistor. The best solution is adding external pull-up/pull-down resistor to ensure the fixed status of the gpio during reset.

Thanks