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

BQ25121: Excess quiescent current draw beyond specification when enabling the LDO in some devices

February 19, 2018, 1:01 pm
$
0
0

Part Number:BQ25121

I know this part is being deprecated and that BQ25120a should be used as a replacement where possible, but a first run of devices of our product shipped before the notice and replacement part became available. 

A couple devices in our first run came back to us with an issue of drawing too much power at all times, on the order of 100uA to 300uA. After investigation, we found that the current would disappear if we shut off the LDO powering just one sensor on the board (LS/LSO pin). We cut the trace and confirmed that the excess current draw persists (or gets even worse) when we turn on the LDO output and there is nothing connected to the output. 

It may be possible that this is a solder issue under the BGA but it's impossible for me to test that. Therefore I'd like to know if behavior like this has been observed before in the field or in the lab, and if my application might be doing anything to trigger the condition. Note that the majority of the devices in this product delivery don't exhibit this behavior and have quiescent currents in line with the datasheet specification, so this would have to either be a part to part variation or just that I've set something to a knife's edge of compatibility. The circuit is based off of the typical application circuit from the datasheet, but with a 10uF cap on PMID, no diode/connection between PMID and PG, and no battery monitoring. Both SYSOUT and the LDO are set to 3.3V in our application. 

It's important to me to have this answered because I need to know if this can also happen with the BQ25120a and if there's something I can to do prevent it. 

Regards, Nate

↧
Search

CCS/TMS320F28335: Target `main-build' not remade because of errors.

February 19, 2018, 1:04 pm
$
0
0

Part Number:TMS320F28335

Tool/software: Code Composer Studio

I just started having issues rebuilding my code this afternoon.  It was building fine before lunch.  I'm using CCS Version: 6.1.1.00022, XDC tools version 3.25.4.88 and BIOS version 6.35.5.54.

The output I am getting is as follows:

**** Build of configuration Debug_HW1v5 for project Sensor_Interface ****

Nothing to generate
' '
gmake[1]: Target `main-build' not remade because of errors.
gmake: *** [all] Error 2

**** Build Finished ****

This started happening after I told it to do a clean and rebuild.

I've tried the following things I have found on the forums already

1. Rebuild the project.

2. Delete the Debug directory (in my case Debug_HW11v5).

3.  Disable the antivirus.

Even after doing all these things the issue continued.  Any ideas on what could be causing the problem and how to get my project to build properly.

↧
↧

TUSB9261DEMO: TUSB9261DEMO

February 19, 2018, 1:05 pm
↧

VSP5611: Part not active?

February 19, 2018, 1:28 pm
$
0
0

Part Number:VSP5611

Hi Praveen

The TI's web site lists the VSP5611 as "active" and "production". So what is true? "Not recommended for New Designs" or "active"?

Best regards,

-Urs

↧

RM48L930: linker errors after enabling FreeRTOS mutex & timer support in HALCoGen

February 19, 2018, 1:46 pm
$
0
0

Part Number:RM48L930

Hello,

I created a HALCoGen FreeRTOS project (selected the RM48L950ZWT_FREERTOS device) and with default settings built the code Ok in CCSv7.  Then I went back into HALCoGen, clicked on the OS tab, and enabled 'Use Mutexes', and 'use Recursive Mutexes'.  I also added some test code in to create 2 tasks then call  vTaskStartScheduler in main().

With this config I get a linker error for missing function xQueueCreateMutexStatic.   This is because the default settings in FreeRTOSConfig.h are configSUPPORT_STATIC_ALLOCATION = 0.   But when I change this to configSUPPORT_STATIC_ALLOCATION = 1 I then get 5 other linker errors (vApplicationGetIdleTaskMemory, xEventGroupCreate, xQueueGenericCreate, xTaskCreate).  Any thoughts on this?  On a side note, it seems that if I do change the default settings in FreeRTOSConfig.h they will be lost the next time I generate code in HALCoGen, since there is no #ifndef preceding the #define configSUPPORT_STATIC_ALLOCATION  0.  I'm new to HALCoGen and FreeRTOS, what am I missing?  All comments are welcome!

Thank you,

Keith

↧
↧

CCS/TRF7970A: Building new project for RFID

February 19, 2018, 1:52 pm
$
0
0

Part Number:TRF7970A

Tool/software: Code Composer Studio

I would like to know how to build a new project based on the MSP430F5529 and the reference design.

I am new to the TI tool set and would like to take this down to only what I need.

Tag support for 14443 A/B and 15693 for read/write and collision.

Later I would do NFC and a USB Bootloader.

What is the best way to get a new project started and include the above.?

Thanks.

↧

LMG5200: LMG5200 evaluation boards

February 19, 2018, 1:58 pm
↧

AM5728: USB Type C Support

February 19, 2018, 2:03 pm
$
0
0

Part Number:AM5728

Hi Sitara Team,

I’ve got a customer that is looking for a processor that is able to interface with an Intel Realsense Depth Camera. From Intel’s website, it looks like this would plug directly in to a USB Type C port, is this something the AM57x supports?

Thanks!
Barend

↧
Search

SN74HC04: 5.5V tolerance

February 19, 2018, 2:14 pm
$
0
0

Part Number:SN74HC04

How does the input protection circuitry work for the 'HC04 to be 5.5V tolerant despite any Vcc voltage? 

↧
↧

TPS65130: Similar part or parts that gets more than ±15V?

February 19, 2018, 2:14 pm
$
0
0

Part Number:TPS65130

Hi,


I'm looking to put together a ±15V supplies for a circuit, but I need to keep the ripple and noise low.

I'd originally thought about using the TPS65130 and pair it up with the TPS7A39. However, with the ±15V as the maximum/minimum voltage for the TPS65130, the LDO drops me below ±14.5V when I include the error. Is there anything (even with combinations of other parts) that gets me to ±15.5V so that I can use the LDO? It looks like the negative supply is the problematic rail and most similar devices only get to -15V minimum. This application doesn't require high output current and I'll likely use less than 10mA of load. I'll be starting with a +5V supply.


Joseph Wu

↧

CC2541: Can IAR Embedded Workbench be told to ALWAYS compile a file?

February 19, 2018, 2:15 pm
$
0
0

Part Number:CC2541

This is somewhat off-topic...

Does anyone know a way to tell the IAR Embedded Workbench to ignore dependencies for one file and always compile it?

I'd like to have a version module that uses the __DATE__ and __TIME__ macros and always have it reflect the latest compile time.

I know I can have an external tool "touch" the file so that it will get compiled - but it would be nice if I could do it all from within IAR.

Thanks.

↧

ADC12J4000EVM: Compatibility with Xilinx ZCU102 Zynq Ultrascale+ MPSoC

February 19, 2018, 2:18 pm
$
0
0

Part Number:ADC12J4000EVM

Hi,

My customer has the question below:

We are working with the TI ADC12J4000EVM. We want to plug the FMC board into Xilinx ZCU102 Zynq Ultrascale+ MPSoC. We have compared the pinouts of the boards and other than the FMC_DEVCLK and FMC_SYSREF differential pins, they look compatible. From the ADC12J4000EVM schematic and ZCU102 datasheet, if we were to use Xilinx JESD IP to interface to the ADC, all the needed IO pins are accounted for. From our analysis, it looks like all the needed connections are available but have been informed from different sources (Xilinx/forums) that these parts are not compatible. Are there are any particular reasons for this?

Thanks,

Chuchen

↧

AWR1642: where I can find the document about mmwavelib functions?

February 19, 2018, 2:19 pm
$
0
0

Part Number:AWR1642

I want to understand what its functions  actually do, such as:

           mmwavelib_log2Abs32(

                       (int32_t *) obj->fftOut2D,

                       obj->log2Abs,

                       obj->numDopplerBins);

 

           mmwavelib_accum16(obj->log2Abs, obj->sumAbs, obj->numDopplerBins);

Best Regards,

Xinsi Lin

↧
↧

UC3525A: Dead time variation with themp

February 19, 2018, 2:39 pm
$
0
0

Part Number:UC3525A

My customer is using the UC3525 and is noticing a fair amount of variation of dead time with temp.  They have the following questions:

1.       Is deadtime controlled or characterized in any way? I see a curve in section 6.6 (above) but no measured specs in section 6.5 for deadtime.

2.       Is the correlation between dead time and temp (higher temp is more dead time) a known and “correct” behavior?

3.       Our design uses 470pF for CT. Section 6.3 recommends only down to 1000pF (twice our value), but the Maximum Frequency parameter in section 6.5 uses 470pF so it makes me think this may be fine.

Thanks,

Dan

↧

BQ24770: Inconsistent charge current

February 19, 2018, 2:49 pm
$
0
0

Part Number:BQ24770

Hello, 

I am using a BQ24770 based upon the reference BQ2477x-EVM, which originally had a BQ24773. While we've implemented all the necessary logic to control a BQ24770 in addition to a BQ24773, we see inconsistent results with the charging current from a BQ24770. If we enable charging, and write the charge current values, if there is any glitch in charging input to the BQ24770, then the charge current will drop and latch down to around 130ma. This behavior doesn't happen on a BQ24773. We're measuring the charge current from a reference fuel-gauge design for the bq4050. We had similar behavior when we would initiate charging with the BQ24770, which was set or defaulted to 3A of charge current, and would consistently latch down to 130ma, we corrected this by changing our charge current value to 896, which is close to the 15W of power we expect to get out of our chargers.

Is there some sort of protection mechanism built into the BQ24770 that would force the charge current down to this lower limit, and is there a way to bypass it without constantly checking the charge current via the fuelgauge and resetting the charge current on the bq24770? 

↧
Search

INA138: Need help - I've ruined 3 parts now and I don't know why

February 19, 2018, 2:52 pm
$
0
0

Part Number:INA138

Hi Folks,

I need to measure the charging current going to a 8S3P LiFePO4 battery pack and so far I've broken two INA138 chips and one INA168.  The max current is <11A and my sense resistor is 0.01 ohms.  The max  charge voltage is 30V and min is 27V.  Pin 3 is connected to the + end of the sense resistor.  I've measured the voltage at the sense resistor and it doesn't exceed 0.110 volts.  The gain is approximately 27.

Is there a recommended protection scheme for the inputs?  I haven't put a scope on the sense resistor but do you think that maybe a spike is getting to the '168 and killing it?  The leads from the sense resistor are about 12 inches long.

Any suggestions are greatly appreciated.

Thanks,

Richard

↧

CCS: How could I do a simple simulation?

February 19, 2018, 3:03 pm
$
0
0

Tool/software: Code Composer Studio

Hello

I have a simple question about simulation in Code Composer Studio. When I write a C based program in Codevision for an AVR microcontroller, I build the project and produce hex file. The simple simulation software, Proteus help me to do my simulation. In the category of microprocessors of Proteus I can find for example ATmega32 and so on. Even MSP430 family ICs can be used from that list, but I really know that DSP ICs like TMS320VC5509 don't exist there. 

This is my matter, how to do my simulations in Code Composer Studio or any other software similar to what I can do in Proteus for AVRs.


Thanks, 

↧
↧

CCS/TUSB9261DEMO: What Product Family to be installed while installing CCS v7.4?

February 19, 2018, 3:11 pm
$
0
0

Part Number:TUSB9261DEMO

Tool/software: Code Composer Studio

Hi,

I am trying to install Code Composer Studio v7.4 to build firmware for TUSB9261 DEMO board. I was asked to "Select Product Families to be installed". TUSB9261 uses an ARM Cotex-M3 microcontroller, but I don't see that option. Should I choose "TM4C12x ARM Cortex-M4f core-bases MCUs which looks the closest?

Thanks

Amy

↧

TUSB9261DEMO: How to force the demo board to bootloader mode?

February 19, 2018, 3:16 pm
$
0
0

Part Number:TUSB9261DEMO

Hi,

I loaded a bad firmware to the TUSB9261 demo board. Afterwards the board does not get enumerated in Windows 7, and I can't erase the firmware using TI Flash Burner. Is there a way to force it into bootloader mode?

Thanks,

Amy

↧

AWR1642BOOST: AWR1642BOOST & TIDEP-0092

February 19, 2018, 3:32 pm
↧
Viewing all 262198 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>