Jump to content

pabigot

Members
  • Content Count

    577
  • Joined

  • Last visited

  • Days Won

    30

Reputation Activity

  1. Like
    pabigot got a reaction from gsutton in programming a MSP430G2955?   
    Thanks, but there's nothing technical in the way of doing this.  I don't have any of the newest chips to use, but I have no reason to believe that they would cause trouble.  It was only the change to the FRAM interrupt vectors that caused a headache that prevents using any of the current compiler releases with an updated msp430-libc, and I already have the required compiler modifications in place and have been using it for my own stuff.
     
    The issue with a release is that it's 20+ hours effort to do the git repository manipulations to pull patches into the right branches, build the system on a couple Linux releases, and run the test suite on a couple different types of boards.  The next release should be an LTS one, probably based on 4.7.2, which requires a little more testing since it's a pain to put out patches.
  2. Like
    pabigot got a reaction from gsutton in programming a MSP430G2955?   
    TI hasn't even acknowledged my proposal that they support my efforts in maintaining mspgcc during the transition to the new RedHat toolchain.  I'd like to provide this support for the community, but a new release is a fair amount of effort and I have to focus my time on things that might eventually produce income or at least are of direct interest to me personally.  At this time I have no plans for another mspgcc release.
  3. Like
    pabigot got a reaction from tripwire in A new MSP430 coming [MSP432 ARM]   
    Silicon Labs (the Energy Micro line) and Nordic (the nRF51 line) are two I have personal experience with. There are "right" ones for Tiva out on github, which I think somebody generated from CMSIS-SVD files using ARM tools, but for some reason TI isn't providing them directly.
     
    It's frustrating because TI appears to be doing more work to generate headers that aren't consistent with what other Cortex-M vendors produce. Maybe they think their approach is better somehow.
  4. Like
    pabigot got a reaction from tripwire in A new MSP430 coming [MSP432 ARM]   
    Unpacking MSP432_Driver_Library it appears there are CMSIS Core standard peripheral structs and defines, which will make it easier for those of us who like to use the hardware directly bizarre union/bitfield structs and defines that make programming an ARM look sorta like programming an MSP430 but not really.  (Teach me to post before fully inspecting what's been given.)
  5. Like
    pabigot got a reaction from spirilis in A new MSP430 coming [MSP432 ARM]   
    Unpacking MSP432_Driver_Library it appears there are CMSIS Core standard peripheral structs and defines, which will make it easier for those of us who like to use the hardware directly bizarre union/bitfield structs and defines that make programming an ARM look sorta like programming an MSP430 but not really.  (Teach me to post before fully inspecting what's been given.)
  6. Like
    pabigot got a reaction from roadrunner84 in Updates and going forward   
    I'm still here, though not doing much with TI chips because I'm now using nRF51 chips (which I'm pretty happy with).  Personally, I concur with @@Fred about putting Energia somewhere else.  It's a fine system with a lot of traction, but programming with Energia is not really relevant to those of us who work on bare metal MCUs, and vice-versa.  Over the past several months I've frequently noticed a topic and though "Looks interesting...oh wait, Energia."  The degree of mixing waters down the value for both communities, in my opinion.
  7. Like
    pabigot got a reaction from oPossum in Updates and going forward   
    I'm still here, though not doing much with TI chips because I'm now using nRF51 chips (which I'm pretty happy with).  Personally, I concur with @@Fred about putting Energia somewhere else.  It's a fine system with a lot of traction, but programming with Energia is not really relevant to those of us who work on bare metal MCUs, and vice-versa.  Over the past several months I've frequently noticed a topic and though "Looks interesting...oh wait, Energia."  The degree of mixing waters down the value for both communities, in my opinion.
  8. Like
    pabigot got a reaction from greeeg in dtostrf() function works in arduino but not Energia   
    That quote appears to come from avr-libc documentation (it may have come from an mspgcc-oriented site, but if so, it was either written more than five years ago or is simply wrong). mspgcc uses a completely different libc, and dtostrf is not in it.
     
    %f formatting is not supported by mspgcc, so unless Energia's transitioned to msp430-elf that won't work either.
     
    Using floating point on the MSP430 will simply cause pain. Get the value using a fixed point calculation, and format it in whatever way you need. "%u.%03u" would work if you split an integral milli-value into v/1000 and v%1000 components.
  9. Like
    pabigot got a reaction from spirilis in dtostrf() function works in arduino but not Energia   
    That quote appears to come from avr-libc documentation (it may have come from an mspgcc-oriented site, but if so, it was either written more than five years ago or is simply wrong). mspgcc uses a completely different libc, and dtostrf is not in it.
     
    %f formatting is not supported by mspgcc, so unless Energia's transitioned to msp430-elf that won't work either.
     
    Using floating point on the MSP430 will simply cause pain. Get the value using a fixed point calculation, and format it in whatever way you need. "%u.%03u" would work if you split an integral milli-value into v/1000 and v%1000 components.
  10. Like
    pabigot got a reaction from mamurtaza in Trouble in compiling ELM Chan FatFs   
    The name of the type provided by <stdbool.h> is bool (lower case). Its constants true and false are also lower-case.
     
    You're apparently using PetitFS rather than FatFS; older versions of that had this in a header integer.h:
     

    /* Boolean type */ typedef enum { FALSE = 0, TRUE } BOOL; That sort of thing was mostly removed from FatFS releases around 0.9, and PetiteFS around 0.02a. My archival repository at https://github.com/pabigot/FatFs/tree/ff/master would be one way to see the changes per version.
  11. Like
    pabigot got a reaction from fairysontk92 in How to calc the clock   
    An anomaly with this: if you're using driverlib TivaWare_C_Series-2.1.0.12573 on a TM4C123GH6PM (i.e. an EK-TM4C123GXL launchpad) you can use

    SysCtlClockSet(SYSCTL_SYSDIV_2_5 | SYSCTL_USE_PLL | SYSCTL_OSC_MAIN | SYSCTL_XTAL_16MHZ); /* 2*PLL/5 = 80 MHz */ to set the clocks to 80MHz, but if you then call SysCtlClockGet() it'll tell you you're running at 66MHz. This is because SYSCTL->DC1.MINSYSDIV, which driverlib consults, insists that the minimum divider is 3, so you can't possibly be running faster than 66MHz. 
    At least TI gives us the source code so we can figure these things out, and per this e2e post with a patch it'll be fixed some day.
  12. Like
    pabigot got a reaction from mamurtaza in Trouble in compiling ELM Chan FatFs   
    The msp430 MCU headers that have USB support define DIR as a preprocessor symbol containing the value for the USB Data Response Bit. A solution is to include ff.h before anything includes msp430.h, or to not include both in the same file at all.
  13. Like
    pabigot got a reaction from RobG in What am I going to do with ...   
    Set them in grout to make a coffee-table top.
  14. Like
    pabigot got a reaction from zeke in What am I going to do with ...   
    Set them in grout to make a coffee-table top.
  15. Like
    pabigot got a reaction from tripwire in What am I going to do with ...   
    Set them in grout to make a coffee-table top.
  16. Like
    pabigot got a reaction from Fred in What am I going to do with ...   
    Set them in grout to make a coffee-table top.
  17. Like
    pabigot got a reaction from spirilis in What am I going to do with ...   
    Set them in grout to make a coffee-table top.
  18. Like
    pabigot got a reaction from StefanWxx in Is this 38KHz PWM ?   
    Well, maybe. One thing: fix the comment to note that TASSEL_2 means you're actually using SMCLK (nominally 1.1 MHz) instead of ACLK (nominally 12 kHz on that MCU with that initialization sequence).
     
    At 1.1MHz I think you'd get 42.3 kHz with 26 ticks per cycle. Since DCO tolerance on the MSP430G2553 is +/- 6% it's probably not very close to 38 kHz.
  19. Like
    pabigot got a reaction from bluehash in New Dev Platform for MSP430FR5969   
    That error comes from the MSPDebug stack. There are three locations in the latest release that error is produced. Since it's open source, I'd download and build that locally, reproduce the problem with mspdebug, then instrument the source code to figure out what conditions cause it to occur. Should be a clue in there somewhere.
  20. Like
    pabigot got a reaction from JuliaJose in Maximum input frequency detectable by MSP430g2553   
    Please clarify: is this a digital or analog signal? [edit: yes you do say "through the analog pins" which I missed on first reading, but if the signal could be treated as digital it becomes a lot simpler]
     
    For a digital signal any MSP430 device could easily satisfy your requirement using an internal clock (ACLK or SMCLK) at a known frequency and the timer capture/compare infrastructure. I couldn't say how to do it in Energia, though.
  21. Like
    pabigot reacted to oPossum in Is this 38KHz PWM ?   
    It's close. Can be made more accurate...
     
    Set the oscillator to one of the calibrated values.

    DCOCTL = 0; BCSCTL1 = CALBC1_1MHZ; DCOCTL = CALDCO_1MHZ; Set the max count to N - 1
    TA0CCR0 = (1000000 / 38000) - 1; TA0CCR1 = TA0CCR0 >> 1;
  22. Like
    pabigot got a reaction from anning865 in How to implement Timer interruption in Energia?   
    The error will almost certainly be on line 107. Recall that TI's headers define single-character macros that inconveniently interfere with variable declarations:

    /************************************************************ * STATUS REGISTER BITS ************************************************************/ #define C (0x0001) #define Z (0x0002) #define N (0x0004) #define V (0x0100) As a general rule, don't use fully capitalized symbols for variable names, and particularly not single-letter ones.
  23. Like
    pabigot got a reaction from greeeg in New BSP430 release available   
    BSP430 has been updated to the 20141115 release, which includes full support for msp430-elf and support for the new FR4xx/2xx chip families. Details are available on the web site.
     
    Of particular interest to 43oh folks might be the updated script to build an msp430-elf toolchain, and the newlib sys integration.
     
    If you use BSP430 and encounter any problems, please file issue reports on github.
     
    This is the last version of BSP430 that will default to mspgcc. Henceforth it's going to be msp430-elf, though mspgcc will still be supported (at about the level that CCS is supported, i.e. not very much). I highly recommend everybody else start transitioning too. The new toolchain has its problems, but it's still the way forward.
  24. Like
    pabigot got a reaction from spirilis in How to implement Timer interruption in Energia?   
    The error will almost certainly be on line 107. Recall that TI's headers define single-character macros that inconveniently interfere with variable declarations:

    /************************************************************ * STATUS REGISTER BITS ************************************************************/ #define C (0x0001) #define Z (0x0002) #define N (0x0004) #define V (0x0100) As a general rule, don't use fully capitalized symbols for variable names, and particularly not single-letter ones.
  25. Like
    pabigot got a reaction from bluehash in New BSP430 release available   
    BSP430 has been updated to the 20141115 release, which includes full support for msp430-elf and support for the new FR4xx/2xx chip families. Details are available on the web site.
     
    Of particular interest to 43oh folks might be the updated script to build an msp430-elf toolchain, and the newlib sys integration.
     
    If you use BSP430 and encounter any problems, please file issue reports on github.
     
    This is the last version of BSP430 that will default to mspgcc. Henceforth it's going to be msp430-elf, though mspgcc will still be supported (at about the level that CCS is supported, i.e. not very much). I highly recommend everybody else start transitioning too. The new toolchain has its problems, but it's still the way forward.
×
×
  • Create New...