Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by veryalive

  1. veryalive

    Hi from the Netherlands

    Goede morgen - onder de rook van A'dam
  2. veryalive

    msp430fr2355 serial monitor

    a clarification: - if you use energia : just wire up an async FTDI module to the LP 'backchannel' then use your favourite async sw (putty) - if you use CCS : as above; plus write your own async driver. ccs printf() can be made to send characters to the async port -or- write a 'tiny printf()' - there's a good one somewhere on this forum as I recall (by opossum).
  3. veryalive

    msp430fr2355 serial monitor

  4. veryalive

    msp430fr2355 serial monitor

    this is a known problem with the 2355 launchpad emulator section. (FR2433 as well). The output from the emulator to the PC is delayed many seconds in time , OR, comes out quickly when the emulator buffer contains 64 characters. TI will not fix it any time soon. It has been reported on the e2e forum as well. A workaround is to either wait that time for the characters, or write your own async driver, then wire the launchpad async port directly to an off-board module like an FTDI-type. This may be a bit complex if you've never done it before. I wish there were better news, but that's it !!
  5. veryalive

    MSPflash do not work on MSP4305969

    As I'm just learning about FRAM on Energia -- and referring to the example above: QUESTION --- does count need to be declared persistent ? (or other declared as other type?) cheers,
  6. veryalive

    Promotion of MSP430FR2433 MCU LaunchPad™ kit

    Yes, the new FR2433 LP is a nice one; and good value-for-money. The I/O is generous and handy. I'm curious why TI configured it's internals the way they did. What is the end-user application(s)? Why the HW 32 bit MPY (yes 32), only a 10 bit ADC, CRC, small FRAM, large SRAM; etcetera. Thoughts?
  7. veryalive

    Suggestions on MCU/Chip Selection

    Like the old saying goes" "Better never than late".... or was that the other way around ?!?
  8. veryalive

    NRF25L01 MSP430 to Arduino

    I have used the nRF24L01 Spirilis library both on Energia and CCS; both worked well. I used it point-to-point. My target was '2553. My only wish is that I would have more time to dig into this library and this excellent, low cost nRF further; alas, not to happen soon. cheers,
  9. Hi all, Something called 'Pythagoras Week' means free shipping and a few discounts at the TI Store ... http://www.ti.com/lsds/ti/store/pythagorean-week-august.page?HQS=rtp-tistore-promo-pythagweek17-bitpp-lp-null-wwe
  10. Ah, OK. I see you are not using the SPI however. I don't have a CC3200 - I'll try this on a 2553 / 5529, E17 for interest, this weekend, just to see what happens. I use the SPI / I2C / etc on Energia to quickly try things, so your observation is of interest to me. Maybe someone else on this forum has more experience with your exact configuration....
  11. Which processor are you using? I'm wondering about SRAM memory limitations / buffers breaking. FWIW, I generally use Energia 17 for my non-CCS 6.3 projects; mainly using CCS however. mvg,
  12. veryalive

    My Stupid Question Space

    Yes, that's the logic analyser. Good price, too. I have 4 of these units attached to various projects / breadboards. And using two laptops the odd time. Cheers.
  13. veryalive

    Solar power display

    Yep, a great application. May I inquire : are you muxing the LED array one digit -or- one SEGMENT per digit at a time ? Any the 'ON' time ? Just curious how much current the IO pins can supply, it sounds like there's no series limiting resistance, which is perfectly OK. Cheers.
  14. veryalive

    My Stupid Question Space

    May I recommend that you consider buying a cheap (sub $10), 8-bit, low speed (eg 24 MHz), logic analyser sooner than later ? That, plus experience with the MSP430 'register page' of the CCS IDE 'Debugger' will be good friends to help you sort out the programming of MSP430 family peripherals. Welcome to the forum!
  15. Its definitely possible to program the 2553 / 28 pin device with the Launchpad - especially with CCS. So, likely there's a PCB / wiring issue on your proto. Looking at your schematic.... the capacitor C2 / 0.1 uF -- not needed. Reset needs a +- 30K pullup / 1nF to ground but this may already be provided - depending on where exactly you wired your jumper onto the Launchpad. Can we assume that you've got +3volt / GND connected? Anything else on the schematic we should know about? And I would start with the CCS 'blink' example (toggles P1.0 - often connected to an LED), just to check the communication via Spy By Wire. Keep going - it'll work !!
  16. veryalive

    I hate it when I forget...

    would those have been rev 1.4 -or- rev 1.5 ? just curious as I have both. Thanks
  17. veryalive

    More C versus C++

    The Dan Saks video is brilliant! Thank you for posting.
  18. Very nice to see some new, practical projects on the forum ! Its great to learn from these.
  19. Hi folks, I just spotted the TI Store announcement ----> Free Shipping on orders this week. http://www.ti.com/lsds/ti/store/engineers-week-february.page?HQS=rtp-tistore-promo-engweek17-bitpp-lp-null-wwe I haven't tried it yet. Cheers
  20. veryalive

    Set PinMode on 2 pins simultaneously

    Hi, I've been following your bit-bang I2C efforts. If you are making a custom version, perhaps using direct port I/O would be useful? As follows: P1DIR |= BIT7 + BIT6; // make these outputs P1OUT |= BIT7 + BIT6; // make them simultaneously go hi P1OUT &= ~(BIT7+BIT6); // ditto, but go low The only thing is that it departs from energia statements. I suspect you must have a scope / logic analyser or you wouldn't have known / measured the delay between the two PinMode statements you tried? Is this OK for your app? Cheers,
  21. veryalive

    Fading an LED....With an Stellaris EK

    Not knowing your level of experience, I'll offer this C - for - embedded course on youtube...
  22. veryalive

    DriverLib Examples for the MSP430F5529

    Thanks folks, I'll give that a try. cheers...
  23. veryalive

    DriverLib Examples for the MSP430F5529

    Thank you @@Fmilburn Your article got me interested, again, in driverlib. In fact, I was not able to get it working when I first tried some months ago, and I'm having the same problem as I did on my first attempt. Here's an open question to you or the forum -----> When I try driverlib, I can't get CCS to find it in my computer's file system; likely a path problem; despite trying, I've been unable to solve it --- any ideas, folks? Here's Frank's simple 'blink' which I tried today and the CCS error output...... (I underlined the offending line. **** Build of configuration Debug for project test-5229-drvlib-1 **** "C:\\ti\\ccsv6\\utils\\bin\\gmake" -k all 'Building file: ../main.c' 'Invoking: MSP430 Compiler' "C:/ti/ccsv6/tools/compiler/msp430_15.12.3.LTS/bin/cl430" -vmspx --data_model=restricted --use_hw_mpy=F5 --include_path="C:/ti/ccsv6/ccs_base/msp430/include" --include_path="C:/ti/ccsv6/tools/compiler/msp430_15.12.3.LTS/include" --advice:power=all -g --define=__MSP430F5529__ --diag_warning=225 --diag_wrap=off --display_error_number --silicon_errata=CPU21 --silicon_errata=CPU22 --silicon_errata=CPU23 --silicon_errata=CPU40 --printf_support=minimal --preproc_with_compile --preproc_dependency="main.d" "../main.c" >> Compilation failure subdir_rules.mk:7: recipe for target 'main.obj' failed "../main.c", line 2: fatal error #1965: cannot open source file "driverlib.h" 1 catastrophic error detected in the compilation of "../main.c". Compilation terminated. gmake: *** [main.obj] Error 1 gmake: Target 'all' not remade because of errors. **** Build Finished **** and the code... #include <msp430.h> #include "driverlib.h" #define DELAY_CYCLES 1045000 /* * main.c */ int main(void) { WDT_A_hold(WDT_A_BASE); GPIO_setAsOutputPin(RED_LED); for(; { GPIO_setOutputHighOnPin(GPIO_PORT_P1,GPIO_PIN0); _delay_cycles(DELAY_CYCLES); GPIO_setOutputLowOnPin(GPIO_PORT_P1,GPIO_PIN0); _delay_cycles(DELAY_CYCLES); } } WDTCTL = WDTPW | WDTHOLD; // Stop watchdog timer return 0; }
  24. veryalive

    UART - Sending 3 bytes per start/stop bit sets.

    You're clearly deep into this, so I don't know if this fits..... What about programming an MSP to do that protocol in real time, then have it communicate up to the Linux box as required? As I've never heard of that 16/24 bit scheme you mentioned, I'd be absolutely no use progressing this idea further! Cheers,
  25. veryalive

    I2C Device at any address LM4F120

    hi - although I'm a bit late to this thread... Regarding +5 volt operation on the LM4F120 I/O pins... Specifically the LM4F on the 'old' Stellaris Launchpad..... I have followed the data sheet explicitly where it states that certain of the I/O pins are 5volt tolerant on input. I have not damaged anything by reading 5volt input signals to the chip. I cannot measure anything to confirm it is true, however; I just trusted the data sheet. The data sheet I'm using is : DS-LM4F120H5QR-13200.2535 SPMS294G, starting in Chapter 10. And, in section 10.1 : All GPIO signals are 5-V tolerant when configured as inputs except for PD4, PD5, PB0 and PB1, which are limited to 3.6 V I'd be very curious if someone else has successfully used this for I2C which uses pull-up resistors (+-3 K ohms) to a +5volt bus. Cheers..