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

UCC27714: UVLO fault, how can I open the HO gate to HS source? Please help me

$
0
0

Part Number:UCC27714

I bought some UCC27714 half-bridge driver to make a piezo high voltage driver few weeks ago.In my testing period, I encountered some problems. One is that the HO output is abnormal.

If I give a period rectangular wave that is HI and LI change from 0 to 1 periodicly. I find that the LO response is right. But the HO response is always the Vgate(Voltage on the FET’s gate pin) is equal to Vsource(voltage on source pin).My diagram is like this:

The yellow points represents test points. The red values are the tested values. I think this is UVLO fault. But I don’t know how to solve it.

Please give some tips. Thank you very much!


CCS/MSP430F5529: How to interface accerlerometer adxl335 ?

$
0
0

Part Number:MSP430F5529

Tool/software: Code Composer Studio

Hi, I'm using msp430f5529 and adxl5529 for my project and I don't know how to use analog input in code composer studio (CCS). I couldn't find any tutorial regarding this on there official site.

TAS5754M: No response to access request PurePath Console

$
0
0

Part Number:TAS5754M

A couple of days ago I requested access to the PurePath Console using the form, but I have not received any response yet. There is no TI email in spam, nothing.

I have designed the TAS5754 on my board and would like to get started using it. I do not have the evaluation module hardware.

Please advise on how to proceed, thank you.

DLPDLCR2000EVM: dlp lightcrafter 2000 not booting

$
0
0

Part Number:DLPDLCR2000EVM

hello,

can anyone help me here? this is sanjay calling from india.

i got 2 dlp-lightcrafter-2000.

first one I accidentally  plugged in 9v and it just got hot at the right corner( below black projector set up). I sensed a burnt smell and it got hot despite me pulling down suddenly.

I did then plugged 5 v, 1 amp and there is no splash screen. And nothing seems to really happening. the leds go on and off when hands are near it but nothing really happens.

before plugging 9 volts, i had tried to supply power from raspberry pi 3( jumper j3 and ground). because it did not seem to work i ventured in to 9volts( it was plugged in for a very short time. i pulled out the moment i sensed the heat. may be it was too late. i have no clue)

the second one works perfectly( I did not plug inn 9 volts here. after first experience)

Is there no sort of voltage protection? is power supply not adequate for the first one hence it is not booting? or the first one just had some sort of failure at display? it got hot at the right bottom! Or it is more likely to work at 5 v and 3A only?

the second one works at 5 v, 1 amp supply( this one i have not tried from raspberry pi 3 )

can the first one be salvaged? I really needed both of them. texas instruments does not have any seller here( bangalore). I got it from mouser.com straight from states and incurred massive tax locally.

any sort of help is appreciated.

CCS/CC1310: EasyLink: rxPacket.rxTimeout = EasyLink_us_To_RadioTime(10); results infinite timeout

$
0
0

Part Number:CC1310

Tool/software: Code Composer Studio

Hello!

I found that this code results infinite timeout:

rxPacket.rxTimeout = EasyLink_us_To_RadioTime(10);

EasyLink_receive(&rxPacket);

I understand, that this small timeout is useless, but, in my case, timeout value was calculated in cycle. I think, that will be better if EasyLink documentation or code will be corrected.   

LMS33460: Power ON/OFF circuit with under voltage protection

$
0
0

Part Number:LMS33460

Hi,

I have put together the push button circuit explained in TI's SCEA048B application report with an under voltage protection using TI's LMS33460 chip. I ended up with the circuit attached.

The idea is to have the LMS33460 under voltage detector monitoring the +PACK line from the battery so it pulls down the regulator enable pin to power down the device in case the battery voltage falls bellow 3v, but I have several doubts:

1. After doing the schematic I realized that I should use an under voltage detector that triggers at 3.4v instead of 3v, because the 3.3v LDO regulator has a maximum dropout voltage of 250mV and the TM4C123GH6PM has a minimum operating voltage of 3.15v, so 3.15v + 0.25v = 3.4v.. under this battery voltage the microcontroller will not have enough voltage supply. But, since I am using a 3.7v lithium battery, this would only give 3.7-3.4 = 300mV of margin for the battery to discharge.. I don't know much about lithium batteries but that doesn't seem to be a lot... is that a problem?

2. I haven't found the input resistance of the TLV70033's Enable pin in the datasheet, so how can I know the maximum pull down resistor (R33) to minimize consumption and still pull down the voltage to turn off the regulator. Anyway, this pull down resistor is not needed anymore after connecting the enable line to the flip-flop, since its output is not an open drain and it will command the line high or low, right?.

3. Do you think this would work?  : )

4. Is there a better way for protecting the battery?

Thanks

CCS: IQ library and TMS320F28030

$
0
0

Tool/software: Code Composer Studio

Hello,

I have been working with TMS320F28030.

I have two data that i need to multiply them in IQ format but i couldnot find an IQ value which gives me correct values.

what i did so far is;

//defines 

#define GLOBAL_Q 16 // changed 16 to few other values to test
long GlobalQ = GLOBAL_Q;

#define res16 0.0000762939453125 //  = 5/2^16
#define data 0x9B76 //16 bit data

_iq res16_iq;
_iq data_iq;

in main loop;

res16_iq = _IQ(res16);
data_iq = _IQ(data);

when i change GLOBAL_Q 16 to

GLOBAL_Q 15 or less i get correct value for data_iq but wrong value for res16_iq,

GLOBAL_Q 16 or more i get correct value for res16_iq but wrong value for data_iq.

1) is there any way to multiply data_iq and res16_iq in an _IQ value? such like _IQmpy(data_iq, res16_iq)

2) and for the project when i debug it with flash i can see correct values of _IQ but when i try without flash _IQ values appears to be different then expected.

Question about MPPT and converter "the boost"

$
0
0

Hi

suddenly I have a question about PV-MPPT

I want to make a Hybrid system PV- ESS with grid on psim

so i found about MPPT converter with boost

then I was wanderling how can I Control DC-Bus.

as you can see Fig 1 

-the yello circle is a DC-Bus.

-the blue circle is inverters output of grid

Q1 ==> if I didn`t make sure about DC-bus How can I  make reference of DC-bus?

Q2 ==> is there any Document or paper to help me about MPPT output Control?

Thank you very much

PS : here is the psim simview


Compiler/TMS320C6678: openmp performance evaluation

$
0
0

Part Number:TMS320C6678

Tool/software: TI C/C++ Compiler

Has anyone tested the speedup of OpenMP program using the runtime implemented by  TI ?

Or is there any official documentation supplied by  TI  covered such issues on the details of the improvement of performance about one OpenMP program running on C6678 using 8 cores and  only one core?

Best Regards 

TDC1000-TDC7200EVM: Ringdown effect

$
0
0

Part Number:TDC1000-TDC7200EVM

Hi everyone,

I'm using a TDC1000-TDC7200EVM board in order to evaluate the distance between two transducers (one as trasmitter and the other as receiver). I have connected the transmitter to channel 2 and the receiver to channel 1. I have also select channel 2 for trasmission (CH_SEL=CH2 (TX2)) and channel 1 for receiving (Mode 1). I correctly stimulate the transmitter and it shows the ringdown effect. I don't understand why the ringing affect the minimum measurable distance even if the receiver channel is the one connected to the other transducer. I'm using short TOF mode because i have to measure short distances and i have to wait until the ringing has stopped in order to have good measures. Could someone explain me why the ringodwn effect still influences the measurement even if the receiver channel is the one not connected to the ringing transducer? Thank you very much

Regards,

Luigi

BQ76940EVM: Schematic queries

$
0
0

Part Number:BQ76940EVM

Hi,

Please reply on my queries on BQ76940EVM schematic slvu925b 

1)what is the functionality of C4,C5?why we need to use that?

2)what is the functionality of C6,C7?why we need to use that?

3)D1 & D4 used for protection?please explain

4)what is the use of Q5?can we connect CHG directly to R7 ?bypassing Q5 

CCS/AM3358: JTAG error connecting to PRU

$
0
0

Part Number:AM3358

Tool/software: Code Composer Studio

I use CCS Studio : 8.0.0.00016 on Linux Mint 16.04.

I read this, this and this.

I imported the PRU_Hardware_UART project from the support package and this is my target configuration file:

and selecting PRU_0:

Are these gel files correct ( I have not changed them ) ?

Clicking on Test Connection seems to succeed:

[Start: Texas Instruments XDS110 USB Debug Probe_0]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity

[Result]


-----[Print the board config pathname(s)]------------------------------------

/home/p/.ti/ti/0/0/BrdDat/testBoard.dat

-----[Print the reset-command software log-file]-----------------------------

This utility has selected a 100- or 510-class product.
This utility will load the adapter 'libjioxds110.so'.
The library build date was 'Feb  8 2018'.
The library build time was '18:25:14'.
The library package version is '7.0.188.0'.
The library component version is '35.35.0.0'.
The controller does not use a programmable FPGA.
The controller has a version number of '5' (0x00000005).
The controller has an insertion length of '0' (0x00000000).
This utility will attempt to reset the controller.
This utility has successfully reset the controller.

-----[Print the reset-command hardware log-file]-----------------------------

The scan-path will be reset by toggling the JTAG TRST signal.
The controller is the XDS110 with USB interface.
The link from controller to target is direct (without cable).
The software is configured for XDS110 features.
The controller cannot monitor the value on the EMU[0] pin.
The controller cannot monitor the value on the EMU[1] pin.
The controller cannot control the timing on output pins.
The controller cannot control the timing on input pins.
The scan-path link-delay has been set to exactly '0' (0x0000).

-----[Perform the Integrity scan-test on the JTAG IR]------------------------

This test will use blocks of 64 32-bit words.
This test will be applied just once.

Do a test using 0xFFFFFFFF.
Scan tests: 1, skipped: 0, failed: 0
Do a test using 0x00000000.
Scan tests: 2, skipped: 0, failed: 0
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 0
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 0
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 0
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 0
All of the values were scanned correctly.

The JTAG IR Integrity scan-test has succeeded.

-----[Perform the Integrity scan-test on the JTAG DR]------------------------

This test will use blocks of 64 32-bit words.
This test will be applied just once.

Do a test using 0xFFFFFFFF.
Scan tests: 1, skipped: 0, failed: 0
Do a test using 0x00000000.
Scan tests: 2, skipped: 0, failed: 0
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 0
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 0
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 0
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 0
All of the values were scanned correctly.

The JTAG DR Integrity scan-test has succeeded.

[End: Texas Instruments XDS110 USB Debug Probe_0]

In PRU Training: Hands-on Labs , step 9 of Lab1 says:

9. Let’s launch the debugger and load the code!

a. Right click the Target Configuration file we just created and select Launch Selected Configuration.

There is no menu entry Launch Selected Configuration:

I added the startup script to the debug configuration:

And when I click Debug, I get:

What can I do ?

(Note: There is no SDCard inserted and I pressed the Boot button at startup to prevent Linux from booting , only the power LED is lit, no heartbeat blinking )

Thanks and regards

Peter

LAUNCHXL-F28069M: DRV8305 custom board, F28069M Launchpad and Motorware

$
0
0

Part Number:LAUNCHXL-F28069M

Hi,

I have a custom DRV8305 board which is more or less identical to the BOOSTXL-DRV8305 board, which I have connected to the LAUNCHXL-F28069M. Just that the MOSFET's are different and it has an additional voltage regulator on the board.

Using Code Composer Studio  Version: 8.0.0.00016, motorware_1_01_00_18, I would like to quickly test the DRV8305 board functionality with one of the Proj_Lab files. I am wondering which project would be ideally suited to test the DRV8305 board with the minimal hassles ?

Any suggestions ?

Thanks,

Manu

smart RF studio and Sniffer

RTOS/TM4C1294NCPDT: TI-RTOS last update since 2 years?

$
0
0

Part Number:TM4C1294NCPDT

Tool/software:TI-RTOS

Hello

Does TI-ROTS is getting further developed? And Is there a development roadmap?
Latest version 2.16.01.14 (for tiva C) is from April 2016.

Cheers
Chris


CCS/LAUNCHXL-CC2650: CCS v8 Compiler errors on TI example code

$
0
0

Part Number:LAUNCHXL-CC2650

Tool/software: Code Composer Studio

Hello ...first time user of TI software tools.

1. Downloaded latest CCS v8 and installed it on my computer. Downloaded and installed TI-RTOS as well.

2. Went through the Introduction and as suggested also downloaded and installed the BLE SDK 2.2.2.

3. Have I downloaded all necessary software modules I need to start my project?

Problems (2 of them):

1. I can't see the BLE SDK folder in Project Explorer on the left but can see the RTOS folder and its subdirectories (see below). How can I resolve this problem?

2. I tried to run one of the example files (by clicking the "Build" hammer button) and got a whole bunch of compilation errors. See pic below and inserted compilation log file. I was under the impression that all will run smoothly as the documentation said. What can I do to resolve these errors? I suspect maybe there's one root cause for all of them, but I have no proof to back up my suspicions.

**** Build of configuration Debug for project pinInterrupt_CC2650_LAUNCHXL_TI ****
"C:\\Texas Instruments\\ccsv8\\utils\\bin\\gmake" -k -j 8 all -O 
 
making ../src/sysbios/rom_sysbios.aem3 ...
Building file: "../pinInterrupt.cfg"
Building file: "../CC2650_LAUNCHXL.c"
Invoking: ARM Compiler
"C:/Texas Instruments/ccsv8/tools/compiler/ti-cgt-arm_18.1.1.LTS/bin/armcl" -mv7M3 --code_state=16 --float_support=vfplib -me --include_path="D:/Backups/Graduate School/UMass-Lowell/Semester/Haselmeier Project/Embedded Software/pinInterrupt_CC2650_LAUNCHXL_TI" --include_path="D:/Backups/Graduate School/UMass-Lowell/Semester/Haselmeier Project/Embedded Software/pinInterrupt_CC2650_LAUNCHXL_TI" --include_path="C:/TI/tirtos_cc13xx_cc26xx_2_21_00_06/products/cc26xxware_2_24_03_17272" --include_path="C:/Texas Instruments/ccsv8/tools/compiler/ti-cgt-arm_18.1.1.LTS/include" --define=ccs -g --diag_warning=225 --diag_warning=255 --diag_wrap=off --display_error_number --gen_func_subsections=on --abi=eabi --preproc_with_compile --preproc_dependency="CC2650_LAUNCHXL.d_raw" --cmd_file="configPkg/compiler.opt" "../CC2650_LAUNCHXL.c"
[include.]
 
>> Compilation failure
subdir_rules.mk:9: recipe for target 'CC2650_LAUNCHXL.obj' failed
>> WARNING: more than one source file is specified; preprocessor output will be generated for last file only
Fatal error #1965: cannot open source file "Instruments/ccsv8/tools/compiler/ti-cgt-arm_18.1.1.LTS/include"
1 catastrophic error detected in the compilation of "Instruments/ccsv8/tools/compiler/ti-cgt-arm_18.1.1.LTS/include".
Compilation terminated.
gmake: *** [CC2650_LAUNCHXL.obj] Error 1
Building file: "../ccfg.c"
Invoking: ARM Compiler
"C:/Texas Instruments/ccsv8/tools/compiler/ti-cgt-arm_18.1.1.LTS/bin/armcl" -mv7M3 --code_state=16 --float_support=vfplib -me --include_path="D:/Backups/Graduate School/UMass-Lowell/Semester/Haselmeier Project/Embedded Software/pinInterrupt_CC2650_LAUNCHXL_TI" --include_path="D:/Backups/Graduate School/UMass-Lowell/Semester/Haselmeier Project/Embedded Software/pinInterrupt_CC2650_LAUNCHXL_TI" --include_path="C:/TI/tirtos_cc13xx_cc26xx_2_21_00_06/products/cc26xxware_2_24_03_17272" --include_path="C:/Texas Instruments/ccsv8/tools/compiler/ti-cgt-arm_18.1.1.LTS/include" --define=ccs -g --diag_warning=225 --diag_warning=255 --diag_wrap=off --display_error_number --gen_func_subsections=on --abi=eabi --preproc_with_compile --preproc_dependency="ccfg.d_raw" --cmd_file="configPkg/compiler.opt" "../ccfg.c"
[include.]
 
>> Compilation failure
subdir_rules.mk:16: recipe for target 'ccfg.obj' failed
>> WARNING: more than one source file is specified; preprocessor output will be generated for last file only
Fatal error #1965: cannot open source file "Instruments/ccsv8/tools/compiler/ti-cgt-arm_18.1.1.LTS/include"
1 catastrophic error detected in the compilation of "Instruments/ccsv8/tools/compiler/ti-cgt-arm_18.1.1.LTS/include".
Compilation terminated.
gmake: *** [ccfg.obj] Error 1
Building file: "../pinInterrupt.c"
Invoking: ARM Compiler
"C:/Texas Instruments/ccsv8/tools/compiler/ti-cgt-arm_18.1.1.LTS/bin/armcl" -mv7M3 --code_state=16 --float_support=vfplib -me --include_path="D:/Backups/Graduate School/UMass-Lowell/Semester/Haselmeier Project/Embedded Software/pinInterrupt_CC2650_LAUNCHXL_TI" --include_path="D:/Backups/Graduate School/UMass-Lowell/Semester/Haselmeier Project/Embedded Software/pinInterrupt_CC2650_LAUNCHXL_TI" --include_path="C:/TI/tirtos_cc13xx_cc26xx_2_21_00_06/products/cc26xxware_2_24_03_17272" --include_path="C:/Texas Instruments/ccsv8/tools/compiler/ti-cgt-arm_18.1.1.LTS/include" --define=ccs -g --diag_warning=225 --diag_warning=255 --diag_wrap=off --display_error_number --gen_func_subsections=on --abi=eabi --preproc_with_compile --preproc_dependency="pinInterrupt.d_raw" --cmd_file="configPkg/compiler.opt" "../pinInterrupt.c"
[include.]
 
>> Compilation failure
subdir_rules.mk:23: recipe for target 'pinInterrupt.obj' failed
>> WARNING: more than one source file is specified; preprocessor output will be generated for last file only
Fatal error #1965: cannot open source file "Instruments/ccsv8/tools/compiler/ti-cgt-arm_18.1.1.LTS/include"
1 catastrophic error detected in the compilation of "Instruments/ccsv8/tools/compiler/ti-cgt-arm_18.1.1.LTS/include".
Compilation terminated.
gmake: *** [pinInterrupt.obj] Error 1
Invoking: XDCtools
"C:/TI/xdctools_3_32_00_06_core/xs" --xdcpath="C:/TI/tirtos_cc13xx_cc26xx_2_21_00_06/packages;C:/TI/tirtos_cc13xx_cc26xx_2_21_00_06/products/tidrivers_cc13xx_cc26xx_2_21_00_04/packages;C:/TI/tirtos_cc13xx_cc26xx_2_21_00_06/products/bios_6_46_01_37/packages;C:/TI/tirtos_cc13xx_cc26xx_2_21_00_06/products/uia_2_01_00_01/packages;" xdc.tools.configuro -o configPkg -t ti.targets.arm.elf.M3 -p ti.platforms.simplelink:CC2650F128 -r release -c "C:/Texas Instruments/ccsv8/tools/compiler/ti-cgt-arm_18.1.1.LTS" --compileOptions "-mv7M3 --code_state=16 --float_support=vfplib -me --include_path=\"D:/Backups/Graduate School/UMass-Lowell/Semester/Haselmeier Project/Embedded Software/pinInterrupt_CC2650_LAUNCHXL_TI\" --include_path=\"D:/Backups/Graduate School/UMass-Lowell/Semester/Haselmeier Project/Embedded Software/pinInterrupt_CC2650_LAUNCHXL_TI\" --include_path=\"C:/TI/tirtos_cc13xx_cc26xx_2_21_00_06/products/cc26xxware_2_24_03_17272\" --include_path=\"C:/Texas Instruments/ccsv8/tools/compiler/ti-cgt-arm_18.1.1.LTS/include\" --define=ccs -g --diag_warning=225 --diag_warning=255 --diag_wrap=off --display_error_number --gen_func_subsections=on --abi=eabi  " "../pinInterrupt.cfg"
gmake[1]: Entering directory 'D:/Backups/Graduate School/UMass-Lowell/Semester/Haselmeier Project/Embedded Software/pinInterrupt_CC2650_LAUNCHXL_TI/src/sysbios'
asmem3 C:/TI/tirtos_cc13xx_cc26xx_2_21_00_06/products/bios_6_46_01_37/packages/ti/sysbios/family/arm/m3/Hwi_asm.sv7M ...
 
>> Compilation failure
makefile:40: recipe for target 'm3_Hwi_asm.obj' failed
Fatal error: cannot open source file "Instruments/ccsv8/tools/compiler/ti-cgt-arm_18.1.1.LTS/include"
1 catastrophic error detected in the compilation of "Instruments/ccsv8/tools/compiler/ti-cgt-arm_18.1.1.LTS/include".
Compilation terminated.
gmake[1]: *** [m3_Hwi_asm.obj] Error 1
gmake[1]: Leaving directory 'D:/Backups/Graduate School/UMass-Lowell/Semester/Haselmeier Project/Embedded Software/pinInterrupt_CC2650_LAUNCHXL_TI/src/sysbios'
gmake[1]: Entering directory 'D:/Backups/Graduate School/UMass-Lowell/Semester/Haselmeier Project/Embedded Software/pinInterrupt_CC2650_LAUNCHXL_TI/src/sysbios'
asmem3 C:/TI/tirtos_cc13xx_cc26xx_2_21_00_06/products/bios_6_46_01_37/packages/ti/sysbios/family/arm/m3/Hwi_asm_switch.sv7M ...
 
>> Compilation failure
makefile:44: recipe for target 'm3_Hwi_asm_switch.obj' failed
Fatal error: cannot open source file "Instruments/ccsv8/tools/compiler/ti-cgt-arm_18.1.1.LTS/include"
1 catastrophic error detected in the compilation of "Instruments/ccsv8/tools/compiler/ti-cgt-arm_18.1.1.LTS/include".
Compilation terminated.
gmake[1]: *** [m3_Hwi_asm_switch.obj] Error 1
Fatal error: cannot open source file "Instruments/ccsv8/tools/compiler/ti-cgt-arm_18.1.1.LTS/include"
1 catastrophic error detected in the compilation of "Instruments/ccsv8/tools/compiler/ti-cgt-arm_18.1.1.LTS/include".
Compilation terminated.
gmake[1]: *** [rom_sysbios.obj] Error 1
gmake[1]: Leaving directory 'D:/Backups/Graduate School/UMass-Lowell/Semester/Haselmeier Project/Embedded Software/pinInterrupt_CC2650_LAUNCHXL_TI/src/sysbios'
gmake[1]: Entering directory 'D:/Backups/Graduate School/UMass-Lowell/Semester/Haselmeier Project/Embedded Software/pinInterrupt_CC2650_LAUNCHXL_TI/src/sysbios'
clem3 C:/TI/tirtos_cc13xx_cc26xx_2_21_00_06/products/bios_6_46_01_37/packages/ti/sysbios/BIOS.c ...
 
>> Compilation failure
makefile:57: recipe for target 'rom_sysbios.obj' failed
gmake[1]: Leaving directory 'D:/Backups/Graduate School/UMass-Lowell/Semester/Haselmeier Project/Embedded Software/pinInterrupt_CC2650_LAUNCHXL_TI/src/sysbios'
gmake[1]: Entering directory 'D:/Backups/Graduate School/UMass-Lowell/Semester/Haselmeier Project/Embedded Software/pinInterrupt_CC2650_LAUNCHXL_TI/src/sysbios'
asmem3 C:/TI/tirtos_cc13xx_cc26xx_2_21_00_06/products/bios_6_46_01_37/packages/ti/sysbios/family/arm/m3/IntrinsicsSupport_asm.sv7M ...
 
>> Compilation failure
makefile:48: recipe for target 'm3_IntrinsicsSupport_asm.obj' failed
Fatal error: cannot open source file "Instruments/ccsv8/tools/compiler/ti-cgt-arm_18.1.1.LTS/include"
1 catastrophic error detected in the compilation of "Instruments/ccsv8/tools/compiler/ti-cgt-arm_18.1.1.LTS/include".
Compilation terminated.
gmake[1]: *** [m3_IntrinsicsSupport_asm.obj] Error 1
gmake[1]: Leaving directory 'D:/Backups/Graduate School/UMass-Lowell/Semester/Haselmeier Project/Embedded Software/pinInterrupt_CC2650_LAUNCHXL_TI/src/sysbios'
gmake[1]: Entering directory 'D:/Backups/Graduate School/UMass-Lowell/Semester/Haselmeier Project/Embedded Software/pinInterrupt_CC2650_LAUNCHXL_TI/src/sysbios'
asmem3 C:/TI/tirtos_cc13xx_cc26xx_2_21_00_06/products/bios_6_46_01_37/packages/ti/sysbios/family/arm/m3/TaskSupport_asm.sv7M ...
 
>> Compilation failure
makefile:52: recipe for target 'm3_TaskSupport_asm.obj' failed
Fatal error: cannot open source file "Instruments/ccsv8/tools/compiler/ti-cgt-arm_18.1.1.LTS/include"
1 catastrophic error detected in the compilation of "Instruments/ccsv8/tools/compiler/ti-cgt-arm_18.1.1.LTS/include".
Compilation terminated.
gmake[1]: *** [m3_TaskSupport_asm.obj] Error 1
gmake[1]: Target 'all' not remade because of errors.
gmake[1]: Leaving directory 'D:/Backups/Graduate School/UMass-Lowell/Semester/Haselmeier Project/Embedded Software/pinInterrupt_CC2650_LAUNCHXL_TI/src/sysbios'
../src/makefile.libs:56: recipe for target '../src/sysbios/rom_sysbios.aem3' failed
gmake: *** [../src/sysbios/rom_sysbios.aem3] Error 2
configuring pinInterrupt.xem3 from package/cfg/pinInterrupt_pem3.cfg ...
generating custom ROM library makefile ... 
Starting build of library sources ...
Build of libraries failed.
subdir_rules.mk:33: recipe for target 'build-1613913039-inproc' failed
gmake: D:/Backups/Graduate: No such file or directory
gmake: *** No rule to make target `D:/Backups/Graduate'.  Stop.
error: xdc.cfg.SourceDir: "C:/TI/xdctools_3_32_00_06_core/packages/xdc/cfg/SourceDir.xs", line 209: xdc.cfg.SourceDir : Build of generated source libraries failed: exit status = 2:
 
js: "C:/TI/xdctools_3_32_00_06_core/packages/xdc/cfg/Main.xs", line 160: Error: Configuration failed!
xdctools_3_32_00_06_core\gmake.exe: *** [package/cfg/pinInterrupt_pem3.xdl] Error 1
xdctools_3_32_00_06_core\gmake.exe: *** Deleting file `package/cfg/pinInterrupt_pem3.xdl'
xdctools_3_32_00_06_core\gmake.exe: *** [package/cfg/pinInterrupt_pem3.xdl] Deleting file `package/cfg/pinInterrupt_pem3.h'
xdctools_3_32_00_06_core\gmake.exe: *** [package/cfg/pinInterrupt_pem3.xdl] Deleting file `package/cfg/pinInterrupt_pem3.c'
js: "C:/TI/xdctools_3_32_00_06_core/packages/xdc/tools/Cmdr.xs", line 51: Error: xdc.tools.configuro: configuration failed due to earlier errors (status = 2); 'linker.cmd' deleted.
gmake[1]: *** [build-1613913039-inproc] Error 1
gmake: *** [build-1613913039] Error 2
subdir_rules.mk:30: recipe for target 'build-1613913039' failed
gmake: Target 'all' not remade because of errors.
**** Build Finished ****

CCS/CC3200: ti_rtos_config

$
0
0

Part Number:CC3200

Tool/software: Code Composer Studio

I keep on getting this error message and can't seem to figure out why i can't get it to work?

the problem i think i am having is The package 'ti.sysbios.knl' is not compatible with XDCtools used in this build. Please either use XDCtools compatible with that package, or update the product containing that package, or rebuild the package with XDCtools 3.50 or later. js: "C:/ti/xdctools_3_50_05_12_core/packages/xdc/cfg/Main.xs", line 160: Error: Configuration failed!




**** Clean-only build of configuration Default for project ti_rtos_config **** "C:\\ti\\ccsv8\\utils\\bin\\gmake" -k clean DEL /F "ti_rtos_config.lib" "configPkg\linker.cmd" "configPkg\compiler.opt" RMDIR /S/Q "configPkg\" Could Not Find F:\ti workspace\ti_rtos_config\Default\ti_rtos_config.lib Finished clean **** Build Finished **** **** Build of configuration Default for project ti_rtos_config **** "C:\\ti\\ccsv8\\utils\\bin\\gmake" -k all Building file: "C:/ti/CC3200SDK_1.3.0/cc3200-sdk/ti_rtos/ti_rtos_config/app.cfg" Invoking: XDCtools "C:/ti/xdctools_3_50_05_12_core/xs" --xdcpath="C:/ti/ccsv8/ccs_base;C:/ti/tirtos_cc32xx_2_15_00_17/packages;C:/ti/tirtos_cc32xx_2_15_00_17/products/tidrivers_cc32xx_2_15_00_26/packages;C:/ti/tirtos_cc32xx_2_15_00_17/products/bios_6_45_00_20/packages;C:/ti/tirtos_cc32xx_2_15_00_17/products/uia_2_00_02_39/packages;" xdc.tools.configuro -o configPkg -t ti.targets.arm.elf.M4 -p ti.platforms.simplelink:CC3200 -r release -c "C:/ti/ccsv8/tools/compiler/ti-cgt-arm_18.1.1.LTS" "C:/ti/CC3200SDK_1.3.0/cc3200-sdk/ti_rtos/ti_rtos_config/app.cfg" making package.mak (because of package.bld) ... generating interfaces for package configPkg (because package/package.xdc.inc is older than package.xdc) ... configuring app.xem4 from package/cfg/app_pem4.cfg ... subdir_rules.mk:12: recipe for target 'build-11648687-inproc' failed error: xdc.cfg.Program: "C:/ti/xdctools_3_50_05_12_core/packages/xdc/cfg/Program.xs", line 71: xdc.cfg.Program : The package 'ti.sysbios.knl' is not compatible with XDCtools used in this build. Please either use XDCtools compatible with that package, or update the product containing that package, or rebuild the package with XDCtools 3.50 or later. js: "C:/ti/xdctools_3_50_05_12_core/packages/xdc/cfg/Main.xs", line 160: Error: Configuration failed! gmake.exe: *** [package/cfg/app_pem4.xdl] Error 1 js: "C:/ti/xdctools_3_50_05_12_core/packages/xdc/tools/Cmdr.xs", line 52: Error: xdc.tools.configuro: configuration failed due to earlier errors (status = 2); 'linker.cmd' deleted. gmake[2]: *** [build-11648687-inproc] Error 1 gmake[1]: *** [build-11648687] Error 2 gmake[1]: Target 'configPkg/linker.cmd' not remade because of errors. gmake: *** [all] Error 2 subdir_rules.mk:9: recipe for target 'build-11648687' failed makefile:127: recipe for target 'all' failed **** Build Finished ****

SN65DSI84: compatible and Dual-Link LVDS

$
0
0

Part Number:SN65DSI84

Hello,

1,How to make SN65DSI83 and SN65DSI84 compatible?We did not find the device ID with the register.

2,Screen resolution is 1920*720.I want to use the Dual-Link LVDS.Soc output to SN65DSI84 resolution is 1920*720.And then,SN65DSI84 parameters can be configured as 960*720,Dual-Link LVDS.Is that so?

CCS/MSP430FR4133: ADC Register Conversion From MSP430FR6989

$
0
0

Part Number:MSP430FR4133

Tool/software: Code Composer Studio

Hi all,

I wrote this code block for ADC conversion for MSP430FR6989. It worked well. My question is, I want to implement same code on MSP430FR4133, the things is when I write the same code for it, LED is not working. Also I don't have any building error. It might be related with 12-bit ADC to 10-bit ADC conversion in my code. I also suspect "PM5CTL0 = ENABLE_PINS" line to be faulty. Please check the code blocks.

Application should be like that:

Between 0.8V and 1.2V, P1.0(LED) must be high. Else, low. 

Working code in MSP430FR6989 

#include <msp430.h>
#define ENABLE_PINS 0xFFFE // Enables inputs and outputs
void ADC_SETUP(void); // Used to setup ADC12 peripheral
main()
{
WDTCTL = WDTPW | WDTHOLD; // Stop WDT
PM5CTL0 = ENABLE_PINS; // Enable inputs and outputs
P1DIR = BIT0; // Set RED LED to output
ADC_SETUP(); // Sets up ADC peripheral
while(1)
{
ADC12CTL0 = ADC12CTL0 | ADC12ENC; // Enable conversion
ADC12CTL0 = ADC12CTL0 | ADC12SC; // Start conversion
if ((ADC12MEM0 >= 0x3C0)&&(ADC12MEM0<=0x5C0)) // 0.8V<Voltage<1.2V HIGH
{
P1OUT = BIT0; // Turn on red LED
}
else // Else input <= 1.65V
{
P1OUT = 0x00; // Turn off red LED
}
}// end while(1)
}// end main()

void ADC_SETUP(void)
{
#define ADC12_SHT_16 0x0200 // 16 clock cycles for sample and hold
#define ADC12_ON 0x0010 // Used to turn ADC12 peripheral on
#define ADC12_SHT_SRC_SEL 0x0200 // Selects source for sample & hold
#define ADC12_12BIT 0x0020 // Selects 12-bits of resolution
#define ADC12_P92 0x000A // Use input P9.2 for analog input
ADC12CTL0 = ADC12_SHT_16 | ADC12_ON ; // Turn on, set sample & hold time
ADC12CTL1 = ADC12_SHT_SRC_SEL; // Specify sample & hold clock source
ADC12CTL2 = ADC12_12BIT; // 12-bit conversion results
ADC12MCTL0 = ADC12_P92; // P9.2 is analog input
}

Not working code in MSP430FR4133 for same function. 

#include <msp430.h>
#define ENABLE_PINS 0xFFFE // Enables inputs and outputs
void ADC_SETUP(void); // Used to setup ADC12 peripheral

main(){
WDTCTL = WDTPW | WDTHOLD; // Stop WDT
PM5CTL0 = PM5CTL0 & ENABLE_PINS; // Enable inputs and outputs
P1DIR = BIT0; // Set RED LED to output
ADC_SETUP(); // Sets up ADC peripheral

while(1){

ADCCTL0 = ADCCTL0 | ADCENC; // Enable conversion
ADCCTL0 = ADCCTL0 | ADCSC; // Start conversion
if ((ADCMEM0 >= 0x0F0)&&(ADCMEM0<=0x170)){ // 0.8V<Voltage<1.2V HIGH
P1OUT = BIT0; // Turn on red LED
}
else { // Else
P1OUT = 0x00; // Turn off red LED
}
} // end while(1)
} // end main()

void ADC_SETUP(void)

{
#define ADC_SHT_16 0x0200 // 16 clock cycles for sample and hold
#define ADC_ON 0x0010 // Used to turn ADC12 peripheral on
#define ADC_SHT_SRC_SEL 0x0200 // Selects source for sample & hold
#define ADC_12BIT 0x0020 // Selects 12-bits of resolution
#define ADC_P81 0x0009 // Use input P8.1 for analog input --->A9
ADCCTL0 = ADC_SHT_16 | ADC_ON ; // Turn on, set sample & hold time
ADCCTL1 = ADC_SHT_SRC_SEL; // Specify sample & hold clock source
ADCCTL2 = ADC_12BIT; // 12-bit conversion results
ADCMCTL0 = ADC_P81; // P8.1 is analog input --->A9
}

Best Regards, Ali.

 

LM2743: LM2743 0.5V output noice on 1.2V output

$
0
0

Part Number:LM2743

Hello,

We have designed in a power circuit into our FPGA based device, that uses LM2743 buck controller.
It provide us pretty stable DC current; however, it has a strong noise on the output.
Here is our circuit and noise picture,

Anybody has an idea how to reduce this noise?

Thank you

Viewing all 262198 articles
Browse latest View live


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