CC2640R2F: CC2640R2F OAD Offchip with btool

Steffen,

Can you check in your board file to see if the I2C and the SPI drivers are trying to use the same pins?

Hi Evan,

I checked the board file but SPI and I²C are using different pins.

Another question is how I can generate a production file that includes BIM, App & Stack and can be flashed by SmartRF Flash Programmer 2?

In the documentation under the topic "Generate production Off-Chip Image using IAR" its said to add this line as a custoim build action:
"$TOOLS_BLE$\oad\oad_image_tool.exe" "$PROJ_DIR$\..\..\..\..\bim_oad_offchip\tirtos\iar\app\FlashOnly\Exe\bim_oad_offchip.hex" "$PROJ_DIR$\..\stack\FlashROM\Exe\simple_peripheral_cc2640r2lp_stack.hex" "$PROJ_DIR$\FlashROM_OAD_Offchip\Exe\simple_peripheral_cc2640r2lp_app.hex" -t onchip -i production -v 0 -m 0x0000 -ob "$PROJ_DIR$\FlashROM_OAD_Offchip\Exe\simple_peripheral_cc2640r2lp_app_oad.bin"

But this seems to be deprecated; the oad image tool included in the sdk doesn't support these parameters.

Currently I have this line:
cmd /C "$TOOLS_BLE_DIR$\output_converter\output_converter.exe $EXE_DIR$\sp_oad_offchip_$PROJ_FNAME$_$CONFIG_NAME$.bin & $TOOLS_BLE_DIR$\oad\oad_image_tool.exe iar $PROJ_DIR$ 1 $EXE_DIR$\$TARGET_BNAME$.hex $PROJ_DIR$\..\config\iar_boundary.xcl $PROJ_DIR$\..\stack\FlashROM\Exe\sp_oad_offchip_cc2640r2lp_stack_FlashROM.hex -o $EXE_DIR$\$TARGET_BNAME$_oad"

But when I flash this Image with SmartRF Flash Programmer 2 the application does not run.

Regards
Steffen

Hi Steffen,

Are you using board file from CC2650 SensorTag? I suggest you use Board file from CC2640R2F SDK.

-kel

Hi Markel,

I tried both files. Both with the same result.

Regards

Steffen