Quantcast
Channel: Forums - Recent Threads
Viewing all articles
Browse latest Browse all 262198

CC2640: Device stops advertising after successful OAD.

$
0
0

Part Number:CC2640

Hi,

I have a CC2640 custom board.

I have followed on-chip out of box demo described in OAD user's guide.

I have created the merged file by running merge.bat script and uploaded the merged image into the board using Flash Programmer.

Then I created a hex file for simple_peripheral_cc2650lp_app and used oad_image_tool to create a bin file.

The script output is as follows:

******************************************************************************************
Texas Instruments OAD Image Tool
Version: 1.0
******************************************************************************************

OAD Type: onchip
Img Type: APP
Input file(s): simple_peripheral_cc2650lp_app.hex
Output Hex file: None
Output Bin file: test1.bin

Layout of concatenated input files, per flash sector, before applying --range.

 00 | 01 | 02 | 03 | 04 | 05 | 06 | 07 | 08 | 09 | 10 | 11 | 12 | 13 | 14 | 15
---- ---- ---- ---- ---- ---- ---- ---- ---- XXXX XXXX XXXX XXXX XXXX XXXX XXXX
---- ---- ---- ---- ---- ---- ---- ---- ---- XXXX XXXX XXXX XXXX XXXX XXXX XXXX
---- ---- ---- ---- ---- ---- ---- ---- ---- XXXX XXXX XXXX XXXX XXXX XXXX XXXX
---- ---- ---- ---- ---- ---- ---- ---- ---- xXXX XXXX XXXX XXXX XXXX XXXX XXXX
 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31
XXXX XX-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ----
XXXX XX-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ----
XXXX XX-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ----
XXXX XX.- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ----

  Legend: `X` 100% full, `x` >50% full, `.` <50% full, `-` empty, `F` all 0xFF,
  `0` all 0x00.
******************************************************************************************
Runtime Output:

Last address was 0x11843. Expanded to 0x11850 to be divisible by OAD block size
Expanded address range. Placed metadata at 0x00009000

The script has calculated the 16 Byte OAD Metadata vector below

Bytes: | 0 - 2  |  2 - 4   | 4 - 6  | 6 - 8  |     8-12    | 12 - 14 |   15    |  16  |
Desc : |  CRC   | CRC-SHDW | imgVer | imgLen |     usrId   | imgAddr | imgType | stat |
---------------------------------------------------------------------------------------
Data : | 0x955A |  0xFFFF  |     1  |   8724 | 45:45:45:45 |   2400  |   01    |  FF  |
******************************************************************************************

Header As It Is:
OrderedDict([('crc', 38234), ('crcShdw', 65535), ('imgVer', 1), ('imgLen', 8724), ('usrId', '45:45:45:45'), ('imgAddr', 9216), ('imgType', 1), ('status', 255)])
Writing to:
 test1.bin
******************************************************************************************
Success
******************************************************************************************


Then I tried to upload the bin file over the air using BTool and CC2540 USB Dongle... When process completed, btool showed OAD Successful and my custom device automatically disconnected..

But then it stopped advertising. Even after resetting the device.


Viewing all articles
Browse latest Browse all 262198

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>