I have been looking for a newer version of firmware to download and install to a myRIO. I have not been able to find any downloads for myRIO firmware, let alone a recent version. Any thoughts as to where I could look for a new version of the firmware?
Download the new release of Device Drivers from NI and you will get a new firmware for your myRIO.
See more details here
Related
I am having some issues as I need the latest version of UHD for my USRP's FPGA image to be compatible. I have the updated version of UHD locally installed but I need GNUraido to use the local version. GNUradio installs the outdated version of UHD and only uses it.
Please ask if you need more information, and thank you.
I'm working on a project which uses the D2XX drivers from FTDI chip.
We are delivering the ftd2xx.dll file as part of our application. As far as I understand, the other files (e.g. ftdibus.sys) are installed on the system (at least for Windows) where the application runs. Linux is also a target for us, but let's ignore that for simplicity now.
My question is regarding the relation between these files? If, for example, I upgrade the ftd2xx.dll file delivered with our application, will users have to install the newest drivers? What if they do not?
In addition to the specific FTDI drivers, any general source of information on this area is also very welcome.
I used to work on a project that made use of FTDI's D2XX library.
There is no tight coupling between the exact version of ftd2xx.dll and ftdibus.sys. I believe the interface between ftd2xx.dll and the kernel mode driver is version independent at the basic feature level (at least since version 2.04.06 or so). There is even functions in the DLL to query DLL and driver versions respectively.
Thus, it can happen that they are 'out of sync'. I.e. ftd2xx.dll could be one from a more recent release than ftdibys.sys or vice versa. That is not a problem as such.
You are of course in complete control of the ftd2xx.dll version, but how does the driver package get installed? Is it installed as part of your application, or do you rely on the user obtaining the driver from another source? If your application has an installer, it could be an option to include FTDI's driver package in the installation. Thereby you will know which driver version is available.
What can be really tricky (and what has caused me headaches) is if there are other devices on the PC that use FTDI's chip. If such a device is supplied with media containing an older version of the driver and the user chooses to install this driver, it will simply overwrite any existing version of the driver (e.g. the version that your installer provided). This is a potential cause of regression, because FTDI has resolved a lot of bugs in the driver over the years.
If I were you, I would check the driver version at runtime and compare it to a version that is known to work (the version that you tested your application with). If the driver is older, suggest the user to upgrade it. Otherwise I would assume it is compatible.
I want to build a sample included in Vulkan SDK.
I downloaded the SDK from http://vulkan.lunarg.com and install it.
Then I opened the Visual Studio (I have a 2013 version), I open the solution from this path: (C:\VulkanSDK\1.0.13.0\Demos). I choose DEMOS.sln file. Then when I click on LocalWindowsDebugger this message pops up:
vkCreateInstance Failure:
vkEnumerateInstanceExtensionProperties failed to find the VK_KHR_surface extention.
Do you have a compatible Vulkan installable client driver (ICD) insatalled? Please look at the Getting Started guide for additional information.
I have never worked with vulkan, but as it named "Demo", I think that everything inside of it should be set in order to work.
I searched the web, but as it is new, there are few resources talked about it.
What is ICD? and how to install it? (is it different from installer of VulkanSDK?) OR this error is about completely different property? like setting properties of VisualStudio?
ICD is basically your GPU driver...
Both the SDK and driver install vulkaninfo app. Use it to determine what extensions you have and whatnot.
BTW Some time ago AMD drivers forgot to export the extensions like VK_KHR_surface. Make sure you are using the latest driver (16.5.2.1 on AMD and 365.19 on NVIDIA as of time of writing).
Also you need supported GPU. Consult:
NVIDIA supported GPUs
AMD supported GPUs
Khronos maintained list
BTW: All the demos work for me.
Do you have a compatible Vulkan installable client driver (ICD) installed?
This message tells you that Vulkan's loader wasn't able to find a Vulkan driver on your device. ICD is the installable client driver that comes with the driver of your graphics card.
What GPU are you using and do you have a driver installed that actually supports Vulkan? Note that while your card may support OpenGL it may not support Vulkan.
Check NVIDIA(performance mode) is selected at "Nvidia X Server Settings" application if you are using ubuntu.
I recently installed the AC6 System Workbench in order
to work with the STM32 OSXMotionFX Library
and I'm experiencing some troubles related
to the sample application shipped with this library.
Let me know if there is a better place to post such question.
It seems that the sample project works with a different
version of the STM32 Cube expansion drivers for the
X-Nucleo-IKS01A1 expansion board of the base
STM32 Nucleo-F401RE board I have.
In particular the sample project links to driver files
that are missing, some of them seem with different names
compared to the existing ones, that's why I guess
the sample project is referring to an old version of the drivers.
Any one does know how to get the previous versions of the
STM32CubeExpansion_MEMS1_V1.4.0 software ?
I did already search the ST Microelectronics web site
but to no avail, the X-CUBE-MEM1 software
is only shipped at version 2.0.0
and it seems I need the previous version.
Thanks in advance for redirecting me to the correct site in case.
You can download the sample application in the software package osxMotionFX v1.4.0. It is aligned to the new version of the X-CUBE-MEMS1 drivers (v2.0.0). Unfortunately osxMotionFX v1.3.0 is not compatible with the new version of the X-CUBE-MEMS1 drivers.
You mean that osxMotionFX v1.4.0 does not work with X-CUBE-MEMS1 v2.0.0? It is very strange. I'm able to use them without any issue. So probably, you are using osxMotionFX v1.4.0 with an old version of X-CUBE-MEMS1 package. Try to uninstall your current osxMotionFX package, download again the X-CUBE-MEMS1 package v2.0.0 and reinstall the osxMotionFX v1.4.0 over the new X-CUBE-MEMS1 package v2.0.0. Let me know if it fixes your issue.
I use sample application of osxMotionFX v1.4.0 with X-CUBE-MEMS1 v2.0.0. I'm sure that you are not using X-CUBE-MEMS1 v2.0.0 because "x_nucleo_iks01a1_accelero.h" and "x_nucleo_iks01a1_gyro.h" are only defined in X-CUBE-MEMS1 v2.0.0 and not in the previous version of the package. You can also cross-check it looking at the installation folder that you are using for osxMotionFX; if it is not "STM32CubeExpansion_MEMS1_V2.0.0", then you are using a previous version of X-CUBE-MEMS1. Please, try to download again X-CUBE-MEMS1 software package.
I am trying to find release notes for mono versions 2.10.11 and 2.10.12 but cant seem to find them. The latest I can find is 2.10.9. http://www.mono-project.com/Release_Notes_Mono_2.10.9
Thanks
Mono updated to version 3.
See latest mono release notes:
http://www.mono-project.com/Release_Notes_Mono_3.0#New_in_Mono_3.0
Actual Mono version for MAC OS X, Windows and openSUSE is 3.2:
http://www.mono-project.com/Release_Notes_Mono_3.2