Installing the CE Toolchain
Download the latest stable toolchain release below:
If you would rather try the “nightly” build (which includes the latest features and bugfixes before an official release) you can find it here.
Extract the zip to a folder without any spaces in the full path, e.g.
cedev.batinside the extracted CEdev folder to launch the toolchain environment. You may have to allow the script to be run depending on the user account control.
If you want to avoid using the
cedev.batscript, you can extend the PATH environment variable to point to the
CEdev/bindirectory. Here is a guide.
On Linux or Mac
Extract the archive to a path without any spaces, e.g.
Extend the PATH environment variable to point to
CEdev/binby modifying .bashrc, .zshrc, or whatever flavor the OS uses. An example command may be:export PATH=/<insert path here>/CEdev/bin:$PATH
The toolchain update process is the exact same as installation - the only extra step is to delete the current
CEdev folder if it exists beforehand.
Open a build session by double-clicking
cedev.bat on Windows or launching a terminal session on Linux/macOS.
Navigate to the examples folder using the
cd examples command.
This folder contains example projects that you can build and modify to learn how to write different programs.
Navigate the to the hello_world example project using the command
make and press enter.
This command invokes the compiler, assembler, and linker creating the program
Use the CEmu emulator to run the built program, or transfer it to a real calculator using TI Connect CE.
If on Windows you encounter errors such as
Missing vcruntime140.dll, install the latest Microsoft Visual C++ Redistributable package.
The download can be found at this link, depending on the architecture you will need to install one of either vc_redist.x86.exe or vc_redist.x64.exe.
Antivirus software (e.g. Windows Defender) may flag binaries in the
CEdev/bin directory as false positives, and either quarantine/remove the files or prevent them from running.
This may result in build errors such as being unable find/execute fasmg.
Please whitelist or disable scanning in
CEdev/bin to prevent these false positives from occurring.
Every CE Toolchain project has the following folder structure. It is highly recommended to keep the same structure to ensure that your project can build with future toolchain versions.
This is the directory where all source files can be placed. Sources are built automatically if they end in a
.cppextension, and can be edited with any text editor or IDE. Subdirectories are allowed as long as they do not contain spaces.
Compiled C/C++ files are placed here, and contain intermediate assembly output.
This is where the final linked calculator program will be placed, ending with a
A text file used by
maketo build the program. There are options for setting the program name, description, and more.
This is a 16x16 icon that is displayed in shells such as Cesium.
A text file that describes the program’s operation.
This file can be loaded into CEmu’s Autotester to test and validate the program. This feature may be useful for creating testable code coverage.