• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 51 subscribers
  • Views 367 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Difference of behavior between two TI OAD Applications

Dhaval V
Genius 4470 points

Hi,

There are two OAD Applications available from TI for iPhone :

1. TI OAD Ex

2. TI Multitool

Previously, we were using TI OAD Ex for doing OAD and currently we are using the later one. But the first one was taking around 4-5 mins to upgrade the firmware while the later one is taking around 1.5 to 2 mins to upgrade the firmware of same size. Why there is a difference?

Now, in any of the case, device resets itself after OAD is done to boot with newer image.But in case of TI Multitool application, many times we have observed that device is not resetting itself and it stays there i.e. in limbo. And it never comes out of this until we reset the device. This is really weird. Following setting we are using with TI's Multitool:

Use Notification: Yes

Timer Delay: 90 ms

Packets per timer / notif. : 18

Your help is appreciated.

Thanks,

Dhaval

  • 0
    Intellectual 405 points

    I would check connection interval and number of packets per interval. Use a sniffer, or if that's not option, try checking the following code using breakpoints.

    Connection establish event (check connection interval)

    ParamUpdateEvent (check status, connection event)

    It may be that IOS is connecting at 100ms interval and then not going to faster interval. This may be in IOS application code and/or the OAD app may request paramUpdate (faster connection interval) and this may be rejected.

    You can also hook up GPIO to connection notify Callback event, and check connection interval using a scope.

    Once image is downloaded, a CRC check is performed. Perhaps this is failing sometime. It's a little work, but you can check code in breakpoint here also in OAD profile. There is another CRC check in bootloader code. This may also be failing for some reason. Use debug without downloading to step through bootloader after OAD is complete.

    BR,

    -GReg

  • 0 in reply to Greg Stewart
    Genius 4470 points

    Hi Greg,

    Thanks for your quick reply!

    Both the application is running on iPhone having same iOS versions.

    And in our case, OAD profiles checks for the number of blocks received and if total number of blocks received then it reset the device to boot with newly upgraded image.

    Thanks,

    Dhaval