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

3D darktime signal format

$
0
0

Hi Everybody,

I have a question. What is the TTL signal structure of 3D darktime SYNC for DCI Projectors ?

3D signal out is ?? Hz Square wave (%50 duty cycle) but I can not find darktime signal format. Could you help me about darktime signal format ?

Thanks ..

Mastercodex

 


HDC2080: High power consumption when voltage higher than 2.7v

$
0
0

Part Number: HDC2080

HI E2E,

I have a problem with the new hds2080 chips. When powered by a 3-volt voltage, the chip consumption is too high and does not match the datasheet. I take measurements using the Nordic power profiler. I attached two images with measurements at different supply voltages

Voltage 1.8v -  power consumption 3uA. All good.

Voltage 2.8v - 19uA .... It is very high

ISO1211: Problem with the comum ground

$
0
0

Part Number: ISO1211

Hello Team!

I'm developing a board, then I need to "convert" 24V input to 3.3V output. But, I saw in the datasheet the common ground, but when I was testing this didnt work, so I tested connect the FGROUND to the ground of 24V and 3.3V to GROUND.

Im testing this with two power supplies, do I really have to separate the grounds?

My english is a little bit rusty, so I appreciate your help!

TMS320F280049: run time support lib

$
0
0

Part Number: TMS320F280049

Dear C2000 expert,

From F28004x Firmware Development Package User's Guilde, It mentioned that the run time support library should be rts2800_fpu32.lib instead of libc.a, but the example project, launchxl_ex1_f280049c_demo, is still using libc.a, can you please help me know what differences are between those 2 libs? Which lib should be used?

BQ20Z655-R1: Chg mosfet doesn't turns on at learning cycle

$
0
0

Part Number: BQ20Z655-R1

Hi,

I created my gg file. Update status is 02 at first data.

Then I started to the learning cycle. After discharge battery with C/5 I let it relax mode for 5 hour. Update status is 06now. But I cant charge it now. Chg fet is turned off.I tried 21 and 41 but it doesn't work. I can discharge it but it cant be charged. I need quick help !!

Thanks.

IWR6843AOPEVM: mmWave Demo Visualizer can't connect to data port

$
0
0

Part Number: IWR6843AOPEVM

When I try to connect to the IWR6843AOPEVM module via mmWave Demo Visualizer, it connects successfully to the CFG_port_Transport but keeps retrying to connect to the DATA_port_Transport (see screen shots below).

So far here are the steps that I've taken:

1. I've successfully uploaded the packages\ti\demo\xwr64xx\mmw\xwr64xxAOP_mmw_demo.bin image onto the IWR6843AOPEVM module.

2. Switched SOP2 to OFF position (SOP0, SOP1 are also off)

3. In CHROME go to  mmWave Visualizer https://dev.ti.com/gallery/view/mmwave/mmWave_Demo_Visualizer_IWR6843AOP/ver/1.0.0/

4. Select ports as below screen shot.

5. The CFG port is successfully connected but the data port doesn't (see image below). The status at the bottom of the screen says "waiting for data" for that port. 

Please help.

Compiler: changing to previous mode

$
0
0

Tool/software: TI C/C++ Compiler

Hello,

i am attaching figure in which i have two modes 1. SPWM(d) and other is SPWMPOS(). before step change(point TO) SPWM(d) is running and after  step change (To) immediately i am using SPWMPOS() mode. I have calculated the time for SPWMPOS() after this time SPWMPOS() switches off and again first mode SPWM(d) mode will start . 2nd mode occurs once when there is step change.In my code i used delay function to realise step change for GPIO3. i am writting my code please have a look and guide me how can i realize this changing modes. SPWM(d) is closed loop in which CMP is calculated from dual loop PI duty cycle and running in UPDOWN mode and its TBPRD is 1000 . SPWMPOS is open loop CMP is know and its running in UP count mode and its TBPRD is 11800.EALLOW;

GpioCtrlRegs.GPAPUD.bit.GPIO3 = 0;
GpioCtrlRegs.GPAMUX1.bit.GPIO3 = 0;
GpioCtrlRegs.GPADIR.bit.GPIO3 = 1;

EDIS;

GpioDataRegs.GPACLEAR.bit.GPIO3 = 1;

SPWM(d);  // mode is running

DELAY_US(3333333);    //  step change 

GpioDataRegs.GPASET.bit.GPIO3 = 1;

 SPWMPOS();                     // after step change second mode is running for calculated time 

// How to change back to moade 1. SPWM(d)   

????

//PWM1

void InitEPwm1Example()
{

EPwm1Regs.TBPRD = PERIOD ; // Set timer period
EPwm1Regs.TBPHS.bit.TBPHS = 0x0000; // Phase is 0
EPwm1Regs.TBCTR = 0x0000; // Clear counter

//
// Setup counter mode
//
EPwm1Regs.TBCTL.bit.CTRMODE = TB_COUNT_UPDOWN;
EPwm1Regs.TBCTL.bit.PHSEN = TB_DISABLE; // Disable phase loading
EPwm1Regs.TBCTL.bit.HSPCLKDIV = TB_DIV1; // Clock ratio to SYSCLKOUT
EPwm1Regs.TBCTL.bit.CLKDIV = TB_DIV1;
EPwm1Regs.TBCTL.bit.SYNCOSEL = TB_CTR_ZERO; // Sync output is equal to zero

//

//
// Setup compare
//
EPwm1Regs.CMPA.bit.CMPA = 0; //
// EPwm1Regs.CMPB.bit.CMPB = 0;
//
// Set actions

EPwm1Regs.AQCTLA.bit.CAU = AQ_CLEAR; // EPW1A
EPwm1Regs.AQCTLA.bit.CAD = AQ_SET; // EPW1A

EPwm1Regs.AQCTLB.bit.CAU = AQ_SET; // EPW1B
EPwm1Regs.AQCTLB.bit.CAD = AQ_CLEAR; // EPW1B


// Setup shadowing
//
EPwm1Regs.CMPCTL.bit.SHDWAMODE = CC_SHADOW;
EPwm1Regs.CMPCTL.bit.SHDWBMODE = CC_SHADOW;
EPwm1Regs.CMPCTL.bit.LOADAMODE = CC_CTR_ZERO; // Load on Zero
EPwm1Regs.CMPCTL.bit.LOADBMODE = CC_CTR_ZERO;

EPwm1Regs.ETSEL.bit.INTSEL = ET_CTR_ZERO; // Select INT on Zero event INTSEL= interrupt selection
EPwm1Regs.ETSEL.bit.INTEN = 1; // Enable INT
EPwm1Regs.ETPS.bit.INTPRD = ET_1ST; // Generate INT on 1st event

//Start Conversion of ADC
EPwm1Regs.ETSEL.bit.SOCAEN = 1; // Enable SOC on A group
EPwm1Regs.ETSEL.bit.SOCASEL = 2;
EPwm1Regs.ETPS.bit.SOCAPRD = 1; // Generate pulse on 1st event

//  mode 1 SPWM(d)

void SPWM(float Ea )
{
float CMP;

CMP = PERIOD*((1+Ea)/2);        // CMP is cal
EPwm1Regs.CMPA.bit.CMPA = (Uint16)CMP;

}

// Mode 2 SPWMPOS()

void SPWMPOS()
{
EPwm1Regs.TBPRD = 2000*5.9 ; // Set timer period

EPwm1Regs.TBCTL.bit.CTRMODE = TB_COUNT_UP;
EPwm1Regs.CMPA.bit.CMPA = 10340; //1025 for negative

EPwm1Regs.AQCTLA.bit.ZRO = AQ_SET; // Set PWM1A on Zero
EPwm1Regs.AQCTLA.bit.CAU = AQ_CLEAR; // Clear PWM1A on event A, up count

EPwm1Regs.AQCTLB.bit.ZRO = AQ_SET; // Set PWM1B on Zero
EPwm1Regs.AQCTLB.bit.CAU = AQ_CLEAR; // Clear PWM1B on event B, up count

// Setup shadowing
//
EPwm1Regs.CMPCTL.bit.SHDWAMODE = CC_SHADOW;
EPwm1Regs.CMPCTL.bit.SHDWBMODE = CC_SHADOW;
EPwm1Regs.CMPCTL.bit.LOADAMODE = CC_CTR_PRD; // Load on Zero
EPwm1Regs.CMPCTL.bit.LOADBMODE = CC_CTR_PRD;}

AWR1843BOOST: mmwave studio: Object reference not set to an instance of an object

$
0
0

Part Number: AWR1843BOOST

Hi team,

I am getting the following exception on running the mmwave studio 2.0.0.2 with AWR1843Boost and DCA1000 EVM.

PC we use is Intel NUC with Intel Core i7, 8GB RAM, 256 SSD, and Windows 10 operating system, which meets the requirements in the mmwave studio user’s guide.

We are sure that we have installed 32-bit Matlab Runtime Engine 8.5.1, Microsoft Visual C++ 2013 Redistributable package and FTDI Drivers. And we have tried reinstalling it while DCA1000 board was connected to the PC, but still failed.

We tried to install mmwave studio on several computers. We found that it could work on all old computers, but would fail on PC with newly installed operating system. We have tried different versions of Windows 10 operating system. As long as the system was newly installed, mmwave studio wouldn’t work then, with the error shown in the picture above.

Any help would be appreciated.


AFE4300: afe4300 ADC result

$
0
0

Part Number: AFE4300

Hello,

I used the AFE4300 to design a PCB board. When I used FWR MODE for calibration resistance correction, I found that the value read by the ADC is not as linear as the data sheet. My offset is very large. I have carefully studied the application manual. The ADC example offset on the manual is very small, and it is 1 ohm corresponding to the 13ADC value,For example, consider two reference resistors measured as 698.4 Ω at Rx, and 949.1 Ω at Ry. Injecting a 64-kHz frequency current and setting the data rate of the ADC to 64 SPS, the ADC codes are 9074 and 12331. So the slope of Equation 1 is (949.1 – 698.4) / (12331 – 9074) = 0.07697 and the offset is 698.4 – (0.07697 × 9074) = –0.026, is this fixed? For 100 ohms, the value I read is 970 (hexadecimal representation) 1K corresponds to 2fb3 (hexadecimal representation).And the slope:0.091313 offset:-117.499344.This is too different from the Body Impedance to Output Voltage Transfer Curve in the data sheet. I don't know if my reading is wrong. If it is wrong, what is the reason?

thank you for your time.

INA240: what is the accuracy of the internal 50k ohm resistor?

$
0
0

Part Number: INA240

Customer is asking for the accuracy of the internal 50k ohm resistor for REF1 and REF2? Could you help address it? Thank you.

CCS/LAUNCHXL-F28379D: why write "asm(" ESTOP0");" in ADC conversion ?

$
0
0

Part Number: LAUNCHXL-F28379D

Tool/software: Code Composer Studio

Hello all,

In below software there was a command " asm("   ESTOP0"); " . But I don't know why write it. When remove " asm("   ESTOP0"); " the AdcaResultRegs.ADCRESULT0 ( and AdcaResultRegs.ADCRESULT1; and  AdcbResultRegs.ADCRESULT0;  and AdcbResultRegs.ADCRESULT1;) not change.(don't sampling)

Now I have a question.

1 - Why write " asm("   ESTOP0"); "  ? ( in line number 185 )

2 - When remove " asm("   ESTOP0"); "  . Why sampling not happen ? ( and what I do to sampling without writing " asm("   ESTOP0"); " ?)

Thank you for helping.

//###########################################################################
//
// FILE:   adc_soc_software_cpu01.c
//
// TITLE:  ADC software triggering for F2837xD.
//
//! \addtogroup cpu01_example_list
//! <h1> ADC SOC Software Force (adc_soc_software)</h1>
//!
//! This example converts some voltages on ADCA and ADCB  based on a software
//! trigger.
//!
//! After the program runs, the memory will contain:
//!
//! - \b AdcaResult0 \b: a digital representation of the voltage on pin A2\n
//! - \b AdcaResult1 \b: a digital representation of the voltage on pin A3\n
//! - \b AdcbResult0 \b: a digital representation of the voltage on pin B2\n
//! - \b AdcbResult1 \b: a digital representation of the voltage on pin B3\n
//!
//! Note: The software triggers for the two ADCs happen sequentially, so the
//! two ADCs will run asynchronously.
//!
//
//###########################################################################
// $TI Release: F2837xD Support Library v3.06.00.00 $
// $Release Date: Mon May 27 06:48:24 CDT 2019 $
// $Copyright:
// Copyright (C) 2013-2019 Texas Instruments Incorporated - http://www.ti.com/
//
// Redistribution and use in source and binary forms, with or without 
// modification, are permitted provided that the following conditions 
// are met:
// 
//   Redistributions of source code must retain the above copyright 
//   notice, this list of conditions and the following disclaimer.
// 
//   Redistributions in binary form must reproduce the above copyright
//   notice, this list of conditions and the following disclaimer in the 
//   documentation and/or other materials provided with the   
//   distribution.
// 
//   Neither the name of Texas Instruments Incorporated nor the names of
//   its contributors may be used to endorse or promote products derived
//   from this software without specific prior written permission.
// 
// THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 
// "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 
// LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
// A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 
// OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 
// SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 
// LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
// DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
// THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 
// (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 
// OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
// $
//###########################################################################

//
// Included Files
//
#include "F28x_Project.h"

//
// Function Prototypes
//
void ConfigureADC(void);
void SetupADCSoftware(void);

//
// Globals
//
Uint16 AdcaResult0;
Uint16 AdcaResult1;
Uint16 AdcbResult0;
Uint16 AdcbResult1;

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

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

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

//
// Initialize the 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 F2837xD_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 F2837xD_DefaultIsr.c.
// This function is found in F2837xD_PieVect.c.
//
    InitPieVectTable();

//
// Enable global Interrupts and higher priority real-time debug events:
//
    EINT;  // Enable Global interrupt INTM
    ERTM;  // Enable Global realtime interrupt DBGM

//
//Configure the ADCs and power them up
//
    ConfigureADC();

//
//Setup the ADCs for software conversions
//
    SetupADCSoftware();

//
//take conversions indefinitely in loop
//
    do
    {
        //
        //convert, wait for completion, and store results
        //start conversions immediately via software, ADCA
        //
        AdcaRegs.ADCSOCFRC1.all = 0x0003; //SOC0 and SOC1

        //
        //start conversions immediately via software, ADCB
        //
        AdcbRegs.ADCSOCFRC1.all = 0x0003; //SOC0 and SOC1

        //
        //wait for ADCA to complete, then acknowledge flag
        //
        while(AdcaRegs.ADCINTFLG.bit.ADCINT1 == 0);
        AdcaRegs.ADCINTFLGCLR.bit.ADCINT1 = 1;

        //
        //wait for ADCB to complete, then acknowledge flag
        //
        while(AdcbRegs.ADCINTFLG.bit.ADCINT1 == 0);
        AdcbRegs.ADCINTFLGCLR.bit.ADCINT1 = 1;

        //
        //store results
        //
        AdcaResult0 = AdcaResultRegs.ADCRESULT0;
        AdcaResult1 = AdcaResultRegs.ADCRESULT1;
        AdcbResult0 = AdcbResultRegs.ADCRESULT0;
        AdcbResult1 = AdcbResultRegs.ADCRESULT1;

        //
        //at this point, conversion results are stored in
        //AdcaResult0, AdcaResult1, AdcbResult0, and AdcbResult1
        //

        //
        //software breakpoint, hit run again to get updated conversions
        //
        asm("   ESTOP0");

    }while(1);
}

//
// ConfigureADC - Write ADC configurations and power up the ADC for both
//                ADC A and ADC B
//
void ConfigureADC(void)
{
    EALLOW;

    //
    //write configurations
    //
    AdcaRegs.ADCCTL2.bit.PRESCALE = 6; //set ADCCLK divider to /4
    AdcbRegs.ADCCTL2.bit.PRESCALE = 6; //set ADCCLK divider to /4
    AdcSetMode(ADC_ADCA, ADC_RESOLUTION_12BIT, ADC_SIGNALMODE_SINGLE);
    AdcSetMode(ADC_ADCB, ADC_RESOLUTION_12BIT, ADC_SIGNALMODE_SINGLE);

    //
    //Set pulse positions to late
    //
    AdcaRegs.ADCCTL1.bit.INTPULSEPOS = 1;
    AdcbRegs.ADCCTL1.bit.INTPULSEPOS = 1;

    //
    //power up the ADCs
    //
    AdcaRegs.ADCCTL1.bit.ADCPWDNZ = 1;
    AdcbRegs.ADCCTL1.bit.ADCPWDNZ = 1;

    //
    //delay for 1ms to allow ADC time to power up
    //
    DELAY_US(1000);

    EDIS;
}

//
// SetupADCSoftware - Setup ADC channels and acquisition window
//
void SetupADCSoftware(void)
{
    Uint16 acqps;

    //
    // Determine minimum acquisition window (in SYSCLKS) based on resolution
    //
    if(ADC_RESOLUTION_12BIT == AdcaRegs.ADCCTL2.bit.RESOLUTION)
    {
        acqps = 14; //75ns
    }
    else //resolution is 16-bit
    {
        acqps = 63; //320ns
    }

    //
    //Select the channels to convert and end of conversion flag
    //ADCA
    //
    EALLOW;
    AdcaRegs.ADCSOC0CTL.bit.CHSEL = 2;  //SOC0 will convert pin A2
    AdcaRegs.ADCSOC0CTL.bit.ACQPS = acqps; //sample window is acqps +
                                           //1 SYSCLK cycles
    AdcaRegs.ADCSOC1CTL.bit.CHSEL = 3;  //SOC1 will convert pin A3
    AdcaRegs.ADCSOC1CTL.bit.ACQPS = acqps; //sample window is acqps +
                                           //1 SYSCLK cycles
    AdcaRegs.ADCINTSEL1N2.bit.INT1SEL = 1; //end of SOC1 will set INT1 flag
    AdcaRegs.ADCINTSEL1N2.bit.INT1E = 1;   //enable INT1 flag
    AdcaRegs.ADCINTFLGCLR.bit.ADCINT1 = 1; //make sure INT1 flag is cleared
    //ADCB
    AdcbRegs.ADCSOC0CTL.bit.CHSEL = 2;  //SOC0 will convert pin B2
    AdcbRegs.ADCSOC0CTL.bit.ACQPS = acqps; //sample window is acqps +
                                           //1 SYSCLK cycles
    AdcbRegs.ADCSOC1CTL.bit.CHSEL = 3;  //SOC1 will convert pin B3
    AdcbRegs.ADCSOC1CTL.bit.ACQPS = acqps; //sample window is acqps +
                                           //1 SYSCLK cycles
    AdcbRegs.ADCINTSEL1N2.bit.INT1SEL = 1; //end of SOC1 will set INT1 flag
    AdcbRegs.ADCINTSEL1N2.bit.INT1E = 1;   //enable INT1 flag
    AdcbRegs.ADCINTFLGCLR.bit.ADCINT1 = 1; //make sure INT1 flag is cleared
    EDIS;
}

//
// End of file
//

TMS320C6652: TMS320C6652:Unused clocks/IOs

$
0
0

Part Number: TMS320C6652

Hi,

In TMS320C6652CZHA6 I need clarifications on the below

1. MCIMCLKP / N

 I am not using MCIM in the design. These pins are mentioned are reserved in datasheet.Can these pins be left floating.

2.GPIO pins

Should we add pullup/pull down on GPIO input pins? I understand from datasheet GPIO outputs doesnot require pullup/down.

Also series termination to be used on GPIO outputs. Please confirm.

3. MDCLK

MDC is not used in the design. Can this pin be left floating?

Thanks,

Divy

UCC21750-Q1: Global Shutdown of multiple devices

$
0
0

Part Number: UCC21750-Q1

Hi 

I'm looking into changing our currently used ISO5452 with the UCC21750

Any things that must be considered for this change? 

Wrt. the driving of the UCC21750, we are interested in the Global Shutdown with Inverting input as done for the ISO5452, is this still achievable with the UCC21750?

Thanks

Hermann

CCS/CC1352R: How to synchronize one of GPTs with RTC

$
0
0

Part Number: CC1352R

Tool/software: Code Composer Studio

Hello
 
I use CC13X2 along with TI-RTOS.
I’m trying to properly synchronize one of the GPTs to RTC.
I already know that RAT is nicely synchronized to RTC, unfortunately RAT is active only if the whole RF domain is active (powered on).
 
Currently, my approach to synchronize GPT with RTC is as follows:
- GPT handle is always open (GPTimerCC26XX_open)
- GPT starts (GPTimerCC26XX_start) within this callback:
var Timer = xdc.module('ti.sysbios.family.arm.cc26xx.Timer');
Timer.funcHookCH1 = "&Scheduler_rtcAlarmHandler";
- RTC is scheduled using channel 1 and compare value,
AONRTCCompareValueSet(AON_RTC_CH1, (relTime >> 4) & 0xFFFFFFFE);
- custom powerPolicy is used to properly counts ticks till the next interrupt.

This approach works fine but it introduces unwanted overhead and jitter.

Questions.
 
1) Is there any way to automatically synchronize GPT to RTC (I mean a more “hardware-based” approach)?

2) What is the best way to synchronize GPT to RTC?

/Adam

MSP430F5438A: Max deviation of RTC component in the MSP430 MCUs

$
0
0

Part Number: MSP430F5438A

Hi

I considering using one of these MSP MCUs

MSP430F5438A    or

MSP430FR5994

As I saw these MCU has ultra low energy consumption and also has a RTC build-in component.

How can I know the max deviation of the RTC ?

The app will work in open area in temperature of (-10) to 60 Celsius degrees.  I need it will have deviation of not more than 2 hours per ten years.

Were can I find this information? Didn't see any mention at the product datasheet description section.

Thanks


BQ76940EVM: Reduced Cell Count BQ76940

$
0
0

Part Number: BQ76940EVM

Hi experts,

I understand the requirements for reduced cell count usage with BQ76940 IC. My question is is that apart from shortening the cells, is it mandatory to desolder the parts where there are no cells present? Because later on i want to use the full cell count and I have to resolder it again. 

My other question is that, the reduction is set by the table 26 in the datasheet. Further reduction is not possible ? For example in the case of 15 cell IC the reduction is maximum to 9 cells. It this number can be further reduced or this is the maximum reduction?

Thanks,

Andras

CC2640R2F: oad question

$
0
0

Part Number: CC2640R2F

I am working on my project based on sdk 1.40, oad sample project.

I made it work, for example, I name it version 1.0,  then I modify some code, name it version 2.0.

if I program 1.0 hex, and oad 1.0 bin, it is ok.

program 2.0 hex, and oad 2.0 bin, ok.

but,   1.0 hex, oad 2.0 bin,   not work, no adv and no helloworld I print.

2.0 hex oad to 1.0 bin, the same issue.

is there anything important I missed?

TMUX1111: Low current power rail switching

$
0
0

Part Number: TMUX1111

Dear TI-Team,

we're looking for a switch/mux to select 1 of 4 3.6V (max) input rails. The average cont. current will be below 2mA and it is a battery-powered application. Thus, we need a low-drop, low Iq solution.

I came across TMUX1111 which looks goods but it seems to be marketed as a signal switch, not a load switch. Will it fit our application? What about cross conduction?

An alternate which states "Power Routing" in its d/s could be TS3A4751 but it has a max of 3.6V and I don't know if it's okay to hit the max 90% of time

Please advise, I'm also open for alternative parts 

DAC38RF82: JESD204B configuration

$
0
0

Part Number: DAC38RF82

hello,

We have a one JESD204B master implemented on a Xilinx FPGA (ULTRASCALE device).

In the FPGA configuration M=2, L=8 (LMFS).

Eight serdes lanes are connected to the DAC38RF82.

We have a 16bit/2.5Gbps mode in which four lanes are connected to DAC A in the DAC38RF82 and four lanes are connected to DAC B (ONE_DAC_ONLY=0, ONE_LINK_ONLY=1).

The physical connections are as follows:

FPGA                     DAC38RF82

TX0                        RX1

TX1                        RX4

TX2                        RX6

TX3                        RX7

TX4                        RX5

TX5                        RX0

TX6                        RX2

TX7                        RX3

 Polarity should be inverted (in the DAC) for TX0, TX2, TX5, TX7.

The JESD mode we use for the 16bit/2.5Gsps is LMFSHd=82121.

In the FPGA, TX0 uses lane ID=0, TX1 uses lane ID=1 and so on for the rest of the TXn.

FPGA TX0-TX3 are routed to DAC A of the device (via the cross-bar, lane enable, etc.).

FPGA TX4-TX7 are routed to DAC B of the device.

 

My questions:

  1. Using Table 9, JESD204B Formats for DAC38RF82 and DAC38RF89 (p. 30 in the datasheet):
    We use the mode in last table entry (41121 / 82121).
    It seems the mode we require is 2 TX, 82121.
    What is the difference between 1 TX and 2 TX? (we use ONE_DAC_ONLY=0, ONE_LINK_ONLY=1).
  2. Using Table 41, Register Programming for JESD and Interpolation Mode (p. 52 in the datasheet):
    Which mode is the correct one for us: 82121/NA or 41121/82121 ?
  3. Giving the above information, can you fill the enclosed (from DAC38RFxx EVM GUI):
    (or supply with the relevant registers settings)

Thank you !

Gil Hershman

TDA2PXEVM: How does the TDA2PX board capture the lvds data from ub933 on TDA2HG board

$
0
0

Part Number: TDA2PXEVM

Hello,

We need to capture lvds data from TDA2HG board to TDA2PX board based on VSDK 03 05, and then output the data from HDMI on TDA2PX. How do we do?

ps: DS90UB933-Q1 as output on TDA2HG board, and DS90UB964-Q1 as input on TDA2PX board.

Thanks

Terence

Viewing all 262198 articles
Browse latest View live


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