veryalive

Members
  • Content count

    131
  • Joined

  • Last visited

  • Days Won

    4

veryalive last won the day on September 7 2016

veryalive had the most liked content!

1 Follower

About veryalive

  • Rank
    Level 1

Profile Information

  • Gender
    Not Telling
  1. 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
  2. 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....
  3. 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,
  4. 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.
  5. 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.
  6. 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!
  7. 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 !!
  8. would those have been rev 1.4 -or- rev 1.5 ? just curious as I have both. Thanks
  9. The Dan Saks video is brilliant! Thank you for posting.
  10. Very nice to see some new, practical projects on the forum ! Its great to learn from these.
  11. 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
  12. 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,
  13. Not knowing your level of experience, I'll offer this C - for - embedded course on youtube...
  14. Thanks folks, I'll give that a try. cheers...
  15. 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; }