A related question is a question created from another question. When the related question is created, it will be automatically linked to the original question.
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.
Can you please describe what you are attempting to do? Also, please clarify if you are using a LAUNCHXL-CC2640R2?
By looking at the image, it seems that you're using an invalid binary image file for that board. You're pointing to SDK 2.2.4 for the CC2650, which is an older device. Maybe try using an equivalent image from the proper SDK for the CC2640R2 (you might need to install it from here). The latest version is 4.10.
I use the Launch-cc2640r2 as a OAD Downloader and the cc2640 as a OAD Target. I'm pointing to SDK 1.40 for Launch-cc2640r2 , and use this SDK for BTool. I set up cc2640 followed CC2640 BLE OAD User‘s Guide. The cc2640 running is ok, but readng image occurs the above error using BTool.
Like Luis mentioned, there are newer versions of the SDK available and I would strongly recommend you migrate to a newer version if that is possible to get the newest features and bug fixes.
Just to clarify, are you using a CC2640R2 LaunchPad as the OAD distributor and a custom board with a CC2640 device as the OAD target? The reason why I ask is that they are seen as two different devices and use different SDKs.
The file you are trying to load does not look like a typical OAD file which might be the reason why you are seeing this error. OAD files are generated by the OAD Image Tool and can be used as a post-build step (recommended) or as a standalone tool. These files include an OAD image header which is required in order for the BIM to boot the device with that image. The files that are generated by this tool end with _oad.bin. Do you have a file with this ending in your project? If yes, try and use this file instead.
