Part Number:LMK61E0M

Hi!

I'm using the LMK61E0M in my design.  I'm attempting to do a signal analysis on this part of my circuit.

I'm looking for the IBIS file for this part so I can do the simulation.  

Could some one point me to the IBIS file, if it exists?  I have one for the LMK00334.

Part Number:TUSB2077A

This design has been in production since 2013. Dual hub primary TUSB2077A and secondary TUSB2046B in series to create a 9 port hub product. There have been no documented problems until recent revisions of Windows 10 interaction resulting in random port disable state. In a static connection to 8 devices all under self power and the hub self powered and ports individually monitored for current draw faults, simply disconnecting the USB link to the host Windows 10 and reconnecting results in 0 to 3 devices, mostly 1 or 2, fail to enumerate properly. Missing in the OS record of connected devices is the end point establishment and device ID. Some but not all of the device "hello" data is transferred. Also associated with the failure is pin 42 PORTDIS is low. If all devices enumerate properly then PORTDIS is high. When devices that are connected to the ports are directly connected to host, the device never fails to enumerate. This leads me to the conclusion that there is some sort of race condition causing the hub to detect a port disable and it remains in that state until the next connection cycle. I need advice from an FAE on how to tackle this problem.

The attached schematic shows pull-down resistors on the DPx and DMx pins - these are unpopulated in the production build and reset duration has been extended with larger R values 232k at R49 and 118.

(Please visit the site to view this file)

Part Number:BQ24618

I am thinking BQ24618 as a charger for 3-cell battery (12.6V), and BQ24618 datasheet tells it's BUCK converter. I tried to find what the Vin minimum to fully charge 3-cell battery, but unfortunately I could not find such parameter in datasheet; the typical application in datasheet uses 19V for 3-cell, 19V is too high for my power source selection, please advise what Vin-Vout minimum drop voltage is.

Regards,

Yunfa

Part Number:CC2642R

Tool/software: Code Composer Studio

Recently had a colleague update his setup from bottom up (CCS v9, etc. etc.) and wanted to "catch up" to make sure compilers, emulator tools, etc. were on par between the two of us.

Upon working on some code today, I started a debug session. Things worked as expected, and I needed to make edits then re-debug the code again. I ended the debug session and began a new one just as before. This time the debugger gets to the point of programming and accessing the device at the reset vector, but then the entire program shuts down without a trace. Any changes to the workspace are also lost since the last successful close.

This is VERY repeatable and happens every second debug attempt I make after opening the project.

If I manually reset my PCBs, it shows that the new code has been downloaded to the device, but it remains that the debug session itself is failing. I have attached dump files and log files for the last two such issues.

I am currently running with:

• CCS v8.2.0.00007
• ARM Compiler Tools v18.12.1
• CC26xx Device Support v3.10.10.02
• TI Emulators v8.1.0.00005

I found in the properties for this emulator package that it was only tested with CCS v8.3 and above. Is there any reason that this package shouldn't work properly with CCS v8.2?

Is there a way to downgrade emulator packages back to what worked? I'd MUCH rather do that than re-download CCS v9 and start from the bottom up installation again.

(Please visit the site to view this file)

Part Number:TMP468

Hi,

1) If using a NPN diode connection as shown in Fig 1, does the  TMP468 provides/outputs constant current source on these pins (D1+ through D8+)? 

2) is that more accurate to use two NPN transistors connected in series with their respective base and collectors short-circuited?  see below drawing, for example

Thanks,

Tim

Part Number:CC2650

Tool/software: Code Composer Studio

Fiends, 

CCS v901,
ble_sdk_2_02_01_18 installed under default C:\ti\simplelink\ble_sdk_2_02_01_18.
simple_peripheral_cc2650lp_app imported. 
Build comes with the following errors:

**** Build of configuration FlashROM for project simple_peripheral_cc2650lp_app ****

"C:\\ti\\ccs901\\ccs\\utils\\bin\\gmake" -k -j 2 all -O

Building file: "C:/ti/simplelink/ble_sdk_2_02_02_25/examples/cc2650lp/simple_peripheral/ccs/config/app_ble.cfg"
Invoking: XDCtools
"C:/ti/XDCtools/xdctools_3_32_00_06_core/xs" --xdcpath="C:/ti/ccs901/ccs/ccs_base;C:/ti/TI-RTOS/tirtos_cc13xx_cc26xx_2_21_01_08/packages;C:/ti/TI-RTOS/tirtos_cc13xx_cc26xx_2_21_01_08/products/tidrivers_cc13xx_cc26xx_2_21_01_01/packages;C:/ti/TI-RTOS/tirtos_cc13xx_cc26xx_2_21_01_08/products/bios_6_46_01_38/packages;C:/ti/TI-RTOS/tirtos_cc13xx_cc26xx_2_21_01_08/products/uia_2_01_00_01/packages;" xdc.tools.configuro -o configPkg -t ti.targets.arm.elf.M3 -p ti.platforms.simplelink:CC2640F128 -r release -c "C:/ti/CGT/ti-cgt-arm_16.9.4.LTS" --compileOptions "-mv7M3 --code_state=16 --abi=eabi -me -O4 --opt_for_speed=0 --include_path=\"C:/ti/CGT/ti-cgt-arm_16.9.4.LTS/include\" --include_path=\"C:/ti/simplelink/ble_sdk_2_02_02_25/src/examples/simple_peripheral/cc26xx/app\" --include_path=\"C:/ti/simplelink/ble_sdk_2_02_02_25/src/inc\" --include_path=\"C:/ti/simplelink/ble_sdk_2_02_02_25/src/icall/inc\" --include_path=\"C:/ti/simplelink/ble_sdk_2_02_02_25/src/profiles/roles/cc26xx\" --include_path=\"C:/ti/simplelink/ble_sdk_2_02_02_25/src/profiles/roles\" --include_path=\"C:/ti/simplelink/ble_sdk_2_02_02_25/src/profiles/dev_info\" --include_path=\"C:/ti/simplelink/ble_sdk_2_02_02_25/src/profiles/simple_profile/cc26xx\" --include_path=\"C:/ti/simplelink/ble_sdk_2_02_02_25/src/profiles/simple_profile\" --include_path=\"C:/ti/simplelink/ble_sdk_2_02_02_25/src/common/cc26xx\" --include_path=\"C:/ti/simplelink/ble_sdk_2_02_02_25/src/components/heapmgr\" --include_path=\"C:/ti/simplelink/ble_sdk_2_02_02_25/src/controller/cc26xx/inc\" --include_path=\"C:/ti/simplelink/ble_sdk_2_02_02_25/src/components/hal/src/target/_common\" --include_path=\"C:/ti/simplelink/ble_sdk_2_02_02_25/src/target\" --include_path=\"C:/ti/simplelink/ble_sdk_2_02_02_25/src/components/hal/src/target/_common/cc26xx\" --include_path=\"C:/ti/simplelink/ble_sdk_2_02_02_25/src/components/hal/src/inc\" --include_path=\"C:/ti/simplelink/ble_sdk_2_02_02_25/src/components/osal/src/inc\" --include_path=\"C:/ti/simplelink/ble_sdk_2_02_02_25/src/components/services/src/sdata\" --include_path=\"C:/ti/simplelink/ble_sdk_2_02_02_25/src/components/services/src/saddr\" --include_path=\"C:/ti/simplelink/ble_sdk_2_02_02_25/src/components/icall/src/inc\" --include_path=\"C:/ti/simplelink/ble_sdk_2_02_02_25/src/inc\" --include_path=\"C:/ti/simplelink/ble_sdk_2_02_02_25/src/rom\" --include_path=\"C:/ti/tirtos_cc13xx_cc26xx_2_21_01_08/products/cc26xxware_2_24_03_17272\" -g --c99 --gcc --define=BOARD_DISPLAY_EXCLUDE_LCD --define=BOARD_DISPLAY_EXCLUDE_UART --define=CC2650_LAUNCHXL --define=CC26XX --define=Display_DISABLE_ALL --define=GAPROLE_TASK_STACK_SIZE=540 --define=HEAPMGR_SIZE=0 --define=ICALL_MAX_NUM_ENTITIES=6 --define=ICALL_MAX_NUM_TASKS=3 --define=POWER_MEASURE --define=POWER_SAVING --define=USE_ICALL --define=xdc_runtime_Assert_DISABLE_ALL --define=xdc_runtime_Log_DISABLE_ALL --diag_warning=225 --diag_suppress=48 --diag_wrap=off --display_error_number --gen_func_subsections=on " "C:/ti/simplelink/ble_sdk_2_02_02_25/examples/cc2650lp/simple_peripheral/ccs/config/app_ble.cfg"
TOOLS/subdir_rules.mk:12: recipe for target 'build-1641678497-inproc' failed
js: "C:/ti/XDCtools/xdctools_3_32_00_06_core/packages/xdc/tools/Cmdr.xs", line 51: Error: xdc.tools.configuro: Error: Can't find the platform package 'ti.platforms.simplelink'. TI platforms are no longer shipped as part of XDCtools (C:\ti\XDCtools\xdctools_3_32_00_06_core). Please ensure you are either using a pre-3.30 version of XDCtools or you have added a product that includes your platform support along the path 'C:/ti/ccs901/ccs/ccs_base;C:/ti/TI-RTOS/tirtos_cc13xx_cc26xx_2_21_01_08/packages;C:/ti/TI-RTOS/tirtos_cc13xx_cc26xx_2_21_01_08/products/tidrivers_cc13xx_cc26xx_2_21_01_01/packages;C:/ti/TI-RTOS/tirtos_cc13xx_cc26xx_2_21_01_08/products/bios_6_46_01_38/packages;C:/ti/TI-RTOS/tirtos_cc13xx_cc26xx_2_21_01_08/products/uia_2_01_00_01/packages;C:\ti\XDCtools\xdctools_3_32_00_06_core/packages'. Check that this path names a directory containing the necessary platform support and that the platform name is properly spelled.
gmake[1]: *** [build-1641678497-inproc] Error 1
gmake: *** [build-1641678497] Error 2
TOOLS/subdir_rules.mk:9: recipe for target 'build-1641678497' failed
gmake: Target 'all' not remade because of errors.

**** Build Finished ****

Having needed TI-RTOS and UIA within c:\ti\TI-RTOS and c:\ti\UIA
I added needed products to the project as shown below:

After successful build I have the following warning messages: 

The products installation paths issue is solved. 

I pay attention to warnings.

How to manage an example configurations to fix the warnings?

Part Number:CC1350

I see that TI's description of the CC1350 states that: 

• 2.4-GHz RF Transceiver Compatible With Bluetooth low energy 4.2 Specification

Does this include data length extension support?

SmartRF Studio 7 caps the payload length at 37. Is this a limitation of SmartRF Studio or the CC1350?

Thanks,

Louis

Part Number:IWR1443BOOST

Tool/software: Linux

Hello,

I would like to know if it is possible to access the data from the IWR1443BOOST ES3.0 SDK 2.1 before the object detection takes place.

I am looking forward to being able to see how the data comes before it is filtered only with detected objects, is it possible? 

As a side question, I have seen that most of the labs available do not fit with IWR1443BOOST ES3. Are there any new labs that will be available soon?

Best Regards,

Daniel

Part Number:TM4C1290NCPDT

Tool/software: TI C/C++ Compiler

CCS v 8.3.0.00009

The following header code generates several odd error messages:

extern  void  Info_Msg( char* );
inline  void  Info_Msg( const char* pMsg ) { Info_Msg(const_cast<char*>(pMsg)); }

error #148: declaration is incompatible with "void Info_Msg(char *)"

error #20: identifier "const_cast" is undefined

error #29: expected an expression

This compiles successfully in Sourcery Codebench IDE 2015.12-104  (gcc)

Part Number:CC1352P

Tool/software: TI-RTOS

Is it possible to use ROV to monitor CPU Load and Heap usage?  I tried enabling the CPU Load module in the app.cfg file, but then I get compile errors saying can't be used with ROM.

And I can't find how to turn on Heap monitoring.

Thanks,

- Bill

Part Number:BQ24296M

Hi,

I have a few design questions related to the BQ24296M:

1) Our LiPo battery does not have a thermistor.  How do you disable the TS signal?

2) In regards to PSEL and ILIM, does the charger use the lower of the two current limits?  For example, if PSEL = 0 (adapter, 3A) and ILIM is set for 2A, will the charger max out at 2A?

Best,

Matt

Part Number:TPD4EUSB30

The TPD4EUSB30 datasheet pin table indicates that pins 6,7,9,10 are not normally connected. Is it acceptable to connect these pins as implied by the comment "flow through" routing (ie pin 1&10 together, 2&9, 4&7, 5&6) to ease routing? It is not clear from the datasheet that this is okay.

Part Number:TPS53641

TPS53641 has VR_FAULT# asserted low.  the fusion shows  VIN_OV_FAULT_LIMIT (register 0x55) to be 15.000, with HEX value of 0x000F. 

This is the only item that is different from a good working controller which shows VIN_OV_FAULT_LIMIT(register 0x55) to be 17.000, with HEX value of 0x0011

As a result of this failure the output voltage is at VBOOT value, and VOUT_MAX is at 3.04V (0x00FF). 

Since I don't know what has caused this over voltage, I compared all pins voltages with the good working controller. The only difference that is see

is with pin TSEN (pin 40). the failing controller reads 0.833 volts, and the good controller reads 0.887 volt.

The input to TSEN is wire-AND of TAO output of two regulators(CSD95372BQ5M), as this controller  has two phases connected to these two regulators.

Would you please instruct as what could be the issue, and your recommendation on resolving it.

Note. FUSION shows the IMAX, value to be 55A, the same as good working board. I have checked all items listed in FUSION's General, Advanced, Device_info, and All config

to be the same as good working controller except the one mentioned above.

Thanks,

-jahan

Part Number:PROCESSOR-SDK-AM57X

Tool/software: TI-RTOS

Hello

I'm using TI-RTOS SDK 05.03 with CCS v8.1.0 on AM572x IDK board. I need to asynchronous send & receive information from TCP socket.

I want to use only one thread because TI-RTOS is used as TCP server with multiple connections.

I'm using TI-RTOS Mailboxes to pass info to required thread.

As I read, mailboxes can trigger TI-RTOS Events, and that's the way to wait for messages from few mailboxes.

How can I tell NDK to post required Event when a piece of information was received from the client socket?

With regards,
Alex

Part Number:CC2640R2F

Tool/software: Code Composer Studio

We are working with the i2ctmp116_CC2640R2_LAUNCHXL_tirtos_ccs project.  We are using the TI CC2640R2 Development Kit board.  The board also has LAUNCHXL-CC2640R2 Rev 1.0  written on it.

My question is about the Display_printf() function.  It is called many times in the code in order to display meaningful information.  But the messages it prints are not visible in either the Console window nor the Terminal window in CCS.

Since we want to modify the code for our own use on our own board, we'd like to be able to use these messages to help us test/debug our new code.

Does the Display_printf() function print to some kind of display device connected to the TI CC2640R2 Development Kit board?  How can we get such a display device?

Is it possible to redirect the Display_printf() function, or use a similar function, to print messages to a CCS window?

Thanks for any help you can give.
Dan Benkman
Innowave

Part Number:CC2541

CC2541 has a new stack release (1.5) - http://www.ti.com/tool/BLE-STACK

It claims full support of BLE5. BLE5 supports 244-byte payload. Can CC2541 support these large payloads with this stack?

Brian

Part Number:DAC8750

Hi,

What is the easiest way to calibrate DAC8750? Is there an example that we can use to quickly

calibrate this part?

Thanks,

Bob

Hi,

What is the best Flybuck isolated switching regulator to use with the following requirements:

1) Input voltage : 28V - 12V
2) Output voltage: 7.5V
3) Output current: 300mA

Please provide TI part number. 

Thanks,

Bob

Part Number:AWR1243BOOST

Tool/software: Linux

Hi,

I am currently in the process of porting the AWR1243 to the Raspberry Pi (NOOBS OS). Therefore, I am required to implement the functions in rls_studio.h and rls_osi.h. I noticed that the function rlsSpiOpen in rls_studio.h returns rlsDevHandle_t which is the radarlink studio device handle. I looked through the documentation and comments and cannot get any more information on what rlsDevHandle points to and how to get that information. Any help would be great.

Thanks!

Part Number:LAUNCHXL-F28379D

Hello,

My goal is to be able to force the output of all of the PWMs to a low state from either core.  For one core, that involves using a GPIO pin connected to the PWM through XBAR Input 1 to the one shot trip zone of the PWMs.  This works well, and it can be found in the trip zone example code.  However, I'm not sure of a way to be able to trigger the PWMs from either core.

The currently unsuccessful method I'm using is to initialize the XBAR and PWM trigger on CPU1.  CPU2 is given control of a GPIO pin.  If CPU2 needs to trip the PWMs, it would directly control the XBAR connected GPIO.  If CPU1 needs to trip the PWMs, it is configured to raise an IPC flag that causes CPU2 to interrupt and directly control the XBAR connected GPIO.

Here's the main() code for CPU1 to initialize the PWMs, XBAR, and trigger:

    EALLOW;

    GPIO_setPadConfig(32, GPIO_PIN_TYPE_STD);
    GPIO_setDirectionMode(32, GPIO_DIR_MODE_OUT);
    GPIO_setMasterCore(32, GPIO_CORE_CPU2);

    InputXbarRegs.INPUT1SELECT = 32;

    EPwm1Regs.TZSEL.bit.OSHT1 = 1;          
    EPwm1Regs.TZCTL.bit.TZA = TZ_FORCE_LO;  
    EPwm2Regs.TZSEL.bit.OSHT1 = 1;          
    EPwm2Regs.TZCTL.bit.TZA = TZ_FORCE_LO;  
    EPwm3Regs.TZSEL.bit.OSHT1 = 1;          
    EPwm3Regs.TZCTL.bit.TZA = TZ_FORCE_LO;  

    EDIS;

    CpuSysRegs.PCLKCR2.bit.EPWM1 = 1;
    CpuSysRegs.PCLKCR2.bit.EPWM2 = 1;
    CpuSysRegs.PCLKCR2.bit.EPWM3 = 1;
    InitEPwmGpio();

    EALLOW;                             
    EPwm1Regs.TZCLR.bit.OST = 1;        
    EPwm1Regs.TZCLR.bit.INT = 1;        
    EPwm2Regs.TZCLR.bit.OST = 1;        
    EPwm2Regs.TZCLR.bit.INT = 1;        
    EPwm3Regs.TZCLR.bit.OST = 1;        
    EPwm3Regs.TZCLR.bit.INT = 1;   
    EDIS;

This code is in an 8kHz timer interrupt on CPU1 used to request a trigger from CPU2 after 4 seconds:

    static int debugCount = 0;
    debugCount++;
    if (debugCount >= 32000)
    {
        HWREG(IPC_BASE + IPC_O_SET) = 1UL << IPC_TRIGGER_FAULT;
    }

The following is in main() on CPU2 to initialize the IPC interrupt:

    EALLOW;
    PieVectTable.IPC0_INT = &FaultTrigger;
    EDIS;    

    // Enable CPU INT1 which is connected to Upper PIE IPC INT0-3:
    IER |= M_INT1;

    // Enable CPU01 to CPU02 INTn in the PIE: Group 11 interrupts
    PieCtrlRegs.PIEIER1.bit.INTx13 = 1;   // CPU1 to CPU2 INT0

Finally, this is the IPC ISR:

__interrupt void FaultTrigger(void)
{
    EALLOW;
    GpioDataRegs.GPBCLEAR.bit.GPIO32 = 1; // Used to trip the trigger
    GpioDataRegs.GPBSET.bit.GPIO32 = 1;
    EDIS;

    // Clear the IPC flag
    HWREG(IPC_BASE + IPC_O_CLR) = 1UL << IPC_TRIGGER_FAULT;

    // Acknowledge IPC INT0 Flag and PIE to receive more interrupts
    IpcRegs.IPCACK.bit.IPC0 = 1;
    PieCtrlRegs.PIEACK.all = PIEACK_GROUP1;
}

Is there a simpler approach to this that allows both cores to directly cause the PWM, which is set up on CPU1, to force all of the outputs low?

Thanks!