Part Number:ADS1247

I have a customer using a product of ours with the ADS 1247, and they are trying to measure a pulse that is not much bigger than the noise floor.  The problem is that they are seeing sets of 2 repeated data patterns, separated by one or more non repeating data points. The sensor is in continuous sample mode, and the microprocessor is polling the Busy pin before taking another data point.  Our custom software takes the data of the device and translates it into process units. I would expect to see repeated data points at the step size of the ADC, but not 3 data points precisely repeated.  Any insight?  

Part Number:CC2564

Team,

a new design based on CC2564MODA is working fine with android and apple smartphone.

However after some times (hours, days) , the bluetooth is not visible anymore. After a power reset, everything works fine again.

If the customer closes the stack and the communication => this works. But if he initializes the stack again, the following error occurs.

BSC_Initialize(HCI_DriverInformation,0); => BT_FUNCTION_ERROR -4

Thank you for a quick response how to solve this issue?

Best regards

Karim

Tool/software: Code Composer Studio

Hello.

I have been using CCSV8 (Version: 8.3.0.00009) with C2000 (ti-cgt-c2000_18.1.4.LTS) under Windows7. I am migrating to Ubuntu16. I can build the project under both OS, but the *.out file has a different size (a couple of kB). 

Is this something to expect?

I am using the same version of CCS and C2000 under both OS. I have check the building logs and they seem fine.

Thank you.

Best regards.

Part Number:SYSBIOS

Tool/software: TI-RTOS

Hi,

I am using SYSBIOS v6.75.01.05 for 66AK2G12 DSP.

I have created a task dynamically. I would like to pass only one argument to the task function.

Would the task function still need to be declared with two arguments?

Example:

Task_Params params;

Error_Block eb;

Task_Params_init(&params);

Error_init(&eb);

params.arg0 = (UArg) MyArg;

Task_create((Task_FuncPtr) TaskFunc, &params, &eb);

Now, can the Task Function definition be:

void TaskFunc(UArg arg0)

{

}

Or, does it need to be :

void TaskFunc(UArg arg0, UArg arg1)

{

}

Regards,

Amruta

Part Number:TPS65981

Hello Team,

Have a question brought up from one of the design engineers with NI.  They are wanting to program the TPS65981 blank SPI flash firmware over the I2C bus during manufacturing, but noticed that the TPS65981 only supports SPI flash updates if the SPI flash is already programmed. Does the TPS65981 support SPI flash updates of blank SPI flashes?

I believe the answer is no because from what I understand the PD controller will not be able to boot up without the SPI flash programmed. Do you know have any recommendations for the best way for NI to proceed with their programming throughout manufacturing?

Thanks in advance for your support. 

Part Number:MSP430F5659

Hello,

I'm trying to update the FW of my MSP430F5659 through radio.

1/ The example demo given by TI (SLAA600D–June 2013–Revised February 2018) works well between two LaunchPads F5529LP.

2/ my setup:

host: LaunchPad F5529LP

Target: F5659 board.

3/  What is working:

a) Radio communication between target and host works well.

c) parsed a sample blink using the image2C.pl utility.

I'm following a simple process:

After power up, The target enters directly to the boot mode.

The host sends the code segments, the checksum, and finally the BSL_JMP_APP_CMD.

No Flash erase.

Issues:

1/ I can see that my target is receiving RF packets, and doing like a Reset, and stick there, can't see my uploaded app running.

2/ is there anything that I should consider in the memory map configuration.

Here is my Target config:

#define __LARGE_DATA_MODEL__
/****************************************************************************/
/* SPECIFY THE SYSTEM MEMORY MAP */
/****************************************************************************/

/* RAM Memory Addresses */
__RAM_Start = 0x2400; /* RAM Start */
__RAM_End = 0x63FF; /* RAM End */
/* RAM shared between App and Bootloader, must be reserved */
PassWd = 0x2400; /* Password sent by App to force boot mode */
StatCtrl = 0x2402; /* Status and Control byte used by Comm */
CI_State_Machine = 0x2403; /* State machine variable used by Comm */
CI_Callback_ptr = 0x2404; /* Pointer to Comm callback structure */
/* Unreserved RAM used for Bootloader or App purposes */
_NonReserved_RAM_Start = 0x2408; /* Non-reserved RAM */

/* Flash memory addresses */
_Appl_Start = 0x8000; /* Start of Application area */
_Appl_End = 0xEFFF; /* End of Application area */
_Flex_Start = 0x10000; /* Start of flex space (app or download, project-dependent) */
_Flex_End = 0x87FFF; /* End of flex space (app or download, project-dependent) */

/* Reserved Flash locations for Bootloader Area */
__Boot_Start = 0xF000; /* Boot flash */
__Boot_Reset = 0xFFFE; /* Boot reset vector */
__Boot_VectorTable = 0xFF80; /* Boot vector table */
__Boot_SharedCallbacks_Len = 6; /* Length of shared callbacks (2 calls =4B(msp430) or 8B(msp430x) */
__Boot_SharedCallbacks = 0xFF7A; /* Start of Shared callbacks */
_Appl_Proxy_Vector_Start = 0xEF02; /* Proxy interrupt table */
/* Reserved Flash locations for Application Area */
_Appl_Checksum = (_Appl_Start); /* CRC16 of Application */
_Appl_Start_Memory = (_Appl_Start+2); /* Application Area */
_Appl_CRC_Size1 = (_Appl_End - _Appl_Start_Memory +1); /* Number of bytes in lower memory calculated for CRC */
_Appl_CRC_Size2 = (_Flex_End - _Flex_Start + 1); /* Number of bytes in upper memory calculated for CRC */

_Appl_Reset_Vector = (__Boot_Start - 2);

MEMORY
{
SFR : origin = 0x0000, length = 0x0010
PERIPHERALS_8BIT : origin = 0x0010, length = 0x00F0
PERIPHERALS_16BIT : origin = 0x0100, length = 0x0100
// RAM from _NonReserved_RAM_Start - __RAM_End
RAM : origin = 0x2408, length = 0x3FF8
RAM2 : origin = 0xF0000, length = 0xC000
USBRAM : origin = 0x1C00, length = 0x0800
INFOA : origin = 0x1980, length = 0x0080
INFOB : origin = 0x1900, length = 0x0080
INFOC : origin = 0x1880, length = 0x0080
INFOD : origin = 0x1800, length = 0x0080
// Flash from __Boot_Start -( __Boot_SharedCallbacks or INT_VECTOR_TABLE)
FLASH : origin = 0xF000, length = 0x0F6F
// Shared callbacks from __Boot_SharedCallbacks + Len (when used)
BOOT_SHARED_CALLBACKS : origin = 0xFF70, length = 0x10
FLASH2 : origin = 0x10000, length = 0x78000
// Boot vector Table from __Boot_VectorTable- __Boot_Reset
INT_VECTOR_TABLE : origin = 0xFF80, length = 0x7E
// Boot reset from __Boot_Reset-_Flash_End
RESET : origin = 0xFFFE, length = 0x0002

/*
INT00 : origin = 0xFF80, length = 0x0002
INT01 : origin = 0xFF82, length = 0x0002
INT02 : origin = 0xFF84, length = 0x0002
INT03 : origin = 0xFF86, length = 0x0002
INT04 : origin = 0xFF88, length = 0x0002
INT05 : origin = 0xFF8A, length = 0x0002
INT06 : origin = 0xFF8C, length = 0x0002
INT07 : origin = 0xFF8E, length = 0x0002
INT08 : origin = 0xFF90, length = 0x0002
INT09 : origin = 0xFF92, length = 0x0002
INT10 : origin = 0xFF94, length = 0x0002
INT11 : origin = 0xFF96, length = 0x0002
INT12 : origin = 0xFF98, length = 0x0002
INT13 : origin = 0xFF9A, length = 0x0002
INT14 : origin = 0xFF9C, length = 0x0002
INT15 : origin = 0xFF9E, length = 0x0002
INT16 : origin = 0xFFA0, length = 0x0002
INT17 : origin = 0xFFA2, length = 0x0002
INT18 : origin = 0xFFA4, length = 0x0002
INT19 : origin = 0xFFA6, length = 0x0002
INT20 : origin = 0xFFA8, length = 0x0002
INT21 : origin = 0xFFAA, length = 0x0002
INT22 : origin = 0xFFAC, length = 0x0002
INT23 : origin = 0xFFAE, length = 0x0002
INT24 : origin = 0xFFB0, length = 0x0002
INT25 : origin = 0xFFB2, length = 0x0002
INT26 : origin = 0xFFB4, length = 0x0002
INT27 : origin = 0xFFB6, length = 0x0002
INT28 : origin = 0xFFB8, length = 0x0002
INT29 : origin = 0xFFBA, length = 0x0002
INT30 : origin = 0xFFBC, length = 0x0002
INT31 : origin = 0xFFBE, length = 0x0002
INT32 : origin = 0xFFC0, length = 0x0002
INT33 : origin = 0xFFC2, length = 0x0002
INT34 : origin = 0xFFC4, length = 0x0002
INT35 : origin = 0xFFC6, length = 0x0002
INT36 : origin = 0xFFC8, length = 0x0002
INT37 : origin = 0xFFCA, length = 0x0002
INT38 : origin = 0xFFCC, length = 0x0002
INT39 : origin = 0xFFCE, length = 0x0002
INT40 : origin = 0xFFD0, length = 0x0002
INT41 : origin = 0xFFD2, length = 0x0002
INT42 : origin = 0xFFD4, length = 0x0002
INT43 : origin = 0xFFD6, length = 0x0002
INT44 : origin = 0xFFD8, length = 0x0002
INT45 : origin = 0xFFDA, length = 0x0002
INT46 : origin = 0xFFDC, length = 0x0002
INT47 : origin = 0xFFDE, length = 0x0002
INT48 : origin = 0xFFE0, length = 0x0002
INT49 : origin = 0xFFE2, length = 0x0002
INT50 : origin = 0xFFE4, length = 0x0002
INT51 : origin = 0xFFE6, length = 0x0002
INT52 : origin = 0xFFE8, length = 0x0002
INT53 : origin = 0xFFEA, length = 0x0002
INT54 : origin = 0xFFEC, length = 0x0002
INT55 : origin = 0xFFEE, length = 0x0002
INT56 : origin = 0xFFF0, length = 0x0002
INT57 : origin = 0xFFF2, length = 0x0002
INT58 : origin = 0xFFF4, length = 0x0002
INT59 : origin = 0xFFF6, length = 0x0002
INT60 : origin = 0xFFF8, length = 0x0002
INT61 : origin = 0xFFFA, length = 0x0002
INT62 : origin = 0xFFFC, length = 0x0002
RESET : origin = 0xFFFE, length = 0x0002
*/
}

/****************************************************************************/
/* SPECIFY THE SECTIONS ALLOCATION INTO MEMORY */
/****************************************************************************/

SECTIONS
{
.bss : {} > RAM | RAM2 /* GLOBAL & STATIC VARS */
.data : {} > RAM | RAM2 /* GLOBAL & STATIC VARS */
.sysmem : {} > RAM /* DYNAMIC MEMORY ALLOCATION AREA */
.stack : {} > RAM (HIGH) /* SOFTWARE SYSTEM STACK */

.text : {}>> FLASH2 /* CODE */
.text:_isr : {} > FLASH | FLASH2 /* ISR CODE SPACE */
.cinit : {} > FLASH /* INITIALIZATION TABLES */
.const : {} > FLASH /* CONSTANT DATA */

.cio : {} > RAM /* C I/O BUFFER */

.pinit : {} > FLASH /* C++ CONSTRUCTOR TABLES */
.init_array : {} > FLASH /* C++ CONSTRUCTOR TABLES */
.mspabi.exidx : {} > FLASH /* C++ CONSTRUCTOR TABLES */
.mspabi.extab : {} > FLASH /* C++ CONSTRUCTOR TABLES */

.infoA : {} > INFOA /* MSP430 INFO FLASH MEMORY SEGMENTS */
.infoB : {} > INFOB
.infoC : {} > INFOC
.infoD : {} > INFOD

.BOOT_APP_VECTORS : {} > BOOT_SHARED_CALLBACKS
/* MSP430 INTERRUPT VECTORS */
.BOOT_VECTOR_TABLE : {} > INT_VECTOR_TABLE

....

Part Number:DS90UB953-Q1

Hello,

I need to interface DS90UB953 FPDLinkIII serializer to a device featuring LVDS dual-link interface. I also need to interface DS90UB954 to a device featuring LVDS dual-link interface only.

In other words I need a bridge to convert from LVDS dual-link to MIPI CSI-2 for DS90UB953 and another bridge to convert from MIPI CSI-2 to LVDS dual-link for DS90UB954.

Can you suggest a suitable solution? Does TI have such bridges in its portfolio?

Thank you for your valuable support and best regards.

Part Number:TMS320F280049

Hi,

My customer want to develop themselves programming software used on production line to do programming via XDS100.

They don't have C2000-GANG, so can't do it by C2000-GANG.dll.

Is there any advice about the programming software development? Thanks a lot.

Part Number:ADS8548

Hi,

We are using a ADS8548 in our system, configured via SW mode (SW/HW pins is pulled up), to use internal reference at 2.5V. Configuration register is set to 0x800083FF on system power up.

Most of the time, there is no issue, but at some customers, every once is a while it seems like the device is powered up & configured but for some reason, the reference is 0V instead of 2.5V.

Any issue you are familiar with that may explain this?

Thanks,

Shachar.

Part Number:TMS570LC4357

Hi,

The following thread has been locked but has no answer: here.

Can you clarify it please?

Gael

Part Number:TPS54560

Hi there,

I wanted to check if there is a possible way to parallel 2 TPS5450 to double the total current available to the load?

I've had a read of two similar post that says these devices aren't really designed for this purpose and recommends the UCC39002http://www.ti.com/product/UCC39002, to regulate the feedback for each device.

However I also stumbled upon this which seems to show the parallel operation of two very similar devices (TPS54620) http://www.ti.com/lit/an/slva389/slva389.pdf , and just wanted to check whats the main difference between these two devices?

Kind Regards

Ricky

Part Number:TMS320F28035

Tool/software: Code Composer Studio

Hello, 

I want to upload different programs into the piccolo F28035 control card of TI board, i faced an error shown as follow:

- c_int00()at boot28.asm:261 0x3E8439 (the entry point was reached)

So because of this line i can't upload correctly the .out file generated from Matlab/Simulink!

How can i deal with this! Thank you.

Part Number:LM3478

Hi,

I have a prototype circuit board with a boost converter utilizing the LM3478 switching regulator. 

The output voltage on the DCDC has a low frequency ripple on it when no load is connected on the DCDC's output (2V, 5Hz). When the load connected to the DCDC's output is increased the frequency for the ripple increases until the ripple disappears. I have measured the voltage across the MOSFET (VDS) and it seems like the regulator is only driving the MOSFET for a short period of time (Burst-mode?, over voltage protection triggered?).

What causes the output voltage ripple at low loads? Is this a feature like pulse-skipping our is some internal protection triggered at low loads?

*I have attached the schematic below.

Schematic:

Regards,

Niklas

Part Number:AM6548

Tool/software: TI-RTOS

Hello,

I can reproduce the issue described in (Target not run as the symbol "main" is not defined)

with CCS  8.2.0.00007 as well.

Is there any fix in the pipeline for the next update, or a workaround?

Best regards,

Thomas

Part Number:TAS5805M

Tool/software: Code Composer Studio

Audio Software team,

I have PPC 3.1.1 installed.  I would like to connect the TAS5805M EVM, but PPC doesn’t appear to be working.  When I click Available EVM Apps, the GUI stays empty.  When I click Installed EVM Apps to Download the Platform Update (not sure if this is necessary), it says Failed to Download.

Under My Secure Software, it says I have access to TAS5825-SW, but there are only PDFs there.

What am I doing wrong?  Or do I need to be granted access? 

Thanks,
Darren

Part Number:OPA4350

Dear TI,

I'm working on a project similar to TIDA-01606: 10-kW Three-level, Three-Phase Grid tie Inverter Reference Design for Solar String Inverters.

As I am not so familar with OpAmps and there are so many of them available, I wonder why exactly you chose the OPA4340 (current) and OPA4350 (voltage).

Could I relpace the OPA-devices for example with the TLV27x? Or would this lead to any performance degradation, because it has lower bandwidh and more noise leaving anything else unchanged?

Is the TLV27x also suitable to drive the ADC on the 28377D or a similar C2000 device.

I hope you can help me.

MK

Part Number:TMDS570LS31HDK

Tool/software: Code Composer Studio

After developing and debugging a project ok in Debug mode  I thought I would do a Release version.

After adding some missing include paths to match the Debug settings the project seemed to build ok.

But there is no .out file in the Release directory like there is in the Debug directory and no other feedback.

Any ideas?

Part Number:TDA2P-ACD

Tool/software: TI-RTOS

Hi,

I would like to setup LCD on TDA2p to 1920x1080@30 fps. Can you send me required timing parameters for this configuration?

Is there anything else that I should change in order to get 1920x1080@30 fps (RGB888) except following:

pVInfo->mInfo.pixelClock = 78000U;
pVInfo->mInfo.fps = 32U;
pVInfo->mInfo.hBackPorch = 32U;
pVInfo->mInfo.hSyncLen = 16U;
pVInfo->mInfo.hFrontPorch = 112U;
pVInfo->mInfo.vBackPorch = 16U;
pVInfo->mInfo.vSyncLen = 2U;
pVInfo->mInfo.vFrontPorch = 17U;

This parameteres are for 1920x1200, can you send me same for 1920x1080.

Best Regards,

Stefan.

Part Number:BQ77915

Hi,

I'm from the University of Florida. I have a robot that has 8 thrusters, a computer, and several sensors, cameras, and other small actuators. We have been running with a 48V rail comprised of two 6S LiPos in series. We're changing thrusters so we're switching to a 24V rail and taking the two batteries we're running in series and running them in parallel. We're taking this opportunity to finally add in battery protection. This is an area I do not have much experience with so I am looking for advice.

The overall topology I'm imagining something like this:

The biggest thing I want to protect against is over-discharging, or under-volting, the batteries. For at least this initial version, we will continue to remove the batteries and put them on a dedicated charger. This circuit only needs to protect against discharging events. OT and OC protection would be nice. We'd also like to be able to monitor the battery voltage and current.

This is what I'm thinking based on what I've found poking around TI's website:

Battery protection:

The BQ77915 looks like a chip that would meet and exceed our needs, but we'd have to use two because our batteries are 6S and put multiple FETs in parallel because our maximum power draw at nominal 24V is 1200W per battery.

Alternatively, I was thinking we might have to implement a solution where we monitor the battery voltage with a uC and then cut power if the batteries get too low. We have a relay on each thruster that we used for our "kill" functionality and we could add a relay to the computer/sensor power. The benefit here would be that we don't have to do FET paralleling but the disadvantage would be the time to design and test the circuit.

Battery monitoring:

We have a separate circuit that does this that we've used on other vehicles in our lab. It is based on the INA302

Battery paralleling:

We've used the LM5050-2 to do this before, we plan on continuing to use the chip on this vehicle as well.

Part Number:AWR1642BOOST

I miss information about the VPP voltage, and the efuse function overall. Is this described in any document? I have not found it in any of the technical documents ont your homepage.

/emil