Quantcast
Viewing all 262198 articles
Browse latest View live

CC2640R2F: BLE mouse report rate issue ( Windows 7 )

Part Number: CC2640R2F

Hi All,

PC OS : windows 7

Platform : CC2640R2F

Application : BLE mouse

SDK : simplelink_cc2640r2_sdk_2_40_00_32

Our customer using CC2640R2F on BLE mouse product ( BT 4.2 ) , test on windows 7 and find out report rate was very low. Also test competitor product ( BT4.2 ) , but without any report rate issue.

So we using sniffer to Capture packet and compare  the message log between CC2640R2F and competitor.

We find out when CC2640R2F send start encryption but master did not respond, then master start to do new connection ( Goes on and on ).

Image may be NSFW.
Clik here to view.

But test competitor product, it sends start encryption and get response packet form master ( Windows 7 ).

Image may be NSFW.
Clik here to view.

So, does BLE encryption fail cause the low report rate? If yes, any command can fix this issue ?

If not, any other reason cause the low report rate?

P.S Sniffer log as below link.

Image may be NSFW.
Clik here to view.


CCS/TMS320F28377D: Memory organization,

Part Number: TMS320F28377D

Tool/software: Code Composer Studio

Dear TI Hello,

I have a question about the memory organization of the TMS320F28377D,

The TMS320F28377D has a multiple memory blocks.

  • M0 RAM
  • D0 RAM
  • Shared LS0-LS5    RAM
  • Shared GS0-GS15 RAM
  • ...

I d like to know the difference between the M0, D0, LS, GS and D0.

Is there any specific use of the M0 and D0? Boot for example ...

Regards,

Thank you in advance,

S.Tarik,

LM5119: When the output of LM5119 is idle, the input power consumption is too large (0.1a 48V). What is the reason for this?

Part Number: LM5119

When the output of LM5119 is idle, the input power consumption is too large (0.1a 48V). What is the reason for this?
We made the products according to the attached schematic diagram
48 v input
Output 8 a 42 v
When the output is 0 load, the input power consumption is 48V, 0.1a?What's the reason?

Image may be NSFW.
Clik here to view.

Compiler/AWR1443BOOST: xwr14xx_can_mss.xer4f

Part Number: AWR1443BOOST

Tool/software: TI C/C++ Compiler

Hi,

for awr1443 board, I installed sdk mmwave_sdk_01_01_00_02.  I imported can driver into CCS.

I flashed ccsdebug of 1443 also.  i am not getting .xer4f for 1443. 

I tried to add symbpols in properities. but that option is not there.

when i build the code ,    only .xer4f for 1642 is generated    i want .xer4f for awr1443.  

for that    where should i define SOC_XWR14XX .     or any modifications should i do in code to get  .xer4f for 1443. 

by default soc is defined for 1642.   where sould i modify.  please guide me to run awr1443 board with CAN driver     not with demo code. 

Thanks and regards,

K Subrahmaniam

DS90UB953-Q1: Details of Reg 0x77 and 0x79

DCA1000EVM: data collection is abnormal for DCA1000 capture card

Part Number: DCA1000EVM

Hi Team,

Customer uses DCA1000 capture card with AWR1642 EVM board for data acquisition and testing. The board voltage is abnormal, then he replaced power chip. After that, the test voltage is normal. But the collected data is incorrect.

Customer did the following testing. He sends fixed data 0xAA to the data acquisition board through the electric demo board. The data is not all 0xAA, some abnormal data will appear. Collect data as shown below.

Customer would like to know:
1. How to reslove this issue?
2. DCA1000 capture card board uses FPGA. Is there an FPGA source code available?
3. Will TI provide repair services?

Image may be NSFW.
Clik here to view.

DS90UB941AS-Q1: Application consult

Part Number: DS90UB941AS-Q1

Dear experts,

Our customer is using our SerDes products. Now they have below questions:

1. What's the difference between UH and UB version of 941 except for UH supports HDCP applications?

2. What's the difference among input signal and sequence in time demand of UB, UH, A, AS version?

Thanks for your help!

DS90UB954-Q1: Internal clock

Part Number: DS90UB954-Q1

Hi team,

We do emission tests on the 953-954 system.

Therefore, I want to know the frequency of the internal clocks the both of 953 and 954 respectively.

Best regards,

Tomoaki Yoshida


TMS320C6655: Application of Chip Support Library(CSL) for TMS320C6000

Part Number: TMS320C6655

Hi Team,

Please help me answer the follow question from my customer, thank you so much.

Please confirm whether TMS320C6000 Chip Support Library can be used when developing TMS320C6655CZH.
If we can't use it, please let me know alternative CSL and system documentation.

The TMS320C6416 series was used in the previous product and the above CSL was used at that time.

Best Regards,
Tom Liu

LM5119: can it be used for constant current output?

Part Number: LM5119

Customer wants to use a controller for 12V input, <= 3V output, with 45A constant  output current. Can LM5119 achieve this? If not, do you have any other suggested parts? Thank you.

Open / short teat

Part Number: UCC28180

Hi

My customer is considering the behavior of open/short test.

Could you please give me your comment for attached file?

(Please visit the site to view this file)

Muk

TPS560430: OPTIONAL FILTER VALUE

Part Number: TPS560430

Hello,

              We need one more optional filter for TPS560430 O/P side. Kindly suggest me optional filter value.

               Present value is : 15uH.

With Regards,

Nivetha A.

ISO5852S: ISO5852 IC Details

Part Number: ISO5852S

Does the ISO5852 offers high input impedance.This information is not available in the datasheet.

Also the input current requirement?

ADS1296R: RESPIRATION QUESTIONS

Part Number: ADS1296R

Hi,

I posted a question yesterday and thanks for replying.

e2e.ti.com/.../3083831

There are few more related questions:

1. Is the settle time equivalent to the sampling time of the ADC?

2.Why the rise/fall period leads to higher noise? theoretically, the rise/fall time will affect the gain of the signal and noise at the same time ( if encountered with the rise time, the signal gain will decrease so will the noise).Why the rise/fall time in experiment weaken the signal while increasing the noise?

SN74CB3Q3257: Difference between SN74CB3Q3257 and SN74CBLV3257

Part Number: SN74CB3Q3257

Hi there,

 

What's the detailed difference between SN74CB3Q3257 and SN74CBLV3257.

The reason I am asking is that we observed some signal quality issues(solid failure) with SN74CBLV3257, while with SN74CB3Q3257 it is error free. So I am wondering if there are any difference between these two parts on the signals passing by.

 

Some more info here:

In our design, VCC=3.3V and failure rate become higher if we apply voltage margin to 5%.

And the select pin is always high.


CC2530: Auto bind on joining the network

Part Number: CC2530

Hi,

We are using Zstack 302 and a znp coordinator.

How can a router add coordinator to its binding table on joining a network?
I would like the coordinator to receive reports from the router automatically( without the coordinator making a bind request to the router) .

TCA9617B: TCA9617BDGKR

Part Number: TCA9617B

Hi Team,

We are going to use TCA9617BDGKR in our design. So, I request you to  provide the nominal current consumption details of VCC5V & VCCA. It is not available in the datasheet

As of now we have calculated using the pull-up resistors, since it is acting as a level shifter.

Thanks & regards,

E.Rohini

AM3354: Custom board based on AM335x Starter Kit - second ethernet (DP83822) not working

Part Number: AM3354

Hi,
we are developing a custom board based on AM335x Starter Kit, equipped with two etherent ports with physical device DP83822.

The dts file part related to ethernet configuration is the following:

    cpsw_default: cpsw_default {
        pinctrl-single,pins = <
            /* Slave 1 */
            AM33XX_IOPAD(0x90c, PIN_INPUT | MUX_MODE1) /* (H17) gmii1_crs.rmii1_crs_dv */
            AM33XX_IOPAD(0x910, PIN_INPUT | MUX_MODE1) /* (J15) gmii1_rxer.rmii1_rxer */
            AM33XX_IOPAD(0x914, PIN_OUTPUT | MUX_MODE1) /* (J16) gmii1_txen.rmii1_txen */
            AM33XX_IOPAD(0x928, PIN_OUTPUT | MUX_MODE1) /* (K17) gmii1_txd0.rmii1_txd0 */
            AM33XX_IOPAD(0x924, PIN_OUTPUT | MUX_MODE1) /* (K16) gmii1_txd1.rmii1_txd1 */
            AM33XX_IOPAD(0x940, PIN_INPUT | MUX_MODE1) /* (M16) gmii1_rxd0.rmii1_rxd0 */
            AM33XX_IOPAD(0x93c, PIN_INPUT | MUX_MODE1) /* (L15) gmii1_rxd1.rmii1_rxd1 */
            AM33XX_IOPAD(0x944, PIN_INPUT | MUX_MODE0) /* (H18) rmii1_refclk.rmii1_refclk */

            /* Slave 2 */
            AM33XX_IOPAD(0x864, PIN_INPUT | MUX_MODE3) /* (U16) gpmc_a9.rmii2_crs_dv */
            AM33XX_IOPAD(0x874, PIN_INPUT | MUX_MODE3) /* (U17) gpmc_wpn.rmii2_rxer */
            AM33XX_IOPAD(0x840, PIN_OUTPUT | MUX_MODE3) /* (R13) gpmc_a0.rmii2_txen */
            AM33XX_IOPAD(0x854, PIN_OUTPUT | MUX_MODE3) /* (V15) gpmc_a5.rmii2_txd0 */
            AM33XX_IOPAD(0x850, PIN_OUTPUT | MUX_MODE3) /* (R14) gpmc_a4.rmii2_txd1 */
            AM33XX_IOPAD(0x86c, PIN_INPUT | MUX_MODE3) /* (V17) gpmc_a11.rmii2_rxd0 */
            AM33XX_IOPAD(0x868, PIN_INPUT | MUX_MODE3) /* (T16) gpmc_a10.rmii2_rxd1 */
            AM33XX_IOPAD(0x908, PIN_INPUT | MUX_MODE1) /* (H16) gmii1_col.rmii2_refclk */
        >;
    };

    davinci_mdio_default: davinci_mdio_default {
        pinctrl-single,pins = <
            /* MDIO */
            AM33XX_IOPAD(0x948, PIN_INPUT | MUX_MODE0)  /* (M17) mdio_data.mdio_data */
            AM33XX_IOPAD(0x94c, PIN_OUTPUT | MUX_MODE0) /* (M18) mdio_clk.mdio_clk */
        >;
    };

....

&mac {
    pinctrl-names = "default", "sleep";
    pinctrl-0 = <&cpsw_default>;
    pinctrl-1 = <&cpsw_sleep>;
    dual_emac = <1>;
    status = "okay";
};

&davinci_mdio {
    pinctrl-names = "default", "sleep";
    pinctrl-0 = <&davinci_mdio_default>;
    pinctrl-1 = <&davinci_mdio_sleep>;
    status = "okay";
    reset-gpios = <&gpio1 18 GPIO_ACTIVE_LOW>;
    reset-delay-us = <2>;   /* PHY datasheet states 1uS min */

    ethphy0: ethernet-phy@1 {
        reg = <1>;
    };

    ethphy1: ethernet-phy@2 {
        reg = <2>;
    };
};

&cpsw_emac0 {
    phy-handle = <&ethphy0>;
    phy-mode = "rmii";
    dual_emac_res_vlan = <1>;
};

&cpsw_emac1 {
    phy-handle = <&ethphy1>;
    phy-mode = "rmii";
    dual_emac_res_vlan = <2>;
};

&phy_sel {
    rmii-clock-ext;
};

The first port (eth0) works fine (dhcp works as well on this port), while the second (eth1) is not working.
We checked with a network sniffer that the trasmitting part (for eth1) is ok (ARP packet requests and responses are logged during a ping command), and the physical level (rmii_rxd0 and rmii_rxd1) seems ok (checked with an oscilloscope) since we see data flowing. Anyway the network communication is not working.
We have also verified that all pins connection in receiving part are ok: we configured the pins as output GPIO and checking the output on physical the level is the one expected.
We checked the DP83822 register configurations for both ports, and they are correct and and the same for both ports.

The problem has been seen and debugged on different boards, so we exclude a single faulty unit.

Here are some kernel logs at startup:

...
[    1.007968] libphy: Fixed MDIO Bus: probed
[    1.078735] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6, bus freq 1000000
[    1.086779] libphy: 4a101000.mdio: probed
[    1.093311] davinci_mdio 4a101000.mdio: phy[1]: device 4a101000.mdio:01, driver TI DP83822 10/100 Mbps PHY
[    1.103566] davinci_mdio 4a101000.mdio: phy[2]: device 4a101000.mdio:02, driver TI DP83822 10/100 Mbps PHY
[    1.114605] cpsw 4a100000.ethernet: Detected MACID = 74:e1:82:8b:63:97
[    1.121777] cpsw 4a100000.ethernet: initialized cpsw ale version 1.4
[    1.128440] cpsw 4a100000.ethernet: ALE Table size 1024
[    1.134873] cpsw 4a100000.ethernet: cpsw: Detected MACID = 74:e1:82:8b:63:99
...

[    5.939999] net eth0: initializing cpsw version 1.12 (0)
[    6.043537] TI DP83822 10/100 Mbps PHY 4a101000.mdio:01: attached PHY driver [TI DP83822 10/100 Mbps PHY] (mii_bus:phy_addr=4a101000.mdio:01, irq=POLL)
...
[   15.439020] net eth1: initializing cpsw version 1.12 (0)
[   15.563550] TI DP83822 10/100 Mbps PHY 4a101000.mdio:02: attached PHY driver [TI DP83822 10/100 Mbps PHY] (mii_bus:phy_addr=4a101000.mdio:02, irq=POLL)
...

Connecting the cable to eth1 the link is correctly up:
[   18.730744] cpsw 4a100000.ethernet eth1: Link is Up - 100Mbps/Full - flow control rx/tx

We have set eth1 port to static IP configuration and run the ping command to my PC, the ifconfig command returns the following:

#ifconfig
eth0      Link encap:Ethernet  HWaddr 74:E1:82:8B:63:97  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:43

eth1      Link encap:Ethernet  HWaddr 74:E1:82:8B:63:99  
          inet addr:172.20.1.29  Bcast:0.0.0.0  Mask:255.255.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:576 (576.0 B)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:11 errors:0 dropped:0 overruns:0 frame:0
          TX packets:11 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1232 (1.2 KiB)  TX bytes:1232 (1.2 KiB)

The ethtool output for the second port:

# ethtool eth1
Settings for eth1:
    Supported ports: [ TP MII ]
    Supported link modes:   10baseT/Half 10baseT/Full
                            100baseT/Half 100baseT/Full
    Supported pause frame use: Symmetric Receive-only
    Supports auto-negotiation: Yes
    Advertised link modes:  10baseT/Half 10baseT/Full
                            100baseT/Half 100baseT/Full
    Advertised pause frame use: No
    Advertised auto-negotiation: Yes
    Link partner advertised link modes:  10baseT/Half 10baseT/Full
                                         100baseT/Half 100baseT/Full
    Link partner advertised pause frame use: Symmetric Receive-only
    Link partner advertised auto-negotiation: Yes
    Speed: 100Mb/s
    Duplex: Full
    Port: MII
    PHYAD: 2
    Transceiver: internal
    Auto-negotiation: on
    Supports Wake-on: d
    Wake-on: d
    Current message level: 0x00000000 (0)
                   
    Link detected: yes

Can you please help us with this issue?

Thanks.

TPD12S016: TPD12S016PWR

Part Number: TPD12S016

Hi Team,

We would like to know the maximum current consumption details of TPD12S016PWR for our new design, since it is not available in datasheet.

Thanks & regards,

E.Rohini

TLV320AIC3106: TLV320AIC3106IRGZT

Part Number: TLV320AIC3106

Hi Team,

We would like to kkow the current consumption details of TLV320AIC3106IRGZT for our new design, since it is not available in the datasheet or any design documents.

Thanks & Regards,

E.Rohini

Viewing all 262198 articles
Browse latest View live


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