Currently, the JNI bindings are generated by Swig and, unfortunately, the interface available through Java is lower-level than that for C++ (ie, direct access to the ctre code through the JNI bindings, rather than an interface on top of that), but it does work. See eclipse plugins for some short samples. There are a couple of short unit tests as placeholders. Still needs some cleaning up. Change-Id: Iae2f74693ca6b80bf7d5aca0625c66aa6e0b7f85 Added quick samples for C++/Java CAN Talon stuff. Change-Id: I3acb27d6fd5568d88931e0d678c09973d436735d
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