Rickta59
-
Content Count
1,135 -
Joined
-
Last visited
-
Days Won
71
Everything posted by Rickta59
-
I went to the trouble of trying to include valid xml text .. jeez now the "BBcode" drop down doesn't include that ..
-
no different
-
I have tried turning off all the wysiwyg .. and just typing ... © let's see what this does
-
I'm not pasting anything all i did was press ( c )
-
©
-
I'm using google chrome on linux .. or mac .. or android .. all i did was reply in the box below .. and type © and press "POST" btw i typed 3 chracters '(' 'c' ')'
-
-
It seems to have broken all the old posts .. just search for 'icon_e_wink.gif' ... or the copyright symbol ... code that used to say © ...
-
Is it just me, or does this ip.board really suck when it comes to dealing with preformatted / code blocks? I've gone back and looked at some code I and others have posted. Why isn't there an easy way to include code with something like phpbb does with bbcodes? Take this post for example: http://forum.43oh.com/topic/1284-software-async-serial-txrx-without-timer/?p=12640 Something has gone in and rewrote the for loop code and stuffed html image tags in there ? What can we do so I can use code from old posts without having to try and figure out what got replaced with html tags?
-
Seems to work fine with msp430g2553 .. and fails with msp430g2231 and msp430g2452. Are you using a g2231 or g2452? If so this code isn't going to work. The IR demo code uses both serial and the TIMER1. The g2231/g2452 chips don't have a second timer. So it won't work. This code should probably have a #ifndef __MSP430_HAS_T1A3__ #error "this only works with the msp430g2553" #endif -rick [Edited: .. wasn't a problem with UART and TIMER0 conflict, but more that IR code uses the second timer (TIMER1) and g2231 and g2452 chips only have one timer]
-
msp430g2553.h uses some defines that are conflicting with this code. ... /************************************************************ * STATUS REGISTER BITS ************************************************************/ #define C (0x0001) #define Z (0x0002) #define N (0x0004) #define V (0x0100) #define GIE (0x0008) #define CPUOFF (0x0010) #define OSCOFF (0x0020) #define SCG0 (0x0040) #define SCG1 (0x0080) ... The #define for 'C' and 'N' are -
In the code below the green led only blinks when you aren't holding down SW2. /** * lpmfoo.cpp - low power mode testing with ISR tests * * Desc: simple test to see if ISRS block other ISR execution * * Uses: P1.0 - RED LED * P1.6 - GREEN LED * P1.3 - SW2 push button * * Compiled with: * msp430-gcc -DF_CPU=1002400 -mmcu=msp430g2553 -mdisable-watchdog \ * -Os -g -fdata-sections -ffunction-sections -Wl,--gc-sections lpmfoo.cpp * mspdebug rf2500 "prog a.out" * * Author: rick@kimballsoftware.com * Date: 01-26-2013 Created * */ #include <msp430.h> #
-
This might be a reasonable approach. For the next release of Energia it might make sense to try and focus on some low power optimizations like this. You are all welcome to take a stab at it. -rick
-
I don't think other ISR routines, like the watchdog, can interrupt your ISR unless you enable GIE inside your ISR. I could be wrong but that is my impression. In slau144i, page 38 it talks about the GIE being cleared "6. The SR is cleared. This terminates any low-power mode. Because the GIE bit is cleared, further interrupts are disabled." In slaa294a, page 3 it says something along those lines also: "Given this ability to change the power mode from the ISR, the developer can choose to implement the full functionality of the ISR within the routine itself, or use the ISR to wake u
-
The code I shared does all its work in the ISR routines, flipping between LPM4 and LPM3. Once loop() calls LPM4; .. it never gets control again. -rick
-
https://github.com/energia/Energia/blob/master/hardware/msp430/cores/msp430/wiring.c line 222 ... /* Exit from LMP3 on reti (this includes LMP0) */ __bic_status_register_on_exit(LPM3_bits); which is why you need to disable the watchdog isr to even do anything with low power and Energia.
-
[Energia Library] Nordic nRF24L01+ library
Rickta59 replied to spirilis's topic in MSP Energia Libraries
This is great thanks spirilis. Just got my radios in the mail today and less than an hour later after reading some docs and finding pin descriptions on my radio modules I had it going. I loaded up the TX_demo on a g2452 and the RX_demo on a g2553. Powered em up, opened 2 serial windows and watch it successfully set the red led remotely. Nice work! I did apply the usci code change you suggest in my energia core code and the usci spi g2553 fix (github issue #164) I got my radios on ebay. 10 for ~$12 .. amazing .. cheaper than dumb 433MHz radios ebay search string: '10Pcs NRF24L01 -
There is actually more than sleeping or not sleeping. You might want to sleep in LPM4 until an external interrupt is detected, at that point you might just want to switch to LPM3 to run a clock, and then switch back to LPM4. In a previous post, http://forum.43oh.com/topic/2759-problem-with-interrupts-on-p1-and-a-timer/#entry23367 , I outlined some replacement code for the underlying interrupt structure for that posters specific problem. I created an attachInterrupt2() function that allows you to adjust the power mode from user functions called from the ISR. Energia is an msp430 implementa
-
What are you doing that you are messing with the DCO? I've never had a problem setting the clock or seen any glitch or hang. I use: DCOCTL = 0; BCSCTL1 = CALBC1_16MHZ; // could be any value DCOCTL = CALDCO_16MHZ;
-
Other people running ubuntu 12.04 who have used the launchpad with it. http://forum.43oh.com/topic/2296-linux-serial-communication-working-wmodified-cdc-acm-module/ You also need to create a udev entry so that non-root users can access /dev/ttyACM0. Thinking about it ... that is probably your problem. Sorry I didn't mention it earlier. $ cat /etc/udev/rules.d/61-tilaunchpad.rules # This file allows access to TI launchpad # See udev(7) for syntax. # SUBSYSTEM=="usb",ATTRS{idVendor}=="0451",ATTRS{idProduct}=="f432",MODE="0666" search 43oh.com for 'udev rules' for more in
- 19 replies
-
- 1
-
-
- Hardware uart
- linux
- (and 1 more)
-
btw, do all those tests without energia running.
-
Have you looked at your dmesg output? Unplug your launchpad, wait, wait ... open a command window and tail your syslog. # tail -f /var/log/syslog ... plug in your device... look for output that looks something like this: Jan 24 14:44:56 ubuntu kernel: [688267.722444] usb 1-1.1.1: USB disconnect, address 38 Jan 24 14:45:01 ubuntu kernel: [688273.056218] usb 1-1.1.1: new full speed USB device using ehci_hcd and address 39 Jan 24 14:45:01 ubuntu kernel: [688273.193294] cdc_acm 1-1.1.1:1.0: This device cannot do calls on its own. It is not a modem. Jan 24 14:45:01 ubuntu kernel: [68827
-
On my ubuntu 11.04 setup, I cannot use the cdc_acm driver that ships with the system. When I plug in the launchpad it just locks up the system while it tries to enumerate. If the firmware you load on your launchpad prints before ubuntu has enumerated then it just fails. Basically, the stock cdc_acm doesn't like the way the usb serial port firmware works on the launchpad. So, have you tried using the modified linux cdc driver mentioned in the wiki? You do have a version 1.5 launchpad board yes? Rotating the jumper pins on a 1.4 board will damage your board.
-
Is there some reason you are using that vs CCS v5? With version 5 they dumped some of the custom plugins they had developed that seemed to cause crashes and slowness in version 4. When I originally tried out CCS v4 I was amazed how far removed from the latest version of Eclipse it was. The CCS v4 version didn't even do source code formatting. The kind of source code formatting that happens with a right click and allows you to pick a variety coding styles K&R, BSD, AT&T or even a version with your own custom code style features. With Energia I really miss the source code inspec
-
A common reason that java applications are slow is that anti virus programs will verify java and each of its jar file which can be quite large. On my setup with linux Energia starts up appears quickly as I'm not running any virus stuff. The few times I've tried it on windows it also launched quickly ... seconds not 10s of seconds. But then again I wasn't running any anti-virus. I just tried on a 2009 imac and it was ready to run in less than 4 seconds... again no virus program. -rick