Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by veryalive

  1. good to hear from you! i'll be there very soon, alta vi area.
  2. thank you, @@tripwire. I overlooked that the 432 LP xds emulator is for arm devices. 432 LP manual excerpt below. I only spotted the serial debug from the emulator onboard the 432 LP (table 1 in the document mentioned immediately below) and hoped it supported sbw. It appears to be jtag. But, nevertheless, thanks for sparing me an incorrect purchase. cheers ================ excerpt from 432 LP user guide --- SLAU597A
  3. @@chicken @@Fmilburn or anyone familiar with the energytrace hardware on Launchpads ........ Hi, A big 'Thank You' to Fmilburn for your clear and useful tutorial on energytrace with CCS and Energia. I'm very interested in energytrace and want to purchase a Launchpad with that capability. I use CCS mainly, and find energia invaluable for fast prototyping. My chips of choice are 5529 2553 2452 2252 2271. But I want to try the 432 ARM Launchpad, (with its ez-fet and energytrace) instead of buying another xx5xxx type launchpad. So, here's my question: >>>> can I use the 432 ARM Launchpad to power / program / energytrace / backchannel async standalone MSP430F/G chips <<<<< ????? I've looked into it, and, on paper, it appears that its possible, but I just wanted to check with you guys to make sure. Many thanks !!
  4. often, i like a very very simple terminal program just to monitor async streams from multiple projects. and tiny enough so that i can run multiple instances on my desktop / or 2nd monitor extended desktop. here's a couple, both are free: - PComm terminal emulator. moxa (from ethernet / serial bridges). features - auto serial port finding. - nice hex display. - Mosaic Terminal. (from Mosaic Industries, a single-board-computer supplier) features - selectable background colour so it is easy to identify which output I'm receiving. I find the CCS v 6 terminal window handy of course. cheers..................
  5. Ahhhhh OK. thanks. so MT is RTOS, i gather (where MT = multitasking in energia, done with customized TI RTOS I presume) cheers....
  6. BRAVO, FOLKS !! May I ask : Which processors are supported with the RTOS multitasking? Or another way to say it: when are the RTOS libraries invoked / restricted while building a sketch? Many thanks for a great package...
  7. Hi guys. I used Zeke's sw a long time ago, so maybe my recollection is correct / useful: .... Check your bit times with a scope ....? I recall changing baud rate down to 9600 and also got bit errors. The logic analyser showed faster bit times than 104 uSec (9600), it was around 95 or 97 ? When I adjusted dividers in the async uart setup routine, it worked. Maybe this helps? Cheers....
  8. 2553 is great! I often downsize to other favorites for which I have small stock on hand: 2252, 2452.
  9. I still have this problem. Hovering over 'tools', or accessing files such as 'examples', or previous sketches causes a delay before energia reacts. It is disturbing and I really wish I could get it fixed ! @@energia ? I'm using vista, tried with/without antivirus, etc, the usual stuff. Being suspicious, I'm wondering if it started when I began with 5529 launchpad? It didn't happen with G2 chips. Are there any ideas out there on how to fix this??? Super thanks !!
  10. I just started having this problem too, @@energia. Started with version 14, which I recently upgraded to. When I hover over 'Tools', Energia hangs for a long time (minutes/minutes) before that menu drops down. I haven't had the time to dig into this yet, however. But, I'd jump at an easy solution if one came up in the meantime!
  11. There's a free programmer / loader I found. See below. It seems very nice, I used it a few times to save raw binary files, inspect / erase flash, etcetera. As I'm working primarily with LPs and single quantity projects, I don't use that tool. Maybe this is something for you : FET-PRO430 lite (free) http://www.elprotronic.com/download.html O
  12. Thank you ! I did not realize this about the FR5969 launchpad, thanks. <<< EDIT --- now checking that FR5969 !!!!! >> Interesting for me. Variable Vcc. Blow the fuse. (Others TBD?). Possible upgradeable with TI firmware (don't know). So, the MSP FET it is at that price. << but still checking the FR5969 >>>> FWIW - to confirm other folks' observations: - shipping cost is now included. To bad, but it was bound to happen - the discount code works - and deducts - right on the first page of ordering on MyTI - I like the new look of the TI online shopping page. Thanks you @@spirilis O
  13. The MSP-FET looks very interesting to me.... 60% off $115 is $46 price for this?!? >>>> Here is A REQUEST FROM A KNOWLEDGEABLE USER please? >>>>> Is this FET unit the latest / greatest MSP debug tool on available from Texas Instruments today ? I've read the forum posts and FETs, in general, seem to get great ratings across the board / CCS compatible / etcetera. ( to self: Is it time to buy an MSP-FET ?) Cheers ! O
  14. I've seen it and was impressed. (was it over a year ago?); but did not see much written at the time. Personally - I got a Saleae 8 bit instead at that time. Currently, I'm stalled on a Rigol as I'm OK with my Tektronix analog. I don't need much analog bandwidth for what I do with microcontrollers. NOW, I'm interested (again) in that Analog Discovery tool, because folks on this forum are very to-the-point. I'm curious about your real-life experience (eg: @RobG) EG: How is the logic analyser part - can it compare to Saleae Software? Is it really 16bit capture? Only 2 triggers? Is there pre-trigger on logic analyser and digital scope? And is it any good? How is the user interface; combined analog/digital triggering .... etcetera. I saw the EEVblog a few times, but it's more a rundown of features & functions rather than hands-on experience. Cheers, Good 2015 !!! O
  15. CONGRATULATIONS to both of you. This is wonderful news !! So she did indeed include "........., something blue."
  16. just curious - did you intend to post 'I2?C' ? i see 'software serial' posted .... cheers !
  17. first off, please note the 7447 maximum Vcc is about 6 volts, from it's 5 volt TTL heritage. i suspect that 9 volts could burn your 7447. i quickly add that i've pushed TTL and HC logic well over their Vcc/Vdd max on many occasions to get more speed (out of HC). secondly, a 7447 with 5v ---> this means that turning on 2 series blue LEDs, whose combined total voltage drop is somewhere around 6 to 7ish volts (batch dependent) might not happen if you stick to 7447 Vcc specs. so - your decision #1 is how to turn on those 2 LEDs reliably, for which you could try boosting the 7447 Vcc on your breadboard. this in fact means the 7447 drivers power dissipation per driver pin can be very small, and this is an important, practical side-effect. Example: Vcc = 7.0v Vled = 3.2v Vsat 7447 = 0.1v so the 7447 output transistor drops only 0.5v at its given current. As a practical matter, you have to adjust Vcc on the breadboard so that the 2 blue LEDs turn on. However --- here's an idea you may want to consider --- 'it the spirit of experimentation' - and to understand how volume production handles this situation Try pulsing the LEDs. you'll likely be doing this as part of the clock digit scan routine anyway. If you were using only ONE LED, you would connect the MSP430 output pin directly to the LED itself, anode or cathode depending on your design. TIMING (one LED driver pin -or- 7447 RBIpin5. or 4bits if you are sending bcd to 7447) or etcetera: ====== __________ _________________________ _________..... ____ ___| dim LED |_____________________| bright LED |______| ....___| . A B A C A D A --> timing A to A is constant, let's call it the 'scan rate' --> timing A to B produces a dim LED as it is short --> timing A to C produces a bright LED as it is 2x longer than A-B --> BtoA CtoA and DtoA are required to prevent 'ghosting' The current into an LED that you measure with a DC connection will be higher than the current used by the LED in a pulsed situation. This is what consumer electronics folks figured out decades ago to cut cost in display units. It is better design. As a plus, one can become more familiar with programming duty cycles with microprocessors for all sorts of things : LEDs, stepper / other motors, even switching power supplies have been I/O pins, a timer ISR, inductor and transistor for ages now. Last point, which is certainly known by you as an experienced clock maker making a(nother) one --- your could read the ambient room light level with a 'light dependent resistor', average it's value, then change the LED on-times accordingly.
  18. veryalive


    oh well, fwiw: in my mail box today, not directly related to 430 stuff, but will be supported by 430 (read on).... ======= Crystals : ======= 1----- 4.194304 MHz. quantity 29. in order to build some IF filters for a 30 meter band ham radio transceiver. The LO is a super-vcxo based on standard 14.318 4x colour burst xtals. (LO - IF = 10.124 MHz. 30m band 10.1-10.15) MSP430 task - control various aspects of the radio: tuning/display/etc/ auto antenna tuner. 2----- 9.8304 MHz. qty 20ish. still indulging myself with hc811E and hc11F1 (3MHz versions. so, 9600bps bootstrap mode). Several projects with MSP430 overtones: I'll get the existing HC11s to become SPI slave devices to the MSP430 to do additional processing. eg: - inductance meter (shifted Fo technique) - antenna swr / impedance -- etc
  19. veryalive

    A buffer?

    A very handy buffer IC, and often under utilized, is the CMOS 4050 (MC14050, CD4050, etc... also in HC ). This is a cheap way to protect AND translate high voltages (up to 15v) down to the low voltages (+-3.6) tolerable by the MSP430. With this buffer, you can safely input digital signals into the MSP430 which have a HIGHER voltage than the MSP430 supply ! Connect the 4050 supply voltage (Vdd) and ground (Vss) to the MSP430 supply & ground, and the 4050 buffer output(s) to the 430 input pin(s) ---- then 'external world' digital signals go to the respective 4050 inputs. Please refer to the 4050 - type datasheet and read it a few times and then get a few parts, they are very cheap.
  20. yeah, i thougfht it was a shift register too, 74hc299 or 323 type, but there are too many wiring differences (or errors) for it to be that type - including no vcc/gnd.
  21. actually, the sound card scope is a great idea. i should really use it more often for low frequency stuff. here's the one i use, v1.4.1 (i have no affiliations, but take my hat off to herr zeitnitz):
  22. good to know about pulseIn ! i didn't use it at that narrow a pulse width (200 uS) glad to hear that you checked the source code as a bonus ---->> as an alternative, perhaps the Energia 'microcseconds' function micros(), with a call at the rising edge, a second call at the falling edge, then a subtraction. cheers,
  23. .... i'll throw my hat into the ring here .... if the question still is : 'how fast does this execute' ------> and additionally: - you'd like it to be easy to set up - you have an additional Launchpad and serial port (or spare LCD) available - you are satisfied with +- 10 / 20 uSec resolutions - you don't want / need a scope or logic analyzer then, in the spirit of 'rapid prototyping', here's an idea. please note I haven't done this, but i've used these energia routines myself. I use Energia and a bunch of handy, jumperized, IO devices for quickie measurement projects. DIAGRAM: ======== your existing LP#1 is your 'simulator', already described. The LP#2 just measures and displays a pulse width. LAUNCHPAD#1 -------> PULSE OUT PER LOOP ---> LAUNCHPAD#2 TO BE TIMED (2 wires) MEASURING ----> DISPLAY (SW added to toggle a pin THE PULSE (SERIAL or LCD) a pulse at top of loop) OVERALL DESCRIPTION: ==================== - for the loop timing to be measured (ie: how fast does this execute) LP#1 has a spare IO bit set for output which toggles at the top of the loop (XOR). The resulting high pulse is wired over to LP#2 to be measured and displayed by a quick-'n-dirty Energia script. SOFTWARE ======== LP#1 - you know how to do this. and you've wired 1 output bit + ground to LP#2 input bit of your choice. LP#2 - i think you've worked with Energia. Key is the pulseIn() function. So here's some example code: int pin = 7; unsigned long duration; void setup() { pinMode(pin, INPUT); } void loop() { duration = pulseIn(pin, HIGH); } --------------------------------> then display 'duration' to the device of your choice
  24. think of 'averaging' as a low pass filter in this case. if you use the 16-sample-then-average (window size 16), then one noise spike in that batch of samples gets strongly reduced. in the other case, where you take the last sample added to the running average (window size 2, sort of), if the last sample is a noise spike, it will come through distinctly. (EDIT 1 - in fact, it's a convolution - a time-domain rendition of a low pass filter - which can lead to some very interesting filtering in a 430 with the hardware multiplier. A FIR, if you're a DSP guy. Block averaging being a 'rectangular' window. Other shapes are handy, like sin x / x or triangle, and correspond to the filter's frequency response expressed as the time-domain impulse response.) (EDIT 2 - and to your question on 'oversampling', this means the sample rate (ADC rate) compared to the highest signal frequency of interest (eg: the change in temperature of a room). In many uController apps, our sample rate is much higher than the signal's rate of change ---- eg: Ksamples/sec vs Degrees C per second --- and this is an example of oversampling. You can throw away samples (decimation) if you want to reduce computation / memory array size / etc without significantly reducing the fidelity. Note, FIR filters have a delay. Much of this is equally - or better - handled in the frequency domain.)
  • Create New...