User’s Manual Release Notecaxapa.ru/thumbs/757844/r11ut0004eu0111-synergy-ssp-120... · 2020. 2. 17. · Rev.1.11 Mar 2017 Renesas Synergy™ Platform Synergy Software SSP v1.2.0

Rev.1.11 Mar 2017

Renesas Synergy™ Platform Synergy Software SSP v1.2.0

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).

Renesas Synergy Software Package (SSP) v1.2.0

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

R11UT0004EU0111 Rev.1.11 Page 3 of 78 Mar 14, 2017

Renesas Synergy™ Platform

Renesas Synergy Software Package (SSP) v1.2.0 1. Introduction This document contains the release notes for SSP version 1.2.0.

2. Release Information SSP Release Version v1.2.0 Release date Mar 13, 2017

3. Synergy MCUs Supported MCUs from the S7G2, S3A7, S124, and S5D9 Groups.

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

5.3.1 Software development environment.

Link: https://synergygallery.renesas.com/

IAR EW for Synergy

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

SSC 5.3.1 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 Synergy S7G2 Group MCU DK-S124 3.0 Development Kit for Synergy S124 Group MCU DK-S7G2 3.1 Development Kit for Synergy S7G2 Group MCU SK-S7G2 3.1 Starter Kit for Synergy S7G2 Group MCU DK-S3A7 2.0 Development Kit for Synergy S3A7 Group MCU PK-S5D9 1.0 Promotional Kit for Synergy S5D9 Group MCU J-Link Software 6.10n Segger J-Link™ debugging probe

5. Version Information for Express Logic, Inc software components Component Version ThreadX® 5.7 NetXTM 5.9 NetX Duo™ 5.10 SP1 NetX Application bundle 5.9 SP2 NetX Duo Application bundle 5.10 SP1 USBXTM Host 5.7 SP7 USBXTM Device 5.7 SP4 FileX® 5.4 SP2 GUIX™ 5.3.2 TraceX® 5.2.0 GUIX™ Studio 5.3.2.2

R11UT0004EU0111 Rev.1.11

Mar 14, 2017

https://synergygallery.renesas.com/



Renesas Synergy™ Platform Renesas Synergy Software Package (SSP) v1.2.0


NetX™ Protocol Support status in this version

Component Supported Configurator Support

NetX Auto IP (nx_auto_ip) Yes Yes

NetX BSD (nx_bsd) Yes Yes

NetX DHCP Client (nx_dhcp) Yes Yes

NetX DHCP Server (nx_dhcp_server) Yes Yes

NetX DNS Client (nx_dns) Yes Yes

NetX FTP Client (nx_ftp_client) Yes Yes

NetX FTP Server (nx_ftp_server) Yes Yes

NetX HTTP Client (nx_http_client) + NetX MD5 (nx_md5) Yes Yes

NetX HTTP Server (nx_http_server) + NetX MD5 (nx_md5) Yes Yes

NetX POP3 (nx_pop3) Yes Yes

NetX PPP (nx_ppp) No No

NetX SMTP Client (nx_smtp_client) Yes Yes

NetX SNTP Client (nx_sntp_client) Yes Yes

NetX Telnet Client (nx_telnet_client) Yes Yes

NetX Telnet Server (nx_telnet_server) Yes Yes

NetX TFTP Client (nx_tftp_client) Yes Yes

NetX TFTP Server (nx_tftp_server) Yes Yes



NetX Duo™ Protocol Support status in this version


NetX Duo Auto IP (nxd_auto_ip) Yes Yes

NetX Duo BSD (nxd_bsd) Yes Yes

NetX Duo DHCP IPv4 Client (nxd_dhcp) Yes Yes

NetX Duo DHCP IPv6 Client (nxd_dhcp) Yes Yes

NetX Duo DHCP IPv4 Server (nxd_dhcp_server) Yes Yes

NetX Duo DHCP IPv6 Server (nxd_dhcp_server) Yes Yes

NetX Duo DNS Client (nxd_dns) Yes Yes

NetX Duo FTP Client (nxd_ftp_client) Yes Yes

NetX Duo FTP Server (nxd_ftp_server) Yes Yes

NetX Duo HTTP Client (nxd_http_client) + NetX MD5 (nx_md5) Yes Yes

NetX Duo HTTP Server (nxd_http_server) + NetX MD5 (nx_md5) Yes Yes

NetX Duo NAT (nxd_nat) Yes Yes

NetX Duo POP3 (nxd_pop3) Yes Yes

NetX Duo PPP (nxd_ppp) No No

NetX Duo SMTP Client (nxd_smtp_client) Yes Yes

NetX Duo SNTP Client (nxd_sntp_client) Yes Yes

NetX Duo Telnet Client (nxd_telnet_client) Yes Yes

NetX Duo Telnet Server (nxd_telnet_server) Yes Yes

NetX Duo TFTP Client (nxd_tftp_client) Yes Yes

NetX Duo TFTP Server (nxd_tftp_server) Yes Yes



USBX™ Class Support status in this version


USBX Host Class Mass Storage (ux_host_class_storage) Yes Yes

USBX Host Class HID (ux_host_class_hid) Yes Yes

USBX Host Class CDC-ACM (ux_host_class_cdc_acm) Yes Yes

USBX Host HUB (ux_host_class_hub) Yes Yes

USBX Device Class Mass Storage (ux_device_class_storage) Yes Yes

USBX Device Class HID (ux_device_class_hid) Yes Yes

USBX Device Class CDC-ACM (ux_device_class_cdc_acm) Yes Yes

USBX Host Class Audio (ux_host_class_audio) No No

USBX Host Class Generic Serial (ux_host_class_gser) No No

USBX Host Class Printer (ux_host_class_printer) No No

USBX Host Class Prolific (ux_host_class_prolific) No No

USBX Host Class Swar (ux_host_class_swar) No No

USBX Device Class CDC-ECM (ux_device_class_cdc_ecm) No No

USBX Device Class RNDIS (ux_device_class_rndis) No No

USBX Network Driver (ux_network_driver) No No Note: The USB classes listed above as not supported are currently in development. Although these USB

classes are included in this SSP distribution release, they have not yet been completely tested or qualified. Renesas will not support these USB classes until they have completed development and their qualification is complete in a future SSP release. It is not given that all non-supported USB classes in the table above will become supported classes in future SSP releases.

IMPORTANT NOTICE: USBX Port driver (SF_EL_UX) in this SSP version does not support USB Isochronous Transfers. Any USB Class which requires Isochronous Transfer, such as USBX Host Class Audio, will not function.

6. Information for upgrading existing SSP projects to SSP v1.2.0 IMPORTANT NOTICES:

• SSP project upgrade in e2 studio environment is only supported from SSP v1.1.0 to SSP v1.2.0. Upgrade from SSP v1.0.0 to SSP v1.2.0 is not supported.

• The pre-built library for USBX Host Mass Storage class v5.7 in SSP versions v1.1.(z) cannot be used with FileX v5.4 pre-built library or the source code provided with SSP v1.2.0 due to the interaction between USBX Host MSC and FileX. Additional information can be found in the ‘Run-time Errors’ section of the Upgrade Guide.

• GUIX Studio auto-generated code must be regenerated from GUIX Studio v5.3.2.2 due to newer versions of GUIX/GUIX Studio. To upgrade your GUIX Studio project developed with GUIX Studio v5.3.0.1, follow the steps described in the ‘Run-time Errors’ section of the Upgrade Guide.

• X-Ware related components have been relocated to the X-Ware category in the graphical view in the Synergy Configurator. Configurability has been improved.

• For additional information on these topics see the Upgrade Guide: Upgrading Projects to SSP v1.2.0 Application Note on our website.



7. SSP release package and installation information Before installing the SSP, ensure that the following items are installed on your PC:

• Renesas e2 studio ISDE v5.3.1 (download from Renesas Gallery https://synergygallery.renesas.com/) • GNU ARM Compiler (included in Renesas e2 studio ISDE v5.3.1 installer)

To install the SSP, follow these steps:

1. Download the following items for the SSP Release from Synergy Gallery:

• SSP_Distribution_1.2.0.zip (SSP Package Installer, including SSP Package, SSP User’s Manual and readme_SSP.txt)

• SSP v1.2.0 Release Note document in HTML format

2. Unzip the package and run the SSP_Distribution_1.2.0.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.

The SSP documentation installs by default to ~Renesas\Synergy\SSP_Documentation. You can change the default location during the installation. The following documents will be installed:

• ssp-user-manual-html-v1.00-sspv1.2.0.zip (HTML version of the SSP User’s Manual) • readme_SSP.txt (critical information and last-minute updates).

8. New features and functions for SSP v1.2.0 compared to SSP v1.1.3 New features

8.1.1 BSP (Board Support Package) Description

BSP and peripheral support has been added for the PK-S5D9 kits.

Applies to: PK-S5D9 kits

8.1.2 C++ support Description

SSP modules will now support C++ application environment. SSP modules can be configured and used in a C++ language environment supported by the e2 studio tool. Both GCC and IAR compilers can be used for C++ support.

Following are the configurations and other technical details for C++ support.

• ISDE e2 studio v5.2.1 and later will support “Synergy C Project” and “Synergy C++ project”. Synergy C++ projects will have all the tool chain support required for C++ applications.

• For GCC compiler, the default C++ programming language standard supported by the tool is ISO 2011 C++ (-std=c++11)

• For IAR compiler, the default C++ programing language standard by the tool is ISO/IEC 14882:2003 (C++).

Refer to the SSP C++ Usage Guide in SSP User’s Manual for more usage details, this document is available on our website.

Applies to: All supported Synergy MCU Groups.

8.1.3 fx (FileX) Description

FileX is upgraded to version 5.4, which includes a new Fault Tolerance feature. Existing user applications will not be impacted by this upgrade. However, note the important information provided in section, Applications with GUIX, in this Release Note.





8.1.4 fx_src (FileX Source) Description

FileX is upgraded to version 5.4, which includes a new Fault Tolerance feature. Existing user applications will not be impacted by this upgrade. However, note the important information provided in section, Applications with GUIX, in this Release Note.


8.1.5 gx (GUIX) Description

GUIX is upgraded to version 5.3.2 (v5.3 Service Pack 2) and GUIX Studio version 5.3.2.2, which include a new feature, 8-bit CLUT format support. Existing user applications are not impacted by this upgrade. However, note the important information provided in section, Configuration Support for X-Ware™, in this Release Note.

Applies to: S7G2, and S5D9 MCU Groups.

8.1.6 gx_src (GUIX Source) Description

GUIX is upgraded to version 5.3.2 (v5.3 Service Pack 2) and GUIX Studio version 5.3.2.2, which include a new feature - 8-bit CLUT format support. Existing user applications are not impacted by this upgrade. However, note the important information provided in section, Applications with GUIX, in this Release Note.

Applies to: S7G2, and S5D9 MCU Groups.

8.1.7 NetX and NetX Applications Bundle Configuration Support Description

New configurators have been added for NetX and NetX Applications Bundle. Previously, all NetX and NetX applications modules were required to be added and configured using a component window, but now can be done using the configurator. This improvement does the following:

• Allows users to add NetX modules using the thread stack window • Auto-resolves all dependencies by bringing in required modules • Allows users to specify and configure all run time and compile time options using a configuration window • Allows users to share the modules that can be shared • Allows users to choose different options available for an interface • Creates an instance of all required low-level modules and creates an instance of a top-level module with user-

specified parameters by generating the appropriate C code.



This is applicable to:

• nx (NetX) • nx_auto_ip (NetX Auto IP) • nx_bsd (NetX BSD) • nx_dhcp (NetX DHCP Client) • nx_dhcp_server (NetX DHCP Server) • nx_dns (NetX DNS) • nx_ftp_client (NetX FTP Client) • nx_ftp_server (NetX FTP Server) • nx_http_client (NetX HTTP Client) • nx_http_server (NetX HTTP Server) • nx_pop3 (NetX POP3) • nx_smtp (NetX SMTP) • nx_sntp (NetX SNTP) • nx_src (NetX Source) • nx_telnet_client (NetX Telnet Client) • nx_telnet_server (NetX Telnet Server) • nx_tftp_client (NetX TFTP Client) • nx_tftp_server (NetX TFTP Server)


8.1.8 r_ctsu (Capacitive Touch Sensing Unit) Description

Capacitive Touch Workbench is updated to read MCU information directly from the project configuration instead of manual entry.

Applies to: S3A7, S124, S7G2 MCU Groups.

8.1.9 r_flash_hp (Flash Memory, High Performance) Description

Implemented Infoget() API function for the flash HP driver, which returns information about the underlying high-performance flash memory. This information includes the number of flash regions, minimum erase and write sizes for both code and data flash memory.

Applies to: S7G2 and S5D9 MCU Groups.

8.1.10 r_flash_lp (Flash Memory, Low Power) Description

Implemented Infoget() API function for the flash LP driver, which returns information about the underlying low-power flash memory. This information includes the number of flash regions, minimum erase and write sizes for both code and data flash memory.

Applies to: S3A7 and S124 Groups.

8.1.11 r_qspi (Quad Serial Peripheral Interface) Description

New API added to provide different erase sizes as well as information about the underlying flash APIs



• Added new API R_QSPI_Erase to r_qspi driver, which erases a block of memory depending on the input argument byte_count passed to the API (Typical byte_count value-4096,32768)

• Added new API R_QSPI_InfoGet to r_qspi driver, which provides information about the underlying flash such as supported erase sizes, size of flash, flash program size, and so forth.

Applies to: S7G2 and S3A7 MCU Groups.

8.1.12 r_riic (IIC) Description

Added DTC transfer support for SCI I2C. Addition of this feature provides the user with the ability to use DTC to transfer data from receive buffer to user memory, and from user memory to transfer memory without using CPU cycles.

Applies to: All MCU Groups.

Description

Added DTC transfer support for RIIC. Addition of this feature provides the user with the ability to use DTC to transfer data from receive buffer to user memory, and from user memory to transfer memory without loading the CPU for data transfer operations.


8.1.13 r_riic_slave (IIC) Description

Added I2C Slave support to the MCU so that a Synergy kit can communicate with other devices as a I2C slaves.


8.1.14 r_rspi (Serial Peripheral Interface) Description

Added SPI slave support to the MCU so that the Synergy kit can communicate with other devices as a I2C slave.


8.1.15 r_sce (Secure Crypto Engine) Issue ID: 6009

Description

RNG and AES cryptographic modules are now supported on the S124 Group MCU devices.

Applies to: S124 MCU Group

Issue ID: 6348

Description

Adds ability to use r_sce module from Synergy C++ projects.

Applies to: S7G2, S3A7, S5D9 and S124 MCU Groups.

Issue ID: 5698

Description

Added support for crypto libraries for the S5D9 Group MCU devices.



Applies to: S5D9 MCU Groups

8.1.16 r_sci_i2c (Serial Communication Interface I2C) Description

Added bit-rate modulation function on all SCI modules to improve the accuracy of the baud-rate generation. Using the bit-rate modulation function, the bit rate can be evenly corrected using the number specified in the MDDR register. This helps to reduce the % error on baud rates in data communications.

Note: This function is more beneficial for circuit boards having odd frequency crystals and for lower baud-rate communications.


8.1.17 r_sci_spi (Serial Communication Interface SPI) Description

Added bit-rate modulation function on all SCI modules to improve the accuracy of the baud-rate generation. Using the bit-rate modulation function, the bit rate can be evenly corrected using the number specified in the MDDR register. This helps to reduce % error on baud rates in data communications.

Note: This function is more beneficial for circuit boards with odd frequency crystals and for lower baud-rate communications.


8.1.18 r_sci_uart (Serial Communication Interface UART) Description

Added bit-rate modulation function on all SCI modules to improve the accuracy of the baud-rate generation. Using the bit-rate modulation function, the bit rate can be evenly corrected using the number specified in the MDDR register. This will help to reduce % error on baud rates in data communications.

Note: This function is more beneficial for circuit boards with odd frequency crystals and for lower baud-rate communications.


8.1.19 r_ssi ((Inter IC Sound) interface [old: Serial Sound Int.] or r_i2s) Description

The SSI driver supports the new SSI v2 (SSIE) hardware in S5D9 Group MCU devices.

Applies to: S5D9 MCU Groups.

8.1.20 sf_audio_record_adc (Audio Record) Description

Added new audio recording ADC framework. Using this framework, the user can record audio from an analog device and get the digital recorded data into the buffer configured by user.

Applies to: S7G2 MCU groups.

8.1.21 sf_el_nx (Synergy NetX Interface) Description

Added callback support to configure the MAC address to the network interface at run time. To use this feature, follow the steps below:



• Define the user callback function void (*p_callback)(nx_mac_address_t *) to return the Ethernet MAC address through the argument

• Set the name of your callback function to the Callback property in the NetX Port ETHER on sf_el_nx component properties in the Synergy Configuration tool.

Note: Note that there is a known issue relevant to this feature. For more information Refer to the section on ‘Known

Issues and Limitations' of this document.

Applies to: S7G2, S5D9 MCU Groups

8.1.22 sf_el_ux (Synergy USBX Interface) Description

Added the feature to force the USB-HS hardware to run in USB Host, FS mode. To enable the feature, set Enable High Speed configuration in the USBX Port HCD on sf_el_ux for USBHS component to Disable.

Applies to: S7G2 MCU Groups

Description

The category of Synergy USBX Interface (USBX Port HS and FS on sf_el_ux) component on the Stacks view in Threads tab on Synergy Configurator was moved from Framework > USB to X-ware > USBX > Device>Synergy Port or Framework > USB to X-ware > USBX > Host > Synergy Port. All the X-Ware related components will be organized/placed/located at in this location in all future SSP releases. In addition, be aware of the component being split into 4 components in this release.

• USBX Port DCD on sf_el_ux for USBFS (USBX Device Controller Driver for USBFS hardware) • USBX Port DCD on sf_el_ux for USBHS (USBX Device Controller Driver for USBHS hardware) • USBX Port HCD on sf_el_ux for USBFS (USBX Host Controller Driver for USBFS hardware) • USBX Port HCD on sf_el_ux for USBHS (USBX Host Controller Driver for USBHS hardware)

Applies to: S7G2, S3A7 and S124 MCU Groups

8.1.23 USBX Configuration Support Description

USBX Host and Device Class stacks are now configurable through Synergy Configurator. By this feature addition, USBX Host/Device Mass Storage Class, HID Class, and CDC-ACM Class stack configuration are supported and stack initialization is taken care of in the auto-generated code. For more details, see the SSP Usage Notes at on our website.



Applies to:

• ux_host_class_cdc_acm (USBX Host CDC-ACM) • ux_host_class_cdc_acm_src (USBX Host CDC-ACM Source) • ux_host_class_hid (USBX Host HID Class) • ux_host_class_hid_src (USBX Host HID Class Source) • ux_host_class_storage (USBX Host Mass Storage Class) • ux_host_class_storage_src (USBX Host Mass Storage Class Source) • ux_host_class_hub (USBX Host HUB Class) • ux_host_class_hub_src (USBX Host HUB Class Source) • ux_device_class_cdc_acm (USBX Device CDC-ACM) • ux_device_class_cdc_acm_src (USBX Device CDC-ACM Source) • ux_device_class_hid (USBX Device HID Class) • ux_device_class_hid_src (USBX Device HID Class Source) • ux_device_class_storage (USBX Device Mass Storage Class) • ux_device_class_storage_src (USBX Device Mass Storage Class Source) • ux (USBX) • ux_src (USBX Source).

Note: ux_device_class_cdc_acm and ux(USBX) have been supported in the Synergy Configurator in SSP v1.1.(z), but those are marked as DEPRECATED in this version, which means that they are not recommended for new development.

Applies to: S7G2, S5D9, S3A7 and S124 MCU Groups.

8.1.24 NetX Duo and NetX Duo Application Bundle Description

NetX Duo and NetX Duo Application bundle modules are upgraded to 5.10 SP1 to optimize the internal logic.

Updated Features for SSP v1.2.0 8.2.1 Common update to all modules Description

The following architecture updates were made to all modules to improve portability between MCUs:

• A new API, productFeatureGet, has been added to the FMI to query the factory flash for MCU specific features and capabilities. All SSP modules now use this API to query the capabilities and features available in the MCU.

• The vector table and an associated vector information array are now built at link time from SSP_VECTOR_DEFINE macros instead of being a fixed list of pre-named vectors. This is handled by the Synergy Configuration tool when interrupts are enabled.

• Interrupt priorities are passed into each module during open() instead of being set once during initialization. • Weak links to internal callbacks defined in the SSP generated code are no longer provided. If a user callback is used,

it must be defined in the application code, or a linker error occurs. • The functions R_BSP_HardwareLock and R_BSP_HardwareUnlock now take ssp_feature_t as an argument

instead of the bsp_hw_lock_t enumerated list • All control structures (<interface>_ctrl_t) have been moved from the interface header files

(ssp/inc/api/<interface>_api.h) to the instance header file (ssp/inc/instances/<instance>.h). This change is transparent in code generated by the e2 studio Synergy Configuration tool. If a control structure is allocated in application code outside the Synergy Configuration tool, the typedef name used in the declaration must be changed from <interface>_ctrl_t to <instance>_instance_ctrl_t.

• A new API, eventInfoGet, has been added to the FMI to get the ELC event (elc_event_t) and IRQ number (IRQn_Type) for a given feature and signal.




Description

Module initialization code for shared or common modules used by multiple threads is run from the first thread to execute instead of being run before the RTOS has started.


Description

Added the feature in all framework XMLs to incorporate the following improvements:

1. To catch the failures in the initialization function in the generated code. 2. Creation of weak function in the generated code, which can be overridden by the user in the application in a user

defined function, if required. 3. Whenever the initialization function fails in the generated code, it calls the user defined function, if it is defined in

the application. If these steps are not followed, weak function is called which has a break point macro BSP_CFG_HANDLE_UNRECOVERABLE_ERROR(0).


Description

All non-SSP externals drivers that go along with the SSP are now moved to a new directory structure under renesas_sybd directory. Contents under renesas_sybd are in non-encrypted format, and the user can update existing drivers or add new custom drivers to this folder. This folder is visible only if your project contains any module using an external driver, for example, the touch i2c framework.

See the SSP User’s Manual to learn how to add custom drivers to the framework.


8.2.2 bsp (Board Support Package) Description

When ThreadX is added to a project, BSP_CFG_RTOS (in bsp_cfg.h) is now automatically set, no longer requiring you to do so.

Applies to: SK-S7G2 and DK-S3A7 Kits. S7G2 and S124 MCU Groups.

8.2.3 NetX (HTTP, DNS, DHCP, FTP, TFTP, Telnet) Issue ID: 6775

Description

All X-Ware user manual/guide documents are distributed through the Synergy Gallery. In case of inconsistency with the available document in the SSP pack, the user is advised to refer to the corresponding document available from the Synergy Gallery.


8.2.4 r_agt (Asynchronous General Purpose Timer) Description

Added set duty cycle support to AGT timer.




8.2.5 r_cgc (Clock Generation Circuit) Description

XML is created to create a cgc_clocks_cfg_t structure.


Description

A new clocksCfg API is added to the CGC module. This API enables the application to start and stop multiple clocks, and switch the clock source in a single API.


Description

Operating power control is now integrated into CGC. The user no longer needs to explicitly control the operating power control mode of the MCU. The only exception is if they need to use the operating power control mode, low voltage.


8.2.6 r_dmac (Direct Memory Access Controller) Description

Added support of blockReset() in DMA driver, to support run-time reset of configuration parameters in a block transfer.

Applies to: S7G2 MCU Group. SK-S7G2 and DK-S3A7 Kits.

8.2.7 r_dtc (Data Transfer Controller) Description

Added support of blockReset() in dtc driver, to support run-time reset of configuration parameters in a block transfer.

Applies to: S3A7, S7G2 and S124 MCU Groups.

8.2.8 r_flash_hp (Flash Memory, High Performance) Description

Flash HP module now supports S5D9 Group MCUs in addition to the S7G2 Group.

Applies to: S5D9 MCU Group.

Issue ID: 6400

Description

r_flash_hp and r_flash_lp use 'f' suffix with floating point constants. Applies to: All Synergy Kits that use MCUs from S7G2 and S5D9 Groups.

8.2.9 r_flash_lp (Flash Memory, Low Power) Issue ID: 6844

Description

r_flash_hp and r_flash_lp use 'f' suffix with floating point constants.




8.2.10 r_lpmv2 (Low-Power Mode) Description

LPM V2 is a new Low-Power Modes peripheral driver with enhanced configuration support available in the Threads tab of the e2 studio Synergy Configurator.


8.2.11 r_sce (Crypto Library) Issue ID: 6009

Description

Added support for RNG and AES in Crypto Library for S124.

Applies to: S124 MCU Group.

8.2.12 r_sdmmc (SDHI driver for SDIO and SD/MMC memory devices) Description

Made the transfer module a required option for SDIO transfer, whereas earlier it was optional. Also, the SDIO block overrides all the options in DMAC/DTC except for the name.

Applies to: S7G2 and S3A7 MCU Groups.

Description

Added new control command SSP_COMMAND_SET_BLOCK_SIZE to change the block size of the SDMMC.

Applies to: S7G2 MCU Group. DK-S3A7 Kit.

8.2.13 sf_el_nx_comms (Synergy NetX Communication Interface) Description

Modified Error handling in Read API as it is returning SSP_ERR_INTERNAL instead of SSP_ERR_TIMEOUT whenever time out occurs.

Applies to: S7G2, S5D9 MCU Groups.

8.2.14 sf_el_ux (Synergy USBX Interface) Description

Changed the implementation of the USBX Port Device Controller Driver (DCD) to utilize the Block Reset API if the Transfer Module is used.

Applies to: S7G2, S7G2, S3A7 and S124 MCU Groups.

Description

Double buffer feature is implemented in the USB Port Host Controller Driver (HCD).

Applies to: S7G2, S5D9, S3A7 and S124 MCU Groups.

8.2.15 sf_message (Inter-Thread Messaging) Description

Fixed issue with using keyword ‘class’ in the st_sf_message_header. Member 'class' is now changed to 'class_code'. This change is made to make the module compatible with C++ language.




8.2.16 sf_touch_panel_i2c (Touch Panel I2C) Issue ID: 5595

Description

There is a feature to rotate a GUIX screen in GUIX Synergy Port module (sf_el_gx) in SSP1.1.0. However, there was no function to rotate touch coordinates data in the Touch Panel I2C Framework module, so users were required to rotate the coordinates manually. With this update, users are able to rotate the touch coordinate data through the Synergy Configurator. Users can configure the module property Touch Coordinate Rotation Angle (Clockwise) to apply 90|180|270 degree coordinate rotation.

Applies to: S7G2 MCU Group.

Issue ID: 5021

Description

In SSP 1.2.0-b.1 Touch chip drivers for ft5x06 and sx8654 are moved out from sf_touch_panel_i2c module. All external drivers are now placed under the renesas_sybd folder (this folder was renamed to ssp_supplemental) in SSP v1.2.0 (Issue ID 7822). With this change, the external device drivers are in non-encrypted format.

Note: For existing projects using sf_touch_panel_i2c, users need to select the touch chip driver in the configuration (use the Add Touch Driver box to select the touch driver) and generate project content. Users will see an additional directory structure for touch drivers when generating the project.

See the SSP User’s Manual to learn how to add custom drivers to the framework.


Issue ID: 7822

Description

In SSP v1.2.0 The name of the directory containing add-on modules and external driver modules such as touch panel is changed from renesas_sybd to ssp_supplemental. Known issues and their workarounds are mentioned in Section 10 of this release note.


8.2.17 ux (USBX) Description

The category of USBX (USB on ux) component on the Stacks view in the Threads tab on the Synergy Configurator was moved from Framework > USB to X-Ware > USBX. All the X-Ware related components will be placed at this location in future SSP releases.

Note: We still have USBX (USB on ux) at Framework > USB but it is marked as DEPRECATED in this version, which means it is not recommended for new development.

Applies to: S7G2, S5D9, S3A7, S124 MCU Groups.

8.2.18 ux_device_class_cdc_acm (USBX Device Class CDC-ACM) Description

The category of USBX Device Class CDC-ACM (ux_device_class_cdc_acm) component on the Stacks view in Threads tab on Synergy Configurator was moved from Framework > USB to X-Ware > USBX > Classes. All the X-Ware related components will be placed at this location in future SSP releases. In addition to the category change, the USBX Device Class stack configuration is updated. When adding the module, all relevant modules which the USBX Device Class stack relies on are automatically added to the project (auto-fill-in function).



Note: We still have USBX Device Class CDC-ACM (ux_device_class_cdc_acm) at Framework > USB, but it is marked as DEPRECATED in this version, which means it is not recommended for new development.


8.2.19 ux_src (USBX (Source) Description

The category of USBX Source (ux_src) component on the Stacks view in Threads tab on Synergy Configurator was moved from Framework > USB to X-Ware > USBX. All the X-Ware related components will be placed at this location in future SSP releases.


9. Summary of bug fixes since SSP v1.1.3 BSP (Board Support Package)

Description

Added critical section regarding update for individual MCU Register protections.

Applies to: S5D9, S7G2, S3A7 and S124 MCU Groups.

Issue ID: 5566

Description

The IOPORT write function was not reentrant, and as a result it might not actually write the expected value because another thread could lock the register before the write occurs. This has been fixed.


Issue ID: 7886

Description

The following macros, if configured for anything other than the default, may not have worked as expected.

This could have manifested itself as a problem with debugging with TraceX for example, which uses SF_CONTEXT_SAVE and SF_CONTEXT_RESTORE.

These macros now work as expected.


Issue ID: 5566

Description

The IOPORT write function was not reentrant, and as a result, may not have actually written the expected value because another thread could lock the register before the write occurs. This has been fixed.


Issue ID: 5447

Description

Fixed the defined SCI channel numbers that are not contiguous. This previously resulted in the SCI driver potentially requesting, taking and/or releasing a lock that did not belong to the SCI driver.

Applies to: S3A7, S124 MCU Groups.



r_adc (A/D converter) Description

r_adc API is updated to support 16 sample addition.

Applies to: S3A7, S7G2, S124 MCU Groups.

Issue ID: 7592

Description

Initializing ADC unit 1 after unit 0 was initialized caused unit 0 to stop working. This has been fixed now.


Issue ID: 7376

Description

The sample states value for the temperature and voltage sensors was set to a fixed value. Now, the ADC driver calculates sample states for internal sensors according to the ADC operating clock


r_agt (Asynchronous General Purpose Timer) Description

AGTCR flags are no longer cleared during start and stop for proper operation of read-modify-write.


r_can (CAN Driver) Issue ID: 7750

Description

The CAN API did not disable CAN interrupts in the close API call. The updated driver disables CAN interrupts as part of the close() function.


Issue ID: 7663

Description

If parameter checking was disabled, then the CAN open() call would fail. This has been fixed so that the CAN open() call will work irrespective of whether parameter checking is enabled or disabled.


r_cgc (Clock Generation Circuit) Description

The Systick timer interrupt priority was changed if the application changed the system clock source at runtime. This prevented the RTOS scheduler from running after the system source clock was changed.




Issue ID: 7383

Description

CGC driver was being configured to operate in low speed by default, which lead to increased power consumption and lower battery life. Now, the CGC driver is updated to set the operating mode to subosc.

Applies to: S5D9 MCU Group.

Issue ID: 7330

Description

Enum and the macro values for low voltage and low speed operating modes were interchanged. Now, they have been corrected.

Applies to: S7G2, S124 MCU Groups

r_crc (CRC Driver) Description

Issue ID: 7601

The r_crc driver does not acquire hardware lock during initialization. This could lead to failure when multiple instances of the driver attempt to use the CRC module simultaneously. The driver is now modified to acquire a hardware lock during initialization.


r_ctsu (CTSU Driver) Description

Issue ID: 6376

The DK-S3A7 and the SK-S7G2 Kits are not laid out for the best capacitive touch performance. Using boards specifically designed for capacitive touch reduces the probability of false touches and improper operation.

Applies to: S7G2, S3A7 MCU Groups

r_dmac (DMAC Driver) Description

Issue ID: 7722

Alignment error checking has been added to the r_dmac and r_dtc drivers. Alignment of the source and destination addresses must be to 2 bytes for 2 byte transfers or 4 bytes for 4 byte transfers.

Module Name: r_dmac, r_dtc

Applies to: S7G2; S5D9, S3A7 MCU Groups

r_dtc (Data Transfer Controller) Issue ID: 6299

Description

The DTC HAL driver limits the transfer size in normal mode to 1024 bytes. In synergy/ssp/src/driver/r_dtc.c, in the function R_DTC_Enable():

if (TRANSFER_MODE_NORMAL == p_local_info->mode)

{ SSP_ASSERT(p_local_info->length <= DTC_NORMAL_MAX_LENGTH); }



Where (from synergy/ssp/inc/driver/instances/r_dtc.h)

/** Length limited to 1024 transfers for normal mode */

#define DTC_NORMAL_MAX_LENGTH (0x400)

However, the DTC HW can execute up to 65535 transfers in normal mode (if CRA is set to 0xFFFF).

In repeat mode, the maximum data transfer size is 256 x 32 bits = 1024 bytes, or in block transfer mode, the maximum block size is 256 X 32 bits = 1024 bytes.

Applies to: S7G2, S3A7, S5D9 and S124 MCU Groups.

Description

The DTC xml buf fix for software event vector assignment is complete.


Issue ID: 6873

Description

DTC data transfer used to fail with blockReset API if the number of transfers were greater than 1. DTC driver can now support block data transfer up to 256 blocks.


Issue ID: 6423

Description

DTC vector table has to be aligned to a 1 K memory boundary. This could result in memory holes if left to the default allocator. There were no provisions for the user to relocate the vector table.

The DTC vector table is now configured to be at the start of the internal SRAM by default.

The linker section in which the DTC vector table should reside is made configurable through the DTC configurator.

If the default section is not used, the user is responsible for creating the corresponding linker section.

Applies to: S7G2, S5D9, S3A7, S124 MCU Groups

r_flash_hp (Flash Memory, High Performance) Description

Removed global variable g_flash_api_open and used available control structure member.


Issue ID: 6844

Description

Flash users will see a reduction of 1kB - 2kB in the amount of required ROM for this module compared with previous versions.


r_flash_lp (Flash Memory, Low Power) Description

The API opened flag has been moved into the flash_ctrl_t structure, and it is no longer a global variable.




Issue ID: 7466

Description

For the Flash LP module, accessWindowSet() no longer requires that it is preceded by a call to an erase, blankcheck, or write function.


r_gpt (General Input Timer) Description

Typo in GPT configurator displaying incorrect text (PCLK/64) in the drop-down for clock divisors fixed.


Issue ID: 7452

Description

The callback event field in the callback arguments for r_gpt was previously uninitialized. It is now initialized to TIMER_EVENT_EXPIRED.


r_ioport (General Purpose I/O Ports) Description

Ensures that the PWPR register is protected and under the control of a reference counter so that in a multithreaded system, its contents cannot be altered by another thread while executing a HW_IOPORT_PFSWrite() call.


Issue ID: 6816

Description

Null pointer check was not implemented for p_pin_cfg_data in Initialization function.

Updated IOPORT driver to perform NULL pointer check.


r_jpeg_decode (JPEG Decoder) Issue ID: 4637

Description

Two compiler warnings regarding unused parameters in auto generated code were reported for the JPEG driver. The issue is now addressed and the driver no longer generates any compiler warnings.

Applies to: S7G2 Synergy MCU Group.

Issue ID: 7623

Description

A bug was found in the r_jpeg_decode module. Data swap configurations for data input and output are applied in reverse. The issue was fixed in this release.



Applies to: S7G2 Synergy MCU Group.

r_lpm (Low-Power Mode) Description

An application using the LPM driver and ThreadX should revert the low-power mode to sleep immediately after wake up from standby. The LPM driver usage notes in SSP User’s Manual were updated to describe how to do this. This is not needed if the Power Profiles framework is used.


r_lvd (Low Voltage Detection) Issue ID: 7598

Description

When the LVD driver invoked a user callback, it did not give the correct monitor number within the returned arguments. The driver is now modified to return the correct monitor number.


Issue ID: 8005

Description

Only the register settings and configurations of the LVD peripheral have been tested using the IAR toolchain. The GCC toolchain was used for the manual tests with varying voltage as well as for the register settings and configurations of the LVD peripheral.


r_qspi (QSPI Driver) Issue ID: 6618

Description

The existing sectorErase() function available in the QSPI Interface does not provide adequate information to the user about the size of the erase being performed. A new function, erase(), has been added to the QSPI Interface which allows the user to specify the erase size. The size specified must match an erase size supported by the QSPI chip. Available erase sizes can be determined using the infoGet() function.

Applies to: S7G2, S5D9 and S3A7 MCU Groups.

r_riic (I2C Driver) Issue ID: 6699

Description

The RIIC slave driver was not capable of handling bus conditions (STOP or RESTART) that mark the end of an I2C transaction. This caused the driver to respond incorrectly in scenarios when the length of the transaction is not the same for both master and slave. The RIIC Slave driver can now detect bus conditions and correctly handle these scenarios


r_rspi (RSPI Driver) Issue ID: 7418

Description

Error ISR in the RSPI driver was modified to set the p_context value. This value was not set before, crashing the application.




Issue ID: 6015

Description

In the driver error callback, the context was not set properly. This led to a crash when user tries to dereference the context pointer. The RSPI driver now correctly sets the user context prior to invoking the callback.


Issue ID: 7531

Description

p_context in the RSPI driver was incorrectly initialized to p_ctrl in the open function, resulting in execution ending up in Default_Handler(). This issue has been resolved in this release.


r_rtc (Real Time Clock) Issue ID: 7605

Description

The RTC driver does not support the source clock adjustment feature to account for an unstable subclock oscillator or a non-32.768-kHz subclock used as RTC clock source.

The clock error correction function was removed, as this was not properly implemented. Updated the module configurator to remove these fields.

Applies to: All supported Synergy MCU Groups

Issue ID: 6340

Description

RTC driver code is updated to remove the use of the interrupt keyword as a variable name in the driver.


r_sci_i2c (SCI/I2C Driver) Issue ID: 6878

Description

A new API (slaveAddressSet) is added in the I2C Master HAL drivers (SCI I2C and RIIC) to change the slave address at run time. This API can be used to switch the slave devices without reconfiguring (no need to close and open) the bus in an application using multiple slave devices. For example, g_i2c.p_api-> slaveAddressSet (g_i2c.p_ctrl, slave, addr_mode) where g_i2c.p_ctrl is the same control instance that used in the last opened device. The driver will use the same bus configuration to communicate with the new slave device except for the slave address and addressing modes. In this case, the application can use the same device control instance to communicate with different slave devices by setting the new slave address and then using the read or write APIs. The existing way of closing the first device and opening the new device will also work.


Module Name: r_sci_i2c, r_riic



Issue ID: 6277

Description

During clock setting, the SCI_I2C driver checks for the availability of an S7G2 Group MCU device, which results in improper clock setting. The update driver checks for a specific frequency range.

Applies to: S7G2 MCU Groups

Issue ID: 5773

Description

The SCI_I2C driver did not provide proper calculations to obtain clock rate as per I2C standards. This occurred due to rounding down in integer math that is used to calculate the clock rate. The updated calculations for clock settings now round up in integer math.


Issue ID: 7755

Description

The sda delay setting on S3A7 MCUs is now calculated correctly. Previously it was reduced by 300 nanoseconds and clamped at 0 nanoseconds.

Applies to: S3A7 MCU Group

Issue ID: 6826

Description

The clock period that preceded a bus condition marking the end of an I2C transaction was too short. This caused the transaction to fail for low-speed I2C slaves. The driver is now modified to generate a valid clock period prior to issuing a bus condition (STOP or RESTART) that marks the end of an I2C transaction.


r_sci_spi (SCI/SPI Driver) Issue ID: 7417

Description

Error ISR in the SCI SPI driver was modified to set the p_context value. This value was not set before, crashing the application.


Issue ID: 6067

Description

An issue in SCI SPI with DTC that generates receive overrun errors for continuous write-only operations is fixed in this release. Only a transmit interrupt is now enabled if a transfer module is used in a write-only operation.


Issue ID: 5939

Description

In the driver error callback, the context was not set properly. This caused a crash when the user tries to dereference the context pointer. The SCI_SPI driver now correctly sets the user context prior to invoking the callback.




r_sci_uart (SCI/UART Driver) Issue ID: 8064

Description

The r_sci_uart module using with RTS callback was not built correctly with the IAR compiler. The issue has been fixed in this release.


Issue ID: 7618

Description

The Bit Rate Modulation Enable feature of the r_sci_uart did not reduce % error in the baud rate as expected. This has been corrected.


Issue ID: 7608

Description

When using r_sci_uart in 9-bit mode, the most significant bit would be incorrect. This has been corrected.

Issue ID: 6531


Description

On non FIFO channels, the UART driver used to transmit an extra duplicate byte. The UART driver is now modified to remove the duplication during transmission.


Issue ID: 7346

Description

An issue was fixed where UART write would not complete when writing one byte with DTC enabled for transmission.


r_sdmmc (SD/MMC) Issue ID: 7217

Description

The infoGet function now additionally returns the values for the following fields:

• p_info->bus_width • p_info->hs_timing • p_info->device_type • p_info->sdio

Applies to: S7G2, S5D9 and S3A7 MCU Groups



Issue ID: 7233

Description

The r_sdmmc read and erase functions now return an error if a previous transaction is still in progress or if the card status is busy. Previously only the write function returned an error if a previous transaction is still in progress or if the card status is busy.

Applies to: S3A7, S5D9, S7G2 MCU Groups

Issue ID: 7798

Description

The hardware lock may be released if open is called more than once for the same channel. This may cause a subsequent open to succeed prior to the channel being closed with respect to the previous open.


Issue ID: 7355

Description

For SD cards or eMMC, the default block size is set to 512. No other block size is supported in this version. Also the read or write buffers must be at word (32-bit) boundaries.

Applies to: All Synergy Kits using devices from the S3A7 and S7G2 MCU Groups.

Issue ID: 7337

Description

The SD or eMMC media may or may not work, or may exhibit errors at a PCLKA speed greater than 32 MHz. Boundary conditions are now checked.


r_slcdc (LCD Controller) Issue ID: 7465

Description

The r_slcdc module was not functional because it used an incorrect base address to access SLCDC registers. This has been corrected.


r_ssi ((Inter-IC Sound) interface [old: Serial Sound Int.] or r_i2s) Description

Typo in I2S configurator text, Enabled should be I2S_WS_CONTINUE_ON.

Applies to: S7G2 MCU Group

Description

Fixed typo in the generated code for the transfer driver instance in SSI configurator.

Applies to: S7G2 MCU Group



Description

The SSI DTC activation source calculation for channel 1 was incorrect. This is fixed, and SSI channel 1 can be used with DTC.

Applies to: S7G2 and S3A7 MCU Groups

Issue ID: 7891

Description

The transmit overflow interrupt in the r_ssi module was not cleared correctly. The transmit overflow interrupt is not used by the driver, so it has been disabled.

Applies to: 5D9 MCU Group

sf_audio_playback (Audio Playback Framework) Issue ID: 5945

Description

During audio playback, invoking the stop API while the stream is playing would put the driver to an invalid state. This would cause all subsequent attempts to start a playback to fail. Driver is now modified to do proper cleanup on invocation of stop API.


Issue ID: 7482

Description

An issue was fixed that caused incorrect playback when using mixing in sf_audio_playback and not using software volume control, shifting, or scaling.


Issue ID: 7481

Description

An issue was fixed that caused sf_audio_playback stop() to stop all streams in the system instead of just the stream stop() was called for.


sf_console (Console Framework) Issue ID: 7599

Description

USBX comms framework auto-generated code always initializes itself. This will cause failures in scenarios such as where the device is connected after the board is powered on. The issue has been fixed by giving the user an option to configure whether or not the initialization call should be enabled/disabled and specify the name of the initialization function in the Synergy configurator.

Module: SF_EL_UX_COMMS and SF_CONSOLE




sf_el_fx (Synergy FileX Interface) Issue ID: 7395

Description

Fixed an issue where the FileX service call fx_file_write() could cause a hard-fault error due to an invalid pointer that may have been inadvertently assigned to the fx_file_write_notify user callback function.

Fixed an issue where the API fx_file_write_notify_set() caused a build error due to an incorrect MACRO definition


sf_el_gx (Synergy GUIX Interface) Description

There was an issue in GUI Synergy Port module that caused slow rendering and tearing on LCD panel screen for the following configurations:

• Screen rotated 90 or 270 degrees • 2DG engine enabled (DRW module) With this fix, the rendering speed got faster and tearing does not happen.

Applies to: S7G2 and S5D9 MCU Group.

Issue ID: 5754

Description

A bug was found in the GUIX Studio resource generation that caused "externs" for pixelmaps written to secondary output file not to be declared, and it caused build errors. This issue was fixed in v5.3.2.2.


Issue ID: 6366

Description

GUIX driver had a different output when used with software rendering compared to hardware rendering. GUIX is updated to render the same output independent of the rendering engine.


Issue ID: 6029

Description

GUIX configurator was allocating memory to JPEG work buffer even if it was not enabled. This is now modified to allocate memory to JPEG work buffer only when the respective option is enabled.


Issue ID: 6091

Description

There was a bug creating a "smudging" effect in the GUIX scrolling chart if DAVE 2D hardware acceleration was enabled. This issue was fixed in this release.




Issue ID: 5697

Description

The use of C standard library such as sprintf could have affected the 2DG engine (TES D/AVE 2D). This was because sprintf could overflow the heap memory (.heap) if it is not large enough, and the broken .heap_d1 section used by the 2DG engine to create the Display List. .heap_d1 section was located at right after .heap section. The order of heap sections was changed to locate .heap_d1 before .heap to make this issue less likely.

Side note: Users need to be aware of large heap memory use when sprintf is used.

Applies to: S7G2 and S5D9 MCU Groups

sf_el_nx_comms (Synergy NetX Communication Interface) Description

Chained Packet support was added in SSP v1.1.0 but one compiler warning remained unresolved. The warning is now resolved.


Issue ID: 7319

Description

Implementation of the user callback support for the run-time Ethernet MAC address configuration is now supported in the Synergy Configuration tool.


Issue ID: 7760

Description

The PHY driver files ether_phy.c and ether_phy.h can no longer be modified without changes being overwritten during the build process. To create a custom PHY driver, these files must be copied into the application source and edited there. The PHY driver packaged with the SSP must then be excluded from the build.


Issue ID: 5767

Description

After deleting an IP instance, then creating a new one, Ethernet negotiation would fail. This has been fixed.


Issue ID: 8051

Description

When the runtime MAC address is used, it was not updated in the hardware. This caused missed reception of all incoming Ethernet packets. This is now fixed.




sf_el_ux (Synergy USBX Interface) Description

Assigned proper FIFO Index for USBX HCD Interrupt transfer, so that the driver uses DFIFO for DMA Interrupt transfer, instead of using CFIFO every time.

Applies to: S7G2, S3A7 MCU Groups.

Description

On Synergy Configurator Stacks view, there is a constraint for the USBX Port (sf_el_ux) component to warn users to enable the USBFS interrupt, if not enabled. However, the constraint was not functional for MCUs from the S3A7 Group. With this fix, the constraint works as designed.

In addition, the component USBX Port (sf_el_ux) is split to four components in this release, as described in section 8.1.22.

For devices from S3A7 Group MCUs, users can choose USBX Port HCD for USBFS for USB Host classes, or USBX Port DCD for USBFS for USB Device classes.

Applies to: S3A7 MCU Group.

Description

USBHS peripheral on S7G2 or S5D9 Group MCU devices has a BUSWAIT register, which is used for adjusting access cycles to the USBHS registers from bus masters (CPU/DMAC or DTC). In SSP release 1.1.0, the access cycle was fixed to 7 cycles but it was only appropriate when the PCLKA frequency is 120 MHz. The access cycle calculation has been made configurable at run-time based on the PCLKA frequency configuration that is selected.


Description

USB data throughput is improved for USB HCD (Host Controller Driver) for bulk transfer, by adding continuous transfer, configurable FIFO size, and optimized read (IN) and write (OUT) transfer logic.

The FIFO size can be configured using the macro UX_SYNERGY_MAX_BULK_PAYLOAD as a preprocessing option in your project. The valid values start from 64 bytes to 2kB for bulk transfer, but it is recommended to configure the macro value to 2048, to achieve maximum throughput.

The FIFO size configuration is valid in the case of High Speed Host and not valid for Full speed.

Applies to: S7G2, S3A7 MCU Groups.

Issue ID: 7648

Description

Because of wrong definition in the sf_el_ux XML, the auto-generated code in common_data.c did not setup the USBX port driver to enable DMA transfer for USBFS port even if the transfer modules were added in the Synergy Configuration tool. The issue is fixed in this release.


Issue ID: 7595, 6781

Description

A constraint was missing for the Interrupt Priority setting of USB peripheral in the USBX Port HCD|DCD on sf_el_ux component, if DMA transfer is used. It was added in this release so that users are warned if they make an invalid setting.



DMA Interrupt priority value should be always higher than USB interrupt priority when configured in the xml configurator (interrupt priority value of 0 is highest priority and value of 15 is the lowest priority).


Issue ID: 7400

Description

The Synergy Configuration tool might have crashed if the migration of the pincfg file failed and sf_el_ux was in the project. The issue is fixed in this release.


Issue ID: 7151

Description

There was a bug in the XML for [DEPRECATED] USBX Port HS and FS on sf_el_gx to set BSP_IRQ_DISABLED(=255) to the interrupt priority of USB peripheral even if the valid interrupt priority was set to the property. Because of that, the SF_EL_UX (USB Port driver) module did not work correctly (actually it ran, but too slowly). The issue is fixed in this release.

Applies to: S7G2, S3A7 and S5D9 MCU Groups

Issue ID: 6908

Description

There was non-appropriate implementation in SSP v.1.2.0-b.1 to generate multiple USB host class instances (UX_HOST_CLASS type) in the auto-generated code from the XMLs for USBX Host Classes. In SSP v.1.2.0, the instance is no longer generated more than once. Users can get the host instance in their application code by using USBX Host stack API ux_host_stack_class_get.


Issue ID: 6119

Description

There is a bug found in _ux_hcd_synergy_control_td_add(). Because of that, USB Host Control Driver set the wrong device address if a device was connected behind a USB Hub. The issue is fixed in this release.


Issue ID: 7732

Description

A wrong macro definition was is found in SF_EL_UX (USBX Port driver).

UX_SYNERGY_HC_MAX_BUF_NUM defined in ux_hcd_synergy.h and UX_SYNERGY_DCD_MAX_BUF_NUM defined in ux_dcd_synergy.h are 127 (0x7F) but the correct value is 135 (0x87). This issue is fixed in this release.


Issue ID: 7472

Description

DTC is now available for use with the USBX Port driver. Previously, the same ELC event source (ELC_EVENT_ELC_SOFTWARE_EVENT_0), as the DTC activation source, was provided for both the USB transmission and reception channels. However, each channel needs a different activation source



ELC_EVENT_ELC_SOFTWARE_EVENT_0 and ELC_EVENT_ELC_SOFTWARE_EVENT_1, to make it work. The issue is resolved in this release.


Issue ID: 7761

Description

Fixed the data corruption issue while using DMA transfer for file read from a mass storage device in high speed mode. This fix impacts the performance for mass storage bulk read operation. Currently, the maximum throughput achieved for mass storage read is around 14.7 Mbps for High-speed mode with 32 kB configured in the usbx host class configurator for storage memory size and maximum transfer size.


Issue ID: 6351

Description

Connection failure was observed when a USB device was repeatedly connected and disconnected. A USB device can now be reconnected any number of times to the USBX host controller driver (HCD).


Issue ID: 6638

Description

Due to a bug with fixed value of "g_sf_comms0_instance_ctrl" in the configurator generated code, only one instance (one COM channel), and the default given name was available for use. The issue was fixed in this release.


Issue ID: 7557

Description

The USBX Host Controller Driver (HCD) in SF_EL_UX module is now able to handle Bulk-Out Transfer required for USB Host Class Mass storage or CDC-ACM. Previously, the USBX HCD stopped working in transaction because the Transaction Counter supported by the USBHS peripheral was enabled incorrectly if the property "FIFO size for Bulk Pipes" of "USBX Port HCD on sf_el_ux for USBHS" component was set to 1024 bytes, 1536 bytes, or 2048 bytes in the Synergy Configuration tool. The transaction counter is only valid for reception PIPEs. sf_el_ux_comms (Synergy USBX Communication Interface)


Description

The USB CDC class initialization is moved from the open function call of sf_el_ux_comms framework to the code auto-generated by the USBx CDC XML configurator.

Applies to: All Synergy MCU Groups

Issue ID: 7631

Description

sf_el_ux_comms instance name was not configurable by the user in the Synergy configurator. It is now user configurable.

All supported Synergy MCU Groups




Issue ID: 7545

Description

The sf_console framework did not work with the [DEPRECATED] sf_el_ux_comms communication framework due to incorrect auto-generated code.

The issue is fixed by generating the correct code.

All supported Synergy MCU Groups

Issue ID: 6119

Description

There was a bug found in _ux_hcd_synergy_control_td_add(). Because of that, USB Host Control Driver set wrong device address if a device was connected behind a USB Hub. The issue was fixed in this release


Issue ID: 7557

Description

The USBX Host Controller Driver (HCD) in SF_EL_UX module is now able to handle Bulk-Out Transfer required for USB Host Class Mass storage or CDC-ACM. Previosuly the USBX HCD stopped the working in transaction because the Transaction Counter supported by USBHS peripheral was enabled wrongly if the property "FIFO size for Bulk Pipes" of "USBX Port HCD on sf_el_ux for USBHS" component was set to 1024 bytes, 1536 bytes or 2048 bytes in the Synergy Configuration tool. Transaction counter is only valid for reception PIPEs.


sf_power_profiles (Power Mode Profile) Description

The clock configuration was not being verified before changing the operating power control mode of the MCU. The clock configuration is now verified to be compatible with the subosc-speed operating power control mode.


Description

Power Profiles was updated to revert the low-power mode after wake up from standby when ThreadX is part of a project.


sf_thread_monitor (Thread Monitor) Issue ID: 5724

Description

Fixed a bug in which the ThreadX port would cause a hard fault if the CM0+ ThreadX source was used on GCC with no optimization.




Issue ID: 6247

Description

ThreadX Source for CM0+ parts may end up in the default handler. The issue has been fixed.


sf_touch_panel_i2c (Touch Panel I2C) Description

An issue was found in getting a NAK return from SX8654 touch chip controller in the I2C communication. It resulted in the hang up of the Touch Panel I2C Framework module as the touch chip continues to hold the IRQ signal line at a low level. The framework module needs the IRQ signal line to be back high to handle the next touch event, so it needs to have the touch chip set the IRQ signal high. With this update, the SX8654 touch controller driver performs retry communications (up to 10 times) if the chip returned NAK and tries to return the IRQ signal back to high.


gx (GUIX) Issue ID: 6370

Description

Resolved a bug in GUIX API _gx_system_timer_expiration() to not set a member named 'gx_event_target' of the timer_event structure.


Description

GUIX sporadically crashed due to the usage of an uninitialized variable. Variables are now initialized properly prior to use.


Issue ID: 6220

Description

Multi-line texts drawn by _gx_multi_line_text_view_text_set() API may be gone from the widget if the widget is once hidden under the other widget.

This issue fix was addressed in GUIX5.3.2.


Issue ID: 6370

Description

GUIX use to sporadically crash due to use of an uninitialized variable. Variables are now initialized properly prior to use.


Issue ID: 6220

Description

Multi-line text drawn by the _gx_multi_line_text_view_text_set() API may disappear from the widget if the widget was once hidden under another widget. This issue was fixed in GUIX 5.3.2.




Issue ID: 6828

Description

A bug that caused the JPEG hardware rendering failure happened in the _gx_synergy_jpeg_draw function when SSP1.2.0-p.1 was released. The cause is that SSP module architecture was updated to use sf_jpeg_decode_instance_ctrl_t or jpeg_decode_instance_ctrl_t instead of sf_jpeg_decode_ctrl_t or jpeg_decode_ctrl_t respectively as the driver control block, but the required changes were not made to the functions. The issue was fixed in this release.

Module name: gx (GUIX)/sf_el_gx (GUIX Synergy Port)

Applies to: DK-S7G2, SK-S7G2, PE-HMI1, DK-S5D9 Kits

ux_host_class_storage(USBX Host Mass Storage Class) Issue ID: 6866

Description

There was a known issue that USBX Host Mass Storage Class (MSC) and NetX HTTP Server did not work together. It was because the pointer to a FileX Media control block (FX_MEDIA * type) which is required for NetX HTTP Server was not provided by USBX Host MSC. The issue was resolved in this release.


nx (NetX) Issue ID: 7833

Description

NetX IP Instance auto-generated code used to combine all errors, effectively corrupting the error value. The driver was modified to return errors immediately, thus makes debugging easier.


Issue ID: 7800

Description

The NetX configurator did not have an option to enable/disable IP fragmentation. The configurator can now support this configuration option.


Issue ID: 7725

Description

Default pool packet size of 512 bytes was not large enough to accommodate the default HTTP servers packet size of minimum 600 bytes along with a minimum of 40 bytes for IP packet header. Packet pool size now defaults to 640 bytes to accommodate this.


Issue ID: 7559

Description

A NetX packet pool that does not have NetX common as a dependency, caused the packet pool pointer to reinitialize, leaving already created packet pool unusable. The driver is now modified to have the correct dependency tree.




Issue ID: 7512

Description

The NetX source component in ISDE had an option for enabling/disabling NAT. NAT is not available for NetX, it is only available for NetX Duo. Configurator is now modified to remove this option.


Issue ID: 8063, 8062

Description

Build issues in the generated code of the nx_auto_ip and nx_telnet_server_v2 modules with the IAR compiler are fixed in this release.


nxd_dhcp (NetX Duo DHCP Client) Issue ID: 6646

Description

A bug in the nx_dhcp_user_option_retrieve function to return data with bytes swapped is now fixed. This issue was observed from SSP1.1.1 to SSP1.2.0-b.1. Users who used these SSP versions and applied the recommended workaround "Swap bytes of the IP address which is obtained by nx_dhcp_user_option_retrieve()" now need to remove the workaround code.

Impacts nx_dhcp (NetX DHCP Client) and nxd_dhcp (NetX Duo DHCP Client)


ThreadX Issue ID: 6872

Description

Some of the display names in the ISDE Pin Configurator for the SCI and Bus signals were inaccurate/inconsistent. These were fixed.


tx_src (ThreadX Source) Issue ID: 5625

Description

SSP now supports ThreadX configuration through the Synergy Configurator, which was not available before SSP1.1.0 release. Users had needed to edit tx_port.h to change the ThreadX build-time options but it is no longer required. To configure Thread X build-time options, set the Properties of the ThreadX Source (tx_src) component under the Threads tab in the Synergy Configurator. Configurations are outputted to tx_src_user.h in the \synergy_cfg\framework\el\ directory.




ux (USBX) Description

USBX Device CDC-ACM Class could stall in the service call ux_device_class_cdc_acm_read() when it met the following conditions:

• "requested_length" argument of ux_device_class_cdc_acm_read() is larger than wMaxPacketSize (*see note below)

• Reception data in bytes from USB Host CDC-ACM device was exactly the same number as wMaxPacketSize • USB Host CDC-ACM device did not send consequent data after sending bytes with wMaxPacketSize. *Note: wMaxPacketSize: Maximum payload size specified in the BULK-OUT Endpoint Descriptor in the USB Device

Descriptor (it is 64 Byte in FS mode or 512 Byte in HS mode in general).

This issue no longer occurs in this release since the ux_device_class_cdc_acm_read() was updated to return to the caller application when receiving data equal to wMaxPacketSize in bytes.

IMPORTANT NOTICE: The ux_device_class_cdc_acm_read() returns to the caller when receiving data equal to wMaxPacketSize in bytes, regardless of the number specified to "requested_length". It is the user’s responsibility to check the "actual_length" argument returned back from the service call to find out if the total reception bytes reached the "requested_length".

Applies to: S7G2, S3A7, S124 MCU Groups.

Description

Resolved an issue where the ux_host_class_hub.h file has duplicate entries in Synergy project and caused compilation errors in some situations.


Issue ID: 6775

Description

NetX and USBX X-Ware user manuals are longer distributed as part of the Synergy Software Package. However they are available on Synergy Gallery

Applies to: USBX and NetX

Issue ID: 7549

Description

There was a bug in USBX that wasted extra memory (1.6 kB) of the USBX system memory pool. This issue was fixed in USBX5.7SP7 and the version was integrated in this release.

There was another issue in USBX, that did not check the size of USBX system memory pool which is given by user through USBX ux_system_initialize API and resulted in wrong calculation of free memory area and ended in system crash. This issue was fixed in USBX5.7SP7 and the version was integrated in this release.


ux_host_class_hid (USBX Host Class HID) Issue ID: 7621

Description

Added new Class Code "Device (0x00)" in the Properties of the "USBX Device Configuration" component.

Module Name: USBX Device Classes

CDC interface number is now configurable. This issue was seen in the Device Descriptor for High-Speed.



Module Name: USBX Device CDC-ACM Class


Issue ID: 7818

Description

In 1.2.0-b.1, the prebuilt library for USBX Host HID does not work when included in the application project. This is due to an incorrect build-time configuration applied for the library build. This issue has been fixed in 1.2.0. Applications can now use pre-built library for USBX Host HID.


ux_host_class_storage (USBX Host Mass Storage Class) Issue ID: 6866

Description

There was a known issue that USBX Host Mass Storage Class (MSC) and NetX HTTP Server did not work together. It was because the pointer to a FileX Media control block (FX_MEDIA * type), which is required for NetX HTTP Server, was not provided by USBX Host MSC. The issue was resolved in this release.


ux (USBX) Issue ID: 6672

Description

Low-speed devices were not supported by the Synergy USB host. Low-speed devices such as USB keyboard and mice are now supported.


Express Logic X-Ware Issue ID: 5633

Description

A multiple symbol definition error may occur during linkage if an X-Ware library component and the corresponding source component such as ux and ux_src are included. If this occurs, remove the library such as libux.a from the list of libraries used by the linker.

For GCC: in the Cross ARM C Linker > Libraries section of the C/C++ Build > Settings in the project Properties.

For IAR: in the IAR Linker for ARM > Library section of the C/C++ Build > Settings in the project Properties.

Module Names: ux (USBX), tx (ThreadX), nx (NetX), nxd (NetX Duo), fx (FileX), gx (GUIX), ux_host_class_XXX (USBX Host Classes), ux_device_class_XXX (USBX Device Classes).


Crypto API Issue ID: 7933

Description

Fixed an issue where the zeroPaddingDecrypt() function for the AES GCM interface returns an incorrect status code when validating an authentication tag.




NetX POP3 Client Issue ID: 7392

Description

NetX POP3 client auto-generated code always initializes itself by trying to connect to the POP3 server. This will cause failures in scenarios where the POP3 server is not ready to service any requests.

The issue has been fixed by giving the user an option to configure whether auto-generated code should be enabled/disabled and to specify the name of the initialization function in the Synergy configurator.


NetX with Ethernet Driver Issue ID: 5725

Description

A memory leak was caused by nx_http_client_get_start() if we received a GOOD request without “Content-Length”. This issue was fixed in this release.


MCU Implementation/SW Architecture Issue ID: 6530

Description

The BSP properties page did not accurately allow configuration of the Secure MPU for S3A7. That has been corrected.

Additionally it also did not allow any configuration of the Secure MPU for S5D9. That has also been corrected and the Secure MPU may now be configured from the BSP properties page for these MCUs.

Applies to: S3A7, S5D9 MCU Groups

Issue ID: 7433

Description

Three MCU devices from S124 Group are added to the SSP: R7FS124762A01CLM, R7FS124763A01CFL, and R7FS124763A01CFM.

Applies to: S124 MCU Groups.

Issue ID: 7894

Description

The S3A7 Factory Flash had an incorrect register offset for the high-speed comparator. This has been fixed.


Synergy Tools – GCC Toolchain Issue ID: 5545

Description

Customers should use the version 4.9 or greater GCC ARM Embedded Toolchain.



Otherwise the build might fail to build due to _sbrk function duplication (original exists in the GCC library). An improved version of _sbrk has been added to the SSP to fix the malloc() issue, but the compiler reports function duplicate on build and generates an error.

Workaround for GCC Toolchain 4.8: In the project settings, the default linker flag: --specs=rdimon.specs should be changed to: --specs=nosys.specs.

Applies to: Projects using GCC ARM Embedded Toolchain

Synergy Tools – ISDE Pin Configurator Issue ID: 6862

Description

In the ISDE Pin Configurator, some pins could be set for IRQ behavior when the port pin was in a disabled state.


10. Known issues with SSP v1.2.0 release Issues Common to all of SSP modules (generic)

Issue ID: 5612

Description

Information in the Description column of the Components pane of the Synergy Configurator in e2 studio might be invalid.

Workaround: Ignore the information in the Description column of the Components pane.

Applies to: All SSP modules.

r_adc (ADC Module) Issue ID: 8072

Description

If the ADC driver is configured to use the temperature or voltage sensor, then the infoGet function will not return the right address for the conversion result register for those sensors. This information is primarily used by the DTC to automatically transfer data when a conversion is complete.

Impact - Since the ADC Periodic Framework uses this function, the framework will not be functional with the temperature or voltage sensors.

Workaround: Application can use the ADC HAL driver directly with temperature and voltage sensors. Applies to: All supported Synergy MCU Groups.

r_cac (CAC Module) Issue ID: 7790

Description

When specifying 'External' as the CAC reference clock, e2 studio generates incorrect configuration.

Workaround:

The correct configuration must be created using a manually created configuration structure, adjusting the measurement and reference clock sources as needed. An example is shown below, which shows a Measurement clock of HOCO and an External Reference clock.

void myCACCallback(cac_callback_args_t * p_args);

void hal_entry(void)



{

ssp_err_t err;

static const cac_cfg_t my_cac0_cfg =

{ .mei_interrupt_enabled = true, .ovf_interrupt_enabled = true, .cac_ref_clock.digfilter = CAC_REF_DIGITAL_FILTER_OFF,

.cac_ref_clock.edge = CAC_REF_EDGE_RISE, .ferr_interrupt_enabled = true, .continuous_mode = true,

.cac_ref_clock.clock = CAC_CLOCK_SOURCE_EXTERNAL, .cac_ref_clock.divider = CAC_REF_DIV_32, .cac_meas_clock.clock =

CAC_CLOCK_SOURCE_HOCO,

.cac_meas_clock.divider = CAC_MEAS_DIV_1, .cac_upper_limit = 0, .cac_lower_limit = 0, .frequency_error_ipl = (1),

.measurement_end_ipl = (1), .overflow_ipl = (1), .p_callback = myCACCallback, .p_context = &g_cac0

};

err = g_cac0.p_api->open(g_cac0.p_ctrl, &my_cac0_cfg);


Issue ID: 7958

Description

Low-level ARC4 cryptographic functions have been removed this release.


gx (GUIX) Issue ID: 5731

Description

In file gx_port.h, a macro named GX_TICKS_SECOND is set to 20 by default, which sets the delay time to 400 ms (20 x 20 ms), instead of the anticipated 1 second (1000 ms), if GUIX system tick time is set to 20 ms (default).

Workaround: Define the symbol “GX_TICKS_SECOND=50” in the C Compiler Preprocessor, which sets the delay time to 1000 ms (50 x 20 ms).


Issue ID: 5343

Description

The IS_SIGNAL() macro is wrongly defined in gx_api.h and uses the label 'LAST_SIGNAL', which is not defined within GUIX, but is a typo of 'GX_LAST_SIGNAL'. The use of IS_SIGNAL() results in a build error.

Workaround: Define LAST_SIGNAL=0x00ffffff as a C Compiler Preprocessor.

Applies to: S7G2, S5D9, S3A7 MCU Groups

MCU Implementation/ SW Architecture Issue ID: 7329

Description

Module: BSP (CMSIS DSP Library)



A linker error may occur when DSP library functions are used.

Workaround: Download the DSP library from ARM and add the file CMSIS\DSP_Lib\Source\CommonTables\arm_const_structs.c to your project. The CMSIS DSP library can be downloaded at http://www.arm.com/products/processors/cortex-m/cortex-microcontroller-software-interface-standard.php.


Issue ID: 6625

Description

In the current SSP code for C++, the static constructor for C++ is not added by default.

Workaround: The user needs to add this in the application code. This will be added as part of the SSP code in the next version. Please refer user manual to see how to add the static constructor in the application.

Module: C++ support


Issue ID: 5812

Description

When developing with SSP using e2 studio for Linux (available as a beta version), users will run into issues caused due to the case used in folder names (Linux being case-sensitive). This is because some folder names in SSP are in upper case (they should have been in lower case).

Workaround:

In order to work around this issue, manually make the following corrections in the <e2_studio_base_dir>/internal/projectgen/arm folder:

• Rename "Packs" folder to "packs" • Rename "Templates" folder to "templates" • Rename "Licenses" folder to "licenses"

Note: It is NOT necessary to change the sub-folder names below the "templates/synergy" folder.

NetX Issue ID: 7923

Description

If the user adds NetX Duo NAT support to their project, the ISDE does not warn them that NAT is disabled by default in NetX Duo, that is, that the default value for NX_MAX_PHYSICAL_INTERFACES is 1.

Workaround: To use NetX Duo NAT, the user must first add NetX Duo Source to their project. The prebuilt NetX Duo library uses default settings, where NAT is disabled. Once NetX Duo Source has been added, the user should enable NAT in its properties. It is likely that the user may need to modify the "Maximum Physical Interfaces" property, which controls the NX_MAX_PHYSICAL_INTERFACES macro, as it defaults to 1. The NetX Duo User Manual has more details about the NX_MAX_PHYSICAL_INTERFACES macro.


Issue ID: 6390

Description

NetX Duo (5.10 SP1) does not compile when TraceX is enabled.

Workaround: Do not use TraceX if NetX Duo is used. This will be fixed in upcoming release.

http://www.arm.com/products/processors/cortex-m/cortex-microcontroller-software-interface-standard.php

http://www.arm.com/products/processors/cortex-m/cortex-microcontroller-software-interface-standard.php




Issue ID: 8117

Description

NetX and NetX Duo FTP server, FTP Client, HTTP server, and TFTP server will not compile with FileX support disabled.

Workaround: FileX support is required to be enabled while using NetX/NetX Duo, for FTP, HTTP or TFT server or FTP client Module name: NetX and NetX Duo FTP server, FTP Client, HTTP server, and TFTP server.


NetX DHCP (Client) Issue ID: 8174

Description

NetX DHCP Client does not work if TraceX is enabled.

Workaround: None, do not use TraceX for NetX DHCP Client.


NetX with Ethernet Driver Issue ID: 7803

Description

HTTP Server for NetX and NetX Duo cannot parse the HTTP request when it receives CR/LF separately.

Workaround: The HTTP Server nx_http_server_content_get() API is used to get the beginning data of HTTP body. The message header must be sent in one packet. Once nx_http_server_content_get() returns successfully, the application can retrieve the remaining data by calling the nx_http_server_packet_get() API.


r_cac Issue ID: 7678

Description

Using an inactive clock source in the CAC configuration structure when calling open()returns SSP_ERR_CLOCK_INACTIVE even though the function header does not list this as a possible return code.

Applies to: All Synergy MCUs supported by the r_cac driver.

Workaround: User code must expect SSP_ERR_CLOCK_INACTIVE to be returned if the selected clock source is inactive.




r_can Issue ID: 8003

Description

CAN bus recovery and subsequent user notification may not be functional. CAN bus recovery occurs when a CAN device is unplugged from the CAN bus and subsequently plugged back in. The CAN bus recovery is used to notify the application that the device has been plugged back in successfully.

Workaround: The CAN_EVENT_ERR_BUS_OFF notification is provided to the user when the device is unplugged from the bus. Use this event to stop CAN operation and close the driver. Periodically re-open the driver and check to see if messages can be sent indicating that the device is plugged back in.


r_cgc Issue ID: 8057

Description

A project generated for the S7G2-DK or S7G2 HMI boards has the r_cgc Main Oscillator Clock Source incorrectly set to Crystal or Resonator. The proper setting for these boards should be External Oscillator.

Workaround: Subsequent to creating an application for either of these boards, navigate to the g_cgc CGC Driver on r_cgc in the HAL/Common Stacks window. In the properties for that driver, change Main Oscillator Clock Source to External Oscillator.


Issue ID: 6481

Description

The API functions systemClockGet, systemClockFreqGet, and clockStart do not check parameters that are NULL pointers for NULL. The application code using the functions should check this either in the code or by code audit.


r_ctsu Issue ID: 6931

Description

Parameter checking for NULL parameters is not implemented. Passing in a NULL parameter to the r_ctsu API results in undefined system operation.


r_flash_lp Issue ID: 7492

Description

On Flash LP parts with 1 MB Code Flash and/or 16 K Data Flash, a blankcheck spanning the midpoint memory boundary may return inaccurate results, possibly reflecting the blank status of only part of the requested range.

Some Data Flash examples that meet this criteria:

blankCheck(&ctrl, 0x40100000, 0x4000, &blank_check_result)

blankCheck(&ctrl, 0x40101F00, 0x200, &blank_check_result)

Some Code Flash examples that meet this criteria:



blankCheck(&ctrl, 0, 0x90000, &blank_check_result)


Workaround: To ensure that accurate results do not issue a singular blankcheck function whose range spans the midpoint of the Code or Data Flash memory, break the request into two separate blankcheck requests, one up to, but not crossing the midpoint, and a second blankcheck making up the difference.

Using the examples above, and breaking the operation into two separate operations, the operations would look like the following:

Workaround Data Flash examples:



blankCheck(&ctrl, 0x40101F00, 0x100, &blank_check_result)


Workaround Code Flash examples:

blankCheck(&ctrl, 0, 0x80000, &blank_check_result)




Applies to: S3A7, S124 MCU Groups

Workaround: None.

r_gpt Issue ID: 7954

Description

If the gpt_instance_ctrl_t control block is allocated on the stack (uninitialized), the timer may operate in one shot mode event if periodic mode is selected during configuration.

Workaround: Initialize the gpt_instance_ctrl_t block to {0} prior to calling open() if it is allocated on the stack.

Issue ID: 7731

Description

If the user is attempting to use the GPT timer in one-shot mode, but interrupts are not enabled, the driver will return an SSP_ERR_IRQ_BSP_DISABLED error. The function header states that SSP_ERR_INVALID_ARGUMENT will be returned in this case, which is a documentation error.

Similarly, attempting to configure an invalid GPT timer channel will cause the driver to return SSP_ERR_IP_CHANNEL_NOT_PRESENT. The function header states that SSP_ERR_ASSERTION will be returned in this case, which is a documentation error.

Workaround: The user application should expect SSP_ERR_BSP_IRQ_ENABLED to be returned if attempting to configure the timer in one-shot mode with interrupts disabled.

The user application should expect SSP_ERR_IP_CHANNEL_NOT_PRESENT to be returned if attempting to configure an invalid timer channel.



r_gpt_input_capture Issue ID: 6720

Description

Only GTIOCA can be used as a capture source by the GPT input capture module. GTIOCB cannot be used as a capture source.

Workaround: Use GTIOCA as the capture source.

Issue ID: 8060

Description

The configurator for r_gpt_input_capture does not automatically add r_gpt to the project

Workaround: When using r_gpt_input_capture, make sure that r_gpt is checked on the Components tab to avoid build errors.

r_lpmv2 Issue ID: 8058

Description

Module: r_lpm, sf_power_profiles, r_lpmv2, the low power mode peripheral hardware, ThreadX

The issue is caused by ThreadX executing the WFI (wait for interrupt) instruction without checking that the low power mode peripheral is in the correct mode.

Workaround:

The user of r_lpm, sf_power_profiles, r_lpmv2, or the low power mode peripheral directly, will need to make sure to keep the low power mode peripheral configured in Sleep mode at all times, if there is a possibility that at least one thread is not in the ready to run state. This means that the user of r_lpm and r_lpmv2 should only configure the low power mode peripheral (lowPowerCfg) immediately before the function lowPowerModeEnter is called. The user must also revert the configuration of the low power mode peripheral to Sleep mode after the execution returns from lowPowerModeEnter.

r_rspi Issue ID: 6068

Description

In SPI slave mode operation, when using in CPHA=0 configuration, master receives incorrect data in some cases.

Workaround: It is recommended to use CPHA=1 configuration for SPI slave mode operations.

Issue ID: 8112

Description

The RSPI module configuration in the Threads tab shows wrong Tx transfer (DTC) activation source (Software activation instead of TX Interrupt).

Impact - There would be no functional impact because of this issue as the driver code behind this is using the correct activation source.



r_sci_i2c Issue ID: 7946

Description

SCI I2C driver in IRQ mode may not work with noise and timing sensitive slave devices. Driver needs to configure with DTC transfer module in order to work with such slave devices.

Workaround: In that case it is recommended to use the DTC transfer mode.

SDHI and MMC Issue ID: 6118

Description

MMC cards do not work with the SDMMC driver. This is not an issue with SD cards or eMMC devices.

Workaround: Use SD cards instead of MMC cards.

sf_el_gx (GUIX Port) Issue ID: 7693

Description

Alpha blending does not work in the glyph drawing if 2DG engine (D/AVE 2D) is used.

Workaround: Disable the use of 2DG engine if alpha blending is required for glyph drawing.

Issue ID: 7641

Description

A build error happens if having a sprite on the top window. GUIX Studio generate code "xxx_specifications.h" cannot be built if having a sprite on the top window.

Workaround: Replace "GX_sprite_MEMBERS_DECLARE" with "GX_SPRITE_MEMBERS_DECLARE" in the "xxx_specifications.h" file, which is generated by the GUIX Studio. The fix is available in the latest release of GUIX Studio (v5.3.2.6) which is now in testing by Renesas.

Issue ID: 8044

Description

Customers cannot use the hardware accelerated JPEG drawing for their GUIX application because the GUIX Port driver (SF_EL_GX) fails occasionally in the JPEG draw function. Timeout occurs if the Synergy internal bus system was busy to finish the JPEG hardware rendering, this results in the JPEG rendering abort and causes critical screen corruption in a frame buffer. .

Workaround: Deselect "Raw Format" in the GUIX Studio setting to avoid the JPEG draw function called.

Issue ID: 8082

Description

Chained packet reception causes the code to get stuck in a while() loop in the receive interrupt of the Ethernet driver (sf_el_nx). This halts program execution.

Workaround: Use a packet pool large enough for the largest packet size you expect to receive for the end system. If the largest packet size is not known, set the packet size to the maximum Ethernet frame size of 1518 (based on IEEE 802.ac).



SF_EL_UX (USBX Port) Issue ID: 8037

Description

GUIX and SF_EL_GX (GUIX Port) do not work if ThreadX timer tick is set to 1 ms, if the hardware graphics accelerators (DRW and JPEG) are enabled.

Workaround: Use GUIX and 2DG or JPEG hardware accelerators with ThreadX tick time to 10ms.

Issue ID: 7576

Description

USB VBUS pin could be incorrectly controlled as active low even though the "VBUSEN pin Signal Logic" property of USBX Port HCD on sf_el_ux for USBxS component configures it as active high.

Workaround:

If your project uses USBX Port HCD on sf_el_ux for USBHS component:

Add X-ware > USBX > Host > Synergy Port > USBX Port HCD on sf_el_ux for USBFS and check the "VBUSEN pin Signal Logic" property. It should be configured to Active Low. Change the configuration to Active High. Save the configuration and delete the component. The configuration is not visible in the graphical view once the component is deleted, but the configuration will be recorded in the configuration.xml and is still valid for your project. To output logic high on the VBUSEN pin, both components need to configure the property to Active High in this version.

If your project uses USBX Port HCD on sf_el_ux for USBFS component:

Add X-ware > USBX > Host > Synergy Port > USBX Port HCD on sf_el_ux for USBHS and check the “VBUSEN pin Signal Logic" property. It should be configured to Active Low. Change the configuration to Active High. Save the configuration and delete the component.

If your project uses both USBX Port HCD on sf_el_ux for USBHS, and USBX Port HCD on sf_el_ux for USBFS components:

The same configuration is allowed to be set for both USBHS and USBFS in this version. There is no workaround if your target board needed a different VBUS control logic for USB controllers.

Applies to: S7G2, ASK-S5D9 MCU Groups

Issue ID: 7916

Description

Synergy Users who have a source license can tick a box in the SSP license file dialog that instructs e2 studio to generate plain text files for the encrypted files that the user has a source license for, when performing a project build.

However, even if the checkbox is ticked, e2 studio v5.3.1 is not generating the plain-text files when doing a project build.

Workaround: None - This issue will be resolved in the next release of e2 studio.

Impact - Only when an individual file is compiled, the decrypted file is written to the work-space in plain-text format.

Issue ID: 7665

Description

When using the Synergy configurator in e2 studio / SSC, if you rename a thread on the Threads tab and generate code, a new thread_entry.c file will be created with template content, and the old thread_entry.c file will remain in the project. If you have edited thread_entry.c, your changes are not moved to the new file. The old file remains in the project. It will not be called, however, and causes a build error if not removed from the project manually.

Workaround: Manually move your edits (if you have made any) from the old thread_entry.c file to the new thread_entry.c file, then manually delete the old thread_entry.c file from your project.



sf_el_ux_comms Issue ID: 4203

Description

The close API is not functional and should not be used. The USBX communications framework can only be configured once. There is no workaround at this time. The configuration parameters passed into open and the descriptors defined in sf_el_ux_comms_port.h are persistent and cannot be updated at runtime after open is called.

SF_EXTERNAL_IRQ Issue ID: 6407

Description

Mutex is not released while returning through error path. This can lead to functional issues in the framework when threadX APIs return error. Framework may not work as expected in such error cases since mutex is not released when threadX returns error.

In the normal case, when threadX APIs return success, framework functionality is as expected.

sf_power_profiles Issue ID: 6537

Description

When using sf_power_profiles, if the threadx mutex creation fails, the user may not be notified at the time of mutex creation, instead, the failure is indirectly notified during a subsequent call to the mutex_get function. Mutex creation failure notification will be available in the upcoming release.

Applies to: All MCU Groups when using ThreadX

sf_uart_comms Issue ID: 7669

Description

Bytes may be received out of order when using sf_uart_comms with DTC.

Workaround: Call sf_uart_comms read() while the receive pin is idle before any bytes arrive. If this is not possible in your application, do not use DTC for UART reception (using DTC for transmission is fine).

ThreadX Issue ID: 7882

Description

When configuring ThreadX source in the Configurator, the default value of the "Notify Callbacks" property does not match the text description that shows at the bottom of the ISDE.

Workaround: The default value should be determined by looking at the options for the "Notify Callbacks" property instead of the description text. Notify callbacks are disabled by default.



USBX Device CDC-ACM Issue ID: 7597

Description

USBX Device CDC-ACM Class may not respond the Device Descriptor data against GET CONFIGURATION REQUEST from a USB Host. While analyzing the issue, it responded to two consequent GET CONFIGURATION REQUEST from a Windows10 machine, but sporadically did not respond to the third request. If this happens, the USB Host cannot get the Descriptor data from a Synergy USB Device, and so the USB bus enumeration stops in the middle and the USB connection ends up in failure. This issue was observed when a Windows10 machine is used as a USB Host.

Workaround: Try to use Windows7 machine.

Issue ID: 8076

Description

USBX Device Class CDC-ACM fails on some Windows 10 machines.

Workaround: Set 'Miscellaneous' (0xEF) to 'Class code' property of USBX Device Configuration component for Windows 10 machines. Appropriate Device Descriptor configuration is going to be applied in the future SSP release.

Issue ID: 6389

Description

Module: ux_device_class_rndis (USBX Device RNDIS Class) / ux_network_driver (USBX Network Driver)

Public header files for USBX Device RNDIS Class and USBX Network Driver are not stored in the SSP public header file directory for X-wares \synergy\ssp\inc\framework\el, so a user application would not build with such USBX components. RNDIS and USBX Network Driver are in SSP, but they still are experimental modules and have been only partially tested.

Workaround: Add ux_device_class_rndis_src or ux_network_driver_src module to your project through Synergy Configurator Components tab. Use populated header files and move them to path \synergy\ssp\inc\framework\el\, or add the file include paths to the e2 studio project property settings (Cross ARM C Compiler - Includes - Include paths) to make them compile.

USBX Host Issue ID: 7811

Description

When "Auto Media Initialization" is set to Disabled for "FileX on USB Mass Storage," the FileX pointer is not available to upper layer modules. This can cause errors for upper layer function calls. Examples include FTP Server, HTTP Server, and TFTP Server for NetX and NetX Duo. These modules return an error during initialization.

Workaround: The user can handle errors in the upper layer modules by defining the error callbacks for those modules. For example, if the user was using FTP Server with the name "g_ftp_server0," then they could implement the g_ftp_server0_err_callback() function. The user could then choose to ignore the problem at start-up, and try to initialize the entire stack at a later point, when the USB device was enumerated.

GUIX Issue ID: 8000

Description

Developers will get a compiler warning [-Wimplicit-function-declaration] if they use either of the APIs listed below, in their application code because the function prototypes are missing in gx_api.h. gx_multi_line_text_button_text_id_set



gx_multi_line_text_button_text_set

gx_multi_line_text_view_char_index_set

Workaround: No special workaround is required for the functionality, but users can add the API prototype in the application code to resolve the compiler warning.

r_agt Issue ID: 8016

Description

The timer period of r_agt is limited to 2 seconds or less when the subclock or LOCO is used.

Workaround: If a period of more than 2 seconds is required and the subclock or LOCO is the clock source, configure the clock for a period of 2 seconds or less and wait for multiple callbacks until the total time elapsed reaches the desired time.

11. Additional Usage Notes for SSP v1.2.0 This section provides usage notes that are in addition the SSP User’s manual and have been provided to communicate additional information about the SSP modules not included in the SSP User’s manual and assist the developers in their usage.

Important usage notes that are considered as required reading for the module user have been identified by putting them in a box.

All SSP Modules Issue ID: 7243

Applications that have multiple instances of the same peripheral and channel in the configurator need to define the following macro in the preprocessor settings of your project, otherwise the project may not build correctly.

SSP_SUPPRESS_ISR_<instance_name>

where "instance_name" is the name of the additional device connected to the same channel.

For example, if three I2C devices g_i2c0, g_i2c1, and g_i2c2 are connected on a same channel, then define the following two macros in the project preprocessor settings.

#define SSP_SUPPRESS_ISR_g_i2c1

#define SSP_SUPPRESS_ISR_g_i2c2

MCU Implementation/Software Architecture Issue ID: 6399

If control structures are not all zeros, then, function calls other than open() may incorrectly determine that the module has already been opened. If this occurs, then the module may cause undefined behavior since it has not been properly initialized. Statically allocated control structures are zeroed-out as part of the C runtime initialization by the BSP. An example of when a control structure should be explicitly zeroed-out is if it was allocated off the stack.

Workaround:

a. User should follow SSP rules and ensure that the open() function is always called before the other APIs.

b. Ensure that control structures are all zeros before first use.

Issue ID: 6630

“Blinky” and “Blinky with Threadx” project templates cannot be used with C++ projects, as they will create an additional .c entry file during build process and builds using C compiler. Use BSP project templates to create C++ projects.



Module Name: C++ support

Crypto Library (r_sce) Issue ID: 5103

Description

Cryptographic functions are not thread safe.

Workaround: User code will need to use mutex resources around cryptographic function calls.

Issue ID: 7763

For S1 series and S3 series MCUs, when the TRNG (True Random Number Generator) module is not being used, a ring oscillator in TRNG stays active and an operation current may be generated resulting in more current consumption than expected. To eliminate this excess current usage the TRNG module must be started and stopped.

Workaround:

For S1 MCUs:

1. Set the MSTPCRC.MSTPC28 bit to 0 (Cancel the module-stop state) 2. Wait for 3 PCLK 3. And then, set the MSTPCRC.MSTPC28 bit to 1 (Enter the module-stop state) Refer to the hardware manual for the MSTPCRC register definitions. Alternatively, the following code sequence may be used to work-around the stated issue:

void R_BSP_WarmStart (bsp_warm_start_event_t event)

{

ssp_feature_t trng_ip;

switch (event)

{ case (BSP_WARM_START_PRE_C):

trng_ip.id = SSP_IP_TRNG;

trng_ip.channel = 0;

trng_ip.unit = 0;

R_BSP_ModuleStart(&trng_ip); /* Clears the MSTPCRC.MSTPC28 bit */

R_BSP_SoftwareDelay(100, BSP_DELAY_UNITS_MICROSECONDS); /* 3 cycles @32kHz clock rate */

R_BSP_ModuleStop(&trng_ip); /* Sets the MSTPCRC.MSTPC28 bit */

break;

case (BSP_WARM_START_POST_C):

break;

default:

break;

}

}

For MCUs in S3A7 Group:

1. Set the MSTPCRC.MSTPC31 bit to 0 (Cancel the module-stop state) 2. Wait for 3 PCLK 3. And then, set the MSTPCRC.MSTPC31 bit to 1 (Enter the module-stop state)



Refer the hardware manual for the MSTPCRC register definitions. Alternatively, the following code sequence may be used to work-around the stated issue


{

ssp_feature_t trng_ip;

switch (event)

{ case (BSP_WARM_START_PRE_C):

trng_ip.id = SSP_IP_SCE;

trng_ip.channel = 0;

trng_ip.unit = 0;

R_BSP_ModuleStart(&trng_ip); /* Clears the MSTPCRC.MSTPC31 bit */

R_BSP_SoftwareDelay(100, BSP_DELAY_UNITS_MICROSECONDS); /* 3 cycles @32kHz clock rate */

R_BSP_ModuleStop(&trng_ip); /* Sets the MSTPCRC.MSTPC31 bit */

break;

case (BSP_WARM_START_POST_C):

break;

default:

break;

}

}

BSP Issue ID: 7794

Description

When creating an SSP project and choosing "Custom User Board (Any Device)” as the board type, building the generated project will produce a build warning.

Workaround: The following is a workaround to remove the warning:

1. Edit the Synergy generated file: synergy_cfg/ssp_cfg/bsp/bsp_board_cfg.h adding the prototype for bsp_init such that it looks like this:

/* generated configuration header file - do not edit */ #ifndef BSP_BOARD_CFG_H_ #define BSP_BOARD_CFG_H_ void bsp_init(void * p_args); #endif /* BSP_BOARD_CFG_H_ */

2. Save the file.

3. Right click the file in the Project Explorer and select Properties.

4. Make the file Read-only by checking the Read-only attributes check box and click Apply.

Issue ID: 8017

Description

If the user provides a NULL pointer as a parameter to either R_SSP_VersionGet() or R_BSP_VersionGet(), the function does not check for NULL pointer and return an error code. Instead, the function will attempt to use the provided pointer, possibly corrupting memory.



Workaround: Ensure that the pointer provided to these function calls points to a valid memory area that has been allocated for the purpose of storing the returned version information.

QSPI Issue ID: 5515

Description

On the boards listed, the setup of the QSPI interface by the BSP does not set all unused bits to a known value. This will not break any functionality of QSPI and does not impact the QSPI module itself. It is mentioned only in the event that someone is writing code to use/test the QSPI that is on the development boards.

Workaround: None.

r_dac Issue ID: 7797

Description

The Synergy Configuration Tool for r_dac allows configuration of the Output Amplifier for S3A7 and S124 MCU Groups even though these MCUs do not have an output amplifier.

Workaround: None. The output amplifier setting should be ignored on these MCUs since it will have no effect.

sf_message Issue ID: 6379

Description

Messaging framework requires the size of message queue be set to 1 word (4 bytes).

Workaround:

The size of each message should be less than or equal to 1 word. Messaging Configurator on e2 studio sets the size of each message to 1 by default when the code is being generated.

sf_spi Issue ID: 7815

Description

When configuring SPI Framework Devices, follow these points.

1. For each SPI Framework Device, the corresponding SPI Driver associated to it should also be configured. For example, when configuring SPI framework device “g_sf_spi_device0”, add a SPI Driver like ”g_spi0” (r_sci_spi/r_rspi) and configure required lower level configurations like phase, polarity, bitrate and so forth, of the device linked to it. Each SPI Framework Device in the application should be configured like this.

2. When configuring the Framework Shared Bus, the channel number should be configured with the channel number to which the device has been connected; this channel will be used for the lower level configuration. The channel configured in the SPI Driver configuration underneath the Framework Device will be overridden by the channel configured in the bus.

3. The type of low level driver used by the SPI Framework should be configured correctly in the Framework Shared Bus configuration (that is, SCI SPI or RSPI).

4. Each SPI Framework Device should be configured separately for DTC/non-DTC use. If the user wishes to use DTC for all SPI Framework Devices then each device should have DTC filled in underneath the SPI Driver.



Issue ID: 6785

Description

sf_spi framework does not validate the configuration parameter for the shared bus instance. This could lead to undefined behavior in case of invalid configuration parameter.

Workaround: Manually validate the shared bus instance argument in ISDE.

sf_thread_monitor Issue ID: 7563

Description

Adding DHCP client to the RTOS thread would cause the delay APIs to take twice the time.

SF_TOUCH_PANEL_I2C Issue ID: 7795

Description

SX8654 Touch chip driver has delay in the I2C read and write functions. This impacts not only delay time but also possibly cause I2C communication stall in SX8654_i2c_write_followed_by_read if SCI I2C is used.

Workaround: Modify SX8654_i2c_read, SX8654_i2c_write, and SX8654_i2c_write_followed_by_read function in touch_panel_i2c_sx8654.c to remove line to call tx_thread_sleep. The file is in ssp_supplemental directory in SSP1.2.0. This workaround is only required if the delay was critical or if I2C stall was observed.


Issue ID: 7312

Description

User code will exhibit undefined behavior if the Reset() API is called without Open() API being called first. This is because the Reset() implementation does not check whether the framework is open or not.


sf_uart_comms Issue ID: 7723

Description

When a timeout occurs in sf_uart_comms, the lower layer driver operation in progress is not aborted. If write() is called and a timeout occurs, then write() is called again, the driver will return an "in use" error.

Workaround: Wait until the previous write completes before calling write() again.

Issue ID: 6272

Description

The write() API of sf_uart_comms returns SSP_ERR_INTERNAL when a timeout error occurs. In the future it will be changed to return SSP_ERR_TIMEOUT.



External IRQ Framework Issue ID: 7393

Description

External IRQ framework supports opening only one instance on a channel. Opening a second or more instances will lead to the first instance not receiving callbacks.

Workaround: Do not open an instance of the sf_external IRQ on same channel while another instance is already using it.

Synergy Software Configurator Issue ID: 7808

Description

A Synergy project in e2 studio using the IAR compiler will not build in headless mode unless the user sets up the license file and the IAR path in their workspace using the e2 studio IDE.

r_sci_spi Issue ID: 7600

Description

Current version of SSP does not support slave mode in the SCI SPI driver.

Workaround: The work around is to use the other SPI peripheral that supports slave mode, SPI (r_rspi) driver in the current SSP supports slave mode.

ux_network_driver (USBX Network Driver) Issue ID: 6192

Description

USBX Network Driver is currently included in the SSP package as an experimental module but yet tested so the functionality is not guaranteed.

Workaround: Not applicable.

Issue ID: 7826

Description

For both S7G2 and S5D9 MCU Groups, the system is configured to insert one wait state for SRAM access. At ICLK rates <= 120 MHz an SRAM wait state is not required, but still inserted resulting in slower SRAM access.

Workaround: A limited workaround is possible. If the system clock has been set, and it will not change, and meets the following criteria, the wait states could be set to zero. Changing the wait states and then increasing the ICLK frequency could result in unpredictable SRAM behavior.

If IClk <= 120 MHz, low speed RAM (SRAM0 and SRAM1) could be set for zero wait states.

R_SRAM->RAMPRCR = 0xF1; // Enable writes to protected registers

R_SRAM->RAMWTSC_b.SRAM0WTEN = 0; // No wait states for SRAM0

R_SRAM->RAMWTSC_b.SRAM1WTEN = 0; // No wait states for SRAM1

R_SRAM->RAMPRCR = 0xF0; // Disable writes to protected registers

If IClk <= 200 MHz, High speed RAM (SRAMHS) could be set for zero wait states.

R_SRAM->RAMPRCR = 0xF1; // Enable writes to protected registers



R_SRAM->RAMWTSC_b.SRAMHSWTEN = 0; // No wait states for SRAMHS

R_SRAM->RAMPRCR = 0xF0; // Disable writes to protected registers.


r_sdmmc Issue ID: 7870

Description

The user does not have access to both the CSD version and the SD Memory Card Specification Version of the SD card through the infoGet function.

Workaround: The application developer should determine the SD Memory Card Specification Version of the card using information from the manufacturer, or by debugging and setting a breakpoint in the internal function csd_save() in the file ssp\src\driver\r_sdmmc\sdmmc_driver.c and looking at the raw values obtained from the card.

Applies to: S3A7, S7G2, S5D9 MCU Groups

Issue ID: 7799

Description

The r_sdmmc driver does not close when the SDMMC card is removed.

Impact: On the S7G2 MCU, the r_sdmmc driver will be closed when there is a card access interrupt (upon removing the card). On all other MCUs that have the sdmmc peripheral, the hardware does not support card access interrupt, due to which the r_sdmmc driver will not be closed if the card is removed.

NetX Applications Issue ID: 5721

Description

NetX HTTP Client currently only supports HTTP version 1.0.

SF_BLOCK_MEDIA_SDMMC Issue ID: 6673

Description

Return values from threadX API calls are not checked in the framework. This can lead to functional issues in the framework when threadX APIs return error. Framework may not work as expected in such error cases since errors are not handled.

Workaround: There is no work around. In the normal case when threadX APIs return success framework functionality will be as expected.

sf_el_gx (GUIX Port) Issue ID: 8061

Description

Properties "Name of Display Driver Run-time Configuration", "Name of Frame Buffer A" and "Name of Frame Buffer B" require to be amended by users manually. Those might be inherited from the dependent module 'Display Driver on r_glcd' in the future release.

Workaround: Amend properties above appropriately. Refer to the SSP User's Manual 'Table SF_EL_GX configuration' for more detail of configuration properties.



Issue ID: 7382

Description

Open and Close APIs do not check for the return codes of ThreadX API calls. This could lead to undefined behavior in case of the threadx API failure(s)

Framework APIs do not check for NULL pointer arguments. This causes undefined behavior in case where pointer arguments are NULL.

sf_i2c Issue ID: 7813

Description

When configuring I2C Framework Devices, follow these instructions:

1. All I2C Framework Devices on the same bus must use the same lower level configuration settings (that is, I2C driver) except for the slave address and addressing mode. The framework will use the configuration of the first device that it opens in the application to configure the bus. This means that all I2C Framework Devices on the same bus must have the same lower level configuration settings (except for the slave address and addressing mode). If different configurations are used, then proper operation cannot be guaranteed. I2C Framework code internally switches the devices by switching the slave address using the slaveAddressSet() function.

2. In order to use the DTC, the first device that the application opens should be configured with DTC. Figuring out which device is opened first can be difficult in a threaded application, so it is recommended to configure all the lower level devices with DTC or non-DTC for ease of use. By default, all the drivers will be added with DTC.

3. The type of low level driver used by the I2C Framework should be configured correctly in the Framework Shared Bus configuration (that is, SCI I2C or RIIC).

4. When configuring the Framework Shared Bus, the channel number should be configured with the channel number to which the device has been connected. This channel will be used for the lower level configuration. The channel configured in the I2C Driver, underneath the I2C Framework Device, will be overridden by the channel configured in the bus.

5. For each I2C Framework Device that is created, an I2C Driver will also have to be created. Even though the channel configured in the I2C Driver will be ignored by the I2C Framework (as described in Step 4), it can cause build issues. Users will likely use the same channel number in the I2C Driver as the I2C Framework Shared Bus. When multiple I2C Driver instances have the same channel number, a build error will occur. To fix this, the user should add a preprocessor macro for each I2C Framework Device instance on the same bus, except for one. The macro names will be based upon the I2C Driver instance names underneath each I2C Framework Device.

An example would be if there are three I2C Driver instances named g_i2c0, g_i2c1, and g_i2c2. Each I2C Driver is underneath an associated I2C Framework Device. If the I2C Drivers are all configured to use the same channel, then define the following two macros in the project preprocessor settings to avoid build errors.

#define SSP_SUPPRESS_ISR_g_i2c1 #define SSP_SUPPRESS_ISR_g_i2c2

A macro for g_i2c0 is not created because one I2C Driver for the channel needs to exist.

SF_EL_UX (USBX port) Issue ID: 7998

Description

The module has been tested and verified with –O2 optimization in GCC. Using -O3 optimization for the USB MSC Host is not recommended since there are known unresolved issues when –O3 is used.



Issue ID: 8012

Description

All SSP modules are tested using the default configuration settings in the e2 studio. Operation of the modules with other configurations are not guaranteed.

Workaround: None

Issue ID: 7687

Description

USBX HID Host API to get mouse events or keyboard events may not work and may return with 'no data' even though actual HID reports were received from a HID device. This issue occurs if the USBX failed to allocate enough memory.

Workaround: Specify enough memory for the USBX (set the value to "USBX Pool Memory Size" in the Properties of "USBX on ux" component)

Here are few examples of the USBX Pool Memory Size setting (minimum). The values are obtained through measurements on a Synergy target board.

HID Mouse:

• 35 KB if USBX Host Class HID Pre-built library is used • 28 KB if USBX Host Class HID Source module is used HID Keyboard:

• 43 KB if USBX Host Class HID Pre-built library is used • 33 KB if USBX Host Class HID Source module is used Following fixed configurations are used for USBX Host Class HID Pre-built library.

• UX_HOST_CLASS_HID_DECOMPRESSION_BUFFER:4096 (in bytes, default value) • UX_HOST_CLASS_HID_USAGE:1024 (in WORDs, default value) Following configurations are used for USBX Host Class HID Source module.

• UX_HOST_CLASS_HID_DECOMPRESSION_BUFFER:128 (in bytes) • UX_HOST_CLASS_HID_USAGE:256 (in words).

Issue ID: 8055

Description

FIFO size for Bulk OUT transfer can be configured by the user from default 512 bytes to a maximum of 2048 bytes. Even after configuring to maximum FIFO size the code uses 512 bytes for the write operation (OUT) without utilizing the complete configured FIFO size.

This impacts the USB data throughput for the write operation for larger transfer size and the number of transfer descriptors created in USBX exceeds the maximum limit (UX_MAX_TD).

Workaround: Increase the Maximum TDs value in the property window for USBX Source in Synergy configurator so that we would not exceed the maximum limit of transfer descriptor.

sf_power_profiles Issue ID: 6189

Description

The sf_power_profiles framework is a few bytes larger than necessary due to code that checks return value of the underlying driver r_lpm. But the underlying driver will not return an error in this case.




Description

1. In function SF_SPI_Read, when the parameters length and bit_width are set to invalid values, the function returns SSP_ERR_ASSERTION instead of SSP_ERR_UNDEF.

2. In function SF_SPI_Read, when the parameter dev_state is set to SF_SPI_DEV_STATE_CLOSED, the function returns SSP_ERR_NOT_OPEN instead of SSP_ERR_UNDEF.

Synergy Software Configurator Issue ID: 7817

Description

After upgrading a project for MCUs of S3A7 Group from SSP v1.1.(z) to SSP v1.2.0 using the auto-upgrade support in e2 studio, there may be a problem with pins P012, P013, and P015 in that the Pin Configuration settings for these pins may be blank / non-existent.

Workaround: Recreate your project in SSP v1.2.0 instead of upgrading it from v1.1.z.

Issue ID: 7401

Description

If an SSP v1.1.x .pincfg file enables both _A and _B pin options for a peripheral (which in itself is an invalid combination that is allowed by the SSP v1.1.z Pin Configurator), but then does not assign any pins, the Renesas pin configuration migration tool in e2 studio / SSC creates an invalid SSP v1.2.0 .pincfg file, which will not load in the Pin Configurator.

Workaround: Fix the invalid SSP v1.1.x .pincfg file in the original SSP v1.1.z project such that it does not enable both _A and _B pin options for a peripheral, and assigns the appropriate pins. Then, upgrade the project to SSP v1.2.0. In this case, the Renesas pin configuration migration tool creates a valid SSP v1.2.0 .pinfcg file, which properly loads in the Pin Configurator.

Issue ID: 7865

Description

If a module instance is deleted from a stack on the Threads tab in e2 studio / SSC (for example, a Transfer Driver on DTC), and there are still one or more instances of that same module remaining in the stack, then the configuration.xml file is not marked as ‘changed’.

The configuration.xml file is only marked as ‘changed’ (by placing an asterisk in front of the file name in the e2 studio / SSC editor) if deletion of a module instance results in no remaining instances of that module in the stack.

Workaround: None.

Issue ID: 8047

Description

Using the e2 studio 'cut and paste' feature to move a configured module stack from one thread to another thread (in the same project) on the Threads tab does not work if you cut, and then paste in the project configuration. Users will experience build errors because the selected SSP modules are removed from the project in the 'cut' operation', but are not added again in the 'paste' operation

Workaround: Copy the module stack, paste it to the new location, and then delete it from the original location.



Issue ID: 5987

Description

The maximum operating frequency is defined in the S124 Group MCU manual for ICLK, PCLKB and PCLKD, which is shown below:

ICLK: 32 MHz

PCLKB: 32 MHz

PCLKD: 64 MHz

Despite this, it is possible, using the Clocks Configuration window, to specify a combination of HOCO frequency and clock dividers that result in one or more of these clocks exceeding their recommended maximum operating frequency.

Impact - Operating with one or more clocks that exceed their recommended maximum could result in unpredictable behavior or complete non operation of all hardware components (including the MCU) that use the clock.

Issue ID: 7880

Description

Certain C library functions that require thread local storage, or synchronization with other threads, will not be thread-safe. For IAR, the following objects will not have the system locks implemented, and therefore will not protect against reentrancy:

1. The heap, that is, the usage of malloc, free, realloc, and calloc.

2. The file system (only available in the full library configuration), but not the file streams themselves. The file system is updated by opening or closing a stream, that is, the usage of fopen, fclose, fdopen, fflush, and freopen.

3. The signal system, that is, the usage of signal.

4. The tempfile system, that is, the usage of tmpnam.

5. Initialization of static function objects.

For IAR the following objects require TLS, and since only single instance of TLS is supported, use across multiple threads is not guaranteed to work correctly:

1. Error functions, that is, the usage of errno and strerror.

2. Locale functions, that is, the usage of localeconv and setlocale.

3. Time functions, that is, the usage of asctime, localtime, gmtime, and mktime.

4. Multibyte functions, that is, the usage of mbrlen, mbrtowc, mbsrtowc, mbtowc, wcrtomb, wcsrtomb, and wctomb.

5. Rand functions, that is, the usage of rand and srand etc. functions, i.e. the usage of atexit and strtok.

6. C++ exception engine.

Workaround: The user can manually implement the required functionality for the toolchain they are using. For example, the user could follow the instructions on the page below to fix this issue for IAR.

http://supp.iar.com/FilesPublic/UPDINFO/005691/arm/doc/infocenter/DLIBThreadSupport.html

Issue ID: 6756

Description

The IAR C/C++ library requires thread local storage (TLS) for certain objects. Even in non-threaded applications, one instance of this storage is required for the "main thread". The main thread storage is allocated in a separate memory section named __DLIB_PERTHREAD. This section is not created by default for a Synergy project and is not initialized during start-up. If this section is not initialized it will cause runtime failures when the library functions are called.

These library objects need TLS:

• Error functions, i.e. the usage of errno and strerror

• Locale functions, i.e. the usage of localeconv and setlocale




• Time functions, i.e. the usage of asctime, localtime, gmtime, and mktime

• Multibyte functions, i.e. the usage of mbrlen, mbrtowc, mbsrtowc, mbtowc, wcrtomb, wcsrtomb, and wctomb

• Rand functions, i.e. the usage of rand and srand. etc functions, i.e. the usage of atexit and strtok

• Etc. functions, i.e. the usage of atexit and strtok

• C++ exception engine.

Follow the link below for more information: http://supp.iar.com/FilesPublic/UPDINFO/005691/arm/doc/infocenter/DLIBThreadSupport.html

Workaround:

1. Add the following lines to the linker script initialize by copy with packing = none { section __DLIB_PERTHREAD };

2. Override BSP warm start function to perform the IAR section initialization

For example:


{ if (BSP_WARM_START_PRE_C == event)

{ /* C runtime environment has not been setup so you cannot use globals. System clocks and pins are not setup. */

__iar_data_init3(); }

else if (BSP_WARM_START_POST_C == event)

{

/* C runtime environment, system clocks, and pins are all setup. */

}

else

{

/* Unhandled case. */

}

}

ux_host_class_storage (USBX Host Class Mass Storage) Issue ID: 7801

Description

Pre-built library for USBX Host Mass Storage was built with the build-time options below as described.

- UX_HOST_CLASS_STORAGE_MEMORY_BUFFER_SIZE: 8192 (Byte).

- UX_THREAD_STACK_SIZE: 2048 (Byte).

The default value of these options for USBX Host Mass Storage Source module are 1024, 1024 respectively so users need to be aware that the Pre-built library consumes extra 8K bytes (in the USBX memory pool) and behaves different from the Source module unless the Source module is built with same configurations above.

Workaround: Use USBX Host MSC Source module instead of the pre-built library if the build-time options applied to the pre-built library settings do not match to your system.




Issue ID: 7802

Description

The information was incorrect in the SSP User’s Manual, Chapter ‘User Guides’, Section ‘Express Logic USBX’ - ‘Express Logic USBX Memory Requirements’ - Table 20 ‘Memory (RAM) requirements for USBX memory pool’. Correct information is given below.

The memory size of USBX Host Mass Storage (ux_host_class_storage) for non-S1 parts:

• Pre-built library: 47KB

• Source: 37KB + UX_HOST_CLASS_STORAGE_MEMORY_BUFFER_SIZE + UX_HOST_CLASS_STORAGE_THREAD_STACK_SIZE

The memory size is changed because the size of FX_MEDIA structure (FileX Control Block) is increased in FileX 5.4. The size change impacts to the memory size of USBX Host Class Mass Storage because it is allocated in the USBX memory pool. The equation for the USBX Host Class Storage Source is also updated. Previously the memory size for UX_HOST_CLASS_STORAGE_THREAD_STACK_SIZE (configured as 1KB) was included in '36KB' presented in the previous revision of SSP User's Manual.

Note that the value above was tested with following USB Flash Drives and USBX configurations.

• USB Flash Drive under test (1): SanDisk Cruzer Glide CZ60 32GB

• USB Flash Drive under test (2): SanDisk Fit CZ33 8GB

• ‘USBX Pool Memory Size’ property of ‘USBX on ux’ component: 48128 (for the Pre-built library) or 39936 (for the Source)

• All the Properties of ‘USBX Host Class Mass Storage Source’ component: Default settings (only applicable for the Source)

Workaround: Set the memory size described above or more than the number to ‘USBX Pool Memory Size’ property of ‘USBX on ux’ component when using USBX Host Class Storage.

Issue ID: 7496

Description

When importing a Synergy project into e2 studio that was exported using the e2 studio Synergy Project Exporter, the SSP components are not present immediately after import. Therefore, e2 studio may show warnings in the Problems view regarding Invalid include paths.

Workaround: Clicking the "Generate Project Content" button re-generates the SSP components and the associated directories, and the include paths become valid.

Issue ID: 5627

Description

When building a project using GCC, it is possible that not all of the requested heap area is made available to the application. As part of a fix for a prior issue with GCC, which would allocate areas outside of the heap, Renesas now provides its own _sbrk() function for heap allocation. The library version of malloc() in use, requires a minimum 4 K pagesize. As a result, a request for memory through malloc() may fail even though there is sufficient space available for the request.

Workaround: If malloc() requests are failing and indicating that no memory is available, then it is necessary to increase the heap size.

Issue ID: 6144

Description

Warnings or errors may occur when parameter checking is disabled.

Workaround: None - Do not disable parameter checking.



Issue ID: 8149

Description

The documentation contents (doc folder) from the SSP 1.2.0 pack has been removed, because of this the generation of documentation (HTML user manual and doxygen files) through e2studio is not supported in this release.

Synergy Tools (GUIX Studio) Issue ID: 8085

Description

Users cannot show a pixelmap image in a GUIX Drop List automatically.

Workaround: To show a pixelmap in a GUIX drop list, set a pixelmap by gx_drop_list_pixelmap_set() after the status of the drop list became to GX_STATUS_VISIBLE.

ux_device_class_storage (USBX Device Mass Storage Class) Issue ID: 7410

Description

One of the configuration properties in the USBX Interface Configuration Mass Storage Class component has a typo and is explained incorrectly.

Incorrect: "Interface Number of Communications Class interface"

Correct: "Interface Number of Bulk-Only Data Interface"

Workaround: This is not a functional defect, so no any workaround required.

ux_host_class_prolific (USBX Host Prolific Class) Issue ID: 6470

Description

USBX Host Class Prolific is currently included in the SSP package as an experimental module. It has been partially tested, so the functionality is not guaranteed.

r_sdmmc Issue ID: 6690

Description

The documented error return may not always match the actual error return value, in some cases.

The error return as described in the function header may not always match the actual error return value, in some cases.

The bus_width member of sdmmc_hw_t (nested sturcture in sdmmc_cfg_t) is not strictly used as shown in the enum sdmmc_hw_t. The value in bus_width may not match the enums in sdmmc_hw_t.

Workaround:

The API function IoIntEnable does not check p_ctrl for NULL. The user needs to verify that the p_ctrl parameter is not NULL if directly calling IoIntEnable either by a adding check in code or by code audit.

Applies to: All MCU Groups



Issue ID: 6692

Description

If SDMMC driver is opened with ACCESS IRQ disabled, the driver open fails without releasing the hardware lock. This results in the SDMMC peripheral being locked out for any further operation.

Workaround: Manually inspect the ISDE configurator to verify that the ACCESS interrupt is enabled for the driver.


Description

User’s Manual for SSP v1.2.0 has incorrect information regarding API return codes as follows:

1. For input to bit_width as valid values (for example, SPI_BIT_WIDTH_8_BITS, SPI_BIT_WIDTH_16_BITS), SF_SPI_Write() and SF_SPI_WriteRead() functions return SSP_ERR_ASSERTION instead of RETURN_SSP_NOT_SUCCESS .

2. For input to bit_width as valid values (for example, SPI_BIT_WIDTH_8_BITS, SPI_BIT_WIDTH_16_BISWIOT-6786 TS), SF_SPI_Read() function returns SSP_ERR_ASSERTION instead of SSP_ERR_UNDEF.

3. For input to dev_state as valid value (for example, SF_SPI_DEV_STATE_CLOSED), SF_SPI_Write() and SF_SPI_WriteRead() functions return SSP_ERR_NOT_OPEN instead of RETURN_SSP_NOT_SUCCESS.

4. For input to dev_state as valid value (for example, SF_SPI_DEV_STATE_CLOSED), SF_SPI_Read() functions return SSP_ERR_NOT_OPEN instead of SSP_ERR_UNDEF.

Issue ID: 6787

Description

User’s Manual for SSP v1.2.0 has incorrect information regarding API return codes.

1. For input to p_dest as NULL, SF_SPI_Read() and SF_SPI_WriteRead() functions return SSP_ERR_ASSERTION instead of SSP_ERR_INVALID_POINTER.

2. For input to p_src as NULL, SF_SPI_WriteRead() and SF_SPI_Write() functions return SSP_ERR_ASSERTION instead of SSP_ERR_INVALID_POINTER.

3. For input to L_p_ctrl, L_p_cfg as NULL, SF_SPI_Close(), SF_SPI_WriteRead(), SF_SPI_Write(), SF_SPI_Read(), SF_SPI_Open(), SF_SPI_Lock(), SF_SPI_Unlock() functions return SSP_ERR_ASSERTION instead of SSP_ERR_INVALID_POINTER.

4. For input to "p_lower_lvl_cfg" and "p_bus" as NULL, SF_SPI_Open() function returns SSP_ERR_ASSERTION instead of SSP_ERR_INVALID_POINTER.

5. When the driver is not opened successfully, SF_SPI_Close() function returns SSP_ERR_NOT_OPEN instead of SSP_ERR_IN_USE.

r_qspi Issue ID: 6708

Description

The p_device_address parameter of the read, pageProgram, erase, and sectorErase API functions is not checked to be within the QSPI peripheral address range. In some cases, no error may be returned. The application code should verify that this address is correctly within the QSPI range of addresses.




SF_EXTERNAL_IRQ Issue ID: 7517

Description

The valid channel option in the external interrupt usage notes is listed as 0-5 for S3A7. However, it should be 0-15. Channels 6-15 can be used on MCU devices in the S3A7 Group.

Synergy Tools Issue ID: 7596

Description

The ADSSTR06 register is not available in the IO Registers pane when debugging.

Workaround: The user can add an expression to the Expressions pane to monitor the value of the ADSSTR06 register. For example, "*(uint8_t *)0x4005c0e6" could be used for ADC120.ADSSTR06. Refer to the hardware manual for the proper address.

Certain C library functions that require thread local storage, or synchronization with other threads, will not be thread safe.

Issue ID: 7880

For IAR the following objects will not have the system locks implemented and therefore will not protect against reentrancy:

• The heap, i.e.the usage of malloc, free, realloc, and calloc. • The file system (only available in the full library configuration), but not the file streams themselves. The file system

is updated by opening or closing a stream, i.e. the usage of fopen, fclose, fdopen, fflush, and freopen. • The signal system, i.e. the usage of signal. • The tempfile system, i.e. the usage of tmpnam. • Initialization of static function objects.

For IAR the following objects require TLS, and since only 1 TLS is supported, use across multiple threads is not guaranteed to work correctly:

• Error functions, i.e. the usage of errno and strerror. • Locale functions, i.e. the usage of localeconv and setlocale. • Time functions, i.e. the usage of asctime, localtime, gmtime, and mktime. • Multibyte functions, i.e. the usage of mbrlen, mbrtowc, mbsrtowc, mbtowc, wcrtomb, wcsrtomb, and wctomb. • Rand functions, i.e. the usage of rand and srand. • Eetc functions, i.e. the usage of atexit and strtok. • C++ exception engine. Workaround: The user can manually implement the required functionality for the toolchain they are using. For example, the user could follow the instructions on the page below to fix this issue for IAR.


sf_el_nx_comms Issue ID: 7228

Description

In SF_EL_NX_COMMS_Write(), SF_EL_NX_COMMS_Read() functions when the arguments are NULL or number of bytes to read or write is zero, the API will return "SSP_ERR_ASSERTION" but the user manual says that the API will return "SSP_ERR_INTERNAL".




Issue ID: 7411

Description

In the Thread Stacks pane under the Threads tab, sf_el_nx_comms communication framework component comes up with two NetX port components. Users should use only one NetX component. It is recommended to use NetX port ETHER on sf_el_nx (on the left bottom in the figure below), instead of adding it to the NetX port (on the right side in the figure).

Workaround: Add only one NetX Port ETHER on sf_el_nx component under NetX on nx component.

sf_el_ux_comms Issue ID: 7860

Description

USBX interface with DTC is not supported in this release.

Workaround: Use the CPU copy, instead of DTC for USBX.

Issue ID: 7921

Description

The sf_el_ux_comms module does not migrate correctly from 1.2.0-b.1 (or previous releases) to 1.2.0. After migrating a project with sf_el_ux-comms, the sf_el_ux_comms stack is removed from the thread it is used in. Workaround: Before migrating from 1.2.0-b.1, go to the Components tab of the Synergy Configuration tool. Check Framework Services > all > sf_el_ux_comms_v2. Migrate to 1.2.0 by switching the SSP version on the BSP tab. After migration, uncheck sf_el_ux_comms on the Components tab.

NetX Application bundle modules (common) Issue ID: 7991

Module: NetX TFTP Server, NetX Duo TFTP Server, NetX and NetX Duo DHCP Server

The following are presented in Configuration properties, but these configurations are redundant, and are not used by the module. There is a description about these configurations in the Express Logic NetX/NetX Duo TFTP Server User Guide, but those are inaccurate and are expected to be removed in future release.

The redundant configurations are:

1. “TFTP Server activity timeout enable”

2. Server activity time out (ticks).

3. ACK or data retransmission interval (ticks).

4. Size of array for holding available IP addresses.

5. Server option list (required - use space for separation)

This feature is planned to be deprecated in future SSP release.

Modules Module: NetX TFTP Server, NetX Duo TFTP Server

Description

“Server activity time out (ticks)” property is presented in the configuration properties but it is not used by the module.

The description about the configuration in the Express Logic NetX/NetX Duo TFTP Server User Guide is incorrect. It is for NX_TFTP_SERVER_RETRANSMIT_TIMEOUT (and also relevant to NX_TFTP_SERVER_MAX_RETRIES) but not for NX_TFTP_SERVER_ACTIVITY_TIMEOUT. The property is to be obsoleted and Express Logic User Guide to be updated accordingly.

Workaround: Not required. It is to be obsoleted in the future SSP release.



Description

Reword NX_TFTP_SERVER_ACTIVITY_TIMEOUT to NX_TFTP_SERVER_RETRANSMIT_TIMEOUT when reading the Express Logic NetX/NetX Duo TFTP Server User Guide.

“ACK or data retransmission interval (ticks)” property is presented in the configuration properties but it is not used by the module.


Module: NetX BSD, NetX Duo BSD

Description

User projects would not be built without defining _POSIX_SOURCE.

Workaround: Define _POSIX_SOURCE in the compiler preprocessor setting.

Module: NetX Duo NAT

Description

“timeout for translation entry (ticks)” property is set to 240 ticks by default but it is too short as the timeout value. 24000 ticks match to the default value given by Express Logic (24000 ticks is 4 minutes if OS system tick time is 10ms).

Workaround: Set the property to appropriate value.

Module: NetX and NetX Duo DHCP Server

Description

“Size of array for holding available IP addresses” property is presented in the configuration properties but it is not used by the module. There is a description about the configuration in the Express Logic NetX/NetX Duo DHCP Server User Guide but it is incorrect so to be obsoleted accordingly.


Description

“Server option list (required - use space for separation)” property is presented in the configuration properties but not configurable for the module.


Module: NetX Duo FTP Server

Description

“Name of Login Function” or “Name of Logout Function” callbacks are not permitted to set NULL in this version, otherwise users will have a compile error in the auto-generated code.

Workaround: Define the callback functions in user application code even if no any callback processing required. If there is nothing to do in the callback function, create a callback function which simply returns NX_SUCCESS.

r_cgc Issue ID: 6479

Description

The systemClockSet function documentation is not correct.



The error return will be SSP_ERR_NOT_STABILIZED is a clock is started but not yet stabilized, instead of SSP_ERR_STABILIZED.

Issue ID: 8164

Description

The CGC properties do not offer the necessary functionality to get a callback when an Oscillation Stop Detect event occurs. This functionality must be manually added by the user.

Workaround: Add the following code to the user application.

/* Prototype the callback function */

void my_osc_stop_callback(cgc_callback_args_t * p_args);

void hal_entry(void)

{

/* Enable the Osc Stop Detect functionality */

g_cgc.p_api->oscStopDetect( my_osc_stop_callback, true );

/* Osc Stop Detect is an NMI interrupt. Enable the NMI in ICU */

R_ICU->NMIER_b.OSTEN = 1;

}

/* Create a CGC Osc Stop Detect callback.

void my_osc_stop_callback(cgc_callback_args_t * p_args)

{

/* Do Oscillation Stop Detect Processing */

}


Description

When transferring a set of data, a gap in the clock signal between each set of data transfer is shown. No functional impact with regard to this is observed.

r_riic Issue ID: 7995

Description

In IIC and SCI I2C with DTC, the maximum possible data transfer size in a single transaction is 64Kbytes.

Workaround:

Transfer using more than 64KBytes data size should be split into multiple transactions. This restriction does not apply to CPU transfer mode.




Description

Driver open status is not checked in APIs. This can lead to functional issues in the driver when RSPI APIs are called without opening a module. Driver will not work as expected in such error cases.

Workaround: No RSPI APIs should be called before calling Open API.

In the normal case when module is opened before calling other APIs, driver behavior will be as expected.


Description

For PCLKA clock frequencies from 32 MHz to 120 MHz range, SPI baud rate supported are minimum of 3.20 Mbps and maximum of 30.0 Mbps. Refer MCU user manual for all the baud rates supported with BRDV value zero.

Issue ID: 6714

Description

In all R_SPI public interfaces, User manual says that if a NULL pointer is passed in argument the expected return value is "SSP_INVALID_ARGUMENT" while actual return value is "SSP_ERR_ASSERTION."

r_ctsu Issue ID: 6929

Description

Auto-calibration, Auto-scan and Auto-drift compensation features are not available in the r_ctsu driver in this release.

Issue ID: 6928

Description

If the R_CTSU_Read is called while the driver is in an uninitialized state, then the documented return code is SSP_SUCCESS, but the actual return code will be SSP_ERR_NOT_OPEN. When calling R_CTSU_Read while the driver is uninitialized, the application should expect a return code of SSP_ERR_NOT_OPEN.

The R_CTSU_Read() function is not sufficiently tested with the CTSU_READ_FILTERED_REF_ICO_VALUES_SEL and CTSU_READ_FILTERED_REF_ICO_VALUES_ALL options

Issue ID: 6927

Description

R_CTSU_Update_Parameters() returns following error codes

a. SSP_ERR_NOT_OPEN when mode is set to CTSU_MODE_UNCONFIGURED

b. SSP_ERR_IN_USE when Measurement Status Counter set to non-zero value or CTSU Data Transfer Status flag is set.

c. SSP_ERR_CTSU_RC_OVERFLOW when CTSUROVF flag is set

d. SSP_ERR_CTSU_SC_OVERFLOW when CTSUSOVF flag is set

e. SSP_ERR_CTSU_ICOMP when TSCAP Voltage Error Monitor flag is set

In cases where the returned error code is not described in the function header, refer to the description of the return code in ssp_common_api.h

Issue ID: 8032



Description

The CTSU driver has been partially tested on S5D9 Group MCU devices. However it has been completely tested on S7G2 Group MCU devices which has the same hardware IP as S5D9 Group MCUs.

r_flash_lp Issue ID: 8098

Description

When using the Flash LP module, the read() function allows a request to read areas outside the Flash area. If the address provided to the read() function is between the end of code flash and the start of Data Flash, it will attempt read the requested address and return its contents. If the address provided is part of a Reserved memory area, the Read request may generate a System Hard Fault Exception.

Workaround: Ensure that the address range requested of read() is within the range of code or Data Flash.

Applies to: S124 and S3A7 MCU Groups

Block Media Interface for SD Multi Media Card Issue ID: 7867

Description

Initialization of FileX on Block Media fails if an SD Card is not inserted. The application code needs to verify that a card is inserted before calling the initialization function.

Workaround:

Requires SD card to be inserted before FileX initialization.

r_ssi Issue ID: 6825

Description

On S5D9 MCUs, due to hardware limitations the I2S interface does not allow for turning of the WS continue mode. Due to this the word select line is continuously output from the time the driver is opened until the driver is closed. If WS continue mode is off in the Synergy Configuration tool, the driver ignores this setting and turns WS continue mode on.

Workaround: The workaround is built into the driver. There is no way to turn off WS continue mode on S5D9 MCUs

Applies to: S5D9 MCU Group

sf_console Issue ID: 7607

Description

The sf_console internal timeout is fixed to 5 ticks. This timeout is used for echo and menu prints, and may cause menu or echo prints to be cut off. This timeout may not be long enough for slower UART speeds.

Workaround: When using sf_console with UART, increase the baud rate if menu printouts are cut off.

sf_el_nx (NetX Port) Issue ID: 7513



Description

Current sf_el_nx NetX port driver is set to use RMMI interface, which is for a Micrel Ethernet PHY chip mounted on Renesas kits, but does not support other PHY chips or the MMI interface. Customers need to define their own Ethernet PHY chip driver if they use a different PHY chip than the one mounted on Renesas kits, or use a PHY chip with MII interface.

Workaround: Support for additional Ethernet PHY chip drivers in SSP is not planned, so users are required to create their own PHY chip driver. To do that, you can utilize ether_phy.c and ether_phy.h under /ssp/src/framework/sf_el_nx/phy/ as a template and modify it for your Ethernet PHY chip. Source files under sf_el_nx (NetX Port) are in unencrypted text format, so they can be copied to other directories, such as /src/ directory and exclude original ether_phy.c and ether_phy.h from building to avoid 'multiple definition' compile-error.

Notes: • ether_phy.c and ether_phy.h under /ssp/src/framework/sf_el_nx/phy/ will be overwritten by tool when

building your project so you should copy the files before your editing. • To exclude files from building, right-click on the files and select 'Exclude from build..' (for e2 studio).



12. Complete List of Modules Available in this SSP Release Module Name SSP Feature Supported MCU Groups

Driver bsp Board Support Package S124,S3A7,S5D9,S7G2 r_adc A/D Converter S124,S3A7,S5D9,S7G2

r_agt Asynchronous General Purpose Timer S124,S3A7,S5D9,S7G2

r_cac Clock Frequency Accuracy Measurement Circuit S124,S3A7,S5D9,S7G2

r_can Controller Area Network S124,S3A7,S5D9,S7G2 r_cgc Clock Generation Circuit S124,S3A7,S5D9,S7G2

r_crc Cyclic Redundancy Check calculator S124,S3A7,S5D9,S7G2

r_ctsu Capacitive Touch Sensing Unit S124,S3A7,S5D9,S7G2 r_dac Digital to Analog Converter S124,S3A7,S5D9,S7G2 r_dmac Direct Memory Access Controller S3A7,S5D9,S7G2 r_doc Data Operation Circuit S124,S3A7,S5D9,S7G2 r_dtc Data Transfer Controller S124,S3A7,S5D9,S7G2 r_elc Event Link Controller S124,S3A7,S5D9,S7G2 r_flash_hp Flash Memory, High Performance S5D9,S7G2 r_flash_lp Flash Memory, Low Power S124,S3A7

r_fmi Factory Microcontroller Information S124,S3A7,S5D9,S7G2

r_glcd Graphics LCD Controller S5D9,S7G2 r_gpt General Purpose Timer S124,S3A7,S5D9,S7G2 r_gpt_input_capture General Input Capture S124,S3A7,S5D9,S7G2 r_icu Interrupt Controller Unit S124,S3A7,S5D9,S7G2 r_ioport General Purpose I/O Ports S124,S3A7,S5D9,S7G2 r_iwdt Independent Watchdog Timer S124,S3A7,S5D9,S7G2 r_jpeg_decode JPEG Decode S5D9,S7G2 r_kint Keyboard Interrupt Interface S124,S3A7,S5D9,S7G2 r_lpm Low Power Mode S124,S3A7,S7G2 r_lpmv2_s124 Low Power Mode V2 for S124 S124 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_lvd Low Voltage Detection Driver S124,S3A7,S5D9,S7G2 r_pdc Parallel Data Capture Unit S5D9,S7G2 r_qspi Quad Serial Peripheral Interface S3A7,S5D9,S7G2 r_riic IIC S124,S3A7,S5D9,S7G2 r_riic_slave IIC Slave S124,S3A7,S5D9,S7G2 r_rspi Serial Peripheral Interface S124,S3A7,S5D9,S7G2 r_rtc Real-time Clock S124,S3A7,S5D9,S7G2

r_sce

Secure Crypto Engine (TRNG, AES, RSA, TDES, HASH, DSA, ARC4) S124,S3A7,S5D9,S7G2



r_sci_i2c Serial Communication Interface I2C S124,S3A7,S5D9,S7G2

r_sci_spi Serial Communication Interface SPI S124,S3A7,S5D9,S7G2

r_sci_uart Serial Communication Interface UART S124,S3A7,S5D9,S7G2

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

r_slcdc Segment LCD Controller S3A7

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

r_wdt Watchdog Timer S124,S3A7,S5D9,S7G2 Framework

sf_adc_perodic Periodic Sampling ADC S124,S3A7,S5D9,S7G2 sf_audio_playback Audio Playback S124,S3A7,S5D9,S7G2 sf_audio_playback_hw_dac Audio Playback HW DAC S124,S3A7,S5D9,S7G2 sf_audio_playback_hw_i2s Audio Playback HW I2S S3A7,S5D9,S7G2 sf_audio_record_adc Audio Record ADC S3A7,S5D9,S7G2

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

sf_console Console S124,S3A7,S5D9,S7G2 sf_el_fx Synergy FileX Interface S3A7,S5D9,S7G2 sf_el_gx Synergy GUIX Interface S5D9,S7G2 sf_el_nx Synergy NetX Interface S5D9,S7G2

sf_el_nx_comms Synergy NetX Communication Interface S5D9,S7G2

sf_el_ux Synergy USBX Interface S124,S3A7,S5D9,S7G2

sf_el_ux_comms Synergy USBX Communication Interface S124,S3A7,S5D9,S7G2

sf_el_ux_comms_v2 Synergy USBX Communication Interface V2 S124,S3A7,S5D9,S7G2

sf_external_irq External Interrupt Framework S124,S3A7,S5D9,S7G2 sf_i2c I2C Framework S124,S3A7,S5D9,S7G2 sf_jpeg_decode JPEG Decode S5D9,S7G2 sf_message Inter-Thread Messaging S124,S3A7,S5D9,S7G2 sf_power_profiles Power Mode Profile S124,S3A7, S7G2 sf_spi SPI Framework S124,S3A7,S5D9,S7G2 sf_tes_2d_drw 2D Drawing Engine Framework S5D9,S7G2 sf_thread_monitor Thread Monitor (Watchdog) S3A7,S5D9,S7G2 sf_touch_ctsu Capacitive Touch Sensing Unit S124,S3A7,S5D9,S7G2

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

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

sf_touch_panel_i2c Touch Panel I2C S5D9,S7G2 sf_uart_comms UART framework S124,S3A7,S5D9,S7G2

X-Ware Stacks fx FileX S124,S3A7,S5D9,S7G2 gx GUIX S5D9,S7G2 nx NetX S5D9,S7G2 nx_auto_ip NetX Auto IP S5D9,S7G2 nx_bsd NetX BSD S5D9,S7G2



nx_dhcp_client NetX DHCP Client S5D9,S7G2 nx_dhcp_server NetX DHCP Server S5D9,S7G2 nx_dns_client NetX DNS Client S5D9,S7G2 nx_ftp_client NetX FTP Client S5D9,S7G2 nx_ftp_server NetX FTP Server S5D9,S7G2 nx_http_client NetX HTTP Client S5D9,S7G2 nx_http_server NetX HTTP Server S5D9,S7G2 nx_pop3 NetX POP3 S5D9,S7G2 nx_ppp NetX PPP S5D9,S7G2 nx_smtp_client NetX SMTP Client S5D9,S7G2 nx_sntp_client NetX SNTP Client S5D9,S7G2 nx_telnet_client NetX Telnet Client S5D9,S7G2 nx_telnet_server NetX Telnet Server S5D9,S7G2 nx_tftp_client NetX TFTP Client S5D9,S7G2 nx_tftp_server NetX TFTP Server S5D9,S7G2 nxd_auto_ip NetX Duo Auto IP S5D9,S7G2 nxd_bsd NetX Duo BSD S5D9,S7G2 nxd_dhcp NetX Duo DHCP IPv4 Client S5D9,S7G2 nxd_dhcp NetX Duo DHCP IPv6 Client S5D9,S7G2 nxd_dhcp_server NetX Duo DHCP IPv4 Server S5D9,S7G2 nxd_dhcp_server NetX Duo DHCP IPv6 Server S5D9,S7G2 nxd_dns NetX Duo DNS Client S5D9,S7G2 nxd_ftp_client NetX Duo FTP Client S5D9,S7G2 nxd_ftp_server NetX Duo FTP Server S5D9,S7G2 nxd_http_client NetX Duo HTTP Client S5D9,S7G2 nxd_http_server NetX Duo HTTP Server S5D9,S7G2 nxd_nat NetX Duo NAT S5D9,S7G2 nxd_pop3 NetX Duo POP3 S5D9,S7G2 nxd_ppp NetX Duo PPP S5D9,S7G2 nxd_smtp_client NetX Duo SMTP Client S5D9,S7G2 nxd_sntp_client NetX Duo SNTP Client S5D9,S7G2 nxd_telnet_client NetX Duo Telnet Client S5D9,S7G2 nxd_telnet_server NetX Duo Telnet Server S5D9,S7G2 nxd_tftp_client NetX Duo TFTP Client S5D9,S7G2 nxd_tftp_server NetX Duo TFTP Server S5D9,S7G2

ux_host_class_storage USBX Host Class Mass Storage S5D9,S7G2

ux_host_class_hid USBX Host Class HID S5D9,S7G2 ux_host_class_cdc_acm USBX Host Class CDC-ACM S5D9,S7G2 ux_host_class_hub USBX Host HUB S5D9,S7G2

ux_device_class_storage USBX Device Class Mass Storage S124,S3A7, S5D9,S7G2

ux_device_class_hid USBX Device Class HID S124,S3A7, S5D9,S7G2 ux_device_class_cdc_acm

USBX Device Class CDC-ACM S124,S3A7, S5D9,S7G2

ux_host_class_audio USBX Host Class Audio S3A7, S5D9,S7G2 ux_host_class_gser USBX Host Class Generic

Serial S3A7, S5D9,S7G2 ux_host_class_printer USBX Host Class Printer S3A7, S5D9,S7G2 ux_host_class_prolific USBX Host Class Prolific S3A7, S5D9,S7G2 ux_host_class_swar USBX Host Class Swar S3A7, S5D9,S7G2 ux_device_class_cdc_ecm USBX Device Class CDC-ECM S124,S3A7, S5D9,S7G2 ux_device_class_rndis USBX Device Class RNDIS S124,S3A7, S5D9,S7G2 ux_network_driver USBX Network Driver S124,S3A7, S5D9,S7G2



13. Additional Technical Notices 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

nxd NetX Duo Stack S5D9,S7G2, tx ThreadX S124,S3A7,S5D9,S7G2 ux USBX S124,S3A7,S5D9,S7G2 ux_host_class_storage USBX Host Class Mass Storage S5D9,S7G2 ux_host_class_hid USBX Host Class HID S5D9,S7G2 ux_device_class_hid USBX Device Class HID S124,S3A7,S5D9,S7G2

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://renesas.zendesk.com/anonymous_requests/new • 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://renesas.zendesk.com/anonymous_requests/new

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

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

Renesas Synergy Software Package (SSP) v1.2.0 Publication Date: Rev.1.11 Mar 14, 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

Renesas Synergy™ Platform Renesas Synergy Software Package

Renesas Synergy Software Package (SSP) v1.2.0

R11UT0004EU0111

Documents

User’s Manual Release Notecaxapa.ru/thumbs/757844/r11ut0004eu0111-synergy-ssp-120... · 2020. 2. 17. · Rev.1.11 Mar 2017 Renesas Synergy™ Platform Synergy Software SSP v1.2.0