Add all of the most recent headers and .SOs Also make DriverStation work with the new FRC comm protocol, using the new functions for getting status data Change-Id: I1c7fc5f90e72c5fbebf87d9923ce0967ed0ef3bc Initial HAL support for v13 ds Change-Id: I9a7f37ef8e24241598fa3981cb3df30c07c52e0f New ds stuff in the HAL Change-Id: I025910625453baf63f79f49bbc70ba8b2f093f50 New ds stuff in C++ Joysticks are still todo Driver station IO is pulled out Change-Id: I1bb59037c097713bd943e7bef00e12f67f13c3ac New ds works in C++ and Java. Joysticks still todo Change-Id: Ic93f8686856761badc592eceaf05964f52355578 Make joysticks work again with the v13 image protocol Change-Id: Ief7ee95d3398c2262ca07ab7d60499af3c8f60f7
Purpose
The HAL is a hardware abstraction layer that provides a uniform interface that can be used to access a number of primarily I/O features in the underlying platform. The features include:
- Analog input, accumulation and triggers
- PWM, Relay and Solenoid output
- Digital input and output
- I2C and SPI communication
- Encoders and counters
- Interrupts and Notifiers
The initial goal is to allow a higher level like WPILib to support both the CRIO and the upcoming Athena platform only by changing which version of the HAL it's running on.
Editing
You can always use any text editor and then build with Maven. There
are also eclipse project files so that it can be edited in the same
eclipse environment that teams develop with. For the AthenaXX, this
can be found in the root directory of this project. It imports as an
FRC Robot C++ Eclipse project. The Windriver project can be imported
from the src directory.
Building with Maven
There are multiple build targets that the HAL supports. Instructions for setting up the environment and building each of these is described below. Current targets are listed below:
- All: All of the following targets.
- include: The header files for the HAL.
- Azalea: CRIO C++ build.
- AthenaXX: Athena Dos Equis C++ build.
- AthenaXXJava: Athena Dos Equis Java build with auto-generated JNA wrappers.
Output from each build target is placed in the directory
target/<target-name>. So, the Azalea output is placed in
target/Azalea.
All
Note: Windows only due to the Windriver requirement.
- Ensure that
C:\WindRiver\gnu\3.4.4-vxworks-6.3\x86-win32\binis on the system path so thatccppcandarppccan be accessed. - Set the environment variable
WIND_BASEtoC:\WindRiver\vxworks-6.3. - Ensure that
$HOME/wpilib/toolchains/arm-none-linux-gnueabi-4.4.1/bin/is on the system path so thatarm-none-linux-gnueabi-g++andarm-none-linux-gnueabi-arcan be accessed. - Checkout and install the NI-Libraries from Github: https://github.com/first/NI-Libraries.
- Run the following maven command:
mvn clean install - Success
include
cdinto the include directory:cd include- Run the following maven command:
mvn clean install - Success
Azalea
Note: Windows only.
- Ensure that
C:\WindRiver\gnu\3.4.4-vxworks-6.3\x86-win32\binis on the system path so thatccppcandarppccan be accessed. - Set the environment variable
WIND_BASEtoC:\WindRiver\vxworks-6.3. cdinto the AthenaXX directory:cd AthenaXXcdinto the Azalea directory:cd Azalea- Run the following maven command:
mvn clean install - Success
AthenaXX
- Ensure that
$HOME/wpilib/toolchains/arm-none-linux-gnueabi-4.4.1/bin/is on the system path so thatarm-none-linux-gnueabi-g++andarm-none-linux-gnueabi-arcan be accessed. - Install the include target.
cdinto the AthenaXX directory:cd AthenaXX- Run the following maven command:
mvn clean install - Success
AthenaXXJava
- Ensure that
$HOME/wpilib/toolchains/arm-none-linux-gnueabi-4.4.1/bin/is on the system path so thatarm-none-linux-gnueabi-g++andarm-none-linux-gnueabi-arcan be accessed. - Checkout and install the NI-Libraries from Github: https://github.com/first/NI-Libraries.
- Install the include target.
cdinto the AthenaXXJava directory:cd AthenaXXJava- Run the following maven command:
mvn clean install - Success