• State TI Thinks Resolved
  • Locked Locked
  • Replies 10 replies
  • Answers 1 answer
  • Subscribers 52 subscribers
  • Views 438 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: OAD file Size

SenseGiz Team
Expert 1800 points

Part Number: CC2640R2F

Hi Sir,

i am using

SDK 1.4

CCS 7.4.0

OAD Tool= Btool

OAD Mode -offChip

1) Using Simple Peripheral OffChip OAD Firmware .bin (file Size 114 Kb) Working with Btool

2) Using Custom1 OAD Firmware .bin(file Size 115 Kb) Below Problem with Btool

3) Using Custom2 OAD Firmware .bin(file Size 108 Kb) Below Problem with Btool

Please Suggest what is exact Problem? is a size or any other issue? ( as Compared with Simple peri. oad Custom size is less)

Regard's

Toravi

  • 0
    Guru 86785 points

    Hi Rohit,

    Maybe you are loading the wrong bin file. From your screenshot multi_role project is selected. Also I suggest you use the latest SDK and CCS version.

    -kel

  • 0 in reply to Markel Robregado
    Expert 1800 points

    Hi kel,

    I am loading the Correct bin file. ble5_multi_role_cc2640r2lp_app.bin

     

    Regard's

    Toravi

  • 0 in reply to SenseGiz Team
    Guru 86785 points

    Rohit Karekar said:
    ble5_multi_role_cc2640r2lp_app.b

    This is not a OAD capable example program. So OAD is not going to happen. Also if I remember correctly multi role example program does not exist at SDK 1.40. Another is that BLE5 example program are big for CC2640R2F and you might encounter memory issues. If you are going to need BLE5 features then I suggest you use other TI BLE MCU that is recommended for BLE5.

    -kel

  • 0 in reply to Markel Robregado
    Expert 1800 points

    Hi kel,

    From Pervious question

    1) Using Simple Peripheral OffChip OAD Firmware .bin (file Size 114 Kb) Working with Btool

    3) Using Custom2 OAD Firmware .bin(file Size 108 Kb) Below Problem with Btool (size Problem) (using ios mobile app OAD is working).

    from the above two, size Simple Peripheral OffChip OAD Firmware .bin (file Size 114 Kb)is less as compared with Simple Peripheral OffChip OAD Firmware .bin (file Size 114 Kb) even then got Memory Error.

    Regard's

    Toravi

  • 0 in reply to SenseGiz Team
    Guru 86785 points

    Hi,

    From the information you provided here initially, you are programming the ble5_multi_role_cc2640r2lp_app.bin, which is not a modified simple peripheral. So, it is not certain you are doing the correct procedure.

    I have worked with simple peripheral OAD at SDKv1.40 and have modified it a lot and still can perform OAD. Some issues with bluetooth occurs with specific models of smart phone and was decided by my predecessor to add code to calibrate the crystal. I am not sure if that code that calibrates the crystal works.

    OAD issues will occur if your encountering memory issues. I have seen this happen many times. OAD may happen a few times but to ensure it is reliable you need to test it repeatedly maybe at least 100x.

    -kel

  • 0 in reply to Markel Robregado
    Guru 86785 points

    Hi Toravi,

    Forgot to mention this, there are big changes, improvements from Simple Peripheral OAD SDKv1.40 to latest SDK version. Just adding some code implementations to Simple Peripheral OAD of latest SDK version you will encounter OAD issues. You need to evaluate this yourself. If you encounter OAD issues evaluate if a TI BLE MCU with bigger flash and ram would work.

    -kel

  • 0 in reply to Markel Robregado
    Expert 1800 points

    Hi kel

    3) Using Custom2 OAD Firmware .bin(file Size 108 Kb) 

    This Firmware (perform OAD) is working with IOS Mobile App but the problem with only Btool (size Problem)

    Regard's

    Toravi

  • 0 in reply to SenseGiz Team
    TI__Mastermind 25810 points

    Hello,

    In addition to Kel's comments, can you try updating your host_test firmware/Btool version to the latest SDK on the CC2640R2F? This would help rule out any already resolved issue with Btool since the version you are using is not up to date.

  • 0 in reply to Ammar N
    Expert 1800 points

    Hi Ammar,

    Check with SDK 1.4, 3.1, 4.2 (Host Test and Btool), But even then got the same Error.

    Regard's

    Toravi

  • 0 in reply to SenseGiz Team
    TI__Mastermind 25810 points

    Hey Rohit,

    My apologies for the delay in response due to the winter storms last week.

    Try to perform a diff of the .map files and compare your custom1 with the SDK example to see if the custom1 was modified (and how) the memory layout of the projects. Perhaps there is some inconsistency here that Btool catches and prevents you from performing the OAD.