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.

cc2541 image B loading issue

Other Parts Discussed in Thread: CC2541

Hi,

I have one question regarding loading of image B on CC2541F256.

Currently I am using BIM image provided by TI and I am using ODA to load image B to processor successfully.

But what if I want to flash image B instead of OAD, is that possible? how?

I am following procedure using smart RF flash tool:

1. Erase, program and verify BIM.

2. Append and verify image A.

3. Append and verify image B.

I have tried that but not working. 

  • Hi Maulik,

    I'm not sure the architecture of BIM allows you to directly flash image B. If so, I think you need to make sure Image A is not present at all. In example, flash BIM then Image B. I'm not sure though, maybe someone else has tried that.

    Best Regards

    Joakim

  • Let me add some more detail to what Maulik explained.

    We are supposed to give over the air upgrade feature as a product release, but during production we want to have quick and wired method to upload ImageB. 

    Just similar to ImageA, we need a mechanism to append and flash ImageB from debugger. So our production is faster. We can't do each and every production unit ImageB flashing with OAD.

    I hope this explains the situation. Kindly let us know in case of any more information required.

    Your quick response will be appreciated.

    Thanks.

  • Hi,

    I'm not sure that is possible. You would have to invalidate Image A in some way then. Could you not simply re-flash BIM + New Image A instead of appending Image B?

    Best Regards

    Joakim

  • Hi Joakim,

    Let me explain it properly.

    Three images are required because 

    1. BIM is must.

    2. Image A contains code only for OAD nothing else.

    3. Image B is main FW image.

    Now, we can successfully flash BIM and then append image A. We can also load image B via OAD. 

    but we are searching for mechanism where we can flash BIM, Image A and Image B all three, instead of loading image B over the air because OAD will increase time.

    Is there anyway we can flash all 3 images during production and then in future updates can be provided by OAD?

    or Image B can be only loaded through OAD ?

  • Hello ,

    I am using CC2541 BLE device i flashed the BIM and ImgB into device at this time it's not supporting for OAD process  ?.

    when i flash the BIM and ImgA into device it's supporting for OAD ( Update the Firmware ) but it's accepting only ImgA.bin file ( already img A is present in the device ) it's not accepting ImgB.bin file ( As per OAD process  when ImgA is present in the device it should accept ImgB binfile and vice versa ) 

    can any one suggest solution for this ?

    Thanks in advance

  • Hi,

    A few questions:

    Are you following this OAD Guide:

    http://processors.wiki.ti.com/index.php/OAD

     

    Is your ImgA and ImgB set to be the same size?

    Thanks,

  • Hi Zahid,

    The Boot Image Manager (BIM) and Image-A are resident images. And using OAD we are updating only Image-B.

    So Image-A and Image-B are of different size.

    Let me know if you need any other information.

    Apart from this, we are urgently seeking resolution on following issue:

    http://e2e.ti.com/support/wireless_connectivity/f/538/t/353581.aspx

    I'll appreciate if you can help us on above issue ASAP.

    Thanks,

    Dhaval

  • Hi Zahid ,

    I followed the above document according to that I produced OAD ImgA & OADImgB .

     

    In my case ImgA and ImgB both have an same size.

     But I don't understand why ImgB.bin file is not updating through OAD process at this same time ImgA.bin was updating.

  • Hi Maulik,

    Were you able to solve this problem? I am currently facing the same problem.

    Regards,
    Leo
  • Hi Leo,

    I think you can do the following:

    1. First write BIM to the device using 'Erase and program' option of SmartRF Flash Programmer.

    2. Then do Image-A HEX file using 'append and verify' option of SmartRF Flash Programmer.

    3. Then do OAD of Image-B .bin file using the mobile application.

    4. Now the device has all three images. Now readback the flash using into the HEX file using "Read flash into the HEX file" option of SmartRF Flash Programmer. This HEX file contains all three images. And you can use this HEX file to program the CC2541 during production.

    Hope this helps!

    Regards,

    Dhaval

    Note: If this has answered your question, you may like to click on 'Verify Answer'.

  • Hi Dhaval,

    We went with your suggestion because of schedule constraints.

    Thanks,
    Leo
  • Does it resolve your problem?

  • Hi Dhaval,

    It did sort of solve the problem for now. But, I am still trying to find the solution to the original problem of just programming the image B to the chip.

    Regards,
    Leo
  • Good to know that it helps to resolve your problem at certain extent. You may like to 'Verify Answer', so it helps others to resolve similar issue.
  • Hi Dhaval,

    I would like to select it as a verified answer, but I don't see the Verify button. I think the original author of the question is the only one that can verify an answer.

    Regards,
    Leo