Part Number:LAUNCHXL-CC26X2R1

Tool/software: Code Composer Studio

This is a follow up to my previous post:

e2e.ti.com/.../783218

I was able to get the LAUNCHXL-CC26X2R1 working on battery power through project_zero on both IAR 8.32.3 and CCS9 (with both 2.4 and 3.1 SDK). When I took my code to my own business (hardware PCB) implementation, I started having issues booting up from the battery. I am using 2xAA Alkaline batteries on VBAT and able to “boost” a running Debug/Release build by connecting VBAT during Debug mode and unplugging the cJTAG and UART connectors. I still have Project Zero functionality with BLE. However, unplugging the power and reconnecting it will not work anymore. I need to reconnect the cJTAG, flash the image with Uniflash/IAR/CCS9 to restore functionality.

We modeled our schematic to be as close to the CC26X2 Launchpad as possible. The only major differences are pin mappings:

/* Analog Capable DIOs */
#define CC26X2R1_LAUNCHXL_DIO23_ANALOG PIN_UNASSIGNED
#define CC26X2R1_LAUNCHXL_DIO24_ANALOG PIN_UNASSIGNED
#define CC26X2R1_LAUNCHXL_DIO25_ANALOG PIN_UNASSIGNED
#define CC26X2R1_LAUNCHXL_DIO26_ANALOG PIN_UNASSIGNED
#define CC26X2R1_LAUNCHXL_DIO27_ANALOG PIN_UNASSIGNED
#define CC26X2R1_LAUNCHXL_DIO28_ANALOG PIN_UNASSIGNED
#define CC26X2R1_LAUNCHXL_DIO29_ANALOG PIN_UNASSIGNED
#define CC26X2R1_LAUNCHXL_DIO30_ANALOG PIN_UNASSIGNED

/* Digital IOs */
#define CC26X2R1_LAUNCHXL_DIO0 PIN_UNASSIGNED
#define CC26X2R1_LAUNCHXL_DIO1_RFSW PIN_UNASSIGNED
#define CC26X2R1_LAUNCHXL_DIO12 PIN_UNASSIGNED
#define CC26X2R1_LAUNCHXL_DIO15 PIN_UNASSIGNED
#define CC26X2R1_LAUNCHXL_DIO16_TDO PIN_UNASSIGNED
#define CC26X2R1_LAUNCHXL_DIO17_TDI PIN_UNASSIGNED
#define CC26X2R1_LAUNCHXL_DIO21 PIN_UNASSIGNED
#define CC26X2R1_LAUNCHXL_DIO22 PIN_UNASSIGNED

/* Discrete Inputs */
#define CC26X2R1_LAUNCHXL_PIN_BTN1 IOID_13
#define CC26X2R1_LAUNCHXL_PIN_BTN2 PIN_UNASSIGNED
#define CC26X2R1_LAUNCHXL_PIN_EH IOID_23


/* GPIO */
#define CC26X2R1_LAUNCHXL_GPIO_LED_ON 1
#define CC26X2R1_LAUNCHXL_GPIO_LED_OFF 0


/* I2C */
#define CC26X2R1_LAUNCHXL_I2C0_SCL0 IOID_6
#define CC26X2R1_LAUNCHXL_I2C0_SDA0 IOID_7
#define CC26X2R1_LAUNCHXL_I2C1_SCL IOID_3
#define CC26X2R1_LAUNCHXL_I2C1_SDA IOID_2
#define CC26X2R1_LAUNCHXL_I2C2_SCL IOID_1
#define CC26X2R1_LAUNCHXL_I2C2_SDA IOID_0

/* I2S */
#define CC26X2R1_LAUNCHXL_I2S_ADO PIN_UNASSIGNED
#define CC26X2R1_LAUNCHXL_I2S_ADI PIN_UNASSIGNED
#define CC26X2R1_LAUNCHXL_I2S_BCLK PIN_UNASSIGNED
#define CC26X2R1_LAUNCHXL_I2S_MCLK PIN_UNASSIGNED
#define CC26X2R1_LAUNCHXL_I2S_WCLK PIN_UNASSIGNED

/* LEDs */
#define CC26X2R1_LAUNCHXL_PIN_LED_ON 1
#define CC26X2R1_LAUNCHXL_PIN_LED_OFF 0
#define CC26X2R1_LAUNCHXL_PIN_RLED IOID_5
#define CC26X2R1_LAUNCHXL_PIN_GLED PIN_UNASSIGNED

/* PWM Outputs */
#define CC26X2R1_LAUNCHXL_PWMPIN0 CC26X2R1_LAUNCHXL_PIN_RLED
#define CC26X2R1_LAUNCHXL_PWMPIN1 CC26X2R1_LAUNCHXL_PIN_GLED
#define CC26X2R1_LAUNCHXL_PWMPIN2 PIN_UNASSIGNED
#define CC26X2R1_LAUNCHXL_PWMPIN3 PIN_UNASSIGNED
#define CC26X2R1_LAUNCHXL_PWMPIN4 PIN_UNASSIGNED
#define CC26X2R1_LAUNCHXL_PWMPIN5 PIN_UNASSIGNED
#define CC26X2R1_LAUNCHXL_PWMPIN6 PIN_UNASSIGNED
#define CC26X2R1_LAUNCHXL_PWMPIN7 PIN_UNASSIGNED


/* Power Control */
#define SENSOR_GPIO_TEMP_PWR_ IOID_15
#define SENSOR_GPIO_LIGHT_PWR_ IOID_29
#define SENSOR_GPIO_PWR_ON 0
#define SENSOR_GPIO_PWR_OFF 1

/* SPI */
#define CC26X2R1_LAUNCHXL_SPI_FLASH_CS PIN_UNASSIGNED
#define CC26X2R1_LAUNCHXL_FLASH_CS_ON 0
#define CC26X2R1_LAUNCHXL_FLASH_CS_OFF 1

/* SPI Board */
#define CC26X2R1_LAUNCHXL_SPI0_MISO PIN_UNASSIGNED /* RF1.20 */
#define CC26X2R1_LAUNCHXL_SPI0_MOSI PIN_UNASSIGNED /* RF1.18 */
#define CC26X2R1_LAUNCHXL_SPI0_CLK PIN_UNASSIGNED /* RF1.16 */
#define CC26X2R1_LAUNCHXL_SPI0_CSN PIN_UNASSIGNED
#define CC26X2R1_LAUNCHXL_SPI1_MISO PIN_UNASSIGNED
#define CC26X2R1_LAUNCHXL_SPI1_MOSI PIN_UNASSIGNED
#define CC26X2R1_LAUNCHXL_SPI1_CLK PIN_UNASSIGNED
#define CC26X2R1_LAUNCHXL_SPI1_CSN PIN_UNASSIGNED

/* UART Board */
#define CC26X2R1_LAUNCHXL_UART0_RX IOID_18 /* MAIN RXD */
#define CC26X2R1_LAUNCHXL_UART0_TX IOID_19 /* MAIN TXD */
#define CC26X2R1_LAUNCHXL_UART0_CTS PIN_UNASSIGNED
#define CC26X2R1_LAUNCHXL_UART0_RTS PIN_UNASSIGNED
#define CC26X2R1_LAUNCHXL_UART1_RX PIN_UNASSIGNED
#define CC26X2R1_LAUNCHXL_UART1_TX PIN_UNASSIGNED
#define CC26X2R1_LAUNCHXL_UART1_CTS PIN_UNASSIGNED
#define CC26X2R1_LAUNCHXL_UART1_RTS PIN_UNASSIGNED

Furthermore, when I remap the following:

CC26X2R1_LAUNCHXL_PIN_RLED IOID_5

Project zero happily uses the new pin and I have LED control with the SimpleLink app. But now when I try to GPIO.toggle() or GPIO.write() to any of my assigned pins, the hardware does not respond. I can “read” the pin state, but no LED is working on the hardware. So I can only control the pins that ProjectZero is mapped to, and I can't “toggle” GPIO pins in my actual program code.

Could my pin mapping of the CC2652 be crashing the app on battery power bootup?

Also, simple_broadcaster and ti-rtos based projects like i2ctmp116 DO work off battery power. Any help is greatly appreciated.

Part Number:UCD90160A

During forced fault events (part of testing during development), I get my fault source recorded correctly, but our programmed response to the fault usually results in other power supply rails (slaves) getting shut down, and additional faults are subsequently recorded for those events as well.  It makes looking through the fault logs more confusing, as all these faults often have the same timestamp.

 Anyway… Is it possible to store/record only the first fault seen, and ignore recording other faults until SW clears the initial one?

Part Number:F28M36P63C2

Hello,

I am using the CARD Concert F28M36x control in simulink, but I have problems with the sample time, I do not understand how it works.

I am developing a control for buck converter.

When I select a sample time of 1 / (100kHz) the control works, but when I increase the sample time to 1 / (1MHz) the microcontroller does not work.

my questions are:

Does the sampe time depend on the ADC?
F28M36x has an ADC of 2.88 MSPS, should I be able to select 1 / (2.88 MHz) as the maximum sampling time?

Thank you

Part Number:ADS1299

Hello,

I am designing a schematic around the ADS1299 for EEG acquisition. I plan to use a referential configuration with the 8 positive pins, SRB1 and Bias out.

I want to keep the PCB as small as possible, so was planning to go with a uni-polar supply (avoid extra inverter, -2.5V LDO and 2.5V LDO). 

I am using a 3.7V Lipo battery with a charge IC, 5V boost IC and 3.3V LDO.

Pictures of my design are below and I have a couple questions that I would like some help with.

1. I read here that there is no disadvantage in performance by using uni-polar supply versus bi-polar. I understand that a common-mode offset must be applied to bring the positive pins to mid-supply, but don't fully understand the rest of the configuration. Is there any additional hardware I need to consider for this? Does it change anything on the ADS1299 pin connections on the schematic? Or is it purely just register configuration?

2. I don't fully understand AGND and DGND connections. I've seen some designs that just use a single ground. Is the grounds I've labelled correct? All grounds in my power circuitry are AGnd except for the ground on the 3.3V LDO, which is my DGnd? Do I still need separate analog and digital grounds when using a uni-polar supply? I understand if using bi-polar supply as AGnd will be -2.5V and DGnd will be 0V. But for uni-polar, both are 0V? I saw that in Fig 62 of the EEGFE-PDK datasheet that AGnd and DGnd are tied together using a 0Ohm resistor. Is this recommended? If so at what stage should I tie them together? 

3. Related to the previous question, are decoupling capacitors only needed between AVdd-AGnd and DVdd-DGnd? I've seen designs with caps between AVdd-DGnd too, is this necessary? How many decoupling caps do I need between AVdd-AGnd? I've seen some designs with just one pair of parallel 1uF and 0.1uF caps, and other designs with 3 of these parallel circuits.

4. I have connected AVdd1 with AVdd and AVss1 with AVss. Is this ok? The datasheet says AVdd1 is for the charge pump block and that it should be star-connected with AVdd.

5. The 5V boost converter can supply 5V with 500mA output current and an output voltage ripple of +/-25mV. The 3.3V LDO can supply 250mA output current. Firstly, I assume this is more than enough current to drive the ADS1299, an STM32F4 uC, and an AN1325A BT chip? Secondly, will 25mV ripple affect the ADS1299's performance at all?

6. I want to measure all positive electrode inputs with reference to SRB1. Is it best to tie all negative inputs together with SRB1 like I have done? Or should I use the internal input multiplexer via MISC1 register instead and leave the negative pins floating? I need to use AC lead-off too. So I want to output the AC lead-off signal on the SRB1 electrode and record it on the 8 positive electrodes to get individual impedance measurements for each electrode. Is this possible? Does this affect how I should connect the negative inputs to SRB1 (either by wire or using the input multiplexer).

7. As I am using referential montage, I can't use a differential capacitor between positive and negative pins (as all negative pins are tied together with SRB1). Instead I am using a shunt capacitor to ground. Will this have a large effect on the CMRR? Is there any way of using a differential capacitor with SRB1 for all channels?

8. Protection! I have a series 5k resistor between each electrode and pin. Is this enough? I have seen designs with ESD chips. Is it necessary? Also, on the power management side, should I have a protection IC for over-voltage/discharge/current and short-circuit to protect the ADS? Or is the fact that the switch disconnects the 5V boost and supply to the ADS when the charger is turned on?

9. Finally, I would appreciate it if any poor elements of my design could be pointed out, or if there are any suggestions on how to improve the design to achieve higher quality EEG.

Thanks in advance for any support with this.

Mark

Part Number:ADS1299

Hello,

We are thinking about making  a 32 ways acquisition system at 250 SPS from a single ADS1299 and 8 mux ADG659

In order to achieve that we where thinking of :

• Setting in the Output data rate at 8kSPS.
• Switching of canal every 2 acquisitions ( 1>2>3>4>1).
• Ditching 1 acquisition just after the mux switching.

But our conclusion is that the digital Filter stage will prevent us to get good result.

Could you confirm us this conclusion?

Thanks in advance.

Regards

Part Number:CC2500EMK

Dear All,

We have some very tight real-time constraints in our software.The reason for doing a "manual calibration" is that from IDLE to Rx/Tx with calibration, the state transition time is about 800 usec. whereas, from IDLE to Tx/Rx without calibration, its only takes 90 usec.

we have read in the datasheet that there are 3 ways to do calibration:

a) Auto calibration (default)

b) Calculating FSCAL1,2,3 upfront for calibration use

c) Calibration with Charge pump disabled

Our concern is

[1]  We cant afford auto calibration because it takes about 800us. If we go with "Option B":

a) How much time it will be required to do a calibration in this case ?

b) Do we have to give SCAL strobe for this option B ?

c) How much temperature variation we can afford with this option B ?

d) Do we have to give manual calibration if we go with "Option B"

 [2] If we go with "Option C": [ We think that this is the feasible way ]

a) If we disable charge pump what are the disadvantage we get by doing this ?

b) If we use SCAL to calibrate will we again have to wait for 800us to get calibrated like in case of  "Option A"

c) How often manual calibration have to be done if we go with "Option C"

Our architecture requirements:

Number of Channels : 0 to 24

Frequency hopping used: Yes

Range: 100 m

Note:

Please provide the answer with respect to above mentioned points.

Regards,

MHS

Part Number:LMX2615-SP

OUTA_PD = 1, OUTB_PD = 1

OUTA_MUX = OUTB_MUX = 1

OUTA_PWR = 25, CPG=7

fOSC= fPD = 80 MHz, fVCO = fOUT = 1.6 GHz

Thanks!,

Kyle

Part Number:LMG3410R070

In SNOU140A on the app of LMG3410 circuit you have C8 .

This is powering the chip in boost-up mode, shown  to be 47uF

This is huge!

In an app where everything is low power, there is low current including peaks.

Can it be selected to something nominal such as 1uF/25V MLCCor something such as 2.2uF?

Is the 47uF value due to the buckboost negative bias the chip generates internally?

Will appreciate a range of values min to max.

Pl see attached pdf of my circuit in 380V @ 300W application where we need 2 such sync switches. I only copy the relevant part of the circuit.

thnx(Please visit the site to view this file)

r

Part Number:EVM430-FR6047

Hello,

I am just getting started with the EVM430-FR6047 eval board and am using the Ultrasonic Sensing Design Center (Water Mode).  I am reading http://www.ti.com/lit/ug/slau720b/slau720b.pdf

3.2 Loading a Configuration
An existing meter configuration can be loaded using the “Load Configuration” button in the main tab as
seen in Figure 7. Some example configurations are available in USS SW Library "example" directory.

Can you please tell me where exactly this directory is located and/or what the configuration file extension might be?  I have looked through the C:\ti\msp\USS_02_20_00_16\USS\examples\USSSWLib_template_example folder and it refuses to load any file located in this folder (extensions of .projectspec, .cmd, .ewd, .ewp and .h).  Obviously I'm not looking in the correct location but I can find no other folder that was installed with either the USS Design Center or Code Composer Studio that is called "example".  Thanks for your help. 

Hi Team,

Customer is asking whether we have such DDS products:

• At least two output channels.
• Good phase noise.
• Output frequency: 10MHz - 300MHz

Looking forward to your reply! Thank you!

Marc

Part Number:TLV320ADC3101

Hi,

I am given a differential Audio signal from a device which is coming out of a transformer as shown below. And I need to input these signals to TLV320ADC3101 in single-ended configuration. I do not have access to the ground of the transmitter side. 

Do you have any suggestions / components...etc. for converting this differential signal with an unknown reference ground to my circuit.

One way might be using Audio transformers however they are pretty expensive. (~$20)

Regards

Part Number:LAUNCHXL-F28379D

Tool/software: Code Composer Studio

Hello TI people,
Am working on TMS320F28379D Delfino launchpad. I have managed to run a simple code on CLA processor in parallel with CPU1 using RAM linker file. For the time being i have migrated to Flash linker file (provided from CC2000ware_x_x_x) but the code is no longer working. Sure, I have defined the CPU1,  FLASH macro and CLA_C in predefined symbols that reside in project properties.
Am here for any suggestion.

I posted the same question on this thread "e2e.ti.com/.../792762" but no one replay i got and it was useless.  

best regards
Hosam

Part Number:DLPC3470

Hi Kyle,

As you pointed out, my flash data signals were flipped, so I corrected them.  As before, I toggled the PROJ_ON signal every few seconds and watched the SPI bus as the 3470 attempts to boot.  Since I never saw PROJ_IRQ drop (signaling the completion of booting), I probed the four SPI signals (CS, DI, DO and CLK) with a deep memory scope and downloaded the data into a PC.  I then wrote some software to process the collected data to convert the signals into SPI commands and data.

I see the 3470 issue a series of 4 fast read commands (0xb) followed by 24-bit addresses: 0, 0x1000, 0 and 0x2A0A0.  I collected the read data and discovered that there was an extra 0x00 byte proceeding what is correct data from the master file you sent me (dlpc347x_7.0.1.s37).  In other words, if I remove one bytes of 0x00 from the Flash ROM's output that I captured it matches the master file.  I've reviewed the SPI signals in this region to verify that the software isn't lying to me.  I figured this extra byte of zero is the cause of the 3470 not booting.  I can't explain why the zero is present.  The SPI signals look very good (nice 3.3V and 0V levels).

I removed the Flash chip and replaced it with another I'd programmed from the master file.  I also downloaded the content of the removed Flash ROM and compared it to the master.  It was an exact match except of course for the unprogrammed locations (e.g. the master file doesn't contain all 32 MB of data).  The data was perfectly intact.

With the Flash ROM replaced on the board, I see the chip select signal looks the same as it did with the original Flash ROM and IRQ never drops signaling the end of booting.  I have verified that IRQ isn't shorted because I can toggle it as an output from the CX3 (mipi controller) to which it is attached.

We have a second set of boards I will modify and try.

Thanks for your help,

Scott

Part Number:ADS1298ECGFE-PDK

The RPS goes into short circuit mode the moment MMB0 EVM board is connected. The LED's are on.  The ADS1298 board is separated from the motherboard.

Not sure what the reason is

Part Number:TPS2372

I'm having a bit of an issue with the TPS2372 TPH and TPL outputs. Hopefully
you can tell me what I'm doing wrong.

We think that their output should be a direct function of the number
of class cycles produced by the PSE per table 2 in the datasheet.
Unfortunately, the observed outputs are different.

By changing the requested class, we can observe a change in number of
class cycles:

Requested Observed Expected Observed
Class     Class    TPH TPL  TPH TPL
          Cycles
3         1        1   1    1   1
4         3        1   0    0   0
5         4        0   1    0   0
6         4        0   1    0   0

As you can see, TPH and TPL are either both high or both low.
We never observe them having different values. This has been confirmed with
multiple boards. We also checked that they are not shorted together.

Attached is cut/paste of the relevant schematic sections as well as
a scope shot for the power on sequence when we request class 4 operation.
The scope is observing VDD relative to VSS as seen by the TPS2372-4.

Any ideas?

Part Number:CC2642R

Hello,

We're troubleshooting some issues causing disconnections between our peripheral (CC2642) and central device. I've seen some bizarre things in the sniffer traces (BPA Low Energy sniffer) that I can't explain, and was hoping to get a second opinion. The sequence of events in the screenshot below are throwing me for a loop, my best theory is timing issues on the central side that might be causing the sniffer to display things incorrectly. "Side 1" is supposed to be the central and "Side 2" the peripheral. Starting at frame 464,570, the sniffer displays a long series of connection events where only side 2 is present. The signal strength is good enough that I think it's unlikely the sniffer missed that many packets in a row from the central side.

I'm wondering if the timing is off in the central, and frame 464,570 is actually coming from the central, because the next frame after it is a notification from the peripheral. The Delta between frame 464,566 (first packet in the previous connection interval) and frame 464,570 is ~7.9 ms. Our connection interval is 7.5 ms. Is it possible that the central started connection event 0x9004 later than it should have, and the sniffer software is assuming it missed the central's packet and interprets it as a peripheral packet?

On a more general note, it's not possible for the peripheral to send a packet in a connection event if the central doesn't send a packet, right? I thought this was just how BLE worked, but maybe I'm mistaken?

Part Number:TMS320F28335

Tool/software: Code Composer Studio

Hello, 

In my Simulink Model i added an outport named out1, how can i visualize it via graph window in ccs 

Part Number:CC2652R

Tool/software: TI-RTOS

Dear Support:

I am going through different files in the SDK v2.30 examples for the CC26xx and CC13xx and see several of the calls where the Timer is constructed as the following:

static Clock_Struct keyChangeClock;

Timer_construct( &keyChangeClock, board_key_changeHandler, (KEY_DEBOUNCE_TIMEOUT), 0, false, 0 );

However the arguments in this call (notice there are 6 of them) does not match what is provided in the docs folder for the TI-RTOS API call that is referenced in the SDK.  For example in the docs folder of this SDK for tirtos there is this folder:

C:\TI\simplelink_cc26x2_sdk_2_30_00_34\docs\tirtos\sysbios\docs

and located in this directory, there is this file:

Bios_APIs.html

which references the TI-RTOS APIs and for the one above, it is defined as follows for the Timer:

Notice there are 5 arguments for this same call used above and the parameters don't match in number or in value relative to what is used above in the SDK.  So when looking through example code in the SDK, where do I find the correct documentation for the TI-RTOS cals that are made so I can make sense out of the API calls that are used in the code?  Please advise.

Thanks,
Tim

Part Number:TMS320C6748

Tool/software: Code Composer Studio

Issue with using trace analyzer of CCS Version: 8.3.0.00009.

I get an error message upon starting the trace analyzer.  Emulator probe used is XDS100v2.   Using ETB.  The error message is captured in the file attached.

(Please visit the site to view this file)

Part Number:LAUNCHXL-F28379D

Tool/software: Code Composer Studio

I've got two projects in CCS: one for CPU1 and the other for CPU2.  I'd like to load both projects onto the Launchpad into flash so that they can run independently of the CCS debugger after powering down and powering up again.  When debugging, the programs will both run.  However, if I power down the board after flashing for debug, only CPU1 runs. 

The CPU2 project uses 2837xD_FLASH_lnk_cpu2.cmd.  CPU2 and _FLASH are in the predefine symbols.  F2837xD_CodeStartBranch.asm is in the "device" directory of the CPU2 project.  The switches on the board near the label "S1 BOOT" are all in the position closest to "ON CST".

What am I missing that keeps both programs from running in standalone mode?

Thanks