Part Number:DLPA2000
Hello all,
I am a proud owner of the DLP2010 and DLPC3430 in the specification of the DLP2010 (Revised July 2016) it is stated, that also a
DLPA-Driver is needed for running all the parts as a chipset. As far as I understand the specification from the DLPA2000 there is no
PCB incorporated. Do we have to design the board by ourselfs?
Best,
Lars
Part Number:TXS0108E
Hi, team,
My customer have one question about TXS0108E. The VIL is very low, about 0.15V maximum in datasheet. On customer's board, after the voltage drops to 0V, there will be one small rise with 0.15V peak value.
1. Will this bring risk to TXS0108E output?
2. If there is risk, what voltage should be the maximum voltage for VIH here?
Thanks.
Johnny
Part Number:THVD1552
I want to make RS485 to optical fiber media converter. Please confirm me these part numbers can I use or not .. please suggest me... please have look on the block diagram below. (Please visit the site to view this file)
Part Number:LAUNCHXL-CC1352R1
Tool/software: Code Composer Studio
Hi,
I'm working on a project that need DMM to work. I've included the header files as follow:
#include <dmm/dmm_scheduler.h>
#include <dmm/dmm_policy_blesp_wsnnode.h>
#include <OTHERSTUFF.h>
but I still have linking problems like below.
Any ideas?
Part Number:AM5748
Tool/software: TI-RTOS
From field:
Since IAR compiler(IAR systems) has higher code efficiency historically customer will try to build Processor SDK RTOS by it.
Are there any customers to do same approach for Processor SDK RTOS ?
:
Does your software group have any suggestion for their approach ?
Part Number:SIMPLELINK-CC3220-SDK
How can resolve this issue? I have a memory leak using detroyObject and destroyTemplate
Thank you very much
Lisa
Part Number:LM5035
Hello!
I imitated the LM5035 half-bridge demo board to make two converters using the synchronous rectification and the non-Synchronous rectification as follows: Vin= 16-40V(nominal value : 28V) Vout = 5V Iout = 4A fs=300KHz. The difference between these two converters is only the rectification method. When the Vin=28V and output current is below 45% Iout, the efficiency of the synchronous converter is lower than the non-synchronous one as shown in the picture. By measuring, I found that when the output current is below 10% Iout, the inductor current of the non-synchronous converter is in DCM state. For the synchronous converter, the inductor current is continuous and can be reversed at light load due to the bidirectional conduction characteristics of MOSFET. The current flowing from the drain to the source in the MOSFET causes a current flowing from the GND to the Vout. This circulating current consumes energy and brings additional losses. However, when the output current is in the range of 10% to 45%, the inductor currents of the two converters are all in CCM state. I would like to know what is the reason for the efficiency of synchronous rectification in this interval is lower than the non-synchronous one.
Thank you very much!
Rui Tang
Part Number:UCC28C42
Tool/software:TINA-TI or Spice Models
Hello,
I am simulating a DCDC flyback converter curcuit, which should have a output voltage of 12V in the range of 110V to 850V input voltage.
The simulation works, till I change the coupling coefficient to values <1.
I use a non-linear transformer with 3 windings.
If I simulate just the transformer and change the coupling coefficient then I have a very low output. Lower than I expect.(Please visit the site to view this file)(Please visit the site to view this file)
When I use coupled inductors and change mutal inductance (k<1) it works as expected.
Do I have to use coupled inductors for energy transfer or is something else false?
I hope someone can help me.
Tool/software: Code Composer Studio
Is there a way to download CCS Resource Explorer content for offline use? At my place of work all of our development workstations are not connected to the internet and I have been unable to find code examples for use with the TMS320C6657 EVM through the traditional means of web searches.
Thanks
Part Number:TPS54320
Hi, team,
My customer has one question about TPS54320 BOOT-PH voltage.
In their test, the BOOT-PH voltage DC value is 6~7V. And the maximum value is >7V, out of device BOOT-PH specification in datasheet.
Is this a normal phenomenon for TPS54320 in normal working condition?
Thanks.
Johnny
Part Number:MSP430FR4133
Tool/software: Code Composer Studio
Hello,
I am planing to build a little clock for evaluation with the MSP 430FR4133. I have found a lot of documents but stumbled over an example code. It is located in the SLAC625e.zip file. The file msp430fr413x_LCDE_01.c refers to some registers that I could not find in any documentation (datasheet, users guide and the slaa654a). The code in lines 162 to 178 seems to refer to some registers like LCDM0 or LCDPCTL0 that I could not find any reference to in any of the documents and CSS also does not know these registers. Is there any documentation on the LCD specific for the FR4133? And is there any include file that I can give in CSS? I seem to be missing a part about the registers and setup of com and segment.
Thanks for any tips.
/* --COPYRIGHT--,BSD_EX
* Copyright (c) 2014, 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.
*
*******************************************************************************
*
* MSP430 CODE EXAMPLE DISCLAIMER
*
* MSP430 code examples are self-contained low-level programs that typically
* demonstrate a single peripheral function or device feature in a highly
* concise manner. For this the code may rely on the device's power-on default
* register values and settings such as the clock configuration and care must
* be taken when combining code from several examples to avoid potential side
* effects. Also see www.ti.com/grace for a GUI- and www.ti.com/msp430ware
* for an API functional library-approach to peripheral configuration.
*
* --/COPYRIGHT--*/
//******************************************************************************
// MSP430FR413x Demo - LCD_E, Display a string "123456" on LCD in LPM3.5 mode.
//
// Description: Displays "123456" in sequence to the LCD display.
// f(LCD) = 32768Hz/((7+1)*16) = 256Hz.
// MSP430 works in LPM3.5 mode for ultra low power.
// ACLK = default REFO ~32768Hz,
// MCLK = SMCLK = default DCODIV ~1MHz.
//
// MSP430FR4133
// -----------------
// /|\| |
// | | XIN|--
// GND --|RST | ~32768Hz
// | | XOUT|--
// |--0.1uF--|R13 |
// |--0.1uF--|R23 (L3)COM3|----------------|
// |--0.1uF--|R33 (L2)COM2|---------------||
// --|LCDC2 (L1)COM1|--------------|||
// 4.7uF | (L0)COM0|-------------||||
// --|LCDC1 | -------------
// | L4~L39|---| 1 2 3 4 5 6 |
// | except L27~L35| -------------
// | | TI LCD
// | |
//
// LCD pin - Port Pin Map
// LCD pin G6021_LineX
// 1 L8 (P3.0)
// 2 L9 (P3.1)
// 3 L10 (P3.2)
// 4 L11 (P3.3)
// 5 L12 (P3.4)
// 6 L13 (P3.5)
// 7 L14 (P3.6)
// 8 L15 (P3.7)
// 9 L16 (P6.0)
// 10 L17 (P6.1)
// 11 L18 (P6.2)
// 12 L19 (P6.3)
// 13 L20 (P6.4)
// 14 L21 (P6.5)
// 15 L22 (P6.6)
// 16 L23 (P6.7)
// 17 L4 (P7.4)
// 18 L5 (P7.5)
// 19 L6 (P7.6)
// 20 L7 (P7.7)
// 21 L3 (P7.3)
// 22 L2 (P7.2)
// 23 L1 (P7.1)
// 24 L0 (P7.0)
// 25 -
// 26 -
// 27 -
// 28 -
// 29 -
// 30 -
// 31 -
// 32 L24 (P2.0)
// 33 L25 (P2.1)
// 34 L26 (P2.2)
// 35 L36 (P5.4)
// 36 L37 (P5.5)
// 37 L38 (P5.6)
// 38 L39 (P5.7)
//
// Cen Fang
// Wei Zhao
// Texas Instruments Inc.
// Oct 2013
// Built with IAR Embedded Workbench v5.60 & Code Composer Studio v5.5
//******************************************************************************
#include <msp430.h>
#define pos1 4 // Digit A1 - L4
#define pos2 6 // Digit A2 - L6
#define pos3 8 // Digit A3 - L8
#define pos4 10 // Digit A4 - L10
#define pos5 2 // Digit A5 - L2
#define pos6 18 // Digit A6 - L18
const char digit[10] =
{
0xFC, // "0"
0x60, // "1"
0xDB, // "2"
0xF3, // "3"
0x67, // "4"
0xB7, // "5"
0xBF, // "6"
0xE4, // "7"
0xFF, // "8"
0xF7 // "9"
};
int main( void )
{
WDTCTL = WDTPW | WDTHOLD; // Stop watchdog timer
// Configure XT1 oscillator
P4SEL0 |= BIT1 | BIT2; // P4.2~P4.1: crystal pins
do
{
CSCTL7 &= ~(XT1OFFG | DCOFFG); // Clear XT1 and DCO fault flag
SFRIFG1 &= ~OFIFG;
}while (SFRIFG1 & OFIFG); // Test oscillator fault flag
CSCTL6 = (CSCTL6 & ~(XT1DRIVE_3)) | XT1DRIVE_2; // Higher drive strength and current consumption for XT1 oscillator
// Disable the GPIO power-on default high-impedance mode
// to activate previously configured port settings
PM5CTL0 &= ~LOCKLPM5;
// Configure LCD pins
SYSCFG2 |= LCDPCTL; // R13/R23/R33/LCDCAP0/LCDCAP1 pins selected
LCDPCTL0 = 0xFFFF;
LCDPCTL1 = 0x07FF;
LCDPCTL2 = 0x00F0; // L0~L26 & L36~L39 pins selected
LCDCTL0 = LCDSSEL_0 | LCDDIV_7; // flcd ref freq is xtclk
// LCD Operation - Mode 3, internal 3.08v, charge pump 256Hz
LCDVCTL = LCDCPEN | LCDREFEN | VLCD_6 | (LCDCPFSEL0 | LCDCPFSEL1 | LCDCPFSEL2 | LCDCPFSEL3);
LCDMEMCTL |= LCDCLRM; // Clear LCD memory
LCDCSSEL0 = 0x000F; // Configure COMs and SEGs
LCDCSSEL1 = 0x0000; // L0, L1, L2, L3: COM pins
LCDCSSEL2 = 0x0000;
LCDM0 = 0x21; // L0 = COM0, L1 = COM1
LCDM1 = 0x84; // L2 = COM2, L3 = COM3
// Display "123456"
LCDMEM[pos1] = digit[1];
LCDMEM[pos2] = digit[2];
LCDMEM[pos3] = digit[3];
LCDMEM[pos4] = digit[4];
LCDMEM[pos5] = digit[5];
LCDMEM[pos6] = digit[6];
LCDCTL0 |= LCD4MUX | LCDON; // Turn on LCD, 4-mux selected
PMMCTL0_H = PMMPW_H; // Open PMM Registers for write
PMMCTL0_L |= PMMREGOFF_L; // and set PMMREGOFF
__bis_SR_register(LPM3_bits | GIE); // Enter LPM3.5
__no_operation(); // For debugger
}
Part Number:BLE-STACK
In order to be compatible with the ancient version of android and hope to support the MultiRole Demo.
I want to find the newest version SDK for support Bluetooth 4.1 downloading linker.
Now BLE-STACK v2.2.2 supports Bluetooth 4.2 for CC2640/CC2650 is available in
http://www.ti.com/tool/ble-stack, but BLE-STACK supports Bluetooth 4.1 is not available, where can I find the downloading linker?
Many thanks.
BR
Kelly
Part Number:TMDXDOCK280049M
I'm working with the TMDXCNC280049M control card and I can't connect using the on-board XDS100v2. I've followed the manual, wiki notes and can't find anything on forums. Can someone please offer suggestions to resolve my issue.
The Error I keep receiving is:
[Start]
Execute the command:
%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -F inform,logfile=yes -S pathlength -S integrity
[Result]
-----[Print the board config pathname(s)]------------------------------------
C:\Users\Antonios\AppData\Local\TEXASI~1\
CCS\ti\2\0\BrdDat\testBoard.dat
-----[Print the reset-command software log-file]-----------------------------
This utility has selected a 100- or 510-class product.
This utility will load the adapter 'jioserdesusb.dll'.
The library build date was 'May 30 2018'.
The library build time was '23:03:35'.
The library package version is '8.0.27.9'.
The library component version is '35.35.0.0'.
The controller does not use a programmable FPGA.
The controller has a version number of '4' (0x00000004).
The controller has an insertion length of '0' (0x00000000).
This utility will attempt to reset the controller.
This utility has successfully reset the controller.
-----[Print the reset-command hardware log-file]-----------------------------
The scan-path will be reset by toggling the JTAG TRST signal.
The controller is the FTDI FT2232 with USB interface.
The link from controller to target is direct (without cable).
The software is configured for FTDI FT2232 features.
The controller cannot monitor the value on the EMU[0] pin.
The controller cannot monitor the value on the EMU[1] pin.
The controller cannot control the timing on output pins.
The controller cannot control the timing on input pins.
The scan-path link-delay has been set to exactly '0' (0x0000).
-----[The log-file for the JTAG TCLK output generated from the PLL]----------
There is no hardware for programming the JTAG TCLK frequency.
-----[Measure the source and frequency of the final JTAG TCLKR input]--------
There is no hardware for measuring the JTAG TCLK frequency.
-----[Perform the standard path-length test on the JTAG IR and DR]-----------
This path-length test uses blocks of 64 32-bit words.
The test for the JTAG IR instruction path-length failed.
The JTAG IR instruction scan-path is stuck-at-ones.
The test for the JTAG DR bypass path-length failed.
The JTAG DR bypass scan-path is stuck-at-ones.
-----[Perform the Integrity scan-test on the JTAG IR]------------------------
This test will use blocks of 64 32-bit words.
This test will be applied just once.
Do a test using 0xFFFFFFFF.
Scan tests: 1, skipped: 0, failed: 0
Do a test using 0x00000000.
Test 2 Word 0: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 1: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 2: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 3: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 4: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 5: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 6: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 7: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
The details of the first 8 errors have been provided.
The utility will now report only the count of failed tests.
Scan tests: 2, skipped: 0, failed: 1
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 2
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 3
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 4
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 5
Some of the values were corrupted - 83.3 percent.
The JTAG IR Integrity scan-test has failed.
-----[Perform the Integrity scan-test on the JTAG DR]------------------------
This test will use blocks of 64 32-bit words.
This test will be applied just once.
Do a test using 0xFFFFFFFF.
Scan tests: 1, skipped: 0, failed: 0
Do a test using 0x00000000.
Test 2 Word 0: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 1: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 2: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 3: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 4: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 5: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 6: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 7: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
The details of the first 8 errors have been provided.
The utility will now report only the count of failed tests.
Scan tests: 2, skipped: 0, failed: 1
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 2
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 3
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 4
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 5
Some of the values were corrupted - 83.3 percent.
The JTAG DR Integrity scan-test has failed.
[End]
Part Number:CC3200
Hello everybody,
We're designed and produced 5000 pcs of smart thermometer which have CC3200 and CC2541 BLE modules.
Issue that appeared to us is following:
When scanning wi-fi networks routers that are using channels 12 and 13 are discovering only in 20-30% of cases. This make huge inconveniences to our customers in EU. Are there any solutions to solve this ?
We're using CC3200R1M2RGC and SDK v1.3.0
God bless everybody for help!
Part Number:LMP7721
Tool/software:TINA-TI or Spice Models
Dir Sir/Miss.
From LMP7721 specification, it tells me that the typical input capacitance of the LMP7721 is about 11pF, and I have download the spice model and run some simulation, I'm not sure whether the model has build this input capacitor in? and the capacitors are connecting between the inputs and the V- pin right?
Thanks
Jack
Part Number:TDC1000-TDC7200EVM
Hi!
I am wondering if it is possible to compile my own BSL flasher program using BSL Scripter source code on Mac OS X to flash the TDC1000-7200EVM firmware using a HEX-file through USB?
And do I need to know the password that is set to the MSP430? (Right now I flash it using TI MSP430 USB Firmware Upgrade Example v1.1.4, but I would like to assign serial numbers dynamically with the script).
Thanks in advance!
Kind regards,
Thibault
Part Number:DRV8837
Hello
My customer needs some help on the current limit for the DRV8837. Here is the problem description
We are using the DRV8837 to drive motors +/-1 Amp average with a 9V power supply (6 AA batteries) in production. There is 8" of wire between the driver and the motor.
We use caps across the motors to prevent EMI. We use a 0.1uf across the motor leads and two 0.1uf from each lead to the motor case. Electrically it looks like 0.15uf across the DRV output.
We found a problem because the DRV8837 is going into cycle-by-cycle peak current limit even with low average motor current (<0.5A).
We found that the peak current spec is exceeded with the three 0.1uf caps, but also with three 0.01uf caps, and even with no caps.
I'm attaching scope shots of those three measurements.
We want to drill down and find out a safe operating region where we know the limit will not fire. The length of time of the spike must play a roll, but we don't know what it is.
Can you please help us understand where the limits are and how the spike width affects it?
The scope traces are 1A/div. 0.1uf, 0.01uf, and no caps.
Thanks
Faizul Bacchus
Part Number:TLV320AIC3262
Reading the data sheets and user manuals for TLV320AIC3262EVM-U I couldn't find any reference to digital I2S inputs.
Are they available on this evaluation board?
I need to test a digital microphone.
Thanks.
Part Number:TPS65986
With the new ability in ver3.18 to specify the memory addresses of each region offset, it would be great if there was a way to save the desired default values as part of the .pjt file itself. That would help reduce the chances of someone messing up the region addresses each time we spin a new FW. Is this a feature you can add to the tool?