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

TPL5111: TPL5111

$
0
0

Part Number:TPL5111

Hello,

I want to design a circuit to turn on/off power of microcontroller using a momentary button.The idea is to use the button as a power switch.

The logic is the following: Push the Button -> Turn on power of microcontroller, Press the button again -> turn off power of microcontroller, etc...

Can I use TPL5111 to turn on/off power using momentary button?

Best regards


RTOS/EK-TM4C1294XL: Migrating project to a new computer. How to update version of TI-RTOS used in project?

$
0
0

Part Number:EK-TM4C1294XL

Tool/software: TI-RTOS

Hi all,

I'm attempting to move a project to a new computer. The new computer is running CCS7 and I've installed TI-RTOS for Tiva-C version 2.16.01.14 with XDC Tools version 3.32.01.22. The previous computer was running some version of CCS6 and TI-RTOS version 2.14.0.10. I was hoping to update the RTOS version used for this project so it'll work on the new computer (without having to use the older version of RTOS). However, I've been unable to find any way to go about this.

Right now, when I attempt to build the project, I get the follow errors/warnings.

Errors:

  • Product 'com.ti.rtsc.TIRTOStivac' v2.14.0.10 is not currently installed and no compatible version is available. Please install this product or a compatible version. TM4C_Receiver TM4C_Receiver Problems

Warnings:

  • Invalid project path: Include path not found (C:\CCS_Workspace\workspace_v6_0\TM4C_Receiver). TM4C_Receiver pathentry Path Entry Problem
  • Invalid project path: Include path not found (C:\ti\ccsv6\tools\compiler\ti-cgt-arm_15.9.0.STS\include). TM4C_Receiver pathentry Path Entry Problem
  • Invalid project path: Include path not found (C:\ti\tirtos_tivac_2_14_00_10\packages\ti\drivers\wifi\cc3100\Simplelink). TM4C_Receiver pathentry Path Entry Problem
  • Invalid project path: Include path not found (C:\ti\tirtos_tivac_2_14_00_10\packages\ti\drivers\wifi\cc3100\Simplelink\Include). TM4C_Receiver pathentry Path Entry Problem
  • Invalid project path: Include path not found (C:\ti\tirtos_tivac_2_14_00_10\products\ndk_2_24_03_35). TM4C_Receiver pathentry Path Entry Problem
  • Invalid project path: Include path not found (C:\ti\tirtos_tivac_2_14_00_10\products\ndk_2_24_03_35\packages\ti\ndk\inc). TM4C_Receiver pathentry Path Entry Problem
  • Invalid project path: Include path not found (C:\ti\tirtos_tivac_2_14_00_10\products\ndk_2_24_03_35\packages\ti\ndk\inc\bsd). TM4C_Receiver pathentry Path Entry Problem
  • Invalid project path: Include path not found (C:\ti\tirtos_tivac_2_14_00_10\products\TivaWare_C_Series-2.1.1.71b). TM4C_Receiver pathentry Path Entry Problem

Does anyone have any suggestions? If there's no other way, I could use the older version of RTOS, but I'd prefer not to. Also, I wasn't sure if this should be in this forum or the CCS forum, so just let me know if I should move it.

Thanks.

- Tyler

RTOS/CC2640: cc2640: ADC possible?

$
0
0

Part Number:CC2640

Tool/software: TI-RTOS

Hi,

I tried to implement the the example code:

//intialize ADC
Hwi_Params hwiParams;
Hwi_Params_init(&hwiParams);
hwiParams.enableInt = true;

Hwi_construct(&hwi, INT_AUX_ADC_IRQ, adcIsr, &hwiParams, NULL);
// Enable clock for ADC digital and analog interface (not currently enabled in driver)
//AUXWUCClockEnable();

// Set up pins
ADC_pinHandle = PIN_open(&ADC_pinState, alsPins);

AUXWUCClockEnable(AUX_WUC_ADI_CLOCK|AUX_WUC_MODCLKEN0_ANAIF_M); //AUX_WUC_MODCLKEN0_ANAIF_M

Power_setConstraint(PowerCC26XX_SB_DISALLOW);
Power_setConstraint(PowerCC26XX_IDLE_PD_DISALLOW);
Power_setConstraint(PowerCC26XX_SD_DISALLOW);

AUXWUCClockEnable(AUX_WUC_ADI_CLOCK|AUX_WUC_MODCLKEN0_ANAIF_M ); //AUX_WUC_MODCLKEN0_ANAIF_M

// Connect AUX IO3 (pin 26) as analog input. see table 11-2 in SWCU117f for pin mapping- our 4X4 package is RSM
AUXADCSelectInput(ADC_COMPB_IN_AUXIO3);

//why is this line crashing the BIOS?
AUXADCEnableSync(AUXADC_REF_VDDS_REL, AUXADC_SAMPLE_TIME_42P6_US, AUXADC_TRIGGER_MANUAL); //AUXADC_REF_VDDS_REL means nominally VDDS as a reference

AUXADCGenManualTrigger(); //reading V1 from ADC on first phase, because at this phase v1 is at the source side electrode terminal

It works from within the JTAG debugger, but it doesn't work when run if powering and running the SW (no JTAG)

it seems to crash on the code line: AUXADCEnableSync(AUXADC_REF_VDDS_REL, AUXADC_SAMPLE_TIME_42P6_US, AUXADC_TRIGGER_MANUAL);

I was told to downport the ADC driver from RTOS 2.2 to RTOS 2.18 and use the driver - but then I couldn't find any driver example.

I've been trying to solve this problem for two weeks by now. 

Had any body succeeded using ADC with TI cc2640 from before?

please help

MF

CCS/TMS320F28075: Custom build command, unwanted '-O' option

$
0
0

Part Number:TMS320F28075

Tool/software: Code Composer Studio

Hi all,

I made a new project in code composer v7 ( Version: 7.0.0.00043) and want to use a custom makefile to build the project. I have specified the following build settings in my project:

But when I try to build, CCS adds the extra option '-O' to the build command which results in a build failure:

**** Build of configuration Debug for project cdm_application ****

make -k -j 4 build_debug -O
make: invalid option -- O
Usage: make [options] [target] ...

I have searched through a lot of settingsbut I cannot find the setting that stops CCS adding the '-O' option to the build command. Does anybody now how I can prevent CCS adding this option and simply execute the command as requested?

Thanks in advance,

Ron Sonnemans

BQ24090: Charging NiMH and ISET2 control

$
0
0

Part Number:BQ24090

When I look at the bq24090 Data sheet on page 1 I see in the lower right hand corner of the block diagram a block labeled Host. Since I am charging a NiMH battery I believe that I should be able to hardwire the ISET2 pin and not require any external controller for the bq24090 for my application of charging 3 series 1500 mAHr cells.

Please clarify.

Thanks,

Larry

AM5728: DPLL_VIDEO1 configuration problems

$
0
0

Part Number:AM5728

Hi, 

Im trying to just enable the video1 clock to be used in other parts of the system but im having problems with it and it would be great to have some help. 

Following the Figure 11-13 of the AM57x TRM at page 2617, I want to generate an output of 27 MHz. My SYS_CLK1 is 20MHz.

DPLL_VIDEO1_CLK is derived directly from SYS_CLK1 or SYS_CLK2, and I set the register CM_CLKSEL_VIDEO1_PLL_SYS to use SYS_CLK1.

Im using:

RegN + 1 = 7
RegM = 293
M4+1 = 1
M7+1 = 1
M8+1 = 1

The steps im using to configure the PLL are:

1) Configure the PLL_CTRL register (0x4A0A4000) to use:

## PLL_CTRL_REG
## HSDIV (bit 4) set to 1
## PLL_SYSRESET (bit 3) set to 1
## PLL_HALTMOD (bit 2) set to 0
## PLL_GATEMODE (bit 1) set to 0
## PLL_AUTOMODE (bit 0) set to 0

So, I wrote 0x18 to the register 0x4A0A4000

2) Configure the PLL_CONFIGURATION1 (0x4A0A400C):

## M=293: $((293 << 9))
## N+1=4: $((3 << 1))
## M4+1=1: $((0 << 21))

So, i wrote 0x24A06 to the register 0x4A0A400C

3) configure the PLL_CONFIGURATION2 (0x4A0A4010)

## M7_CLOCK_EN (bit 25) set to 1
## M6_CLOCK_EN (bit 23) set to 1
## REFSEL (bits 21 and 22) must be set to 0x3
## HSDIVBYPASS (bit 20) set to 0
## M4_CLOCK_EN (bit 16) set to 1
## BYPASSEN (bit 15) should be set to 0
## PHY_CLKINEN (bit 14) set to 1
## PLL_REFEN (bit 13) set to 1
## PLL_HIGHFREQ is not divided by 2 (bit 12 is set to 0)
## PLL_CLKSEL selects SYSCLK as PLL reference clock (set to 0)
## PLL_LOCKSETL (bits 9:10) set to 0x0
## PLL_DRIFTGUARDEN (bit 8) is set to 0
## PLL_LOWCURRSTDBY (bit 6) set to 0
## PLL_LLLLPMODE (bit 5) set to 0
## PLL_IDLE (bit 0) set to 0

I wrote 0x2E16000 to the register 0x4A0A1010

4) Configure the PLL_CONFIGURATION3 (0x4A0A4014)
## M6+1 = 1
## M7+1 = 1

I wrote 0x0 to the register 0x4A0A4014

5) Set the PLL_GO(0x4A0A4008) bit to 1

I wrote 0x1 to the register 0x4A0A4008

After these steps I read the 0x4A0A4008 and it was set to 0x0, which tells me that the sequence is completed.

But, if I read the status register (0x4A0A4004), the output is 0x18CC8, which means:

PLL_TICOPWDN is set to 1: Internal oscillator power down
PLL_LDOPWDN is set to 1: PLL internal LDO is powered up
BYPASS_ACKZ is set to 0: PHY or HSDIVIDER has switched to using the bypass clocks
SSC_EN_ACK is set to 0: SSC is disabled
M7_CLOCK_ACK is set to 1: M7 clock is active
M6_CLOCK_ACK is set to 1: M6 clock is active
BYPASSACKZ_MERGED is set to 0: PHY and HSDIVIDER have switched to using the bypass clocks
M4_CLOCK_ACK is set to 0: M4 clock is active
PLL_BYPASS is set to 1: PLL bypass
PLL_HIGHJITTER is set to 0: Normal jitter
PLL_LOSSREF is set to 1: Reference input inactive
PLL_RECAL is set to 0: Recalibration is not required
PLL_LOCK is set to 0: PLL is not locked
PLL_CTRL_RESET_DONE is set to 0: Reset is in progress

The main thing that the status register is telling me is that:

a) PLL is not locked
b) Input reference is inactive
c) reset is in progress

So, Im not sure what I am doing wrong here. I must have forgotten some step as per TRM`s description. Could anyone point me out what I am missing here?

Thank you

regards,

David 

CC2640R2F: 32kHz less operation when using BLE SDK configured as Central device

$
0
0

Part Number:CC2640R2F

According to the below document you can not run the CC2640 in central mode without the use of the 32kHz clock. Does this apply to R2 as well?  If so what is causing this limitation? My customer is not concerned with low power operation but is concerned on system cost and does not want to use the 32kHz crystal.

"The 32 kHz crystal-less feature is supported on CC2640/CC2650 wireless MCUs implementing the Bluetooth low energy peripheral, observer and broadcast (beacon) roles only. Thus, all central role or master devices must use the 32 kHz crystal oscillator."

http://www.ti.com/lit/pdf/swra499

LAUNCHXL-F28377S: 40-pin connectors


CCS/TMS320F28069: tmdscncd28069iso -- General Congfiguration and Connection

$
0
0

Part Number:TMS320F28069

Tool/software: Code Composer Studio

Hello Folks,

I bought TMDSCNCD28069ISO Dev Board for piccolo. I am pretty new to CCS. I have started playing with this dev board. I have used USB cable to establish the connection between the computer and dev kit. While I am trying to debug the code, I got an error like

C28xx: Error connecting to the target: (Error -1135 @ 0x0) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 6.0.504.4).

 What is the general setup configuration and connections  for the target  tmdscncd28069iso. How can I flash the dev kit. Where can I get some sample example to play with this development board.

Thanks in advance,


Regards,

Ranjit

DRV8301-69M-KIT: Mains power supply during development

$
0
0

Part Number:DRV8301-69M-KIT

Hi,

I am evaluating the instaspin kit DRV8301-69M-KIT and it appears to fit the bill in terms of the drive capacity and for my high current powerpack.

The issue I have is that powering via 10S LIPO cells (36 volts ) all  works fine, however when using a mains power supply again 36 volts and around 1.5 kw I find the mosfets overheat very quickly.

I have been advised that long power cables are not acceptable due to inductance issues and that the regenerative power is not absorbed by a mains supply as it would be using LIPO cells so capacitors must be placed across the DC power lines as in high power radio control ESC units

Has anyone else experienced this and if so ..any solutions. I am trying to avoid charging LIPO cells during the development phase. 

TMS320F28069M: Different USER.C files in paths

$
0
0

Part Number:TMS320F28069M

Hi, just noticed that I wasn't editing the USER.C file that my build used. There are two in the Motorware 17 install that are on include paths. My two paths:

C:\TI\Motorware\motorware_1_01_00_17\sw\solutions\instaspin_motion\src

C:\TI\Motorware\motorware_1_01_00_17\sw\modules\user\src\32b

My build used the second one. A file compare showed that they both have paths in their comments (line 32), however, the paths are switched! The solutions one has a modules path, and vice versa. It would take me a while to investigate the "correct" one. I am inclined to rename or move the one not being used, but perhaps there is a reason for the second USER.c?

Thanks, Bill

LMK00105: device name difference

$
0
0

Part Number:LMK00105

Hi Team,

Customer has one quick question, what is the difference among below 3 devices? Thanks!

LMK00105SQ/NOPB

LMK00105SQE/NOPB

LMK00105SQX/NOPB 

Andrew

Footprint for the CC2564BYFVR

$
0
0

Hello Team,

I have a customer requesting the Footprint for the CC2564BYFVR BGA package. This device does not show on our website, however WW show different and it is available through distribution. 

Can you provide me with the Footprint for the CC2564BYFVR BGA ?

Thank you for your time.

Have a great day!

Regards,

Ed Watts

Weastone Bridge MS1451 Pressure Sensor adaptation with Microcontroller

$
0
0

Hello TI people, 

Long time not to come here looking for your great help. In this occasion i need to use this pressure sensor with a microcontroller which on it ADC pins drives a voltage range between 0 to 3.6V, but i dont know which is the best way to adapt them. So i would like you can help me this, i was reading about to use a differential amplifier circuit with a filter and the an ADC conversor; but really i am a little confuse.

Thansk for your attention,

Ricardo R

LP8861-Q1: LED driver output circuit, can you parallel the outputs?

$
0
0

Part Number:LP8861-Q1

this LED driver is a current source, it has 4 channels of 100mA each.  QUESTION:  can you tie the outputs together to get one 400mA current sink instead of 4 channels of 100mA??


TPS65982-HIUTILITY: The Source Capabilities register shows the power paths incorrectly and therefore the user may operate it incorrectly.

$
0
0

Part Number:TPS65982-HIUTILITY

I'm using the latest version (2.3 - July 2016) of the TPS6598x Host Interface tool. I'm connected through an Aardvark to my TPS65982.

Under the "PP Switch for PDO#" field for any of the PDOs is a list of four paths:

PP_5V internal
PP_5V internal
PP_HV internal
PP_HVE external.

However, if you select the 2nd, you get PP_HV, if you select the 3rd you get PP_5V. I have tested this with voltages and this is how it works. The Appl Customization tool has some misleading info in the Switch Source pulldowns for setting up this field, it shows the PP_5V0 choices as (00b) and (01b). In reality they are really (00b and 10b). The Appl. Customization tool correctly sets up the paths during image creation (I think), but the 01/10 and the order is incorrect. If you look at the slvuan1 HostTechRefManual that describes these bits in the register it says in Table 3-16, the 0x32 TX Source... register that Byte 3 has the following bits:
0 - controls PP_5V0 on/off. If 0, then PP_5V0 is the PDO0, if 1 then PP_EXT is PDO0.
1 - IFF bit 0 = 1, then this selects between PP_HV and PP_EXT.
So, 00 = PP_5V0, 10= PP_5V0, 01 = PP_HV, 11 = PP_EXT.
This is how the TPS65982 operates, so the AppCustom Tool is misleading and the Host Interface tool labels are incorrect, then 2nd (presumably 01) says PP_5V but really selects HV and the 3rd (presumably 02) says PP_HV but really selects PP_5V.

Warren

CC2564MODN: RED Compliance

TPS65982-HIUTILITY: In the TPS6598x Host Interface Tool the USBEPenable and USBRPenable selections are flipped

$
0
0

Part Number:TPS65982-HIUTILITY

In the System Config register (0x28) there are two checkboxs for USBEPenable and USBRPenable.
Most users it seems from the discussions have these bits both enabled. However, version 2.3 of this tool shows and controls these bits incorrectly.
The EP allows the TPS65982 to respond as an endpoint for Billboard requests, and the RP allows an external device to be attached to provide the billboard information. The EP takes precedence (I think).

If I select only EP in the AppCustomization tool then in the RAW view of Register 28, byte 13 = xxxx-x10x,
with RP selected byte 13 = xxxx-x01x,
both selected byte 13 = xxxx-x11x.

Now if you download the image to the TPS65982 with only one selected and then look in the system config register you will find that the Opposite one is checked.
I can read this register over I2C and see that even though it says RP, it really is the EP bit as the AppCustomization tool says.
If you don't look at or use the Host Interface tool it doesn't matter that the wrong bit is checked. But if you use the tool and check USBEPenable, you will enable RP and vice versa.

I found out the hard way when I was trying to get the billboarding working and only figured this out after making a few images and tracking the HostInterface reporting with what I had setup in the AppCustomization tool. I found out that it was flipped and confirmed it by reading the register over I2C with my own interface.

Bottom line I found that I could leave both bits checked and it looks like the EP overrides the RP selection.
But I don't know if this is completely safe.

Warren

LMR64010: SOT23-5 package support max load current (1A)?

$
0
0

Part Number:LMR64010

My Input is 5V and output is 12V. What component changes I would required in order to support max load current at output? I believe I need to change inductor value but not sure to what value.  Currently I am using exactly same design on page 11 (figure 19) on datasheet.

-Thanks 

Maulik Patel

SN74LVC2G17: How will this part handle slow input rise time?

$
0
0

Part Number:SN74LVC2G17

The input rise time that we are seeing into the device is in the range of 600ns.

PCIE reset signal is the input and the output resets a NIC and FPGA.

Viewing all 262198 articles
Browse latest View live


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