• State
  • Replies 4 replies
  • Subscribers 51 subscribers
  • Views 59 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

LP-EM-CC2340R5: MCU Boot for OAD On Chip is directly booting the persistent application

Sushant Thakur
Prodigy 10 points
Part Number: LP-EM-CC2340R5
Other Parts Discussed in Thread: CC2340R5

Tool/software:

Hi, I am using CC2340R5 and trying to implement On Chip OAD Example. The CCS version being used is 12.8.1 .The flashing process which I am using to flash is as :-

https://software-dl.ti.com/simplelink/esd/simplelink_lowpower_f3_sdk/8.20.00.119/exports/examples/rtos/LP_EM_CC2340R5/ble5stack/basic_ble_oad_onchip/README.html

2. After which I am using my IOS to connect to the device, the device is showing the device name as Persistent App, but as per my understanding mcu boot should load the ble_oad_onchip firmware and as per that in my ios I should be able to see the device name as Basic BLE Project. 

PS:- I used Red and Green LED on the board to verify the above behavior and the results were as expected. The mcuboot is booting the persistent app directly after reset. 

Any clarity on this would be helpful.

  • 0
    TI__Genius 12145 points

    Hello Sushant,

    Thanks for reaching out. Could you please follow the steps described in this training material: https://dev.ti.com/tirex/explore/node?node=A__AbMoFvWD.bZAg65tD.7NsQ__SIMPLELINK-ACADEMY-CC23XX__gsUPh5j__LATEST
    Also, could you please try directly with the mcuboot hex file from \examples\rtos\LP_EM_CC2340R5\ble5stack\hexfiles for a quick sanity check.

    Best Regards,

    David.

  • 0 in reply to David
    Prodigy 10 points

    Hello David, 
    Thanks for your quick response. I already did followed the training material and I am literally not able to understand why the persistent application is getting loaded by the mcuboot.

    However when I do try to use the mcuboot_on_chip hex file directly it is working fine. 

    But still I want to modify my mcuboot for my application development and I dont know from where can I find the source code for the particular hex file. 

    Please do let me know if something can be done.

  • 0 in reply to Sushant Thakur
    TI__Genius 12145 points

    Hello Sushant,

    I see, thanks for trying that.

    What might be happening here is that the slot size defined for the OAD image is not the same as the one configured in the MCUBoot project. Please make sure the slot size (BOOT_SECONDARY_1_SIZE) in flash_map_backend.h (inside mcuboot project) is the same as the slot size defined in the post build steps of the oad on chip example.

    BR,

    David

  • 0 in reply to David
    Prodigy 10 points

    Hi David,

    I did changed the slot size defined in the post build steps of the oad on chip example, to same as that of the BOOT_SECONDARY_1_SIZE defined in flash_map_backend.h , but still no luck. 

    Below are some screenshots for better understanding.:-

    Please do let me know if something else can be done. Thanks for your constant support.