Hi,
I can see TPS73633-Q1 part in TPS736-Q1 Datasheet, I have TPS73633-Q1 (Fixed 3.3V output ) part, but I did not see TPS73633-Q1 order information.
Do you check TPS73633-Q1 RTM? can we provide this part TPS73633-Q1? Thanks!
Hi,
I can see TPS73633-Q1 part in TPS736-Q1 Datasheet, I have TPS73633-Q1 (Fixed 3.3V output ) part, but I did not see TPS73633-Q1 order information.
Do you check TPS73633-Q1 RTM? can we provide this part TPS73633-Q1? Thanks!
Part Number:TCA9534A
Hi team,
My customer wants to know when /INT is reset.
In the datasheet page.17 8.3.2 Interrupt Output (INT) section, there is a description that
"Resetting the interrupt circuit is achieved when data on the port is changed to the original
setting or data is read from the port that generated the interrupt".
We understood as in the following time chart, is it correct? please let me know.
Best regards,
Fumio Nakano
Part Number:OPA857
Hi team,
Is OPA857 a proper device for the following photodiodes? Otherwise, can you please recommend the proper transimpedance amp?
C30737PH (Silicon Avalanch Photodiodes for Lidar) : http://www.excelitas.com/downloads/DTS_C30737PH.pdf
Thanks,
Sam Lee
Part Number:DP83867IS
HI,
THIS IS KISHORE .WE HAVE A CUSTOM BOARD (XILINX ARTIX 7 FPGA) WHICH IS INTERFACED TO TI PART NO :DP83867ISRGZ IN RGMII MODE.
STRAP CONFIGURATIONS ARE AS FOLLOWS:
GPIO_0 : MODE3
GPIO_1 : MODE2
LED_0 : MODE1
LED_1 : MODE2
LED_2 : MODE1
RX_CTRL : MODE3
RX_D0 : MODE1
RX_D2 : MODE1.
WE HAVE CHECKED ALL THE VOLTAGES AT THE RESPECTIVE STRAPS AND IT IS WITH IN THE RANGE AS PER THE DATASHEET.
DURING AUTONEG 1G SPEED IS DETECTED BUT IT'S NOT PINGING.
-----lwIP TCP echo server ------
TCP packets sent to port 6001 will be echoed back
Start PHY autonegotiation
Start PHY autonegotiation
Waiting for PHY to complete autonegotiation.
autonegotiation complete
auto-negotiated link speed: 1000
DHCP Timeout
Configuring default IP of 192.168.1.10
Board IP: 192.168.1.10
Netmask : 255.255.255.0
Gateway : 192.168.1.1
TCP echo server started @ port 7.
KINDLY HELP US ,THE PROJECT IS IN CRITICAL STAGE .KINDLY ARRANGE TO SEND YOUR APPLICATION ENGINEER TO OUR WORK PLACE.
Part Number:TPS7B63-Q1
Hi all,
my customer wants to use the watchdog function of TPS7B6333-Q1 with the following parameters (see, datasheet p. 15):
FSEL = Low
R_ROSC = 2 k .. 10 kOhm (twd = 1 .. 5 ms), lower value is better from customer’s systems perspective.
In the overview / specification R_ROSC is used as a parameter (not limited) with values >= 20 kOhm
Does/What kind of side effect(s) does the customer introduce if they choose R_ROSC in the range 2k .. 10 kOhm?
What disadvantages besides of higher power dissipation will occur?
Thanks,
Konrad
Part Number:TMDSDOCK28379D
Hello,
I receive "The JTAG DR Integrity scan-test has failed" warning upon trying a test connection. I cannot debug and load the program as well, i did not record the error message.
While searching the previous answers for related problems, I happened to find another control card, when I installed in on the docking station everything works as expected. Which eliminates the possibility of software related errors, I suppose.
The point is: the device was not connected to a converter, I was following the "multi-day workshop". I returned from lunch and saw the card malfunctioning. Electrical damage to the control card is very unlikely as it just sits on the table.
Does this situation show that the previous control card is physically damaged? It is kind of bad loosing a control card like this.
Any advice will be appreciated.
Thank you in advance
Part Number:TMS320C6678
Hello Champs,
Do we have matrix Inversion based on cholesky for TMS320C6678? Customer needs a high speed matrix inversion function.
Thanks.
Rgds
Shine
Part Number:AM3352
Tool/software: Linux
Hello, everybody.
I use SDK 04.00.00.04, and linux version is 4.9.28. After I set the ethernet to RMII mode and then I got the error like this:
[ 1.556382] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6
[ 1.562893] davinci_mdio 4a101000.mdio: no live phy, scanning all
[ 1.569968] davinci_mdio: probe of 4a101000.mdio failed with error -5
[ 1.578211] cpsw 4a100000.ethernet: No slave[1] phy_id, phy-handle, or fixed-link property
The phy I used is dp83620.Following is my dts about ethernet:
cpsw_default: cpsw_default {
pinctrl-single,pins = <
/* Slave 1 */
AM33XX_IOPAD(0x90C, PIN_INPUT_PULLDOWN | MUX_MODE1) /* mii1_crs.rmii1_crs_dv */
AM33XX_IOPAD(0x910, PIN_INPUT_PULLDOWN | MUX_MODE1) /* mii1_rxerr.rmii1_rxerr */
AM33XX_IOPAD(0x914, PIN_OUTPUT | MUX_MODE1) /* mii1_txen.rmii1_txen */
AM33XX_IOPAD(0x924, PIN_OUTPUT | MUX_MODE1) /* mii1_txd1.rmii1_txd1 */
AM33XX_IOPAD(0x928, PIN_OUTPUT | MUX_MODE1) /* mii1_txd0.rmii1_txd0 */
AM33XX_IOPAD(0x944, PIN_INPUT_PULLDOWN | MUX_MODE0) /* mii1_refclk.rmii1_refclk */
AM33XX_IOPAD(0x93c, PIN_INPUT_PULLDOWN | MUX_MODE1) /* mii1_rxd1.rmii1_rxd1 */
AM33XX_IOPAD(0x940, PIN_INPUT_PULLDOWN | MUX_MODE1) /* mii1_rxd0.rmii1_rxd0 */
>;
};
cpsw_sleep: cpsw_sleep {
pinctrl-single,pins = <
/* Slave 1 reset value */
AM33XX_IOPAD(0x90C, PIN_INPUT_PULLDOWN | MUX_MODE7)
AM33XX_IOPAD(0x910, PIN_INPUT_PULLDOWN | MUX_MODE7)
AM33XX_IOPAD(0x914, PIN_INPUT_PULLDOWN | MUX_MODE7)
AM33XX_IOPAD(0x924, PIN_INPUT_PULLDOWN | MUX_MODE7)
AM33XX_IOPAD(0x928, PIN_INPUT_PULLDOWN | MUX_MODE7)
AM33XX_IOPAD(0x944, PIN_INPUT_PULLDOWN | MUX_MODE7)
AM33XX_IOPAD(0x93c, PIN_INPUT_PULLDOWN | MUX_MODE7)
AM33XX_IOPAD(0x940, PIN_INPUT_PULLDOWN | MUX_MODE7)
>;
};
davinci_mdio_default: davinci_mdio_default {
pinctrl-single,pins = <
/* MDIO */
AM33XX_IOPAD(0x948, PIN_INPUT_PULLUP | SLEWCTRL_FAST | MUX_MODE0) /* mdio_data.mdio_data */
AM33XX_IOPAD(0x94c, PIN_OUTPUT_PULLUP | MUX_MODE0) /* mdio_clk.mdio_clk */
>;
};
davinci_mdio_sleep: davinci_mdio_sleep {
pinctrl-single,pins = <
/* MDIO reset value */
AM33XX_IOPAD(0x948, PIN_INPUT_PULLDOWN | MUX_MODE7)
AM33XX_IOPAD(0x94c, PIN_INPUT_PULLDOWN | MUX_MODE7)
>;
};
&mac {
pinctrl-names = "default", "sleep";
pinctrl-0 = <&cpsw_default>;
pinctrl-1 = <&cpsw_sleep>;
status = "okay";
};
&davinci_mdio {
pinctrl-names = "default", "sleep";
pinctrl-0 = <&davinci_mdio_default>;
pinctrl-1 = <&davinci_mdio_sleep>;
status = "okay";
};
&cpsw_emac0 {
phy_id = <&davinci_mdio>, <5>;
phy-mode = "rmii";
};
&phy_sel {
rmii-clock-ext;
};
Is there any error in my dts? How can I deal the problem?
Thanks!
Part Number:DK-TM4C129X
The raster mode is set. DMA is on. Ping-Pong is not used.
If we change the picture pixel by pixel, then everything is fine, but if we update it with a block, for example, symbol 44 font, the display blinks. There is an interrupt DMA FIFO Underflow. Apparently interrupted LCD DMA
At what point can we write to the buffer to avoid interrupting the DMA?
Part Number:PCA9306-Q1
What is the difference between PCA9306IDCURQ1 and PCA9306TDCURQ1?
Best Regards,
Yaita / Japan disty
Part Number:TCAN1051-Q1
Hello,
The S pin of TCAN1051 is suggested connected to GND via a pulldown resistor when unused in the datasheet p.27.
But is the resistor really necessary? Can't it be connected directly to GND?
Thanks.
Regards,
Oguri
Part Number:TMP116
Tool/software: Code Composer Studio
it is possible, you send me how to interface the temperature sensor TMP116 with cc1310f64, please?
Part Number:TMS320F280049
Hello,
are there any plans to add the TMS320F280049 in Motorware?
Regards, Holger
Part Number:TMS320C6678
Tool/software: TI C/C++ Compiler
Dear Team,
My customer is complaining on the build time of C6x compiler and requested to provide coding guide to avoid long build time.
Their compiler version is very old - v7.3.0. Do you think this compile time can be shorter when they upgrade compiler version with latest one?
Actually, I'm afraid they can not upgrade compiler version as they have used it very long time and their RTOS version and other SW packages are also old.
In C6000 compiler v7.3.0, Could you please provide a guide to reduce this compile time?
- Is there compiler option to reduce build time with minimal impact on performance?
- Is there coding guide to reduce build time? like avoid if, for, and so on.
My customer's log is as below.
/opt/CCSv5/C6000CGT7.3.0/bin/cl6x -@DebugThread_ccsCompiler.opt
+----- /opt/CCSv5/ccsv5/utils/gmake/gmake -k -j8 all
+---- (build time: 02m26s) /opt/CCSv5/C6000CGT7.3.0/bin/opt6x --gen_opt_info=2 tmp/147320aKbMU tmp/147326jX9Zp --opt_info_filename=DebugThread.nfo
+---- (build time: 11m34s) /opt/CCSv5/C6000CGT7.3.0/bin/cg6x tmp/23670asnYm9 --template_info_file=tmp/23670ySMnvt DebugThread.asm
+---- (build time: 6m34s) /opt/CCSv5/C6000CGT7.3.0/bin/cmp6x tmp/23670Ip34M7 DebugThread.obj DebugThread.lst
+---- (build time: 0m 2s) /opt/CCSv5/C6000CGT7.3.0/bin/lnk6x -ltmp/13903sjyewy
~~~~~~~
< from nfo file >
extern unsigned DownlinkChannelInfoFix() is called from 0 sites in this file.
It appears to be inlineable (size = 12506 units)
It has 6 non-trivial scope blocks nested 4 deep.
It calls these functions:
HasFeature() (12 times)
AggregationAndBoostInfoSetForCa() (1 times)
PdschUpstepSizeDecide() (1 times)
MacControlChInfoSet() (1 times)
OlrcBackOffAdjustInitialize() (1 times)
SetDlSmart() (1 times)
SDM_MemoryPuts() (8 times)
SDM_MemoryPrintf() (413 times)
atoi() (787 times)
strcmp() (189 times)
<...skip....>
extern unsigned DownlinkChannelInfoFix() is called from 0 sites in this file.
It appears to be inlineable (size = 12506 units)
It has 6 non-trivial scope blocks nested 4 deep.
It calls these functions:
strcmp() (189 times)
HasFeature() (12 times)
====== Unroll-and-jam Result Summary ======
LOOP#46 in DownlinkChannelInfoFix() fails to unroll-and-jam: Impermissible side effects
====== End Unroll-and-jam Result ======
Optimization summary for cross-iteration vectorization (SIMD)
in DownlinkChannelInfoFix()
Unrolling and vectorizing the "for" loop at lines 14017-14020 by a factor of 2x.
This loop has 25 iterations.
The unrolling factor 2 does not provably divide the
iteration count, so we will add a 'peeled' loop for
the last few iterations. Its iteration count is 1.
Vectorizing this store 2x at line 14019: *(NONALIGN((unsigned *)((unsigned *)v$2+cElement*4+68))) = S2V(0uLL);
in this statement: ((unsigned *)v$2)[cElement+17] = 0u;
~~~~~~~
< compiler option >
<file: DebugThread_ccsCompiler.opt>
-mv6600
--symdebug:skeletal
-O3
--gcc
--include_path=/opt/CCSv5/C6000CGT7.3.0/include --include_path=/opt/CCSv5/pdk_C6678_1_0_0_15_new/packages --include_path=/opt/CCSv5/pdk_C6678_1_0_0_15_new/ti/csl/src/intc <생략>
--display_error_number
--diag_suppress=1 --diag_suppress=145 --diag_suppress=169 --diag_suppress=67 --diag_suppress=179 --diag_suppress=552
--diag_warning=225
--big_endian
--mem_model:data=far
--abi=eabi
--opt_for_speed=5
--gen_opt_info=2
-k
--asm_listing
--output_all_syms
--preproc_with_compile
--preproc_dependency=DebugThread.pp
--obj_directory=COMMON
--cmd_file=./configPkg/compiler.opt
<file: Debug/configPkg/compiler.opt>
-me -mv6600 --abi=elfabi -I"/opt/CCSv5/bios_6_31_04_27/packages" -I"/opt/CCSv5/pdk_C6678_1_0_0_15_new/packages" -I"/opt/CCSv5/ipc_1_22_05_27/packages" -I"/opt/CCSv5/edma3_lld_02_11_05_02/packages" -I"/opt/CCSv5/xdctools_3_20_08_88/packages" -I"configPkg/.." -I/opt/CCSv5/C6000CGT7.3.0/include -Dxdc_target_types__="ti/targets/elf/std.h" -Dxdc_target_name__=C66_big_endian -Dxdc_cfg__header__="configPkg/package/cfg/PHY_pe66e.h
Thanks and Best Regards,
SI.
Part Number:TPL5110EVM
Hi,
Firstly, i am reading documentation for TPL5110EVM from following link "http://www.ti.com/product/TPL5110/technicaldocuments"
I understand the basic concept that, TPL5110EVM active power consumption is significantly lower than microcontroller sleep state consumption. I got that.
But i have following questions:
Q1. TPL5110EVM will totally cut off power to mcu during "OFF Time" right. Thats mean, when it back to "ON Time" again, mcu will behave like, just power on and will have to re-initialize all of its routine again, isn't it just consuming more power rather than wake up from sleep state?
Q2. Is there any documentation/experiment that is conducted for Q1 related scenarios using mcu such as CC2541 or CC2641 to verify that TPL5100EVM is saving power even though mcu has to redo the initialization?
Thank you.
LB
Part Number:MSP-FET
Good Morning everybody!
Today I'm here to highlight an annoying issue with MSP-FET Flash Emulation Tool.
What I noticed is this: if in close proximity of my FET there is, for example, a power strip with on/off switch button and someone else is using it (switching on or off) while I'm doing the debug of my code, the program suddenly gets stuck. This is the same behaviour as if you have some relays on the board on wich you are programming: if I'm in debug mode, step by step, and at some point the relay is triggered, the debug gets stuck and I have to:
--> stop the debug mode
--> disconnect the emulator from both the PC and the board
--> re-connect everything and actually re-start with my debug section.
How is it possible that the emulator is so sensitive?
Is there a way to avoid this annoying behaviour?
I really would appreciate any advice and piece of help.
Kind Regards,
Maria Angela