CC2640: OAD Production Application problem

Marie,

Thanks for the fast reply! I'll comment the steps individually.

- OAD target: CC2640F128 using BLE-Stack 2.2.2
* I'm already on this Stack version. I'm using both the OAD_Target and Simple_Peripheral examples, from the cc2650lp folder. In IAR, I'm changing the processor in "Options/General Options" and changing CC26500_LAUNCHPAD to CC2650DK_5XD in "Options/C C++ Compiler/Preprocessor";

- OAD distributor: CC2640F128 or CC2650 Launchapd running Host test from BLE-Stack 2.2.2.
* I do not have a CC2650 Launchpad, just the CC2640R2 one - which I'm flashing with the host_test hex file from CC2640R2 SDK 2.30.00.28. I do have a few custom board with the CC2640F128, but they are very simple (only for reading ADC values and advertise them); since I was able to perform OAD, I don't think the distributor is a problem. Do you think it's a huge difference?

- Use OAD Image Tool from BLE-Stack 2.2.2
* This is the version I'm using, along with the command line from the User Guide.

- Use IDE version recomended in BLE-Stack 2.2.2 (CCS v. 7.4.0 / IAR v. 7.80.4).
* I was using the newer version of IAR. I couldn't find any download link for the '.4' release, but I downloaded the '7.80.3' one. Still have the same problem (I will try to explain in better below).


- Create production image by following the steps in the BLE-Stack 2.2.2 (CC2640 BLE OAD User's Guide).
* I followed all the steps from the BLE-Stack 2.2.2 OAD User Guide. I'm building all the 4 projects, getting the '.hex' files and trying to merge them with the recommended command line. I am able to perform the OAD flawlessly if I flash the 'oad_target_cc2650lp_app_oad_onchip_production.bin' from the OAD_Target folder to my board, and update it after using BTool along the 'simple_peripheral_cc2650lp_app_oad.bin' file from the Simple_Peripheral folder.

My problem is: when I do it, the Image A starts advertising in my board. Since I'm flashing several boards, I won't be able to update all of them using OAD. I'm looking for a way to already flash and run the Image B from the start, and use OAD only if I eventually need to update the firmware.

More information:

The command line from the tutorial is:

<python> <oad_image_tool.py> <BIM hexfile> <Image A hexfile> <Stack hexfile> <Image B hexfile> -o <Output hexfile> -i production –t onchip

The command line from OAD_Target app project is:

"$TOOLS_BLE$\oad\oad_image_tool.exe" "$PROJ_DIR$\FlashROM\Exe\oad_target_cc2650lp_app.hex" "$PROJ_DIR$\..\stack\FlashROM\Exe\oad_target_cc2650lp_stack.hex" "$PROJ_DIR$\..\..\..\..\util\bim\cc2640\iar\FlashOnly\Exe\bim.hex" -t onchip -i production -v 0 --usrId AAAA  -ob "$PROJ_DIR$\FlashROM\Exe\oad_target_cc2650lp_app_oad_onchip_production.bin" -m 0x0600

The command line from Simple_Peripheral is:

"$TOOLS_BLE$\oad\oad_image_tool.exe" "$PROJ_DIR$\FlashOnly_OAD_ImgB\Exe\simple_peripheral_cc2650lp_app.hex" -t onchip -i app --imgVer 0 --usrId BBBB -ob "$PROJ_DIR$\FlashOnly_OAD_ImgB\Exe\simple_peripheral_cc2650lp_app_oad.bin" -m 0x9000 --r 0x9000

The latter ones are under "Options/Build Actions/Post-build command line" for each project, and generate de '.bin' files which I can perform OAD with. The first one (from the User Guide) does not have the '-v', 'usrId', '-m' or '--r' parameters. Aren't they necessary?

Also, the latter ones generate a '.bin' file, and the User Guide one generate a '.hex' file. I tried adding '-ob' instead of '-o' in the command line, but I still get the metadata location error.

Edit: I just realized I haven't mentioned before: for my application, since I don't have an external flash memory in my custom board, I need to perform ON Chip OAD.

Sean,

I don't think Image B has a bad CRC, since I can upload it to my board using OAD flawlessly. I'm having problems specifically when I try to merge the files. I've tried both oad_image_tool.py and srecord, but they fail due to ovelapping.

I'm attaching my hex and bin files - can you please try to merge them and see if you also have the problem?

Files:  oad.zip