• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 53 subscribers
  • Views 1948 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.

CC2640R2F: What must we update source code porting from CC2640 to CC2640R2?

Shinya Muramatsu
Expert 1010 points

Part Number: CC2640R2F
Other Parts Discussed in Thread: CC2640, SYSBIOS

Hello,I'm FAE of distributor in Japan.
Customer ask me about 4 questions as bellow.
Please answer or advice us.

[Background]
They start to develop CC2640F128 already 1st,then they changed device to CC2640R2 on same board.
Customer already confirmed their source code in CC2640F128 with ble_sdk_02_02_01_18. on CCSv6.
Now they are porting their source code to CC2640R2 SDK on CCSv7.
They want multi_role function. and they add their own code to TI example source code of CC2640R2 SDK.
They changed pin assign of SPI and UART.

[Questions]
Q1)Please infrom us where we jump bellow link.
<software-dl.ti.com/.../cc2640-to-cc2640r2.html

Upgarade and Compatibility information link jump 404 error.(blue color hatching in bellow).

2)Do you have all difference changing peripheral drivers or stack list from CC2640 to CC2640R2? 
    They only changed pin assign part on CC2640R2_launchxl.C and pin_init on main.c for matching their board,
    but program goes to infinite loop(around ti_sysbios_family_arm_m3_Hwi_excHandler__I from MAP info).
   Then they add "call uart_init and SPI_init" before "call each *_open" in their own code(We found comment of each *_open)
   After above additional,program went to main loop. we don't  know what we need to change another periperal drivers or stack.

3)How should we debug about BLE communication RX issue?
   Now they couldn't catch to receive BLE radio communication from outside TX.
   They tried to add advertise on events,they can detect advertise from CC2640R2  outside.
   It means BLE TX side operate rightly.

4)How can they integrate ble_sdk_02_02_01_18 on CC2640R2 in CCSv7?
   Is it easy way?

Regards,
Shinya Muramatsu

  • 0
    Guru 735705 points
    If you install simplelink_cc2640r2_sdk_1_00_00_22 ,you can refer to poring guide under file:///C:/ti/simplelink_cc2640r2_sdk_1_00_00_22/docs/blestack/html/cc2640/ble-sdg/cc2640-to-cc2640r2.html#
  • 0
    TI__Guru* 83901 points
    Hi Shinya,

    Sorry about the broken link, it should point to your local simplelink stack release notes (e.g. file:///C:/ti/simplelink_cc2640r2_sdk_1_00_00_22/release_notes_simplelink_cc2640r2_sdk_1_00_00_22.html ).

    The list of chenges drivers:
    PDMCC26XX.h
    PDMCC26XX_util.h
    PINCC26XX.h
    PWMTimerCC26XX.h
    UARTCC26XX.h
    WatchdogCC26XX.h

    The changes are documented in each drivers headers.

    I'm not sure what you mean by "integrate ble_sdk_02_02_01_18 on CC2640R2". The general approach for porting should be to start from an R2 stack example project (such as multi role).
  • 0 in reply to Marie H
    Expert 1010 points
    Marie-san

    Thank you for support.
    I cleared Q1) and Q2).

    About Q3)
    Please help us to debug.

    > 4)How can they integrate ble_sdk_02_02_01_18 on CC2640R2 in CCSv7?
    > Is it easy way?

    I explain about Q4) meaning.
    They already integrated their own software with ble_sdk_02_02_01_18 on CC2640 in CCSv6 before.
    But they changed device from CC2640 to CC2640R2.
    They are debugging integrate own software with cc2640r2_sdk_1_00_00_22 on CC2640R2 in CCSv7 now.
    If they can directly import from CC2640 software to CC2640R2 with a few customizing ,it is very easy.(they don't mind stack version now.)
    Do you have aney idea?

    Regards,
    Shinya Muramatsu
  • 0 in reply to Shinya Muramatsu
    TI__Guru* 83901 points
    Hi Shinya,

    I'm glad we cleared a few things up :)

    About Q3: If I understand correctly they have
    - started from an example project in R2 stack
    - imported their 2.2.1 code and made necessary changes listed in the porting guide
    - they have no compiler errors or warnings

    When they load the project into CC2640R2, they can see CC2640 advertise, but the CC2640R2 can not discover other BLE devices.

    What is their own software doing?
  • 0 in reply to Marie H
    Expert 1010 points
    Marie-san

    Thank you for quick response and Sorry to late reply.

    Their own software communicate with outside device by wire,
    Before BLE communication.
    They didn't change multi role part.

    Regards,
    Shinya Muramatsu.
  • 0 in reply to Shinya Muramatsu
    TI__Guru* 83901 points
    Hi Shinya,

    It sounds like they added a driver for communicating over wire, like SPI? All these drivers exist in CC2640R2 stack as well. I don't understand the problem.