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

TMS320F28377D: process to use C2000-gang.dll to program both cores on the Delfino TMS320F28377D

$
0
0

Part Number:TMS320F28377D

Hi, I'm wondering the process to use C2000-gang.dll to program both cores on the Delfino TMS320F28377D.  Should I try and program it as one process, or do I need to run C2000GANG_InteractiveProcess twice, once for each codefile?  I don't see an example of this.  I tried the following process and it doesn't seem to program the second core.  For the second "SetConfig, I selected " SecondCodeFile (3)  for setting number 44 (CFG_OPEN_FILE_TYPE), because it gave an error saying something to the effect of "code already loaded in that slot" when I used "CODE2_FILE_INDEX" (4). 

C2000GANG_InitCom

C2000GANG_Default_Config

C2000GANG_SetConfig.

C2000GANG_GetConfig

C2000GANG_Set_MCU_Name

C2000GANG_Read_Code_File

C2000GANG_SetConfig  (Again for the second core)

C2000GANG_Read_Code_File   (Again for the second core)

C2000GANG_CreateGangImage

C2000GANG_InteractiveProcess

C2000GANG_GetProgressStatus

C2000GANG_ReleaseCom


LAUNCHXL-CC1352P: Connecting an antenna (hardware design question)

$
0
0

Part Number:LAUNCHXL-CC1352P

The LAUNCHXL-CC1352P1 has a SKY13317-373, three-port RF switch that's controlled by three digital I/O pins.  The antenna is on one side of the switch, and there are three "inputs" (if you will) on the other side:

  • 2.4 GHz RF
  • SUB_1 GHz RF
  • TX 20DBM

I'm making my own schematic and I'm wondering how much of this I can eliminate.  I'm not using sub-1GHz at all so I assume I can either just ground those pins or leave them open.  But at that point I still think I need an RF switch, because the antenna has to be switched to 2_4_GHZ_RF (P and N) for receive, and to TX_20DBM (P and N) for transmit.  Is that correct?

If you aren't using the +20DBM amplifier, does the TX output come out 2_4_GHZ_RF (P and N) ?  

Finally, where is the software in the demo project that controls SWCTRL0_DIO29, SWCTRL1_DIO30, and SWCTRL2_DIO28?

--Chris

FDC1004: Demultiplexing signals from multiple sensors to FDC1004 channels

$
0
0

Part Number:FDC1004

There is a need for multiple sensors around 50 in one of the application that we are working on and the question is,

1. Can we use a demux chip to de-multiplex the signals from various sensors into FDC1004 channels? If so, what is the best ti DEMUX IC we can use in the range of 3.3 to 5V rating?

2. We were exploring FDC 2214 and found that it could not be hot swapped. Our understanding is, we cannot use demux. Is that right?

3. How better MSP430 CapTIvate is compared to FDC1004 for a sensor size around a 10mmX10mm size?

Thank you in advance.

MSP430F5359: FET tool cannot connect with JTAG

$
0
0

Part Number:MSP430F5359

Dear Sirs,

We have been using IAR tools to debug and to create a FW image on our products for years without incident.

We never password protect the JTAG.

Within the last week or so we have found that we cannot access any board with the MSP FET for debugging nor can we flash any board using the MSP FET with the MSP flasher software.  We have two newer FET boxes and one older one plus three cables.  We have tried them in all combinations on four different MSP430s: MSP430F5438, 5638, 5659 nad 5359.   We have tried multiple boards including boards that were already running with external power when the JTAG was plugged-in.  We can see the reset line toggling wit a scope probe but the attempt to connect always ends with "unknown Device" or "Device not found".

When we switch the FET between the Debug tool and the MSP430 Flasher, we notice that the FET updates its firmware.  Could a new firmware in the FET be causing our issue?

Thank you.

Regards,

Paul Mayer 

LMX2594EVM: Duty cycle tolerance for LMX2594 using the 2xOSCin

$
0
0

Part Number:LMX2594EVM

Hi

My customer has a question regarding the duty cycle of the OSCin reference clock when using the 2xOSCin in the LMX2594. In the datasheet, it is mentioned that the duty cycle for the OSCin should be 50% if the 2x OSCin is used. There is not such perfect 50% duty cycle clock, so what is the tolerance on the duty cycle for OSCin when 2xOSC is used?

Thanks,

Kawtar

TMS320F28379D: Help with Bit field code references.

$
0
0

Part Number:TMS320F28379D

Hello all,

I am following the one-day MCU tutorial for C2000 MCU (F28379D) in this example there are few bit field code written. For example-

  GpioDataRegs.GPBDAT.bit.GPIO32 = 1;    // Turn off LED

or Command -  EDIS;

Where can I find these bit field/register reference and command reference? Specific document needed.

Thanks.

SN65LVDS2: Calculations for Rise/Fall Time of SN65LVDS2

$
0
0

Part Number:SN65LVDS2

Hi,

In the datasheet under the switching characteristics table, you list out the test conditions for your AC measurements. These conditions are 100ohm load with 10pF cap, and list the 10/90 tr/tf typ as 600ps.

How is this number achieved? If following a 10/90 reference level, tr/tf should equal 2.2 Time Constants. Using the test condition values in the formula the rise time is actually 2.2ns in this condition. If 600ps were to be designed for, I believe the cap load should be roughly 2.7pF.

Could you help explain the differences in the datasheet spec and my calculations and see if I am making any mistakes/wrong assumptions?

Thanks
Jonny

BQ27421-G1: Taper rate calculation

$
0
0

Part Number:BQ27421-G1

Hi,

I am using the battery management studio to test the gauge BQ27421 with EV2400. The Parameter Q&A - Quick configuration section has a formula for taper rate as 10*(design_capacity/(taper_current + 0.1*taper_current)). There is an example configuration provided too.

The Gauge communication document (SLUA801 - Jan 2017) has taper rate calculation as: (DESIGN_CAPACITY / (0.1 * TAPER_CURRENT))

These formulae are slightly different from each other. Can you please let me know which one is correct and why?


66AK2H06: how to trigger exception manually?

$
0
0

Part Number:66AK2H06

Hi all,

I set a NMI iand enable the external and internal exception by setting register in TSR.GEE.

I also hook NMI to an interrupt c code.

Now, i want to test if my setup works, how to I trigger an exception?

is it possible by doing this in dsp c code side?

Regards,

Yao-Ting

LP87564-Q1: Multiple LP87564-Q1 on single I2C bus?

$
0
0

Part Number:LP87564-Q1

Can LP87564-Q1 slave address be changed through custom OTP setting?  If not possible, I will recommend to use a I2C mux or use a separate bus.

Thanks,
Alan

UC1707: Max/Min Output voltage. What is it?

$
0
0

Part Number:UC1707

What is the maximum/minimum voltage on the output pins for the UC1707?  We are using the military part number 5962-8761901V2A.  We are considering what kinds of diodes we can use for protection on the outputs.

Replacement for QS3L384PAG 10 channel 1:1 switch

$
0
0

My customer is looking for a TI alternative to competitor’s device “QS3L384PAG”

 The customer will consider replacing this device if TI has a cheaper option.

RTOS/TMS320C6657: DbgPrintf does not print to console

$
0
0

Part Number:TMS320C6657

Tool/software: TI-RTOS

Hi,

I'm not getting console output when I call the DbgPrintf function while running the NDK 3.40.1.01 on an EVMC6657L board.

I'm using SYSBIOS 6.75.2.00

XDC 3.50.8.24_core

I've set the debug print level to DBG_INFO in the stack configuration task:

rc = DBG_INFO;
   CfgAddEntry (hCfg, CFGTAG_OS, CFGITEM_OS_DBGPRINTLEVEL,
      CFG_ADDMODE_UNIQUE, sizeof(uint32_t), (UINT8 *) &rc, 0);

I've also tried just calling System_printf( ) directly, from main() and also from a task. If I simply call the printf() function, I do see the output on the console. The console, is viewed through the jtag emulator:

My SYSBIOS configuration file is pasted below. I'd appreciate some help in getting this functionality working.

Thanks,

Jim

var Defaults = xdc.useModule('xdc.runtime.Defaults');
var Diags = xdc.useModule('xdc.runtime.Diags');
var Error = xdc.useModule('xdc.runtime.Error');
var Log = xdc.useModule('xdc.runtime.Log');
var LoggerBuf = xdc.useModule('xdc.runtime.LoggerBuf');
var Main = xdc.useModule('xdc.runtime.Main');
var Memory = xdc.useModule('xdc.runtime.Memory')
var SysMin = xdc.useModule('xdc.runtime.SysMin');
var System = xdc.useModule('xdc.runtime.System');
var Text = xdc.useModule('xdc.runtime.Text');

var BIOS = xdc.useModule('ti.sysbios.BIOS');
var Clock = xdc.useModule('ti.sysbios.knl.Clock');
var Swi = xdc.useModule('ti.sysbios.knl.Swi');
var Task = xdc.useModule('ti.sysbios.knl.Task');
var Semaphore = xdc.useModule('ti.sysbios.knl.Semaphore');
var Hwi = xdc.useModule('ti.sysbios.hal.Hwi');
var Idle = xdc.useModule('ti.sysbios.knl.Idle');
var Timer = xdc.useModule('ti.sysbios.timers.timer64.Timer');


var Timestamp = xdc.useModule('xdc.runtime.Timestamp');

var Cache       =   xdc.useModule('ti.sysbios.family.c66.Cache');

/* lower half of DDR3 is cached */
Cache.setMarMeta(0x80000000, 0x10000000, 1);

/* upper half of DDR3 is non-cached */
Cache.setMarMeta(0x90000000, 0x10000000, 0);


var Exception = xdc.useModule('ti.sysbios.family.c64p.Exception');
var CpIntc = xdc.useModule('ti.sysbios.family.c66.tci66xx.CpIntc');
var EventCombiner = xdc.useModule('ti.sysbios.family.c64p.EventCombiner');
var HeapMem = xdc.useModule('ti.sysbios.heaps.HeapMem');
var HeapBuf = xdc.useModule('ti.sysbios.heaps.HeapBuf');

/*
** Use this load to configure NDK 2.2 and above using RTSC. In previous versions of
** the NDK RTSC configuration was not supported and you should comment this out.
*/
var Ndk       = xdc.loadPackage('ti.ndk.config');
var Global       = xdc.useModule('ti.ndk.config.Global');
/*
** This allows the heart beat (poll function) to be created but does not generate the stack threads
**
** Look in the cdoc (help files) to see what CfgAddEntry items can be configured. We tell it NOT
** to create any stack threads (services) as we configure those ourselves in our Main Task
** thread hpdspuaStart.
*/  
Global.enableCodeGeneration = false;

var Startup = xdc.useModule('xdc.runtime.Startup');
var SysStd = xdc.useModule('xdc.runtime.SysStd');

/*
 * Uncomment this line to globally disable Asserts.
 * All modules inherit the default from the 'Defaults' module.  You
 * can override these defaults on a per-module basis using Module.common$.
 * Disabling Asserts will save code space and improve runtime performance.
Defaults.common$.diags_ASSERT = Diags.ALWAYS_OFF;
 */

/*
 * Uncomment this line to keep module names from being loaded on the target.
 * The module name strings are placed in the .const section. Setting this
 * parameter to false will save space in the .const section.  Error and
 * Assert messages will contain an "unknown module" prefix instead
 * of the actual module name.
Defaults.common$.namedModule = false;
 */

/*
 * Minimize exit handler array in System.  The System module includes
 * an array of functions that are registered with System_atexit() to be
 * called by System_exit().
 */
System.maxAtexitHandlers = 8;

/*
 * Uncomment this line to disable the Error print function.  
 * We lose error information when this is disabled since the errors are
 * not printed.  Disabling the raiseHook will save some code space if
 * your app is not using System_printf() since the Error_print() function
 * calls System_printf().
Error.raiseHook = null;
 */

/*
 * Uncomment this line to keep Error, Assert, and Log strings from being
 * loaded on the target.  These strings are placed in the .const section.
 * Setting this parameter to false will save space in the .const section.
 * Error, Assert and Log message will print raw ids and args instead of
 * a formatted message.
Text.isLoaded = false;
 */

/*
 * Uncomment this line to disable the output of characters by SysMin
 * when the program exits.  SysMin writes characters to a circular buffer.
 * This buffer can be viewed using the SysMin Output view in ROV.
SysMin.flushAtExit = false;
 */

/*
 * The BIOS module will create the default heap for the system.
 * Specify the size of this default heap.
 */
BIOS.heapSize = 0x1000;

/*
 * Build a custom SYS/BIOS library from sources.
 */
BIOS.libType = BIOS.LibType_Custom;

/* System stack size (used by ISRs and Swis) */
Program.stack = 0x2000;

/* Circular buffer size for System_printf() */
SysMin.bufSize = 0x200;

/*
 * Create and install logger for the whole system
 */
var loggerBufParams = new LoggerBuf.Params();
loggerBufParams.numEntries = 16;
var logger0 = LoggerBuf.create(loggerBufParams);
Defaults.common$.logger = logger0;
Main.common$.diags_INFO = Diags.ALWAYS_ON;

System.SupportProxy = SysMin;

var clock0Params = new Clock.Params();
clock0Params.instance.name = "clock0";
clock0Params.period = 1;
clock0Params.startFlag = true;
Program.global.clock0 = Clock.create("&GpakSchedulingTimer", 1, clock0Params);
Idle.idleFxns[0] = "&GpakIdleTaskFunc";


var HeapMem = xdc.useModule('ti.sysbios.heaps.HeapMem');
var heapMemParams = new HeapMem.Params();
heapMemParams.size = 0x8000;
heapMemParams.sectionName = "systemHeap";
Program.global.heap0 = HeapMem.create(heapMemParams);

Memory.defaultHeapInstance  =   Program.global.heap0;

Program.sectMap["sharedL2"] = "MSMCSRAM";
Program.sectMap["systemHeap"] = "MSMCSRAM";
Program.sectMap[".sysmem"]  = "MSMCSRAM";
Program.sectMap[".args"]    = "MSMCSRAM";
Program.sectMap[".cio"]     = "MSMCSRAM";
Program.sectMap[".far"]     =     "MSMCSRAM";
/*
Program.sectMap[".rodata"]     =     "MSMCSRAM";
Program.sectMap[".neardata"]     =     "MSMCSRAM";
Program.sectMap[".bss"]        =    "MSMCSRAM";
*/
Program.sectMap[".cppi"]     =     "MSMCSRAM";
Program.sectMap[".init_array"]     =     "MSMCSRAM";
Program.sectMap[".qmss"]     =     "MSMCSRAM";
Program.sectMap[".cinit"]     =     "MSMCSRAM";
Program.sectMap[".const"]    =    "MSMCSRAM";
Program.sectMap[".text"]    =    "MSMCSRAM";
Program.sectMap[".code"]    =    "MSMCSRAM";
Program.sectMap[".switch"]    =    "MSMCSRAM";
Program.sectMap[".data"]    =    "MSMCSRAM";
Program.sectMap[".fardata"] =     "MSMCSRAM";
Program.sectMap[".args"]     =     "MSMCSRAM";
Program.sectMap[".cio"]     =     "MSMCSRAM";
Program.sectMap[".vecs"]     =     "MSMCSRAM";
Program.sectMap["emacComm"]          = "L2SRAM"
Program.sectMap[".far:taskStackSection"] = "L2SRAM";
Program.sectMap[".stack"]    =    "L2SRAM";
Program.sectMap[".far:IMAGEDATA"] = {loadSegment: "L2SRAM", loadAlign: 8};
Program.sectMap[".far:NDK_OBJMEM"] = {loadSegment: "L2SRAM", loadAlign: 8};
Program.sectMap[".far:NDK_PACKETMEM"] = {loadSegment: "L2SRAM", loadAlign: 128};


/* Load the CSL package */
var devType                     =     "c6657";
var Csl                         =     xdc.useModule('ti.csl.Settings');
Csl.deviceType                     =     devType;
Csl.useCSLIntcLib                 =     true;

/* Load the OSAL package */
var osType = "tirtos"
var Osal = xdc.useModule('ti.osal.Settings');
Osal.osType = osType;

/* Load the QMSS package */
var Qmss                        =   xdc.loadPackage('ti.drv.qmss');

/* Load the EMAC packages */
var Emac = xdc.loadPackage('ti.drv.emac');
Emac.Settings.socType = devType;
var socType           = "c6657";

var Nimu         = xdc.loadPackage('ti.transport.ndk.nimu');
Nimu.Settings.socType  = socType;


DRV8876: IPROPI PIN

$
0
0

Part Number:DRV8876

Hello,

We are using now the DRV8876PWPR in a new schematic.

We will not use the current sense feature. Is it correct to connect the IPROPI pin to ground?

Thanks!

LMX2594: divider with a channel divide of 2

$
0
0

Part Number:LMX2594

I am trying to get the settings correct for the include divider with a channel divide of 2.  The 1st row of table 8 in the data sheet (SEG0=2).   According to the flow chart in figure 26 the loop is category 1.

 

N=50

M=2

Fvco=8000MHz

Fout=4000MHz

Fpd=80MHz

setting

R31[14]=0    0: Disabled (only valid for CHDIV=2)l

R75[10:6]     0: 2  VCO Divider value

R[014]=1      1 : Enable phase SYNC mode

R36=50        N

The loop will not lock using these setting.  If I program N=100 the loop locks and the output is 4GHz.  It appears the SEG0 divider is being bypassed, see figure 25.   How do I include the SEG0 divider?  

 

FYI, everything works as expected with the CHDIV>2.          


TMUX1072: COM pins leakage when voltage > Vcc

$
0
0

Part Number:TMUX1072

For the TMUX1072, if there is a 15V common mode on its COM pins, will the ESD structures conduct so that there is current backdriving into its Vcc?

We want to make sure that there is no leakage current from the COM pins to the Vcc pin when Vcc < V_COM or when Vcc is in an unpowered state.

Compiler/MSP432P401R: Optimizer bug or user error

$
0
0

Part Number:MSP432P401R

Tool/software: TI C/C++ Compiler

Hello.

I've run into a problem where I'm trying to add two large numbers and I'm losing the carry bit when I increase the optimizer level to 2.

To demonstrate the problem I have lightly modified the uart loopback example (uart_loopback_24mhz_brclk.c). At none, 0 or 1 optimization it outputs a "y" for successful result.

At level 2 and above, I get a "n". The carry bit is not being carried between each 32bit addition.

Is this user error, or failure of the optimizer? I've tried a for() loop instead of while() and get the same result.

/* --COPYRIGHT--,BSD
 * Copyright (c) 2017, 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.
 * --/COPYRIGHT--*/
/******************************************************************************
 * MSP432 UART - Loopback with 24MHz DCO BRCLK
 *
 * Description: This demo connects TX to RX of the MSP432 UART
 * The example code shows proper initialization of registers
 * and interrupts to receive and transmit data. If data is incorrect P1.0 LED
 * is turned ON.
 *
 *  MCLK = HSMCLK = SMCLK = DCO of 24MHz
 *
 *               MSP432P401
 *             -----------------
 *            |                 |
 *       RST -|     P1.3/UCA0TXD|----|
 *            |                 |    |
 *           -|                 |    |
 *            |     P1.2/UCA0RXD|----|
 *            |                 |
 *            |             P1.0|---> LED
 *            |                 |
 *
 *******************************************************************************/
/* DriverLib Includes */
#include <ti/devices/msp432p4xx/driverlib/driverlib.h>

/* Standard Includes */
#include <stdint.h>
#include <stdbool.h>
#include <stddef.h>

uint8_t TXData = 1;
uint8_t RXData = 0;

/* UART Configuration Parameter. These are the configuration parameters to
 * make the eUSCI A UART module to operate with a 115200 baud rate. These
 * values were calculated using the online calculator that TI provides
 * at:
 * software-dl.ti.com/.../index.html
 */
const eUSCI_UART_Config uartConfig =
{
        EUSCI_A_UART_CLOCKSOURCE_SMCLK,          // SMCLK Clock Source
        13,                                      // BRDIV = 13
        0,                                       // UCxBRF = 0
        37,                                      // UCxBRS = 37
        EUSCI_A_UART_NO_PARITY,                  // No Parity
        EUSCI_A_UART_MSB_FIRST,                  // MSB First
        EUSCI_A_UART_ONE_STOP_BIT,               // One stop bit
        EUSCI_A_UART_MODE,                       // UART mode
        EUSCI_A_UART_OVERSAMPLING_BAUDRATE_GENERATION  // Oversampling
};

uint32_t BigAdd(uint32_t *result, const uint32_t *x,
                          const uint32_t *y, size_t size)
{
    uint64_t carry = 0;
    while (size > 0) {
        carry += *x++;
        carry += *y++;
        *result++ = (uint32_t)carry;
        carry >>= 32;
        --size;
    }
    return (uint32_t)carry;
}
const uint32_t one_256bit[8] = {0x00000001, 0x00000000,
                                0x00000000, 0x00000000,
                                0x00000000, 0x00000000,
                                0x00000000, 0x00000000 };
const uint32_t efs_256bit[8] = {0xFFFFFFFF, 0xFFFFFFFF,
                                0xFFFFFFFF, 0xFFFFFFFF,
                                0xFFFFFFFF, 0xFFFFFFFF,
                                0xFFFFFFFF, 0xFFFFFFFF };

int main(void)
{
    uint32_t result[8];
    /* Halting WDT  */
    MAP_WDT_A_holdTimer();

    /* Selecting P1.2 and P1.3 in UART mode and P1.0 as output (LED) */
    MAP_GPIO_setAsPeripheralModuleFunctionInputPin(GPIO_PORT_P1,
             GPIO_PIN2 | GPIO_PIN3, GPIO_PRIMARY_MODULE_FUNCTION);
    MAP_GPIO_setAsOutputPin(GPIO_PORT_P1, GPIO_PIN0);
    MAP_GPIO_setOutputLowOnPin(GPIO_PORT_P1, GPIO_PIN0);

    /* Setting DCO to 24MHz (upping Vcore) */
    FlashCtl_setWaitState(FLASH_BANK0, 1);
    FlashCtl_setWaitState(FLASH_BANK1, 1);
    MAP_PCM_setCoreVoltageLevel(PCM_VCORE1);
    CS_setDCOCenteredFrequency(CS_DCO_FREQUENCY_24);

    /* Configuring UART Module */
    MAP_UART_initModule(EUSCI_A0_BASE, &uartConfig);

    /* Enable UART module */
    MAP_UART_enableModule(EUSCI_A0_BASE);

    /* Enabling interrupts */
    MAP_UART_enableInterrupt(EUSCI_A0_BASE, EUSCI_A_UART_RECEIVE_INTERRUPT);
    MAP_Interrupt_enableInterrupt(INT_EUSCIA0);
    MAP_Interrupt_enableSleepOnIsrExit();

    if(BigAdd(result,one_256bit,efs_256bit,8))
        MAP_UART_transmitData(EUSCI_A0_BASE, 'y');
    else
        MAP_UART_transmitData(EUSCI_A0_BASE, 'n');
    while(1)
    {
        MAP_UART_transmitData(EUSCI_A0_BASE, TXData);

        MAP_Interrupt_enableSleepOnIsrExit();
        MAP_PCM_gotoLPM0InterruptSafe();
    }
}

/* EUSCI A0 UART ISR - Echos data back to PC host */
void EUSCIA0_IRQHandler(void)
{
    uint32_t status = MAP_UART_getEnabledInterruptStatus(EUSCI_A0_BASE);

    MAP_UART_clearInterruptFlag(EUSCI_A0_BASE, status);

    if(status & EUSCI_A_UART_RECEIVE_INTERRUPT_FLAG)
    {
        RXData = MAP_UART_receiveData(EUSCI_A0_BASE);

        if(RXData != TXData)              // Check value
        {
            MAP_GPIO_setOutputHighOnPin(GPIO_PORT_P1, GPIO_PIN0);
            while(1);                       // Trap CPU
        }
        TXData++;
        MAP_Interrupt_disableSleepOnIsrExit();
    }

}

TMS320F28379D: DCSM - How to continue debugging from WAIT mode

$
0
0

Part Number:TMS320F28379D

I have locked the device and to debug the code, I place the TI boot loader into the WAIT mode.

After unlocking the device via the CCS debugger, I set a break point at the start address (0x80000).  However, pressing the continue button, causes the following error:

C28xx_CPU1: Error: (Error -1135 @ 0x3FF16A) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 8.1.0.00007)
C28xx_CPU1: Unable to determine target status after 20 attempts
C28xx_CPU1: Breakpoint Manager: Unable to remove requested AET job
C28xx_CPU1: Failed to remove the debug state from the target before disconnecting.  There may still be breakpoint op-codes embedded in program memory.  It is recommended that you reset the emulator before you connect and reload your program before you continue debugging

How can I continue debugging after unlocking the device?

LMH0397: LOCK_N pin in Power-off condition

$
0
0

Part Number:LMH0397

Hello,

According to the datasheet, LOCK_N pin is a 3.3V tolerant and open-drain output.

So Lock_N pin could be pulled up to 3.3V when LMH0397 is powered off.

But I can see the leakage current on the LOCK_N pin in the power-off condition.

Is it acceptable?

Best Regards,

M.Murai 

CCS/CC1200: CC1200DK

$
0
0

Part Number:CC1200

Tool/software: Code Composer Studio

Hi 

I am using CC1200 DK for wireless communication setup. I have exported the corresponded registers for radio settings from SmartRF studio 7 (both source file and head). When I add them to my code in code composer studio, it gives me an error. The error is (the code defines RF_SETTINGS): 

Description Resource Path Location Type
#20 identifier "RF_SETTINGS" is undefined CC1200.c /test10 line 2 C/C++ Problem

Can anyone help me on the issue? I'd appreciate it.

Saber

Viewing all 262198 articles
Browse latest View live


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