↧
TUSB214: More information about TUSB21* USB 2.0 Conditioner
↧
ADS131A04: Device only delivers 16bit values
Part Number:ADS131A04
Team,
my customer evaluates the device, but they only get 16bit values from the device instead of 24bit.
- M0 : IOVDD
- M1 : open
- M2 : GND
Registers:
- 0x0b = 0x78
- 0x0c = 0x32
- 0x0d = 0x01
- 0x0e = 0x2c
- 0x0f = 0x0f
Do you see any configuration fault?
Thanks!
↧
↧
RTOS/TM4C1294NCPDT: Using TI-RTOS from custom path
Part Number:TM4C1294NCPDT
Tool/software: TI-RTOS
Hi,
I am developing an embedded application on TM4C1294NCPDT using TI-RTOS V2.16. Compiler CCS v6.2.
I want to use TI-RTOS from custom path.
How can I make configuration in CCS to use custom path for TI-RTOS and TIVAWARE drivers ?
Regards,
Harshal
↧
LAUNCHXL-F28379D: communication problem for f28379D
Part Number:LAUNCHXL-F28379D
Dear all
I have ordered a LAUNCHXL-F28379D and I am trying to run an example project from control suit. My Code Composer Studio version is 7.4. The example is blinky_cpu01. Properties of the examplefile as follows;
Configuration: CPU1_RAM[ACTIVE]
Variant: TMS320F28329D
Connection: Texas Instruments XDS100V2usb debug prob
Linker commend file:2837x_RAM_lnk_cpu1.cmd
When I try to load te example program into DSP or verfy the connection from proporties, the following message is occured and loading is failed
Error connecting to the target:
(Error -151 @ 0x0)
One of the FTDI driver functions used during the connect
returned bad status or an error. The cause may be one or
more of: no XDS100 is plugged in, invalid XDS100 serial number,
blank XDS100 EEPROM, missing FTDI drivers, faulty USB cable.
Use the xds100serial command-line utility in the 'common/uscif'
folder to verify the XDS100 can be located.
(Emulation package 8.0.803.0)
Thank you for your attention, in advance.
Regards
Fahri
↧
TPA3113D2: about "DC detect fault"
Part Number:TPA3113D2
Hi everyone!
I have a question about "7.3.5 DC Detect" on the data sheet.
Currently, among the several boards, only one, the Fault signal is asserted 420 ms later. I recognize this as "DC Detect Fault".
question 1:
In order to check with the signal pin, what should be observed on the defective board and how should we identify the current office?
Question 2:
Is there an example of the waveform when this phenomenon "DC Detect Fault" occurs?
Question 3:
Is there a confirmation method so that good board, "DC Detect Fault" occurs?
Question 4:
Are there any supplementary explanation materials on "DC Detect Fault"?
Question 5:
Data sheet "7.3.5 DC Detect" description,
"To trigger the DC detect are show in table 2."
Is not this correct table 3?
Question 6:
Data sheet:
"Table 3. DC Detect Threshold" "Vin (mV, differential)"
Is this Vin an input signal such as LINP, LINN?
Or is it a speaker input such as OUTPL, OUTPN?
Please let me know if you have any information.
Best Regards
Shing
↧
↧
UCC28056: DC50V-300V in 385V 200W out
Part Number:UCC28056
Hi all,
I have heard that UCC28056 accepts DC input.
This is new issue.
From DC50V to 300V input and 385V 200W output, no digital control, only analog controller.
Between DC50V and DC150V input, no efficiency spec.
Between DC150V and DC300V input, efficiency 98% want.
UCC28056 can meet this?
↧
TPS65986: USB+DP to C dongle(adapter) can not enter ALT mode when the dongle(adapter) is in UFP mode. Help share the TUSB546EVM project file.
Part Number:TPS65986
Hi, Team
My customer project using our TPS65986 act as the USB+DP to C dongle(adapter) for the PC. the dongle(adapter) is to display the DP signal to the Type-C monitor using ALT mode.
Normally, the dongle(adapter) is in DFP and the monitor is in UFP. but customer found that if the monitor in DFP and the dongle(adapter) in UFP, the TPS65986 can not enter ALT success. pls check the attach file for more detail information.
BTW, customer using our TUSB546 EVM binary file to program the flash directly(see the bin file in attachment), so they didn’t have the project file.
And I also post the issue in e2e before(https://e2e.ti.com/support/interface/f/138/t/720275), BU share the TUSB546EVM project file to us, and help us change some configuration(add DR_SWAP function) base on the TUSB546EVM project file.
But after check, all these 2 project file can not work. Also pls also notice that customer using the TUSB546EVM BIN file for projection, this BIN file size is 1M, but the new BIN file just 135K. so we think the new project file is not the same as former project file. Could u help to check and give some comments?
Thanks.
HSDC025A_Project.pjt: new TUSB546EVM project file, share by BU.
HSDC025A_Project_Modified.pjt: BU add the DR_SWAP function, base on HSDC025A_Project.pjt.
TUSB546EVMFlash.bin: original TUSB546EVM BIN file. This size is 1M. This file can operation normal except the SWAP function.
TUSB546 EVM 0906.bin: BIN file create from HSDC025A_Project.pjt. this size is 135K. TPS65986 can not operation normal, besides SWAP function.
TUSB546 EVM Modify 0906.bin: BIN file create from HSDC025A_Project_Modified.pjt. this size is 135K. TPS65986 can not operation normal, besides SWAP function.
/cfs-file/__key/communityserver-discussions-components-files/138/0702.TPS65986-issue.zip
/cfs-file/__key/communityserver-discussions-components-files/138/Project-and-BIN-file.zip
George.W
↧
AWR1642: AWR1642
↧
TIDA-01436: Compatability
Part Number:TIDA-01436
Can we use Beaglebone board instead of TMDSEVM437X for people counting.
↧
↧
TUSB4020BI: short test and open test
Part Number:TUSB4020BI
Our customer is designing their board of TUSB4020 and TUSB4041I.
They are requesting us all I/O pins short test and open test.
Could you have these test results?
Best Regards,
Y.Hirata
↧
Alternatives to ADM2587E - Isolated RS485 with DC/DC
Hello team,
I bumped into the ADM2587E on one of my customer's boards and was thinking if we have any product that could replace it.
Datasheet can be found here 
Do you have any suggestions?
Thank you and best regards,
Adrian
↧
LAUNCHXL-CC1352R1: how to select development mode in uniflash?
↧
CCS/CC2640R2F: Failed to update advertising data with uart
Part Number:CC2640R2F
Tool/software: Code Composer Studio
I'm using simple peripheral project to complete my own design and encounter an issue. Details below:
With uart task, the program receive data and update these data to advertising buffer, but it failed after create connection, enable notify and send data to HostTest board as well as updating advertising data.
I need to make it clear, only after enabling notify will lead to the problem, create connection or not has no influence on this issue.
codes:
//the callback function used by uart task
static void simple_peripheral_handleNPIRxMsg(uint8 *p, uint8 len)
{
uint8 temp[MAX_SIMPLEPROFILE_CHAR6_LEN]={};
//setAdv();
//setparameter();
memcpy(temp, p, len);
SC_Log_info1("parameter len %d",len);
SetAdvData(temp,len);
SimpleProfile_SetParameter(SIMPLEPROFILE_CHAR6, len, temp);/**/
SC_Log_info0("set parameter");
}static bool SetAdvData(uint8_t *pdata, uint8_t Len)
{
bStatus_t status = FAILURE;
if(Len > 80)
{
return false;
}
// Disable advertising and prepare the buffer.
status = GapAdv_prepareLoadByBuffer(advertData, FALSE);
SIMPLEPERIPHERAL_ASSERT(status == SUCCESS);
if(Len < 80)
{
for(uint8_t i = Len;i < 80;i++)
{
advertData[i] = 0;
}
}
for(uint8_t i = 0;i < Len;i++)
{
advertData[i] = pdata[i];
}
advertDataLength = Len + 1;
SC_Log_info0( "Ready to change advert data");
// Set event mask for set #2
status = GapAdv_setEventMask(advHandleLongRange,
GAP_ADV_EVT_MASK_START_AFTER_ENABLE |
GAP_ADV_EVT_MASK_END_AFTER_DISABLE |
GAP_ADV_EVT_MASK_SET_TERMINATED);
SIMPLEPERIPHERAL_ASSERT(status == SUCCESS);
status = GapAdv_loadByBuffer(advertDataLength, advertData);
SIMPLEPERIPHERAL_ASSERT(status == SUCCESS);
SC_Log_info2("Len: %d, change advert data: %s",advertDataLength,advertData);
return true;
}the log:
↧
↧
Linux/DP83848Q-Q1: DP83848Q-Q1 driver support on Linux 4.9.88
Part Number:DP83848Q-Q1
Tool/software: Linux
Hi All,
We are trying to support DP83848Q-Q1 PHY (RMII 100 MBPS)on NXP iMx8 based custom platform.
Linux kernel version : 4.9.88
We have modified pin configuration as per our custom platform and enabled "DP83848_PHY" in Linux kernel configuration (make menuconfig).
GPIO reset sequence is implemented for PHY to come out of reset. From the CRO probe, we have confirmed the clock, RMII Mode and reset states.
However, we found that PHY is not getting recognized in Linux.
Whether we can use PHY driver available in Linux (drivers/net/phy/dp83848.c) for DP83848Q-Q1 PHY?
Please provide your input.
Thanks and Regards,
Krishna
↧
TS3DV642: Can TS3DV642 support PCIE 5Gbps scenario?
↧
WEBENCH® Tools: Does XDS110 JTAG Debug Probe support MMW chip download program or debugging?Like IWR1443 or 1642.If supported them, Is there a driver package for debugging emulation?
Tool/software: WEBENCH® Design Tools
↧
BQ24640: BQ24640 support EDLC?
↧
↧
TMS570LC4357: EMAC Reset
Part Number:TMS570LC4357
Hello,
We would like to have more information about EMAC deactivation means.
The Reference manual mention in section 32.2.15.1 that "Unlike the EMAC module, the MDIO and EMAC control modules cannot be placed in reset from a register inside their memory map."
Nevertheless the EMAC control module seems to be in reset via the RESET bit in the SOFTRESET register (section 32.3.2) whereas the EMAC module is in reset via the SOFTRESET bit in the SOFTRESET register (section 32.5.34).
Could you precise us if each of these modules can be reset via the registers as described in registers section of reference manual ?
Best regards,
Christopher
↧
Compiler/CC2650: cc2650
Part Number:CC2650
Tool/software: TI C/C++ Compiler
hey i am using IAR (8.32.1 version) and ble stack 2_02_02_25
if can't able to download application i am getting following error please help to to solve it.
Building configuration: cc2650stk_app - FlashROM
Updating build tree...
Performing Pre-Build Action
Error while running "C:\ti\xdctools_3_32_00_06_core/xs" --xdcpath="C:\ti\tirtos_cc13xx_cc26xx_2_21_01_08\products\
tidrivers_cc13xx_cc26xx_2_21_01_01\packages;C:\ti\tirtos_cc13xx_cc26xx_2_21_01_08\products\bios_6_46_01_38\
packages" iar.tools.configuro -c "C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.2\arm" --cc "C:\Program
Files (x86)\IAR Systems\Embedded Workbench 8.2\arm\bin\iccarm.exe" --device "CC2650F128" --compileOptions
"dummy.c -D CC2650STK -D CC26XX -D Display_DISABLE_ALL -D EXCLUDE_AUDIO -D
EXCLUDE_FACTORY_RESET -D EXCLUDE_OAD -D GAPROLE_TASK_STACK_SIZE=440 -D
GATT_TI_UUID_128_BIT -D HEAPMGR_SIZE=0 -D ICALL_MAX_NUM_ENTITIES=11 -D ICALL_MAX_NUM_TASKS=8
-D POWER_SAVING -D USE_ICALL -D xdc_runtime_Assert_DISABLE_ALL -D xdc_runtime_Log_DISABLE_ALL
--diag_suppress Pa050 -o C:\ti\simplelink\ble_sdk_2_02_02_25\examples\cc2650stk\sensortag\iar\app\FlashROM\Obj
--debug --endian=little --cpu=Cortex-M3 -f C:\ti\simplelink\ble_sdk_2_02_02_25\examples\cc2650stk\sensortag\iar\app\..\
..\..\..\..\src/config/build_components.opt -f C:\ti\simplelink\ble_sdk_2_02_02_25\examples\cc2650stk\sensortag\iar\app\..\
stack\build_config.opt -f C:\ti\simplelink\ble_sdk_2_02_02_25\examples\cc2650stk\sensortag\iar\app\..\config\configPkg\
compiler.opt.defs -f C:\ti\simplelink\ble_sdk_2_02_02_25\examples\cc2650stk\sensortag\iar\app\..\config\
iar_boundary.bdef -e --fpu=None --dlib_config \"C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.2\arm\inc\
c\DLib_Config_Normal.h\" -I C:\ti\simplelink\ble_sdk_2_02_02_25\examples\cc2650stk\sensortag\iar\app\..\..\..\..\..\
src/controller/cc26xx/inc\ -I C:\ti\simplelink\ble_sdk_2_02_02_25\examples\cc2650stk\sensortag\iar\app\..\..\..\..\..\src/inc\
-I C:\ti\simplelink\ble_sdk_2_02_02_25\examples\cc2650stk\sensortag\iar\app\..\..\..\..\..\src/common/cc26xx\ -I C:\ti\
simplelink\ble_sdk_2_02_02_25\examples\cc2650stk\sensortag\iar\app\..\..\..\..\..\src/examples/sensortag/cc26xx/app\ -I
C:\ti\simplelink\ble_sdk_2_02_02_25\examples\cc2650stk\sensortag\iar\app\..\..\..\..\..\src/icall/inc\ -I C:\ti\simplelink\
ble_sdk_2_02_02_25\examples\cc2650stk\sensortag\iar\app\..\..\..\..\..\src/inc\ -I C:\ti\simplelink\ble_sdk_2_02_02_25\
examples\cc2650stk\sensortag\iar\app\..\..\..\..\..\src/profiles/batt/cc26xx\ -I C:\ti\simplelink\ble_sdk_2_02_02_25\
examples\cc2650stk\sensortag\iar\app\..\..\..\..\..\src/profiles/dev_info\ -I C:\ti\simplelink\ble_sdk_2_02_02_25\examples\
cc2650stk\sensortag\iar\app\..\..\..\..\..\src/profiles/hid_dev/cc26xx\ -I C:\ti\simplelink\ble_sdk_2_02_02_25\examples\
cc2650stk\sensortag\iar\app\..\..\..\..\..\src/profiles/keys\ -I C:\ti\simplelink\ble_sdk_2_02_02_25\examples\cc2650stk\
sensortag\iar\app\..\..\..\..\..\src/profiles/roles\ -I C:\ti\simplelink\ble_sdk_2_02_02_25\examples\cc2650stk\sensortag\iar\
app\..\..\..\..\..\src/profiles/roles/cc26xx\ -I C:\ti\simplelink\ble_sdk_2_02_02_25\examples\cc2650stk\sensortag\iar\app\..\
..\..\..\..\src/profiles/sensor_profile/cc26xx\ -I C:\ti\simplelink\ble_sdk_2_02_02_25\examples\cc2650stk\sensortag\iar\app\
..\..\..\..\..\src/target\ -I C:\ti\simplelink\ble_sdk_2_02_02_25\examples\cc2650stk\sensortag\iar\app\..\..\..\..\..\src\
components/hal/src/inc\ -I C:\ti\simplelink\ble_sdk_2_02_02_25\examples\cc2650stk\sensortag\iar\app\..\..\..\..\..\src\
components/hal/src/target/_common\ -I C:\ti\simplelink\ble_sdk_2_02_02_25\examples\cc2650stk\sensortag\iar\app\..\..\
..\..\..\src\components/hal/src/target/_common/cc26xx\ -I C:\ti\simplelink\ble_sdk_2_02_02_25\examples\cc2650stk\
sensortag\iar\app\..\..\..\..\..\src\components/heapmgr\ -I C:\ti\simplelink\ble_sdk_2_02_02_25\examples\cc2650stk\
sensortag\iar\app\..\..\..\..\..\src\components/icall/src\ -I C:\ti\simplelink\ble_sdk_2_02_02_25\examples\cc2650stk\
sensortag\iar\app\..\..\..\..\..\src\components/icall/src/inc\ -I C:\ti\simplelink\ble_sdk_2_02_02_25\examples\cc2650stk\
sensortag\iar\app\..\..\..\..\..\src\components/osal/src/inc\ -I C:\ti\simplelink\ble_sdk_2_02_02_25\examples\cc2650stk\
sensortag\iar\app\..\..\..\..\..\src\components/services/src/saddr\ -I C:\ti\simplelink\ble_sdk_2_02_02_25\examples\
cc2650stk\sensortag\iar\app\..\..\..\..\..\src\components/services/src/sdata\ -I C:\ti\tirtos_cc13xx_cc26xx_2_21_01_08\
products\cc26xxware_2_24_03_17272\ -I C:\ti\tirtos_cc13xx_cc26xx_2_21_01_08\products\
tidrivers_cc13xx_cc26xx_2_21_01_01\packages\ -I C:\ti\tirtos_cc13xx_cc26xx_2_21_01_08\products\
tidrivers_cc13xx_cc26xx_2_21_01_01\packages/ti/mw/extflash\ -I C:\ti\tirtos_cc13xx_cc26xx_2_21_01_08\products\
tidrivers_cc13xx_cc26xx_2_21_01_01\packages/ti/mw/sensors\ -I C:\ti\tirtos_cc13xx_cc26xx_2_21_01_08\products\
tidrivers_cc13xx_cc26xx_2_21_01_01\packages/ti/mw/sensortag\ -Ohz" --linkOptions "--no_out_extension -o C:\ti\
simplelink\ble_sdk_2_02_02_25\examples\cc2650stk\sensortag\iar\app\FlashROM\Exe\sensortag_cc2650stk_app.out
--map C:\ti\simplelink\ble_sdk_2_02_02_25\examples\cc2650stk\sensortag\iar\app\FlashROM\List\
sensortag_cc2650stk_app.map --config C:\ti\simplelink\ble_sdk_2_02_02_25\examples\cc2650stk\sensortag\iar\app\..\..\
..\..\..\src/common/cc26xx/iar/cc26xx_app.icf --keep __vector_table -f C:\ti\simplelink\ble_sdk_2_02_02_25\examples\
cc2650stk\sensortag\iar\app\..\config\configPkg\linker.cmd -f C:\ti\simplelink\ble_sdk_2_02_02_25\examples\cc2650stk\
sensortag\iar\app\..\config\iar_boundary.xcl --semihosting C:\ti\simplelink\ble_sdk_2_02_02_25\examples\cc2650stk\
sensortag\iar\app\..\..\..\..\..\src\rom\common_rom_releases\03282014\common_rom.symbols C:\ti\
tirtos_cc13xx_cc26xx_2_21_01_08\products\cc26xxware_2_24_03_17272\driverlib\bin\iar\driverlib.lib --entry
__iar_program_start --vfe --text_out locale" --profile release --projFile "C:\ti\simplelink\ble_sdk_2_02_02_25\examples\
cc2650stk\sensortag\iar\app\cc2650stk_app.ewp"
Total number of errors: 1
Total number of warnings: 0
thanks and regards
santhosh
↧
TMS320F28075: VDDIO short to VSS and GPIO58 short to VSS.
Part Number:TMS320F28075
Hi, my customer is using F28075 and find several devices broken recently.
5 devices are VDDIO short to VSS. 2 devices are GPIO58 short to VSS.
The schematic is shown below.
Three GPIOs and GND on board 1 and board 2 are connected to one DIP switch with about 70cm long wire.
The problem happens after the wire extended from less than 10cm to about 70cm. So I guess the problem is caused by the long cable.
It's strange that they just put the board there with 3.3V powered, main power stage(buck) not powered, and the device failed without any touch.
1. What may cause the device fail? Are GPIO58 short to VSS and VDDIO short to VSS caused by the same reason?
2. How to solve this problem?
↧