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 R-Car D3 (Draak) Board:Release Notes

Date of this edition: November 14, 2019

Note: Changes to these notes since March 7, 2018 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 D3 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 17 (7.0.17.E201902081139)

  • USB packaging was updated. To ensure you have the proper packaging to build the BSP, ensure you update your USB components in your installation. (Ref# J2531157)
  • This version of the BSP has been built and tested with the Screen Board Support R-Car D3 packages, versions 7.0 BuildID 6442 and 7.0 BuildID 6529. For more information, see the Screen Board Support R-Car D3: Release Notes from the QNX Software Center.

BuildID 14 (7.0.14.E201811291039)

  • 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, which allows you to enable DMA
    • -D, which allows you to enable DMA with a specific channel request

    (Ref# J2598899)

  • The r-car-thermal supports now supports 4 as a new driver version for the -V option. The new driver version is for boards that don't have a CIVM (voltage monitor). (Ref# J2625376, J2627402)
  • Added graphics support to the BSP. When you want to build Screen for this board, ensure you have the corresponding QNX SDP 7.0 Screen Board Support R-Car D3 package that's available in the QNX Software Center. For information about the QNX SDP 7.0 Screen Board Support R-Car D3 package, see its release notes. (Ref# J2593224, J2231850)
  • Added interrupt tables in the buildfiles. (Ref# J2537130)
  • 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)
  • The SPI Flash driver ( devf-rcar_qspi-gen3driver) has the following updates:
    • It now supports MX66Y1g45G 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. 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/graphics/. For example, if you gave the name graphics, the typed memory name could be /memory/graphics/. For the syntax of this option, see the "startup-* options" chapter in the QNX Neutrino Utilities Reference.

    (Ref# J2603235)

  • The -E option is now supported. 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 -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)
  • The board no longer hangs after you run the flashctl -p /dev/fs0p0 -o 32M -fv command to format HyperFlash. (Ref# J2617005)
  • Fixed the network driver (devnp-ravb.so) so that packets no longer sporadically drop, which previously caused networking issues. (Ref# J2231946)

Build ID 9 (7.0.9.E201803071335)

  • Initial release. This was an experimental build.

Supported hardware

Our BSP supports the following boards:

  • Renesas R-Car D3 Draak Board SoC ES 1.0

Known issues

This BSP has the following known issues:

  • New: (Found in Build ID 17) 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 BuildID 17) After you update your QNX SDP installation to 7.0.4 on your host machine, this BSP may no longer build; or if your BSP builds successfully, you may see new issues in the rebuilt image when you try to load it on your target.

    Workaround: To identify a solution to your build error or the solution to an issue in the rebuilt image, see the Troubleshooting Board Support Packages guide on the QNX website.

  • New: (Found in BuildID 17) The dhclient doesn’t work in the provide images because binaries are missing from the buildfile and the dhclient command doesn’t have the correct parameters. (Ref# J2765627)

    Workaround: Modify the buildfiles manually and rebuild the images for this BSP. In your buildfile, ensure you have the following:

    • the dhclient command is: dhclient -m -lf /dev/shmem/dhclient.leases -pf /dev/shmem/dhclient.pid -nw interface where interface is the name of your network interface such as ravb0
    • the dhclient-script has execute permissions ( e.g., [search=${QNX_TARGET}/sbin perms=a+x] /sbin/dhclient-script=dhclient-script)
    • the following binaries are included in the buildfiles:
      • /etc/dhclient.conf
      • /sbin/dhclient-script
      • arp
      • cat
      • chmod
      • cp
      • dhclient
      • echo
      • getconf
      • hostname
      • ifconfig
      • mv
      • more
      • omshell
      • ping
      • rm
      • route
      • sed
      • setconf
      • sleep
    For example, in the rcar_d3-graphics.build file, make the following changes:
    • Remove the line ifconfg ravb0 up (approximately line 113)
    • Change dhclient -nw -lf /tmp/dhclient.leases ravb0 to dchclient -m -lf /dev/shmem/dhclient.leases -pf /dev/shmem/dhclient.pid -nw -ravb0 (approximately line 114)
    • Add the arp, hostname, omshell, and route binaries to the list of Network driver binaries (approximately line 379)
    • Remove route from the general binaries and add the sed, getconf, setconf, and more binaries to the list of General commands (approximately line 547)
  • New: (Found in BuildID 17) Under heavy usage and a filesystem that is heavily fragmented, occasionally, an EBADFSYS error may occur. (Ref# J2696606)

    Workaround: None.

  • New: 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 17) 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 17) When the 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 17) When you use the sendnto utility to send the IFS to the board over a serial connection, it fails with the error "Unrecognized source file type". (Ref# J2653837)

    Workaround: You must use the -r with the sendtonto command because this platform uses raw IFS in the buildfile. For example, use the following command from your host:

    sendnto -r -d /dev/ttyUSB0 $BSP_ROOT_DIR/images/ifs-rcar_d3.bin
  • New: (Found in BuildID 17) 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

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.