• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 30 subscribers
  • Views 458 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

AWR1843AOPEVM: AWR1843AOPEVM

TSRDM
Prodigy 690 points
Part Number: AWR1843AOPEVM
Other Parts Discussed in Thread: CC2640R2F, AWR1843

Hi TI mmWave Technical Support, I am helping a University Student who has some technical questions to help complete his Senior project which uses our AWR1843AOPEVM for development, please see below. Unfortunately we have discontinued the ability for University Students to ask technical support question to our e2e. I was directed to enter the request on his behalf. Please see below, thank you in advance for helping our future customer! 

**********************************

I've learned quite a bit about the EVM.  In particular, I noted that the EVM is capable of communicating information via Bluetooth.  The UART and logger output of the AOP device are routed to the Bluetooth chip (and also to the UART-USB converter chip).  I am able to interact with the EVM via USB so that I can use the cloud-based visualizer.    But I would prefer to communicate with the AOP via Bluetooth so that I can perform some processing on my IOS device.  

 

However, the Bluetooth device seems to be configured with some generic code.  For example, it broadcasts the name "Simple Peripheral" and has only two services.  The first service is the device information service and the characteristics for that service are non-specified (e.g., Model Number String = "Model Number").  The other service is 0xFFF0, which seems to be a custom service.  The characteristics for that service are 0xFFF1, 0xFFF2, 0xFFF4, 0xFFF5.  A snapshot of some debug output is attached.  After some digging, I came across the following TI website: (https://software-dl.ti.com/lprf/simplelink_cc2640r2_sdk/1.30.00.25/exports/examples/rtos/CC2640R2_LAUNCHXL/blestack/simple_peripheral/README.html#char1, which indicates to me that the Bluetooth chip is flashed with some generic/baseline code.

 

I've been unable to find any information online regarding using Bluetooth with the EVM.  Can you help me out with this?  Does the part need to be flashed with some particular code to get it to work with the EVM?  Also, do I need any additional HW to do the flashing (e.g., the BOOST module)?

 

Any help you can provide would be greatly appreciated.

  • 0
    TI__Mastermind 35255 points

    Hello Dave,

    There is no information available for the use case that the customer has mentioned.
    They will have to integrate the EVM with a Bluetooth capable microcontroller and then the data needs to be transferred over an interface like SPI/I2C/UART depending upon the Bluetooth microcontroller. Then they will have to go through the user guide/ documentation of that particular chip and then implement the model they desire.
    They will need to get in touch with the respective team from Bluetooth controller if they want more details on how to modify their program/SDK.
    We do not have any integrations readily available.

    Regards,
    Saswat Kumar

  • 0 in reply to Saswat Kumar
    TI__Prodigy 690 points

    Hi Saswat, our customer is asking for directions on how to enable the the already integrated TI CC2640R2F Bluetooth Low Energy SoC that the Radar team designed into the AWR1843AOPEVM so the  AWR1843AOPEVM can communicate with their iOS device. How does the user of  AWR1843AOPEVM use the integrated integrated TI CC2640R2F Bluetooth Low Energy SoC to communicate with the outside world? Thanks, Dave Melinger 847 302 0438

  • 0 in reply to TSRDM
    TI__Mastermind 35255 points

    Hello Dave,

    Currently there is no reference design we have to support the integration between TI CC2640R2F Bluetooth Low Energy SoC and the AWR1843.
    I have provided the interfaces that could be utilized to communicate with SOC. The user will have to architect the design based on his/her requirements.
    For questions related to the bluetooth controller, you can raise another E2E thread with the bluetooth part and they will be able to provide you the right guidance to modify the application on the bluetooth controller.

    Regards,
    Saswat Kumar