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.

CC2642R: Inquiries about RF Design parameters on sysconfig

Part Number: CC2642R
Other Parts Discussed in Thread: LAUNCHXL-CC26X2R1, , SYSCONFIG, UNIFLASH

Hi Experts,

Our customer was developing their system with CC2642R, and they plan to support/add DTM(Direct Test Mode) function. therefore, customer is verifying the Host_test source code for LAUNCHXL-CC26X2R1. Since the current customer’s board is supporting “Internal BIAS, Single-Ended mode RFN”, they changed this parameter on sysconfig. However, it seems there is not any difference between before and after making changes. This means, this change does not affect it. So, customer is asking how they should change “Single-Ended setting”. Customer is using “SimpleLink CC13xxCC26xx SDK 6.30.0.84”.  Can we have your experts advice/comments on this, please?

And the, as far as I checked Host_test on SDK(ver 7.10.00.98), I was not able to select “Internal BIAS, Single-Ended mode RFN”, and it seems compile-error occurs, as well

 

It will be appreciated if you share any advice/comments on this.

Best regards,

Miyazaki

  • Hi Miyazaki,

    Your v7.10 setup is witnessing the SysConfig error since the LAUNCHXL-CC26X2R1 does not support any front-end configuration other than "Internal Bias, Differential mode".  You can select "USE CUSTOM BOARD" from the "Board View" to resolve this.

    For the customer's part, after changing to "Internal Bias, Single-Ended mode RFN" they should be able to select ti_radio_config.h from the "Generated Files" view to observe that definitions have changed from FRONTEND_24G_DIFF_RF to FRONTEND_24G_SE_RFN.  This will be used during the project build.  Is the customer's board encountering any issues while using this setup?

    Regards,
    Ryan

  • Hello Ryan,

    Thank you for your reply.

    I shared your comments with our customer, and I received some feedback. When customer selected "USE CUSTOM BOARD" on sysconfig, they noticed PIO setting was changed. So, customer re-changed PIO setting to their pin-configuration again. And then, customer was able to confirm the change from FRONTEND_24G_DIFF_RF to FRONTEND_24G_SE_RFN in  ti_radio_config.h file after changing to "Internal Bias, Single-Ended mode RFN" certainly, however, there is no different between default hex file and this file. This means, customer is considering  ti_radio_config.h file does not affect this compile and there may be linker issue or something.

    And then, customer did a similar test with Simple_peripheral_oad_offchip Sample project in SDK 7.10.00.98. In this case, it seems there is difference of hex file after changing to “Single ended” configuration.

    Would you check this behavior, please?

    Best regards,

    Miyazaki

  • Hi Miyazaki,

    I believe updating the SysConfig to use a specific front-end should be enough for host_test to use the set front-end. Is the customer not seeing a performance difference or are they seeing unexpected behavior after flashing the device?

    Best Regards,

    Jan

  • Hello Ryan,

    My name is Kuwashima, and I am Mr. Miyazaki's client.
    Thank you for answering.
    I have a question about your answer.
    Why can you change the frontend by flashing the same xxx.hex file to the device?
    I flash the xxx.hex file with UniFlash, but I don't think the front end will change with the same file.

    The results of my consideration are as follows.
     1-1. host_test (Original: Internal Bias, Differential mode)
     1-2. host_test (Custom: Internal Bias, Single-Ended mode RFN/Custom board)
     1-3. Simple_peripheral_oad_offchip (Original: Internal Bias, Differential mode)
     1-4. Simple_peripheral_oad_offchip (Custom: Single-Ended mode RFN/Custom board)

    After building, 1-1. and 1-2. Hex files were the same.
    Also, 1-3. and 1-4. are different, and there are changes that seem to be Single-Ended Mode RFN.

    See attachment.

    Based on the above, I believe host_test is not linking ti_radio_config.h which is generated by configuring sysconfig.
    Could you please release the correct host_test source code?

    Best regards,

    Kuwajima

  • Hi Kuwajima,

    I was able to reproduce the behavior you are seeing on my end. Taking a step back, does your application use host_test to operate or are you using host_test for some testing?

    Best Regards,

    Jan

  • Hello Ryan,

    Thank you for your reply.
    I design based on simple_peripheral_oad_offchip in my application.
    So front-end configuration in the product is not a problem.
    Also, the product's application firmware does not implement PTM as the evaluation function should be removed.
    Therefore, we plan to use HostTest for RF testing in production and then write the application firmware.

    Also, TI's RF test and Bluetooth certification documents say to use Host_Test.
    Please release the source code as soon as possible in the sense of preparing a standard development environment.

    Best Regards,

    Kuwajima

  • Hi Kuwajima,

    Understood. The source code for the host_test project is present in the SDK and can be found in the examples folder. Specifically, it can be found at the following directory: {SDK_INSTALL_DIR}\examples\rtos\CC26X2R1_LAUNCHXL\ble5stack\host_test

    After importing your project, you can modify the source code files located in the application:

    Best Regards,

    Jan

  • Hello Ryan,

    Thank you for your reply.

    But it doesn't seem to have the information I want.
    As I wrote last time, 1-1. and 1-2. use files imported from {SDK_INSTALL_DIR}\examples\rtos\CC26X2R1_LAUNCHXL\ble5stack\host_test.
    I would like the source code where the frontend settings are updated.
    This is because I make changes at my own discretion and am afraid that some changes may be overlooked.
    At the very least, I would like snippet information to change this part of this file.

    best regards,

    Kuwashima

  • Hi Kuwashima,

    I believe I have found where this is set in the host_test project. It is located in the ble_user_config.c file within the iCallBLE file. At the following lines:

    This file is a linked resources which means any modification to this file will change the SDK file as well and impact all projects that reference this file. I recommend replacing this linked resource with a local copy to allow you to modify as needed without impacting other projects.

    Best Regards,

    Jan

  • Hello Ryan,

    Thank you for your reply.
    I have solved the problem.

    It seems that the RF Front-End cannot be easily changed in SysConfig of host_test.

    I was able to confirm the change by following the steps below. (No need to change SysConfig)
    1. Copy ble_user_config.c from the link to your own iCallBLE folder.
    2. Copy ble_user_config.h from the link to your own iCallBLE folder.
    3. Change RF_FE_DIFFERENTIAL on line 343 of ble_user_config.h in your own iCallBLE folder to RF_FE_SINGLE_ENDED_RFN.


    best regards,

    Kuwashima