Jump to content
43oh

paulpthcom

Members
  • Content Count

    71
  • Joined

  • Last visited

  • Days Won

    1

Reputation Activity

  1. Like
    paulpthcom got a reaction from gsutton in programming a MSP430G2955?   
    The source of mspdebug has been updated with support for the 2955 in case anyone else wants to give that a try.
     
    http://sourceforge.net/p/mspdebug/code/ci/a0499ab6f067e60d387fbd31952c7cc36cbd9027/tree/
  2. Like
    paulpthcom got a reaction from Rickta59 in programming a MSP430G2955?   
    The source of mspdebug has been updated with support for the 2955 in case anyone else wants to give that a try.
     
    http://sourceforge.net/p/mspdebug/code/ci/a0499ab6f067e60d387fbd31952c7cc36cbd9027/tree/
  3. Like
    paulpthcom got a reaction from JWoodrell in programming a MSP430G2955?   
    I didn't see that link, will give it a try.
     
    I didn't see that option in the man page, but I did go look over at the code a few minutes ago and looks like adding support for the new chips is basically 2 lines per device, mostly copy/paste. I'll probably give that a try as well.
  4. Like
    paulpthcom reacted to yyrkoon in programming a MSP430G2955?   
    header files pabigot linked to a while back are not working ? Sorry no chips to toy with here, but it seemed to me that most, if not everything needed for mspgcc was included from the sourceforge link he gave.
     
    As for mspdebug, it has an "unsupported" MCU feature built into it, 
  5. Like
    paulpthcom got a reaction from JWoodrell in programming a MSP430G2955?   
    I used the launchpad as a SBW programmer, connected to a breadboard with the 2955 in a SSOP->DIP adapter and the minimum circuit required (caps on VCC/AVCC, pull up resistor and pull down cap on RST). Toolchain all hosted on a Mac, mspgcc and mspdebug, neither of which currently support the 2955. I told the compiler and mspdebug it was a msp430f2274 (not a msp430g2744, which is also not supported).
     
    Pretty sure adding support for at least mspdebug and the new chips should be pretty easy, gcc would probably just involve a new header.
     
    Feel free to ask any questions.
     
    BTW unrelated but just noticed it https://www.olimex.com/Products/MSP430/Booster/MSP430-G2744BP/ is that new? Looks like they have the DIP packaged 2744.
  6. Like
    paulpthcom got a reaction from bluehash in programming a MSP430G2955?   
    I used the launchpad as a SBW programmer, connected to a breadboard with the 2955 in a SSOP->DIP adapter and the minimum circuit required (caps on VCC/AVCC, pull up resistor and pull down cap on RST). Toolchain all hosted on a Mac, mspgcc and mspdebug, neither of which currently support the 2955. I told the compiler and mspdebug it was a msp430f2274 (not a msp430g2744, which is also not supported).
     
    Pretty sure adding support for at least mspdebug and the new chips should be pretty easy, gcc would probably just involve a new header.
     
    Feel free to ask any questions.
     
    BTW unrelated but just noticed it https://www.olimex.com/Products/MSP430/Booster/MSP430-G2744BP/ is that new? Looks like they have the DIP packaged 2744.
  7. Like
    paulpthcom got a reaction from bluehash in programming a MSP430G2955?   
    I was able to get the 2955 working with the standard SBW with no unexpected problems. I used a standard blinking LED program, compiled it for the 2274 with mspgcc and loaded it from the launchpad via mspdebug after I forced it to think the chip was a 2274. Other than the tools not supporting the 2995 it was just removing the 2274 from the breadboard and adding in the 2995 instead.
     
    Don't really have any suggestions, but figured it'd be good to know that it actually did work for someone else.
  8. Like
    paulpthcom reacted to pabigot in New (soon to be) valueline chip. MSP430G2955 56kb Flash 4kb Ram!   
    There is no MSP430F2744. There's an MSP430F2274, which is identical to the MSP430G2744 in terms of memory and peripherals except it has on-board opamps. The internal architecture of the value-line series would change power profiles, chip errata, and possibly the accuracy of calibration constants.
    llc[12]$ egrep 'Name|2..4' /msp430/msp430mcu/upstream/devices.csv # Device Name,CPU_TYPE,CPU_Bugs,MPY_TYPE,SBW,EEM,BREAKPOINTS,CLOCKCONTROL,CYCLECOUNTER,STACKSIZE,RAMStart,RAMEnd,RAMStart2,RAMEnd2,USBRAMStart,USBRAMEnd,MirrowedRAMSource,MirrowedRAMStart,MirrowRAMEnd,BSLStart,BSLSize,BSLEnd,INFOStart,INFOSize,INFOEnd,INFOA,INFOB,INFOC,INFOD,FStart,FEnd,FStart2,FEnd2,Signature_Start,Signature_Size,INTStart,INTEnd
    msp430f2234,0,0,0,1,EMEX_LOW,2,STANDARD,0,80,0200,03FF,0,0,0,0,0,0,0,0,0,0,1000,40,10FF,10C0,1080,1040,1000,E000,FFDD,0,0,,,FFE0,FFFF
    msp430f2254,0,0,0,1,EMEX_LOW,2,STANDARD,0,80,0200,03FF,0,0,0,0,0,0,0,0,0,0,1000,40,10FF,10C0,1080,1040,1000,C000,FFDD,0,0,,,FFE0,FFFF
    msp430f2274,0,0,0,1,EMEX_LOW,2,STANDARD,0,80,0200,05FF,0,0,0,0,0,0,0,0,0,0,1000,40,10FF,10C0,1080,1040,1000,8000,FFDD,0,0,,,FFE0,FFFF
    msp430g2444,0,0,0,1,EMEX_LOW,2,STANDARD,0,80,0200,03FF,0,0,0,0,0,0,0,0,0,0,1000,40,10FF,10C0,1080,1040,1000,E000,FFDD,0,0,,,FFE0,FFFF
    msp430g2544,0,0,0,1,EMEX_LOW,2,STANDARD,0,80,0200,03FF,0,0,0,0,0,0,0,0,0,0,1000,40,10FF,10C0,1080,1040,1000,C000,FFDD,0,0,,,FFE0,FFFF
    msp430g2744,0,0,0,1,EMEX_LOW,2,STANDARD,0,80,0200,05FF,0,0,0,0,0,0,0,0,0,0,1000,40,10FF,10C0,1080,1040,1000,8000,FFDD,0,0,,,FFE0,FFFF
    llc[13]$ diff -u /msp430/msp430mcu/analysis/peripherals/msp430{g274,f227}4.periph
    --- /msp430/msp430mcu/analysis/peripherals/msp430g2744.periph 2013-03-25 13:32:48.522471649 -0500
    +++ /msp430/msp430mcu/analysis/peripherals/msp430f2274.periph 2013-03-25 13:32:47.541478264 -0500
    ADC10
    BC2
    FLASH2
    +OA_2
    PORT1_R
    PORT2_R
    PORT3_R

  9. Like
    paulpthcom got a reaction from roadrunner84 in New (soon to be) valueline chip. MSP430G2955 56kb Flash 4kb Ram!   
    Is there any difference between the MSP430G2744 and MSP430F2744? The details look pretty much identical except that the G part has a higher current listed in Standby mode for some reason.
  10. Like
    paulpthcom got a reaction from kerplatz in GPIO pin sharing   
    I'm a bit at a loss as to what the 5V shutdown exactly is, but you already have SPI, why not just hang a SPI shift register off of that? 
×
×
  • Create New...