TPS3513: Can I extend the output current to 7.5 under the condition of 12v output voltage

October 20, 2017, 2:18 am

≫ Next: TPS7B7701-Q1: SENSE_EN pin and Output Filter

≪ Previous: CCS/CC1310: EasyLink Lib. , Does It support frequencies 433Mhz?

Part Number:TPS3513

Hi experts,

I have a customer who wants to use TPS3513 to implement over-current sensing, Is it possible to achieve output current 7.5A in the case of 12v output voltage? If possible, please give some directions. If not, do you have better solution?

Thanks& Best Regards

↧

TPS7B7701-Q1: SENSE_EN pin and Output Filter

October 20, 2017, 2:18 am

≫ Next: DRA746: VOUT AC timing during Default IO Timing Mode

≪ Previous: TPS3513: Can I extend the output current to 7.5 under the condition of 12v output voltage

Part Number:TPS7B7701-Q1

[ TPS7B7701-Q1 ] SENSE_EN pin and Output Filter

Hi,

Can you help my customer to finalize their TPS7B7701-Q1 deisgn?

<SENSE_EN pin>:

This pin can be connected to GND without any filter, correct?
From EVM schematics, it should be no problem.

<Output Filter>:

My customer would use following output filters. Can you take a look and let me know if you have any of concerns?

EMI filter BLM21PG331SN from Murata
www.murata.com/.../productdetail

10uF and 47pF to GND

10nH

Thank you for your support in advance.
Regards,
Ken

↧

DRA746: VOUT AC timing during Default IO Timing Mode

October 20, 2017, 2:30 am

≫ Next: LMR23625-Q1: External bias is applied to the output

≪ Previous: TPS7B7701-Q1: SENSE_EN pin and Output Filter

Part Number:DRA746

Hi Experts,

My customer looks at Jacinto6 Data Manual (SPRS950C) and wants to know D1 to D6 values when MODESELECT is 0 (i.e. Default IO Timing Mode). Can you please share the information? They understand following caution in DM Section 7.7.

The IO timings provided in this section are only valid if signals within a single IOSET are used. The IOSETs are defined in the Table 7-19 and Table 7-20.

The IO Timings provided in this section are only valid for some DSS usage modes when the corresponding Virtual IO Timings or Manual IO Timings are configured as described in the tables found in this section.

Best regards,
Ken

↧

LMR23625-Q1: External bias is applied to the output

October 20, 2017, 2:35 am

≫ Next: BQ2973: The Dout is always low

≪ Previous: DRA746: VOUT AC timing during Default IO Timing Mode

Part Number:LMR23625-Q1

Hi,

We got a question from the customer about LMR23625-Q1.
Could you help us?

[Question]
When the IC operates under the following condition, the external bias is applied to the output. Are there any concerns for these usage?

Part Number=LMR23625CF-Q1 *FPWM option
Vin=8~16V
Vout=5V
Iout=max 1.8A
fsw=460kHz by external clock

- Case 1
They are thinking the small current flows through from 5.5V to the output. It should be OK.

- Case 2
They are thinking the output voltage will be 5.5V and low side FET turn on to discharge from output capacitor in this condition. They are concerned the possibility to damage the IC.

Best Regards,
tateo

↧

BQ2973: The Dout is always low

October 20, 2017, 2:36 am

≫ Next: CC3200MOD: Self signed CAcertificate always expire in one month

≪ Previous: LMR23625-Q1: External bias is applied to the output

Part Number:BQ2973

Dear sir

I use the BQ2973 for the battery protection. Here is the schematic.

I used a DC power supply to add a 4V between BAT+ and BAT-. I found the CSD87313 is not on. I measued the Cout and Dout of BQ2973, Cout = 1 and Dout =0?

Why this is happened?

Thanks

Ren

↧

CC3200MOD: Self signed CAcertificate always expire in one month

October 20, 2017, 2:36 am

≫ Next: TPS54260: Burned in prototype

≪ Previous: BQ2973: The Dout is always low

Part Number:CC3200MOD

Hello everyone,
I'm facing a strange issue with a self signed certificate used by the mqtt client SSL connection, I generate a certificate that expires after 50 years, but one month after the certificate creation, the device returns the code -461 (connected with certificate date verification error) on connection. During the previous month I didn't have any issue on mqtt client connections.

I've followed the guide in the SDK documentation "CC32xx Serial Wifi.pdf" where I added the -days option when generating CA file, here my openssl commands to generate the certificate:

# Generate a CA certificate valid for 50 years:
$ openssl req -out CAroot.pem -new -x509 -days 18250
# this command create CAroot.pem and privkey.pem files.

# Generate server certificate/key pair:
$ openssl genrsa -out server.key 1024
$ openssl req -key server.key -new -out server.req -days 18250
$ echo 00 > file.srl
$ openssl x509 -req -in server.req -CA CAroot.pem -CAkey privkey.pem -CAserial file.srl -out server.pem
# these commands create server.key and server.pem files

# Translate CA certificate to DER format (to be read from the device):
$ openssl x509 -in CAroot.pem -inform PEM -out CAroot.der -outform DER

Then I flash the /crt/CAroot.der file on the CC3200, my mqtt client configuration is the following:

 
char *security_file_list[] = {"/crt/CAroot.der"};
 
SlMqttClientCtxCfg_t broker_config =
{
    {
        SL_MQTT_NETCONN_SEC,
        "192.168.1.120",
        8884,
        SL_SO_SEC_METHOD_TLSV1_2,
        SL_SEC_MASK_TLS_RSA_WITH_AES_256_CBC_SHA,
        1,
        security_file_list
    },
    SERVER_MODE,
    true,
};

I also tried with 90 days, but configuring a date farther than 30 days from today on the server and the device, the -461 error will be returned by the sl_Connect() function.

Am I doing something wrong?
Is there any configuration that I'm missing?

Thanks.

Regards,
Rosario

↧

TPS54260: Burned in prototype

October 20, 2017, 2:38 am

≫ Next: AM3352: eMMC1 timing characteristics clarifications

≪ Previous: CC3200MOD: Self signed CAcertificate always expire in one month

Part Number:TPS54260

Hello Team,
Our customer have question about TPS54260DGQR in their new design of Automotive GPS Tracker.
When they tested their prototype devices, one TPS54260DGQR burned after 2 hours of testing.

Could you check please the PCB and Schematic?(attached) Thetopology was taken from datasheet.

(Please visit the site to view this file)

↧

AM3352: eMMC1 timing characteristics clarifications

October 20, 2017, 2:45 am

≫ Next: TLC5971: Unable to address individual pixels

≪ Previous: TPS54260: Burned in prototype

Part Number:AM3352

Hi,

a customer is seeing output timing difference between datasheet & on board measurement.

He is willing to understand & clarify the cause of it.

- Input setup time (CMD): spec min/max : 6.8/17.8ns - measure 4.6ns

- Input Hold time (CMD) : spec min/max : 3/14ns - measure 16ns

- Input set-up time (Data0) : spec min/max : 6.8/17.8ns - measure 3.6ns

- Input Hold time (Data0) : spec min/max 3/14ns - measure 17ns

- Setup time MMC_DAT0 valid before MMC_CLK rising clock edge : Max 13.7ns - Measure 14.9

...

Setup is AM3352 connected to eMMC with read & write initiated from AM3352/Linux

Thanks

Nicolas

↧

TLC5971: Unable to address individual pixels

October 20, 2017, 2:49 am

≫ Next: TMS320F28377S: TMS320F28377S PowerPad

≪ Previous: AM3352: eMMC1 timing characteristics clarifications

Part Number:TLC5971

Hello

I am using an Arduino Uno to send data to a number of custom build led boards driven by the TLC5971 driver. Each board is fitted with 10 TLC5971 drivers which each drives 12 LED's (120 total/board). These 12 LED's are grouped into 4 groups, so each group consists of 3 LED's which in thise case is regarded as a pixel. In other words: each driver controls 4 pixels. I want to be able to address each of these pixels individually.

PROBLEM: When trying to address a pixel (a group of 3 LED's) the next pixel on the TLC5971 outputs light too. This goes on for the whole layout - the next pixel is always lid and i can't access only one pixel at once (see video).

I have at random times been able to make it work as it should. This was done by tweaking a few variables in the code related to brightness. But when I cycle the power to the boards everything goes back to the initial problem as described above. And after re-uploading the code that just worked a moment ago, it still doesn’t work. Therefore the code might not be the problem, and I am wondering if the problem has to do with a setting on the drives that I don’t know of…

TEST SETUP: Arduino Uno sending data via SPI bus to three boards which are daisy chained. (note: Arduino Due, Mega and M0 has been tested as well). The setup is driven by a standard 15V 10A switch mode psu. I am using Ulrich Stern's Arduino library for controlling TI's TLC59711 chip. (The TLC59711 is slightly different but the data package if the same, so shouldn't be a problem). I have looped through all data latch configurations on the TLC5971 by using the "setTmgrst" function in the library without luck.

The SPI output from the arduino has been checked through a scope but everything looks fine there too... This could be related to a software problem...

Any help is appreciated.

Pictures, video and code can be found here: https://we.tl/TwX2UWbbtv

Library:github.com/.../Tlc59711

↧

TMS320F28377S: TMS320F28377S PowerPad

October 20, 2017, 2:50 am

≫ Next: What's Peer-to-Peer mode speed (Throughput) ?

≪ Previous: TLC5971: Unable to address individual pixels

Part Number:TMS320F28377S

Hello,

I am developing a PCB with TMS320F28377S (PTP 130 pins) and I have some doubts regarding the PowerPad.

Like for example:
- How many pads does PowerPad make?
- What is the distance between pads?
- Is it necessary to weld the PowerPad or can I put thermal paste / silicone film?
- Should the PowerPad be connected to the Ground of the PCB?

I await your response.

Best regards,
Carlos Martins

↧

What's Peer-to-Peer mode speed (Throughput) ?

October 20, 2017, 2:52 am

≫ Next: TDA2EVM5777: basics of links and chains architecture used in Vision SDK

≪ Previous: TMS320F28377S: TMS320F28377S PowerPad

Hello,

I am trying to send NDEF 8Bytes message from one reader to another using SNEP protocol(LLCP).
My goal is to count what is the throughput of PUT request. (How many bytes of actual data I can send per second). In order to do that I am using timer. The thing is that in 5seconds I count around 30times of 8Bytes was send which will be 48Bytes/s. According to the protocols the bit rates possible are:

106kbits/s ----> 13250Bytes/s

212kbits/s ----> 26500Bytes/s

424kbits/s ----> 53000Bytes/s

so it means that my result for 106 is around 0.362% which I believe is not true.

So maybe someone can explain me what should I expect and maybe other ways to count throughput?

Kind regards,

Gytis

↧

TDA2EVM5777: basics of links and chains architecture used in Vision SDK

October 20, 2017, 2:54 am

≫ Next: low voltage bidirectional current limiter

≪ Previous: What's Peer-to-Peer mode speed (Throughput) ?

Part Number:TDA2EVM5777

Hi,everyone

My question is as title.

I am not familiar with basics of links and chains architecture used in Vision SDK.

Can somebody offer me the documents to study ?

Thanks

Best Regards,

Andy

↧

low voltage bidirectional current limiter

October 20, 2017, 3:04 am

≫ Next: BQ34Z100-G1: BQ34z100-g1. State of health

≪ Previous: TDA2EVM5777: basics of links and chains architecture used in Vision SDK

If there is any bidirectional current limiter (power switch, e-fuse or something similar) in TI portfolio that is working down to 1.8V?

↧

BQ34Z100-G1: BQ34z100-g1. State of health

October 20, 2017, 3:05 am

≫ Next: AWR1642BOOST: 2D FFT Output Q format

≪ Previous: low voltage bidirectional current limiter

Part Number:BQ34Z100-G1

Hi,

I am using BQ34z100-g1 with an 8s2p LiFePO4 battery.

I have charge the battery to full at 23ºC and the the FCC has raised from 6400 (=designCapacity) to 6613mAh.

After that I have introduce the battery in a climate room and set -20ºC. The FCC has dropped to 6075mAh. Then I have started a discontinuous dicharge at C/3.

Now, the battery is at 75% SoC with the next parameters

- FCC=6075 mAh

- RC = 4572 mAh

- TRC = 3852 mAh

- TFCC = 5233 mAh

- SoH = 100%

I have some doubts about them:

1. Why is SoH = 100%. I have read SoH is FCC/designCapacity() but in this case this is not correct.

2. What does the parameter SOH_DISP do? Is it necessary to read a real SoH?

3. If TRC is 3852 mAh (and is lower than TFCC), how can be RC 4572 mAh?

Thank you very much in advance,

↧