Quantcast
Channel: MSP low-power microcontrollers
Viewing all 64959 articles
Browse latest View live

Forum Post: RE: MSP-FET: MSP-FET Max Operating Temperating

$
0
0
Hi Christopher, the MSP-FET is a pure development tool and therefor NOT tested outside of room temperature. Best regards, Britta

Forum Post: MSP430FR5969-SP: Fast SPI

$
0
0
Part Number: MSP430FR5969-SP Can this part support a 10-12MHz SPI (3 or 4 lines) in Slave Mode?

Forum Post: RE: MSP-FET: MSP-FET Max Operating Temperating

$
0
0
Hi Christopher, Let me check with our tools team for the specification.

Forum Post: RE: CCS/MSP430FR5994: Program doesn't fit into available memory.

$
0
0
Hi Fatima, Can you explain or share what the 2 loops are doing. I need to understand how they interact with the IPE memory section.

Forum Post: CCS/MSP430G2553: How to send value to PORT2.1(LED connected & also blink) when IR sensor found obstacle

$
0
0
Ki, Thank you for your advice,but how to send value to PORT2.1(LED connected & also blink) when IR sensor found obstacle. Thanks Darshan

Forum Post: RE: CCS/MSP430FR5994: Program doesn't fit into available memory.

$
0
0
Hi, These are the loops: actions_num = ir(&actions.num[7]); for (i = 0; i < actions_num; i++) { lw(&actions.action_[7][i], (long)get_learn(i)); } and actions_num = ir(&actions.num[10]); for (i = 0; i < actions_num; i++) { lw(&actions.action_[10][i], (long)get_infer(i)); } Here is the structure it is accessing struct actions_ { int (*last_action_)(); int last_action; int last_num[NUM_ACTION]; int returns[NUM_ACTION]; int num[NUM_ACTION]; int (*action_[NUM_ACTION][MAX_NUM_EACH_ACTION])(); }; #pragma PERSISTENT(actions) struct actions_ actions = { 0, }; For more info, I am trying to recreate this project on my machine Above mentioned loops canbe found in learning_intermittent.c

Forum Post: RE: CCS/MSP430G2553: MSP430G2553, CCS

$
0
0
This is a different topic and best served in the MSP forum. I will split it off this thread and move it there. In the future, please start a new thread for a new topic Thanks ki

Forum Post: RE: RTOS/MSP430F5529: normal pin configuration in the pin config array

$
0
0
Hi Wajih, I'm going to mark this as closed since we really cannot progress if you don't have a board. When you get a board and if there are issues, please post a response to this thread or open a new thread if this is locked (which happens after a few weeks of inactivity). Todd

Forum Post: RTOS/MSP432E411Y: GPIO_init generates spikes for open drain configuration

$
0
0
Part Number: MSP432E411Y Tool/software: TI-RTOS Dear TI-Experts, I'm somewhat unhappy about the GPIO_setConfig called by GPIO_init: /* Configure the GPIO pin */ GPIODirModeSet(portBase, pinMask, direction); GPIOPadConfigSet(portBase, pinMask, strength, gpioType); /* Set output value */ if (direction == GPIO_DIR_MODE_OUT) { GPIOPinWrite(portBase, pinMask, ((pinConfig & GPIO_CFG_OUT_HIGH) ? pinMask : 0)); } For totem-pole or open drain output configuration it first enables the output before setting the correct value, if the initial value is high (after POR). Especially in open drain configuration this makes trouble, because the processor interacts with the environment, while it is not intended to do. E.g. a wired-Or interlock. Could you place the "GPIODirModeSet(portBase, pinMask, direction);" command at the end of the sequence,like /* Configure the GPIO pin */ GPIOPadConfigSet(portBase, pinMask, strength, gpioType); /* Set output value */ if (direction == GPIO_DIR_MODE_OUT) { GPIOPinWrite(portBase, pinMask, ((pinConfig & GPIO_CFG_OUT_HIGH) ? pinMask : 0)); } GPIODirModeSet(portBase, pinMask, direction);

Forum Post: RE: CCS/MSP430FR2111: How to decode NEC IR remote control data using MSP430FR2111 MCU.......

$
0
0
Hey Nilesh, I found another resource that may be more helpful. It looks like some example IR decoding SW is also included. You may have to change some of the pin configurations since the example code was written for the G2553 device, but this should be a good starting point. e2e.ti.com/.../665510 Thanks, Mitch

Forum Post: MSP432E401Y: Bug in SimpleLink SDK DriverLib EMACTimestampSysTimeGet()

$
0
0
Part Number: MSP432E401Y Hello, There appears to be a bug in this function: void EMACTimestampSysTimeGet(uint32_t ui32Base, uint32_t *pui32Seconds, uint32_t *pui32SubSeconds) { // // Parameter sanity check. // ASSERT(ui32Base == EMAC0_BASE); ASSERT(pui32Seconds); ASSERT(pui32SubSeconds); // // Read the two-part system time from the seconds and nanoseconds // registers. We do this in a way that should guard against us reading // the registers across a nanosecond wrap. // do { *pui32Seconds = HWREG(ui32Base + EMAC_O_TIMSEC); *pui32SubSeconds = HWREG(ui32Base + EMAC_O_TIMNANO); } while(*pui32SubSeconds > HWREG(ui32Base + EMAC_O_TIMNANO)); } It should either be ```while (*pui32Seconds != HWREG(ui32Base + EMAC_O_TIMNANO))``` Alternately the order the reads could be swapped.

Forum Post: RE: MSP432 Launchpad Problems with Internal Temperature Example from DriverLib

Forum Post: RE: MSP430F6734A: What is the Internal Temperature sensor accuracy with TLV calibration data

$
0
0
With Vcc=3.3V and 5 mA you have 16.5 mW. PN 80 package rated @61.5 degC/W gives 1.01 K upheat. The way you attach the thermocouple should not cause so huge differences. Moreover, @ -20C errors should be lower than @ +60C. If you supply your board using a battery, the battery could be a source of problems because Vbat could be much lower @ -20C than @ +20C. However, it does not explain error @ +60C. I have no idea how to help you. Could you recheck your temp. compensation formula for '(' errors, etc.?

Forum Post: RE: RTOS/MSP432E411Y: GPIO_init generates spikes for open drain configuration

$
0
0
A workaround for other people having the same issue: Call GPIO_initWorkaround before GPIO_init. GPIO_initWorkaround sets the hardware registers according to the GPIOMSP432E4_Config data, such that GPIO_init does not make trouble. (Please visit the site to view this file)

Forum Post: RE: MSP430FR2512: Captivate - MSP430FR2512 Wake-up from any touch key

$
0
0
Hello Huang, In CapTIvate low power mode (referred to as wake on proximity mode), the CapTIvate state machine can only measure and process one cycle, which is cycle 0. Typically, on an MSP430FR2633 , up to 4 blocks (one pin from each block) can be assigned to cycle 0 and are measured in parallel in the (wake on proximity mode). So what you are attempting to do would work on the FR2633. However, since your MSP430FR2512 has only one CapTIvate measurement block (CAP0), only one button can be assigned to cycle 0. Your second button is assigned to cycle 1, a third button is assigned to cycle 2 (if you had more than 2) and so on. You can manually enable/disable the second button just as you enter and exit from the (wake on proximity mode). Here is an example. Note, since the second button is already defined in your code as an RX pin, you only need to use the CAPT_setChannelActive() just before entering (wake on proximity mode) and CAPT_clearChannelActive() when exiting (wake on proximity mode).

Forum Post: RE: MSP432E401Y: Cannot enable CAN0 controller - SysCtlPeripheralReady() always returns false

$
0
0
Hello Josh, Looping at that line leads me to believe that it might be an issue with that specific MCU (especially if it's occurring on the LaunchPad). Basically that line is saying that the CAN peripheral is not ready, that's a hardware issue, either the PCB design fault or MCU fault. I had checked the application on two different LaunchPads, resetting continuously for about 5 to 10 times. Also tried to use the debugger. It did not get stuck at any of the CAN initialization. FYI - The new SDK is available here: www.ti.com/.../SIMPLELINK-MSP432-SDK . You can try this to see if it solves the issue. I am not too confident of that as I believe the issue you are facing is hardware related and not software. Thanks, Sai

Forum Post: RE: MSP430F5242: I2C Driverlib, repeated start condition

$
0
0
USCI_B_I2C_masterSendSingleByteWithTimeout() does a complete I²C transaction, i.e., it generates a stop condition. For a repeated start, you have to send the first byte(s) while pretending that more could follow (USCI_B_I2C_masterSendMultiByteStartWithTimeout()), and then, without doing a stop first, simply start receiving (USCI_B_I2C_masterReceive*Start()).

Forum Post: EVM430-FR6047: LCD display

$
0
0
Part Number: EVM430-FR6047 I am running the vanilla code on EVM430-FR6047 board. I do not have it connected to transducers yet, but expect to see activity on the LCD display. I've tried pressing all five buttons, but nothing seems to be happening on the board. Questions: - do I need transducers to see something on LCD? - Which way to turn the potentiometer (CW, CCW) for maximum contrast?

Forum Post: RE: MSP430FR5969-SP: Fast SPI

$
0
0
The SPI module is designed so that it can communicate with another MSP430 as the master at 16 MHz. For the frequency, see footnote 1 of table 4-20. However, the important thing is not the frequency itself, but the setup/hold times of the master.

Forum Post: RE: EVM430-FR6047: LCD display

$
0
0
Hello Stephen, The LCD should turn on when the top button is pressed. I just tested and it does still turn on even without transducers connected. See section 9 of the users guide below for LCD operation details. If it is not turning on, you may have a bad switch on the board. Try again and let me know the outcome. www.ti.com/.../slau720b.pdf
Viewing all 64959 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>