• State
  • Locked Locked
  • Replies 9 replies
  • Subscribers 51 subscribers
  • Views 405 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.

LP-EM-CC2745R10-Q1: Some problems occurred when the Primary/Secondary values of the Security Configuration of the OAD project were changed

ethan welber
Prodigy 120 points
Part Number: LP-EM-CC2745R10-Q1


Tool/software:

Hi All,

Here are my software and hardware versions:

LP-EM-CC2745R10-Q1

simplelink_lowpower_f3_sdk_8_40_00_61

CCS Version: 20.0.2.5__1.6.2

I need to add some features to the basic_persistent project, and after compiling, I find that the prompt ROM space is not enough.Therefore, I re-changed the size of Primary to 0x32000 and the start address of Secondary in the Security Configuration

The address of NVS is also adapted

I also set the same parameters to the basic_ble_oad_onchip project, and then burned the firmware compiled by the two projects respectively.But basic_ble_oad doesn't seem to work properly.

I tried to read the memory structure and found that the firmware was in the expected location, but it didn't work, I suspected secure boot was the cause, but there was no more information to confirm

I also tried to change the length of Secondary to 0xB2000, but it still didn't work.

Does anyone know what causes it?

  • 0
    TI__Genius 15635 points

    Hello,

    So it appears that you have an overlapping region.

    CONFIG_NVSINTERNAL has a region of 0xE4000 + 0x4000 = 0xE8000. The way you have your CONFIG_NVSINTERNAL1 and secure boot addresses setup: 0x32000 + 0xB3000 = 0xE5000. So it overlaps a bit. I believe that CONFIG_NVSINTERNAL is used for BLE operations/bonding. I think by moving this around so that everything fits in memory without overlapping should fix the issue.

    Best,

    Nima Behmanesh

  • 0 in reply to Nima
    Prodigy 120 points

    Hi Nima,

    There is indeed a warning, but after my testing, I found that this should not be the problem. When I changed the Region Base value of CONFIG_NVSINTERNAL to 0xE5000, the warning was removed, but it still did not run after compiling and downloading.And I have tried to modify  the length of Secondary to 0xB2000  before which can theoretically avoid overlapping problem of nvs,but it is not effective in practice.

    Best,

    Ethan

  • 0 in reply to Nima
    Prodigy 120 points

    When I tried to burn only the basic_ble_oad firmware, I found that the start address can only be set to 0x31000, 0x30000 and 0x32000 will not work, I think it should be the reason here, can you help to analyze it

  • 0 in reply to ethan welber
    TI__Genius 15635 points

    Hello,

    I followed your steps and I'm seeing the same thing. I believe it's an issue with how the project is linked. I'll have to spend some time looking into this, and will try to update you before Thursday.

    Best,

    Nima Behmanesh

  • 0 in reply to Nima
    TI__Genius 15635 points

    Hi Ethan,

    I've reached out to R&D and I'm in the process of creating a ticket regarding this. I'll update you once there's been some progress.

    Best,

    Nima Behmanesh

  • 0 in reply to Nima
    Prodigy 120 points

    Hi Nima,

    Is there any progress now?

    Best,

    Ethan

  • 0 in reply to ethan welber
    TI__Genius 15635 points

    Hi Ethan,

    I created a ticket for R&D, but I haven't received any sort of update regarding this issue. I'll ping the team and keep you posted throughout the week. 

    Best,

    Nima Behmanesh

  • 0 in reply to Nima
    TI__Genius 15635 points

    Hi Ethan,

    Still working on this, I apologize for the long delay here.

    Best,

    Nima Behmanesh

  • 0 in reply to Nima
    Prodigy 120 points

    Hi Nima,

    Thank you for your reply. If there is any progress, please inform me in time. Thank you again.

    Best,

    Ethan