SSP v1.3.2 Release Note - synergygallery.renesas.com · SSP v1.3.2 Release Note ... 3. No license,...

Rev.1.00 Nov 2017

Renesas Synergy™ Platform Synergy Software Synergy Software Package

User’s M

anual

www.renesas.com

All information contained in these materials, including products and product specifications, represents information on the product at the time of publication and is subject to change by Renesas Electronics Corp. without notice. Please review the latest information published by Renesas Electronics Corp. through various means, including the Renesas Electronics Corp. website (http://www.renesas.com).

SSP v1.3.2

Release Note

Release N

ote

Notice 1. Descriptions of circuits, software and other related information in this document are provided only to illustrate the operation of

semiconductor products and application examples. You are fully responsible for the incorporation or any other use of the circuits, software, and information in the design of your product or system. Renesas Electronics disclaims any and all liability for any losses and damages incurred by you or third parties arising from the use of these circuits, software, or information.

2. Renesas Electronics hereby expressly disclaims any warranties against and liability for infringement or any other disputes involving patents, copyrights, or other intellectual property rights of third parties, by or arising from the use of Renesas Electronics products or technical information described in this document, including but not limited to, the product data, drawing, chart, program, algorithm, application examples.

3. No license, express, implied or otherwise, is granted hereby under any patents, copyrights or other intellectual property rights of Renesas Electronics or others.

4. You shall not alter, modify, copy, or otherwise misappropriate any Renesas Electronics product, whether in whole or in part. Renesas Electronics disclaims any and all liability for any losses or damages incurred by you or third parties arising from such alteration, modification, copy or otherwise misappropriation of Renesas Electronics products.

5. Renesas Electronics products are classified according to the following two quality grades: "Standard" and "High Quality". The intended applications for each Renesas Electronics product depends on the product’s quality grade, as indicated below. "Standard": Computers; office equipment; communications equipment; test and measurement equipment; audio and visual

equipment; home electronic appliances; machine tools; personal electronic equipment; and industrial robots etc. "High Quality": Transportation equipment (automobiles, trains, ships, etc.); traffic control (traffic lights); large-scale

communication equipment; key financial terminal systems; safety control equipment; etc. Renesas Electronics products are neither intended nor authorized for use in products or systems that may pose a direct threat to human life or bodily injury (artificial life support devices or systems, surgical implantations etc.), or may cause serious property damages (space and undersea repeaters; nuclear power control systems; aircraft control systems; key plant systems; military equipment; etc.). Renesas Electronics disclaims any and all liability for any damages or losses incurred by you or third parties arising from the use of any Renesas Electronics product for which the product is not intended by Renesas Electronics.

6. When using the Renesas Electronics products, refer to the latest product information (data sheets, user’s manuals, application notes, "General Notes for Handling and Using Semiconductor Devices" in the reliability handbook, etc.), and ensure that usage conditions are within the ranges specified by Renesas Electronics with respect to maximum ratings, operating power supply voltage range, heat radiation characteristics, installation, etc. Renesas Electronics disclaims any and all liability for any malfunctions or failure or accident arising out of the use of Renesas Electronics products beyond such specified ranges.

7. Although Renesas Electronics endeavors to improve the quality and reliability of Renesas Electronics products, semiconductor products have specific characteristics such as the occurrence of failure at a certain rate and malfunctions under certain use conditions. Further, Renesas Electronics products are not subject to radiation resistance design. Please ensure to implement safety measures to guard them against the possibility of bodily injury, injury or damage caused by fire, and social damage in the event of failure or malfunction of Renesas Electronics products, such as safety design for hardware and software including but not limited to redundancy, fire control and malfunction prevention, appropriate treatment for aging degradation or any other appropriate measures by your own responsibility as warranty for your products/system. Because the evaluation of microcomputer software alone is very difficult and not practical, please evaluate the safety of the final products or systems manufactured by you.

8. Please contact a Renesas Electronics sales office for details as to environmental matters such as the environmental compatibility of each Renesas Electronics product. Please investigate applicable laws and regulations that regulate the inclusion or use of controlled substances, including without limitation, the EU RoHS Directive carefully and sufficiently and use Renesas Electronics products in compliance with all these applicable laws and regulations. Renesas Electronics disclaims any and all liability for damages or losses occurring as a result of your noncompliance with applicable laws and regulations.

9. Renesas Electronics products and technologies shall not be used for or incorporated into any products or systems whose manufacture, use, or sale is prohibited under any applicable domestic or foreign laws or regulations. You shall not use Renesas Electronics products or technologies for (1) any purpose relating to the development, design, manufacture, use, stockpiling, etc., of weapons of mass destruction, such as nuclear weapons, chemical weapons, or biological weapons, or missiles (including unmanned aerial vehicles (UAVs)) for delivering such weapons, (2) any purpose relating to the development, design, manufacture, or use of conventional weapons, or (3) any other purpose of disturbing international peace and security, and you shall not sell, export, lease, transfer, or release Renesas Electronics products or technologies to any third party whether directly or indirectly with knowledge or reason to know that the third party or any other party will engage in the activities described above. When exporting, selling, transferring, etc., Renesas Electronics products or technologies, you shall comply with any applicable export control laws and regulations promulgated and administered by the governments of the countries asserting jurisdiction over the parties or transactions.

10. Please acknowledge and agree that you shall bear all the losses and damages which are incurred from the misuse or violation of the terms and conditions described in this document, including this notice, and hold Renesas Electronics harmless, if such misuse or violation results from your resale or making Renesas Electronics products available any third party.

11. This document shall not be reprinted, reproduced or duplicated in any form, in whole or in part, without prior written consent of Renesas Electronics.

12. Please contact a Renesas Electronics sales office if you have any questions regarding the information contained in this document or Renesas Electronics products.

(Note 1) "Renesas Electronics" as used in this document means Renesas Electronics Corporation and also includes its majority-owned subsidiaries.

(Note 2) "Renesas Electronics product(s)" means any product developed or manufactured by or for Renesas Electronics. (Rev.3.0-1 November 2016)

Release Note

R11UT0027EU0100 Rev.1.00 Page 1 of 31 Nov 22, 2017

Renesas Synergy™ Platform

SSP v1.3.2 Release Note Contents

1. Introduction .............................................................................................................................. 4

2. Release information ................................................................................................................. 4

3. Synergy MCU groups supported .............................................................................................. 4

4. Software Tools and Hardware Kits used for SSP Testing ........................................................ 4

5. Version Information for Express Logic, Inc. .............................................................................. 5 5.1 Version Information for Express Logic, Inc. software components ......................................................... 5

6. SSP release package and installation information ................................................................... 5

7. Changes from SSP v1.3.0 to SSP v1.3.2 release .................................................................... 6 7.1 New or updated features ......................................................................................................................... 6 7.1.1 S5D5 MCU support............................................................................................................................... 6 7.1.2 S3A3 MCU support ............................................................................................................................... 6 7.1.3 S3A6 MCU support ............................................................................................................................... 6 7.1.4 Crypto Keygen ...................................................................................................................................... 7 7.1.5 TRNG module ....................................................................................................................................... 7 7.1.6 Hash module ......................................................................................................................................... 7 7.1.7 Cellular Framework ............................................................................................................................... 7 7.1.8 SSI — Support GPT Internal Connection ............................................................................................. 7 7.2 New Improvements.................................................................................................................................. 8 7.2.1 r_rspi ..................................................................................................................................................... 8 7.2.2 r_adc ..................................................................................................................................................... 8 7.2.3 sf_el_ux ................................................................................................................................................ 8 7.2.4 r_sci_spi ................................................................................................................................................ 8 7.2.5 GUIX Driver .......................................................................................................................................... 8 7.2.6 XML Enhancements ............................................................................................................................. 8 7.2.7 sf_el_tx ................................................................................................................................................. 8

8. Summary of bug fixes made since SSP v1.3.0 ........................................................................ 9 8.1 BSP for SSP ............................................................................................................................................ 9 8.2 NetX and NetX Duo ................................................................................................................................. 9 8.3 r_dac8 .................................................................................................................................................... 10 8.4 r_glcd ..................................................................................................................................................... 10 8.5 r_gpt_input_capture............................................................................................................................... 10 8.6 r_lpmv2 .................................................................................................................................................. 10

R11UT0027EU0100 Rev.1.00

Nov 22, 2017

Renesas Synergy™ Platform SSP v1.3.2 Release Note


8.7 r_riic ....................................................................................................................................................... 10 8.8 r_rspi ...................................................................................................................................................... 10 8.9 r_sci_spi ................................................................................................................................................ 11 8.10 r_ssi ....................................................................................................................................................... 11 8.11 sf_cellular .............................................................................................................................................. 11 8.12 sf_ble ..................................................................................................................................................... 12 8.13 sf_console ............................................................................................................................................. 12 8.14 sf_el_gx ................................................................................................................................................. 12 8.15 sf_el_ux ................................................................................................................................................. 12 8.16 sf_power_profiles_v2 ............................................................................................................................ 12 8.17 sf_uart_comms ...................................................................................................................................... 12 8.18 ux ........................................................................................................................................................... 13 8.19 nxd_tls_secure ...................................................................................................................................... 13

9. Known issues and limitations identified after SSP v1.3.0 release........................................... 14 9.1 GUIX integration .................................................................................................................................... 14 9.2 GUIX ...................................................................................................................................................... 14 9.3 NetX and NetX Duo ............................................................................................................................... 15 9.4 r_fmi ....................................................................................................................................................... 15 9.5 r_jpeg_decode ....................................................................................................................................... 15 9.6 r_qspi ..................................................................................................................................................... 15 9.7 r_riic ....................................................................................................................................................... 15 9.8 r_rtc ....................................................................................................................................................... 16 9.9 r_sdmmc ................................................................................................................................................ 16 9.10 r_slcdc ................................................................................................................................................... 16 9.11 sf_audio_playback_hw_dac .................................................................................................................. 17 9.12 sf_cellular .............................................................................................................................................. 17 9.13 sf_el_gx ................................................................................................................................................. 17 9.14 sf_el_tx .................................................................................................................................................. 18 9.15 sf_el_ux ................................................................................................................................................. 18 9.16 sf_thread_monitor.................................................................................................................................. 18 9.17 sf_uart_comms ...................................................................................................................................... 19 9.18 sf_wifi ..................................................................................................................................................... 19 9.19 Synergy Software Configurator ............................................................................................................. 20 9.20 Synergy Tools ........................................................................................................................................ 20 9.21 USBX ..................................................................................................................................................... 20 9.22 BSP for SSP .......................................................................................................................................... 21

10. Additional usage notes for SSP v1.3.2 ................................................................................... 21 10.1 r_sci_i2c ................................................................................................................................................ 21 10.2 r_can ...................................................................................................................................................... 21 10.3 r_rspi ...................................................................................................................................................... 22



10.4 sf_audio_playback ................................................................................................................................. 22 10.5 sf_ble ..................................................................................................................................................... 22 10.6 sf_cellular .............................................................................................................................................. 22 10.7 sf_el_ux ................................................................................................................................................. 23 10.8 sf_i2c ..................................................................................................................................................... 23 10.9 sf_wifi ..................................................................................................................................................... 24 10.10 Tools Development................................................................................................................................ 24 10.11 ux ........................................................................................................................................................... 24

11. Complete list of modules available in this release ................................................................. 25

12. Additional technical notes ...................................................................................................... 30



1. Introduction This document describes the release notes for Synergy Software Package (SSP) version 1.3.2.

2. Release information SSP Release Version v1.3.2

Release Date Nov 22, 2017 Important notices for this release:

The intended audience for this release is Renesas Synergy customers, prospective customers, partners, and support staff.

This release note describes the known issues in SSP v1.3.2 that were identified since the last minor release SSP v1.3.0. For additional known issues, limitations and usage notes in SSP v1.3.2 that were previously reported in SSP v1.3.0, refer to sections 9, 10 and 11 of the SSP v1.3.0 Release Note. This document is available from the Release Archive tab under the Synergy Gallery SSP section.

3. Synergy MCU groups supported S7G2, S5D9, S5D5, S3A7, S3A6, S3A3, S128, and S124 groups.

4. Software Tools and Hardware Kits used for SSP Testing Tool Version Description

e2 studio 5.4.0.023 Software development environment. Link: https://synergygallery.renesas.com/

IAR Embedded Workbench® for Renesas Synergy™

7.71.3 Software development environment. Link: https://synergygallery.renesas.com/

SSC 5.4.0.023 Synergy Standalone Configurator. Used in combination with IAR EW for Synergy. Link: https://synergygallery.renesas.com

GNU Arm Compiler eabi-4_9-2015q3-20150921-win32 GNU Arm® compiler GCC_4.9.3.20150529

IAR Compiler 7.71.1 IAR Arm compiler toolchain

PE-HMI1 2.0 Product Example (PE) for Human Machine Interface to evaluate Renesas Synergy™ S7G2 Group MCU

DK-S124 3.0 Development Kit for Renesas Synergy™ S124 Group MCU

DK-S7G2 3.1 Development Kit for Renesas Synergy™ S7G2 Group MCU

SK-S7G2 3.1 Starter Kit for Renesas Synergy™ S7G2 Group MCU DK-S3A7 2.0 Development Kit for Renesas Synergy™ S3A7 Group MCU PK-S5D9 1.0 Promotion Kit for Renesas Synergy™ S5D9 Group MCU DK-S128 1.1* Development Kit for Renesas Synergy™ S128 Group MCU TB-S3A6 1.0* Kit for Renesas Synergy™ S3A6 Group MCU TB-S5D5 1.0* Kit for Renesas Synergy™ S5D5 Group MCU TB-S3A3 1.0* Kit for Renesas Synergy™ S3A3 Group MCU

J-Link Software 6.16f SEGGER J-Link® debug probe is the quasi standard for Arm® Cortex®-M based MCUs.

Note: * Pre-production versions of these kits were used for SSP testing, results with production kits may vary slightly.

https://synergygallery.renesas.com/





5. Version Information for Express Logic, Inc. 5.1 Version Information for Express Logic, Inc. software components

Component Version ThreadX® 5.7 SP1

NetX™ 5.9 SP2

NetX Duo™ 5.10 SP2

NetX Application bundle 5.9 SP2

NetX Duo Application bundle 5.10 SP2

USBXTM Host 5.8

USBXTM Device 5.8

FileX® 5.5

GUIX™ 5.3.3

TraceX® 5.2.0

GUIX Studio™ 5.3.3.7

NetX Secure 5.10 SP3

NetX Duo MQTT 5.10 SP1

6. SSP release package and installation information This package contains SSP v1.3.2 patch release.

Before installing SSP, ensure that the following items are installed on your PC:

• Renesas e2 studio ISDE v5.4.0.023 (download from Renesas Gallery https://synergygallery.renesas.com/) • GNU Arm Compiler (included in Renesas e2 studio ISDE v5.4.0.023 installer) To install the SSP, follow these steps:

1. Download the following items for the SSP Release from Synergy Gallery: SSP_Distribution_1.3.2.zip (SSP Package Installer, including SSP Package) Renesas Synergy Software Package (SSP) v1.3.2 Release Note

(r11ut0027eu0100-synergy-sspv132-rel-note.pdf) 2. Unzip the package and run the SSP_Distribution_1.3.2.exe installer. 3. Install the SSP in the root folder of a compatible e2 studio installation. Note: The default installation folder for the SSP is C:\Renesas\e2_studio.

SSP documentation is available for download from the Synergy Gallery. Sign in the Synergy Gallery, select the Synergy Software Package section at the top of the page, and then the Documentation or Release Archive tabs to view the Documentation & Support Files available to download.




7. Changes from SSP v1.3.0 to SSP v1.3.2 release 7.1 New or updated features 7.1.1 S5D5 MCU support • Board Support Package (BSP) creation supports TB-S5D5 • Includes support and testing of SSP modules for TB-S5D5 For a Complete list of modules available in this release, see section 11.

Known issues: None Issue ID: 9972

Modules that could not be tested on TB-S5D5:

• r_pdc • sf_touch_ctsu • sf_touch_ctsu_button • sf_touch_ctsu_slider • sf_i2c 7.1.2 S3A3 MCU support

All applicable SSP modules are supported and tested for S3A3.

For a Complete list of modules available in this release, see section 11.

Known issues: None 7.1.3 S3A6 MCU support

Added support for the following modules on S3A6

• lpmv2 • sf_adc_periodic • sf_power_profiles_v2 Known issues: The following SSP modules have not been tested on the S3A6. Issue ID: 9427

• r_ctsu • sf_touch_ctsu • sf_touch_ctsu_slider • sf_touch_ctsu_button • sf_touch_panel_i2c Issue ID: 9479

The USBX host class in SSP v1.3.2 is not functional on the S3A6 because USBX Host classes are not supported on S3A6, with the exception of the USBX Host class, due to the limited RAM size requirement (32 KB). The USBX Host CDC-ACM requires a minimum of 29 KB for the USBX pool memory size, where other USBX Host classes require more than 32 KB.

Workaround: There is no workaround for this issue



7.1.4 Crypto Keygen Added RSA HAL Interface for the following:

• Generating RSA 1024-bit KeyPair in plain text • Generating RSA 2048-bit KeyPair in plain text • Generating RSA 1024-bit KeyPair with wrapped key • Generating RSA 2048-bit KeyPair with wrapped key • Decrypting with wrapped key • Sign • Verify Known issues: None RSA Framework Interface:

• Generating RSA 1024-bit KeyPair in plain text • Generating RSA 2048-bit KeyPair in plain text • Generating RSA 1024-bit KeyPair with wrapped key • Generating RSA 2048-bit KeyPair with wrapped key Known issues: None

Added wrapped key generation support for AES with CBC, CTR, ECB and XTS chaining modes.

• AES keygen 128 bit (ECB, CBC, CTR, and GCTR) • AES keygen 128 bit XTS • AES keygen 192 bit (ECB, CBC, CTR, and GCTR) • AES keygen 256 bit (ECB, CBC, CTR, and GCTR) • AES keygen 256 bit XTS Known issues: None 7.1.5 TRNG module

Added cryptography framework support for true random number generation module.

Known issues: None 7.1.6 Hash module

The sf_crypto_hash framework module provides hash/message digest services through the Secure Cryptographic Engine (SCE) HAL module.

The hash functions supported are SHA-1, SHA-224, and SHA-256.

Known issues: None 7.1.7 Cellular Framework

Synergy Cellular Framework now supports NimbeLink 4G LTE CAT1 Verizon module (NL-SW-LTE-GELS3).

• The framework provides a generic API interface using which applications can configure, provision, and initiate a data connection on a cellular CAT1 module.

• The framework provides a Network Stack Abstraction Layer (NSAL) to help application development using NetX/NetX Duo, on top of Cellular CAT1 module.

• Provides BSD socket API interface to the application to use on-chip networking stack. Known issues: None 7.1.8 SSI — Support GPT Internal Connection

An internal connection to the GPT output GTIOC1A is now supported for r_ssi.

Known issues: None



7.2 New Improvements 7.2.1 r_rspi

All MCUs now support 8, 16, and 32-bit width using r_rspi with and without DTC transfer instances.

Applies to: All supported Synergy MCU Groups 7.2.2 r_adc

The ADC register, ADHVREFCNT is added to the iodefine file. There is no change to ADC HAL features.

Applies to: S124, S128, S3A3, S3A6, S3A7

7.2.3 sf_el_ux When the user buffer is not aligned to 32-bit memory boundary and the USB uses the transfer interface (DMA/DTC), then the host controller driver (HCD) performs a software copy (CPU mode) to transfer USB data during a read operation.

This issue has been resolved in this release and transfer interface is used during a read operation on a word aligned (32 bit) as well as a non-word aligned (8 bit or 16 bit) user buffer.

Applies to: S5D5, S5D9, S7G2 The USB LDO regulator is supported for USBFS controller.

Applies to: S124, S128, S3A3, S3A6, S3A7 7.2.4 r_sci_spi

Slave mode support is now added in the SCI SPI driver; the ISDE configuration has the option to choose either Master or Slave mode. By default, the configuration is set to Master mode.

Applies to: All supported Synergy MCU Groups 7.2.5 GUIX Driver

The sf_el_gx module supports CLUT-8 color format. The CLUT-8 format supports the following:

• Users can expect significant RAM size reduction in their GUIX-based applications. • There are 256 colors available in the format and the colors are set by GUIX Studio in the color palette. Each color

has 24-bit RGB and an alpha channel. • There are two options to render an image: Synergy graphics accelerator (DRW) or software rendering. • Alpha blending is not supported with the CLUT-8 format since the number of colors is limited to 256 and colors

are pre-defined in the color palette. An intermediate color is required for pixel blending, but such a color is not available in color palette. GUIX however can make a pixelmap transparent or opaque against the background color—if software rendering is used—with control available with the alpha channel in each color palette entry.

• Alpha blending with Synergy graphics hardware acceleration is not supported in this release and may cause an unexpected result—to paint pixels in black—if the alpha value of a pixel is not transparent.

Applies to: S7G2, S5D9 7.2.6 XML Enhancements

All return codes from ThreadX during initialization are now checked. On failure tx_startup_err_callback is called. A stub is provided that triggers a breakpoint. Override this by adding a tx_startup_err_callback function to user code.

Applies to: All supported Synergy MCU Groups. 7.2.7 sf_el_tx

Fixed warnings related to duplicate definition of TX_TIMER_TICKS_PER_SECOND when using ThreadX.

Applies to: All supported Synergy MCU Groups.



8. Summary of bug fixes made since SSP v1.3.0 8.1 BSP for SSP Issue ID: 9366

The register bit settings to the CSnWCR2 register (External_bus_CSn_Wait_Control_Register_2) have been corrected and now match their respective hardware manual descriptions.

Applies to: S7G2, S5D9, S5D5, S3A7, S3A3

Issue ID: 10609 This issue has been resolved in this release. In SSP v1.3.0: • At frequencies greater than 80 MHz, the number of inserted ROM wait states are less than that specified by the

hardware manual – 1 instead of 2 wait states. • At frequencies greater than 40 MHz and less than 80 MHz the number of inserted ROM wait states are less than

that specified by the hardware manual – 0 instead of 1 wait states. • At frequencies greater than 60 MHz and less than 120 MHz the number of inserted RAM wait states are less than

that specified by the hardware manual – 0 instead of 1 wait state. • High speed RAM is unaffected.

Applies to: S5D9 and S5D5

8.2 NetX and NetX Duo Issue ID: 9515, Issue ID: 8543

The BSD module in thread stack window now warns about enabling the 'Extended Notify Support' property of NetX Duo source.

Applies to: S7G2, S5D9, S5D5 Issue ID: 9433

The NetX Duo DHCPv6 Server timeout for the server to receive a client response can now be configured from the thread stack configuration window.


The NetX and NetX Duo HTTP client timeout configuration is now functional from the thread stack configuration window.


NetX Duo NAT module in thread stack window now warns the user about the required NetX Duo Source. The module also checks whether NAT support is enabled in the NetX Duo source.


IGMPv2 support is functional for NetX/NetX Duo source.

Applies to: S7G2, S5D9, S5D5



8.3 r_dac8 Issue ID: 9501

The parameter checking option in e2 studio now correctly enables and disables checking for the r_dac8 module.

Applies to: S128, S3A3 Issue ID: 9422

The DAC8 mode option in e2 studio now correctly sets the mode.

Applies to: S128

8.4 r_glcd Issue ID: 8727

Customer boards might not require the Data Enable signal for their graphics LCD panel. For such a hardware configuration, the “Not used” option is given for r_glcd configuration property “TCON - DataEnable.” However, the property was configuring the GLCDC TCON hardware wrong and it resulted in the display image shifting horizontally on the LCD panel. This issue has now been fixed; configuring “Not Used” no longer causes a horizontally-shifted image on LCD.

Applies to: S7G2, S5D9

8.5 r_gpt_input_capture Issue ID: 8060

The r_gpt_input_capture module used to require r_gpt to build. Now, the r_gpt_input_capture module can be used without r_gpt.

Applies to: All supported Synergy MCU Groups

8.6 r_lpmv2 Issue ID: 9393, Issue ID: 9548

The RTC Alarm option in e2 studio now properly configures the RTC alarm.

Applies to: S7G2 and S5D9

8.7 r_riic Issue ID: 8565

In DTC mode, the RIIC was not able to successfully perform a zero-byte data transfer. This data transfer is required when the master needs to send only the address and no data. The current fix supports zero-sized data transfers for both DTC and non-DTC modes


8.8 r_rspi Issue ID: 9526

The transmit-only option has been removed from the integrated system development environment (ISDE). Calls to write configures the module to transmit only. Calls to read or readWrite will configure the module for full duplex.

Applies to: All supported Synergy MCU Groups Issue ID: 9337

A timing issue has been fixed that could have resulted in the r_rspi control block being left in a half open state if closed during mid operation.




8.9 r_sci_spi Issue ID: 9172

When the SPI master performs read operation from the slave on the master in, slave out (MISO) line; the master out, slave in (MOSI) line sends garbage values. According to the SPI standard, the MOSI should be 0xFF (always high). This issue has been fixed by sending 0xFF on the MOSI line during a read only operation (with or without the DTC).


8.10 r_ssi Issue ID: 9312

The r_ssi module no longer transmits or receives 0 data unexpectedly when a writeRead() is called. An error code is returned if read() is called during a write() operation or if write() is called during a read() operation. The SSI must be idle before switching between read and write.


The WS continue mode can now be turned off for SSIE.

Applies to: S3A3, S5D9

8.11 sf_cellular Issue ID: 9583

Removed the SSP_ERROR_LOG statements from sf_cellular_common.c and sf_cellular_common_private.c files which were causing compilation error when BSP_CFG_ERROR_LOG=1.

Applies to: S7G2, S5D9 Issue ID: 9349

Implemented the following BSD socket APIs for NimbeLink CAT3 NL-SW-LTE-TSVG Cellular Framework:

• bind() • listen() • accept() • setsockopt() • getsockopt() Applies to: All supported Synergy MCU Groups Issue ID: 10160

While using the Cellular Framework, an issue related to module initialization caused a failure on the first run of the CAT3 module with ECHO enabled. This issue has been fixed.


Module initialization while using Cellular Framework may fail on first run on an ECHO Enabled CAT1 module. This issue has been fixed.




8.12 sf_ble Issue ID: 9509

Fixed the observed Synergy BLE Framework IAR build issue, with all profiles disabled through ISDE.


8.13 sf_console Issue ID: 9106

Writing to sf_console from other threads is now permitted while waiting for a console input in the prompt() API—if either echo is turned off or the input command string is 0 in length.


8.14 sf_el_gx Issue ID: 9711

Previously, sf_el_gx blended a foreground GUIX widget pixelmap (containing transparent pixels (= zero alpha value)) incorrectly on the background GUIX widget pixelmap and painted the pixels in black if following conditions are met:

1. ARGB8888 color format is used 2. Canvas is not used (the mode GUIX draws directly to the frame buffer) The issue was fixed in this release.


8.15 sf_el_ux Issue ID: 9118

Previously, sf_el_ux hcd (USBX Synergy Host Controller Driver) did not support the USB bus overcurrent interrupt. The interrupt is now supported in this SSP release.

Applies to: S7G2, S5D5, S5D9, S3A7, and S3A6 Issue ID: 8518

When the user buffer is not aligned to 32-bit memory boundary, and the USB uses the transfer interface (DMA/DTC), then the host controller driver (HCD) performs a software copy (CPU mode) of the USB data during a read operation (due to a DMA/DTC failure).

This release fixes the issue; the transfer interface is used during a read operation on a word-aligned (32 bit) and non-word aligned (8 bit or 16 bit) user buffer, without moving to CPU mode.


8.16 sf_power_profiles_v2 Issue ID: 8899

When creating a CGC Configuration Instance in the Synergy Configurator, a divisor of 32 is now available for the following divisors: PCLKA, PCLKB, PCLKC, PCLKD, BCLK, FCLK, and ICLK.


8.17 sf_uart_comms Issue ID: 7669

The read operation on the UART framework is modified to use the UART_EVENT_RX_CHAR callback, rather than the read API of UART driver. As a result, the UART framework does not use the DTC for UART reception, even if the DTC module is selected in the stack. This modification avoids any potential timing issues that could arise when the UART driver uses the DTC in its read API call.




8.18 ux Issue ID: 8648

Previously, the Synergy configurator generated a wrong USB Device Descriptor for the USBX Device HID class—if the configuration property “Interrupt-Out Endpoint (Optional)” was enabled. The issue is now fixed in this release.

This update also includes the addition of a new configuration property, the “USBX Device HID Entry Function” as part of the configuration properties for the USBX Device Class HID component. Users who developed a custom Device HID class to support an Interrupt-Out endpoint can specify the entry function name to the property, so that they can register their custom class to USBX.

Note: USBX Device Class HID does not support an Interrupt-Out endpoint but only supports an Interrupt-In endpoint.

Applies to: All the Synergy MCU groups.

Issue ID: 8397

Previously, the USBX enumeration thread could cause an issue of stack overflow with pre-built UX libraries. Libraries were built with the build-time option UX_THREAD_STACK_SIZE set to 1024 bytes, but the size was not large enough. This issue was avoided this release by building the libraries with the UX_THREAD_STACK_SIZE set to 2048 bytes.

Applies to: All the Synergy MCU groups. Issue ID: 9338

Previously, the USBX Host Class HID module had an issue, the class incorrectly recognized the keyboard character sent from a USB keyboard device. This issue was fixed in this release with the USBX5.8 SP1 integration.

Applies to: All the Synergy MCU group

8.19 nxd_tls_secure Issue ID: 9990

An error occurs in nx_secure_x509_certificate_list_add when restarting a TLS session with renesas.dweet.io. The error occurs when the NetX TLS detects a duplicate certificate in the list, (not with the dweet.io cert itself). This issue is because when trying to re-use a TLS session, all of the certificates that were stored in the previous session are not deleted, and so duplication of certificates occurs. This issue is now fixed in TLS 5.10 SP3

Applies to: S5D9, S7G2 Issue ID: 9916

In the Azure IoT hub, if the TLS client is not configured with local certificate and the TLS server asks for it, and then the TLS exchange fails. This issue is now fixed with TLS 5.10 SP3.

Applies to: S5D9, S7G2 Issue ID: 10161

During the TLS handshake between client and server, the server sends its certificate to the client and the client parses the certificates to check on their validity.

The issue is the first field in the certificate is an OPTIONAL certificate version number (in other words, the type of certificate, 1, 2, or 3). If the version is not present, it is assumed to be 1. The Express Logic stack assumes the certificate version number is always present and this is incorrect. So, a certificate with a version number works, and one without a version number does NOT work. It appears to be very common to have a certificate without an explicit version number, so many will fail. This issue has been reported with server certificate received from MediumOne and OpenSSL.

The above reported issue is now fixed in TLS 5.10 SP3. Applies to: S5D9, S7G2



Issue ID: 10162

The server certificates stored locally are not cleared after the connection between the client and the server. As a result, any attempts to reconnect to the same server results in duplicate certificate error. This issue is fixed with TLS 5.10 SP3.

Applies to: S5D9, S7G2

Issue ID: 10334

The signature of the function nx_secure_x509_certificate_initialize() has been changed between 1.3.0 and 1.3.2 as the following lists. The API now expects one more additional input parameter indicating a private key type.

Note: This is a change in module API and requires a corresponding change in existing applications, based on the SSP v1.3.0 while upgrading to SSP v1.3.2.

Signature in 1.3.0

UINT nx_secure_x509_certificate_initialize(NX_SECURE_X509_CERT *certificate, UCHAR *certificate_data, USHORT length, UCHAR *raw_data_buffer, USHORT buffer_size, const UCHAR *private_key, USHORT priv_len);

Signature in 1.3.2

UINT nx_secure_x509_certificate_initialize (NX_SECURE_X509_CERT *certificate_ptr, const UCHAR *certificate_data, USHORT certificate_data_length, UCHAR *raw_data_buffer, USHORT buffer_size, const UCHAR *private_key_data, USHORT private_key_data_length, UINT private_key_type);

When moving from 1.3.0 to 1.3.2, existing applications need to update their function calls and re compile the application. An example API call in 1.3.2 is listed below:

Example:

/* Initialize our device certificate with the imported certificate data. */ status = nx_secure_x509_certificate_initialize(& https_certificate, device_cert_der,device_cert_der_len,raw_data_buffer,sizeof(raw_data_buffer), device_cert_key_der, device_cert_key_der_len,NX_SECURE_X509_KEY_TYPE_RSA_PKCS1_DER);


Workaround: Update the nx_secure_x509_certificate_initialize() function signature in the application as listed.

9. Known issues and limitations identified after SSP v1.3.0 release 9.1 GUIX integration Issue ID: 9874

The gx_system_timer_stop() returns an error—if the timer ID is set to zero—but the API should accept zero as the timer ID. The expected behavior of the API is to close all the timers associated with the input widget (desired behavior) if zero is specified to the timer ID.


Workaround: Close each timer using the specific timer ID to stop all the widget's timers.

9.2 GUIX Issue ID: 9964

The GUIX v5.3.3 in the button event handling process.

Whenever the user presses a button with auto-repeat, and then moves the finger outside the boundary of the button and releases, the button is locked in auto-repeat state.


Workaround: There is no workaround.



9.3 NetX and NetX Duo Issue ID: 9982

NetX Duo NAT module in thread stack window now warns the user about required value of the “Maximum Physical Interfaces” property.

The minimum value of maximum physical interface property is 2.


Workaround: Set value of 'Maximum Physical Interfaces' property of NetX Duo source module to 2. Issue ID: 9915

The MQTT server closes connection if the first message received by server is PUBLISH or SUBSRIBE and the packet identifier field in the received message is zero.


Workaround: Ensure the MQTT client sets the packet identifier to non-zero value. This can be done by setting the value of nxd_mqtt_client_packet_identifier = 1 in the MQTT client code.

9.4 r_fmi Issue ID: 9688

When creating a custom driver, the SSP_VECTOR_DEFINE* macros causes build errors when used to create vector table entries for COMP_HS, COMP_LS, and LVD (VBATT). SSP does not use these vector table entries.


Workaround: Map the missing definition as a macro to the appropriate enumeration defined in bsp_elc.h.

Example:

#define ELC_EVENT_COMP_HS0_INT ELC_EVENT_COMP_HS_0 SSP_VECTOR_DEFINE_CHAN(hs_comp_isr, COMP_HS, INT, 0);

9.5 r_jpeg_decode Issue ID: 9604

The placeholder for user provided p_context information is not updating in callback function p_context when a JEDI or a JDTI interrupt occurs in the JPEG decode driver. The driver is not passing the p_context to the user in callback function, so the user does not get p_context information in user callback.


Workaround: None

9.6 r_qspi Issue ID: 9809

QSPI operations should be done with valid address range. Invalid address operations do not result in error.


Workaround: Check for valid address range before calling QSPI APIs.

9.7 r_riic Issue ID: 9911

Setting same priority levels for “transmit end” and “transmit and receive” interrupts may result in non-detection of transmit end interrupt.


Workaround: Set higher interrupt priority to transmit end interrupt as compared to transmit and receive interrupts.



Issue ID: 9734

The RIIC HAL driver, when used without a callback, operates in a non-blocking mode.


Workaround: Use callback mode or after write/read API calls, provide sufficient delay for the data transaction depending on data size.

9.8 r_rtc Issue ID: 9892

The RTC driver date validation checks for date >31; months having invalid dates less than 31 are not validated by the driver. For example, invalid dates like 29 and 31 for months Feb and April are not correctly validated.


Workaround: Application has to take care of setting valid dates while initializing the RTC. Issue ID: 9442

When using RTC Open function, it is recommended to check the return value of the API for SSP_SUCCESS before using any other RTC APIs in the application. This is because even in error case RTC p_ctrl->open value is set to OPEN.


Workaround: Check the return values of the RTC open function before using other RTC APIs. Issue ID: 9679

The RTC read value from R_RTC_CalendarTimeGet() API may not be accurate if there is a carry (such as carry over from RSECCNT register to RMINCNT register) while reading time value.


Workaround: Enable the carry interrupt before performing the read. After the read, check if the carry interrupt is triggered, if so read the value again. Repeat until a successful read is performed.

9.9 r_sdmmc Issue ID: 9586

The DMAC Interrupt must be enabled when r_dmac is used as a dependency of r_sdmmc. Not enabling the DMAC Interrupt does not show up as an error in the Synergy Configuration tool.


Workaround: Enable the DMAC Interrupt when using r_dmac as a dependency of r_sdmmc.

9.10 r_slcdc Issue ID: 9538

SLCDC does not work if the clock source is selected as HOCO.

Applies to: S3A7

Workaround: LOCO should be used as clock source for SLCDC.



9.11 sf_audio_playback_hw_dac Issue ID: 9698

The SF_AUDIO_PLAYBACK_HW_DAC_Openreturns successfully instead of invoking an error, even when the transfer driver returns an error.

The document contains incorrect information about the error codes returned from the SF_AUDIO_PLAYBACK_HW_I2S_Play API.


Workaround: None.


The following warning is flagged in the cellular framework file, sf_cellular_cat3.c and sf_cellular_cat1.c, during compilation

warning: missing initializer for field 'api_version_major' of 'struct <anonymous>' [-Wmissing-field-initializers]


Workaround: None Issue ID: 9878

The user code hangs if it tries to transmit data when the cellular interface is not open.


Workaround: The user code needs to make sure the IP link is enabled before any operation is done on the cellular module. In verifying the operation, ensure the module is initialized and it is configured successfully using the Cellular Framework open API, and also ensure the network connection is up.

9.13 sf_el_gx Issue ID: 9880

When the CLUT 8 bpp format is used for a GUIX application, pixelmaps might not be drawn at the exact coordinates where it should be located at the screen. This is due to an incorrect bitmask operation in sf_el_gx 8 bpp draw functions.


Workaround: No workaround available. Issue ID: 9757

The component sf_el_gx allows the user to specify “Display Driver Configuration Inheritance” to “Inherit Graphics Screen 2” (such as foreground); however, the sf_el_gx source always references “DISPLAY_FRAME_LAYER_1” (such as background) when performing buffer toggle operation. This is hard-coded in sf_el_gx_frame_toggle().


Workaround: Projects using GUIX on a foreground should change the “DISPLAY_FRAME_LAYER_1” to “DISPLAY_FRAME_LAYER_2,” which is given as the third argument of the DISPLAY API layerChange() that called in sf_el_gx_frame_toggle().

Note: To apply the work around, users should not edit the original sf_el_gx.c file located at /synergy/src/framework/sf_el_gx/. Instead, copy the file to the /src/ directory and make the change on the copy. The change is because the files under /synergy/ are subject to being overwritten when “Generate Project Content” is clicked or a project is built. Be sure to exclude the original sf_el_gx.c. Right-click the file > Exclude from build > Click Select All > Click OK.



Issue ID: 9566

The D/AVE 2D driver API d2_utility_fbblitcopy() might cause a screen artifact because the driver does not wait for the completion of framebuffer cache flushed. The function is used if a user called GUIX API gx_canvas_block_move().


Workaround: None

9.14 sf_el_tx Issue ID: 9740

Non-standard builds of the ThreadX source (tx_src) module may cause a hard fault exception.


Workaround: Use the standard build configuration for tx_thread_schedule.c when building tx_src.


Current USBX Host HID is not functional when the device are unplugged and then plugged in to host board in between of running USBX Host HID application.


Workaround: In the user application, invoke ThreadX Sleep in all application threads.

Issue ID: 9842

SF_EL_UX HCD would not assert the USB bus reset signal for a duration of at least 50 ms, if the ThreadX tick time is configured to less than 10ms per tick.

Applies to: S7G2, S5D5, S5D9, S3A7, S3A7, S3A6

Workaround: Configure the ThreadX tick time to 10 ms per tick or modify the hardcoded value 5 [tick] given to tx_thread_sleep() in ux_hcd_synergy_port_reset() to have a duration longer than 50 ms.

Issue ID: 9834

The current sf_el_ux hcd does not handle the EoF error interrupt in the interrupt handler, even though the interrupt is enabled. Once the EoF error was detected, the driver becomes stuck in the interrupt handler, since it never clears the interrupt. The EoF error handling routine is not implemented in the driver today, but it is required since the USB hardware disables the USB port if the error is detected.

Applies to: S7G2, S5D5, S5D9, S3A7, S3A3, S3A6

Workaround: None

9.16 sf_thread_monitor Issue ID: 9819

The Thread Monitor application framework uses the watchdog timer (WDT) to reset the device and recover the system if there is any misbehavior in the application threads. Each thread is continuously monitored by the Thread Monitor framework; when detecting an issue with the application thread, WDT invokes and resets the device. If WDT does not initialize before thread creation, it results in blocking the application. A blank console screen displays and stays active.


Workaround:

1. Disable auto-initialisation of the thread monitor. 2. Open the HAL WDT driver using the configuration data from the thread monitor. 3. Unlock the WDT HAL driver. 4. Open the thread monitor.



9.17 sf_uart_comms Issue ID: 9792

The SF_COMMS_LOCK_ALL option is not functional in the sf_uart_comms unlock() API.


Workaround: Call the unlock() API using SF_COMMS_LOCK_TX, and then call unlock() again using SF_COMMS_LOCK_RX.

9.18 sf_wifi Issue ID: 10084

The Synergy WiFi framework's provisioningSet() API fails when the SSID name with length 32 bytes is passed as an argument.


Workaround: Use SSIDs that are less than 32 bytes long. Issue ID: 10012

Project having only SF_WiFi On-Chip stack component fails to compile.


Workaround: • Add directory path “${workspace_loc:/${ProjName}/synergy/ssp/inc/framework/api}” to include paths in project

settings. OR

• Add any other Synergy Framework component to project, such as sf_console. Issue ID: 9919

The Synergy WiFi framework APIs fail if called before successful initialization of WiFi module.


Workaround: Application should wait for WiFi module initialization to complete before calling any Synergy WiFi framework API. Issue ID: 9885

While using the FTP server over the WiFi interface the program does not get user disconnect notifications when the user disconnects from the FTP server.



Projects developed using Synergy WiFi framework does not respond to NetX APIs if the WiFi module is not connected to target platform.


Workaround: Verify that the WiFi module is connected to target platform with required IOPORT pins configured correctly. Issue ID: 9795

Synergy framework console fails to function when using NetX Duo IP instance on the WiFi framework that has auto-initialization of IP instance enabled.




Workaround: Disable auto-initialization of the NetX Duo IP instance and call the instance initialization function from the user code after the console is up. Issue ID: 9100

The NetX POP3 initialization completes before the WiFi module is initialized.

Applies to: All synergy MCUs

Workaround: Application should follow these steps;

1. Auto-initialization for NetX IP Instance should be disabled. 2. IP initialization should be explicitly called and wait for IP link to be up.

See the NetX usage notes section in the WiFi Framework Usage notes. 3. Initialize NetX POP3 Issue ID: 9746

There is an issue in getting the IP address from the DHCP server when the device tries to repeatedly release and acquire the IP address over the WiFi interface. The WiFi framework close() should not be called by the application code if using an IP instance (NSAL).


Workaround: The application should call the nx_ip_delete() which internally calls the WiFi framework close()

9.19 Synergy Software Configurator Issue ID: 9738

If a user imports an existing project exported without the module_descriptions folder in e2 studio v5.4.0, and the older SSP version (SSP v1.2.0 or SSP v1.2.1), then the Synergy Configuration Editor crashes when opening the configuration.xml file, while attempting to upgrade the project. This occurs when the project that was originally created is not installed in e2 studio v5.4.0.


Workaround: Install the older SSP version the project was based; the version used when the project was created in e2 studio v5.40 (such as SSP v1.2.1). Now re-install the latest SSP version (SSP v1.3.2) in e2 studio v5.40. Import the project, now open configuration.xml and generate the project content. Lastly, upgrade the project to the newer SSP version by switching to it on the BSP tab of the Synergy Configuration Editor.

9.20 Synergy Tools Issue ID: 9315

In the e2 studio I/O registers view, the FCACHE registers are located at the wrong address for the S3A7 MCU.

Applies to: S3A7

Workaround: In the Expressions window, enter the following to view the flash cache registers: (R_ROMC_Type *) 0x4001C000

9.21 USBX Issue ID: 9745

USBX Device Class CDC-ACM pre-built library might not complete data reception if data is sent from a Host with exactly 64 bytes (in case of a Full-Speed connection). It needs to wait for the next byte(s) to determine the data transfer is complete.


Workaround: Use the USBX Device Class CDC-ACM Source module instead. The source module does not cause the issue.



9.22 BSP for SSP Issue ID: 8651

When using e2 studio and SSP it is not possible to link the GPT UVW Edge event signal to a peripheral or interrupt. Selecting ELC_EVENT_OPS_UVW_EDGE as an activation source generates a build error.

Applies to: S3A3

Workaround: An application should set the respective ICU event Link Setting register to cause the GPT UVW Edge event to be linked. Issue ID: 8650

A customer would not be able to initiate a DMAC or DTC transfer, or trigger an interrupt based on the SNOOZE CANCEL event.

Selecting the Event ICU SNOOZE CANCEL as an activation source generates a build error.

Applies to: S3A3

Workaround: An application should set the respective ICU event Link Setting register to cause the GPT UVW Edge event to be linked.

10. Additional usage notes for SSP v1.3.2 10.1 r_sci_i2c Issue ID: 9601

For applications with SCI_I2C module requiring high performance when using I2C communication, use the DTC interface for improved performance.



The API slaveAddressSet() of RIIC and SCI_IIC driver can be used to set the device address and addressing mode of the slave without re-configuring the entire bus, which has been configured during the driver open.


Workaround: None

10.2 r_can Issue ID: 9307

1. R_CAN_Read (), R_CAN_InfoGet and R_CAN_Control() return SSP_ERR_NOT_OPEN when passed an unopened control block.

2. Mailbox count must be a multiple of 4 and a max of 32 3. Mailbox mask cannot be larger than 0x1FFFFFFF 4. The CAN frame data_length_code must be in the range 0 through 8 inclusive Applies to: All supported Synergy MCU Groups

Workaround: None



10.3 r_rspi Issue ID: 6068

When using r_rspi in slave mode, either the clock edge must be even, or the master must de-assert the slave select line between API calls. This is a hardware limitation.

Applied to: All supported Synergy MCU Groups

Workaround: None

10.4 sf_audio_playback Issue ID: 9565

The sf_audio_playback cannot be used with r_dac8 as a dependency. The sf_audio_playback only supports 16-bit samples and r_dac8 requires 8-bit samples.

Applies to: S128

Workaround: None

10.5 sf_ble Issue ID: 10007

The BLE GAP Authorization does not work on RL78G1D. This issue is due to the unavailability of the GAP Authorization and GATT profile, and the standard on-board profiles do not work in Authorized mode. The rest of the profile and GAP security modes are not affected.


Workaround: None


Applications using the cellular framework are not be able to upgrade the module firmware due to firmware over-the-air (FOTA) not being supported by the Cellular Framework.



The CAT1 Cellular Framework work only for NimbleLink CAT1 Verizon module with Firmware version B (NL-SW-LTE-GELS3-B). The framework does not work for modules with Firmware Version A (NL-SW-LTE-GELS3) and has not been tested with the NimbeLink firmware for version C (NL-SW-LTE-GELS3-C)



Following features have not been tested with the Cellular framework

1. UDP client 2. UDP Server 3. TCP server Applies to: All supported Synergy MCU Groups

Workaround: None



Issue ID: 9932

On some Cellular networks, it takes longer time to register with the network, which may cause the cellular framework to run out of retries and fail.



Receiving byte loss in the PPP reception. The cellular data receive path may not work for higher data packet sizes (ping with data size ~2048 fails).


Workaround: When using the Cellular Framework, it is recommended to disable the receive DTC transfer interface module under the UART driver.

Issue ID: 9902

A delay of approximately 60 to 70 seconds occurs when establishing a cellular link with Verizon during the network connection.


Workaround: None


In the user application, if the user selects an unsupported USB port (USBHS) for the selected MCU in the Stacks View of XML configurator, the user application generates compilation build errors.


Workaround: Avoid selecting unsupported components in stack view of XML configuration tab for the selected MCU.

10.8 sf_i2c Issue ID: 9603

Framework applications on RIIC module can use the DTC interface for improved performance.



Framework applications on the SCI_I2C module can use DTC interface for improved performance.




10.9 sf_wifi Issue ID: 10076

The Synergy WiFi framework scan() API for GT-202 module can scan maximum 12 SSIDs in a single run and the scan results may contain SSIDs without their name assigned (empty name).



When creating a project using the Synergy WiFi Framework, the ISDE configurator does not show all the configurable properties in the properties window. The ISDE configurator only shows properties that are configurable for the given WiFi module.


Workaround: None

10.10 Tools Development Issue ID: 9596

Users cannot make C++ exception handling work with the libc_nano library (if '--specs==nano-specs' is specified in GCC linker option). The exception ends up in the default handler __gnu_cxx::__verbose_terminate_handler() instead of users' catch(...) handler.


Workaround: Do not use '--specs==nano-specs' option for C++ project. See posts to the GNU Arm Embedded Toolchain community to learn of alternate solutions at https://answers.launchpad.net/gcc-arm-embedded/+question/230716

10.11 ux Issue ID: 10027

USBX Device Class HID does not support Interrupt-Out endpoint. The use of Interrupt Out endpoint is optional in USB HID specification. It is not often used in embedded applications.


Workaround: Contact your Synergy Customer Support representative for a custom HID class example that enables Interrupt-In and Interrupt-Out endpoints.

https://answers.launchpad.net/gcc-arm-embedded/+question/230716

https://answers.launchpad.net/gcc-arm-embedded/+question/230716



11. Complete list of modules available in this release These modules are available for respective MCUs based on the following criteria:

1. If the core functionality of the module has been tested and works on a MCU, even if they have known bugs, then the module is supported on the MCU.

2. If the core functionality is broken or not tested on a MCU then that module is not supported on the MCU. 3. If a Module has been tested on one of the Synergy MCUs, and it is independent of the underlying MCU hardware or

HAL drivers, then the module is supported on all Synergy MCUs on which the underlying driver/framework/stack upon which the module depends on have been completely tested on that MCU.

Module Name SSP Feature Supported Synergy MCU Groups

BSP Board Support Package S124, S128, S3A6, S3A7, S5D5, S5D9, S7G2, S3A3

Driver

r_adc A/D Converter S124, S128, S3A6, S3A7, S5D9, S7G2, S3A3, S5D5

r_agt Asynchronous General Purpose Timer

S124, S128, S3A6, S3A7, S5D5, S5D9, S7G2, S3A3

r_cac Clock Frequency Accuracy Measurement Circuit

S124, S128, S3A6, S3A7, S5D5, S5D9, S7G2, S3A3

r_can Controller Area Network S124, S128, S3A6, S3A7, S5D9, S7G2, S3A3, S5D5

r_cgc Clock Generation Circuit S124, S128, S3A6, S3A7, S5D5, S5D9, S7G2, S3A3

r_crc Cyclic Redundancy Check calculator

S124, S128, S3A6, S3A7, S5D9, S7G2, S3A3, S5D5

r_ctsu Capacitive Touch Sensing Unit S124, S128, S3A7, S7G2, S5D5 r_dac Digital to Analog Converter S124, S3A6, S3A7, S5D9, S7G2, S5D5 r_dac8 8-bit Digital to Analog Converter S128, S3A3 r_dmac Direct Memory Access Controller S3A6, S3A7, S5D5, S5D9, S7G2, S3A3

r_doc Data Operation Circuit S124, S128, S3A6, S3A7, S5D5, S5D9, S7G2, S3A3

r_dtc Data Transfer Controller S124, S128, S3A6, S3A7, S5D5, S5D9, S7G2, S3A3

r_elc Event Link Controller S124, S128, S3A6, S3A7, S5D5, S5D9, S7G2, S3A3

r_flash_hp Flash Memory, High Performance S5D5, S5D9, S7G2

r_flash_lp Flash Memory, Low Power S124, S128, S3A6, S3A7, S3A3

r_fmi Factory Microcontroller Information

S124, S128, S3A6, S3A7, S5D5, S5D9, S7G2, S3A3

r_glcd Graphics LCD Controller S7G2, S5D9

r_gpt General Purpose Timer S124, S128, S3A6, S3A7, S5D5, S5D9, S7G2, S3A3

r_gpt_input_capture General Input Capture S124, S128, S3A6, S3A7, S5D5, S5D9, S7G2, S3A3

r_icu Interrupt Controller Unit S124, S128, S3A6, S3A7, S5D5, S5D9, S7G2, S3A3

r_ioport General Purpose I/O Ports S124, S128, S3A6, S3A7, S5D5, S5D9, S7G2, S3A3

r_iwdt Independent Watchdog Timer S124, S128, S3A6, S3A7, S5D5, S5D9, S7G2, S3A3

r_jpeg_decode JPEG Decode S5D9, S7G2

r_kint Keyboard Interrupt Interface S124, S128, S3A6, S3A7, S5D5, S5D9, S7G2, S3A3



Driver r_lpm† Low Power Mode S124, S3A7, S7G2 r_lpmv2_s124 Low Power Mode V2 for S124 S124 r_lpmv2_s128 Low Power Mode V2 for S128 S128 r_lpmv2_s3a7 Low Power Mode V2 for S3A7 S3A7 r_lpmv2_s5d9 Low Power Mode V2 for S5D9 S5D9 r_lpmv2_s7g2 Low Power Mode V2 for S7G2 S7G2 r_lpmv2_s5d5 Low Power Mode V2 for S5D5 S5D5 r_lpmv2_s3a6 Low Power Mode V2 for S3A6 S3A6 r_lpmv2_s3a3 Low Power Mode V2 for S3A3 S3A3

r_lvd Low Voltage Detection Driver S124, S128, S3A6, S3A7, S5D5, S5D9, S7G2, S3A3

r_pdc Parallel Data Capture Unit S7G2 r_qspi Quad Serial Peripheral Interface S3A7, S5D5, S5D9, S7G2, S3A3

r_riic IIC S124, S128, S3A6, S3A7, S5D5, S5D9, S7G2, S3A3

r_riic_slave IIC Slave S124, S128, S3A6, S3A7, S5D9, S7G2, S3A3, S5D5

r_rspi Serial Peripheral Interface S124, S128, S3A6, S3A7, S5D5, S5D9, S7G2, S3A3

r_rtc Real-time Clock S124, S128, S3A6, S3A7, S5D5, S5D9, S7G2, S3A3

r_sci_i2c Serial Communication Interface I2C S124, S128, S3A6, S3A7, S7G2, S3A3

r_sci_spi Serial Communication Interface SPI

S124, S128, S3A6, S3A7, S5D5, S5D9, S7G2, S3A3

r_sci_uart Serial Communication Interface UART

S124, S128, S3A6, S3A7, S5D5, S5D9, S7G2, S3A3

r_sdmmc SDHI driver for SDIO and SD/MMC memory devices S3A7, S5D9, S7G2, S3A3

r_slcdc Segment LCD Controller S3A6, S3A7, S3A3 Driver

r_ssi (Inter-IC Sound) interface [old: Serial Sound Int.] or r_i2s S3A6, S3A7, S5D9, S7G2, S3A3, S5D5

r_wdt Watchdog Timer S124, S128, S3A6, S3A7, S5D5, S5D9, S7G2, S3A3

Framework

sf_adc_perodic Periodic Sampling ADC S124, S128, S3A7, S5D5, S5D9, S7G2, S3A3, S3A6

sf_audio_playback Audio Playback S124, S3A6, S3A7, S5D9, S7G2, S3A3, S5D5

sf_audio_playback_hw_dac Audio Playback HW DAC S124, S3A6, S3A7, S5D9, S7G2, S3A3, S5D5

sf_audio_playback_hw_i2s Audio Playback HW I2S S3A6, S3A7, S5D9, S7G2, S3A3, S5D5 sf_audio_record Audio Record S3A6, S3A7, S5D5, S5D9, S7G2, S3A3 sf_ble_rl78g1d BLE Framework S3A7, S5D9, S7G2 sf_ble_rl78g1d_onboard_profile BLE Framework onboard profiles S3A7, S5D9, S7G2

sf_block_media_sdmmc Block Media Interface for SD Multi Media Card S3A7, S5D9, S7G2, S3A3

sf_console Console S124, S128, S3A6, S3A7, S5D9, S7G2, S3A3, S5D5

sf_el_fx Synergy FileX Interface S3A7, S5D5, S5D9, S7G2, S3A3



Framework sf_el_gx Synergy GUIX Interface S7G2, S5D9 sf_el_nx Synergy NetX Interface S5D9, S7G2, S5D5

sf_el_nx_comms Synergy NetX Communication Interface S7G2, S5D5

sf_el_ux Synergy USBX Interface S124, S128, S3A7, S5D9, S7G2, S5D5

sf_el_ux_comms† Synergy USBX Communication Interface S3A6, S3A7, S5D9, S7G2, S124, S128

sf_el_ux_comms_v2 Synergy USBX Communication Interface V2

S124, S128, S3A6, S3A7, S5D9, S7G2, S3A3, S5D5

sf_external_irq External Interrupt Framework S124, S128, S3A6, S3A7, S5D5, S5D9, S7G2, S3A3

sf_i2c I2C Framework S3A6, S3A7, S7G2, S3A3, S5D9, S124, S128

sf_jpeg_decode JPEG Decode S5D9, S7G2 sf_message Inter-Thread Messaging S3A7, S5D9, S7G2, S3A3, S5D5 sf_power_profiles† Power Mode Profile S124, S3A7, S7G2

sf_power_profiles_v2 Power Mode Profile V2 S124, S128, S3A7, S5D9, S7G2, S3A3, S5D5, S3A6

sf_spi SPI Framework S124, S128, S3A6, S3A7, S5D5, S5D9, S7G2, S3A3

sf_tes_2d_drw 2D Drawing Engine Framework S5D9, S7G2 sf_thread_monitor Thread Monitor (Watchdog) S3A6, S3A7, S5D5, S5D9, S7G2, S3A3 sf_touch_ctsu Capacitive Touch Sensing Unit S124, S128, S3A7, S7G2

sf_touch_ctsu_button Capacitive Touch Sensing Unit Button S124, S128, S3A7, S7G2

sf_touch_ctsu_slider Capacitive Touch Sensing Unit Slider S124, S128, S3A7, S7G2

sf_touch_panel_i2c Touch Panel I2C S5D9, S7G2

sf_uart_comms UART framework S124, S128, S3A6, S3A7, S5D5, S5D9, S7G2, S3A3

sf_wifi_gt202 Wifi framework S3A7, S5D9, S7G2 sf_wifi_gt202_onchip Wifi framework on chip stack S3A7, S5D9, S7G2 sf_cellular_cat1 Cellular framework cat S3A7, S5D9, S7G2 sf_cellular_cat1_socket Cellular framework cat socket S5D9, S7G2 sf_cellular_cat3 Cellular framework cat S3A7, S5D9, S7G2 sf_cellular_cat3_socket Cellular framework cat socket S3A7, S5D9, S7G2 X-Ware Stacks fx FileX S124, S3A7, S5D9, S7G2, S3A6, S3A3 gx GUIX S5D9, S7G2 nx NetX S7G2, S5D9 nx_auto_ip NetX Auto IP S7G2, S5D9* nx_bsd NetX BSD S7G2, S5D9* nx_dhcp_client NetX DHCP Client S7G2, S5D9* nx_dhcp_server NetX DHCP Server S7G2, S5D9* nx_dns_client NetX DNS Client S7G2, S5D9* nx_ftp_client NetX FTP Client S7G2, S5D9* nx_ftp_server NetX FTP Server S7G2, S5D9* nx_http_client NetX HTTP Client S7G2, S5D9* nx_http_server NetX HTTP Server S7G2, S5D9* nx_pop3 NetX POP3 S7G2, S5D9* nx_ppp NetX PPP S7G2*, S5D9



* NetX and NetX Duo Applications are MCU-independent application layer protocols that depend on the NetX and Ethernet drivers, these protocols are supported on all MCUs on which NetX has been tested and verified.

† Indicates a module that is deprecated starting with SSP v1.3.0 and all subsequent versions. Deprecated

modules will only be available to maintain compatibility with existing projects that may be using them. It is highly recommended that new projects use the recommended replacements and not use deprecated modules. For details, see the SSP User’s Manual.

X-Ware Stacks nx_smtp_client NetX SMTP Client S7G2, S5D9* nx_sntp_client NetX SNTP Client S7G2, S5D9* nx_telnet_client NetX Telnet Client S7G2, S5D9* nx_telnet_server NetX Telnet Server S7G2, S5D9* nx_tftp_client NetX TFTP Client S7G2, S5D9* nx_tftp_server NetX TFTP Server S7G2, S5D9* nxd NetX Duo Stack S7G2, S5D9 nxd_auto_ip NetX Duo Auto IP S7G2, S5D9* nxd_bsd NetX Duo BSD S7G2, S5D9* nxd_dhcp NetX Duo DHCP IPv4 Client S7G2, S5D9* nxd_dhcp NetX Duo DHCP IPv6 Client S7G2, S5D9* nxd_dhcp_server NetX Duo DHCP IPv4 Server S7G2, S5D9* nxd_dhcp_server NetX Duo DHCP IPv6 Server S7G2, S5D9* nxd_dns NetX Duo DNS Client S7G2, S5D9* nxd_ftp_client NetX Duo FTP Client S7G2, S5D9* nxd_ftp_server NetX Duo FTP Server S7G2, S5D9* nxd_http_client NetX Duo HTTP Client S7G2, S5D9* nxd_http_server NetX Duo HTTP Server S7G2, S5D9* nxd_nat NetX Duo NAT S7G2, S5D9* nxd_pop3 NetX Duo POP3 S7G2, S5D9* nxd_ppp NetX Duo PPP S7G2*, S5D9 nxd_smtp_client NetX Duo SMTP Client S7G2, S5D9* nxd_sntp_client NetX Duo SNTP Client S7G2, S5D9* nxd_telnet_client NetX Duo Telnet Client S7G2, S5D9* nxd_telnet_server NetX Duo Telnet Server S7G2, S5D9* nxd_tftp_client NetX Duo TFTP Client S7G2, S5D9* nxd_tftp_server NetX Duo TFTP Server S7G2, S5D9* nxd_mqtt_client NetX Duo MQTT Client S7G2, S5D9 nxd_tls_secure NetX Duo TLS Secure S7G2, S5D9

tx ThreadX S124, S128, S3A6, S3A7, S5D5, S5D9, S7G2, S3A3

ux_device_class_storage USBX Device Class Mass Storage

S124, S128, S3A6, S3A7, S5D9, S7G2, S3A3

ux_device_class_hid USBX Device Class HID S124, S128, S3A6, S3A7, S5D9, S7G2, S3A3

ux_device_class_cdc_acm USBX Device Class CDC-ACM S124, S128, S3A6, S3A7, S5D9, S7G2, S3A3

ux_host_class_cdc_acm USBX Host Class CDC-ACM S5D9, S7G2, S3A6, S3A7, S3A3 ux_host_class_hid USBX Host Class HID S5D9, S7G2, S3A6, S3A7, S3A3 ux_host_class_hub USBX Host HUB S5D9, S7G2 ux_host_class_storage USBX Host Class Mass Storage S5D9, S7G2, S3A6, S3A7, S3A3



Experimental modules: Modules that are dependent on a SSP HAL driver module which has been tested and supported on a particular MCU, but the module in itself has not been tested on the MCU, have been identified as experimental module in the following table. These experimental modules are currently not supported by Synergy Configuration tools and use of these modules in customer projects is not supported by Renesas at this time.

Experimental Modules ux_device_class_cdc_ecm USBX Device Class CDC-ECM S124, S3A7, S5D9, S7G2, S3A3 ux_host_class_gser USBX Host Class Generic Serial S3A7, S5D9, S7G2, S3A3 ux_host_class_printer USBX Host Class Printer S3A7, S5D9, S7G2, S3A3 ux_host_class_prolific USBX Host Class Prolific S3A7, S5D9, S7G2, S3A3 ux_host_class_swar USBX Host Class Swar S3A7, S5D9, S7G2, S3A3 ux network driver USBX Network Driver S124, S3A7, S5D9,S7G2, S3A3

Different cryptographic functions are available for different target MCUs; the following table shows the functionality that is available for each individual MCU-series:

Function S7G2, S5D9, S5D5 S3A3, S3A7, S3A6 S124, S128 TRNG Generate and read random

number Generate and read random number

Generate and read random number

AES Encryption, decryption Encryption, decryption Encryption, decryption AES Key Size 128-bit, 192-bit, 256-bit 128-bit, 256-bit 128-bit, 256-bit AES Key Type Plain text / raw key,

Wrapped key Plain text / raw key, Wrapped key

Plain text / raw key

AES Chaining Modes ECB, CBC, CTR, GCM, XTS ECB, CBC, CTR, GCM, XTS

ECB, CBC, CTR

ARC4 Encryption, decryption NA NA TDES Encryption, decryption NA NA TDES Key Size 192-bit NA NA TDES Chaining Modes ECB, CBC, CTR NA NA RSA Signature Generation,

Signature Verification, Public-key Encryption, Private-key Decryption

NA NA

RSA Key Size 1024-bit, 2048-bit NA NA RSA Key Type Plain text / raw key,

Wrapped key NA NA

DSA Signature Generation, Signature Verification

NA NA

DSA Key Size (1024, 128)-bit, (2048, 224)-bit, (2048, 256)-bit

NA NA

HASH SHA1, SHA224, SHA256 NA NA



12. Additional technical notes • All SSP modules are tested using the default configuration settings in the e2 studio and IAR compiler, operation of

the modules with other configurations are not guaranteed. • Subscribe to the Synergy Technical Bulletin Board to receive the latest technical news and notifications about new

features, known issues, workarounds, and release announcements. To subscribe, visit http://renesasrulz.com/synergy/synergy_tech_notes/f/214.aspx. Sign in to Renesas Rulz, and press ‘Email Subscribe to this forum’.

• Additional technical information, including informative papers and articles on SSP and Synergy can be found at Synergy Knowledge Base, https://en-us.knowledgebase.renesas.com/English_Content/Renesas_Synergy%E2%84%A2_Platform

http://renesasrulz.com/synergy/synergy_tech_notes/f/214.aspx

https://en-us.knowledgebase.renesas.com/English_Content/Renesas_Synergy%E2%84%A2_Platform

https://en-us.knowledgebase.renesas.com/English_Content/Renesas_Synergy%E2%84%A2_Platform



Website and Support Support: https://synergygallery.renesas.com/support

Technical Contact Details:

• America: https://www.renesas.com/en-us/support/contact.html • Europe: https://www.renesas.com/en-eu/support/contact.html • Japan: https://www.renesas.com/ja-jp/support/contact.html All trademarks and registered trademarks are the property of their respective owners.

https://synergygallery.renesas.com/support

https://www.renesas.com/en-us/support/contact.html

https://www.renesas.com/en-eu/support/contact.html

https://www.renesas.com/ja-jp/support/contact.html

Revision History

Rev. Date Description Page Summary

1.00 Nov 22, 2017 — Initial release

SSP v1.3.2 Release Note Publication Date: Rev.1.00 Nov 20, 2017 Published by: Renesas Electronics Corporation

http://www.renesas.comRefer to "http://www.renesas.com/" for the latest and detailed information.

Renesas Electronics America Inc.2801 Scott Boulevard Santa Clara, CA 95050-2549, U.S.A.Tel: +1-408-588-6000, Fax: +1-408-588-6130Renesas Electronics Canada Limited9251 Yonge Street, Suite 8309 Richmond Hill, Ontario Canada L4C 9T3Tel: +1-905-237-2004Renesas Electronics Europe LimitedDukes Meadow, Millboard Road, Bourne End, Buckinghamshire, SL8 5FH, U.KTel: +44-1628-585-100, Fax: +44-1628-585-900Renesas Electronics Europe GmbHArcadiastrasse 10, 40472 Düsseldorf, GermanyTel: +49-211-6503-0, Fax: +49-211-6503-1327Renesas Electronics (China) Co., Ltd.Room 1709, Quantum Plaza, No.27 ZhiChunLu Haidian District, Beijing 100191, P.R.ChinaTel: +86-10-8235-1155, Fax: +86-10-8235-7679Renesas Electronics (Shanghai) Co., Ltd.Unit 301, Tower A, Central Towers, 555 Langao Road, Putuo District, Shanghai, P. R. China 200333Tel: +86-21-2226-0888, Fax: +86-21-2226-0999Renesas Electronics Hong Kong LimitedUnit 1601-1611, 16/F., Tower 2, Grand Century Place, 193 Prince Edward Road West, Mongkok, Kowloon, Hong KongTel: +852-2265-6688, Fax: +852 2886-9022Renesas Electronics Taiwan Co., Ltd.13F, No. 363, Fu Shing North Road, Taipei 10543, TaiwanTel: +886-2-8175-9600, Fax: +886 2-8175-9670Renesas Electronics Singapore Pte. Ltd.80 Bendemeer Road, Unit #06-02 Hyflux Innovation Centre, Singapore 339949Tel: +65-6213-0200, Fax: +65-6213-0300Renesas Electronics Malaysia Sdn.Bhd.Unit 1207, Block B, Menara Amcorp, Amcorp Trade Centre, No. 18, Jln Persiaran Barat, 46050 Petaling Jaya, Selangor Darul Ehsan, MalaysiaTel: +60-3-7955-9390, Fax: +60-3-7955-9510Renesas Electronics India Pvt. Ltd.No.777C, 100 Feet Road, HAL II Stage, Indiranagar, Bangalore, IndiaTel: +91-80-67208700, Fax: +91-80-67208777Renesas Electronics Korea Co., Ltd.12F., 234 Teheran-ro, Gangnam-Gu, Seoul, 135-080, KoreaTel: +82-2-558-3737, Fax: +82-2-558-5141

SALES OFFICES

© 2017 Renesas Electronics Corporation. All rights reserved.Colophon 4.1


R11UT0027EU0100

SSP v1.3.2 Release Note - synergygallery.renesas.com · SSP v1.3.2 Release Note ... 3. No license,...

Documents

Transcript of SSP v1.3.2 Release Note - synergygallery.renesas.com · SSP v1.3.2 Release Note ... 3. No license,...