ReSpeaker Core 2.0

  1. 3.5mm Headphone jack: Output audio. You can plug active speakers or Headphones into this port

  2. USB OTG: This USB Port is used to connect to your computer via serial mode of putty (or other serial tools)

  3. USB Power Input: This port is used to provide power for ReSpeaker Core v2.0

  4. Speaker Jack: Output audio for passive speakers. Jst 2.0 Socket

  5. UART: You also can connect the ReSpeaker Core v2.0 with your computer via this UART port

  6. 8 Pins GPIO: General Purpose Input Output interface for extended applications

  7. SD Card Slot: To plug in micro-SD card

  8. eMMC: Embedded Multi Media Card. You can burn the image into eMMC, so that the ReSpeaker Core v2.0 can boot from the eMMC

  9. USB Host: You can plug USB device, such as USB mouse,USB keyboard and USB flash disk into ReSpeaker Core v2.0 via those two USB hosts

  10. Ethernet: Access to the Internet

  11. HDMI: Output video

  12. Bluetooth and Wi-Fi Antenna: The onboard Antenna is for WIFI and Bluetooth. Also we provide a interface for 2.4G Antenna or PCB Antenna

  13. Grove Socket: Grove Socket for digital or I2C.

Currently, the Sam CLI cannot be used to set up the ReSpeaker Core 2.0, so you will have to manually install assistants. Please scroll down to the bottom of this page to follow the installation instructions.

SdCard / eMMC

Download and flash the ReSpeaker with this image from the official ReSpeaker OneDrive folder.

Install Snips

Follow these install commands:

sudo apt-get update
sudo apt-get install -y dirmngr
sudo apt-get install -y apt-transport-https
sudo bash -c 'echo "deb stable main" > /etc/apt/sources.list.d/snips.list'
sudo apt-key adv --keyserver --recv-keys D4F50CDCA10A2849
sudo apt-get update
sudo apt-get install -y snips-platform-voice
sudo apt-get install -y snips-platform-demo
sudo apt-get install -y snips-tts
sudo apt-get install -y snips-watch
sudo apt-get install -y snips-template snips-skill-server

PulseAudio Sound Configuration

The Respeaker core v2 is using pulsaudio. We need to allow the snips service user to access the pulse audio service:

sudo usermod -a -G pulse-access _snips

For a better sound experience you need to modify the default pulse audio daemon configuration:

sudo vi /etc/pulse/daemon.conf

This file need to contains the lines:

default-fragments = 5
default-fragment-size-msec = 2

Update the snips-audio-server service configuration file

sudo tee /lib/systemd/system/snips-audio-server.service > /dev/null <<EOS
Description=Snips Audio Server pulseaudio.service
sudo systemctl daemon-reload

Update the PulseAudio service configuration file:

sudo tee /lib/systemd/system/pulseaudio.service > /dev/null <<EOS
Description=PulseAudio Daemon
ExecStart=/usr/bin/pulseaudio -v --daemonize=no --system --realtime=no --log-target=journal
ExecStop=/usr/bin/pulseaudio -k
sudo systemctl daemon-reload

Create the snips-audio-server runtime directory

sudo mkdir /var/snips-audio-server
sudo chown _snips:_snips /var/snips-audio-server

Create the snips-audio-server prestart script

sudo tee /usr/local/bin/ > /dev/null <<'EOS'
# name of the mic and speaker to use
# wait for the source to exist
for (( ; ; ))
sleep 1
found=`pactl list sources | grep Name: | grep -v ".monitor" | grep ${mic} | wc -l `
if [ "$found" == "1" ]
sleep 5
sudo chmod +x /usr/local/bin/

Workaround for devices without network connection

The network name resolution is not working without a connection. you need to hardcode the ip address of the mqtt broker. Edit the snips.toml and change localhost to :

sudo vi /etc/snips.toml

Installing the assistant (without Sam)

Before running the install assistant commands, you have to connect to your ReSpeaker using SSH, Serial, etc., you can follow the official tutorial here. Delete the previous assistant if there is one.

$ sudo rm -rf /usr/share/snips/assistant/

Unzip your new assistant in the right ReSpeaker's folder

$ sudo unzip <> -d /usr/share/snips/

The assistant is now installed, let’s relaunch the different snips components:

$ sudo systemctl restart 'snips-*'

If you also have actions in your assistant, you'll need to Deploy your apps manually.