Tool/software: TI C/C++ Compiler
My custom project is based on SimpleBlePeripheralObserver.
I am using the following
1) CC2640R2F Launchpad
2) BLE 4.2 and Ble stack sdk simplelink_cc2640r2_sdk_1_50_00_58
3) Code composer studio version 8.0.0
4) Ti Compiler version 16.9.6
point 1: - describes the problems, I faced during adding OAD to my project according to the following link
dev.ti.com/.../ble_enhanced_oad.html
point 2: - describes the problem, I faced while converting my project from library configuration to split image configuration, and adding OAD
point 1: - I saw the above link and I tried to add OAD in my project according to given steps, I followed each step, but as my project is based on library configuration, not split image configuration so I am getting ICALL_STACK0_START undefined error, but I should not get this error as the project is in library configuration. I saw the CC2642 or CC26X2 OAD example project also, and it's stack part of the project is based on library configuration, while the application part of the project is based on debug and release configuration. And provided OAD example (For CC26X2 or CC2642) does not use ICALL_STACK0_START, because there is a shadow over ICALL_STACK0_START in oad_image_header_app.c file.
Que 1: what is the difference between library configuration, debug and release configuration and split image configuration. I know little but now I want to know more about these configurations.
Que 2: -As ICALL_STACK0_START not used, so where and how did you define .stackEntryAddr and .stackEndAddr.
Que 3: - How can I use/add Frontier Tool in my project to adjusts the respective RAM and flash boundaries based on analysis of the stack linker and map files. So, I think using the frontier tool I will not get ICALL_STACK0_START error.
point 2: - As there is an OAD example for CC2640r2f that is based on split image, by studying this OAD example and studying little bit Ti forum and wiki, i successfully converted my Application project into split image configuration, and for stack I could not convert the stack part into split image, so what I did I just used OAD example stack (simple_peripheral_cc2640r2lp_oad_offchip_stack) in our split image converted main project. Now it's working fine everything initializes (OLED, UART, GPS, IMU) and advertising but the converted project is not scanning the devices. While the project was working fine with library configuration, in my both project(split image configuration and library configuration) profiles and services are same there is no change, while for library configuration its working fine but for the split image configuration it's not scanning.
After converting my custom project to split image i added the OAD functionality in my project, with oad my project is building no error flash is initializing correctly, now i am able to connect with sensortag app and OAD option appear on the APP, after selecting the OAD option no it goes for Enhanced OAD firmware update screen, i am able to select the .bin after selecting the this stuck and the firmware does not update, as in following screenshot
