LAUNCHXL-CC2640R2: UART Configuration

Hi,

Which SDK are you using?

Have you referred to the UART example here: http://dev.ti.com/tirex/explore/node?node=AExXVVS1Iq3nAR4kS7oWXg__krol.2c__LATEST
It shows how to initialize/configure/use UART.

I have notified the BLE team in case you have further questions.

Regards,
Toby

Hi Toby,

Thanks for your fast response. I have read your recommended site and known which file need to be modified. The file is located at C:\ti\simplelink_cc2640r2_sdk_4_20_00_04\source\ti\blestack\boards\CC2640R2_LAUNCHXL\CC2640R2_LAUNCHXL.c

After finding this file, I just realized that when the example project is imported to CCS, we cannot find all files (by using Crtrl + H) that are necessary for compilation. Because the project links or refers to different source and header files on this location C:\ti\simplelink_cc2640r2_sdk_4_20_00_04. 

Maybe I will get lost on managing the source files when I refer again to other example or use example as reference project.

Do we have any way to manage the source file or to know which files are necessary for the example project? Any document/site can be helpful.

Thanks,

Dang

Hi Dang,

I would basically say that all the files imported by the project are required. There is no point in trying to remove some files (because the corresponding code won't be linked and won't take any place on the device).

In general, I suggest users to use the BLE stack and the SDK as a kind of grey box. No need to deeply understand what is in the libraries and files imported. Focus on the application files (the one you have written).
To finish, it is true that CCS cannot find all the files using the Ctrl + H command. When I started working with BLE, I was doing the research on the whole SDK... but with the time I discovered that every thing that is hidden by CCS does not really need my attention (except maybe the files generated by SysConfig but you are not using SysConfig :) )

I hope this will help,

Kind regards,

Hi Clément,

I got your points. It is not convenient to find all references just only with CCS because I think CCS does not  perform indexing all source files.

Fox example, when I am seaching for which API refers to variable displayUartHWAttrs to initialize UART. I see that this variable is used by another variable Display_config. So normally I will use command "Ctrl + Alt + H" to see which API calls Display_config. But this technique is not quite helpful in this case. Finallly I end up with using Notepadd++ and search all source files in folder C:\ti\simplelink_cc2640r2_sdk_4_20_00_04 (using feature "Find in Files"), the results return with a lot of files and I scroll down to find that API Display_doOpen in Display.c refers to that variable. These steps are quite painful and it takes some time to get a final result. :((

Do you have any suggestion in my case? 

Thanks,

Dang.

Hi Dang,

For this case, using the "F3" key on the symbol should lead you to the symbol definition.

Regards,

Hi Clément,

I mean the feature "Open Call Hierarchy" with variable in CCS , because the CCS does not indexing all source files.So this feature is useless. Need to seach for all files with Notepad++ as I mentioned in above comment.

Regards,

Dang