This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Step by Step TIVA firmware compilation and update for NIRscan Nano.

Other Parts Discussed in Thread: DLPNIRNANOEVM

In another thread, I have been inquiring about the possibility of having the Bluetooth turned on on startup for the NIRscan Nano. From the answer I have received, this seems possible through a TIVA firmware update. In his reply, a member of the community mentioned I should change a line of code in C:\ti\DLPNIRscanNanoSoftware_1.1.8\Sources\App\include\common.h, recompile the Tiva sources with Code Composer Studio.

In NIRscanNano GUI, under Utilities, updating the TIVA firmware (.bin) seems to be pretty straightforward. However, I have no idea how I should proceed to recompile the source files in Code Composer Studio.  I have downloaded CCS but I have no idea on how to move forward from there. Is there any documentation, tutorials on how to do so? Is this easy enough for you guys to quickly explain me how to do so here in the forum. I basically just need to switch one line of code in common.h to accomplish what I want to.

Thank you very much.

  • Hello Dominic,

    Instructions for installing and configuring CCS are available in the NIRscan Nano EVM User's Guide, appendices C and D.

    There were a couple of files missing from the version 1.1.x downloads, so for compiling that version, please inspect this forum post, which details the process with screenshots and a couple of files which need to be added. Note the two files referred within that post are included in my earlier reply in that thread.

    The version 2.x firmware is also available for download now (http://www.ti.com/tool/dlpnirnanoevm#software), and will follow the same flow with the exception that adding the manual .cproject files is not necessary because they are properly included in the download bundle.

    Please let us know if this allows you to properly build the firmware.