Developer Resources
Board support packages
Foundry27 projects
Forums
Home
Developer Resources
Technical Articles

QNX Technical Articles

QNX® Software Development Platform 7.0 Board Support Package for the Renesas R-Car H3 and M3: Release Notes

Date of this edition: November 14, 2019

Note: Changes to these notes since February 15, 2017 are highlighted below with this icon: New:

QNX SDP is a cross-compiling and debugging environment, including an IDE and command-line tools, for building binary images and programs for ARM v7, ARM v8, x86, and x86_64 targets running the QNX Neutrino RTOS 7.0.

Board Support Packages (BSP) are available for various hardware platforms on QNX SDP 7.0. This is a release note for the Renesas R-Car H3/M3 BSP.

Throughout this document, you may see reference numbers associated with particular issues, changes, etc. When corresponding with our Technical Support staff about a given issue, please quote the relevant reference number. You might also find the reference numbers useful for tracking issues as they become fixed.

Revision history

The following is a summary of the updates made to this BSP.

BuildID 4196 (7.0.4196.E201908031404)

  • SMMU Manager support has been added to this release that includes the following:
    • Added the smmu option to enable SMMU Manager for the following drivers:
      • SATA (devb-rcarsata)
      • SD/MMC/eMMC (devb-sdmmc-rcar_gen3)
      • Serial (devc-serscif)
      • Ethernet (io-pkt-v6-hc)
      • USB (io-usb-otg)

        Note:Only USB 3.0 devices are supported when you enable SMMU Manager on the driver. USB 1.1, USB 2.0, and USB 3.0 are all supported when SMMU Manager isn't enabled.

      • SPI flash (devf-rcar_qspi-gen3)
      (Ref# J2748239, J2747747, J2729844, J2747436, J2747132, J2747215, J2700131, J2747126, J2747314, J2731735, J2700624)
    • Added the rcar3-h3_r30.smmu file to configure SMMU Manager. (Ref# J2629716)
    • Added a buildfile that shows how to enable SMMU Manager. (Ref# J2748224)
  • To start audio, you now require libsecpol.so in the image, which was added to the buildfiles in this BSP. (Ref# J2741096/J2748224)
  • The QNX IPL is now available for Renesas R-Car M3-W, R-Car M3-W Starter, and R-Car M3-N boards. (Ref# J2737333, J2752272)
  • The optimized string functions (libstringsa64.so) has been removed from the buildfiles. If you're using your buildfile is based on a previous release, you can remove this library as the functions are now available in the updated libc.so. (Ref# J2735956)
  • Writing to Flash memory no longer takes a long time (over an hour). It now takes only a few minutes, as expected. (Ref# J2676563)
  • The devc-serscif driver no longer hangs if you press multiple keys on your keyboard from a serial connection when the board is booting. (Ref# J2543859)
  • USB devices connected to a USB hub are now recognized when you connect the USB to the board. (Ref# J2588649)
  • A small memory leak no longer occurs on the R-Car RAVB Ethernet driver (devb-ravb.so) driver. (Ref# J2668001)
  • Corrected IIC input clock hardware info to be 16.64 MHz/2. (Ref# J2629587).
  • Audio can now be heard with you use the USB open host interface driver (devu-hcd-ohci.so). (Ref# J1692372)
  • The user's guide for this BSP has the following changes:
    • In the user's guide for this board, the command in the "Driver Commands" chapter of the guide to show how to remove lossy decompression has changed to use the area startup-rcar_h3 -r 0x54000000,0x3000000,1 -P4 -W -vvvvv. Previously, it was startup-rcar_h3 -r 0x54000000,0x2FFFFFF,1 -P4 -W -vvvvv, which was incorrect. (Ref# J2648960)
    • Updates to show new options to use SMMU Manager for various drivers. (Ref# J2746410)
    • Added documentation for the R-Car SATA driver (devb-rcarsta), USB device drivers (devu-dcd-usbncm-hsusb-rcar.so, devu-dcd-usbser-hsusb-rcar.so, and devu-dcd-usbumass-hsusb-rcar.so). (Ref# J2746414, J2746415)

BuildID 55 (7.0.55.E201901141359)

  • This was an experimental build.
  • The R-Car H3 and R-Car H3 Starter no longer have boot issues when using U-Boot. (Ref# J2238541)
  • You can now format HyperFlash on WS 2.0 boards. The board no longer hangs after you run the flashctl -p /dev/fs0p0 -o 32M -fv command. (Ref# J2241141)
  • This version of the BSP has been built and tested with the following packages:
    • Screen Board Support R-Car H3 package, version 7.0 BuildID 6529
    • Screen Board Support R-Car M3-N package, version 7.0 BuildID 6529
    • Screen Board Support R-Car M3-W package, version 7.0 BuildID 6529
    For more information, see the Screen Board Support R-Car H3: Release Notes, Screen Board Support R-Car M3-N: Release Notes, and Screen Board Support R-Car M3-W: Release Notes from the QNX Software Center. (Ref# J2551704)
  • For the devb-sdmmc-rcar_gen3 driver, now the board-specific pwr_vdd_base is supported. (Ref# J2621474)
  • For the devc-serscif driver, the following options have been added:
    • -m, which allows you to set the interrupt mode for the driver.
    • -d and -D options that allows you to enable DMA, and enable DMA with a specific channel request, respectively.

    (Ref# J2598899)

  • Added support to boot using Hyperflash memory at 160 Mhz. (Ref# J2521192)
  • Multiple audio driver fixes and changes for the board, which include:
    • Support for 24-bit audio. (Ref# J2562511)
    • Reporting for audio rate capability now functions correctly. (Ref# J2551225)
    • Audio configuration files have been added to support this board. (Ref# J2616213)
    • Audio now uses deva-ctrl-rcar-cs2000.so instead of the deva-ctrl-rcar.so driver. (Ref# J2632842)
    • When you connect to the R-Car H3 board using an HDMI connector and start io-audio, sound is now heard when you play a WAV file.(Ref# J1681187)
  • The SPI Flash driver (devf-rcar_qspi-gen3) has the following updates:
    • The SPI Flash driver (devf-rcar_qspi-gen3) now supports the Macronx MX25 and MX66U1G45G QPSI flash. (Ref# J2596783)
    • The ver option has been added which allows you to specify the board that you're using. (Ref# J2647803)
    • The SPI Flash driver no longer has a memory leak. (Ref #J2619345)
  • For startup, the following options are now supported: - The -R option now supports a third, optional name parameter. The name parameter permits you to assign a string to the typed memory with a system-determined prefix name, which is usually /memory/ram. To see the prefix for the memory you allocated, use the pidin syspage=asinfo command. For example, if you gave the name graphics, the typed memory name could be /memory/ram/graphics/. For the syntax of this option, see the "startup-* options" chapter in the QNX Neutrino Utilities Reference. (Ref# J2603235)
  • Added the below4G parameter to the -R option to allow startup to support allocating reserved memory from the space below 4GB. This is required for certain DMA hardware that has a 32-bit address restriction. The expanded syntax for the -R option is -R size[,align[,name[,below4G]]]. (Ref# J2639314)
  • The -L startup option has been expanded to allow the reservation of multiple memory regions. Also introduced the -d and -p options to startup, which is used for RAM size detection and to set the maximum number of CPUs to run on a boot cluster, respectively. (Ref# J2647834, J2639923)
  • For the R-Car H3 and R-Car H3 Starter Kit boards, added QNX IPL to this BSP, which means you can now use it with the Renesas Loader as a bootloader to load the QNX IFS. (Ref# J2617787)
  • Fixed the network driver (devnp-ravb.so) so that packets no longer sporadically drop, which previously caused networking issues. (Ref# J2231946)

BuildID 45 (7.0.45.E201805180939)

  • Added support to use -E as a startup option.

    If you have QNX SDP 7.0 Security Update (Build ID 861) installed, you can add -E meltdown to the startup command in the buildfile to enable the workaround for the Meltdown exploit (CVE-2017-5754). By default, the workaround for the Meltdown exploit isn't enabled in the buildfile for this BSP. For more about the security update, see the QNX SDP 7.0 Security Update (Build ID 861): Release Notes. (Ref# J2583134)

  • The serial driver now supports the allocation of memory above 4 GB for 64-bit addresses. (Ref# J2531936)
  • You can now use the ETHADDR U-Boot environment variable to set the MAC address. (Ref# J2532000)
  • The Flash EFS partition devf no longer crashes when the DMA buffer size matches the maximum message size during a read or copy operation. (Ref# J2525409)
  • The rcar*-graphics.build buildfiles now correctly specify all the required graphics libraries, which are screen_rcar3-alloc.so, libWFDrcar3_g.so, and libWFDrcar3.so. (Ref# J2547760)
  • HDMI now works on WS2.0 Silicon revisions of the R-Car H3 and R-Car H3 Starter boards. (Ref# J2223647)
  • There's now graphics support for the WS2.0 Silicon Revisions of the R-Car H3 and R-Car H3 Starter boards. (Ref# J2223647)
  • When you use a serial USB port to connect from your host system to the board where the Watchdog is running, the BREAK signal that's sent when you disconnect no longer causes the board to hang. (Ref# J2550651)

BuildID 37 (7.0.37.E201803222043)

  • The following issues were resolved:
    • Fixed the devnp-ravb so that networking issues where packets sporadically drop no longer occur. (Ref# J2231946)
    • Downstream PCI devices are now detected. Now PCI devices are correctly marked as available when the link is up. (Ref# J2531217, J1687714)
    • SCSI errors no longer occur when you use the devb-rcarsata driver in direct I/O mode on the R-Car H3 board. (Ref# J2192758)
  • Added support for PCIe1 on all supported boards. The parameter bus-scan-limit=1 for pci-server has been updated to scan for PCIe1. In the buildfile and the documentation describing the pci-server driver, the command has been updated from pci-server --bus-scan-limit=1 to pci-server --bus-scan-limit=16. You should ensure that you're using the latest version of the pci_hw-rcar-salvator-x.so file. (Ref# J2471877)

BuildID 35 (7.0.35.E201803141101)

  • The following issues were resolved:
    • Intermittent data reads no longer occur when you have a network connection (e.g., telnet) to the board. (Ref# J2511508, J2472552)
  • Improved memcpy() and memset() performance by using optimized strings. (Ref# J2519955)

BuildID 27 (7.0.27.E201712191255)

  • Updated the startup to accept an optional -p option. The numeric value for the -p option specifies the number of CPUs in the boot cluster (cluster 0) to use.
  • Updated the BSP to support R-Car M3-N boards.
  • Updated the BSP to support graphics for R-Car M3-W and R-Car M3-W Starter boards.

BuildID 22 (7.0.22.E201710171603)

  • Introduced big.LITTLE support. The BSP now supports enabling all cores on the board:
    • H3— four A53 cores and four A57 cores
    • M3-W— four A53 cores and two A57 cores

BuildID 16 (7.0.16.E201709081143)

  • Updated the BSP to use RCLK Watchdog Timer (RWDT) from the previous Secure Watchdog Timer (SWDT).
  • Updated the BSP to support R-Car M3-W, R-Car M3-W Starter, and R-Car H3 Starter boards.
  • Updated to support the WS 2.0 Silicon Revision for R-Car H3 boards.
  • Updated the user's guide for this BSP as follows:
    • Added DIP switch settings for R-Car M3-W, R-Car M3-W Starter, and R-Car H3 Starter boards.
    • Fixed the BSP User's Guide to include the branch name when using the git clone command. (Ref# J1690381)
    • Added workaround when the watchdog is disabled in the Renesas BootLoader version 1.09. (Ref# J1687562)
    • Describe how to change a register so that RCLK Watchdog Timer (RWDT) can trigger a reset.

Build 7.0.0 GA201702151736

  • Initial release.

Supported hardware

Our BSP supports the following boards:

  • Renesas R-Car H3, Salvator-X Silicon Revisions WS1.0 and WS1.1, and Salvator-XS, Silicon Revisions WS2.0 and WS3.0 (referred to as the R-Car H3)
  • Renesas R-Car H3 Starter Kit Premier, Silicon Revisions WS1.0, WS1.1, and WS2.0 (referred to as the R-Car H3 Starter)
  • Renesas R-Car M3-W (Salvator-X), Silicon Revision WS1.0 (referred to as the R-Car M3-W)
  • Renesas R-Car M3-W Starter Kit Pror, Silicon Revision WS1.0 (referred to as the R-Car M3-W Starter)
  • Renesas R-Car M3-N (Salvator-X), Silicon Revision WS1.0 (referred to as the R-Car M3-N)

Development and testing for this release were on revision WS1.1 of the R-Car H3 board using the Renesas Bootloader v1.0.9 with the lossy decompression feature disabled. If you're using an earlier version of the Renesas BootLoader, you must use the -r option with the startup-rcar_h3 command. For more information, see the Startup section in the relevant Driver Commands (name_of_board) chapter of the user's guide for this board. For example, if you're using the R-Car H3 Starter board, see the Driver Commands (R-Car H3 Starter) chapter in the user's guide for this BSP.

Note:

For Silicon Revision 2.0 variants of the boards, we have tested only on the R-Car H3 Starter.

Known issues

This BSP has the following known issues:

  • New: (Found in Build ID 4196) When you use QNX IPL to boot your board with the QNX Neutrino RTOS, the network connection may not work as the network device Ethernet link is down.

    For example:

    # nicinfo
ravb0:
  Renesas AVB Network Device Ethernet Controller

  Link is DOWN

  Physical Node ID ........................... 2E09A0 0384FD
  Current Physical Node ID ................... 2E09A0 0384FD
  Current Operation Rate ..................... 0 kb/s half-duplex
  Active Interface Type ...................... MII
    Active PHY address ....................... 0
  Maximum Transmittable data Unit ............ 1500
  Maximum Receivable data Unit ............... 1500
  Hardware Interrupt ......................... 0x5d
  Hardware Interrupt ......................... 0x5f
  I/O Aperture ............................... 0xe6800000 - 0xe68007ff
  Promiscuous Mode ........................... Off
  Multicast Support .......................... Enabled
...
...

    (Ref# J2793535)

    Workaround: Instead, use U-Boot as a loader to boot your board.

  • New: (Found in Build ID 4196) The USB host and device commands in the user's guide don't prefix the USB drivers with "hcd-" or "dcd-", respectively. For this reason, the USB commands differ from the USB commands in buildfiles. For example, to run the USB device controller for mass storage, the command in the user's guide is shown as: 
    io-usb-otg -d usbumass-hsusb-rcar ioport=0xe6590000,irq=139
    But, in the buildfile, the command is shown as: 
    io-usb-otg -d dcd-usbumass-hsusb-rcar ioport=0xe6590000,irq=139
    (Ref# J2784881)

    Workaround: None. Running the command with or without the "hcd-" or "dcd-" to the name of driver doesn't impact its functionality or its operation. We recommend you run the USB commands without the use of the "hcd-" or "dcd-" as shown in the user's guide.

  • New: (Found in BuildID 4196) On R-Car H3 (Silicon Revision WS 3.0) boards, graphics (Screen) doesn't work when you use the provided prebuilt images in this BSP. (Ref# J2777625)

    Workaround: Rebuild your image and ensure that you have the following Screen Board Support packages installed:

    • Screen Board Support R-Car H3 package, version 7.0 BuildID 6529
    • Screen Board Support R-Car M3-N package, version 7.0 BuildID 6529
    • Screen Board Support R-Car M3-W package, version 7.0 BuildID 6529

    Load the rebuilt image onto your board on your board. Graphics should function as expected.

  • New: (Found in BuildID 4196) On some R-Car H3 (Silicon Revision WS 3.0) boards, when you start the SD/MMC/eMMC driver ( e.g., devb-sdmmc-rcar_gen3 blk cache=64m cam bounce=128k mem name=below4G sdmmc partitions=on sdio idx=2,emmc disk name=mmc ), I/O errors may occur. Here's what you might see running slog2info: 
    Jan 01 00:02:28.653 devb_sdmmc_rcar_gen3.188426 slog 0 _scsi_io_cbf: status b, retry 8 
Jan 01 00:02:28.657 devb_sdmmc_rcar_gen3.188426 slog 1800 sdmmc_read_write: sdio_set_partition failure Input/output error
Jan 01 00:02:28.754 devb_sdmmc_rcar_gen3.188426 slog 0 scsi_error (sdmmc ptl-0:2:0): cam_status=0x4b, scsi_status=0x0, flag=0x0000a040, vuflag=0x0001, cmd=0x28 
Jan 01 00:02:28.754 devb_sdmmc_rcar_gen3.188426 slog 0 _scsi_io_cbf: status b, retry 9 
Jan 01 00:02:28.757 devb_sdmmc_rcar_gen3.188426 slog 1800 sdmmc_read_write: sdio_set_partition failure Input/output error
Jan 01 00:02:28.854 devb_sdmmc_rcar_gen3.188426 slog 0 scsi_error (sdmmc ptl-0:2:0): cam_status=0x4b, scsi_status=0x0, flag=0x0000a040, vuflag=0x0001, cmd=0x28 
Jan 01 00:02:28.854 devb_sdmmc_rcar_gen3.188426 slog 0 scsi_io_done ptl-0:2:0: I/O error 5 lba 0 (0 - 7), nlba 8, resid 8 
Jan 01 00:02:28.854 devb_sdmmc_rcar_gen3.188426 slog 0 scsi_error (sdmmc ptl-0:3:0): cam_status=0x56, scsi_status=0x0, flag=0x00000040, vuflag=0x0008, cmd=0x28 
Jan 01 00:02:28.854 devb_sdmmc_rcar_gen3.188426 slog 0 scsi_error (sdmmc ptl-0:3:0): cam_status=0x56, scsi_status=0x0, flag=0x00000040, vuflag=0x0001, cmd=0x28 
Jan 01 00:02:28.854 devb_sdmmc_rcar_gen3.188426 slog 0 scsi_io_done ptl-0:3:0: I/O error 25 lba 0 (0 - 7), nlba 8, resid 8
    (Ref# J2770551)

    Workaround: To prevent I/O errors, clear the HS400 timer when you start the SD/MMC/eMMC driver. Here's the option that you specify in the command:

    devb-sdmmc-rcar_gen3 blk cache=64m cam bounce=128k mem name=below4G sdmmc partitions=on sdio idx=2,emmc,timing=~hs400 disk name=mmc
  • New: (Found in BuildID 4196) On some R-Car H3 Salvator-XS (Silicon Revision WS 3.0) boards, the time synchronization might be unstable. (Ref# J2774253)

    Workaround: None.

  • New: When you connect two R-Car H3 (Revision Salvator-XS) boards together using an Ethernet cable and both boards are running QNX Neutrino, the network linkup fails. (Ref# J2760318)

    Workaround: Connect the boards using a network hub or run Linux on one of the boards.

  • New: (Found in BuildID 4196) When you boot R-Car M3N boards with images from this BSP, you may see the error ldd:FATAL: Could not load library libsecpol.so.1 in your console. This issue occurs because the rcar_m3n.build and rcar_m3n-graphics.build files are missing the Security Policy library (libsecpol.so). (Ref# J2748224)

    Workaround: Add libsecpol.so to $BSP_ROOT_DIR/images/rcar_m3n.build and $BSP_ROOT_DIR/images/rcar_m3n-graphics.build files and then rebuild the image.

  • New: (Found in BuildID 4196) On the R-Car H3 (Salvator-XS Silicon Revision 3) boards, if the SW12, pin 7 isn’t set to ON (1) and you start the PCI Server (i.e., pci-server --bus-scan-limit=1 -c), a memory fault occurs, which is indicated as an error found in slogger as follows: 
    Jan 01 00:00:43.549 pci_server.266262 pci_log 0 ERROR,0,0,2 [266262:1]: hw_init: PHYRDY not ready 
Jan 01 00:00:43.549 pci_server.266262 pci_log 0 INFO ,1,1,2 [266262:1]: ++++ rcar_pcie_init() [PCIe 1] end, Invalid Argument [PCI_ERR_EINVAL] ++++
    (Ref# J2736675)

    Workaround: Power down the board and set SW12, pin 7 to ON (1). After you restart your board, you should not see this issue.

  • New: (Found in BuildID 4196) At times when you run the Flash driver (devf-rcar-qspi-gen3) with the background reclaim option (-b), the reclaim doesn't occur even though the trigger limit has been exceeded. This may cause your Flash disk to run out of space. (Ref# J2743290)

    Workaround: Manually reclaim the space by running the following command before you run out of space on the Flash disk: 

    flashctl -vrp /fs0p1
  • New: (Found in BuildID 4196) When you start the EHCI controller with SMMU Manager enabled, USB 2.0 devices might not be detected when io-usb-otg is started. (Ref# J2756120, J2759613)

    Workaround: Use USB 3.0 devices instead or start the USB driver without SMMU Manager enabled.

  • New: (Found in BuildID 4196) The default SMMU Manager enabled image provided with this BSP incorrectly starts the EHCI and OHCI controllers. USB 2.0 and USB 1.1 devices aren't supported in this release. (Ref# J2759221)

    Workaround: Remove the -d hcd_ehci and -d hcd_ohci with their associated options when you start io-usb-otg from the buildfile and then rebuild the image.

  • New: When you start the OHCI controller with SMMU Manager enabled, USB 1.1 and USB 2.0 devices might not be detected when io-usb-otg is started. (Ref# J2739841)

    Workaround: Use USB 3.0 devices instead or start the USB driver without SMMU Manager enabled.

  • New: (Found in BuildID 4196) There's no usage information for the smmu option for the Flash driver (e.g., type use devf-rcar-qspi-gen3). (Ref# J2736538)

    Workaround: For more information about using the smmu option, see the user's guide for this BSP.

  • New: (Found in BuildID 4196) When you use the serial driver (devc-serscif) with DMA enabled, file transfers can fail over the serial connection when the packet length is a multiple of 512. (Ref# J2758499)

    Workaround: Set the packet length to a non-multiple of 512. For example, if you wanted to use a packet length of 4096 (which is a multiple of 512), set it to 4095 instead.

  • New: (Found in BuildID 4196) For the SPI Flash driver (devf-rcar-qspi-gen3), any options specified after the board-specific options (bs), aren't recognized. (Ref# J2739912)

    Workaround: Specify the board-specific options last when you use the devf-rcar-qspi-gen3 command. For example, for the -b option to be recognized, it must be specified before the board-specific option (bs) as follows:

    devf-rcar_qspi-gen3 -b5 bs=smmu=on
  • New: (Found in BuildID 4196) On the R-Car H3, if you're restarting the Audio service (io-audio) and using typed memory (i.e., using SMMU Manager), the io-audio command fails if you run it from a directory outside of root ("/") with the following error: 
    dma_channel_attach_smmu: parse options failed
    This issue occurs because the code that uses typed memory (sysdmac) doesn’t specify the forward slash ("/") in the posix_typed_mem_open() call. The forward slash ("/") requirement is due to a known QNX SDP 7.0 issue. For more information about the QNX SDP issue, see the QNX Software Development Platform 7.0:Release Notes (Ref# J2737759)

    Workaround: If you need to restart the Audio service, ensure your current working directory is root ("/") before you run the io-audio command. Alternatively, you could modify the BSP code to add the missing slash ("/") in the BSP_ROOT_DIR/src/lib/dma/rcar/sysdmac/sysdmac.c file at line 588 as follows:

    From:

    chan->typed_mem_fd = posix_typed_mem_open("sysram&below4G", O_RDWR, POSIX_TYPED_MEM_ALLOCATE_CONTIG);

    To:

    chan->typed_mem_fd = posix_typed_mem_open("/sysram&below4G", O_RDWR, POSIX_TYPED_MEM_ALLOCATE_CONTIG);
  • New: (Found in BuildID 4196) When you build the BSP, it may fail to build with an error that it can't find the USE_SMMU definition. (Ref# J2750780, J2769097)

    Workaround: To build this BSP, you must update the QNX SDP 7.0 Connectivity - io-char package (com.qnx.sdp.target.connectivity.io_char) to release Build 7.0.4284 or higher. The updated package contains the required definition to build the BSP.

  • New (Found in BuildID 4196) When you build the images for this BSP on a Windows host, you may see the following warning: 
    mkifs -vvv -r../install rcar_h3.build ifs-rcar_h3.bin 
Warning: Host file 'pcidatabase.com-tab_delimited.txt' missing.
    (Ref# J2758495)

    Workaround: The image that's built works as expected. The warning doesn't indicate a problem so you can ignore the warning. If you want to fix the warning, you must replace the colon (":") with a semicolon (";") in the following line in the rcar_h3.build file as follows:

    Change: 
    [search=../install/etc/system/config/pci:${QNX_TARGET}/etc/system/config/pci] /etc/system/config/pci/pcidatabase.com-tab_delimited.txt=pcidatabase.com-tab_delimited.txt
    To: 
    [search=../install/etc/system/config/pci;${QNX_TARGET}/etc/system/config/pci] /etc/system/config/pci/pcidatabase.com-tab_delimited.txt=pcidatabase.com-tab_delimited.txt
  • New: (Found in BuildID 4196) We recommend that you install the latest updates for your QNX SDP 7.0.4 before you build your BSP. If you can't install the latest updates and must selectively update only certain components in your QNX SDP 7.0 installation, this BSP may no longer successfully build; or if this BSP builds, you may see new issues when you load the rebuilt image on your target that aren't identified in this release note.

    Workaround:

    To identify a solution to your build error or issue in the rebuilt image, see the Troubleshooting Board Support Packages guide on the QNX website.
  • New: (Found in BuildID 55) Under heavy usage and a filesystem that is heavily fragmented, occasionally, an EBADFSYS error may occur. (Ref# J2696606)

    Workaround: Ensure that you run background reclaim and recovery option for the Flash driver (i.e., devf-rcar_qspi-gen3 -r -b5) on the board.

  • New: (Found in BuildID 55) When you use the devf-rcar_qspi-gen3 driver to write data to HyperFlash memory, the data fails to write correctly when N processes simultaneously write more than 1/N the total size of the HyperFlash memory, where N represents the number of simultaneous processes running.

    For example, if you have eight processes that write to 16 MB of HyperFlash memory and each process writes more than 2 MB of data, the data fails to write correctly; however, if each process simultaneously writes less than 2 MB of data, the data is correctly written to the HyperFlash memory. (Ref# J2635720)

    Workaround: Ensure that when you simultaneously write data using processes, that the data doesn't exceed 1/N the size of the HyperFlash Memory.

    Alternatively, write data from processes simultaneously to QSPI memory as the issue has not been seen when you use QSPI memory.

  • New: (Found in BuildID 55) Audio on the left and right channels are inverted when in 16-bit mode. The problem doesn't occur when you use 24-bit mode.(Ref# J2251918)

    Workaround: When you start the io-audio driver, use the fsync_pol option to 1 when in 16-bit mode. For example, in the buildfile, you can add the fsync_pol option to the options parameter in the audio configuration file:

    ...
...
/etc/system/config/audio/io_audio.conf = {
########################################
# rcar for On-board audio
########################################
[ctrl]
name=rcar-cs2000
options=ver=d3,tx_ssi=3,rx_ssi=4,sample_rate=32000:48000,fsync_pol=1
mixer_dll=ak4613                       # Load deva-mixer-ak4613.so
ak4613_i2c_dev=0                       # /dev/i2c0
ak4613_i2c_addr=16                     # 0x10
ak4613_out1=enable:differential
ak4613_in1=enable:single-ended
}
...
...
  • New: (Found in BuildID 55) When QNX IPL is used to as the bootloader, there are packets that may sporadically drop, indicating that there are networking issues. (Ref # J2654411)

    Workaround: Use U-Boot instead of the QNX IPL as the bootloader. Packets don't drop when you use U-Boot.

  • New: (Found in BuildID 55) If you run the USB driver (io-usb-otg) with the devu-hcd-ohci.so and connect an Ethernet dongle to the board, you won't be able to ping other devices on the network from the target. (Ref# J2685854)

    Workaround: Start the USB driver with the devu-hcd-ehci.so driver instead of the devu-hcd-ohci.so driver. For example:

    io-usb-otg "io-usb-otg -t memory=/memory/below4G
                       -d hcd-ehci ioport=0xEE080100,irq=0x8C,memory=/memory/below4G
  • New: (Found in BuildID 45) After you install PCI update (Build 7.0.21) to your QNX SDP 7.0 baseline installation, this BSP may fail to build with an error that the pci_hw-*.so shared libraries are missing (e.g., pci_hw-rcar-salvator-x.so). (Ref# J2587257)

    Workaround: Install the QNX SDP 7.0 Connectivity – PCI HW Module Renesas R-CAR SalvatorX in the QNX Software Center and then rebuild your BSP.

    The reason you must install another package is because after installing the PCI update, the hardware platform-specific shared libraries are removed from your QNX SDP 7.0 installation. The required shared libraries are available as separate PC HW Module packages that you install in the QNX Software Center.

  • PCIe doesn’t support maximum link speeds because it doesn't link up at 5.0 GT/s initially during the link train process.(Ref# J2471877)

    Workaround: Manually, change the speed to 5.0 GT/s.

  • When you use a USB hub with the R-Car H3, R-Car H3 Starter, R-Car M3-W, or R-Car M3-W Starter boards (Working Samples(WS) 1.1 and 2.0), the USB driver resets when you run the Screen Graphics Subsystem. (Ref# J2183380)

    Workaround: Don’t use a USB hub.

    If you need to use a USB hub, the QoS settings must be updated. You can use one of the following ways to update the QoS settings to increase USB bandwidth:

    • Use the Renesas qos_tp utility to update the QoS settings with a .csv file.

      Contact Renesas Support to obtain this utility and for instructions on how to use it, see https://elinux.org/R-Car/Boards/Yocto-Gen3#How_do_I_increase_USB_bandwidth.

      This way of updating the QoS settings doesn't persist across reboots. You must run this utility every time you boot to apply the new QoS settings.

    • Update the boot loader (BL2) using these steps.
      1. Contact Renesas Support to obtain information about changing the QoS settings in qos_init_H3_or_M3_vworking_Sample_revision.c.
      2. Change the appropriate QoS settings in the file qos_init_H3_or_M3_vworking_Sample_revision.c.
      3. Use the updated arm-trusted-firmware/plat/renesas/rcar/qos/H3_or_M3/qos_init_H3_or_M3_vworking_Sample_revision.c file when you build the boot loader as described in Building BootLoader to build modified secured settings in the Installation Notes chapter of the Renesas R-Car H3 BSP User's Guide.

        This qos_init_H3_or_M3_vworking_Sample_revision.c file is one of the files used to build the bl2.srec firmware file.

      4. Refresh the firmware to apply the new QoS settings by following the instructions from Programming U-Boot to HyperFlash in the Installation Notes chapter of the Renesas R-Car H3 BSP User's Guide.
  • When you connect a USB 3.0 mass storage device (e.g., USB 3.0 memory stick) directly to the R-Car H3 board, the Upstream Port Speed doesn't detect as SuperSpeed. Instead, the speed is incorrectly detected as Hi-Speed (High). (Ref# J1690324)

    Workaround: Connect the USB 3.0 mass storage device to a USB hub and then connect the USB hub to the R-Car H3 board, the Upstream Port Speed should be detected as SuperSpeed.

Getting started with this BSP

Each BSP has a user's guide that describes what's in the BSP and how to install and work with it. In a browser, after you log in with your myQNX account, you can download the latest revision of the user's guide from the QNX SDP 7.0 Board Support Documentation page.

We recommend that you read the Building Embedded Systems guide, which contains common information about working with all BSPs from QNX Software Systems. This guide is also available on the QNX Software Development Platform 7.0 documentation website.

Note: To ensure that you pick up the same components from your development environment, we recommend that you rebuild the IFS image on your host system.

Included in this BSP are prebuilt IFS images that are provided as convenience for you to quickly get QNX Neutrino running on your board, however these prebuilt images might not have the same components from your development environment.

Technical support

To obtain technical support for any QNX product, visit the Support area on our website (www.qnx.com). You'll find a wide range of support options, including community forums.