• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 51 subscribers
  • Views 166 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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-Q1: CC2642 persistent app SNV

user6193948
Prodigy 120 points
Part Number: CC2642R-Q1

When I set SNV,

build error: 

Description Resource Path Location Type
#10324-D BOUND section ".TI.bound:flashBuf0" spans the boundary of an existing memory range FLASH_IMG_HDR persistent_app_CC26X2R1_LAUNCHXL_tirtos_ccs C/C++ Problem

Description Resource Path Location Type
<a href="file:/C:/ti/ccs1110/ccs/tools/compiler/dmed/HTML/10099.html">#10099-D</a> program will not fit into available memory, or the section contains a call site that requires a trampoline that can't be generated for this section. run placement with alignment fails for section ".TI.bound:flashBuf0" size 0x4000 persistent_app_CC26X2R1_LAUNCHXL_tirtos_ccs C/C++ Problem

  • 0
    TI__Guru**** 202106 points

    Hello,

    Changing the NVS regions from 0x34000 to 0x38000 will conflict with the memory areas and sections assigned in the cc13x2_cc26x2_app.cmd file linked from the Project Properties -> Build -> Arm Linker -> File Search Path.  You would also need to modify the m3Hwi.resetVectorAddress of the persistent_app.cfg file, among other possible changes including the BIM project.  I do not recommend performing these changes unless you have in-depth knowledge of the OAD implementation of the BLE5-Stack.

    Regards,
    Ryan

  • 0 in reply to Ryan Brown1
    Prodigy 120 points

    thanks for your replay。 but In onchip_app, I Changing the NVS regions from 0x34000 to 0x52000, no errors were reported after build. 

  • 0 in reply to user6193948
    TI__Guru**** 202106 points

    That could be true for CONFIG_NVSINTERNAL Region Base, but not CONFIG_NVSINTERNAL1 Region Size, where 0x38000 conflicts with the IMG_A_FLASH_START with the OAD_HDR size taken into account.  It is still unclear why you are trying to modify the pre-determined OAD regions.

    Regards,
    Ryan