Part Number:LM35

Hi Team,

Customer is trying to understand if their condition is 24V single Supply, they need LM35 to measure -30C to 70C. 

They can just just follow Datasheet Figure.18 circuit config as below, correct?

1N914 purpose is to offset the 0C output voltage to 2 diode drop (say 1.0V), so at -30C, we expect to see 1.0V at output-, 0.7V at output+, correct?

Thanks.

Andrew

Part Number:LAUNCHXL-CC1310

Tool/software:TI-RTOS

Hello 

I started to work with SimpleLink-CC13x0-SDK with CC1310-Launchpad Rev.1.3

My question is about, how can i combine different TI-RTOS examples under CC13x0-SDK.

In my application, i need both UART and PWM, it will start PWM, according the command coming from UART.

The "portable_CC1310_LAUNCHXL_tirtos_ccs" is good for start and working fine, and "pwmled_CC1310_LAUNCHXL_tirtos_ccs" is doing what i need.

I changed the "temperatureThread" in the portable_CC1310_LAUNCHXL_tirtos_ccs demo, with the "mainThread" in PWM Led example. But when i run the project, PWM is not working fine, it could 

not open Board_PWM0.

  pwm1 = PWM_open(Board_PWM0, &params);

  if (pwm1 == NULL) {

          /* Board_PWM0 did not open */

           while (1);

  }

Can anyone help me?

BR,

Cagdas

SIMPLELINK-CC13X0-SDK

Part Number:DS90UB925Q-Q1

Hi,

I have problems to find the USB driver for the above mentioned eval-board.  I tried to find them in the drivers folder of the national semiconductor corp.

without success.

I have found the driver document in the ALP and try to update driver in the PC device management, but fail.

I follow the forum below and do not work, and the forum about the update flash is not clear.

e2e.ti.com/.../937139

I want to have some hint to debug the problem, thanks!

Part Number:PCM1808

Hi Team,

I want to config PCM1808 works at 44.1kHz sample rate. Schematic is showed as below. From my understanding, the only one thing is that the master clock (MCLK) should be 11.2896MHz, right? Anything else miss? thanks!

Part Number:LDC1101

Hi,

Please let me ask about RP +L Mode and LHR Mode as below.

1. In page 10 of DS, it states that the sensor Q should be at least 10 for RP measurements in RP + L mode. Then is there any limitation of Q value in LHR mode? And please let me know why there is such difference between RP + L mode and LHR mode if there is no limitation of Q value in LHR mode.
2. In RP + L mode, it states that Q value should be at least 10. Can you please explain why you recommend at least 10? And please let me know what do you concern if we use it lower than 10 Q value in RP + L mode?
3. In LHR mode, can we see correct operation with lower Q value than 10 if we use the sensor amplitude between 0.25 Vpk and 1.25 Vpk?

Best Regards,

Satoshi / Japan Disty

Part Number:BQ24195

I pulled up the /CE (3,3V) pin to disable recharge but the IC still charges battery: I can't read the register but the STAT pin is low (I used a pull up resistor on this pin) meaning charging and I can measure recharge current in the battery.

Any ideas?

Part Number:CC3220SF-LAUNCHXL

Hello team,

my customer is currently evaluating the CC3220SF Launchpad and wants to use the Radio Test Tool. For using that, a specific Firmware needs to be used to change the RF settings. Is that correct?

According to the Wiki (http://processors.wiki.ti.com/index.php/CC3100_%26_CC3200_Radio_Tool) the bin file can be found under: „CC32xxBoardApplication Binary“, but this folder is missing!

Can you tell me where the bin file is located?

Thank you in advance and kind regards,

Felix

Part Number:J6EVM5777

we have generated all the images using the instructions described here "http://www.omappedia.org/wiki/6AO.1.0_Engineering_Drop" 

• Copy u-boot.img and MLO files to an SD card (boot partition) and then boot the target board from this external SD card.

      i) how to partition the SD card?

     ii)  we have got MLO files while preparing eMMC images. we have two MLO files noted 

            MLO and GP_MLO files.

   should i copy the both MLO files? 

Part Number:LAUNCHXL-F28377S

Tool/software: Code Composer Studio

Hi, 

I am using now F28377S launchpad, i connected to 24C16A eeprom launchpad's i2c communication pins and i did also pull up to 3.3V level each of communication pins.

But i cannot writing any byte to eeprom, is anyone can help me? I2C code is below;

//###########################################################################
// FILE: Example_2837xSI2c_eeprom.c
// TITLE: I2C EEPROM Example
//
//! \addtogroup cpu01_example_list
//! <h1>I2C EEPROM Example (i2c_eeprom)</h1>
//!
//! This program will write 1-14 words to EEPROM and read them back.
//! The data written and the EEPROM address written to are contained
//! in the message structure, I2cMsgOut1. The data read back will be
//! contained in the message structure I2cMsgIn1.
//!
//! \b External \b Connections \n
//! - This program requires an external I2C EEPROM connected to
//! the I2C bus at address 0x50.
//
//###########################################################################
// $TI Release: F2837xS Support Library v180 $
// $Release Date: Fri Nov 6 16:27:58 CST 2015 $
// $Copyright: Copyright (C) 2014-2015 Texas Instruments Incorporated -
// http://www.ti.com/ ALL RIGHTS RESERVED $
//###########################################################################

#include "F28x_Project.h" // Device Headerfile and Examples Include File

// Note: I2C Macros used in this example can be found in the
// F2837xS_I2C_defines.h file

// Prototype statements for functions found within this file.
void I2CA_Init(void);

Uint16 ReadEEPROM(Uint16 eepromAdress);
void WriteEEPROM(Uint16 eepromAdress, Uint16 data);

Uint16 DataRead[256];

Uint16 EEPROM_MODE;
enum EEPROM_MODES {WRITE, READ};

//__interrupt void i2c_int1a_isr(void);
void pass(void);
void fail(void);

#define I2C_SLAVE_ADDR 0x00
#define I2C_NUMBYTES 2

// Global variables
// Two bytes will be used for the outgoing address,
// thus only setup 14 bytes maximum

Uint16 PassCount;
Uint16 FailCount;

void main(void)
{
// Uint16 Error;
// Uint16 i;

// Step 1. Initialize System Control:
// PLL, WatchDog, enable Peripheral Clocks
// This example function is found in the F2837xS_SysCtrl.c file.
InitSysCtrl();

// Step 2. Initialize GPIO:
// This example function is found in the F2837xS_Gpio.c file and
// illustrates how to set the GPIO to it's default state.
InitGpio();

// For this example, only init the pins for the SCI-A port.
// These functions are found in the F2837xS_Gpio.c file.
GPIO_SetupPinMux(42, GPIO_MUX_CPU1, 6);
GPIO_SetupPinMux(43, GPIO_MUX_CPU1, 6);

// Step 3. Clear all __interrupts and initialize PIE vector table:
// Disable CPU __interrupts
DINT;

// Initialize PIE control registers to their default state.
// The default state is all PIE __interrupts disabled and flags
// are cleared.
// This function is found in the F2837xS_PieCtrl.c file.
InitPieCtrl();

// Disable CPU __interrupts and clear all CPU __interrupt flags:
IER = 0x0000;
IFR = 0x0000;

// Initialize the PIE vector table with pointers to the shell Interrupt
// Service Routines (ISR).
// This will populate the entire table, even if the __interrupt
// is not used in this example. This is useful for debug purposes.
// The shell ISR routines are found in F2837xS_DefaultIsr.c.
// This function is found in F2837xS_PieVect.c.
InitPieVectTable();

// Interrupts that are used in this example are re-mapped to
// ISR functions found within this file.
EALLOW; // This is needed to write to EALLOW protected registers
//PieVectTable.I2CA_INT = &i2c_int1a_isr;
EDIS; // This is needed to disable write to EALLOW protected registers

// Step 4. Initialize the Device Peripherals:
I2CA_Init();

// Step 5. User specific code

// Clear Counters
PassCount = 0;
FailCount = 0;

// Enable __interrupts required for this example

// Enable I2C __interrupt 1 in the PIE: Group 8 __interrupt 1
//PieCtrlRegs.PIEIER8.bit.INTx1 = 1;

// Enable CPU INT8 which is connected to PIE group 8
IER |= M_INT8;
EINT;

unsigned int j = 0;
EEPROM_MODE = WRITE;

// Application loop
for(;;)
{
if (EEPROM_MODE == WRITE)
{
WriteEEPROM(j, 10+j);
WriteEEPROM(j+1, 10+j+1);

j=j+2;

if (j>=200) {
j = 0;
EEPROM_MODE = READ;
DELAY_US(1e6); // Wait for 1sec to READ mode
}
}

if (EEPROM_MODE == READ)
{
DataRead[j] = ReadEEPROM(j);
DataRead[j+1] = ReadEEPROM(j+1) ;

j=j+2;

if (j>=200)
j = 0;
pass();
}
} // end of for(;;)
} // end of main

void I2CA_Init(void)
{
I2caRegs.I2CMDR.all = 0X0000;
// Initialize I2C
I2caRegs.I2CSAR.all = I2C_SLAVE_ADDR; // Slave address - EEPROM control code

I2caRegs.I2CPSC.all = 6; // Prescaler - need 7-12 Mhz on module clk
I2caRegs.I2CCLKL = 10; // NOTE: must be non zero
I2caRegs.I2CCLKH = 5; // NOTE: must be non zero
//I2caRegs.I2CIER.all = 0x24; // Enable SCD & ARDY __interrupts

I2caRegs.I2CMDR.all = 0x0020; //0x0020; // Take I2C out of reset
// Stop I2C when suspended
I2caRegs.I2CFFTX.all = 0x6000; // Enable FIFO mode and TXFIFO
I2caRegs.I2CFFRX.all = 0x2040; // Enable RXFIFO, clear RXFFINT,

return;
}

Uint16 ReadEEPROM(Uint16 eepromAddress)
{
Uint16 addresslow;
Uint16 addresshigh;
Uint16 tempdata;

I2caRegs.I2CMDR.bit.IRS = 1; // reset I2C
while (I2caRegs.I2CSTR.bit.BB == 1); // busy loop
I2caRegs.I2CSTR.bit.SCD = 1; // Clear the SCD bit (stop condition bit)
while(I2caRegs.I2CMDR.bit.STP == 1); // stop bit loop

addresshigh = eepromAddress>>8;
addresslow = eepromAddress;
I2caRegs.I2CSAR.all = I2C_SLAVE_ADDR; //0x0050;

while (I2caRegs.I2CSTR.bit.BB == 1);
I2caRegs.I2CMDR.all = 0x2620; // start, no stop bit, master, tx, reset I2C
I2caRegs.I2CCNT = 0x0002;
I2caRegs.I2CDXR.all = addresshigh;
I2caRegs.I2CDXR.all = addresslow;
while(!I2caRegs.I2CSTR.bit.ARDY); // all ready?

I2caRegs.I2CMDR.all = 0x2C20; // start, stop bit when CNT =0, master, rx, reset I2C
I2caRegs.I2CCNT = 1;

if(I2caRegs.I2CSTR.bit.NACK == 1)
{
I2caRegs.I2CSTR.all = I2C_CLR_NACK_BIT; // 0x0002
}
I2caRegs.I2CMDR.bit.STP = 1; // stop bit when CNT=0

while(!I2caRegs.I2CSTR.bit.SCD); // stop bit detected?

//tempdata = I2caRegs.I2CDRR << 8; // read data
tempdata = I2caRegs.I2CDRR.all;

DELAY_US(100);

return(tempdata);
}

void WriteEEPROM(Uint16 eepromAdress, Uint16 data)
{
Uint16 addresslow;
Uint16 addresshigh;

I2caRegs.I2CMDR.bit.IRS = 1; // reset I2C

addresshigh = (eepromAdress>>8)&0x00FF;
addresslow = eepromAdress&0x00FF;
I2caRegs.I2CSAR.all = I2C_SLAVE_ADDR; //0x0050; // EEPROM control bits + address (A0-A2). for 24LC256, 0 1 0 1 0 A0 A1 A2

while (I2caRegs.I2CSTR.bit.BB == 1);

I2caRegs.I2CCNT = 3 ;
I2caRegs.I2CMDR.all = 0x6E20; //start, stop, no rm, reset i2c
I2caRegs.I2CDXR.all = addresshigh;
I2caRegs.I2CDXR.all = addresslow;
// I2caRegs.I2CDXR = (data >> 8) & 0x00FF; // high byte data
I2caRegs.I2CDXR.all = data; // low byte data
I2caRegs.I2CMDR.bit.STP = 1; // stop bit when CNT=0

while(!I2caRegs.I2CSTR.bit.SCD); // stop bit detected?

DELAY_US(5000); // 5ms = write cycle time of 24LC256 - based on datasheet 24LC256

return;
}

void pass()
{
asm(" ESTOP0");
for(;;);
}

void fail()
{
asm(" ESTOP0");
for(;;);
}

//===========================================================================
// No more.
//===========================================================================

Part Number:TMS320C6678

Hello!
I use VLFFT demo from e2e.ti.com/.../303599 for calculate 1024K FFT. It's run on Evaluation Board TMDSEVM6678LE.

I use SDK CCS 6.2.0.
I am using the folowing products to compile the VLFFT project are listed below:
XDCTools 3.23.4.60
EDMA3 LLD 2.11.5
IPC 1.24.2.27
MCSDK 2.1.2.6
SYS/BIOS 6.33.4.39

I can't achieve same characteristics which were performed in document "Very large FFT for TMS320C6678 processors". I have next results fo FFT 1024K:
8 Core: 32.484165 ms vs 6.403 ms in document;
4 Core: 35.519242 ms vs 9.605 ms in document;
2 Core: 58.152080 ms vs 19.328 ms in document;
1 Core: 115.402698 ms vs 38.557 ms in document.

Also calculations are dismatch reference results. log is:
max error index: 0
real, 8.515877, real_ref: 36592189439.999998
imag, 8.515877, imag_ref: 36592189439.999998
Fail!!!

Why does it happen?(Please visit the site to view this file)(Please visit the site to view this file)

Part Number:INA333

Tool/software:TINA-TI or Spice Models

Hi Everyone,

I have been trying to get used to using TINA, which is a great simulation software when it does work, but I just seem can't get it to work.

For example the schematic shown below, when I add in the instrumentation amplifier circuit, OPA330 for some reason stops working.

If I remove INA333, then it works again. I have encountered the same issue in the past, it seems to me that TINA has problem simulation more than one IC?

Simulation with both INA333 and OPA330, as shown by the graph, Vout which is the output from OPA330 is at 1.65 flat, when I should see a sine

wave with 200mVpp biased at 1.65V.

VG2 = sine at 100Hz with 200mVpp and biased at 1.65.

Simulation without INA333 circuit, as shown in the graph, once INA333 has been removed, OPA330 simulates correctly.

VG2 = sine at 100Hz with 200mVpp and biased at 1.65.

I have not changed the OPA330 circuity at all, I only removed the INA333 circuity.

Is there a reason why this is happening?

The reason for the OPA330 circuit is because I was using it to remove the DC offset from the INA333, however it wasn't wokring and after some debugging I found

that the opamp just wasn't doing anything.  Please see this post https://e2e.ti.com/support/amplifiers/precision_amplifiers/f/14/t/633065.

Thanks for the help.

Rgs,

Bryan

(Please visit the site to view this file)

I have included the schematic from TINA here.

Part Number:TLV62095

Hi ,

I used TPS62095 in my design. My manager asked the second source. Then i saw TLV62095 is pin-to-pin compatible to TPS62095 and even cheaper. 

Can anyone told me the difference between TLV62095 and TPS62095?

Regards,

Wei

Part Number:TLV320AIC3101

Hi,

is it possible to mix LineIN1 audio input on TLV320AIC3101 with an I2S audio input, so that they both go through the Volume Control block? 

I managed to get the two streams mixed, but only in case where LineIN1 bypasses data converters, so that output of the PGA is routed directly to the output stage. The data routing configuration that I have at the moment is shown in blue on the attached image and the one which I want to have is shown in red.

Part Number:BQ40Z60

I am not using the GPIO 1 and 2

How should i attach them in the design. floating/high/low?

Thanks

Bryan

Part Number:AMC1301

Hello Team

What does input bandwidth mean？1000kHZ？ Can use it to meassure 1000kHZ signal？

Part Number:PROCESSOR-SDK-AM335X

We’re trying to build Qt 5.9.x against TI processor SDK version 3 or 4 (tried both) but are experiencing a build error in the Qt chromium stuff.

Here is the build error we're getting (a sample of actual build output is pasted below):

error: inlining failed in call to always_inline someFunctionName: target specific option mismatch

We get a whole slew of these errors, all for different functions.

We think this is telling us there is a problem with some ARM-specific -m compiler option, that we're either missing one or have one that isn't valid. But we're not sure which option.

Here are the compiler options that the build output shows are being given to the files that are failing to compile:

-Wno-\#pragma-messages -fno-strict-aliasing --param=ssp-buffer-size=4 -fstack-protector -funwind-tables -fPIC -pipe -pthread -march=armv7-a -mfloat-abi=hard -mtune=generic-armv7-a -mfpu=vfpv3-d16 -mthumb -g0 --sysroot=../../../../../../ti-processor-sdk-linux-am335x-evm-04.01.00.06/linux-devkit/sysroots/armv7ahf-neon-linux-gnueabi -fvisibility=hidden -Wno-psabi -Wno-unused-local-typedefs -Wno-maybe-uninitialized -Wno-missing-field-initializers -Wno-unused-parameter -O3 -fno-ident -fdata-sections -ffunction-sections

Anyone have any idea which option we're missing or giving that we shouldn't be?

Thanks in advance!

[5348/17331] CC obj/third_party/opus/bundled_opus/warped_autocorrelation_FIX.o

[5349/17331] CC obj/third_party/opus/bundled_opus/celt_neon_intr.o
FAILED: obj/third_party/opus/bundled_opus/celt_neon_intr.o 
/home/user//ti-processor-sdk-linux-am335x-evm-04.01.00.06/linux-devkit/sysroots/x86_64-arago-linux/usr/bin/arm-linux-gnueabihf-gcc -MMD -MF obj/third_party/opus/bundled_opus/celt_neon_intr.o.d -DOPUS_BUILD -DOPUS_EXPORT= -DHAVE_LRINT -DHAVE_LRINTF -DVAR_ARRAYS -DFIXED_POINT -DOPUS_ARM_ASM -DOPUS_ARM_INLINE_ASM -DOPUS_ARM_INLINE_EDSP -DOPUS_ARM_MAY_HAVE_EDSP -DOPUS_ARM_MAY_HAVE_MEDIA -DOPUS_ARM_MAY_HAVE_NEON -DOPUS_ARM_MAY_HAVE_NEON_INTR -DOPUS_HAVE_RTCD -DV8_DEPRECATION_WARNINGS -DUSE_UDEV -DUSE_AURA=1 -DUSE_OPENSSL_CERTS=1 -DUSE_OZONE=1 -DNO_TCMALLOC -DDISABLE_NACL -DENABLE_TASK_MANAGER=1 -DENABLE_THEMES=1 -DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL -DCHROMIUM_BUILD -DFIELDTRIAL_TESTING_ENABLED -DTOOLKIT_QT -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -DNDEBUG -DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 -DOPUS_FIXED_POINT -I../../3rdparty/chromium/third_party/opus/src/celt -I../../3rdparty/chromium/third_party/opus/src/silk -I../../3rdparty/chromium/third_party/opus/src/silk/fixed -I../../3rdparty/chromium/third_party/opus/src -Igen -I../../3rdparty/chromium -I../../3rdparty/chromium/third_party/opus/src/include -Wno-\#pragma-messages -fno-strict-aliasing --param=ssp-buffer-size=4 -fstack-protector -funwind-tables -fPIC -pipe -pthread -march=armv7-a -mfloat-abi=hard -mtune=generic-armv7-a -mfpu=vfpv3-d16 -mthumb -g0 --sysroot=../../../../../../ti-processor-sdk-linux-am335x-evm-04.01.00.06/linux-devkit/sysroots/armv7ahf-neon-linux-gnueabi -fvisibility=hidden -Wno-psabi -Wno-unused-local-typedefs -Wno-maybe-uninitialized -Wno-missing-field-initializers -Wno-unused-parameter -O3 -fno-ident -fdata-sections -ffunction-sections -c ../../3rdparty/chromium/third_party/opus/src/celt/arm/celt_neon_intr.c -o obj/third_party/opus/bundled_opus/celt_neon_intr.o
In file included from ../../3rdparty/chromium/third_party/opus/src/celt/arm/celt_neon_intr.c:37:0:
../../3rdparty/chromium/third_party/opus/src/celt/arm/celt_neon_intr.c: In function 'xcorr_kernel_neon_fixed':
/home/user/ti-processor-sdk-linux-am335x-evm-04.01.00.06/linux-devkit/sysroots/x86_64-arago-linux/usr/lib/gcc/arm-linux-gnueabihf/6.2.1/include/arm_neon.h:8921:1: error: inlining failed in call to always_inline 'vld1_s16': target specific option mismatch
vld1_s16 (const int16_t * __a)
^~~~~~~~
../../3rdparty/chromium/third_party/opus/src/celt/arm/celt_neon_intr.c:47:14: note: called from here
int16x4_t y0 = vld1_s16(y);
^~
In file included from ../../3rdparty/chromium/third_party/opus/src/celt/arm/celt_neon_intr.c:37:0:
/home/user/ti-processor-sdk-linux-am335x-evm-04.01.00.06/linux-devkit/sysroots/x86_64-arago-linux/usr/lib/gcc/arm-linux-gnueabihf/6.2.1/include/arm_neon.h:9010:1: error: inlining failed in call to always_inline 'vld1q_s32': target specific option mismatch
vld1q_s32 (const int32_t * __a)
^~~~~~~~~
../../3rdparty/chromium/third_party/opus/src/celt/arm/celt_neon_intr.c:44:14: note: called from here
int32x4_t a = vld1q_s32(sum);

And so on (many more of the same error).

Part Number:MSP430FR5994

I see support for this in the IQmathlib for other targets, but nothing for the MSP430FR5994.  The MSP430® IQmathLib Users Guide shows support for IQN, N= 1 to 30.

My ultimate goal is to "printf" the IQ31 values in some readable form.  So, conversion to float or ASCII is fine.

Part Number:TUSB7340

Dear all,

My customer want to know at what condition they need the external EEPROM and if it used, how to write to the EEPROM.

Could you please help send me the tools?

My customer want to initialize the four USBs simultaneously, can they save the EEPROM, if EEPROM is not used, does it mean they just use the default value in the register?

Besides, what are the steps to write to the EEPROM, could you please help describe in details.

Thanks.

Hi team,

Customer wants to know if we have some HDMI-to-MIPI solution?

Any recommended products or introduction portfolio slides? Many thanks!

regards,

Bell

Part Number:RI-STU-MRD2

Hello,

Can i buy from this website or from an supplier of your company an RFID HDX Reader for (multiple) external antenna's with a read range around 40 cm or 20 cm front 20 cm back?

thank you so much