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.
I am putting together a project for the CC1352R1 based on an Easylink Project.
In the display project, the LCD booster pack shows up in the hardware list:
But in the EasyLink based project, it does not show up:
How do I get the LCD booster pack to show up in the list?
See if this post: https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz/f/156/t/969209?LAUNCHXL-CC1312R1-LCD-display could help you. Basically you just have to setup the correct SPI pins to use the LCD boosterpack.
Thanks, I replied in that thread. 8^)
I know I can set the pins manually, but why do that, when, somewhere in TI land, someone has a way to make my launch pad aware of that specific LCD.
No, we are not detecting if a boosterpack is connected. In the Display example some extra lines are added to the .syscfg file to make it easier to select the display boosterpack and to run the example.
If you want the same functionality in other project you have to alter the .syscfg file for that project.
I think I have reached an impasse.
The config file for the display example contains:
var SharpLCD = scripting.addHardware("/ti/boards/boosterpacks/BOOSTXL-SHARP128");
but for the life of me I cannot find the location of /ti/boards/boosterpacks/BOOSTXL-SHARP128, does anyone know where it can be found?
Thanks. Finder really doesn't want me to see hidden files, I had to use the terminal. Which raises the question:
how does sysconfig find the file with that path?
From what I understand, this is how the software is designed. The idea is that the data the tool use to find information about the HW the user selects are placed in .meta folders. The include/ search path for SysConfig ignores the ".meta" in the patch and expect that the data is found somewhere in the tree.
Yeah, I do have some progress to report.
I copied "var SharpLCD = scripting.addHardware("/ti/boards/boosterpacks/BOOSTXL-SHARP128");" to the start of the EasyLink based config file. I changed var to const, since that was what was used in the new config, and the LCD showed up in the hardware list and I was able to add it. As soon as I get a new LCD, I will test it and share the results. It did compile with no errors.
I get to report that this indeed allowed me to add the LCD to the config and use it.