As mentioned at the end of part 2, I've installed Code Composer Studio so that I can upload new code to the development board. following the workshop guide the first step is to generate some code from design studio and import it into CCS. This works fine as long as you don't generate your code into the CCS workstation folder as it will be making a copy of it there.
You can then "Debug" the code to compile and upload it. This may take a few moments the first time as there are some libraries to compile.
I was prompted to upgrade my firmware. I did so and this went smoothly.
Eventually you get into the debugger, and you could step through your code at this point. However for the workshop instructions it's just a case of running the code to see the board in action.
It turned out that I did not need to generate the code, in fact for the proximity demo that did not work and the correct procedure was to import the project directly from the design centre folders. This is a fun demo as it has lights so you can see the interaction. I also tested this one with a glove which gave me a bit more confidence that my glove and overlay tests would work later in the roadtest.
The final demo project is the "phone" demo, this has a haptic feedback and demonstrates how it's possible to cram loads of sensors into one board. This is done with mutual capacitance of adjacent sensors. You can see how TI has built this board by looking on the back.
Next up, I'm going to look at how the technology works with different overlay materials and gloves. So I've reverted the board back to the out of the box code and will look at tuning the settings.
Top Comments