SoundLoader 2.4 has been released and now includes DigiIPL 2.2 for updating all of our firmware updatable products including the DCS240. The package also includes the Microsoft Visual C++ 2008 Redistributable Package that is required for the new version of DigiIPL. Download it here.
If you are having issues with Windows 10's SmartScreen please view this small guide to help you install the program.
- Zephyr Port Devices Driver Download Win 7
- Zephyr Port Devices Driver Download Windows 10
- Zephyr Port Devices Driver Download
- Zephyr Port Devices Driver Downloads
From time to time, Digitrax issues firmware updates for our products. Check below to see if any firmware updates are available for download for your Digitrax equipment.
In addition throttle hardware conversions are available if you want to convert from walk around operation to wireless. Please click here for more information on conversions that are available.
BXP88 Firmware
Nov. 29, 2017 (version 0.2) - Maintenance Update.
DB210 Firmware
Moved stm32 driver to device tree configuration. Added support for setting fixed configuration and read from device tree for ENET ETH interface and PHY in mcux driver. Added support for device that do not use SMI for PHY setup in mcux driver. Added support for multiport gPTP in nativeposix driver. This allows gPTP bridging testing. Welcome to the NETGEAR Download Center!! To find documentation, firmware, software, or other files, enter a whole or partial Model number in the text search box. DS4Windows is a portable program that allows you to get the best experience while using a DualShock 4 on your PC. By emulating a Xbox 360 controller, many more games are accessible.
Nov. 9, 2020 (version 0.1) - March 6th, 2020 update
- Digitrax Device Firmware Update Instructions
Instructions on how to updated your firmware using the DigiIPL tool.
- SoundLoader (version 2.5.1)
The free SoundLoader 2.5.1 program gives the user the ability to overlay sounds in SoundFX project files. Customize sound schemes to suit you! Packaged also contains DigiIPL 2.8.2 and the Microsoft Visual C++ 2008 Redistributable Package. ...read more
DB210 OPTO Firmware
Nov. 9, 2020 (version 0.1) - March 6th, 2020 update
- Digitrax Device Firmware Update Instructions
Instructions on how to updated your firmware using the DigiIPL tool.
- SoundLoader (version 2.5.1)
The free SoundLoader 2.5.1 program gives the user the ability to overlay sounds in SoundFX project files. Customize sound schemes to suit you! Packaged also contains DigiIPL 2.8.2 and the Microsoft Visual C++ 2008 Redistributable Package. ...read more
DB220 Firmware
Nov. 9, 2020 (version 0.1) - March 6th, 2020 update
- Digitrax Device Firmware Update Instructions
Instructions on how to updated your firmware using the DigiIPL tool.
- SoundLoader (version 2.5.1)
The free SoundLoader 2.5.1 program gives the user the ability to overlay sounds in SoundFX project files. Customize sound schemes to suit you! Packaged also contains DigiIPL 2.8.2 and the Microsoft Visual C++ 2008 Redistributable Package. ...read more
DCS210 Firmware
Nov. 9, 2020 (version 0.4) - March 6th, 2020 update
- Digitrax Device Firmware Update Instructions
Instructions on how to updated your firmware using the DigiIPL tool.
- SoundLoader (version 2.5.1)
The free SoundLoader 2.5.1 program gives the user the ability to overlay sounds in SoundFX project files. Customize sound schemes to suit you! Packaged also contains DigiIPL 2.8.2 and the Microsoft Visual C++ 2008 Redistributable Package. ...read more
DCS240 Firmware
Nov. 9, 2020 (version 0.4) - March 6th, 2020 update
- Digitrax Device Firmware Update Instructions
Instructions on how to updated your firmware using the DigiIPL tool.
- SoundLoader (version 2.5.1)
The free SoundLoader 2.5.1 program gives the user the ability to overlay sounds in SoundFX project files. Customize sound schemes to suit you! Packaged also contains DigiIPL 2.8.2 and the Microsoft Visual C++ 2008 Redistributable Package. ...read more
DT402 Firmware
Oct. 10, 2016 (version 2.1) - Maintenance Update, Please read the R21 release notes.
- SoundLoader (version 2.5.1)
The free SoundLoader 2.5.1 program gives the user the ability to overlay sounds in SoundFX project files. Customize sound schemes to suit you! Packaged also contains DigiIPL 2.8.2 and the Microsoft Visual C++ 2008 Redistributable Package. ...read more
DT402 Reversion
Aug. 5, 2016 (version 2.1) - This file allows you to revert your DT402 R2.0’s back to R1.7 if you experience problems.
DT500 Firmware
Oct. 10, 2016 (version 0.1) - Initial Release
- SoundLoader (version 2.5.1)
The free SoundLoader 2.5.1 program gives the user the ability to overlay sounds in SoundFX project files. Customize sound schemes to suit you! Packaged also contains DigiIPL 2.8.2 and the Microsoft Visual C++ 2008 Redistributable Package. ...read more
DT602 Firmware
Sept. 18, 2020 (version 0.1) - Sub-Version: 0.2
- SoundLoader (version 2.5.1)
The free SoundLoader 2.5.1 program gives the user the ability to overlay sounds in SoundFX project files. Customize sound schemes to suit you! Packaged also contains DigiIPL 2.8.2 and the Microsoft Visual C++ 2008 Redistributable Package. ...read more
LNRP Firmware
Oct. 20, 2015 (version R4) - This code improves the Railsync current drive capability and protection and allows better performance on bigger layouts with more connected loads.
- Digitrax Device Firmware Update Instructions
Instructions on how to updated your firmware using the DigiIPL tool.
- SoundLoader (version 2.5.1)
The free SoundLoader 2.5.1 program gives the user the ability to overlay sounds in SoundFX project files. Customize sound schemes to suit you! Packaged also contains DigiIPL 2.8.2 and the Microsoft Visual C++ 2008 Redistributable Package. ...read more
LNWI Firmware
Nov. 28, 2020 (version 0.2) - Support for TCS throttles
PR1 Drivers
April 24, 2013 (version 1.0) -
PR2 Software
Oct. 12, 2020 (version 2.5.1) - All required software for the PR2 is included in the SoundLoader download. ...read more
- SoundLoader
2.1 now contains DigiIPL 2.0 2.1.1 fixed and issue with apps starting at startup. 2.2 Fixed link to Help > 'Help Topics...' 2.3 Including bug fixes 2.4 Includes DigiIPL 2.2 2.5 Updates DigiIPL to 2.8.1. 2.5.1 Updated DigiIPL to 2.8.2.
PR3 Firmware
Zephyr Port Devices Driver Download Win 7
March 6, 2014 (version 1.0) - Update for 64 bit operating systems.
- PR3 1.0 Firmware
This is a product upgrade to expand the PR3 beyond the original 32 bit operating system design capability. Users on 32 bit systems and whose PR3's are working fine do not need to modify their PR3's. This IPL is only recommended for users with 64 bit systems or have had issues with Vista/Win7/Win8.
- PR3 1.0 Update Instructions (for 64 bit systems)
Instructions for the PR3 1.0 update. Please read before trying to install the 1.0 update!
PR3 / PR4 Installation Instructions
Sept. 11, 2013 (version 1.0) -
- PR3 / PR4 Windows 7 Instructions
These instruction will get you up and running on Windows 7 with the PR3 & PR4!
- PR3 / PR4 Windows 8 Instructions
These instruction will get you up and running on Windows 8 with the PR3 & PR4!
- PR3 / PR4 Windows 8.1 Instructions
These instruction will get you up and running on Windows 8.1 with the PR3 & PR4!
- PR3 / PR4 Windows 10 Instructions
These instruction will get you up and running on Windows 10 with the PR3 & PR4!
- PR3 / PR4 Mac OSX Instructions
These instruction will get you up and running on Mac OSX with the PR3 & PR4!
PR3 / PR4 Windows 10 Drivers
Oct. 12, 2020 (version 2.5.1) -
- SoundLoader
2.1 now contains DigiIPL 2.0 2.1.1 fixed and issue with apps starting at startup. 2.2 Fixed link to Help > 'Help Topics...' 2.3 Including bug fixes 2.4 Includes DigiIPL 2.2 2.5 Updates DigiIPL to 2.8.1. 2.5.1 Updated DigiIPL to 2.8.2.
Zephyr Port Devices Driver Download Windows 10
PR3 / PR4 Windows 2000 Drivers
Nov. 4, 2011 (version 1.0) -
- SoundLoader
2.1 now contains DigiIPL 2.0 2.1.1 fixed and issue with apps starting at startup. 2.2 Fixed link to Help > 'Help Topics...' 2.3 Including bug fixes 2.4 Includes DigiIPL 2.2 2.5 Updates DigiIPL to 2.8.1. 2.5.1 Updated DigiIPL to 2.8.2.
PR3 / PR4 Windows XP, Vista, 7, and 8 Drivers
Nov. 4, 2011 (version 1.0) -
- SoundLoader
2.1 now contains DigiIPL 2.0 2.1.1 fixed and issue with apps starting at startup. 2.2 Fixed link to Help > 'Help Topics...' 2.3 Including bug fixes 2.4 Includes DigiIPL 2.2 2.5 Updates DigiIPL to 2.8.1. 2.5.1 Updated DigiIPL to 2.8.2.
PR4 Firmware
Jan. 9, 2018 (version 0.0) - Added legacy support OpSw
UR92 Firmware
Dec. 10, 2015 (version R8) - This rev 8 fixes UR92 link issues with multiple UR devices on the LocoNet and improves Duplex reliability. We want to thank Frank Fezzie Jr. and others that have supported him in helping isolated this intermittent problem. Merry Christmas! ...read more
- Digitrax Device Firmware Update Instructions
Instructions on how to updated your firmware using the DigiIPL tool.
- SoundLoader (version 2.5.1)
The free SoundLoader 2.5.1 program gives the user the ability to overlay sounds in SoundFX project files. Customize sound schemes to suit you! Packaged also contains DigiIPL 2.8.2 and the Microsoft Visual C++ 2008 Redistributable Package. ...read more
Zephyr Express (DCS52) Firmware
Feb. 1, 2019 (version 0.1) - Function update.
- Digitrax Device Firmware Update Instructions
Instructions on how to updated your firmware using the DigiIPL tool.
- SoundLoader (version 2.5.1)
The free SoundLoader 2.5.1 program gives the user the ability to overlay sounds in SoundFX project files. Customize sound schemes to suit you! Packaged also contains DigiIPL 2.8.2 and the Microsoft Visual C++ 2008 Redistributable Package. ...read more
Zephyr Xtra (DCS51) Firmware
July 27, 2015 (version R5) - Small timing changes for the LED driver hardware update.
- Digitrax Device Firmware Update Instructions
Instructions on how to updated your firmware using the DigiIPL tool.
- SoundLoader (version 2.5.1)
The free SoundLoader 2.5.1 program gives the user the ability to overlay sounds in SoundFX project files. Customize sound schemes to suit you! Packaged also contains DigiIPL 2.8.2 and the Microsoft Visual C++ 2008 Redistributable Package. ...read more
Device Model APIs.
Defines
DEVICE_INIT
(dev_name, drv_name, init_fn, data, cfg_info, level, prio)¶Create device object and set it up for boot time initialization.
This macro defines a device object that is automatically configured by the kernel during system initialization.
dev_name
: Device name.drv_name
: The name this instance of the driver exposes to the system.init_fn
: Address to the init function of the driver.data
: Pointer to the device’s configuration data.cfg_info
: The address to the structure containing the configuration information for this instance of the driver.level
: The initialization level at which configuration occurs. Must be one of the following symbols, which are listed in the order they are performed by the kernel:- PRE_KERNEL_1: Used for devices that have no dependencies, such as those that rely solely on hardware present in the processor/SOC. These devices cannot use any kernel services during configuration, since they are not yet available.
- PRE_KERNEL_2: Used for devices that rely on the initialization of devices initialized as part of the PRIMARY level. These devices cannot use any kernel services during configuration, since they are not yet available.
- POST_KERNEL: Used for devices that require kernel services during configuration.
- APPLICATION: Used for application components (i.e. non-kernel components) that need automatic configuration. These devices can use all services provided by the kernel during configuration.
prio
: The initialization priority of the device, relative to other devices of the same initialization level. Specified as an integer value in the range 0 to 99; lower values indicate earlier initialization. Must be a decimal integer literal without leading zeroes or sign (e.g. 32), or an equivalent symbolic name (e.g. #define MY_INIT_PRIO 32); symbolic expressions are not permitted (e.g. CONFIG_KERNEL_INIT_PRIORITY_DEFAULT + 5).
DEVICE_AND_API_INIT
(dev_name, drv_name, init_fn, data, cfg_info, level, prio, api)¶Create device object and set it up for boot time initialization, with the option to set driver_api.
This macro defines a device object that is automatically configured by the kernel during system initialization.
The driver api is also set here, eliminating the need to do that during initialization.
dev_name
: Device name.drv_name
: The name this instance of the driver exposes to the system.init_fn
: Address to the init function of the driver.data
: Pointer to the device’s configuration data.cfg_info
: The address to the structure containing the configuration information for this instance of the driver.level
: The initialization level at which configuration occurs. Must be one of the following symbols, which are listed in the order they are performed by the kernel:- PRE_KERNEL_1: Used for devices that have no dependencies, such as those that rely solely on hardware present in the processor/SOC. These devices cannot use any kernel services during configuration, since they are not yet available.
- PRE_KERNEL_2: Used for devices that rely on the initialization of devices initialized as part of the PRIMARY level. These devices cannot use any kernel services during configuration, since they are not yet available.
- POST_KERNEL: Used for devices that require kernel services during configuration.
- APPLICATION: Used for application components (i.e. non-kernel components) that need automatic configuration. These devices can use all services provided by the kernel during configuration.
prio
: The initialization priority of the device, relative to other devices of the same initialization level. Specified as an integer value in the range 0 to 99; lower values indicate earlier initialization. Must be a decimal integer literal without leading zeroes or sign (e.g. 32), or an equivalent symbolic name (e.g. #define MY_INIT_PRIO 32); symbolic expressions are not permitted (e.g. CONFIG_KERNEL_INIT_PRIORITY_DEFAULT + 5).api
: Provides an initial pointer to the API function struct used by the driver. Can be NULL.
DEVICE_DEFINE
(dev_name, drv_name, init_fn, pm_control_fn, data, cfg_info, level, prio, api)¶Create device object and set it up for boot time initialization, with the option to device_pm_control.
This macro defines a device object that is automatically configured by the kernel during system initialization.
The driver api is also set here, eliminating the need to do that during initialization.
Zephyr Port Devices Driver Download
dev_name
: Device name.drv_name
: The name this instance of the driver exposes to the system.init_fn
: Address to the init function of the driver.data
: Pointer to the device’s configuration data.cfg_info
: The address to the structure containing the configuration information for this instance of the driver.level
: The initialization level at which configuration occurs. Must be one of the following symbols, which are listed in the order they are performed by the kernel:- PRE_KERNEL_1: Used for devices that have no dependencies, such as those that rely solely on hardware present in the processor/SOC. These devices cannot use any kernel services during configuration, since they are not yet available.
- PRE_KERNEL_2: Used for devices that rely on the initialization of devices initialized as part of the PRIMARY level. These devices cannot use any kernel services during configuration, since they are not yet available.
- POST_KERNEL: Used for devices that require kernel services during configuration.
- APPLICATION: Used for application components (i.e. non-kernel components) that need automatic configuration. These devices can use all services provided by the kernel during configuration.
prio
: The initialization priority of the device, relative to other devices of the same initialization level. Specified as an integer value in the range 0 to 99; lower values indicate earlier initialization. Must be a decimal integer literal without leading zeroes or sign (e.g. 32), or an equivalent symbolic name (e.g. #define MY_INIT_PRIO 32); symbolic expressions are not permitted (e.g. CONFIG_KERNEL_INIT_PRIORITY_DEFAULT + 5).api
: Provides an initial pointer to the API function struct used by the driver. Can be NULL.
pm_control_fn
: Pointer to device_pm_control function. Can be empty function (device_pm_control_nop) if not implemented.
DEVICE_NAME_GET
(name)¶Expands to the full name of a global device object.
Return the full name of a device object symbol created by DEVICE_INIT(), using the dev_name provided to DEVICE_INIT().
It is meant to be used for declaring extern symbols pointing on device objects before using the DEVICE_GET macro to get the device object.
name
: The same as dev_name provided to DEVICE_INIT()
DEVICE_GET
(name)¶Obtain a pointer to a device object by name.
Return the address of a device object created by DEVICE_INIT(), using the dev_name provided to DEVICE_INIT().
name
: The same as dev_name provided to DEVICE_INIT()
DEVICE_DECLARE
(name)¶Declare a static device object.
This macro can be used at the top-level to declare a device, such that DEVICE_GET() may be used before the full declaration in DEVICE_INIT().
This is often useful when configuring interrupts statically in a device’s init or per-instance config function, as the init function itself is required by DEVICE_INIT() and use of DEVICE_GET() inside it creates a circular dependency.
name
: Device name
Functions
device_get_binding
(const char *name)¶Retrieve the device structure for a driver by name.
Device objects are created via the DEVICE_INIT() macro and placed in memory by the linker. If a driver needs to bind to another driver it can use this function to retrieve the device structure of the lower level driver by the name the driver exposes to the system.
name
: device name to search for.
device_config
¶Zephyr Port Devices Driver Downloads
#include <device.h>Static device information (In ROM) Per driver instance.
name
: name of the deviceinit
: init function for the driverconfig_info
: address of driver instance config information
device
¶Runtime device structure (In memory) Per driver instance.
device_config
: Build time config informationdriver_api
: pointer to structure containing the API functions for the device type. This pointer is filled in by the driver at init time.driver_data
: driver instance data. For driver use only