text: The.
  Renesas Synergy S-Series
  48,16€ – 50,56€
  Out of stock
  The..
  Get ultimate performance for demanding applications with a 240 MHz Arm® Cortex®-M4 core, largest flash memory available, multiple high-speed secure connectivity channels, and zero wait-state fast SRAM for on-chip graphic display buffers and high-speed communication.
  Applications:
  - Industrial automation
  - Internet of Things
  - Human Interface Device
  Specifications
  Documentation
  3D View
  Applications:
  - Industrial automation
  - Internet of Things
  - Human Interface Device
  Module specifications
  As stated above, this module sports a Renesas S7G2 microcontroller, the controller at the high end of the Synergy Series.
  This module can be powered by either a 3V3 supply or by a 2V8 one in order to improve power performance. It’s able to control any class 2 or 3 Rhomb.io motherboard with up to 3 module sockets, plus it has networking, memory and video capabilities.
  In order to manage all GPIOs in Rhomb.io sockets, this module includes a GPIO Expander IC driven by the main controller via I2C interface. This adds 8 GPIO signals that are used to manage sockets 2 and 3 of the Rhomb.io standard.
  It has two built-in 4-channel analog switches that allow the user to switch between a SDIO interface or a QSPI one, which adds a lot of flexibility for potential projects.
  1User can switch between SDIO or QSPI I/F by setting the level of a GPIO.
  2User can choose where the USB I/F is connected in the module, either to the USB pins of the module connectors, or the OTG pins by setting the level of a GPIO.
  …The following figure identifies the main Integrated Circuits (IC) onboard.
  The next figure shows the Block Diagram for the Renesas Synergy Master Module.
  User Interfaces
  The user can choose wether this master module is supplied by a 3.3V or a 2.8V source simply by closing or opening the solder jumpers at the top-right corner of the module. 2.8V supply is recommended for applications requiring a lower power consumption.
  There is a LED controlled by a PWM output pin of the controller for whatever the user might need, debugging, visual validation…
  GPIO Expander
  A GPIO Expander IC is used in this module so that all GPIO needed for Rhomb.io standard can be fullfilled. This IC is managed by the Renesas Synergy S7G2 through I2C1 I/F.
  SDIO/QSPI Switching
  Users can choose between SDIO or QSPI interfaces being active simply by setting P711 signal from the controller HIGH or LOW.
  USB/OTG Switching
  Users can choose between having the USB connected to the OTG or USB0 pins simply by setting P407 signal from the controller HIGH or LOW.
  Connections
  GPIO
  The following table summarizes the GPIOs used on the Renesas Synergy master module.
  I/O signals managed by the I/O Expander can be controlled by the Renesas MCU through the I2C1 bus. I/O Expander P/N is PCAL6416AHF.
  ANALOG
  The following table summarizes the analog ports used on the Renesas Synergy master module.
  PWM
  The following table summarizes the PWM signals used on the Renesas Synergy master module.
  1PWM[1..3] are muxed, with LCD_G5, LCD_G7 and LCD_R0 respectively. In order to have them available, R9, R10 and R21 must be assembled. Special care must be taken when operating the board with this configuration.
  2IO7 is routed and used as a standard GPIO, but it can actually be used as a PWM output.
  INTERRUPTS
  The following table summarizes the INTERRUPTS used on the Renesas Synergy master module. Please note that interrupts used in this module are not hardware interrupts, as all ports capable of being used hardware interrupt are in use under several different capabilities and interfaces.
  1INT4, INT5 and INT6 are connected to INT3_MOD3 through independent 100k resistors due to not having enough IO ports available for interrupt use.
  Serial interfaces
  The following table indicates the available serial interfaces on the Rhomb.io standard and which of them are in use. The table also shows the nomenclature used on the Rhomb.io standard and its corresponding on the schematic.
  1USB can be connected to the OTG or USB0 pins simply by setting P407 signal from the controller HIGH for OTG or LOW for USB0. Default: LOW
  2QSPI can be alternated with SDIO by changing the state of P711 signal that actuates the analog switches splitting them to their respective connector’s pins. LOW state for SDIO, HIGH for QSPI. Default: LOW.
  3SSIDATA1_A can be routed to either SDI or SDO depending on the assembly of R11 and R12. Default: SDO
  The I2C pull-ups resistors should be mounted on the bus, otherwise, the I2C bus will not work. For more details, look at the module specifications for the Rhomb.io standard.
  SDIO
  The next table shows the nomenclature used on the schematic and its corresponding on the rhomb standard for the Secure Digital Input Output (SDIO) interface.
  1SDIO can be alternated with QSPI by changing the state of P711 signal that actuates the analog switches splitting them to their respective connector’s pins. LOW state for SDIO, HIGH for QSPI. Default: LOW.
  For more details, look at the module specifications for the Rhomb.io standard.
  VIDEO
  The next table shows the nomenclature used on the schematic and its corresponding on the rhomb standard for the video interface.
  Networking
  The Rhomb.io Renesas Synergy master module has a 50MHz RMII interface available, which very interesting for potential projects that make use of networks, such as IoT applications.
  The next table shows the nomenclature used on the schematic and its corresponding on the rhomb standard for the video interface.
  Debug
  Debugging is to be done by using the SWD interface, with the signals SWDIO and SWDCLK.
  Power
  As per the supply lines used on the board, there is a summary on the next table.
  1VDD voltage level can be selected through the solder jumpers on the board, 2.8V and 3.3V can be selected. It is the voltage at which the whole module is powered. 2.8V level recommenden for power efficient applications.
  2VIO_OUT is a power output pin that sets the voltage level for slave modules to this master module. VIO_OUT level is the same as VDD.
  3AREF0 and AREF1 are external power inputs that set the high voltage reference level of the analog converters.
  For more details, look at the module specifications for the Rhomb.io standard.
  Other signals
  On the following table it is shown the remaining signals from the Rhomb.io module connectors standard,and other module-specific signals.
  1This external 32.768kHz can be used on the module if instead of C1,C2 and Y1, R30 is assembled.
  2GPIO assigned to output reset signal to any slave modules interfaced to this master module.
  3Non-maskable interrupt request and mode setting pin. Pulled up by default for normal use, should be pulled down for SCI/USB boot mode.
  41-Wire interface in order to read information from the on-module Eeprom memory.
  5Setting USB_SW HIGH directs the USB bus to the OTG module pins, setting it LOW directs it to the USB0 module pins.
  6Set AS_1 LOW state for SDIO interface, HIGH for QSPI interface. Software must be adapted so that the analog switch position matches the interface in use..
  7GPIO assigned to output reset signal to I/O Expander IC interfaced to the Renesas MCU via I2C1 bus.
  8GPIO assigned to read interrupt signal from the I/O Expander IC.
  For more details, look at the module specifications for the Rhomb.io standard.
  Getting started
  Renesas, through its Synergy Gallery web platform (), offers a wide variety of utilities, IDEs, documentation and everything you need to get started. You must create a (free) user account to access Synergy Gallery.
  In this guide we will use the e2 Studio of Renesas, an Eclipse-based IDE, to make a basic example of blink (hello, world!). We will use a Helios board with a Renesas Synergy S7 module. You will also need a JTAG cable like the Segger J-Link or compatible.
  Required hardware & software
  - 1x Helios board (or any other Rhomb.io Class II/III board) (buy here)
  - 1x Rhomb.io Synergy S7 Master Renesas Module (buy here)
  - 1x JTAG cable type J-link by Segger
  - 4x Jumper Wires (with Helios: 2x male-female and 2x male-male)
  - Windows OS (tested with W8 and W10)
  - e2 Studio >= 6.2
  - SSP Framework (Synergy Software Package) >= 1.3.0
  - JTAG drivers for windows
  At the time of writing this tutorial, the Synergy platform does not offer official support for development from Linux/Mac systems or other editors than e2 Studio. In our case we have used Virtualbox on Debian 8 without major problems.
  We will not use any USB cable to power the board, we will get the 5v power directly from the JTAG.
  Caution! Do not attempt to USB-power a Rhomb.io board from Standard I with the Renesas modules, which meet Standard II. You can seriously damage the microcontroller.
  Software Setup
  Log in to renesas.com and create a free user account to download all the software (e2 Studio and SSP Framework) and generate a license file.
  Renesas offers a PDF document called Basics of Renesas Synergy Platform that includes detailed information about the e2 Studio installation process, as well as lots of other information about the Synergy platform. It’s almost essential that you read it to understand the entire Renesas Synergy ecosystem.
  After installation e2 Studio may has selected an incorrect version of the GNU Tools ARM Embedded. e2 Studio needs the 4.9 X and by default you may have the 5.4 X. Use the preferences (Window menu -> Preferences) to enable v4.9.
  Clean the project every time you change the preferences (menu Project -> Clean).
  Hardware Setup
  To upload the code into the Synergy S7 we have used a Segger J-link with an ARM 20-PIN JTAG type connector (during this tutorial we will refer to this specific JTAG). Beware, not all JTAGs use the same connector with the same pin configuration. Make sure your JTAG uses the same combination of pins as shown below, or else find the equivalencies.
  Look at this image to see the JTAG connection with the Helios Board.
  The above image corresponds to the end of the JTAG cable connected to the J-Link. The pin configuration will be reversed at the other end of the JTAG, where we will connect the cables to the Helios board.
  It will not be necessary to connect the USB cable of the board, the voltage is given by the JTAG. Remember, Renesas modules use Rhomb.io Standar II and should not be connected to PCBs with Standar I.
  Create a new e2 Studio project
  Open e2 Studio and create a new project of type Synergy C. The following window will appear:
  We must select the specific model of our Synergy by Rhomb.io module. You can see the model number written on the silicon itself (with magnifying glass), probably corresponding to one of the following:
  - Synergy S7 -> R7FS7627H2
  - Synergy S5 -> R7FS5D97E2
  - Synergy S3 -> R7FS3A77C2
  The siliciums that mount the rhomb.io modules are 145 pins
  In the next screen we are asked to select the initial configuration of the project, we will use the BSP to create a blank project.
  Our project has been created and to continue you must select the Synergy perspective, if you have not done so when creating the project (a dialog asks you) you can do it by clicking the following button in the upper right corner of e2 Studio.
  The Threads Configuration window of the Synergy perspective corresponds to the configuration.xml file in the project’s file explorer.
  The module with the Rhomb.io Synergy S7 includes a led on pin 713 (port 7, pin 13). By default almost all pins are disabled, this means that if we try to give a HIGH/LOW pulse we will not get any results, for this we first have to configure that pin. In our case we want the 713 to be active as output (it doesn’t matter if HIGH or LOW). To do this we look for the PIN713 in the package window, double click on it and in the Pins tab we configure it as Output.
  Before you continue, look for the “Generate Project Content” button inside the Threads Configuration window of the configuration.xml file to apply the changes we have made to pin 713.
  Happy Coding!
  Let’s add the code part that will make our blink. In the file explorer search for the src/hal_entry.c file, this file represents the main Thread of our application, called HAL/Common. We will add the following code:
  #include "hal_data.h" void hal_entry (void) { bool enable = true; while (1) { // Pin 713 = IOPORT_PORT_07_PIN_13. // On C++, pinWrite doesn't allow a boolean param as sencod // argument (requires a data type ioport_level_t). // g_ioport is available here because our thread has that // component (r_ioport) added by default. See components tab in // the configuration.xml file. g_ioport.p_api->pinWrite(IOPORT_PORT_07_PIN_13, enable); isOn =! isOn; for (int i = 0; i < 1E6; i++) { } } }
  The above example has been simplified, but obviously this code would work better with a timer. Alternatively you can also use `tx_thread_sleep(1000);` to insert a delay instead of the for loop.
  We can add more threads to our application from the configuration.xml file, and each thread will have its input file. Threads, thanks to the synergy RTOS model, are tasks that run in parallel, this means, roughly speaking, that your single core microcontroller will be able to do 2 or more things at a time (at human-eye sight).
  Compile the code with the hammer button
  . Once done, use the debug
  button to load the code into the microcontroller. This will give us a debug view of Eclipse. Once it is loaded you will see that the microcontroller does nothing, press the button
  a couple of times in this same perspective to finish the loading process. Once done, the LED should flash. To exit debug view, press the
  button and then press the button
  to switch to Synergy perspective.
  Conclusions
  The Synergy platform works with Logic Express’s RTOS ThreadX operating system as well as his own libraries (SSP). The possibilities of ThreadX along with the Renesas libraries are enormous and could fill hundreds of books.
  Renesas, with its e2 Studio, includes the ThreadX system through a graphical interface inside the Eclipse (e2 Studio). This same GUI also generates the necessary code for our application depending on what we want to do. There are probably people who don’t like the idea that a graphical interface generates the source code, we included, but in our tests we have been able to verify that the GUI of e2 Studio is really useful and very stable, and of course you can always work writting code instead of using the GUI..