• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 52 subscribers
  • Views 870 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.

How does Device Monitor determine OAD image "type" and "version"

alistair rodger
Prodigy 80 points

When upgrading an image "B", Device Monitor fails saying that my image is a "Type A" image and that i require a type B image.  This worked until I remapped the flash layout as described in document Developer's Guide for Over Air Download for CC254x version 1.2 to increase the size of ImgB.

The following are copies of the headers showing the contents of the header structures.


I also notice that the version numbers are not as described in the image headers.

00000000: cca9 ffff 0b00 0080 4242 4242 ffff ffff  ........BBBB....
00000010: ffff ffff ffff ffff ffff ffff ffff ffff  ................
00000020: 0001 0203 0405 0607 0809 0a0b ffff ffff  ................
00000030: 0237 6e02 4e27 ffff ffff ffff ffff ffff  .7n.N'..........

Past working image

00000000: 1f33 ffff 0708 007c 4242 4242 ffff ffff  .3.....|BBBB....
00000010: ffff ffff ffff ffff ffff ffff ffff ffff  ................
00000020: 0001 0203 0405 0607 0809 0a0b ffff ffff  ................
00000030: 0247 af02 5e5f ffff ffff ffff ffff ffff  .G..^_..........

I can only assume it is some magic done in device monitor as I have found no mention of other locations for version numbers.


Sincerely,

alistair

 

  • 0
    TI__Expert 6840 points

    Hi alistair,

    I got oversized image A to work with dev monitor. Find example at wiki

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

    The check on the firmware side in done in OAD profile. 

    BR,

    -Greg

  • 0 in reply to GregS
    Prodigy 80 points

    I can only presume that the "version" and "type" use the version numbering convention as identified in  "OAD_for_CC254x.pdf" section 8.4.4.  I also presume that this check is done in Device Monitor as there is no communication before this error.  Also removing such checks in the OAD image do not fix the issue.

    I have not helped myself by posting reference to an image that would work as the version number is odd.  I am surprised that I didn't test this.

    I can work around this issue by insisting on odd version numbers whilst using Device Monitor for upgrading.  Just in case anybody else suffers the same issue. ;-)

  • 0 in reply to alistair rodger
    Intellectual 385 points

    Hi Alistair

    Now I am facing same issue how to solve this issue any kind of suggestions are appreciated??

    For running sensor app from TI I am just creating OAD to it.

    My problem is When I download ImgA into the chip and BLE device monitor will shows as Type B and User Id B:B:B:B(in the target image).And if I download the ImgB then BLE device monitor will say OAD not supported how to over come this issue any suggestions??

    With regards

    Jayaraj