Part Number: TPS54160
Hi,
What is the cause of load regulation and line regulation?
I can see a slightly Vout drop, for example, set Vout 3.3V, but test Vout 3.28V. Firstly i thought it is the probe resistance between Vout test point and electronic load.
When i google it, find out it's also related to control loop. Maybe the EA? i'm not sure about it, so i need your help.
Or you can send me some learning resources to my e-mail: mason-liu@ti.com.
Thanks.
Best regards
Mason Liu
Part Number: DRV8313
Hi Team,
PGND is recommended to connect with GND when there is no Rsense. I have two questions, could you please hep explain? Thanks!
1. What are the risks when PGND is not connected to GND? Because several pieces are damaged when doing so by accident.
2. What's the internal connection between PGND and GND? Because the measured resistance between PGND and GND is 3 ohms with DRV8313 only, it seems that PGND and GND is connected internally, why is it designed like this?
Best Regards!
Hao
Part Number: TMS320F28035
Hello,
We are seeking application notes and/or code snippets exemplifying the implementation of security measures making use of CSM and ECSL features to prevent code decompilation both for TMS320F28035 and TMS320F28379D.
Thanks.
EMe.
Part Number: TPS2561
Team,
One of my customer's application needs following:
USB Type-C DFP controller supporting USB 2.0
Two ports
Current limit of 700mA on each port
Do we have any example schematic for connecting TPS2561 with USB 3.0 DFP controller? The EVM schematic shows only TPS2561 device.
Thank you in advance.
Regards,
Sanjay R. Pithadia
Part Number: LMX2594
hi all,
I have two lmx2594 chips in my system and i want to have the outputs phase aligned,how can i use the pin?can you give me some design example?
Now my usage as follows,the sync pin of both lmx2594 i connect together and then i directly connect them to fpga.I didn't know whether my usage is right or wrong.Is there anything i need to pay attention to when using this function?
Thanks.
Part Number: PMLKBUCKEVM
Hi,
Currently i'm doing the experiment 1 test 1, Vin 24V, Vout 3.3V, Iout change from 0.1A to 1.5A.
i find when the Iout is lower than 0.7A, the Vsw will show some weird waveform. shown below.
Iout=0.1A
Iout=0.5A
In the Iout=0.1A image, i think maybe TPS54160 is in ECO-mode. But what cause the ringing in the red circle?
In the Iout=0.5A image, what cause the Vsw is high in the red circle?
Thanks.
Best regards
Mason Liu
Part Number: CC2540
We are currently implementing OAD Firmware updates for our Apps and Windows software and have discovered very odd behavior. We use custom boards with a CC2540 and on some of them the OAD update fails due to potential connection timeouts (I've attached sniffer logs to verify this).
All of the boards we are using are identical and we can successfully update all of them using the TI iOS App and also our own iOS/Android Apps. Right now it seems like only the Windows implementation has this problem and only on some devices (even though all of them are identical).
Here is what happens:
The device connects successfully and the OAD Header gets send to the device. The device answers by requesting the first Block via the Block Characteristic. Then the Windows App sends the first block of data. Now nothing happens and after 10secs the device disconnects and reconnects to repeat these steps indefinitely. This seems like the connection times out because to default connection timeout matches those 10secs.
Using the sniffer it seems like the device drops the connection. I've attached sniffer logs of the same code and firmware running on two different devices. On the first one it times out and on the second one it doesn't. Same firmware, same windows app, just different boards but both boards can be updated using the TI App or out own Apps.
I guess my question is, am I right in assuming the device drops the connection? And if yes how is it possible that the windows App causes the device to disconnect? I don't think there is a hardware malfunction since all boards can be updated via one method. Right now only the OAD Update on Windows causes this. The odd thing is, it seems like the device causes the timeout but the windows app causes this problem to occur, how can this be?
This is the sniffer log for the time out. The first ATT_Write_Req is the header, the device answers by requesting block 0, then the ATT_Write_Command with Block 0 and then nothing but M -> S with no response from the device:
And this is a working case but here the device answers by requesting block 01 and so on. There seems to be a little bit of a
Part Number: TPS54202
We have some prototype boards that have a TPS54202 power supply on them. The TPS4202 doesn't work on one of the boards and I'm still looking into the reason why. So far, the only problem I've found is that the EN line is pulled up to 24v with a 470k resistor. The voltage on the EN line measures 6.8v, which is just below the absolute max of 7v from the datasheet.
We were originally using the TPS563208, which has a built-in zener. We raised the VIN from 12v to 24 and had to remove the old power supply and go with the TPS54202 at the last minute. I didn't catch the change in EN pins between the two switchers. The datasheet for the TPS54202 doesn't mention having an internal clamp on that pin, so I'm wondering if I may have damaged it and that might be why it isn't starting up.
Dear TI Experts,
Anybody can suggest a GAN based reference design from TI which matches or closely matches the Below specification
Input voltage: 400VDC
Output voltage: 35V to 60V
Output Power: 2KW
Isolation required:Yes
Regards
Aneesh
Part Number: DS90UB949-Q1
Hi ,
i am using DS90UB949-Q1 ( 1080p HDMI to FPD-Link III Bridge Serializer ) in my application.i need some clarification on hardware design.
for pin name VTERM ( pin number 57) which connection need to provide? (Can u explain briefly)
3.3V (DC coupled) or 1.8V (AC coupled)? i am referring Typical Application Connection -- Coax (fig 26 in the datasheet)
Best regards,
Mahesh
Part Number: TMS320F28335
Tool/software: Code Composer Studio
Hello,
I have a problem that I was wondering could be solved. I am using an F28335 micro and an XDS100v2 JTAG emulator to log data to a file on my computer using the fprintf function. This all seems to be working fine. However, sometimes the JTAG loses power briefly. Since this logging is all mostly unsupervised, the code will continue running but will not be able to fprintf to a file since the JTAG is no longer connected. I am wondering if there is a way to load code onto the micro that can test when the JTAG is connected or maybe if an fprintf has been successfully executed, so it can go into an error state if not.
Thanks for any advice you can give.
Colin
Part Number: CC1310
Tool/software: Code Composer Studio
hi everyone,
I use the rfEasyLinkEchoTX/RX Routine test,I can use 5K mode on launchpad, but I cannot use 5K mode on 7 * 7 chip. What is the reason?
This is my smartRF_setting：
//*********************************************************************************
// Parameter summary
// Address: off
// Address0: 0xAA
// Address1: 0xBB
// Frequency: 868.00000 MHz
// Data Format: Serial mode disable
// Deviation: 5.000 kHz
// Packet Length Config: Variable
// Max Packet Length: 128
// Packet Length: 20
// RX Filter BW: 49 kHz
// Symbol Rate: 19.99969 kBaud
// Sync Word Length: 32 Bits
// TX Power: 14 dBm (requires define CCFG_FORCE_VDDR_HH = 1 in ccfg.c, see CC13xx/CC26xx Technical Reference Manual)
// Whitening: No whitening
#include <ti/devices/DeviceFamily.h>
#include DEVICE_FAMILY_PATH(driverlib/rf_mailbox.h)
#include DEVICE_FAMILY_PATH(driverlib/rf_common_cmd.h)
#include DEVICE_FAMILY_PATH(driverlib/rf_prop_cmd.h)
#include <ti/drivers/rf/RF.h>
#include DEVICE_FAMILY_PATH(rf_patches/rf_patch_cpe_sl_longrange.h)
#include DEVICE_FAMILY_PATH(rf_patches/rf_patch_rfe_sl_longrange.h)
#include DEVICE_FAMILY_PATH(rf_patches/rf_patch_mce_sl_longrange.h)
#include "smartrf_settings.h"
// TI-RTOS RF Mode Object
RF_Mode RF_prop =
{
.rfMode = RF_MODE_PROPRIETARY_SUB_1,
.cpePatchFxn = &rf_patch_cpe_sl_longrange,
.mcePatchFxn = &rf_patch_mce_sl_longrange,
.rfePatchFxn = &rf_patch_rfe_sl_longrange,
};
// Overrides for CMD_PROP_RADIO_DIV_SETUP
static uint32_t pOverrides[] =
{
// override_use_patch_simplelink_long_range.xml
// PHY: Use MCE RAM patch, RFE RAM patch
MCE_RFE_OVERRIDE(1,0,0,1,0,0),
// override_synth_prop_863_930_div5_lbw60k.xml
// Synth: Set recommended RTRIM to 7
HW_REG_OVERRIDE(0x4038,0x0037),
// Synth: Set Fref to 4 MHz
(uint32_t)0x000684A3,
// Synth: Configure fine calibration setting
HW_REG_OVERRIDE(0x4020,0x7F00),
// Synth: Configure fine calibration setting
HW_REG_OVERRIDE(0x4064,0x0040),
// Synth: Configure fine calibration setting
(uint32_t)0xB1070503,
// Synth: Configure fine calibration setting
(uint32_t)0x05330523,
// Synth: Set loop bandwidth after lock to 60 kHz
(uint32_t)0x40410583,
// Synth: Set loop bandwidth after lock to 60 kHz
(uint32_t)0x32CC0603,
// Synth: Set loop bandwidth after lock to 60 kHz
(uint32_t)0x00010623,
// Synth: Configure VCO LDO (in ADI1, set VCOLDOCFG=0x9F to use voltage input reference)
ADI_REG_OVERRIDE(1,4,0x9F),
// Synth: Configure synth LDO (in ADI1, set SLDOCTL0.COMP_CAP=1)
ADI_HALFREG_OVERRIDE(1,7,0x4,0x4),
// Synth: Use 24 MHz XOSC as synth clock, enable extra PLL filtering
(uint32_t)0x02010403,
// Synth: Configure extra PLL filtering
(uint32_t)0x00108463,
// Synth: Increase synth programming timeout (0x04B0 RAT ticks = 300 us)
(uint32_t)0x04B00243,
// override_synth_disable_bias_div5.xml
// Synth: Set divider bias to disabled
HW32_ARRAY_OVERRIDE(0x405C,1),
// Synth: Set divider bias to disabled (specific for loDivider=5)
(uint32_t)0x18000200,
// override_phy_rx_aaf_bw_0xd.xml
// Rx: Set anti-aliasing filter bandwidth to 0xD (in ADI0, set IFAMPCTL3[7:4]=0xD)
ADI_HALFREG_OVERRIDE(0,61,0xF,0xD),
// override_phy_gfsk_rx.xml
// Rx: Set LNA bias current trim offset to 3
(uint32_t)0x00038883,
// Rx: Freeze RSSI on sync found event
HW_REG_OVERRIDE(0x6084,0x35F1),
// override_phy_gfsk_pa_ramp_agc_reflevel_0x14.xml
// Tx: Configure PA ramping setting (0x41). Rx: Set AGC reference level to 0x14.
HW_REG_OVERRIDE(0x6088,0x4114),
// Tx: Configure PA ramping setting
HW_REG_OVERRIDE(0x608C,0x8213),
// override_phy_long_range_dsss2.xml
// PHY: Configure DSSS SF=2
HW_REG_OVERRIDE(0x505C,0x0100),
// override_phy_rx_rssi_offset_5db.xml
// Rx: Set RSSI offset to adjust reported RSSI by +5 dB
(uint32_t)0x00FB88A3,
// TX power override
// Tx: Set PA trim to max (in ADI0, set PACTL0=0xF8)
ADI_REG_OVERRIDE(0,12,0xF8),
(uint32_t)0xFFFFFFFF,
};
// CMD_PROP_RADIO_DIV_SETUP
// Proprietary Mode Radio Setup Command for All Frequency Bands
rfc_CMD_PROP_RADIO_DIV_SETUP_t RF_cmdPropRadioDivSetup =
{
.commandNo = 0x3807,
.status = 0x0000,
.pNextOp = 0, // INSERT APPLICABLE POINTER: (uint8_t*)&xxx
.startTime = 0x00000000,
.startTrigger.triggerType = 0x0,
.startTrigger.bEnaCmd = 0x0,
.startTrigger.triggerNo = 0x0,
.startTrigger.pastTrig = 0x0,
.condition.rule = 0x1,
.condition.nSkip = 0x0,
.modulation.modType = 0x1,
.modulation.deviation = 0x14,
.symbolRate.preScale = 0x5,
.symbolRate.rateWord = 0x1111,
.rxBw = 0x21,
.preamConf.nPreamBytes = 0x2,
.preamConf.preamMode = 0x0,
.formatConf.nSwBits = 0x20,
.formatConf.bBitReversal = 0x0,
.formatConf.bMsbFirst = 0x0,
.formatConf.fecMode = 0x8,
.formatConf.whitenMode = 0x0,
.config.frontEndMode = 0x0,
.config.biasMode = 0x1,
.config.analogCfgMode = 0x0,
.config.bNoFsPowerUp = 0x0,
.txPower = 0xA73F,
.pRegOverride = pOverrides,
.centerFreq = 0x0364,
.intFreq = 0x8000,
.loDivider = 0x05,
};
// CMD_FS
// Frequency Synthesizer Programming Command
rfc_CMD_FS_t RF_cmdFs =
{
.commandNo = 0x0803,
.status = 0x0000,
.pNextOp = 0, // INSERT APPLICABLE POINTER: (uint8_t*)&xxx
.startTime = 0x00000000,
.startTrigger.triggerType = 0x0,
.startTrigger.bEnaCmd = 0x0,
.startTrigger.triggerNo = 0x0,
.startTrigger.pastTrig = 0x0,
.condition.rule = 0x1,
.condition.nSkip = 0x0,
.frequency = 0x0364,
.fractFreq = 0x0000,
.synthConf.bTxMode = 0x0,
.synthConf.refFreq = 0x0,
.__dummy0 = 0x00,
.__dummy1 = 0x00,
.__dummy2 = 0x00,
.__dummy3 = 0x0000,
};
// CMD_PROP_TX
// Proprietary Mode Transmit Command
rfc_CMD_PROP_TX_t RF_cmdPropTx =
{
.commandNo = 0x3801,
.status = 0x0000,
.pNextOp = 0, // INSERT APPLICABLE POINTER: (uint8_t*)&xxx
.startTime = 0x00000000,
.startTrigger.triggerType = 0x0,
.startTrigger.bEnaCmd = 0x0,
.startTrigger.triggerNo = 0x0,
.startTrigger.pastTrig = 0x0,
.condition.rule = 0x1,
.condition.nSkip = 0x0,
.pktConf.bFsOff = 0x0,
.pktConf.bUseCrc = 0x1,
.pktConf.bVarLen = 0x1,
.pktLen = 0x14, // SET APPLICATION PAYLOAD LENGTH
.syncWord = 0x00000000,
.pPkt = 0, // INSERT APPLICABLE POINTER: (uint8_t*)&xxx
};
// CMD_PROP_RX
// Proprietary Mode Receive Command
rfc_CMD_PROP_RX_t RF_cmdPropRx =
{
.commandNo = 0x3802,
.status = 0x0000,
.pNextOp = 0, // INSERT APPLICABLE POINTER: (uint8_t*)&xxx
.startTime = 0x00000000,
.startTrigger.triggerType = 0x0,
.startTrigger.bEnaCmd = 0x0,
.startTrigger.triggerNo = 0x0,
.startTrigger.pastTrig = 0x0,
.condition.rule = 0x1,
.condition.nSkip = 0x0,
.pktConf.bFsOff = 0x0,
.pktConf.bRepeatOk = 0x0,
.pktConf.bRepeatNok = 0x0,
.pktConf.bUseCrc = 0x1,
.pktConf.bVarLen = 0x1,
.pktConf.bChkAddress = 0x1,
.pktConf.endType = 0x0,
.pktConf.filterOp = 0x0,
.rxConf.bAutoFlushIgnored = 0x0,
.rxConf.bAutoFlushCrcErr = 0x0,
.rxConf.bIncludeHdr = 0x1,
.rxConf.bIncludeCrc = 0x0,
.rxConf.bAppendRssi = 0x0,
.rxConf.bAppendTimestamp = 0x0,
.rxConf.bAppendStatus = 0x1,
.syncWord = 0x00000000,
.maxPktLen = 0x80, // MAKE SURE DATA ENTRY IS LARGE ENOUGH
.address0 = 0xAA,
.address1 = 0xBB,
.endTrigger.triggerType = 0x1,
.endTrigger.bEnaCmd = 0x0,
.endTrigger.triggerNo = 0x0,
.endTrigger.pastTrig = 0x0,
.endTime = 0x00000000,
.pQueue = 0, // INSERT APPLICABLE POINTER: (dataQueue_t*)&xxx
.pOutput = 0, // INSERT APPLICABLE POINTER: (uint8_t*)&xxx
};
This is my SmartRF studio setting:
Ask the engineer to help analyze the reason
Best regards,
lin shi chang
Part Number: ADS8684
Single ended , differential end sensing of analog signal processing with ADS8684 IC radio frequency noise impact on analog values nearly its frequency range 167MHZ
Part Number: DDC264EVM
I have a question about DDC264EVM. I've put a Silicon photodiode at Vin input and looking the output on the DDC264 Evaluation software. my question is that when we are using SiPD what's the effect of Resistors at the input and why they are used in the circuit? because in another question I asked about DDC264 and DDC232, your experts said that DDC have sufficient protection and don't need extra.
Part Number: 66AK2H14
Hello,
The 10GbE user's guide mentions in section 2.6 that the Physical Coding Sublayer supports Forward Error Correction (FEC). But section 3.5.9 PCSR Forward Error Correction Register (PCSR_FEC) describes the enable bits as "tbd".
Is this feature supported?
Thank you.
Best regards,
François.
Part Number: CC2642R
Hi,
I have created a characteristic which have read write notify and write with no response properties. I just want to transfer 240 bytes by writing on the write characteristic via mobile application and receive via BLE SoC.
But I am able to send/write only 90 bytes not more than that. I have tried the below config:
MAX_PDU_SIZE 255
Is there any other configuration is required for the same? If yes, Please let me know.
Part Number: DS25BR101
Hi I have purchase ds25br101.
I have seen device marking of component which I have purchased is 68EXj 2R101.
What does 68EXj indicates.in datasheet it is not specified.can you please let me know.
Part Number: CC2640R2F
Hello
I have read several topics about multi connection from one Central to several Peripheral devices, but still have some questions about such a process for BLE5 stack.
I'm using "simplelink_cc2640r2_sdk_3_10_00_15" SDK and my application is based on "SimpleCentral" example program that I modified to have an autonomous connection to one peripheral with a specific name that was discovered.
At this step all is OK and works perfectly.
My next step is to connect my Central device up to 3 peripherals at the same time to send commands and data.
I can't find a good solution for that.
Do someone can help me ?
Here is my progress and analyze :
- I start by calling "SimpleCentral_doDiscoverDevice()" which lists all the advertising Peripherals with the specific name I'm looking for (I don't use pairing and I dont want to use it)
- Then the main task receives SC_EVT_ADV_REPORT event which is processed by "ProcessAppMsg()" for each discovered Peripheral
- "ProcessAppMsg()" then updates global variables 'numScanRes' and 'scanList[]' with discovered Peripheral datas
- An SC_EVT_SCAN_DISABLED event is then received and processeg by ProcessAppMsg() indicating that scannoing process has ended
- On this event received, ProcessAppMsg() calls "SimpleCentral_doConnect()" to initiate the connection on the found Peripheral (infact, it calls the "GapInit_connect()" function from BLE5-Stack).
I tried to modify at this step by adding a loop to ask for all discovered Peripheral listed in 'scanList[]' but it seems that I only receive one time the next event which is GAP_LINK_ESTABLISHED_EVENT, processed by "ProcessGapMsg()". From my analyze and understanding, It is supposed to update the global variables 'connList[]' an 'numConn', but this is not the situation I observe.
Could someone help me and told me what is the best way to do into this project ?
THank you in advance for any help.
Best regards.Patrick
Part Number: TMS320F28388D
Tool/software: Code Composer Studio
Hi,
I am using ethernet ipc library by TI for communication between C28 and CM processer. I want to access the data send by Ethernet_sendPacket driverlib function. How can i access the data through ethernet?
Thanks,
Khushali Mehta.
Part Number: SN74CBTLV3257
Hi team,
When my customer using the device, the select pin voltage peak is about 3.8v, bottom is about -0.8v. Whether it has risks here? From the datasheet, it may can be 4.6v, -1.2v. Could you please help double check whether it has risks? Thanks.
