The datasheet says “An internal Power-On Reset circuit keeps the outputs in a high-impedance state until the supply voltage has reached a level at which the device will reliably operate”. But I can’t find anywhere that the threshold voltage is specified.

Can you help?

Thanks

Viktorija

↧

LM61460-Q1: PLM61460AASQRJRTQ1

August 30, 2019, 10:34 am

≫ Next: CCS/MMWAVEICBOOST: Software Reset

≪ Previous: SN65HVD3086E: threshold voltage

Part Number: LM61460-Q1

Im looking for the land pattern PCB footprint for LM61460-Q1 - package VQFN-HR (14)

↧

CCS/MMWAVEICBOOST: Software Reset

August 30, 2019, 10:34 am

≫ Next: TPS43060: max power/current

≪ Previous: LM61460-Q1: PLM61460AASQRJRTQ1

Part Number: MMWAVEICBOOST

Tool/software: Code Composer Studio

Hi,

I'm working on IWR6843-ISK along with MMWAVEICBOOST. I want to add a system reset function which has the same ability as pressing NRST SW2 on MMWAVEICBOOST to my project but I can't find where the document or datasheet is. Could you tell me where I can download it? I already downloaded mmwave toolbox 3.6.

Another question I have is that when I used CLI to configure chirp parameter which came from mmwave toolbox demo, it worked perfectly fine. However, after I typed "sensorStop", I gave exactly same chirp parameter as previous step. It shows "Error -1" response on "adcbufCfg 0 1 1 1" command. The only way I found to resolve this issue is to reset the board by pressing NRST SW2. Below is the configuration I used on CLI. Am I missing some commands to stop the sensor?

First given parameter

flushCfg
dfeDataOutputMode 1
channelCfg 15 5 0
adcCfg 2 1
adcbufCfg 0 1 1 1
profileCfg 0 60.6 30 10 62 0 0 53 1 128 2500 0 0 30
chirpCfg 0 0 0 0 0 0 0 1
chirpCfg 1 1 0 0 0 0 0 4
frameCfg 0 1 128 0 50 1 0
lowPower 0 1
guiMonitor 1 1 0 0
cfarCfg 6 4 4 4 4 16 16 4 4 55 67 0
doaCfg 600 1875 30 1 1 0
SceneryParam -6 6 0.5 6
GatingParam 3 2 2 0
StateParam 10 5 100 100 5
AllocationParam 250 250 0.25 30 1 2
trackingCfg 1 2 250 20 52 82 50 90
sensorStart

Second given parameter

sensorStop
flushCfg
dfeDataOutputMode 1
channelCfg 15 5 0
adcCfg 2 1
adcbufCfg 0 1 1 1
profileCfg 0 60.6 30 10 62 0 0 53 1 128 2500 0 0 30
chirpCfg 0 0 0 0 0 0 0 1
chirpCfg 1 1 0 0 0 0 0 4
frameCfg 0 1 128 0 50 1 0
lowPower 0 1
guiMonitor 1 1 0 0
cfarCfg 6 4 4 4 4 16 16 4 4 55 67 0
doaCfg 600 1875 30 1 1 0
SceneryParam -6 6 0.5 6
GatingParam 3 2 2 0
StateParam 10 5 100 100 5
AllocationParam 250 250 0.25 30 1 2
trackingCfg 1 2 250 20 52 82 50 90
sensorStart

↧

TPS43060: max power/current

August 30, 2019, 10:42 am

≫ Next: TLC59284: PWM Dimming

≪ Previous: CCS/MMWAVEICBOOST: Software Reset

Part Number: TPS43060

Team,

Accoring to the parametric search on TI.com TPS43060 is a good option for

12V Vin

48V Vout @ 20A

Is that true?

TPS43060

↧

TLC59284: PWM Dimming

August 30, 2019, 10:44 am

≫ Next: BQ20Z45-R1: Request for bqEVSW download link

≪ Previous: TPS43060: max power/current

Part Number: TLC59284

Hello Team,

I'm working with an engineer that had an interesting question on how to dim their 16-segment LED with the TLC59284 without using external circuitry.

While the current is typically set by using an external resistor on the IREF pin, is it acceptable to use a PWM signal to the BLANK Pin to dim the LED's?

The engineer noted that this works with a 2kHz PWM signal, however, we wanted to confirm if this is okay and if there are any negative implications?

Thanks,

Javier

↧

BQ20Z45-R1: Request for bqEVSW download link

August 30, 2019, 10:46 am

≫ Next: DAC34H84EVM: DAC34H84EVM

≪ Previous: TLC59284: PWM Dimming

Part Number: BQ20Z45-R1

Hi,

I need BQ Evaluation Software (bqEVSW) for bq20Z45-R1 gas gage. Could you please provide a download link?

Thanks,

↧

DAC34H84EVM: DAC34H84EVM

August 30, 2019, 11:03 am

≫ Next: TMS320F280049C: Motorware

≪ Previous: BQ20Z45-R1: Request for bqEVSW download link

Part Number: DAC34H84EVM

Hi, Jim,

We have vc707 xilinx vertex7 based reference boards, we plan to use these boards as TSW1400 to drive DAC34H84EVB, does HSDC pro software have firmware to support this combination?

↧

TMS320F280049C: Motorware

August 30, 2019, 11:25 am

≫ Next: SN74ABT16244A: Vol chart for different loads

≪ Previous: DAC34H84EVM: DAC34H84EVM

Part Number: TMS320F280049C

Hi,

Does Motorware include the TMS320F280049C processor? Also, would it be possible to make PWM frequency reach near 100 KHz with this processor?

Thank you.

↧

SN74ABT16244A: Vol chart for different loads

August 30, 2019, 11:25 am

≫ Next: LAUNCHXL-CC2640R2: Hang in Hwi_excHandler

≪ Previous: TMS320F280049C: Motorware

Part Number: SN74ABT16244A

Hi E2E,

Good day.

Our customer is looking for a chart which shows the Vol at different load test condition. Also, is the SN74ABT16244A be suitable for an application with Vol of <0.4V with 10-12mA load?

Thank you in advance for your help.

Regards,

Carlo

↧

LAUNCHXL-CC2640R2: Hang in Hwi_excHandler

August 30, 2019, 11:31 am

≫ Next: TLV1702-Q1: Window Comparator Output is High When GND Disconnected

≪ Previous: SN74ABT16244A: Vol chart for different loads

Part Number: LAUNCHXL-CC2640R2

I am running a modified version of the simple serial socket server example application, ported to the SDK version 3_20_00_21. The software runs correctly sending data to a PC application for a couple hours, but the application hangs after some period of time.

After loading the ROM symbols, the debugger indicates the program is spinning at the null check in Hwi_excHandler.

Void Hwi_excHandler(UInt *excStack, UInt lr)
{
Hwi_module->excActive[0] = TRUE;

/* spin here if no exception handler is plugged */
while (Hwi_excHandlerFunc == NULL) {
;
}

Hwi_excHandlerFunc(excStack, lr);
}

The callstack indicates the Queue_remove function was interrupted by the hwi.

The stack fill patterns indicate that none of the stacks are close to overflowing, including CSTACK, gapRole task , SSSS Task, and ICall task stacks. Additonally, checks were added to ICall_Malloc and ICall_Free to verify memory being freed or allocated was within the heap.

Is there anything in the OS configuration or operation that could cause this behavior? Can you provide any guidance on where to look for the cause of this issue?

↧

TLV1702-Q1: Window Comparator Output is High When GND Disconnected

August 30, 2019, 11:32 am

≫ Next: CD54HC4351: Maximum current in addressable latches

≪ Previous: LAUNCHXL-CC2640R2: Hang in Hwi_excHandler

Part Number: TLV1702-Q1

The Above Circuit is Designed to satisfy below requirement:

1. HIGH FOUT When LED Is Normal

2. LOW FOUT When LED is Fail Open

3. LOW FOUT When LED is Fail Short

4. LOW FOUT When VCC is Disconnected

5. LOW FOUT When GND is Disconnected.

High Signal Corresponds to 10V or Higher, Low Signal Corresponds to less than 5V

The above Circuit is able to satisfy all the 1-4 Requirements.However, when the Ground is disconnected, it is reading High 12V Signal.

What Changes are required to make it LOW when GND is disconnected.

↧

CD54HC4351: Maximum current in addressable latches

August 30, 2019, 11:42 am

≫ Next: LAUNCHXL-CC2640R2: Trouble debugging example app

≪ Previous: TLV1702-Q1: Window Comparator Output is High When GND Disconnected

Part Number: CD54HC4351

In active state, how much current can an addressable latch serve?

1. Per active pin

2. Maximum output across all pins together

Note that at any given moment, when the latch operates in the memory mode, there could be more than one active pin, due to a previous operation. In such a case, for the CD74HC4351 should we derive the max current per pin? The data sheet specifies trh maximum DC Switch Diode Current for a few VEE combinations but the question is on how to divide the current when we operate all 8 pins at the same moment.

How do I infer/calculate these quantities from the datasheet? Can anyone help with a few examples kindly?

Thanks in advance,

Rahul

↧

LAUNCHXL-CC2640R2: Trouble debugging example app

August 30, 2019, 11:43 am

≫ Next: DS90LV004: Cold sparing or partial power conditions

≪ Previous: CD54HC4351: Maximum current in addressable latches

Part Number: LAUNCHXL-CC2640R2

Hi Team,

I am having trouble debugging the CC2640R2F LAUNCHPAD eval board.I am able to build and flash code, but whenever I try to run the code in Debug mode it crashes and gets stuck in a while() loop. The example app in question is ble5_host_test_cc2640r2lp_app.

There was little success debugging ble5_project_zero_cc2640r2lp_app, but not the app formally mentioned

Any insight is greatly appreciated.

Best regards,

Alexis

↧

DS90LV004: Cold sparing or partial power conditions

August 30, 2019, 11:46 am

≫ Next: SN65LVDS9638: Is there an RS422 drop in replacement for this part?

≪ Previous: LAUNCHXL-CC2640R2: Trouble debugging example app

Part Number: DS90LV004

We have a setup where there’s a chance this part could be powered off while the FPGA driving it could be powered on. Is there any information on if this will cause the board VCC plane to be powered up in this case? We have the enable lines on jumpers which have no digital control.

↧

SN65LVDS9638: Is there an RS422 drop in replacement for this part?

August 30, 2019, 11:48 am

≫ Next: CCS/TMS320F28377D: how to make int16 vector and floating vector multiplication very fast in 28377D?

≪ Previous: DS90LV004: Cold sparing or partial power conditions

Part Number: SN65LVDS9638

Is there an RS422 drop in replacement for this driver (that will operate over temperature)?

↧

CCS/TMS320F28377D: how to make int16 vector and floating vector multiplication very fast in 28377D?

August 30, 2019, 11:56 am

≫ Next: TMS320C5535: DSPlib mul32() not behaving as expected

≪ Previous: SN65LVDS9638: Is there an RS422 drop in replacement for this part?

Part Number: TMS320F28377D

Tool/software: Code Composer Studio

Dear TI engineer,

I'm using 28377D to my project.

I have a problem now, I get some data from ADC in format Uint16, firstly I need change these data to floating data, then make floating multiplication. I found the format changing take a lot of time. I want to know is there has some TI lib function like mpy_SP_RSxRV_2, but the inputs are uint16 vector and float32 vector?

void mpy_SP_RSxRV_2(float32 *y, const float32 *x,
const float32 c, const Uint16 N)

thanks!

↧

TMS320C5535: DSPlib mul32() not behaving as expected

August 30, 2019, 12:14 pm

≫ Next: TUSB8020B: New PCB design doesn't connect to upstream

≪ Previous: CCS/TMS320F28377D: how to make int16 vector and floating vector multiplication very fast in 28377D?

Part Number: TMS320C5535

I'm developing on a TMS320C5535 using the XDS110 debugger, the C5000 chip support library, and Code Composer version: 9.1.0.00010. I'm having a hard time getting mul32() to work in version 03.00.00.03 of DSPlib. To demonstrate where I'm at here is an example of me using add() of DSPlib:

int main(void)
{
    /////////////* Initializations */////////////
    CSL_Status SYS_status;

    SYS_status = SYS_PLL_LDO_init();
    SYS_status = SYS_EBSR_init();
    SYS_status = SYS_GPIO_init();

#define NX 10
    Uint32 i;
//    LDATA x[NX] = {0};
//    LDATA y[NX] = {0};
//    LDATA z[NX] = {0};
    DATA x[NX] = {0};
    DATA y[NX] = {0};
    DATA z[NX] = {0};

    for (i = 0; i < NX; i++){
        x[i] = i;
        y[i] = i;
    }

    add(x, y, z, NX, 0);
//    mul32(x, y, z, NX);

    /////////////* Infinite Loop */////////////
    while(1){
        i = 0;
    }

}

x and y are both = [0,1,2,3, ... ,9]. As expected, z = [0, 2, 4, 6, ... ,18]. Now I try using mul32():

/////////////* Main Function */////////////
int main(void)
{
    /////////////* Initializations */////////////
    CSL_Status SYS_status;

    SYS_status = SYS_PLL_LDO_init();
    SYS_status = SYS_EBSR_init();
    SYS_status = SYS_GPIO_init();

#define NX 10
    Uint32 i;
    LDATA x[NX] = {0};
    LDATA y[NX] = {0};
    LDATA z[NX] = {0};
//    DATA x[NX] = {0};
//    DATA y[NX] = {0};
//    DATA z[NX] = {0};

    for (i = 0; i < NX; i++){
        x[i] = i;
        y[i] = i;
    }

//    add(x, y, z, NX, 0);
    mul32(x, y, z, NX);

    /////////////* Infinite Loop */////////////
    while(1){
        i = 0;
    }

}

x and y are still both = [0,1,2,3, ... ,9]. However, z is incorrectly = [0,0, .... 0].

SPRU422J mentions that "Input and Output vectors must be 32−bit aligned", but I do now know how to do this or if it's the reason this unexpected behavior is occurring. Any guidance would be greatly appreciated

↧

TUSB8020B: New PCB design doesn't connect to upstream

August 30, 2019, 12:15 pm

≫ Next: CC3120: Question about CC3120 802.11g and n mode

≪ Previous: TMS320C5535: DSPlib mul32() not behaving as expected

Part Number: TUSB8020B

We are developing a new PCB which uses the TUSB8020B 2 port USB 3.0 hub IC to interface to an external USB 3.0 peripheral as well as onboard MCU through a USB to UART connection. The PCB was designed following the example circuits in the datasheet, reference design, and evaluation board. However, when we tested the board, it does not enumerate on the upstream PC when connected. As a result the downstream devices also don't connect. In fact, no USB error of any kind is presented, the PC acts as though nothing is connected.

We performed the following tests to see where a possible problem may lie:
- Used USBTreeView to check for any connection
- Tested multiple PCs and multiple USB ports
- Verified the voltage rails were at the correct values
- Power up reset time (GRSTz > 2V after Vcc=3.3V steady state) was measured to be around 10ms which >3ms recommended
- Crystal oscillator XO correctly outputs a ~24MHz clock signal
- Pin 9 USB_VBUS reads ~0.5V
- Since the TUSB8020 first attempts to load the configuration from EEPROM in I2C mode if pins 2 (SCL/SMBCLK), 3 (SDA/SMBDAT) are pulled high, the pullup resistors R1 and R2 were removed to disable configuration reading
- Downstream port wasn’t receiving power so the enable pin 3 of the power switch was pulled high
- Power management was disabled by removing R19
- Pin 22 was probed and the transition from the in circuit pull-up (HIGH) state to the not SuperSpeed connection flag (LOW) state was observed
- Traces to MSP430 on SCL and SDA were cut
- FTDI chip removed
- SMBUSZ I2C mode resistor R23 was removed (still internally pulled up) to match example in datasheet and reference design

Based on the tests performed, it seems as though the chip is running, and despite our modifications to attempt to alleviate any possible issues, it still refuses to connect to the upstream. In the process of debugging we also looked through responses on the help forum and could not find anything that helped us with our particular issue. We are not sure where to proceed in debugging of the TUSB8020B connectivity issues, so any assistance in getting this design to work would be greatly appreciated. I have attached the schematic of our design for reference.

↧