• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 54 subscribers
  • Views 375 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CCS / LAUNCHXL-CC1312R1： about CCS generates the correct HEX file

Kevin Qiu
Expert 1230 points
Part Number: LAUNCHXL-CC1312R1
Other Parts Discussed in Thread: UNIFLASH

Tool/software: Code Composer Studio

Hi Team,

SDK:simplelink_cc13x2_26x2_sdk_4_20_00_35

example:rfPacketTx

 I added wireless data transmission and wireless data reception to the program.

 After receiving the specified data packet, it enters low power consumption.

 I tested 5 devices and tested it many times after powering on again. The phenomenon is that when flash programmer 2 is used to burn the .out/.hex,

 low power consumption could not be entered. But low power consumption can be entered by using CCS load.

 I want to know the difference between CCS load and flash programmer 2.

 Can you help to check it?

codes I eidit:

test.c
Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
/*
* Copyright (c) 2019, Texas Instruments Incorporated
* All rights reserved.
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
*
* * Redistributions of source code must retain the above copyright
* notice, this list of conditions and the following disclaimer.
*
* * Redistributions in binary form must reproduce the above copyright
* notice, this list of conditions and the following disclaimer in the
* documentation and/or other materials provided with the distribution.
*
* * Neither the name of Texas Instruments Incorporated nor the names of
* its contributors may be used to endorse or promote products derived
* from this software without specific prior written permission.
*
* THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
* AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
* THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
* PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR
* CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
* EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
* PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
* OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
* WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
* OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
* EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*/
/***** Includes *****/
/* Standard C Libraries */
#include <stdlib.h>
#include <unistd.h>
/* TI Drivers */
#include <ti/drivers/rf/RF.h>
#include <ti/drivers/PIN.h>
#include <ti/drivers/pin/PINCC26XX.h>
#include <ti/drivers/UART.h>
#include <ti/drivers/SPI.h>
/* Driverlib Header files */
#include DeviceFamily_constructPath(driverlib/rf_prop_mailbox.h)
/* Board Header files */
#include "ti_drivers_config.h"
#include "RFQueue.h"
#include <ti_radio_config.h>
#include "de_bug.h"
#include "ebyte_mx25r2035f.h"
/***** Defines *****/
static void callback(RF_Handle h, RF_CmdHandle ch, RF_EventMask e);
/* Receive dataQueue for RF Core to fill in data */
static dataQueue_t dataQueue;
static rfc_dataEntryGeneral_t* currentDataEntry;
static uint8_t packetLength;
static uint8_t receLenth;
static uint8_t* packetDataPointer;
/* Packet RX Configuration */
#define DATA_ENTRY_HEADER_SIZE 8 /* Constant header size of a Generic Data Entry */
#define MAX_LENGTH 30 /* Max length byte the radio will accept */
#define NUM_DATA_ENTRIES 2 /* NOTE: Only two data entries supported at the moment */
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Regards,

Kevin

  • 0
    TI__Guru** 101450 points

    Hi Kevin,

    Do you mean you are flashing the same HEX with two different tools and are getting different results?

    Can you verify if the content of the flash is exactly the same for the two cases? (you could do a dump of the flash using Uniflash for example)
    Can you also explain how you are doing to determine if you are or are not in "low power consumption"?

    Thanks and regards,

  • 0 in reply to Clément
    Expert 1230 points

    Hi Clément，

    Yeah,I am flashing the same .out /hex with two different tools and  getting different results.

    I measured the current and found it does not enter low power consumption.

    How to do a dump of the flash by Uniflash ?

    regards,

    Kevin

  • 0 in reply to Kevin Qiu
    TI__Guru 58425 points

    Hi Kevin,

    There is no direct difference, CCS loads the same out file but it will keep the debugger attached until you disconnect it yourself, this is the main difference.

    Have you tried connecting to your running target from CCS to check what part of your application is currently running? You might be hitting some of your "trap" and this would be the easiest way to start figuring our project out.