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

LDC0851: Proximity sensing with distance bigger than coil diameter

May 25, 2017, 9:27 am
$
0
0

Part Number:LDC0851

Hi team,

I have a customer using inductive sensing for proximity switch and interested in our LDC0851.

They need to sense up to 40mm distance, but the max coil diameter is < 40mm (range from 8mm to 40mm). They are testing with our EVM and get < 8mm distance.

In our datasheet, it is recommended that the sensing distance is up to 40% of the coil diameter. Could we increase this to beyond 100% of the coil diameter? Will using multi-layer coil help? And any guide for designing multi-layer coil (they prefer discrete coil than using the PCB).

Is it very critical for the reference coil to be identical to the sensing coil? what is the best positioning for the reference coil and sensing coil?

assuming the reference coil and the sensing coil is identical, what will be the tolerance change with temperature (from -40C to 100C). They need to achieve +/-10% tolerance with all variable (including the tolerance of the coil).

↧
Search

LED Driver choice for outdoor application

May 25, 2017, 9:36 am
$
0
0

I need to make a 7 segment digit for outdoor applications. We wanna to use a LED driver to control the brightness and also report us fails as open circuit.

Each segment need to have 28 LEDs. Have anyone a driver to indicate?

We was concern initialy by multiplexing may be a problem in outdoor but as 1 digit uses 196 LEDs, if we multiplex fast enough it will not be a problem.

↧
↧

Compiler/TMS320F2810: Is there any latest compiler built (CCS7.1) libraries available for Flash2810_API_V210.lib and IQmath.lib

May 25, 2017, 9:47 am
$
0
0

Part Number:TMS320F2810

Tool/software: TI C/C++ Compiler

  • is there any  latest compiler built (CCS7.1)  libraries available  for Flash2810_API_V210.lib and  IQmath.lib
  • already i had looked into controlSUITE
  • I need it for 

               1.Flash2810_API_V210.lib   and

               2.IQmath.lib   : v160  

Thanks

Eshwaran J

↧

TMS320C6747: memory analysis of McASP pdk example of PSDK3.3.

May 25, 2017, 9:48 am
$
0
0

Part Number:TMS320C6747

Dear Champs,

I created pdkproject in pdk_omapl13x_1_0_0 directory and build it using CCSv7.1.0, and am analyzing its memory usage now to estimate final memory size of customer's application.

I found total memory usage of this example was 514KB(525,835 Bytes), but can not select exactly which component should be used and what is expected memory size except application code.

And also customer requested to explain each component. I got below information from map file.

Could you please let me know which components will be used in real product in normal?

Could you please your estimated memory size of customer's system except application?

Especially I want to know what is cfg(audiosample_pe674.oe674) and if this will be needed in real product.

Below table is memory size of each module.

attached map file for reference.

(Please visit the site to view this file)

Thanks and Best Regards,

SI.

Module Memory size(code/ro/rw)production
.\  
aic31.obj          
audioSample_io.obj 
aic3106_if.obj     
mcasp_soc.obj      
codec_if.obj       
I2C_soc.obj        
audioSample_main.obj
mcasp_cfg.obj      
audio_evmInit.obj		                                                                    16,879                                                 16,879
\pdk_omapl13x_1_0_0\packages\MyExampleProjects\MCASP_Audio_evmOMAPL137_c674xExampleProject\Release\configPkg\package\cfg\  
audiosample_pe674.oe674                                                                 230,678 
\bios_6_46_04_53\packages\ti\targets\rts6000\lib\boot.ae674  
autoinit.oe674
boot.oe674   		                                                                          480                                                       480
\bios_6_46_04_53\packages\ti\targets\rts6000\lib\ti.targets.rts6000.ae674  
System.oe674    
Text.oe674      
Error.oe674     
Core-mem.oe674  
Startup.oe674   
Memory.oe674    
Core-smem.oe674 
LoggerBuf.oe674 
SysStd.oe674    
Assert.oe674    
Core-label.oe674
Core-params.oe674
SysMin.oe674    
Gate.oe674      
Registry.oe674  
xdc_noinit.oe674 		                                                                      9,729 
\edma3_lld_2_12_03_27\packages\ti\sdo\edma3\drv\lib\674\debug\edma3_lld_drv.ae674  
edma3_drv_init.oe674
edma3_drv_basic.oe674
edma3_drv_adv.oe674  		                                                                    69,758                                                 69,758
\edma3_lld_2_12_03_27\packages\ti\sdo\edma3\drv\sample\lib\omapl137-evm\674\debug\edma3_lld_drv_sample.ae674  
sample_omapl137_cfg.oe674   
sample_cs.oe674             
sample_omapl137_int_reg.oe674
sample_init.oe674		                                                                      4,012 
\edma3_lld_2_12_03_27\packages\ti\sdo\edma3\rm\lib\omapl137-evm\674\debug\edma3_lld_rm.ae674  
edma3resmgr.oe674      
edma3_rm_gbl_data.oe674
edma3_omapl137_cfg.oe674		                                                                    77,674 
\pdk_omapl13x_1_0_0\packages\ti\board\lib\evmOMAPL137\c674\release\ti.board.ae674  
evmOMAPL137_clock.oe674  
evmOMAPL137_pinmux.oe674 
evmOMAPL137_pll.oe674    
evmOMAPL137.oe674        
evmOMAPL137_ddr.oe674    
evmOMAPL137_lld_init.oe674		                                                                      2,560                                                   2,560
\pdk_omapl13x_1_0_0\packages\ti\csl\lib\omapl137\c674\release\ti.csl.ae674  
mcasp.oe674   
uart.oe674    
i2c.oe674     
csl_chip.oe674 		                                                                      4,448                                                   4,448
\pdk_omapl13x_1_0_0\packages\ti\drv\i2c\lib\omapl137\c674\release\ti.drv.i2c.ae674  
I2C_v0.oe674
I2C_drv.oe674		                                                                      6,824                                                   6,824
\pdk_omapl13x_1_0_0\packages\ti\drv\mcasp\example\evmOMAPL137\c674\bios\src\sysbios\sysbios.ae674  
BIOS.obj               
c64p_Hwi_disp_always.obj
c64p_Exception_asm.obj 
c62_TaskSupport_asm.obj
c64p_Hwi_asm_switch.obj
c64p_Hwi_asm.obj		                                                                    34,984                                                 34,984
\pdk_omapl13x_1_0_0\packages\ti\drv\mcasp\lib\omapl137\c674\release\ti.drv.mcasp.ae674  
mcasp_drv.oe674 
mcasp_edma.oe674
mcasp_ioctl.oe674		                                                                    34,750                                                 34,750
\pdk_omapl13x_1_0_0\packages\ti\drv\uart\lib\omapl137\c674\release\ti.drv.uart.ae674  
UART_v0.oe674  
UART_stdio.oe674
UART_soc.oe674 
UART_drv.oe674 		                                                                    10,808                                                 10,808
\pdk_omapl13x_1_0_0\packages\ti\osal\lib\tirtos\omapl137\c674\release\ti.osal.ae674  
RegisterIntr_tirtos.oe674 
EventCombinerP_tirtos.oe674
SemaphoreP_tirtos.oe674   
HwiP_tirtos.oe674         
Utils_tirtos.oe674        
MuxIntcP_tirtos.oe674     
Queue_tirtos.oe674        
CacheP_tirtos.oe674		                                                                      3,316                                                   3,316
\ti-cgt-c6000_8.1.3\lib\rts6740_elf.lib  
trgdrv.obj              
lowlev.obj              
fputs.obj               
defs.obj                
imath64.obj             
fputc.obj               
setvbuf.obj             
trgmsg.obj              
fflush.obj              
fclose.obj              
copy_decompress_rle.obj 
fseek.obj               
_io_perm.obj            
exit.obj                
divi.obj                
llshift.obj             
memset.obj              
divu.obj                
tls.obj                 
fopen.obj               
memcpy64.obj            
remu.obj                
_lock.obj               
args_main.obj           
assert.obj              
strasg.obj              
copy_decompress_none.obj
copy_zero_init.obj       		                                                                    10,776 
   
stack                                                                      4,096                                                   4,096
linker generated                                                                      4,063                                                   4,063
total                                                                 525,835                                              192,966
↧

3DLP Light sources

May 25, 2017, 9:49 am
$
0
0

If I want to use 3 light sources (1R, 1G, 1B) in 3DLP application, how I can merge them into output lens?

↧
↧

OPA1612: Using as headphone driver

May 25, 2017, 9:54 am
$
0
0

Part Number:OPA1612

Hello,

I am considering the OPA1612 as a headphone driver replacement for JRC2114.

In note slyt630.pdf (sorry, pasting the address makes a huge link) you use a ~50 ohm isolation resistor.  Is this necessary when using the 1612 as a headphone driver? The headphone output section of my DAC has a 220R in series with the output.  Should I leave it as is or is it a good idea to bridge it?  I would like to be able to drive any impedance headphones.

Thanks!

David

↧

Compiler/TMS320F2810: While migrating the project to CCS7.1 from CCS3.3 , I am getting "error #10099-D: program will not fit into available memory" Linker Error.

May 25, 2017, 9:56 am
$
0
0

Part Number:TMS320F2810

Tool/software: TI C/C++ Compiler

While migrating the project to CCS7.1 from CCS3.3 , I am getting"error #10099-D: program will not fit into available memory" Linker Error.

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

"f2810_flash.cmd", line 102: error #10099-D: program will not fit into available memory.  run placement with alignment/blocking fails for section


   "SciaRegsFile" size 0x10 page 1.  Available memory ranges: SCIA    size: 0x10   unused: 0x10   max hole: 0x10
   SciaRegsFile      : > SCIA,        PAGE = 1
   
"f2810_flash.cmd", line 103: error #10099-D: program will not fit into  available memory.  run placement with alignment/blocking fails for section


   "ScibRegsFile" size 0x10 page 1.  Available memory ranges: SCIB  size: 0x1f unused: 0x1f max hole: 0x1f
   ScibRegsFile      : > SCIB,        PAGE = 1

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

.cmd file

PAGE 1: /* Data Memory */
  /* RAM/FLASH/OTP blocks can be moved to PAGE0 for program allocation  */
  RAMM0M1     : origin = 0x000000, length = 0x000800
  RAMH0       : origin = 0x3F8000, length = 0x002000
  CSM_PWL     : origin = 0x3F7FF8, length = 0x000008


  SCIA        : origin = 0x007050, length = 0x000040    /* SCI-A registers */
  SCIB        : origin = 0x007750, length = 0x000040    /* SCI-B registers */


 }

------ If the length is increased to 40 in the .cmd file the linker error goes away and

------ in the map file size remains same at  0x10  and   unused: 0x30  for SCIA and SCIB

MAP File 

  • The Map file shows  origin as 00007080  instead of  00007050 for _SciaRegs 
  • The Map file shows  origin as 00007780  instead of  00007750 for _ScibRegs
  • when ofd2000 --obj_display=none,sections ls.out was executed the memory align shows 64
  •  
  • the align section information shows  64 
  • OBJECT FILE: ls.out
  • Section Information

id       name      page   load addr          run addr        size     align   alloc
-- ---- ---- --------- -------- ---- ----- -----

10 SciaRegsFile 1    0x00007080   0x00007080     0x10     64         Y
11 ScibRegsFile 1    0x00007780    0x00007780    0x10      64        Y

 

Please help to resolve

 

Eshwaran

↧

CC1310: Migrating from proprietary RF (TI-RTOS 2.21) to SDK release

May 25, 2017, 10:04 am
$
0
0

Part Number:CC1310

Hi Team,

The firmware that I have designed so far is using the Proprietary RF TI-RTOS 2.21 SDK.

However, now since I want to use the Frequency Hoping concept I will have to use the SimpleLink CC13xx SDK.

I went through the document Migration guide "file:///C:/ti/simplelink_cc13x0_sdk_1_30_00_06/docs/ti154stack/ti154stack-sdg/ti154stack-sdg/migration_guide/Migration_Guide.html"

where is provides a link "

However, if you see in this link there is no documentation on how to migrate from TI-RTOS 2.21 Proprietary RF to SimpleLink.

Request to look into this issue.

Thank you

Vikram

↧
Search

UC1825: Single Ended Configuration of UC1825

May 25, 2017, 10:12 am
↧
↧

LM25066A: Power Up Sequence

May 25, 2017, 10:12 am
$
0
0

Part Number:LM25066A

Referencing the datasheet, pages 20-21 and Figure 32, regarding the Power Up Sequence:

In Figure 32, there is a time period between t1 (Insertion Time) and t2 (In Rush Limiting), where the FET gate is charged with the 22uA source, and the text reads "the GATE pin then switches on Q1".

I have the following questions with regard to this time:

  1. What is meant by Q1 switches on? Is it when the Miller capacitance is fully charged? Is it when drain current starts to flow?
  2. Is current limiting / power limiting happening during this time?
  3. Does the fault timer start at the end of t1 or the beginning of t2?  Figure 32 shows that the fault timer starts at the beginning of t2, but just want to be sure.
  4. If the fault timer starts at the beginning of t2, how does the LM25066A know that Q1 is turned on and that it should start the fault timer for t2?

Thank you,

Chris Arntzen

↧

IWR1443BOOST: What is the purpose of two unused RX antenna in the IWR1443 evaluation board?

May 25, 2017, 10:23 am
$
0
0

Part Number:IWR1443BOOST

Hello everyone

On our IWR1443 board, instead of 4 Rx antenna, there are 6 RX antenna, 2 of them are grounded. Can you tell me what is the purpose of those 2 unused antenna? Is it for the mitigate the edge effect for the array?

Regards

Peter.

↧

CC1101CC1190EMK868: CC1101CC1190EMK868

May 25, 2017, 10:31 am
$
0
0

Part Number:CC1101CC1190EMK868

Can code for the CC1101RTK be used for the above mentioned board?

I'm new to these boards and find it difficult getting explicit documentation and information to help with my project. I feel the boards may have different internal or functional configurations.

Any help would be appreciated.

↧

AM5716: DPLL minimum multiplier setting

May 25, 2017, 10:40 am
$
0
0

Part Number:AM5716

I'm currently reviewing the DPLL settings for the AM5716 design I'm using.  The output frequency of the PLLs are generally determined by the formula (M / (N + 1)) × FINP.  A note in Section 3.6.3.3.2 of the Technical Reference Manual states that "It is preferred to minimize the value for N parameter (it minimizes lock time and jitter). Then M should be chosen to provide correct frequency (with lowest delta as possible)."  My question is if there are any requirements for the value of M or if M can be any value.

↧
↧

TPS61200: Unable to configure adequate UVLO threshold for single-cell lithium-polymer input source (3.7V)

May 25, 2017, 10:44 am
$
0
0

Part Number:TPS61200

I am using the TPS61200 (adjustable) reference application circuit on page 14, where I am connecting a single-cell lithium polymer battery (3.7V nominal) as the input supply, and I am setting the regulator (R1, R2) to 4.7V output.  The circuit works fine, but when trying to configure it to use UVLO as a battery saver, it seems unable to be set in a way that makes sense for a 3.7V lithium polymer input source.  I want to set the UVLO threshold for 3V input, which is the recommended lowest battery voltage to allow it to drain down to.  So I have a 249K resistor (R4) to GND from UVLO, and a 2.7M resistor (R3) from Vin to UVLO.  This results in 0.25V at UVLO when the input drops to 3V.   It seems the regulator won't even turn on when I do this, and it may be because at 3.7V input, the voltage at UVLO may not be above the minimum required based on the chip tolerances I see in the datasheet.  I don't see how you can use UVLO reliably to do this for a 3.7V battery and have a reliable 3.0V cutoff, and also make sure it will work if the battery goes above say 3.2V.  What am I missing, or doing wrong here?

↧

SN75185: Application issue compare with GD65232 --- DTR signal delay

May 25, 2017, 10:47 am
$
0
0

Part Number:SN75185

Hi greeting!

I'm helping customer to debug a issue about their application use SN75185DBR

The VCC +/- is from ATX power +12V/-12V ; the other side is the RS-232 connector with cable hook up another device 

The issue now is they use SN75185 and find the DTR signal will be delay about 2ms after +3.3V ATX power , this is almost the same timing with -12V comes out and will cause system fail to power-on

But if they use the GD65232, it's ok to power-on 

Their schematic and test waveform could refer the file as I attached here. Could you help to provide some idea to us to know:

•Whether the diode is needed or not? (D24, D42), could be replaced by 0 ohm?
•What reason will cause DTR signal delay about 2ms

Thanks again. 

(Please visit the site to view this file)

↧
Search

DAC0800: DAC IC chips

May 25, 2017, 10:48 am
$
0
0

Part Number:DAC0800

Are the DAC IC chips produced by texas instruments are compatible with the comtrade filing system? I've been specifically looking into DAC0802 and DAC0800.

↧

TMS320F28027F: Difference between LAUNCHXL-F28027F and LAUNCHXL-F28027

May 25, 2017, 10:51 am
$
0
0

Part Number:TMS320F28027F

Hello, 

This may be a straightforward question, but I was wondering what the difference between TMS320F28027F and TMS320F28027 ?

I have flash locked my device and I would like to replace the IC on the Launchpad. I understand that buying the LAUNCHXL-F28027F will be easier but I have already proceeded to solder the pin outs to other connections and it has been locked to place. So, changing out the whole controller is not an option. 

I was not able to find the hardware package for the LAUNCHXL-F28027F with the bill of materials to know which MCU is installed on it. I was able to find the hardware package of LAUNCHXL-F28027, which pointed that TMS320F28027PTS is installed on it. 

I checked under the microscope and saw that LAUNCHXL-F28027F has TMS320F28027PTT installed. 

My question remains now is that the only difference between the two is that:

1. TMS320F28027PTT - Has INSTAspin

    TMS320F28027PTS - Does not have INSTAspin

is this information correct?

2. Where can i find the hardware package for LAUNCHXL-F28027F ?

↧
↧

TPS65982: I_PP_HV Readings using HI-Utility not accurate with TI-EVM board

May 25, 2017, 11:02 am
$
0
0

Part Number:TPS65982

I have a TI-EVM board connected with switches set = 6. I have a 1.5A sink contract at 12V and am measuring the current with two other external meters, the one on the sink and an inline meter. When I set it up to sink 1.5A, they both say that is what I am sinking.

However, the version 2.4 of the HI-Utility gives a reading of 0.864844A. If I do a reverse calculation (using 1024 instead of 1023 because of a HI utility bug), I get 0.864844 * 1024 / 1.2 = 738 for the ADC value. Since the current reading is so far off, I tried to figure out what would give a 1.5A reading, and it looks like the formula should be:

ADC reading * 2.1 / 1023. This gives 738 * 2.1 / 1023 = 1.515A. This is much closer to the true value. I tried a few other reads, and 2.1 seems to be the correct number, not 1.2.

I then set the TI-EVM board up to a 20V contract so that it would use the I_PP_EXT reading instead. The readings I get with the same 1.5A load are all right around 1.5A. One, for instance was 1.435547. Using the same formula, 1.435547 * 1024 / 1.2 = 1225.

So, either the ADC readings are wrong for the I_PP_HV readings, or they need to be scaled with 2.1 instead of 1.2.

Maybe the TI firmware I used (version 2.15r2 of the App config) is just off.

WST

↧

controlCARD for instaSPIN-BLDC with the DRV8301-69M-KIT

May 25, 2017, 11:17 am
↧

CCS/CC2640: CCS/CC2640

May 25, 2017, 11:25 am
$
0
0

Part Number:CC2640

Tool/software: Code Composer Studio

Dear Sir, 

I am using SensorTag code to modify it to fit my board. I face a problem when I am using I2C to control LP55231 LED driver. I am using the SensorI2C_writeReg() function for the I2C communication for the LP55231 but system hangs on with CCS shows a window CLE Expression: GLE_Go(0x329e). After I debug into the source code, it hangs on the I2CCC26XX_transfer() function that position as show as below,  

/*
* Wait for the transfer to complete here.
* It's OK to block from here because the I2C's Hwi will unblock
* upon errors
*/
Semaphore_pend(Semaphore_handle(&(object->transferComplete)), BIOS_WAIT_FOREVER);

 It problem seems I2C can complete.

I was trying to change the clock from I2C_400kHz to I2C_100kHz, but the result as same. I am using 10K for the I2C both SDA and SCL pull high resister. 

Could you please have some suggestion for this problem? 

Thank you 

James 

 

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