Part Number: IWR1642BOOST

Dear support

I'm working on IWR1642BOOST along with the SDK user guide (mmwave_sdk_user_guide.pdf). It says:

To experience the mmWave technology offered by TI, you will need to procure the following
Hardware:
mmWave TI EVM
Power supply cable as recommended in TI EVM user guide
PC
Software:
Pre-flashed mmWave Demo running on TI EVM (See instructions in this user guide on how to update the flashed demo)
Chrome browser running on PC
Next, to visualize the data flowing out of TI mmWave devices, follow these steps
1. Connect the EVM to a power outlet via the power cable and to the PC via the included USB cable. EVM should be powered up and connected to PC now.
2. On your PC, browse to dev.ti.com/mmWaveDemoVisualizer in Chrome browser and follow the prompts to install one-time software. [No other software installation is needed at this time]
3. The Visualizer app should detect and connect to your device via COM ports automatically (except for the very first time where users will need to confirm the selection via OptionsSerial Port). Select the right Platform and SDK version and start your evaluation!

I'm done with the procedure 2.(uniflash.png)

But at 3., Demo Visualizer doesn't recognize the sensor (persistent "waiting for data")(visualizer.png)

I confirmed the ports number was correct(port.png)

Please give me some guidance on this.

Regards,

Nagano

hi,

NAND booting on DRA71x issue

Please help how to solve the nand boot issue.

SOC: DRA81x, SDK:ti-processor-sdk-linux-automotive-dra7xx-evm-03_02_00_03 NADN:MT29F1G08ABAEAWP (2048+64bytes) CCS: Code Composer Studio 6.1.2

SYSBOOT[0:15] = 10011100 10010001. [0:3] = 1001. [4:5]=11 

The MLO file can boot from QSPI flash, GP header + MLOfile write to nand flash, it can not boot.

struct Nand_Gp_Header {

 unsigned int size;
 unsigned int code_point;

};

gpheader.size = statbuf.st_size+sizeof(struct Nand_Gp_Header);
gpheader.code_point = 0x40300000;

[ 1.539675] 0x000000000000-0x000003c00000 : "NAND.ROOTFS"
[ 1.578282] 0x000003c00000-0x000007800000 : "NAND.BACK"

flash_erase /dev/mtd0 0 0

nandwrite /dev/mtd0 MLOfile

cold reset, but Soc cannot boot, console do not have any print!!!

So. I use CCS tools to debug it.

On data sheet 33.3.9 , Trace registers have been print, Is there any useful information?

hi,

NAND booting on DRA71x issue

Please help how to solve the nand boot issue.

SOC: DRA81x, SDK:ti-processor-sdk-linux-automotive-dra7xx-evm-03_02_00_03 NADN:MT29F1G08ABAEAWP (2048+64bytes) CCS: Code Composer Studio 6.1.2

SYSBOOT[0:15] = 10011100 10010001. [0:3] = 1001. [4:5]=11 

The MLO file can boot from QSPI flash, GP header + MLOfile write to nand flash, it can not boot.

struct Nand_Gp_Header {

 unsigned int size;
 unsigned int code_point;

};

gpheader.size = statbuf.st_size+sizeof(struct Nand_Gp_Header);
gpheader.code_point = 0x40300000;

[ 1.539675] 0x000000000000-0x000003c00000 : "NAND.ROOTFS"
[ 1.578282] 0x000003c00000-0x000007800000 : "NAND.BACK"

flash_erase /dev/mtd0 0 0

nandwrite /dev/mtd0 MLOfile

cold reset, but Soc cannot boot, console do not have any print!!!

So. I use CCS tools to debug it.

On data sheet 33.3.9 , Trace registers have been print, Is there any useful information?

Part Number: MMWAVE-STUDIO

Hi,experts,

When I came to the sensor configuration tab, I had some related confusion. The complete sensor configuration tab is shown below,

I have read the MmwaveStudio user guide,other relevant official documents and related posts in detail, but I still don’t fully understand it, especially the following parts of this tab，

and

Could you please answer the meaning and relationship of the above parameters and this will be of great help to me, thanks in advance.

Part Number: TPS25982

Dear Team

We already remove the Cdvdt cap, but still have long turn on delay.

It should within 3ms, do you have any comments on it?

BR

Kevin

Part Number: TIDA-01352

Hi, 
Our system will have 64 channels and need TX7332. 
Each TX7332 need 5 supply rails such as: 
1. 1.8V Fixed supply rail 

2. 5.0V Fixed supply rail

3. -5.0V Fixed supply rail

4. 100V Fixed supply rail

5. -100V Fixed supply rail

We intend to design the power board for TX7332 with V_input = 15V.


Q1: Push-Pull transformer 750343547 has V_input = 24V (following datasheet). is it ok if we use V_input for it = 15? 

Q2:  How to choose the value of the resistor and capacitor connected to the Compensation (COMP) pin of LM5030?

Q3: Can we configure the PWM of LM5030 to change the output? 

The below figure with input: 15V and output 100V I had. Any problem if we use this schematic? 

Thanks in advance

Part Number: AM5728

Customer is using Silicon revision 2 BSDL file http://www.ti.com/lit/zip/sprm633 and when loading the file into the Corelis Boundary Scan Tool they get the following error:

They have determined that by commenting out the section below they are able to load the file.

Is that ok to do?  There seems to be some sort of compatibility issue.  Any suggestion?

Part Number: ADS8688

Hi team,

My customer is evaluating ADS8688 performance, they find that if they apply signal to one channel (the yellow one) and left the other channels open. They can measure some noise in the other channels, see green and other waveforms. Do you have some ideas about why we have such a phenomenon? Thanks. 

Part Number: HDC2080

There is a description in the specification that you can read and write to this register, but you cannot read the actual value.

If you read "Table 38. Address 0x0F Measurement Configuration Field Descriptions" in hdc2080.pdf, it will be R / W.

Please check.

Part Number: AM5728

Customer working on thier own custom AM5728 boards.  Software was initialliy developed on the EVM  Difference between the AM572x EVM and custom board is that the custom board has 2 LCD panels connected to different DPI vs. one DPI LCD and one HDMI on the EVM. They are having trouble getting this configured and looking for guidance.

They are able to output to either LCD1 or LCD2, but not both. Custom device tree file looks like this

            lcd0: display {
                status = "okay";

                compatible = "osddisplays,osd070t1718-19ts", "panel-dpi";
                backlight = <&lcd_bl>;
                enable-gpios = <&gpio4 8 GPIO_ACTIVE_HIGH>;
                label = "lcd";

                panel-timing {
                    clock-frequency = <33000000>;
                    de-active = <1>;
                    hactive = <1280>;
                    hback-porch = <16>;
                    hfront-porch = <210>;
                    hsync-active = <0>;
                    hsync-len = <30>;
                    pixelclk-active = <1>;
                    vactive = <800>;
                    vback-porch = <10>;
                    vfront-porch = <22>;
                    vsync-active = <0>;
                    vsync-len = <13>;
                };

                port {
                    lcd0_in: endpoint {
                        remote-endpoint = <&dpi0_out>;
                    };
                };
               
            };

            lcd1: display1
            {
                status = "okay";

                compatible = "osddisplays,osd070t1718-19ts", "panel-dpi";
                backlight = <&lcd_bl>;
                enable-gpios = <&gpio4 4 GPIO_ACTIVE_HIGH>;
                label = "lcd2";


                panel-timing {
                    clock-frequency = <33000000>;
                    de-active = <1>;
                    hactive = <1280>;
                    hback-porch = <16>;
                    hfront-porch = <210>;
                    hsync-active = <0>;
                    hsync-len = <30>;
                    pixelclk-active = <1>;
                    vactive = <800>;
                    vback-porch = <10>;
                    vfront-porch = <22>;
                    vsync-active = <0>;
                    vsync-len = <13>;
                };

                port {
                    status = "okay";

                    lcd1_in: endpoint {
                        remote-endpoint = <&dpi1_out>;
                    };
                };
               
            };            

&dss {
    status = "okay";

    ports {
        #address-cells = <1>;
        #size-cells = <0>;

        port@0 {
            reg = <0>;
            status = "okay";

            dpi0_out: endpoint {
                status = "okay";
                data-lines = <24>;
                remote-endpoint = <&lcd0_in>;
            };
        };

        port@1
        {
            reg = <1>;
            status = "okay";

            dpi1_out: endpoint {
                status = "okay";
                data-lines = <24>;
                remote-endpoint = <&lcd1_in>;
            };
        };
       
    };
};

With this in place,  they get output on LCD1 but not LCD2. If they probe the LCD DE, HSYNC, or VSYNC lines for LCD2,  they see no activity.  They found this e2e discussion https://e2e.ti.com/support/processors/f/791/t/646224 and tried the solution mentioned there, but  still only get output on LCD1.

They can reverse which LCD works in a number of ways. For instance, swapping the reg settings for the dss ports, so that port with dpi0_out uses reg=<0> and the one with dpi1_out use reg=<1> will then show output on LCD2. Also,  they can use a uboot option omapdrm.displays=1,0 and  also get output on LCD2 but not LCD1 (and no DE, HSYNC, or VSYNC activity for LCD1).

Below is the output when I use the modetest utility. They can see the two DPI interfaces showing up there, so they must be missing some other configuration setting.

===================================================================

# modetest
trying to open device 'i915'...failed
trying to open device 'amdgpu'...failed
trying to open device 'radeon'...failed
trying to open device 'nouveau'...failed
trying to open device 'vmwgfx'...failed
trying to open device 'omapdrm'...done
Encoders:
id      crtc    type    possible crtcs  possible clones
34      39      TMDS    0x00000001      0x00000000
40      0       TMDS    0x00000002      0x00000000

Connectors:
id      encoder status          name            size (mm)       modes   encoders
35      34      connected       DPI-1           0x0             1       34
  modes:
        name refresh (Hz) hdisp hss hse htot vdisp vss vse vtot)
  1280x800 25 1280 1490 1520 1536 800 822 835 845 33000 flags: nhsync, nvsync; type: preferred, driver
  props:
        1 EDID:
                flags: immutable blob
                blobs:

                value:
        2 DPMS:
                flags: enum
                enums: On=0 Standby=1 Suspend=2 Off=3
                value: 0
        5 link-status:
                flags: enum
                enums: Good=0 Bad=1
                value: 0
41      0       connected       DPI-2           0x0             1       40
  modes:
        name refresh (Hz) hdisp hss hse htot vdisp vss vse vtot)
  1280x800 25 1280 1490 1520 1536 800 822 835 845 33000 flags: nhsync, nvsync; type: preferred, driver
  props:
        1 EDID:
                flags: immutable blob
                blobs:

                value:
        2 DPMS:
                flags: enum
                enums: On=0 Standby=1 Suspend=2 Off=3
                value: 0
        5 link-status:
                flags: enum
                enums: Good=0 Bad=1
                value: 0

CRTCs:
id      fb      pos     size
39      64      (0,0)   (1280x800)
  1280x800 25 1280 1490 1520 1536 800 822 835 845 33000 flags: nhsync, nvsync; type: preferred, driver
  props:
        23 CTM:
                flags: blob
                blobs:

                value:
        24 GAMMA_LUT:
                flags: blob
                blobs:

                value:
        25 GAMMA_LUT_SIZE:
                flags: immutable range
                values: 0 4294967295
                value: 256
        30 background:
                flags: range
                values: 0 16777215
                value: 0
        31 trans-key-mode:
                flags: enum
                enums: disable=0 gfx-dst=1 vid-src=2
                value: 0
        32 trans-key:
                flags: range
                values: 0 16777215
                value: 0
        33 alpha_blender:
                flags: range
                values: 0 1
                value: 0
        37 rotation:
                flags: bitmask
                values: rotate-0=0x1 rotate-90=0x2 rotate-180=0x4 rotate-270=0x8 reflect-x=0x10 reflect-y=0x20
                value: 1
        27 zorder:
                flags: range
                values: 0 3
                value: 0
47      0       (0,0)   (0x0)
   0 0 0 0 0 0 0 0 0 0 flags: ; type:
  props:
        23 CTM:
                flags: blob
                blobs:

                value:
        24 GAMMA_LUT:
                flags: blob
                blobs:

                value:
        25 GAMMA_LUT_SIZE:
                flags: immutable range
                values: 0 4294967295
                value: 256
        30 background:
                flags: range
                values: 0 16777215
                value: 0
        31 trans-key-mode:
                flags: enum
                enums: disable=0 gfx-dst=1 vid-src=2
                value: 0
        32 trans-key:
                flags: range
                values: 0 16777215
                value: 0
        33 alpha_blender:
                flags: range
                values: 0 1
                value: 0
        43 rotation:
                flags: bitmask
                values: rotate-0=0x1 rotate-90=0x2 rotate-180=0x4 rotate-270=0x8 reflect-x=0x10 reflect-y=0x20
                value: 1
        27 zorder:
                flags: range
                values: 0 3
                value: 0

Planes:
id      crtc    fb      CRTC x,y        x,y     gamma size      possible crtcs
36      39      64      0,0             0,0     0               0x00000003
  formats: RX12 AR12 RG16 XR24 RG24 AR24 RA24 RX24 AR15 XR12 RA12 XR15
  props:
        6 type:
                flags: immutable enum
                enums: Overlay=0 Primary=1 Cursor=2
                value: 1
        37 rotation:
                flags: bitmask
                values: rotate-0=0x1 rotate-90=0x2 rotate-180=0x4 rotate-270=0x8 reflect-x=0x10 reflect-y=0x20
                value: 1
        27 zorder:
                flags: range
                values: 0 3
                value: 0
        38 zpos:
                flags: range
                values: 0 3
                value: 0
        28 global_alpha:
                flags: range
                values: 0 255
                value: 255
        29 pre_mult_alpha:
                flags: range
                values: 0 1
                value: 0
42      0       0       0,0             0,0     0               0x00000003
  formats: RG16 RX12 YUYV AR15 RA24 NV12 RA12 XR24 RG24 UYVY AR12 XR15 AR24 XR12 RX24
  props:
        6 type:
                flags: immutable enum
                enums: Overlay=0 Primary=1 Cursor=2
                value: 1
        43 rotation:
                flags: bitmask
                values: rotate-0=0x1 rotate-90=0x2 rotate-180=0x4 rotate-270=0x8 reflect-x=0x10 reflect-y=0x20
                value: 1
        27 zorder:
                flags: range
                values: 0 3
                value: 0
        44 zpos:
                flags: range
                values: 0 3
                value: 0
        28 global_alpha:
                flags: range
                values: 0 255
                value: 255
        29 pre_mult_alpha:
                flags: range
                values: 0 1
                value: 0
48      0       0       0,0             0,0     0               0x00000003
  formats: RG16 RX12 YUYV AR15 RA24 NV12 RA12 XR24 RG24 UYVY AR12 XR15 AR24 XR12 RX24
  props:
        6 type:
                flags: immutable enum
                enums: Overlay=0 Primary=1 Cursor=2
                value: 0
        49 rotation:
                flags: bitmask
                values: rotate-0=0x1 rotate-90=0x2 rotate-180=0x4 rotate-270=0x8 reflect-x=0x10 reflect-y=0x20
                value: 1
        27 zorder:
                flags: range
                values: 0 3
                value: 2
        50 zpos:
                flags: range
                values: 0 3
                value: 2
        28 global_alpha:
                flags: range
                values: 0 255
                value: 255
        29 pre_mult_alpha:
                flags: range
                values: 0 1
                value: 0
53      0       0       0,0             0,0     0               0x00000003
  formats: RG16 RX12 YUYV AR15 RA24 NV12 RA12 XR24 RG24 UYVY AR12 XR15 AR24 XR12 RX24
  props:
        6 type:
                flags: immutable enum
                enums: Overlay=0 Primary=1 Cursor=2
                value: 0
        54 rotation:
                flags: bitmask
                values: rotate-0=0x1 rotate-90=0x2 rotate-180=0x4 rotate-270=0x8 reflect-x=0x10 reflect-y=0x20
                value: 1
        27 zorder:
                flags: range
                values: 0 3
                value: 3
        55 zpos:
                flags: range
                values: 0 3
                value: 3
        28 global_alpha:
                flags: range
                values: 0 255
                value: 255
        29 pre_mult_alpha:
                flags: range
                values: 0 1
                value: 0

Frame buffers:
id      size    pitch

Part Number: ADS1220

I use  thermocouples of type-R to measure the temperature of molten steel. The ADC sampling chip uses ADS1220, which is normal most of the time. However, when the power of the electric furnace for heating molten steel is relatively large, the ADS1220 chip will be disturbed and the measurement result will be abnormal.Below is my circuit diagram:

Part Number: BQ25886

HI Ricardo！

If I want to test whether USB CDP can be used,How do I change my EVM connection？

The portable device outputs a nominal 0.6-V output on the D– line and reads the voltage input on the D+ line. The portable device concludes the equipment is connected to a CDP if the data line being read remains less than the nominal data detect voltage of 0.3 V. The portable device concludes it is connected to a DCP if the data line being read is greater than the nominal data detect voltage of 0.3 V.

How can I get this 0.6V voltage？I try to put D- in PULL-UP, D + in PGND,but it doesn't work .It still works in SDP mode.

Best regards from China,

Zhetao Xie

Part Number: TPS54060

Hi,

Now i have a problem about TPS54060.Before,  TPS54060A is used in my DC/DC circuit.

And the circuit works properly.When i replace TPS54060A with TPS54060,and increasing load,

the output voltage drops sharply.I'd like to know the differences between TPS54060 and TPS54060A.

Thanks.

Part Number: BQ24002

hi
I have a question
BQ24002 data sheet indicates that VCC current is 1mA
60mA when output current is precharged
But when I use the actual circuit, I find that the output current is related to the input current. When the output current is 60mA, the input current must also be maintained at 60mA. What is the reason for this?
Can you recommend some current charging chips

Thank you
best wishes

Part Number: TPS92611-Q1

Hi Sir,

I check on the spec, TPS92611 will report fault when there is a short/open condition on LED.

My customer would like to know if TPS92611 could report fault when output current over 100mA or lower than 38mA?

Many thanks.

Patrick 

Part Number: CC1352R

Tool/software: Code Composer Studio

Hello,

I am trying to get the driverlib/timer.h included in the CCS project but I am not sure on the location of these files. I installed SimplinkSDK and searched the ti/ directory but it is nowhere to be found. Do I need to download them? If so, it would be great if you could provide me a link.

Thank you for your time 

Vignesh

Part Number: TPS563219A

Dear Team,

Is it acceptable to operate this device with such low current?

BR

Kevin

Part Number: DS90UB953A-Q1

Hi Champs,

I have question about Vos spec in the datasheet, please also check attached file.

Vos is defined in the group of "FPD-LINK III DRIVER SPECIFICATIONS(DIFFERENTIAL)" in Electrical Characteristic clause.

I suppose Vos should be a parameter for single ended, so may I know how Vos defined in differential condition.

Best regards,

Nobuo

(Please visit the site to view this file)

Some questions to be answered..

(Please visit the site to view this file)(Please visit the site to view this file)(Please visit the site to view this file)

Part Number: IWR6843ISK

Hi

I noticed that you use different boards (e.g., ISK, ISK_ODS, AOP) in different labs (Industrial Toolbox 4.1.0)? I was wondering if IWR6843ISK is enough to run all the labs.

Thanks!

Kai