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.
Tool/software: TI C/C++ Compiler
I need the exact Flash layout for On-chip OAD. Especially in ble_simple.. onchip persistent_app, (IMAGE_A)
ccs_linker_defines_tgt.cmd file seems to say FLASH_START = 0xe000,
--define=OAD_TGT_RAM0_START=0x20001000
--define=OAD_TGT_FLASH_START=0xe000
--define=OAD_TGT_ENTRY_ADDR=0x55fc0
Since my app size is larger than 0xe000, That address doesn't make sense.
In Searing my project, I found another code snippet in ble_debug.cfg
m3Hwi.resetVectorAddress = 0x00055fc0;
ROM.constStructAddr = 0x37000;
ROM.externFuncStructAddr = 0x373C0;
If Image_A has start-address 0x37000, All would make sense.
Please help me to understand bellow
OAD_TGT_FLASH_START=0xe000
ROM.constStructAddr = 0x37000;
ROM.externFuncStructAddr = 0x373C0;
Thansk,
Hi dooseok,
Check out the Flash Layout for On-chip OAD section in the BLE Stack User's Guide: http://dev.ti.com/tirex/content/simplelink_cc13x2_26x2_sdk_3_40_00_02/docs/ble5stack/ble_user_guide/html/oad-secure/flash-layout-on-chip-stack-library.html
Hi Severin,
Thanks your comment. I understood this layout concept. However I can't match this concept to my real project.
I want to know how to decide OAD_IMG_A(HDR_START) Address and the exact value.
Could you explain these values presented my asking?
<ible_debug.cfg>
m3Hwi.resetVectorAddress = 0x00055fc0;
ROM.constStructAddr = 0x37000;
ROM.externFuncStructAddr = 0x373C0;
<ccs_compiler_defines.bcfg>
--define=OAD_TGT_ENTRY_ADDR=0x55fc0
--define=OAD_TGT_FLASH_START=0x36000
--define=OAD_TGT_RAM0_START=0x20001000
Thanks,
dooseok