Part Number: TPS7A8300
Hi Team,
Is it OK to assume that the dropout voltage characteristics of TPS7A83A and TPS7A8300 are the same?
My customer asked that
The dropout voltage graph described in the TPS7A8300 data sheet is difficult to understand,
and the TPS7A83A was easy to understand. If the characteristics were the same,
I would like to refer to the TPS7A83A.
Sorry for the urgent request, can you answer ASAP?
Thanks
Best regards,
Shidara
Part Number: DCA1000EVM
Hi, I am trying to determine the maximum number of targets an AWR1642BOOST and DCA1000 can record data for, but there is no documentation on the data size of each target or anything related to the maximum amount of data a system like this can record at the same time. I have the stock 8GB microSD card that the DCA1000EVM comes with. And I am also interested in determining the maximum number of targets a single AWR1642BOOST can view on your web based demo visualizer.
Thanks
Part Number: ADS1158
Hello Sir,
Currently, I make a ADS1158(or ADS1258) based DAQ board with reference to the ADS1158 EVM board (ADS1258 EVM).
I used same capacitor value and same crystal(load capacitance, ESR) to my DAQ board, but it does not provide clock signals.
Sometimes, It generate the clock signal only for short time about less than 20s.
I did many things to make clock signal as explained below.
1) Low temperature soldering for short time
2) Crystal soldering carefully to do not damage the crystal structure
3) Change the crystal to other product (same specification, just different manufacturer)
Even I change the crystal on ADS1158EVM, it does provide clock signal only for short time about 10s as same situation above.
Could you give me advice to make clock signal to ADS1158?
Is there any specific crystal ADS1158 EVM using?
Best regards,
Dae-Jin Kim
Part Number: MSP432E401Y
Hi,
I would like to move the application code space to start at 0x80000. I changed the linker but it fails to build. I'm guessing I also need to change something in the rtos. If I can't change the rtos then can I have a baremetal bootloader run at address 0x80000 and install a rtos app that runs from address 0?
Regards,
-Mike
Part Number: MSP432P4111
Hi,
could someone point me to a working driver for UART with DMA support and NORTOS for MSP432? There are a number of code snippets on e2e, but I must believe we have something known to work.
https://e2e.ti.com/support/microcontrollers/msp430/f/166/p/726810/2681774
Thanks!
--Gunter
Part Number: MSP430F2013
Dear All,
My sensor generates 2.25 volts at no stimulus and down to 1.65 volts at full scale.
The VREF for MPS430 16bit A/D is 1.2 volts with +/-600mv Range at Gain = 1
Does this mean A0+(max) = 1.2V + 300mv and A0-(min)=1.2V - 300mv and this corresponds to +600mV differential input and
A0+(min) = 1.2V - 300mv and A0-(max)=1.2V + 300mV and this corresponds to -600mV differential input.
Do I have to convert my single ended, 2.25V to 1.65V signal, to a differential 1.2V+/- 300mV to harness the full scale of A/D converter ?
Can I just connect VREF=1.2V to A0- and level shift sensor signal down from 2.25 volts to 1.5volts (and 1.65v to 0.9v) and feed at A0+ ?
[ I will lose half the A/D range ]
Thanks
Rajan
Part Number: ADC12DJ3200EVM
Hello,
I have been using the ADC12DJ3200EVM with Fs = 2 GHz in JMODE0. I will attach the .ini file I have been using.
When I increase the Fs to 2.7 GHz using the ADC GUI, I am no longer able to read data and instead get a TIMED_OUT_ERROR.
I am still able to switch back to Fs=2 GHz and get data. Also, I am still able to read data at Fs = 1.6 GHz.
My guess is that I need to edit the .ini file and/or use a different firmware file.
Thank you,
Alex
(Please visit the site to view this file)
Part Number: AM5728
Tool/software: TI C/C++ Compiler
How can I compile fftlib to run fft on DSP in am57x8 evms, and it is based on processor_sdk_rtos_am57xx_4_03_00_05.
Part Number: CC2541EMK
Using SmartRF Studio 7 to control CC2541EMK, I am controlling the LNAGAIN. If I change one of the three LNAs to 0dB, is that LNA bypassed or is the gain changed?
thanks
Part Number: TPS7A4701EVM-094
Hello,
I am using the eval board, with the test setup described in the user guide. However, when the enable jumper is turned to ON it looks like there is a short, the input voltage drops from 12V to 2.5V. Current draw is less than 0.5A. I am using a load resistor of 2 ohms (30W). My output voltage jumper is is set to 3.2V. Switching the jumper back to the off enable jumper, the input voltage shows 12 V.
Part Number: TS3L500
Dear all,
I would like to ask about unnecessary pin processing.
Our customers are trying to use it with 10 / 100Base.
We do not consider using the SW PHY terminal (for example, A4 to A7).
In this case, is there any recommended treatment for unused pins?
I checked the data sheet, but couldn't find it anywhere, so please let me know.
Best Regards,
Y.Ottey
Part Number: MSP432E401Y
Hello,
I am working on a project that requires the ability to take edge counts and time elapsed, and use that information to calculate capacitance. I'm tasked on the hardware side and have very limited knowledge on the software side, which will be done by a different person. That person is also fairly new to programming microcontrollers. I wanted to make sure that I have a board setup that has all the hardware capabilities needed for the software engineer to perform his task.
This current board revision has only one clock source, a 25 MHz main oscillator. Looking through the MSP432E4 technical reference manual (SLAU723), I believe the timer mode that best serves my needs is the input edge count mode. The plan then is to set the target number of edge counts in the match register, then trigger an event or interrupt when that target is reached that will take that edge count and the amount of time it took to get to that edge count. I see that the maximum input signal frequency is (1/4)*25 = 6.25 MHz. I have set up the sensing circuit in such a way then to operate within 800kHz - 1MHz at the capacitance range I am expecting. It also seems the timer can be set up as a 16 bit timer or as a 24 bit timer (without a pre-scaler) and so the resolution should be fine for my needs as well.
My question is with obtaining the time required to get to that edge count. Would I need another external oscillator to the microcontroller? Or would the software engineer just be able to use the 25 MHz clock to calculate the time elapsed to the closest 40ns (1 clock period)?
Thank you very much.
Part Number: TPS7A88
We need to test circuit boards with the TPS7A88 on board supplying +3.3V to the circuit. At the end of the test, we need to turn off power through the TPS7A88 and power the +3.3V bus using an external power supply. Our question is, is the output of the TPS7A88 protected from external power being applied to its output? No other power will be applied to the boards under test.
By the way, the two outputs are tied together in this circuit.
Thank you,
Dave
Part Number: AWR1642BOOST
Tool/software: Code Composer Studio
I have CCS Version: 9.2.0.00013
I have mmWave SDK 3.03.00.03
I'm working on the Driver Vital Signs lab in Automotive Toolsbox v:2.7.1
I imported vitalSigns_16xx_dss and vitalSigns_16xx_mss, and they are in Debug mode.
I rebuild the DSS project and get several errors.
I have searched the ti folder for the file rx_ch_bias_measure.h, but cannot find it. I wonder if I failed to install a dependency. I don't know if that's my only problem, or the first of several...
Thank you for your help!
chris
Here is the build log.
**** Clean-only build of configuration Debug for project vitalSigns_16xx_dss ****
"C:\\ti\\ccs920\\ccs\\utils\\bin\\gmake" -k -j 8 clean -O
DEL /F "vitalSigns_16xx_dss.hex" "configPkg\linker.cmd" "configPkg\compiler.opt" "vitalSigns_16xx_dss.xe674"
DEL /F "dss_config_edma_util.oe674" "dss_data_path.oe674" "dss_main.oe674" "dss_vitalSignsDemo_utilsFunc.oe674"
DEL /F "dss_config_edma_util.d" "dss_data_path.d" "dss_main.d" "dss_vitalSignsDemo_utilsFunc.d"
RMDIR /S/Q "configPkg\"
Could Not Find C:\Users\cschwarz\workspace_v9_2\vitalSigns_16xx_dss\Debug\vitalSigns_16xx_dss.hex
Could Not Find C:\Users\cschwarz\workspace_v9_2\vitalSigns_16xx_dss\Debug\vitalSigns_16xx_dss.xe674
Finished clean
**** Build Finished ****
**** Build of configuration Debug for project vitalSigns_16xx_dss ****
"C:\\ti\\ccs920\\ccs\\utils\\bin\\gmake" -k -j 8 all -O
rm -f C:/Users/cschwarz/workspace_v9_2/vitalSigns_16xx_dss/vitalSigns_16xx_dss.bin
makefile:189: recipe for target 'pre-build' failed
process_begin: CreateProcess(NULL, rm -f C:/Users/cschwarz/workspace_v9_2/vitalSigns_16xx_dss/vitalSigns_16xx_dss.bin, ...) failed.
gmake[1]: [pre-build] Error 2 (ignored)
Building file: "../dss_mmw.cfg"
Invoking: XDCtools
"C:/ti/xdctools_3_50_04_43_core/xs" --xdcpath="C:/ti/bios_6_73_01_01/packages;" xdc.tools.configuro -o configPkg -t ti.targets.elf.C674 -p ti.platforms.c6x:AWR16XX:false:600 -r debug -c "C:/ti/ccs920/ccs/tools/compiler/ti-cgt-c6000_8.3.4" "../dss_mmw.cfg"
making package.mak (because of package.bld) ...
generating interfaces for package configPkg (because package/package.xdc.inc is older than package.xdc) ...
configuring dss_mmw.xe674 from package/cfg/dss_mmw_pe674.cfg ...
generating custom ti.sysbios library makefile ...
Starting build of library sources ...
making C:/Users/cschwarz/workspace_v9_2/vitalSigns_16xx_dss/src/sysbios/sysbios.ae674 ...
gmake[1]: Entering directory `C:/Users/cschwarz/workspace_v9_2/vitalSigns_16xx_dss/src/sysbios'
gmake[1]: Nothing to be done for `all'.
gmake[1]: Leaving directory `C:/Users/cschwarz/workspace_v9_2/vitalSigns_16xx_dss/src/sysbios'
Build of libraries done.
cle674 package/cfg/dss_mmw_pe674.c ...
"package/cfg/dss_mmw_pe674.c", line 11212: warning: statement is unreachable
"package/cfg/dss_mmw_pe674.c", line 11575: warning: statement is unreachable
"package/cfg/dss_mmw_pe674.c", line 11857: warning: statement is unreachable
"package/cfg/dss_mmw_pe674.c", line 12100: warning: statement is unreachable
Finished building: "../dss_mmw.cfg"
Building file: "../dss_data_path.c"
Invoking: C6000 Compiler
"C:/ti/ccs920/ccs/tools/compiler/ti-cgt-c6000_8.3.4/bin/cl6x" -mv6740 --abi=eabi -O3 --include_path="C:/Users/cschwarz/workspace_v9_2/vitalSigns_16xx_dss" --include_path="C:/ti/mmwave_sdk_03_03_00_03/packages" --include_path="C:/ti/mathlib_c674x_3_1_2_1/packages" --include_path="C:/ti/dsplib_c64Px_3_4_0_0/packages/ti/dsplib/src/DSP_fft16x16/c64P" --include_path="C:/ti/dsplib_c64Px_3_4_0_0/packages/ti/dsplib/src/DSP_fft32x32/c64P" --include_path="C:/ti/ccs920/ccs/tools/compiler/ti-cgt-c6000_8.3.4/include" --define=SOC_XWR16XX --define=SUBSYS_DSS --define=DOWNLOAD_FROM_CCS --define=MMWAVE_L3RAM_SIZE=0xC0000 --define=DebugP_ASSERT_ENABLED -g --gcc --diag_warning=225 --diag_wrap=off --display_error_number --gen_func_subsections=on --obj_extension=.oe674 --preproc_with_compile --preproc_dependency="dss_data_path.d_raw" --cmd_file="configPkg/compiler.opt" "../dss_data_path.c"
>> Compilation failure
subdir_rules.mk:9: recipe for target 'dss_data_path.oe674' failed
"C:/ti/mmwave_sdk_03_03_00_03/packages/ti/demo/utils/mmwDemo_monitor.h", line 64: error #102: "MmwDemo_AnaMonitorCfg_t" has already been declared in the current scope
"C:/ti/mmwave_sdk_03_03_00_03/packages/ti/demo/utils/mmwDemo_monitor.h", line 71: error #258: invalid redeclaration of type name "MmwDemo_AnaMonitorCfg" (declared at line 313 of "C:/Users/cschwarz/workspace_v9_2/vitalSigns_16xx_dss/./common/mmw_config.h")
"../dss_data_path.c", line 105: fatal error #1965: cannot open source file "ti/demo/utils/rx_ch_bias_measure.h"
2 errors and 1 catastrophic error detected in the compilation of "../dss_data_path.c".
Compilation terminated.
gmake[1]: *** [dss_data_path.oe674] Error 1
Building file: "../dss_main.c"
Invoking: C6000 Compiler
"C:/ti/ccs920/ccs/tools/compiler/ti-cgt-c6000_8.3.4/bin/cl6x" -mv6740 --abi=eabi -O3 --include_path="C:/Users/cschwarz/workspace_v9_2/vitalSigns_16xx_dss" --include_path="C:/ti/mmwave_sdk_03_03_00_03/packages" --include_path="C:/ti/mathlib_c674x_3_1_2_1/packages" --include_path="C:/ti/dsplib_c64Px_3_4_0_0/packages/ti/dsplib/src/DSP_fft16x16/c64P" --include_path="C:/ti/dsplib_c64Px_3_4_0_0/packages/ti/dsplib/src/DSP_fft32x32/c64P" --include_path="C:/ti/ccs920/ccs/tools/compiler/ti-cgt-c6000_8.3.4/include" --define=SOC_XWR16XX --define=SUBSYS_DSS --define=DOWNLOAD_FROM_CCS --define=MMWAVE_L3RAM_SIZE=0xC0000 --define=DebugP_ASSERT_ENABLED -g --gcc --diag_warning=225 --diag_wrap=off --display_error_number --gen_func_subsections=on --obj_extension=.oe674 --preproc_with_compile --preproc_dependency="dss_main.d_raw" --cmd_file="configPkg/compiler.opt" "../dss_main.c"
>> Compilation failure
subdir_rules.mk:9: recipe for target 'dss_main.oe674' failed
"C:/ti/mmwave_sdk_03_03_00_03/packages/ti/demo/utils/mmwDemo_monitor.h", line 64: error #102: "MmwDemo_AnaMonitorCfg_t" has already been declared in the current scope
"C:/ti/mmwave_sdk_03_03_00_03/packages/ti/demo/utils/mmwDemo_monitor.h", line 71: error #258: invalid redeclaration of type name "MmwDemo_AnaMonitorCfg" (declared at line 313 of "C:/Users/cschwarz/workspace_v9_2/vitalSigns_16xx_dss/./common/mmw_config.h")
2 errors detected in the compilation of "../dss_main.c".
gmake[1]: *** [dss_main.oe674] Error 1
Building file: "../dss_config_edma_util.c"
Invoking: C6000 Compiler
"C:/ti/ccs920/ccs/tools/compiler/ti-cgt-c6000_8.3.4/bin/cl6x" -mv6740 --abi=eabi -O3 --include_path="C:/Users/cschwarz/workspace_v9_2/vitalSigns_16xx_dss" --include_path="C:/ti/mmwave_sdk_03_03_00_03/packages" --include_path="C:/ti/mathlib_c674x_3_1_2_1/packages" --include_path="C:/ti/dsplib_c64Px_3_4_0_0/packages/ti/dsplib/src/DSP_fft16x16/c64P" --include_path="C:/ti/dsplib_c64Px_3_4_0_0/packages/ti/dsplib/src/DSP_fft32x32/c64P" --include_path="C:/ti/ccs920/ccs/tools/compiler/ti-cgt-c6000_8.3.4/include" --define=SOC_XWR16XX --define=SUBSYS_DSS --define=DOWNLOAD_FROM_CCS --define=MMWAVE_L3RAM_SIZE=0xC0000 --define=DebugP_ASSERT_ENABLED -g --gcc --diag_warning=225 --diag_wrap=off --display_error_number --gen_func_subsections=on --obj_extension=.oe674 --preproc_with_compile --preproc_dependency="dss_config_edma_util.d_raw" --cmd_file="configPkg/compiler.opt" "../dss_config_edma_util.c"
Finished building: "../dss_config_edma_util.c"
Building file: "../dss_vitalSignsDemo_utilsFunc.c"
Invoking: C6000 Compiler
"C:/ti/ccs920/ccs/tools/compiler/ti-cgt-c6000_8.3.4/bin/cl6x" -mv6740 --abi=eabi -O3 --include_path="C:/Users/cschwarz/workspace_v9_2/vitalSigns_16xx_dss" --include_path="C:/ti/mmwave_sdk_03_03_00_03/packages" --include_path="C:/ti/mathlib_c674x_3_1_2_1/packages" --include_path="C:/ti/dsplib_c64Px_3_4_0_0/packages/ti/dsplib/src/DSP_fft16x16/c64P" --include_path="C:/ti/dsplib_c64Px_3_4_0_0/packages/ti/dsplib/src/DSP_fft32x32/c64P" --include_path="C:/ti/ccs920/ccs/tools/compiler/ti-cgt-c6000_8.3.4/include" --define=SOC_XWR16XX --define=SUBSYS_DSS --define=DOWNLOAD_FROM_CCS --define=MMWAVE_L3RAM_SIZE=0xC0000 --define=DebugP_ASSERT_ENABLED -g --gcc --diag_warning=225 --diag_wrap=off --display_error_number --gen_func_subsections=on --obj_extension=.oe674 --preproc_with_compile --preproc_dependency="dss_vitalSignsDemo_utilsFunc.d_raw" --cmd_file="configPkg/compiler.opt" "../dss_vitalSignsDemo_utilsFunc.c"
gmake[1]: Target 'main-build' not remade because of errors.
gmake: *** [all] Error 2
Finished building: "../dss_vitalSignsDemo_utilsFunc.c"
makefile:155: recipe for target 'all' failed
**** Build Finished ****
Part Number: TMS570LC4357
The LC43x Technical Reference Manual, section 22.2.6.3.2, says to consult the datasheet for the value of t_d(PU-ADV) -- I suspect this is a typo for t_d(PU-ADC) -- the delay required between ADC powerup and the state of a conversion. Unless it's really well hidden somewhere :-), the current TMS570LC4357 datasheet (rev C) gives no value for this, and in fact is completely silent on the matter.
Part Number: THS6212
Dear Sir,
We would like buying the KGD THS6212YS to run the system-in-package with our chip. How can we start with TI?
By the way, would you please providing the information about the bonding pad thickness of KGD THS6212YS?
Thanks!
Regards,
Ryan
Part Number: MSP430FR6047
Hello,
I'm working on custom PCB for msp430fr6047 and I would like to do some debugging by the GUI.
I have HID bridge for captivate but when I connect the bridge and the PCB the GUI says "HID Bridge is connected - waiting for device"
I'm sure that the connections are good.
so anyone has an idea.
Part Number: TMS570LS0432
Tool/software: Code Composer Studio
Hi,
I am trying to run the example fft program. I was able to build it but the fft coefficients don't match the coefficients that I get from python. Could you please help me understand why this would be happening?
Thanks,
Aditi
Part Number: PGA460
Hello, I'm planning on using a PGA460 to drive the following transducer:
http://www.globalmarket.com/product-info/dual-frequency-ultrasonic-sensor-8249174.html
The idea is to use the transducer underwater and measure the depth of a tank (about 5m). Do you think this transducer and PGA460 (or maybe TDC1000) are suitable for the project? If not, what transducer would you recommend?
Thanks,
Lucas
Part Number: TPS23881
What is the best method to use discrete control signals to enable/disable port power? We have a single port application and need to enable or disable the PSE output power with a discrete control signal. I have been able to perform the power on/off control using the \RESET input. Pulling it low definitely turns off the port power. Is that the best method or is there a better way? Appreciate your help.
