Part Number:TPS92075
Hello,
I just powered on my new 230Vac board that uses TPS92075.
This is schematic:
On output there are 4 LED (series, 3Vx4 = 12V), Rsense is 0.95ohm to reach ~500mA
Main problem is that LED current is ~3mA (Voltage on Rsense is ~4mV)
Minor issue is that LED are turning on after 2-3 seconds
What can I check?
I don't need to dimmer it, there are some component that are controlling triac dimmer? Can I remove them?
Thank you a lot
Part Number:UCC28180
I am investigating the UCC28180. This IC has no Ac line Sense.
The IC can measure the line current and the PFC Output Voltage (Vsense). The measurement point of Vsense is just after the PFC diode where a smoothening capacitor is placed. This means that at this point the input Ac line phase information is lost.
If the IC knows nothing abaout the input Ac line Voltage phase position, how will it be possible that the input current is synchronised with the input AC voltage?
Any app-note describing how the average current mode control of PFC without Ac line sense works is appreciated.
Part Number:TPS650864
Dears:
There are two questions about it.
1. Can we only use IIC to control the power up timing and output voltages?
2. Are there any default output voltages about the new chip? Or need to flash firmware by our-self?
Pls. kindly help!
Part Number:TDC7201-ZAX-EVM
Tool/software: TI-RTOS
I have successfully connected TDC7201GUI, but I have been unable to start measurement. My signal generator is not tektronix but DDS. Is there any difference between taike's INPUT and DDS's EXIT (IN)? DTG_TRIGG must be used?
Tool/software: TI-RTOS
Hi, TI!
Could you help me with my issue.
When i copied all fails SYSbios in RAM (D01SARAM) , code in cmd SECTION i have trouble with My main function it isnt launch. 0x3FE2EE (no symbols are defined)
I have memcopy function in begin of main but TMS didnt go to start of the main. May be i nedd to paste memcopy function to other place?
Whan i deleted section of copy SysBios , TMS starts ok.
SECTION
{
.knl: { *.*(.text:*ti_sysbios_knl*) } LOAD = FLASH,
RUN = D01SARAM, /* must be CSM secured RAM */
LOAD_START(_knlramFuncs_loadstart),
LOAD_END(_knlramFuncs_loadend),
RUN_START(_knlramFuncs_runstart)
PAGE = 0, ALIGN(8)
.hwi: { *.*(.text:*ti_sysbios*_Hwi_*) } LOAD = FLASH,
RUN = D01SARAM, /* must be CSM secured RAM */
LOAD_START(_HwiramFuncs_loadstart),
LOAD_END(_HwiramFuncs_loadend),
RUN_START(_HwiramFuncs_runstart),
PAGE = 0, ALIGN(8)
.sysbios: { *.*(.text:*ti_sysbios*) } LOAD = FLASH,
RUN = D01SARAM, /* must be CSM secured RAM */
LOAD_START(_sysbiosramFuncs_loadstart),
LOAD_END(_sysbiosramFuncs_loadend),
RUN_START(_sysbiosramFuncs_runstart),
PAGE = 0, ALIGN(8)
}
Part Number:AM3359
I'm trying to understand why the PRU pins go high when the remoteproc driver is loaded (without running any firmware). I have the following pins routed to PRU0:
&pruss_soc_bus {
status = "okay";
pruss: pruss@0 {
status = "okay";
pinctrl-names = "default";
pinctrl-0 = <&pru0_pins_default>;
};
};
...
pru0_pins_default: pru0_pins_default {
pinctrl-single,pins = <
AM33XX_IOPAD(0x99c, PIN_OUTPUT_PULLUP | MUX_MODE5) /* (C12) mcasp0_ahclkr.pr1_pru0_pru_r30[3] */
AM33XX_IOPAD(0x9a0, PIN_OUTPUT_PULLUP | MUX_MODE5) /* (B12) mcasp0_aclkr.pr1_pru0_pru_r30[4] */
AM33XX_IOPAD(0x9a4, PIN_OUTPUT_PULLUP | MUX_MODE5) /* (C13) mcasp0_fsr.pr1_pru0_pru_r30[5] */
AM33XX_IOPAD(0x9a8, PIN_OUTPUT_PULLDOWN | MUX_MODE5) /* (D13) mcasp0_axr1.pr1_pru0_pru_r30[6] */
AM33XX_IOPAD(0x9ac, PIN_OUTPUT_PULLDOWN | MUX_MODE5) /* (A14) mcasp0_ahclkx.pr1_pru0_pru_r30[7] */
AM33XX_IOPAD(0x830, PIN_OUTPUT_PULLDOWN | MUX_MODE6) /* (T12) gpmc_ad12.pr1_pru0_pru_r30[14] */
AM33XX_IOPAD(0x834, PIN_OUTPUT_PULLDOWN | MUX_MODE6) /* (R12) gpmc_ad13.pr1_pru0_pru_r30[15] */
AM33XX_IOPAD(0x8fc, PIN_OUTPUT_PULLDOWN | MUX_MODE5) /* (V13) mmc0_dat0.pr1_pru0_pru_r30[11] */
AM33XX_IOPAD(0x838, PIN_INPUT_PULLDOWN | MUX_MODE6) /* (V13) gpmc_ad14.pr1_pru0_pru_r31[14] */
AM33XX_IOPAD(0x83c, PIN_INPUT_PULLDOWN | MUX_MODE6) /* (U13) gpmc_ad15.pr1_pru0_pru_r31[15] */
AM33XX_IOPAD(0x9b4, PIN_INPUT_PULLDOWN | MUX_MODE5) /* (D14) xdma_event_intr1.pr1_pru0_pru_r31[16] */
>;
};
My PRU firmware is loaded correctly and controls the pins fine once it runs. However there is some time (around 100ms) between loading the remoteproc driver and starting the PRU firmware when the above pins go high. Not sure if all of them but I have LEDs connected to 3 of them and they light up right after the remoteproc driver was loaded. The weird thing is that I see the LEDs flashing fast when that happens. My firmware turns off the LEDs immediately. So the pins are low before remoteproc is loaded and go high when remoteproc is loaded.
I also compiled remoteproc as a module and loaded it manually so I am able to reproduce the above behavior: just modprobe the pru modules manually without starting my firmware will cause the LEDs to light up. Once I start my firmware (echo 'start' > ...) the LEDs will go off.
If I don't load remoteproc at all and don't start the PRU then the LEDs stay off as expected.
Is it a normal behavior that the PRU pins go high when the remoteproc driver discovers the PRUs? Is it doing some sort of reset of the PRUs and toggles high all its pins? Is there a way to prevent this behavior and keep them low (or as defined in the dts file - pulldown or pullup)?
Many thanks and let me know if you need more details about this issue.
Part Number:LP8725
Hello,
We are not using BUCK1 in our application (i.e. FB1 (pin E4), SW1 (pin E5)). Nonetheless, we have an inductor and capacitor fitted to this output as it is initially enabled at start-up, and we were unsure of the ramifications of removing these output passives.
Kind regards,
Gerry
Part Number:PGA970
Tool/software: Code Composer Studio
Hi, I need help with the firmware of the internal microcontroller of PGA970.
I want to design a simple firmware which sends data of demodulator 1 to the combuf every time the ADC triggers an interrupt (that is every 128 or 256 us, depending on settings).
I observed that in the reference firmware only 16 bits of the demodulator data are read, nevertheless useful data are 24-bits long.
Is it possible to read the 8 bits missing?
In the reference firmware the code used to tread 16 data bits is the following one:
interrupt void ADC_Handler(void)
{
demod1 = DEMOD1_DATA; //read 16b ADC1 value
demod2 = DEMOD2_DATA;
}
...
where DEMOD1_DATA is defined as (*((VSL *)0x40000410))
Using this code and sending demod1 to the combuf I car read data with an external microcontroller without any problem. Nevertheless, I did not suceed in reading the remaining ADC bits.
I tried to use the same code, but substituting DEMOD1_DATA with (*((VSL *)0x40000412)) in order to get the missing bits, but now the firmware seems freezing and does not send any data to the combuf.
I do not understand which is the problem. Can you please tell me how to read the entire set of 24 bits from the demodulator?
Thank you in advance for your time,
Regards,
Alessandro
Part Number:LM36923H
Quick question concerning the LM36923H and LM36274 modes of operational:
from a control perspective, the desire is to control this with I2C.
If there is a better part to recommend for the above objectives, see design parameters:
VIN range: 2V-3V
Vout: 6.5V max – single UV LED (per channel)
Iout: 50mA max per channel
Hello,
I am getting the same error 'Could not launch TI cloud agent'. I tried steps in troubleshooting guide, but still not able to figure out the problem. I am using Firefox version 65.0.2 (64 bit).
Part Number:TMS320C6657
Tool/software: Code Composer Studio
Hello!
I hawe next question: in while program processing was started very long transmission through DMA channel and it became necessary to stop current DMA transmission.
How can I do that?
Thank you!
Part Number:IWR6843
Hi all!
We want to lower the power consumption of the radar for a specific application. In the future for this application the radar will be stand alone but for the testing at the moment we're using mmWave Studio to have easy access to many parameters.
I saw the power consumption sheet and tested those main parameters which do reduce the power consumption. But we're trying to understand if any of the many other parameters accessible in the mmWave Studio would help with this task, getting the power to even lower levels?
Unfortunately playing around with them didn't really give any results but I am convinced there are many I don't understand fully so insight would be appreciated!
Kind regards and thank you,
Beate
Part Number:EV2400
Hi Support team
My customer is trying to get EV2400 to run on Windows 10. Have we released the latest code for windows 10, and if not when will it be released>
Regards
Jeff Coletti
Part Number:TSC2004
We executed the ESD tests by discharging +/-8kV (air discharge) on a 5" TFT display with integrated resistive touch screen.
The touch screen controller was the TSC2004IRTJR, which should be protected up to +/-25kV (air gap), +/-12kV (contact) and +/-8kV (HBM).
The TSC2004IRTJR melted after 10 - 15 discharges.
A ESD has not sufficient energy to melt a TSC2004. Maybe the ESD triggered something (latchup?) that allows high current from the 3.3V supply.
Could you please help us in finding what was wrong?
Thank you in advance.
Best regards.
Part Number:TMS320F280049
Champs,
I am asking this for our customer.
The user got a warning under MISRA-C 2004 Rule 10.1 when using driverlib like below.
#1393-D (MISRA-C:2004 10.1/R) The value of an expression of integer type shall not be implicitly converted to a different underlying type if it is not a conversion to a wider integer type of the same signedness
The user’s codes are like these:
1. DEVICE_DELAY_US(1000);
2. HWREG_BP(base + CAN_O_IF2CMD) = CAN_IF2CMD_TXRQST | (objID & CAN_IF2CMD_MSG_NUM_M);
3. HWREG_BP(base + CAN_O_IF1CMD) = CAN_IF1CMD_CLRINTPND | (intClr & CAN_IF1CMD_MSG_NUM_M);
4. HWREG_BP(base + CAN_O_IF1CMD) = CAN_IF1CMD_CONTROL | (objID & CAN_IF1CMD_MSG_NUM_M);
5. CMPSS_configRamp (CMPSS1_BASE, (U16)(0xFFFF), Can_Rx_315h_Data.Buck_Slope_Ramp_Dec_Val_Shadow_Set_U16, (U16)(0x0), (U16)(2), true);
6. EPWM_setDeadBandOutputSwapMode(EPWM1_BASE, EPWM_DB_OUTPUT_A, false);
7. EPWM_setDeadBandDelayMode(EPWM1_BASE, EPWM_DB_RED, false);
Our questions are:
1) Does this warning mean the user should have “explicit casting”?
2) Do you have any suggestion how the user can modify his codes to avoid this warning?
3) Is it possible the warning is from the underlying drivelib? Is our driver lib compliant to MISRA-C 2004?
Wayne Huang
Part Number:DAC8806
I am driving my DAC8806 with an FPGA at 3.3v. Last week a GPIO pin on the FPGA quit working. It is connected directly to pin28(reset) on the DAC8806. I thought nothing of it as the FPGA has gone through a year of testing. I replaced the FPGA and through some more use, the same pin on the FPGA went bad in one day. That run on my PCB goes from pin to pin with no vias.
My configuration is as follows, I have a THS4011 connected directly to the DAC8806 as per your PDF. The THS4011( at -9v to +9v) then drives a OPA552(-9v to +40v). It all looks good under Tina.
VREF on the DAC8806 is -9v.
My goal is to generate what looks like a modified version of the upper part of a 0-30v sine wave or "mountain range". Since I can code 0V, do I really need the reset pin?
Do you have any idea as to why the DAC8806 kills my GPIO pin? I looked at it with an O-scope. and there is a little jitter at that pin when I turn the system on and off.
At $100 each for the FPGA, it can get expensive.
Thanks.
Regards,
Doug
Part Number:TMS320F28379D
Tool/software: TI C/C++ Compiler
Is there a way to pass a pointer to an ISR that's passed when the ISR is called?
I have a working solution. Though, it would be nice to avoid global objects when using C++ classes and ISRs.
If not, is there a mechanism to request this feature?
Kindly,
Graham
Part Number:TM4C1294KCPDT
Tool/software: Code Composer Studio
Hi to you all,
I am trying the I2C0 of the TM4C1294KCPDT to send data for 12-bit DAC ( MSP4725 Evaluation board from Microchip) to get familiar with the microcontroller hardware interfaces.
Setting are:
I2C: SCL--> PortB pin2
SDA--> PortB pin3
speed 100kbps or 400kbps
Slave (MSP4725) address is 0xC0.
VDD: 3.3V
I can see on the oscilloscope that the I2C send the address 0x80 instead of 0xC0 and this causes the communication to stop as the slave wasn't selected.
I tried the MSP4725 evaluation board with the PICkit Serial analyser and the board worked as intended as I could change the voltage of the DAC output as needed.
It seems to the I2C of the TM4C1294 is at fault.
Pickit Serial Analyser: https://www.microchip.com/Developmenttools/ProductDetails/DV164122:
MSP4725 evaluation board: http://ww1.microchip.com/downloads/en/devicedoc/51669a.pdf
I am a bit surprise that the I2C didn’t work. Can anyone help me please?
Below is the simple example:
//*****************************************************************************
//
// main()
//
//*****************************************************************************
int
main(void)
{
static uint32_t ui32SysClkFreq, u32GetClock;
ui32SysClkFreq = SysCtlClockFreqSet((SYSCTL_XTAL_25MHZ |
SYSCTL_OSC_MAIN | SYSCTL_USE_PLL |
SYSCTL_CFG_VCO_480), 120000000);
SysCtlPeripheralEnable(SYSCTL_PERIPH_I2C0); // enable I2C0
while(!SysCtlPeripheralReady(SYSCTL_PERIPH_I2C0));
SysCtlPeripheralReset(SYSCTL_PERIPH_I2C0); // Reset I2C0
while(!SysCtlPeripheralReady(SYSCTL_PERIPH_I2C0)) ;
SysCtlPeripheralEnable(SYSCTL_PERIPH_GPIOB); // enable portB (pin_B3 and Pin B2) for I2C0
SysCtlPeripheralEnable(SYSCTL_PERIPH_GPION); // Enable portN for LED for debugging
// Configure SDA o PORTB PIN3
GPIOPinConfigure(GPIO_PB3_I2C0SDA);
GPIOPinTypeI2C(GPIO_PORTB_BASE, GPIO_PIN_3);
// Configure SCL o PORTB PIN2
GPIOPinConfigure(GPIO_PB2_I2C0SCL);
GPIOPinTypeI2CSCL(GPIO_PORTB_BASE, GPIO_PIN_2);
// Configure PORTN PIN0 and PIN1 as output
GPIOPinTypeGPIOOutput(GPIO_PORTN_BASE, GPIO_PIN_0|GPIO_PIN_1); // debug
//Set I2C clock and speed to 100Kbps
I2CMasterInitExpClk(I2C0_BASE,SysCtlClockGet(),false); // tried this
// I2CMasterInitExpClk(I2C0_BASE,ui32SysClkFreq,false); // a120Mhz
while(I2CMasterBusy(I2C0_BASE));
I2CMasterSlaveAddrSet(I2C0_BASE,0xC0,false); set slave address
I2CMasterControl(I2C0_BASE,I2C_MASTER_CMD_BURST_SEND_START);
I2CMasterDataPut(I2C0_BASE,0x0A); // send the DAC’s 4 MSB bits
I2CMasterControl(I2C0_BASE,I2C_MASTER_CMD_BURST_SEND_CONT);
while(I2CMasterBusy(I2C0_BASE));
I2CMasterDataPut(I2C0_BASE,0xAA); // send the DAC’s 8 LSB bits
I2CMasterControl(I2C0_BASE,I2C_MASTER_CMD_BURST_SEND_FINISH);
while(I2CMasterBusy(I2C0_BASE));
I2CMasterControl(I2C0_BASE,I2C_MASTER_CMD_BURST_SEND_STOP);
GPIOPinWrite(GPIO_PORTN_BASE, GPIO_PIN_0|GPIO_PIN_1, 3);
while(1)
{
SysCtlDelay(ui32SysClkFreq / (3 * 5) );
GPIOPinWrite(GPIO_PORTN_BASE, GPIO_PIN_0, 1);
SysCtlDelay(ui32SysClkFreq / (3 * 5) );
GPIOPinWrite(GPIO_PORTN_BASE, GPIO_PIN_0, 0);
}
}
