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

CC3120: Question about CC3120 802.11g and n mode

$
0
0

Part Number: CC3120

Hi,

I have two questions about the wifi mode on CC3120:

1. does CC3120 can be set as single mode g or n when it works as station mode?

2. is there difference of power consumption in g or n mode? for example, n mode can go high speed and large range, so the power consumption will be higher as well?

Thanks,

Jeff


AM5728: USB XHCI problem in u-boot on AM572x EVM

$
0
0

Part Number: AM5728

We are working towards our own board based on the AM572x EVM. I am having problems with XHCI USB devices in u-boot. All tested devices work fine in linux but if "usb start" is run during u-boot, the XHCI controller fails and u-boot aborts and reboots. EHCI and other devices all work fine, but something as simple as an XHCI hub or XHCI thumb drive causes this issue. The issue is identical on all 3 USB ports on the EVM and occurs regardless of whether or not other USB devices are plugged into other ports on the EVM.

I saw this link https://e2e.ti.com/support/interface/f/138/t/592829 which may or may not be related, but it stated that a different version of u-boot resolved the problem. I am wondering if this could be the case with the AM572x and if so where I might find the allegedly magic code.

The condensed part of the error message in u-boot is

Device not responding to set address.

USB device not accepting new address (error=80000000)
Freeing device node: 4
usb_control_msg: request: 0x1, requesttype: 0x23, value 0x1 index 0x2 length 0x0
usb_control_msg: request: 0x0, requesttype: 0xA3, value 0x0 index 0x3 length 0x4
WARN halted endpoint, queueing URB anyway.
Unexpected XHCI event TRB, skipping... (fdf32b70 00000000 13000000 02008400)
BUG at drivers/usb/host/xhci-ring.c:495/abort_td()!
BUG!
resetting ...

And this is the full u-boot log with _DEBUG turned on in common/usb.c and drivers/usb/host/xhci.c:


U-Boot SPL 2018.11-00198-g61b8194d56-dirty (Aug 30 2019 - 11:27:53 -0700)
DRA752-GP ES2.0
Trying to boot from MMC1
no pinctrl state for default mode
no pinctrl state for default mode
Loading Environment from FAT... Unknown partition type - will lookup.
Loading from FAT interface mmc 0:1, file uboot.env
*** Warning - bad CRC, using default environment

U-Boot 2018.11-00198-g61b8194d56-dirty (Aug 30 2019 - 11:27:53 -0700)

CPU : DRA752-GP ES2.0
DRAM: 2 GiB
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
Loading Environment from FAT... Unknown partition type - will lookup.
Loading from FAT interface mmc 0:1, file uboot.env
*** Warning - bad CRC, using default environment

SCSI: SATA link 0 timeout.
AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
flags: 64bit ncq stag pm led clo only pmp pio slum part ccc apst
scanning bus for devices...
Found 0 device(s).

Net:
Warning: ethernet@48484000 using MAC address from ROM
eth0: ethernet@48484000
Hit any key to stop autoboot: 0
starting USB...
USB0: // Halt the HC: 48890020
// Reset the HC
Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.00
scanning bus 0 for devices... New Device 0
set address 1
usb_control_msg: request: 0x5, requesttype: 0x0, value 0x1 index 0x0 length 0x0
USB_REQ_SET_ADDRESS
scrlen = 0
req->length = 0
Len is 0
usb_control_msg: request: 0x6, requesttype: 0x80, value 0x100 index 0x0 length 0x12
USB_DT_DEVICE request
scrlen = 18
req->length = 18
usb_control_msg: request: 0x6, requesttype: 0x80, value 0x200 index 0x0 length 0x9
USB_DT_CONFIG config
scrlen = 25
req->length = 9
usb_control_msg: request: 0x6, requesttype: 0x80, value 0x200 index 0x0 length 0x1F
USB_DT_CONFIG config
scrlen = 25
req->length = 31
get_conf_no 0 Result 25, wLength 31
if 0, ep 0
##EP epmaxpacketin[1] = 8
set configuration 1
usb_control_msg: request: 0x9, requesttype: 0x0, value 0x1 index 0x0 length 0x0
scrlen = 0
req->length = 0
Len is 0
new device strings: Mfr=1, Product=2, SerialNumber=0
usb_control_msg: request: 0x6, requesttype: 0x80, value 0x300 index 0x0 length 0xFF
USB_DT_STRING config
scrlen = 4
req->length = 255
USB device number 1 default language ID 0x409
usb_control_msg: request: 0x6, requesttype: 0x80, value 0x301 index 0x409 length 0xFF
USB_DT_STRING config
scrlen = 14
req->length = 255
usb_control_msg: request: 0x6, requesttype: 0x80, value 0x302 index 0x409 length 0xFF
USB_DT_STRING config
scrlen = 42
req->length = 255
Manufacturer U-Boot
Product XHCI Host Controller
SerialNumber
usb_control_msg: request: 0x6, requesttype: 0xA0, value 0x2A00 index 0x0 length 0x4
USB_DT_HUB config
scrlen = 8
req->length = 4
usb_control_msg: request: 0x6, requesttype: 0xA0, value 0x2A00 index 0x0 length 0xC
USB_DT_HUB config
scrlen = 8
req->length = 12
usb_control_msg: request: 0x0, requesttype: 0xA0, value 0x0 index 0x0 length 0x4
scrlen = 2
req->length = 4
usb_control_msg: request: 0x3, requesttype: 0x23, value 0x8 index 0x1 length 0x0
scrlen = 0
req->length = 0
Len is 0
usb_control_msg: request: 0x3, requesttype: 0x23, value 0x8 index 0x2 length 0x0
scrlen = 0
req->length = 0
Len is 0
usb_control_msg: request: 0x0, requesttype: 0xA3, value 0x0 index 0x1 length 0x4
SPEED = FULLSPEED
scrlen = 4
req->length = 4
usb_control_msg: request: 0x0, requesttype: 0xA3, value 0x0 index 0x1 length 0x4
SPEED = FULLSPEED
scrlen = 4
req->length = 4
usb_control_msg: request: 0x1, requesttype: 0x23, value 0x10 index 0x1 length 0x0
clear port connect change, actual port 1 status = 0x6e1
scrlen = 0
req->length = 0
Len is 0
usb_control_msg: request: 0x3, requesttype: 0x23, value 0x4 index 0x1 length 0x0
scrlen = 0
req->length = 0
Len is 0
usb_control_msg: request: 0x0, requesttype: 0xA3, value 0x0 index 0x1 length 0x4
SPEED = FULLSPEED
scrlen = 4
req->length = 4
usb_control_msg: request: 0x3, requesttype: 0x23, value 0x4 index 0x1 length 0x0
scrlen = 0
req->length = 0
Len is 0
usb_control_msg: request: 0x0, requesttype: 0xA3, value 0x0 index 0x1 length 0x4
SPEED = HIGHSPEED
scrlen = 4
req->length = 4
usb_control_msg: request: 0x1, requesttype: 0x23, value 0x14 index 0x1 length 0x0
clear port reset change, actual port 1 status = 0xe03
scrlen = 0
req->length = 0
Len is 0
New Device 1
set address 2
usb_control_msg: request: 0x5, requesttype: 0x0, value 0x2 index 0x0 length 0x0
Setting up addressable devices fdf37880
Successful Address Device command
xHC internal address is: 1
usb_control_msg: request: 0x6, requesttype: 0x80, value 0x100 index 0x0 length 0x12
usb_control_msg: request: 0x6, requesttype: 0x80, value 0x200 index 0x0 length 0x9
usb_control_msg: request: 0x6, requesttype: 0x80, value 0x200 index 0x0 length 0x29
get_conf_no 0 Result 41, wLength 41
if 0, ep 0
if 0, ep 1
##EP epmaxpacketin[1] = 1
set configuration 1
usb_control_msg: request: 0x9, requesttype: 0x0, value 0x1 index 0x0 length 0x0
Successful Configure Endpoint command
new device strings: Mfr=0, Product=0, SerialNumber=1
usb_control_msg: request: 0x6, requesttype: 0x80, value 0x300 index 0x0 length 0xFF
USB device number 2 default language ID 0x409
usb_control_msg: request: 0x6, requesttype: 0x80, value 0x301 index 0x409 length 0xFF
Manufacturer
Product
SerialNumber 660400590392
usb_control_msg: request: 0x6, requesttype: 0xA0, value 0x2900 index 0x0 length 0x4
usb_control_msg: request: 0x6, requesttype: 0xA0, value 0x2900 index 0x0 length 0x9
usb_control_msg: request: 0xB, requesttype: 0x1, value 0x1 index 0x0 length 0x0
usb_control_msg: request: 0x0, requesttype: 0xA0, value 0x0 index 0x0 length 0x4
usb_control_msg: request: 0x3, requesttype: 0x23, value 0x8 index 0x1 length 0x0
usb_control_msg: request: 0x3, requesttype: 0x23, value 0x8 index 0x2 length 0x0
usb_control_msg: request: 0x3, requesttype: 0x23, value 0x8 index 0x3 length 0x0
usb_control_msg: request: 0x3, requesttype: 0x23, value 0x8 index 0x4 length 0x0
usb_control_msg: request: 0x0, requesttype: 0xA3, value 0x0 index 0x2 length 0x4
SPEED = SUPERSPEED
scrlen = 4
req->length = 4
usb_control_msg: request: 0x0, requesttype: 0xA3, value 0x0 index 0x2 length 0x4
SPEED = SUPERSPEED
scrlen = 4
req->length = 4
usb_control_msg: request: 0x1, requesttype: 0x23, value 0x10 index 0x2 length 0x0
clear port connect change, actual port 2 status = 0x1203
scrlen = 0
req->length = 0
Len is 0
usb_control_msg: request: 0x3, requesttype: 0x23, value 0x4 index 0x2 length 0x0
scrlen = 0
req->length = 0
Len is 0
usb_control_msg: request: 0x0, requesttype: 0xA3, value 0x0 index 0x2 length 0x4
SPEED = SUPERSPEED
scrlen = 4
req->length = 4
usb_control_msg: request: 0x1, requesttype: 0x23, value 0x14 index 0x2 length 0x0
clear port reset change, actual port 2 status = 0x1203
scrlen = 0
req->length = 0
Len is 0
New Device 2
set address 3
usb_control_msg: request: 0x5, requesttype: 0x0, value 0x3 index 0x0 length 0x0
Setting up addressable devices fdf37880
Successful Address Device command
xHC internal address is: 2
usb_control_msg: request: 0x6, requesttype: 0x80, value 0x100 index 0x0 length 0x12
usb_control_msg: request: 0x6, requesttype: 0x80, value 0x200 index 0x0 length 0x9
usb_control_msg: request: 0x6, requesttype: 0x80, value 0x200 index 0x0 length 0x1F
get_conf_no 0 Result 31, wLength 31
if 0, ep 0
##EP epmaxpacketin[1] = 2
set configuration 1
usb_control_msg: request: 0x9, requesttype: 0x0, value 0x1 index 0x0 length 0x0
Successful Configure Endpoint command
new device strings: Mfr=0, Product=0, SerialNumber=0
Manufacturer
Product
SerialNumber
usb_control_msg: request: 0x6, requesttype: 0xA0, value 0x2A00 index 0x0 length 0x4
usb_control_msg: request: 0x6, requesttype: 0xA0, value 0x2A00 index 0x0 length 0xC
usb_control_msg: request: 0x0, requesttype: 0xA0, value 0x0 index 0x0 length 0x4
usb_control_msg: request: 0x3, requesttype: 0x23, value 0x8 index 0x1 length 0x0
usb_control_msg: request: 0x3, requesttype: 0x23, value 0x8 index 0x2 length 0x0
usb_control_msg: request: 0x3, requesttype: 0x23, value 0x8 index 0x3 length 0x0
usb_control_msg: request: 0x3, requesttype: 0x23, value 0x8 index 0x4 length 0x0
usb_control_msg: request: 0x0, requesttype: 0xA3, value 0x0 index 0x1 length 0x4
usb_control_msg: request: 0x0, requesttype: 0xA3, value 0x0 index 0x2 length 0x4
usb_control_msg: request: 0x0, requesttype: 0xA3, value 0x0 index 0x3 length 0x4
usb_control_msg: request: 0x0, requesttype: 0xA3, value 0x0 index 0x4 length 0x4
usb_control_msg: request: 0x0, requesttype: 0xA3, value 0x0 index 0x1 length 0x4
usb_control_msg: request: 0x0, requesttype: 0xA3, value 0x0 index 0x2 length 0x4
usb_control_msg: request: 0x0, requesttype: 0xA3, value 0x0 index 0x3 length 0x4
usb_control_msg: request: 0x0, requesttype: 0xA3, value 0x0 index 0x4 length 0x4
usb_control_msg: request: 0x0, requesttype: 0xA3, value 0x0 index 0x1 length 0x4
usb_control_msg: request: 0x0, requesttype: 0xA3, value 0x0 index 0x2 length 0x4
usb_control_msg: request: 0x0, requesttype: 0xA3, value 0x0 index 0x3 length 0x4
usb_control_msg: request: 0x0, requesttype: 0xA3, value 0x0 index 0x4 length 0x4
usb_control_msg: request: 0x0, requesttype: 0xA3, value 0x0 index 0x1 length 0x4
usb_control_msg: request: 0x0, requesttype: 0xA3, value 0x0 index 0x2 length 0x4
usb_control_msg: request: 0x0, requesttype: 0xA3, value 0x0 index 0x3 length 0x4
usb_control_msg: request: 0x0, requesttype: 0xA3, value 0x0 index 0x4 length 0x4
usb_control_msg: request: 0x0, requesttype: 0xA3, value 0x0 index 0x1 length 0x4
usb_control_msg: request: 0x0, requesttype: 0xA3, value 0x0 index 0x2 length 0x4
usb_control_msg: request: 0x1, requesttype: 0x23, value 0x14 index 0x2 length 0x0
usb_control_msg: request: 0x0, requesttype: 0xA3, value 0x0 index 0x2 length 0x4
usb_control_msg: request: 0x1, requesttype: 0x23, value 0x10 index 0x2 length 0x0
usb_control_msg: request: 0x3, requesttype: 0x23, value 0x4 index 0x2 length 0x0
usb_control_msg: request: 0x0, requesttype: 0xA3, value 0x0 index 0x2 length 0x4
usb_control_msg: request: 0x1, requesttype: 0x23, value 0x14 index 0x2 length 0x0
New Device 3
set address 4
usb_control_msg: request: 0x5, requesttype: 0x0, value 0x4 index 0x0 length 0x0
Setting up addressable devices fdf37880
Device not responding to set address.

USB device not accepting new address (error=80000000)
Freeing device node: 3
usb_control_msg: request: 0x1, requesttype: 0x23, value 0x1 index 0x2 length 0x0
usb_control_msg: request: 0x0, requesttype: 0xA3, value 0x0 index 0x3 length 0x4
WARN halted endpoint, queueing URB anyway.
Unexpected XHCI event TRB, skipping... (fdf38140 00000000 13000000 02008400)
BUG at drivers/usb/host/xhci-ring.c:495/abort_td()!
BUG!
resetting ...

CCS/MSP430F2274: "Unknown device"/"cannot connect to target" error

$
0
0

Part Number: MSP430F2274

Tool/software: Code Composer Studio

I am attempting to write/debug a program to my MSP430F2274, but CCS gives me an "unknown device" error:

I've attempted downloading MSPWare and additional libraries, tried a different programmer, tried a different MSP chip, tried using tool and target power supplies, tried adjusting capacitor values, but none seem to resolve the issue. Here's a quick shot of my system info:

Compiler/CC2640R2F: CC2640R2F

$
0
0

Part Number: CC2640R2F

Tool/software: TI C/C++ Compiler

Hello!

I have 2 problems and asks for help.

The first problem i have - is a problem with a malloc function in my project based on simple peripheral.

This screenshot contains memory allocation of project. So i have about 7k ram

But when i try to allocate a 2048 bytes buffer using malloc - cc2640r2 just hangs. 

So i think that the heap size is small - is it possible to make it bigger? in app_ble_m3 file defines heap function 0x80.

And the second problem is the spi problem -

 

This is how i define hardware pins, and then i do 

volatile static PIN_Id chipselect_main;

bool ll_spi_init( PIN_Id chipselect, spi_device_e device_type )
{
bool result = false;
SPI_Params params = { 0 };

SPI_init();

switch (device_type)
{

case SPI_DAC:

SPI_Params_init(&params);
params.bitRate = 400000;
params.dataSize = 16;
params.frameFormat = SPI_POL0_PHA1;
params.mode = SPI_MASTER;

break;

case SPI_FLASH:

SPI_Params_init(&params);
params.bitRate = 100000;
params.dataSize = 8;
params.frameFormat = SPI_POL1_PHA1;//SPI_POL1_PHA1;
params.mode = SPI_MASTER;

break;

default:

break;

}

spiHandle = SPI_open(SPI_BUS_NUM, &params);

if (spiHandle != NULL) {
result = true;
}
chipselect_main = chipselect;
SPI_control(spiHandle, SPICC26XXDMA_SET_CSN_PIN, &chipselect_main);

return result;
}

If i do this instantly after i2c init

bool ll_i2c_init( void )
{
bool result = false;
I2C_Params params = {0};

I2C_init();
I2C_Params_init( &params );
params.bitRate = I2C_100kHz;

i2cHandle = I2C_open( I2C_BUS_NUM, &params );
if (i2cHandle != NULL) {
result = true;
}

return result;
}

then i sometimes have problems - cc2640r2 hangs too:(

and not instantly after spi open.

Best regards, Dmitrity.

BQ40Z80EVM-020: Two questions regarding cell data

$
0
0

Part Number: BQ40Z80EVM-020

  • I had the board set up with a 6s resistor network, with 6-7 shorted as specified in the datasheet for a 6s configuration. I confirmed in Battery Management Studio that it's reading all 6, but over SMBus, I was only able to read 4 cell voltages, then looked to the datasheet to see that it only actually lists the command codes for 4 cells. Is this correct- that the 7s BMS only designed to provide 4 cell voltages?
  • Also, what is "Cell Current"? Should this not be the same for each battery in series? Is it pack current +- balancing current for that cell?

LMX2594: Doesn't lock at VCO boundaries at cold temperatures

$
0
0

Part Number: LMX2594

Hello,

I am using the LMX2594 and I'm having an issue where the LO will not lock when it is tuning near the boundary of VCO 4 and 5 (11950 MHz to 12000 MHz) and also the boundary between VCO 6 and 7 (13900 to 13950 MHz) when the temperature is low (-10 C or below).  One unit is having the issue at both boundaries and the other is only having the issue between 6 and 7.  On the unit that is only having a problem between boundary 6 and 7 the LO will unlock at 13950 MHz if the previous LO frequency used VCO 7.  If the last frequency used VCO 6 13950 MHz will lock.  It doesn't seem to matter what I make VCO_SEL, VCO_DACISET_STRT, or VCO_CAPCTRL_STRT.  The behavior is the same.  All of the FORCE parameters are set to 0.  I don't have any information from the first unit yet, I wanted to see if it was an isolated issue or a systemic problem so I tested the second one without doing any debug.

Thanks for your help.

CDCLVD2102: Static input

$
0
0

Part Number: CDCLVD2102

Is there any input condition that would cause the LVDS output to rail to 2.5Volts? (i.e. single static input)

DS90UB947-Q1: Register 0x54 setting having effect on back-channel GPIO0 with DS90UB947-Q1 and DS90UB948-Q1

$
0
0

Part Number: DS90UB947-Q1

My customer has been having issues with the DS90UB947-Q1 inability to pass GPIOs on the back channel; particularly GPIO0.  They claim the solution was to set Reg 0x54 of the 947 from its boot up value of 0x3 to 0x0.  They also said Reg 0x54 description table implies we would only have to clear bit 1, but in actuality we have to clear [1:0].  This is different than what the datasheet describes.  Can you please clarify this register table (especially "Reserved" bit 0), and how it is affects back-channel operation for GPIO0?  

Something they noticed in the beginning was register 0x28 of the DS90UB948-Q1 partner device.  The 948 register 0x28 was reading back 0x18, and this seems to indicate GPIO0 and GPIO1 are configured as alternative I2S output mode.  After writing 947 register 0x54 to 0x0, 948 register 0x28 was reading back 0x11 which means GPIO0 and GPIO1 are configured as normal operation.  Would 948 register 0x28[bit 7] = 0 explain how 947 register 0x54 affects GPIO0 and GPIO1 (since bit 7 enables forward channel control of 948 register 0x28)?

Regards,
Alan


PCA9515B: VOL – VILC

$
0
0

Part Number: PCA9515B

Hi E2E,

Good day!

On section 8.1 page 8 of the datasheet, it is stated that "the input voltage of each internal buffer must be 70 mV or more below the low level output when the output is driven low internally". However, on the Table 6.5 page 5, it is indicated that Low-level input voltage below low-level output voltage is typically 120mV.

May I know what is the difference between the two?

Thank you for your usual support.

Best regards,

Franz

TPS3620-33-EP: Vout switching time

$
0
0

Part Number: TPS3620-33-EP

Hello,

Can you provide any information on how long TPS3620-33-EP takes to switch from VBAT to VDD once the requirements are met? The requirements are VDD > VBAT or VDD > VIT. The datasheet makes it look like switching VOUT back to VDD happens instantaneously, but I'm sure some delay exists. I'm using the TPS3620-33-EP to provide backup battery power to an IC, and I'm concerned that if it take too long to switch VOUT from VBAT to VDD, my IC could see 3.3V on its inputs while still running on battery power (~2.5V).

Thanks

PAL16L8A-2M: PAL16L8A-2M life cycle information

$
0
0

Part Number: PAL16L8A-2M

Hi,

Would you please provide some information about the life cycle of the  PAL16L8A-2M. Looks like this part is old. We want to make sure it is not going to be obsolete so quick.

Thanks.

CCS/MSP432P401R: Can't get interrupt on P1.6.

$
0
0

Part Number: MSP432P401R

Tool/software: Code Composer Studio

Hello TI community

I am using MSP432P401R as my processor. I need an interrupt on P1.6. I have configured the registers for this as follows:

 

/**************GPIO2 Interrupt is enabled on P1.6 high>>low transition**********************/


P1REN |= BIT6;                     //Pullp/pulldown resistor is activated.
P1OUT &= ~BIT6;                 //The default of the P1.6 is low.
P1DIR &= ~BIT6;                  //P1.6 is defined as input pin.
P1IE |= BIT6;                        // The interrupt is activated for P1.6.
P1IES |= BIT6;                     // The interrupt is activated on high to low transition.
P1IFG &= ~BIT6;                 // P1.6 IFG cleared

     __enable_irq();

/***************************************************************************************************/

Also in the ISR, I have written as follows:

/*Port 1 Interrupt handler/
void PORT1_IRQHandler(void)
{
[My code]

P1IFG &=~ BIT6;
}

/**************************************************/

The problem I have here is that I don't get the interrupt (The program doesn't go to interrupt service routine). I have checked my code in another MCU (MSP430G2553) and it works fine.

Do you have any idea where the problem come from?

Thanks

Saber

IWR1642BOOST: Traffic Monitoring Demo

$
0
0

Part Number: IWR1642BOOST

Hello, 

I've recorded data using the Traffic Monitoring Demo. However I'd like to know if the timestamp given by the fHist files can be used as actual datetime for the pointclouds or if its merely for device synchronization.

Another question I have, is if there's a way easier than running the Playback.m file for the recorded data (which for a whole day of data, sometimes gives errors), if I could from the fHist files easily track the number of cars in one of my lanes (my example I used 3 lanes, one on the left for cars exiting the location, one on the middle where no cars passed, and one on the right for cars entering).

Thank you for your time

DRA718: DRA718 problem

$
0
0

Part Number: DRA718

hi  Team:

1. in the datasheet:  On page 161  , How to understand"could ramp up concurrently with VDDA_PLL group only if the vdda33v_usb1 power resource has an “off impedance” greater than 100Ω."?

2. I want to use TPS65919 PMIC for DRA718,Can you provide reference circuit diagram?

3.  in the datasheet:     5.10.3 Power Supply Sequences  ,Inconsistent with the following description, which is correct?

PAL16L8A-2M: Package size

$
0
0

Part Number: PAL16L8A-2M

Hello,

On the datasheet, the length of the part is maximum B=1.060. I wanted to know what is the tolerance on this dimension as it is only the maximum value.

Thanks.


SN74LVC2T45-Q1: Is this device AEC rated?

$
0
0

Part Number: SN74LVC2T45-Q1

Hello,

Can someone from TI confirm if P/N SN74LVC2T45-Q1 is rated to AEC-Q100 standards? The datasheet says it's rated for automotive applications, but it doesn't explicitly state anywhere if it's rated to any AEC specification.

Thanks!

DP83869HM: RJ45 matrix

$
0
0

Part Number: DP83869HM

hi  Team:

if I want to designed a RJ45  matrix(2*2 or  12*12),Is there a  solution RJ45 matrix switching circuit for me?

HDC2080: Variation in baseline readings

$
0
0

Part Number: HDC2080

Hi,

I have a customer using a HDC2080 and HDC2010 evms and there is about 5-6% difference in the 2010 evm and 2080 evm in the baseline reading. This is the baseline reading obtained when the units were placed on a desk after power-up and a stabilization period of a few minutes. 

How much variation is expected in the baseline readings between the different sensors? Is there anything the customer should look out for that can cause this variation?

Thanks,

Ishraq

BQ24195: Current is not limited

$
0
0

Part Number: BQ24195

We are making portable chargers based on BQ24195. According to the manual, the charging current is limited to the LOWER of two: value in register 0 and the resistor on ILIM pin. I more or less copied the reference design. The resistor between  ILIM pin and ground is 330 Ohm that is supposed to limit the current to 1.5 A.  The default value in the low 3 bits of the register 0 is 0b101 - also 1.5 A limit. Yet when I plug in a lab power supply, it initially takes way over 2 A triggering the current limiter on the supply.  Now if I set reg.0 to 0x34 - limit 1.2A, then everything appears to be much better.

So two questions:

1. why does the 330 Ohm resistor in ILIM not limiting the current to 1.5 A?

2. why 1.2 A limit wirks and 1.5 A fails?

Thanks.

tpa3118d2

$
0
0

dear TI

      (Please visit the site to view this file)Hello, I am in accordance with the monophonic schematic of the specification. Why is there only no vocal sound in the test? Is there a problem?

Viewing all 262198 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>