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

AM5726: AM57x PET tool DDR termination

July 12, 2018, 7:00 am
$
0
0

Part Number:AM5726

Hi Champs,

I have quetion about this AM572x PET

Q1) Does this DDR power consumption calculation include termination ? If yes, could you please tell us this resistance number ?

↧
Search

LMK03328: Fixed phase sync between input and output

July 12, 2018, 7:03 am
$
0
0

Part Number:LMK03328

Dear Team,

ist it possible to have a fixed phase relation between the input of the LMK03328 and the output? If yes - how can I set this?

Thanks for your help.

Dominic

↧
↧

MSP430F6779: SD24 sample result

July 12, 2018, 7:04 am
$
0
0

Part Number:MSP430F6779

Hi All

We input voltage 0.455V into SD24 ADC pin, and set internal reference 1.2V, we expect the ADC value should be 0.455*（2^24-1）/1.2=6361360

However we try to read ADC result by several times and found result has much difference as below, do you think if any possible reason?

6813306                6791826                        6596934

6926496                6953734                        6166032

7956268                7248024                        6384816

7532230                7626950                        6673594

8247180                8416324                        7396284

7175816                7252200                        6155190

↧

CC3220SF-LAUNCHXL: Data received over SPI incorrectly read

July 12, 2018, 7:07 am
$
0
0

Part Number:CC3220SF-LAUNCHXL

Hi

I have the same issue as the related poster, where when CPOL = 0 and CPHA = 1, incorrect data is being read via the TI SPI drivers.

Regards

Meenal

↧

TPS53353: Ripple injection

July 12, 2018, 7:11 am
$
0
0

Part Number:TPS53353

I have two DC/DC converters based on TPS53353. They both work set to 3,6V, both are identical, same components.

No I am wondering why the ramp(lower picture) which I inject to the VFB pin is a little different in one converter, they both are around 50mV. 

Question is why: one sawtooth is let say  not  "ideal"? 

They are both with noise and spikes I see but why the ramp is not continuous, we can observe a big drop around the peak.
I reduced the amplitude even to 30mV, so that's not the reason. The first picture is with a good Ramp

↧
↧

LM2904: Op AmpDesign

July 12, 2018, 7:14 am
↧

UCC256303: Fullbridge LLC pri. wire low side 2xMOSFETs drive

July 12, 2018, 7:16 am
$
0
0

Part Number:UCC256303

Hi all,

I want to configure the Full Bridge LLC by using one UCC256303.

How to connect to drive pri.wire low side 2x MOSFETs?

In case of using drive transformer, how about below.

For high side mosfet drive trans connection :   HO-HS(pri.) - Gate-Source.

For low side mosfet drive trans connection :   LO-GND(pri.) - Gate-Source.

Is this OK ?  Any additional caution point?

↧

CC2564: CC2564, CC2564B

July 12, 2018, 7:17 am
$
0
0

Part Number:CC2564

Bluetooth SIG is deprecating pre-4.2 versions from January 2019.

I have 2 questions:

  1. Are CC2564 and CC2564B dual mode controllers designed to support Bluetooth version v4.2 ?
  2. If answer to Question 1 is yes, does TI have any plans to re-certify controllers to v4.2 ?

↧
Search

BQ24650: Charge termination discussion

July 12, 2018, 7:19 am
$
0
0

Part Number:BQ24650

Hi, 

I wonder what is the difference between enable and disable charge termination. 

I want to confirm if this is like what my understanding below: 

enable:  the charging current become 0 after battery reaching the termination voltage, and charging recover when meet the condition mention in datasheet.

disable: charger always under the CV mode when the battery is full or almost full, the charger never stop switching

The summary may be: enable termination will help with the efficiency of operation, reduce the switching loss under long time CV operation.

Please help to comment if there are other difference or consideration for choosing to termination or not. 

Thanks for your help.

↧
↧

Compiler/TMS320F28069M: Importing PFUNC library function from 240x to 280x (spra380)

July 12, 2018, 7:23 am
$
0
0

Part Number:TMS320F28069M

Tool/software: TI C/C++ Compiler

Hello,

I am recompiling some legacy code base from a 240x DSP to a F28069M.  The code uses the PFUNC_readWord() function from the pfunc lib described in spra380.

The pfunc.lib library cannot be imported and the asm source cannot be compiled as written.  

Question is what is the fastest approach to getting an executable. 

 Is this function call even needed anymore?  

If so, is there a function that could be used to replace?  Should the asm code be rewritten for the 280x?

Thanks,

Kevin Hobbs

Bergey WindPower

↧

IWR1443BOOST: Cannot find Out OF Box Demo MSS binary Image

July 12, 2018, 7:24 am
$
0
0

Part Number:IWR1443BOOST

.

Thank you. This forum has been very helpful to me in the past.  I am trying to reload the "out of box demo" software back on my IWR1443BOOST sdk.  In the mmwave_sdk_users guide the instructions are to flash images for the BSS & MSS. I was able to find the bin file for the BSS image but, not the MSS. The instructions from the guide are:

For demo mode, choose from one of these binary files from the SDK:

mmwave_sdk_<ver>\packages\ti\demo\xwr14xx\mmw\xwr14xx_mmw_demo_mss.bin

mmwave_sdk_<ver>\packages\ti\demo\xwr14xx\capture\xwr14xx_capture_demo_mss.bin

The problem is that I cannot find either demo_ mss binary file. I tried redownloading and installing the mmWave Device Firmware Package (DFP) but, still cannot find the files. Where can I get these images? Can you send them to me?

Thanks again

Joe

↧

MSP-EXP432P401R: Capacitive Touch via GPIO

July 12, 2018, 7:25 am
$
0
0

Part Number:MSP-EXP432P401R

Hi,

I am an applications intern at TI and I am designing a BoosterPack that utilizes the MSP-EXP432P401R Launchpad. I made a capacitive touch button on my BP that is exposed copper on the top layer and functions as the bottom plate of a capacitor (and your finger is the top plate).  I have this button connected to a GPIO pin to the LaunchPad.

However, to make this capacitive button function by using frequency sensing, I need to attach it in parallel to the crystal oscillator to form a circuit. That way when you finger touches the button, it would change the oscillation frequency and the MSP432 can detect a frequency change as an input.

I cannot find any documentation online that goes through how to connect my button via GPIO to the external crystal oscillator.

Can you point me in the right direction?

Thanks.

Juliana Rolandelli

↧

DS100DF410: Calculating HEO and VEO

July 12, 2018, 7:25 am
$
0
0

Part Number:DS100DF410

Hi,

One of my customer is usng DS100DF410 and are in the process of finalizing the SERDES co-effcient.

They are planning to use the EOM monitor to finalize the co-efficient.  When we access the HEO and VEO values through register 0x27 and 0x28, It gives single byte value which is expected. Now , how do we convert  VEO and HEO to mV and UI.

Also we want to try the full eye (64*64) does it need any external controller to enable the measurement or it can be printed in the CLI itself?

Regards,

Praveen

 

↧
↧

IWR1642BOOST: IWR1443BOOST and IWR1642BOOST

July 12, 2018, 7:26 am
$
0
0

Part Number:IWR1642BOOST

Hello TI Technical Team,

We want to integrate our SDK with people counting hardware xWR1443 EVM and xWR1642 EVM for sending calculated people data to the cloud.
We have understood from technical document mentioned on TI website: We need to download Code compress studio to install firmware on the device and we can see data on mmWave Studio software also we can visualize data using Matlab.
Are we right?

Questions:
1) How can we take calculated people data?
2) Can we integrate our SDK on your mmWave Studio software for a device to cloud communication?
3)Can we parse UART stream with annotation of Frame Header and TLVs? or It will only parse by your software mmWave Studio?
4) Can you guide how we can send data from xWR1443 EVM and xWR1642 EVM to Azure IoT hub?

Regards,
Paras

↧

OPT8241-CDK-EVM: The device connects to Voxel Viewer but no image appears

July 12, 2018, 7:26 am
$
0
0

Part Number:OPT8241-CDK-EVM

The device connects to Voxel Viewer but I cannot get an image to appear. It was working perfectly fine, but an hour later refused to work. I tried a firmware update and that did not help.

Below is a copy of the errors/warnings

Errors/Warnings

Voxel Viewer v0.9.10

Texas Instruments Inc.

INFO: ParameterDMLParser: Found register map with name 'OPT9221' (vPG1P0)

INFO: MainConfigurationFile: Reading from local copy of hardware configuration data

INFO: Data2DCodec: Original number of 8-bit offsets = 1005

INFO: Data2DCodec: Number of invalid pixels in original data = 0

INFO: Data2DCodec: Current number of 8-bit offsets = 1005

ERROR: DepthCamera: Could not set the camera profile to '79'

ERROR: DepthCamera:Could not get value for parameter TintinCDKCamera(0::0451:9105::10977221099732).vco_freq1

ERROR: DepthCamera: Failed to update value for parameter 'mod_freq1'

ERROR: DepthCamera:Could not get value for parameter TintinCDKCamera(0::0451:9105::10977221099732).vco_freq2

ERROR: DepthCamera: Failed to update value for parameter 'mod_freq2'

ERROR: DepthCamera: Failed to update value for parameter 'sysclk_in_freq'

ERROR: DepthCamera: Failed to update value for parameter 'quad_cnt_max'

ERROR: DepthCamera: Failed to update value for parameter 'vco_freq2'

ERROR: DepthCamera: Failed to update value for parameter 'vco_freq1'

ERROR: DepthCamera:Could not get value for parameter TintinCDKCamera(0::0451:9105::10977221099732).vco_freq1

ERROR: DepthCamera: Failed to update value for parameter 'mod_freq1'

ERROR: DepthCamera:Could not get value for parameter TintinCDKCamera(0::0451:9105::10977221099732).vco_freq2

ERROR: DepthCamera: Failed to update value for parameter 'mod_freq2'

ERROR: DepthCamera: Failed to update value for parameter 'sysclk_in_freq'

ERROR: DepthCamera: Failed to update value for parameter 'quad_cnt_max'

ERROR: DepthCamera: Failed to update value for parameter 'vco_freq2'

ERROR: DepthCamera: Failed to update value for parameter 'vco_freq1'

ERROR: CameraSystem: Could not refresh parameters for TintinCDKCamera(0::0451:9105::10977221099732).

ERROR: DepthCamera:Could not get value for parameter TintinCDKCamera(0::0451:9105::10977221099732).vco_freq1Traceback (most recent call last):

File "D:\voxelviewerbitbucket\voxelviewer-devel\build\VoxelViewer\out00-PYZ.pyz\PyVoxelViewer.docks.FrequentlyUsedParametersDockWidget", line 93, in updateView

File "D:\voxelviewerbitbucket\voxelviewer-devel\build\VoxelViewer\out00-PYZ.pyz\PyVoxelViewer.docks.FrequentlyUsedParametersDockWidget", line 46, in showParam

File "D:\voxelviewerbitbucket\voxelviewer-devel\build\VoxelViewer\out00-PYZ.pyz\PyVoxelViewer.views.ParameterHandlerROI", line 127, in __init__

File "D:\voxelviewerbitbucket\voxelviewer-devel\build\VoxelViewer\out00-PYZ.pyz\PyVoxelViewer.views.ParameterHandlerROI", line 259, in init

File "D:\voxelviewerbitbucket\voxelviewer-devel\build\VoxelViewer\out00-PYZ.pyz\PyVoxelViewer.views.XYSpinBox", line 35, in setRange

OverflowError

ERROR: ToFCameraBase: Could not get current frame rate

INFO: ToFCameraBase: Starting with 352x352@0fps

ERROR: TintinCDKCamera: Could not get current frame rate

INFO: CameraSystem: DepthCamera for 0::0451:9105::10977221099732 was already created. Returning it.

ERROR: DepthCamera:Could not get value for parameter TintinCDKCamera(0::0451:9105::10977221099732).vco_freq1

ERROR: DepthCamera: Failed to update value for parameter 'mod_freq1'

ERROR: DepthCamera:Could not get value for parameter TintinCDKCamera(0::0451:9105::10977221099732).vco_freq2

ERROR: DepthCamera: Failed to update value for parameter 'mod_freq2'

ERROR: DepthCamera: Failed to update value for parameter 'sysclk_in_freq'

ERROR: DepthCamera: Failed to update value for parameter 'quad_cnt_max'

ERROR: DepthCamera: Failed to update value for parameter 'vco_freq2'

ERROR: DepthCamera: Failed to update value for parameter 'vco_freq1'

ERROR: CameraSystem: Could not refresh parameters for TintinCDKCamera(0::0451:9105::10977221099732).

ERROR: DepthCamera:Could not get value for parameter TintinCDKCamera(0::0451:9105::10977221099732).vco_freq1Traceback (most recent call last):

File "D:\voxelviewerbitbucket\voxelviewer-devel\build\VoxelViewer\out00-PYZ.pyz\PyVoxelViewer.docks.FrequentlyUsedParametersDockWidget", line 93, in updateView

File "D:\voxelviewerbitbucket\voxelviewer-devel\build\VoxelViewer\out00-PYZ.pyz\PyVoxelViewer.docks.FrequentlyUsedParametersDockWidget", line 46, in showParam

File "D:\voxelviewerbitbucket\voxelviewer-devel\build\VoxelViewer\out00-PYZ.pyz\PyVoxelViewer.views.ParameterHandlerROI", line 127, in __init__

File "D:\voxelviewerbitbucket\voxelviewer-devel\build\VoxelViewer\out00-PYZ.pyz\PyVoxelViewer.views.ParameterHandlerROI", line 259, in init

File "D:\voxelviewerbitbucket\voxelviewer-devel\build\VoxelViewer\out00-PYZ.pyz\PyVoxelViewer.views.XYSpinBox", line 35, in setRange

OverflowError

ERROR: ToFCameraBase: Could not get current frame rate

INFO: ToFCameraBase: Starting with 352x352@0fps

ERROR: TintinCDKCamera: Could not get current frame rate

↧
Search

UCC256303: Fullbridge LLC pri. wire low side 2xMOSFETs drive

July 12, 2018, 7:26 am
$
0
0

Part Number:UCC256303

Hi all,

I want to configure the Full Bridge LLC by using one UCC256303.

How to connect to drive pri.wire low side 2x MOSFETs?

In case of using two Iso Gate Drivers UCC5310, how about below.

For high side mosfet drive trans connection :  Rvcc-Vcc1, GND to GND1, LO to IN+   and  Vcc2- Drain, Vout and CLAMP- Gate, VEE2- Source(SW node)

For low side mosfet drive trans connection : HB-Vcc1, HS to GND1, HO to IN+   and  Vcc2- Drain, Vout and CLAMP- Gate, VEE2- Source(GND)

Is this OK ?  Any additional caution point?

↧

PGA411-Q1: Is there a way to get around a SPI Error causing the PGA411 to fault?

July 12, 2018, 7:30 am
$
0
0

Part Number:PGA411-Q1

I could not find the minimum time to hold the fault reset pin low to reset the faults. What is the minimum time to hold this pin low?

↧
↧

CCS: Need Motorware 1_01_00_16 software

July 12, 2018, 7:56 am
$
0
0

Tool/software: Code Composer Studio

Hello, I am re-posting because I lost communications with my previous thread before any resolution was achieved.  

I need the Motorware version 1_01_00_16 software but currently only v18 is available for download.  Our interfaces to our motor controllers (from a separate main controller) were built around the v16 release of the software (by an engineer who is no longer available). As such, we have legacy code that only works with the rest of the v16 software. Specifically, we use lab02c and a heavily modified version of lab05b. However, I would like to do some of the other labs (all of them really) to improve our performance, better understand how to tune our motors for continued use of our motor apparatus without changing ALL of our existing interface software and hardware. When I try and use the v18 release, I can compile it and follow the instructions but it does not work with our hardware. The motor does not function properly. I don't know more specifically what is failing but I do know that release 16 works, where 18 fails. I don't have the details of what in that pipeline are broken, nor can I contact the engineer who built this originally with the v16 software. So, I'm trying to pick this up but I need the rest of the v16 software to move forward.

Specifically, I need the CCS projects and lab_xx_x.c files.  I have the underlying v16 motor controller files. 

Thank you kindly, 

  - Dave M

↧

CC1310: Problems erasing flash

July 12, 2018, 7:56 am
$
0
0

Part Number:CC1310

Hi,

I am trying to store some app-related info into a flash sector at address 0x1e000 which is 8k from the end of the flash region.  I am testing on

the launchpad eval board using CCS v8.  I am running with the TI-RTOS and am disabling interrupts so that no interrupt handlers run from

flash during the operation.

The code I am using is (using hard-coded address for testing):

printf("sector size: %d protect: %d\n", FlashSectorSizeGet(), FlashProtectionGet((uint32_t)0x1e000));
IntMasterDisable();
uint32_t ret = FlashSectorErase((uint32_t)0x1e000);
printf("FlashSectorErase() returned %d\n", ret);
dumpFlash((uint8_t*)0x1e000);
ret = FlashProgram((uint8_t*)&config, 0x1e000, sizeof(config));
printf("FlashProgram() returned %d\n", ret);
IntMasterEnable();
dumpFlash((uint8_t*)0x1e000);

The output I see is:

00 00 01 00 00 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 3c 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 9d 77 e8 05 ff ff
sector size: 4096 protect: 0
FlashSectorErase() returned 0
00 00 01 00 00 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 3c 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 9d 77 e8 05 ff ff
FlashProgram() returned 0
00 00 01 00 00 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 3c 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 9d 77 e8 05 ff ff

The data to be written to flash is not what is being printed.  What I don't understand is why the values in flash are not 0xff after the erase operation.

Obviously since the erase operation did not work the write operation also failed.

Any ideas?

Victor

↧

CCS: error #10056

July 12, 2018, 7:59 am
$
0
0

Tool/software: Code Composer Studio

Hi: Please help to check what is issue when i compiler the code. 

error #10056: symbol "vApplicationStackOverflowHook" redefined: first defined in "./main.obj"; redefined in "./main_Org.obj"
error #10056: symbol "vApplicationIdleHook" redefined: first defined in "./main.obj"; redefined in "./main_Org.obj"
error #10056: symbol "main" redefined: first defined in "./main.obj"; redefined in "./main_Org.obj"
error #10056: symbol "vApplicationMallocFailedHook" redefined: first defined in "./main.obj"; redefined in "./main_Org.obj"
error #10056: symbol "vAssertCalled" redefined: first defined in "./main.obj"; redefined in "./main_Org.obj"

undefined first referenced
symbol in file
--------- ----------------
GPIO_IF_Get ./cc3200_ds18b20.obj
GPIO_IF_GetPortNPin ./cc3200_ds18b20.obj
GPIO_IF_Set ./cc3200_ds18b20.obj

error #10234-D: unresolved symbols remain
error #10010: errors encountered during linking; "freertos_demo.out" not built

>> Compilation failure
makefile:147: recipe for target 'freertos_demo.out' failed
gmake: *** [freertos_demo.out] Error 1

↧
Viewing all 262198 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>