Part Number:MSP-EXP430FR5994

Hi,

  I am testing both the A0& A1UART ports of the MCU on the MSP-EXP430FR5994 launchpad. I am able to transmit & receive data from A0 (P2.0 & P2.1) successfully, but A1 (P2.5 & P2.6) seems not to work at all. I am providing below the working code first for A0 then followed by A1 code. Note that both codes are same except that all zeros (of A0) have been replaced by ones (of A1) & the GPIO configurations are different. Am I still missing something somewhere?

-------------

WORKING CODE:

#pragma vector = EUSCI_A0_VECTOR
__interrupt void FFF0_ISR(void)
{
switch (__even_in_range(UCA0IV, USCI_UART_UCTXCPTIFG)) {
case USCI_NONE: break;
case USCI_UART_UCRXIFG:
gblLasteceivedUartCharacter_i = EUSCI_A_UART_receiveData(EUSCI_A0_BASE);
__bic_SR_register_on_exit(LPM3_bits); // Exit active CPU
break;
case USCI_UART_UCTXIFG: break;
case USCI_UART_UCSTTIFG: break;
case USCI_UART_UCTXCPTIFG: break;
}
}

-------------

GPIO_setOutputLowOnPin(GPIO_PORT_P2, GPIO_PIN0|GPIO_PIN1);
GPIO_setAsOutputPin(GPIO_PORT_P2, GPIO_PIN0);

// Configure P2.0 - UCA0TXD and P2.1 - UCA0RXD
GPIO_setOutputLowOnPin(GPIO_PORT_P2, GPIO_PIN0);
GPIO_setAsOutputPin(GPIO_PORT_P2, GPIO_PIN0);
GPIO_setAsPeripheralModuleFunctionInputPin(GPIO_PORT_P2, GPIO_PIN1, GPIO_SECONDARY_MODULE_FUNCTION);

// Set PJ.4 and PJ.5 as Primary Module Function Input, LFXT.
GPIO_setAsPeripheralModuleFunctionInputPin(
GPIO_PORT_PJ,
GPIO_PIN4 + GPIO_PIN5,
GPIO_PRIMARY_MODULE_FUNCTION
);

// Set DCO frequency to 8 MHz
CS_setDCOFreq(CS_DCORSEL_0, CS_DCOFSEL_6);
//Set external clock frequency to 32.768 KHz
CS_setExternalClockSource(32768, 0);
//Set ACLK=LFXT
CS_initClockSignal(CS_ACLK, CS_LFXTCLK_SELECT, CS_CLOCK_DIVIDER_1);
// Set SMCLK = DCO with frequency divider of 1
CS_initClockSignal(CS_SMCLK, CS_DCOCLK_SELECT, CS_CLOCK_DIVIDER_1);
// Set MCLK = DCO with frequency divider of 1
CS_initClockSignal(CS_MCLK, CS_DCOCLK_SELECT, CS_CLOCK_DIVIDER_1);
//Start XT1 with no time out
CS_turnOnLFXT(CS_LFXT_DRIVE_3);

GPIO_setAsPeripheralModuleFunctionInputPin(GPIO_PORT_P2, GPIO_PIN0, GPIO_SECONDARY_MODULE_FUNCTION);

// Configure UART
EUSCI_A_UART_initParam param = {0};
param.selectClockSource = EUSCI_A_UART_CLOCKSOURCE_SMCLK;
param.clockPrescalar = 52;
param.firstModReg = 1;
param.secondModReg = 0x49;
param.parity = EUSCI_A_UART_NO_PARITY;
param.msborLsbFirst = EUSCI_A_UART_LSB_FIRST;
param.numberofStopBits = EUSCI_A_UART_ONE_STOP_BIT;
param.uartMode = EUSCI_A_UART_MODE;
param.overSampling = EUSCI_A_UART_OVERSAMPLING_BAUDRATE_GENERATION;

if(STATUS_FAIL == EUSCI_A_UART_init(EUSCI_A0_BASE, &param))
{
LED_RED_ON;
}

EUSCI_A_UART_enable(EUSCI_A0_BASE);

EUSCI_A_UART_clearInterrupt(EUSCI_A0_BASE,
EUSCI_A_UART_RECEIVE_INTERRUPT);

// Enable USCI_A0 RX interrupt
EUSCI_A_UART_enableInterrupt(EUSCI_A0_BASE,
EUSCI_A_UART_RECEIVE_INTERRUPT); // Enable interrupt

// Enable globale interrupt
__enable_interrupt();

while(1)
{
// Send Temp Sensor Calibration Data
EUSCI_A_UART_transmitData(EUSCI_A0_BASE, '-');

__delay_cycles(900000);
GPIO_toggleOutputOnPin(GPIO_PORT_P1, GPIO_PIN1);

// Send Temp Sensor Calibration Data
EUSCI_A_UART_transmitData(EUSCI_A0_BASE, (uint8_t)gblLasteceivedUartCharacter_i);//(uint8_t)gblUartRxCharacter_i);

__delay_cycles(900000);
GPIO_toggleOutputOnPin(GPIO_PORT_P1, GPIO_PIN1);
}

-------------

NON WORKING CODE: Changed sections of the code are highlighted

#pragma vector = EUSCI_A1_VECTOR
__interrupt void FFE6_ISR(void)
{
switch (__even_in_range(UCA1IV, USCI_UART_UCTXCPTIFG)) {
case USCI_NONE: break;
case USCI_UART_UCRXIFG:
gblLasteceivedUartCharacter_i = EUSCI_A_UART_receiveData(EUSCI_A1_BASE);
__bic_SR_register_on_exit(LPM3_bits); // Exit active CPU
break;
case USCI_UART_UCTXIFG: break;
case USCI_UART_UCSTTIFG: break;
case USCI_UART_UCTXCPTIFG: break;
}
}

-------------

GPIO_setOutputLowOnPin(GPIO_PORT_P2, GPIO_PIN5|GPIO_PIN6);
GPIO_setAsOutputPin(GPIO_PORT_P2, GPIO_PIN5);

// Configure P2.5 - UCA1TXD and P2.6 - UCA1RXD
GPIO_setOutputLowOnPin(GPIO_PORT_P2, GPIO_PIN5);
GPIO_setAsOutputPin(GPIO_PORT_P2, GPIO_PIN5);
GPIO_setAsPeripheralModuleFunctionInputPin(GPIO_PORT_P2, GPIO_PIN6, GPIO_SECONDARY_MODULE_FUNCTION);

// Set PJ.4 and PJ.5 as Primary Module Function Input, LFXT.
GPIO_setAsPeripheralModuleFunctionInputPin(
GPIO_PORT_PJ,
GPIO_PIN4 + GPIO_PIN5,
GPIO_PRIMARY_MODULE_FUNCTION
);

// Set DCO frequency to 8 MHz
CS_setDCOFreq(CS_DCORSEL_0, CS_DCOFSEL_6);
//Set external clock frequency to 32.768 KHz
CS_setExternalClockSource(32768, 0);
//Set ACLK=LFXT
CS_initClockSignal(CS_ACLK, CS_LFXTCLK_SELECT, CS_CLOCK_DIVIDER_1);
// Set SMCLK = DCO with frequency divider of 1
CS_initClockSignal(CS_SMCLK, CS_DCOCLK_SELECT, CS_CLOCK_DIVIDER_1);
// Set MCLK = DCO with frequency divider of 1
CS_initClockSignal(CS_MCLK, CS_DCOCLK_SELECT, CS_CLOCK_DIVIDER_1);
//Start XT1 with no time out
CS_turnOnLFXT(CS_LFXT_DRIVE_3);

GPIO_setAsPeripheralModuleFunctionInputPin(GPIO_PORT_P2, GPIO_PIN6, GPIO_SECONDARY_MODULE_FUNCTION);

// Configure UART
EUSCI_A_UART_initParam param = {0};
param.selectClockSource = EUSCI_A_UART_CLOCKSOURCE_SMCLK;
param.clockPrescalar = 52;
param.firstModReg = 1;
param.secondModReg = 0x49;
param.parity = EUSCI_A_UART_NO_PARITY;
param.msborLsbFirst = EUSCI_A_UART_LSB_FIRST;
param.numberofStopBits = EUSCI_A_UART_ONE_STOP_BIT;
param.uartMode = EUSCI_A_UART_MODE;
param.overSampling = EUSCI_A_UART_OVERSAMPLING_BAUDRATE_GENERATION;

if(STATUS_FAIL == EUSCI_A_UART_init(EUSCI_A1_BASE, &param))
{
LED_RED_ON;
}

EUSCI_A_UART_enable(EUSCI_A1_BASE);

EUSCI_A_UART_clearInterrupt(EUSCI_A1_BASE,
EUSCI_A_UART_RECEIVE_INTERRUPT);

// Enable USCI_A1 RX interrupt
EUSCI_A_UART_enableInterrupt(EUSCI_A1_BASE,
EUSCI_A_UART_RECEIVE_INTERRUPT); // Enable interrupt

// Enable globale interrupt
__enable_interrupt();

while(1)
{
// Send Temp Sensor Calibration Data
EUSCI_A_UART_transmitData(EUSCI_A1_BASE, '-');

__delay_cycles(900000);
GPIO_toggleOutputOnPin(GPIO_PORT_P1, GPIO_PIN1);

// Send Temp Sensor Calibration Data
EUSCI_A_UART_transmitData(EUSCI_A1_BASE, (uint8_t)gblLasteceivedUartCharacter_i);//(uint8_t)gblUartRxCharacter_i);

__delay_cycles(900000);
GPIO_toggleOutputOnPin(GPIO_PORT_P1, GPIO_PIN1);
}

-------------

Thanks

Regards

Soumyajit

Part Number:TMDSDSK6713

Hi. I am Ammar and working on a real time audio processing project on DSP Kit  DSK6713 . I need more memory for my Code and trying to use SDRAM but it gives an error because when I call malloc why does it return 0x000000 ? 

Gel file is attached. Kindly help if I need to make changes in the gel file. Kindly tell if any changes or any configuration is needed.

Regards

(Please visit the site to view this file)

Part Number:OMAP-L138

I'm currently using processor_sdk_rtos_omapl138_5_01_00_11 on the DSP side of an OMAP L138 and have this code:

void dspEdma3EnableInterrupts(void) {
  *INTMUX3 = (*INTMUX3 & 0xFFFFFF00) | EDMA3_0_CC0_INT1; // maps INT12 to EDMA_0_CC0_INT1
  edma3_hwi_handle = Hwi_create(12, dspEdma3Isr, NULL, NULL);
  WHICH_EDMA3[IESR] = (1 << PARAM_SLOT_START); // NB, per sprugp9b pg 112, we cannot write IER directly!
  Hwi_enableInterrupt(12);
}

void dspEdma3Disable(void) { // call AFTER dspMcaspDisable()!
  Edma3Param *start = (Edma3Param *) &(WHICH_EDMA3[PARAM(PARAM_SLOT_START)]);
  memset(start, 0, sizeof(Edma3Param));
  WHICH_EDMA3[EECR] = (1 << PARAM_SLOT_START); // NB, sprugp9b, pg 110, cannot write EER directly;
  Hwi_delete(&edma3_hwi_handle);
  Hwi_disableInterrupt(12);
}

I'm trying to shed the RTOS.  I need to replace all the Hwi_* functions.

What is the equivalent bare metal way to do this?

I suspect what I need to know is (a) where in memory the interrupt vector table is and (b) how to enable/disable the interrupt.

I found the CSR.GIE and IER, so that's good.  Can I write them directly? I'm assuming yes.

I found the ISTP, but it points at 0x00700000, which is the L2ROM, so I suspect I need to move it in to RAM.

How do I write to the ISTP from C?

It looks like i need 0x20 bytes * 16 entries == 0x200 bytes.  But what goes here?  It should be executable instructions?  Does it need to be aligned in any way?  I'm assuming yes, and 4 bytes.

Looking at the existing entries, they all seem different, so I'm not sure what a generic entry would look like.  Maybe sprufe8b.pdf or sprui04b.pdf can help me...

I'm not a DSP assembly guru, so I'm a little lost at this point...

Part Number:MSP432P401R

Tool/software: Linux

Hi,

we are able to program exp-msp432p401r launchpad through JTAG using CCS. We want to known how to flash msp432 using BSL UART.

how to flash .txt firmware in msp432 launchpad from pc? can we use msp430 usb firmware upgrade tool for this?...

Part Number:LM5155-Q1

Tool/software: WEBENCH® Design Tools

I used WEBENCH to generate a design for the LM5155 where I am boosting 24VDC up to 100VDC with 0.2A output current. WEBENCH did the design and selected part values. I'm going through the datasheet to verify part selection and am getting stuck on equation 9 for the RSL value selection and equation 13 for Rf and Cf values.

Based on WEBENCH recommendations:
VLoad =100V
Vf=0.62V
Vsupply = 24V
LM = 33uH
RS = 47mOhm
fSW = fRT = 1.97MHz
RSL = 1kohm

Rf = 97.6 ohms

Cf = 1nF

Equation 9 says RSL should be selected to achieve 82% of sensed inductor current falling slope. If I set RSL = 1k as WEBENCH recommends my calculations come out to 127% (which I don't know if is possibe/allowed). If I solve for RSL to achieve 82% I get a resistor value of 173.11 ohms.

Equation 10 calculates the peak inductor current limit in steady state. If I use an RSL of 1k as WEBENCH recommends, the peak current is 1.64A which is within the specifications of the inductor WEBENCH recommends. However if I use a 174 ohm resistor for RSL the peak inductor current is 2.04A which is beyond the limits of the inductor. I don't mind picking a new inductor I just need to know which RSL is correct.

Equation 13 helps determine RC filter values for the CS pin. The Rf and Cf values WEBENCH recommended don't satisfy the required inequality. It's fairly straightforward to pick new values, I'm just not sure why WEBENCH recommended them if they don't work.

Part Number:CC3220SF-LAUNCHXL

Posting this to hopefully help other users having issues getting the SPI peripheral working.  After a few days of debugging, I have written my own SPI driver that is accessing the SPI registers directly to do a simple SPI loopback test.  In hardware, I have the MOSI tied directly to the MISO pin on the CC3220SF.  The symptoms I am seeing is that the value in the SPI_RX register does not seem to be related at all to what is physically present on the MISO pin.  I tried writing every value between 0 and 255 and I get a repeating pattern of 16 values back on the SPI_RX.

After trying every possible setting in the various SPI config registers I eventually tried moving the SPI clk from PIN_05 to PIN_45.  This fix resolved the issue and I was getting the expected values back in the SPI_RX register.  I tried this on two boards, a CC3220SF-LAUNCHXL and a CC3220S-LAUNCHXL.

I am expecting previously ordered PCBs to arrive this week and will update on how they perform.  I expect to have to do some rework to move the SPI clk to the new pin.

Part Number:TMS570LC4357

Hi,

 I'm trying to send and receive data simultaneously through sci module. For some reason the example given here(training.ti.com/hercules-how-tutorial-using-sci-uart-communication) doesn't work properly on my TMS570LC4357. The sciNotification(sciBASE_t *sci, unsigned flags) function isn't being called when I receive data. Is there any help that you can offer to solve this by pointing me to some guide or example which shows how we can read and write data serially through sci modules with rx interrupt.

   HALCoGen config:

    driver enable: enabled sci2

    sci2 Global: enabled RX high level interrupt

    VIM channelLin1: 13 enabled (IQR)

Part Number:TMS570LS3137

Tool/software: Code Composer Studio

Code Composer Studio Version: 8.2.0.00007

I've developed an application which I've been testing on an RM57L HDK for months. But when I try to debug my application on another copy of the HDK I get the following error message:

CortexR4: GEL Output: Memory Map Setup for Flash @ Address 0x0CortexR4: GEL: File: xxx.out Does not match the target endianness, not loaded. Check project build options and target configuration file (ccxml).

To be clear, this error doesn't occur when I debug on another seemingly identical HDK. I've verified that the Hercules Safety MCU Demos do run properly with the new HDK. What am I doing wrong?

Part Number:TMS320F280049C

Hi,

ECCDBLERR and PIEERR are inputs to the F280049's ePWM module.  There is no textual description for these signals, so just looking for some low level light.  Simple example:  Assume ECCDBLERR is just for uncorrectable Flash Errors when Flash ECC is properly enabled (and not for user configurable threshold on single bit), does this cover OTP?, etc?).   

Would appreciate a couple sentence description of these signals in order to eliminate assumptions.  Also, would be a good enhancement to the TRM.

Thanks,
Eric

Part Number:CC2640R2F

Is there a way to flash the board/ upload a program wirelessly?  Also, what is the best way to power the board while using a battery? 

Part Number:TPS54020

Dear TI Support,

Attached is a schematic drawing showing three (3) power supplies, each designed around the TPS54020 switching regulator.

The design team no longer exists and I’m trying to reverse engineer this design to see that it satisfies the requirements of the TPS54020.

A timing diagram is shown on the drawing which indicates Turn ON voltage and Coincidental Tracking.

I have a few questions about this design and was hoping TI could provide some recommendations and guidance.

My first question relates to the ON/OFF Threshold specified by the resistor divider of R3 & R5. Each supply has identical thresholds.

According to the datasheet, “To achieve clean transitions between the OFF and ON states, TI recommends that the turn OFF threshold is no less than 4.2 V, and the turn ON threshold is no less than 4.4 V on the VIN pin.”

Since the OFF & ON trip points are 4.2V and 4.4V (rounded), there is no margin. Additionally, the Main +5.0V input can range from +4.634V to +5.234V.

Secondly, I remain confused about how to calculate the Tracking resistors.

Based on the attached design, I cannot figure out how ΔV was calculated and if the selected resistors meet the design requirements.

Additionally, can you explain what the SS input threshold is that turns ON the part.

I clearly don’t understand this specification;

From a new design perspective, what would be the correct design steps for coincidental tracking. How does one arbitrarily choose values for VOUT1 and VOUT2, then guarantee that value of RS1 is satisfied.

From the datasheet “The ΔV variable is zero volts for simultaneous sequencing.” Well, if ΔV = 0V, then RS1 computes to 0Ω, and RS1 fails to meet the requirements of “RS1 > 2800 ´ VOUT1 -180 x ΔV”

So, based on the information provided, any assistance, explanation, and guidance you can provide is GREATLY appreciation.

Thanks so much!

Best regards,

Barry Weinberger

Barry Weinberger
Sr. Hardware Engineer

Curtiss-Wright
20130 Lakeview Center Plaza, Suite 200, Ashburn, VA 20147
T: 703-840-6727
bweinberger@curtisswright.com | www.curtisswrightds.com

(Please visit the site to view this file)

Part Number:MSP-EXP430F5529LP

Hi.

Is there a way to use the LP (and later minimize the design using only the few parts needed)

to get analogue values from sensors (e.g. temperature, conductivity, etc) into the LP, then use its ADC and get digital values via USB into a mobile?

Any advice appreciated, experts welcome, and if it exists please point me to it.

Thank you.

Part Number:LAUNCHXL-F28069M

Tool/software: Code Composer Studio

I create a custom todo tag, say FIX.  It is highllighted as a task in the editor, but it does not show up in the Task view.  Shouldn't it?

Code Composer Studio   Version: 8.0.0.00016

Mike

Part Number:LMG3410R050

We are investigating the possibility of paralleling two LMG3410R050 half-bridges for a high-power inverter design to exceed 12A. The datasheet mentions using "small decoupling inductors" for paralleling these parts. Do you have any more specific recommendations, including inductor sizing?

Part Number:CC1310

Tool/software: TI-RTOS

Hey guys,

I have Sensor Controller (SC) Studio 2.1.0.440. This is the first time I work with it, so sorry for beginner questions.

I want the SC to count the interrupts for me originating from a PIR sensor. I want the SC to do the task, because the interrupts cause a high current consumption on the CC1310 chip. There are currently 3 steps I perform and they work:

1. Initialize GPIOs, timer and semaphore to prepare the PIR sensor to work
2. I have two comparators. One of them causes a HwI if a movement is detected. So, if I receive a HwI I increment a move counter.
3. The move counter is send from the sensor to the collector in a data message, scheduled by the reporting_intervall of the TI 15.4 stack

I read some articles about the sensor controller and I do now have a lot of questions.

1. Do I have to make the initialization of the sensor (timer, semaphores and GPIOs including the GPIOs for the HwI) in the main application or in the SC task?
2. Do I use "GPIO Event Handler" to detect the GPIO interrupt in the Sensor Controller?
3. Since I need to detect two different HwI sources, do I have to make two different tasks in the SC, since each task can only handle 1 "GPIO Event Handler"?
4. How can I let the SC tasks run continuously? is this a setting in the SC task or do I have to set this in the main application and if so, how?
5. Is it possible to read the move counter, which runs in the SC, by the main application before sending the data message to the controller with a simple command?
6. Can I reset the counter in the SC from the main application?

Hope you guys can help me answer some of the questions so I can proceed faster.

kind regards

Slev1n

Part Number:TIDA-01513

Hello,

I have three questions concerning the reference design guide for the TIDA-01513.

1. There seems to be inconsistencies between what the diagram says and what the scope date illustrates. For example, at Figure 26, when the positive switch is re-opened, the ISO_NEG voltage drops back to reference. (This is for the negative error with 100k resistor to chassis) But in the diagram at Figure 38, at this point in time it says that if ISO_NEG is not equal to the reference voltage then there is an isolation error on the negative pole of the battery. Which is not what we observe at Figure 26. I am wondering what is the correct behavior to detect the positive, negative and both short to chassis errors. How exactly are we supposed to compare ISO_POS and ISO_NEG and what is the expected behavior for all the scenarios?

Also, there is the step after having evaluated ISO_POS after the activation of the positive switch where if ISO_POS is the same as VRef, it says to crosscheck with ... but doesn't say with what.

2. I wonder what the Confirm positive error steps means when ISO_POS > VRef. Because it goes at the same place than if it was not. What is the purpose of this step?

3. I have been using a simulation to try and replicate the results of the application but with no success. Here is the circuit used in TINA :

While I understand that the resistors are not the same values, I am unable to get the same behavior as in the exemples of the reference design guide in section 3.2.2.

Thank you.

Best regards

Louis Pelletier

Part Number:OPA548

Hi there,

I'm just wondering how to interpret the quiescent current rating on this dual supply part.  +/-20mA, does that mean 20mA from my positive supply and 20mA from my negative supply?  Or 10mA from each supply?

Thank you,

Mike

Part Number:AFE4300EVM-PDK

Good morning, I am using the evaluation module AFE300EVM-PDK and would like to know if you could provide me with a diagram indicating how I can connect the load cells.
I am using load cells of 50kg of three wires.
From already thank you very much.

Part Number:IWR6843

I'm currently working with a PCB manufacturer to design a custom radar board based on the IWR6843ISK. I'm planning on copying the antenna design from the development board as it meets the requirements of our application.

When they run the stack-up simulation using their Polar design tool, the resulting trace width (with an 8mil ground plan separation) is smaller than that used in the TI design, 6.3mil vs 7.795mil used for the ISK.

Using the 7.795mil trace width, an impedance of 46.3ohm is calculated.

Any idea where these discrepancies could be coming from?

Part Number:BQ24171

Posting for my customer:

I performed my first charge on a pack with the learned SREC loaded.  I have attached the log data and chart.  I have also attached the learned SREC. and GG file.  The cells are 6000mAh and my learned FCC was 5800.  I am wondering why the RemCap seems to have counted up correctly to 5741 then stopped when FCC was 5800.  Then updated the FCC to a lower value of 5592.  Any ideas ???

 Thanks!

(Please visit the site to view this file)