Jump to content
43oh

KatiePier

Members
  • Content Count

    42
  • Joined

  • Last visited

  • Days Won

    3

Reputation Activity

  1. Like
    KatiePier got a reaction from pine in New MSP430 FRAM - FR41xx/FR2xxx   
    Yeah unfortunately this is because of different pinouts as you alluded to. There is a board that supports FR4xx - but it is a new one: http://www.ti.com/tool/msp-ts430pm64d.
     
     
     
    If you want to learn more about the IR module there's also an app note about it: http://www.ti.com/lit/pdf/slaa644 Really fun if you want to make your own remote control :-)
     
     
     
    Right - currently this device is just sampling engineering samples so people can start designing with it now to be able to go to production at release. Production orders can only be placed later at full release and those parts will be the final release revision and be MSP430FR4133 not XMS430FR4133. If you look at the product page this is why it says "Preview" next to the part number at the top. It will change to "Active" at full production silicon release. http://forum.43oh.com/topic/5609-ti-msp430-wolverine-now-in-production/?p=48972
     
     
    You can find FR2033 device here: http://www.ti.com/product/msp430fr2033 Pretty similar but no LCD.
     
    Finally, if you want to know more about the differences on this part, there are some migration guides posted too:
    http://www.ti.com/lit/pdf/slaa649 (F2xx/G2xx to FR2xx)
    http://www.ti.com/lit/pdf/slaa648 (F4xx to FR4xx)
  2. Like
    KatiePier got a reaction from RobG in New MSP430 FRAM - FR41xx/FR2xxx   
    Yeah unfortunately this is because of different pinouts as you alluded to. There is a board that supports FR4xx - but it is a new one: http://www.ti.com/tool/msp-ts430pm64d.
     
     
     
    If you want to learn more about the IR module there's also an app note about it: http://www.ti.com/lit/pdf/slaa644 Really fun if you want to make your own remote control :-)
     
     
     
    Right - currently this device is just sampling engineering samples so people can start designing with it now to be able to go to production at release. Production orders can only be placed later at full release and those parts will be the final release revision and be MSP430FR4133 not XMS430FR4133. If you look at the product page this is why it says "Preview" next to the part number at the top. It will change to "Active" at full production silicon release. http://forum.43oh.com/topic/5609-ti-msp430-wolverine-now-in-production/?p=48972
     
     
    You can find FR2033 device here: http://www.ti.com/product/msp430fr2033 Pretty similar but no LCD.
     
    Finally, if you want to know more about the differences on this part, there are some migration guides posted too:
    http://www.ti.com/lit/pdf/slaa649 (F2xx/G2xx to FR2xx)
    http://www.ti.com/lit/pdf/slaa648 (F4xx to FR4xx)
  3. Like
    KatiePier got a reaction from greeeg in New MSP430 FRAM - FR41xx/FR2xxx   
    Yeah unfortunately this is because of different pinouts as you alluded to. There is a board that supports FR4xx - but it is a new one: http://www.ti.com/tool/msp-ts430pm64d.
     
     
     
    If you want to learn more about the IR module there's also an app note about it: http://www.ti.com/lit/pdf/slaa644 Really fun if you want to make your own remote control :-)
     
     
     
    Right - currently this device is just sampling engineering samples so people can start designing with it now to be able to go to production at release. Production orders can only be placed later at full release and those parts will be the final release revision and be MSP430FR4133 not XMS430FR4133. If you look at the product page this is why it says "Preview" next to the part number at the top. It will change to "Active" at full production silicon release. http://forum.43oh.com/topic/5609-ti-msp430-wolverine-now-in-production/?p=48972
     
     
    You can find FR2033 device here: http://www.ti.com/product/msp430fr2033 Pretty similar but no LCD.
     
    Finally, if you want to know more about the differences on this part, there are some migration guides posted too:
    http://www.ti.com/lit/pdf/slaa649 (F2xx/G2xx to FR2xx)
    http://www.ti.com/lit/pdf/slaa648 (F4xx to FR4xx)
  4. Like
    KatiePier reacted to spirilis in MSP430i2x?   
    Saw that. I see it as a modern refresh of the MSP430AFExxx series. 24-bit Sigma Delta ADC designed around a +/-1.0V signal for measuring AC voltage & current for energy metering type of apps... but with the more modern eUSCI peripheral.
     
    Sent from my Galaxy Note II with Tapatalk 4
  5. Like
    KatiePier got a reaction from tripwire in New MSP430 FRAM - FR41xx/FR2xxx   
    Yeah unfortunately this is because of different pinouts as you alluded to. There is a board that supports FR4xx - but it is a new one: http://www.ti.com/tool/msp-ts430pm64d.
     
     
     
    If you want to learn more about the IR module there's also an app note about it: http://www.ti.com/lit/pdf/slaa644 Really fun if you want to make your own remote control :-)
     
     
     
    Right - currently this device is just sampling engineering samples so people can start designing with it now to be able to go to production at release. Production orders can only be placed later at full release and those parts will be the final release revision and be MSP430FR4133 not XMS430FR4133. If you look at the product page this is why it says "Preview" next to the part number at the top. It will change to "Active" at full production silicon release. http://forum.43oh.com/topic/5609-ti-msp430-wolverine-now-in-production/?p=48972
     
     
    You can find FR2033 device here: http://www.ti.com/product/msp430fr2033 Pretty similar but no LCD.
     
    Finally, if you want to know more about the differences on this part, there are some migration guides posted too:
    http://www.ti.com/lit/pdf/slaa649 (F2xx/G2xx to FR2xx)
    http://www.ti.com/lit/pdf/slaa648 (F4xx to FR4xx)
  6. Like
    KatiePier got a reaction from dubnet in New MSP430 FRAM - FR41xx/FR2xxx   
    Yeah unfortunately this is because of different pinouts as you alluded to. There is a board that supports FR4xx - but it is a new one: http://www.ti.com/tool/msp-ts430pm64d.
     
     
     
    If you want to learn more about the IR module there's also an app note about it: http://www.ti.com/lit/pdf/slaa644 Really fun if you want to make your own remote control :-)
     
     
     
    Right - currently this device is just sampling engineering samples so people can start designing with it now to be able to go to production at release. Production orders can only be placed later at full release and those parts will be the final release revision and be MSP430FR4133 not XMS430FR4133. If you look at the product page this is why it says "Preview" next to the part number at the top. It will change to "Active" at full production silicon release. http://forum.43oh.com/topic/5609-ti-msp430-wolverine-now-in-production/?p=48972
     
     
    You can find FR2033 device here: http://www.ti.com/product/msp430fr2033 Pretty similar but no LCD.
     
    Finally, if you want to know more about the differences on this part, there are some migration guides posted too:
    http://www.ti.com/lit/pdf/slaa649 (F2xx/G2xx to FR2xx)
    http://www.ti.com/lit/pdf/slaa648 (F4xx to FR4xx)
  7. Like
    KatiePier got a reaction from Fred in New MSP430 FRAM - FR41xx/FR2xxx   
    Yeah unfortunately this is because of different pinouts as you alluded to. There is a board that supports FR4xx - but it is a new one: http://www.ti.com/tool/msp-ts430pm64d.
     
     
     
    If you want to learn more about the IR module there's also an app note about it: http://www.ti.com/lit/pdf/slaa644 Really fun if you want to make your own remote control :-)
     
     
     
    Right - currently this device is just sampling engineering samples so people can start designing with it now to be able to go to production at release. Production orders can only be placed later at full release and those parts will be the final release revision and be MSP430FR4133 not XMS430FR4133. If you look at the product page this is why it says "Preview" next to the part number at the top. It will change to "Active" at full production silicon release. http://forum.43oh.com/topic/5609-ti-msp430-wolverine-now-in-production/?p=48972
     
     
    You can find FR2033 device here: http://www.ti.com/product/msp430fr2033 Pretty similar but no LCD.
     
    Finally, if you want to know more about the differences on this part, there are some migration guides posted too:
    http://www.ti.com/lit/pdf/slaa649 (F2xx/G2xx to FR2xx)
    http://www.ti.com/lit/pdf/slaa648 (F4xx to FR4xx)
  8. Like
    KatiePier reacted to greeeg in New MSP430 FRAM - FR41xx/FR2xxx   
    Bought. I quite like using the builtin LCD module of the MSP, however sourcing nice raw crystal displays is pretty difficult for hobbyists.
     
    I've ordered one. I'll be sure to put it to use somewhere.
  9. Like
    KatiePier reacted to Fred in Program MSP430 from memory card   
    It looks like the MSP Gang Programmer should do what you need. Might be a bit over the top though.
    http://www.ti.com/tool/msp-gang
  10. Like
    KatiePier got a reaction from mrinverter in FR5969 UART Bluetooth   
    Hi @@mrinverter,
     
    There are a few things that jump out at me:
     
    1. Your GPIO setting looks incorrect to me. You are using P2.5 + P2.6 for UCA1TXD/RXD. However, looking at the FR5969 datasheet http://www.ti.com/lit/gpn/msp430fr5969 on p. 88 table 6-52 I see this for the pin setup:
     

     
    You need to have P2SEL1 bit 5 and 6 set to 1, and P2SEL0 bit 5 and 6 set to 0. Right now, it looks like your code does the opposite:
    P2SEL0 |= RXD + TXD;    //Setup the I/O
    //P2SEL1 |= RXD + TXD;
    So switch which line is commented out.
     
    2. You are now using FR5969. This device has an eUSCI module (enhanced USCI) rather than USCI that was present on G2553. There are a few differences (for more detail please see the USCI to eUSCI migration guide http://www.ti.com/lit/pdf/slaa522).
     
    One thing is the interrupt vector is different on eUSCI so this needs to be changed. It should be the USCI_A1_VECTOR, and you should also modify the ISR to have a switch statement to handle and respond to the correct values for UCA1IV because this is different. You may want to look at some FR5969 code examples for a demonstration of this.
     
    Another thing is the baud rate generation. The eUSCI module provides a few more bits to get you better granularity and accuracy for generating baud rates - please check the FR5xx/6xx user's guide http://www.ti.com/lit/pdf/slau367 Table 21-5 for a list of recommended settings to generate different baud rates, and note the slight difference - you should change your code to match this (notably UCBSx = 0x49).
     
    There may be other things to change, but hopefully these tips will help!
    Regards,
    Katie
  11. Like
    KatiePier got a reaction from Fred in FR5969 UART Bluetooth   
    Hi @@mrinverter,
     
    There are a few things that jump out at me:
     
    1. Your GPIO setting looks incorrect to me. You are using P2.5 + P2.6 for UCA1TXD/RXD. However, looking at the FR5969 datasheet http://www.ti.com/lit/gpn/msp430fr5969 on p. 88 table 6-52 I see this for the pin setup:
     

     
    You need to have P2SEL1 bit 5 and 6 set to 1, and P2SEL0 bit 5 and 6 set to 0. Right now, it looks like your code does the opposite:
    P2SEL0 |= RXD + TXD;    //Setup the I/O
    //P2SEL1 |= RXD + TXD;
    So switch which line is commented out.
     
    2. You are now using FR5969. This device has an eUSCI module (enhanced USCI) rather than USCI that was present on G2553. There are a few differences (for more detail please see the USCI to eUSCI migration guide http://www.ti.com/lit/pdf/slaa522).
     
    One thing is the interrupt vector is different on eUSCI so this needs to be changed. It should be the USCI_A1_VECTOR, and you should also modify the ISR to have a switch statement to handle and respond to the correct values for UCA1IV because this is different. You may want to look at some FR5969 code examples for a demonstration of this.
     
    Another thing is the baud rate generation. The eUSCI module provides a few more bits to get you better granularity and accuracy for generating baud rates - please check the FR5xx/6xx user's guide http://www.ti.com/lit/pdf/slau367 Table 21-5 for a list of recommended settings to generate different baud rates, and note the slight difference - you should change your code to match this (notably UCBSx = 0x49).
     
    There may be other things to change, but hopefully these tips will help!
    Regards,
    Katie
  12. Like
    KatiePier got a reaction from alchy75 in Programming/debugging MSP430(G2553) while not common ground   
    As a note, if you have the MSP-FET it will follow the voltage you are providing from the external supply if you connect the pins correctly (it has a pin for inputting to it an external voltage instead of having it provide a voltage to your board). It's not really good to have the debugger and supply at different levels and the communication may not be reliable.
     
     
    ^^This is correct - SBWTDIO is the bidirectional one. There's way more details in www.ti.com/lit/pdf/slau320 - section 1.2.1.3 calls out SBWTDIO as being bi-directional vs SBWTCK which is controlled by the tool. Something you'll want to be careful with if you use isolators or something on these lines is the speed - I've seen people try to do this and had it not work before because their isolators screwed up the timing of the SBW too much. You probably want something that will be pretty responsive and not add much delay.
     
    One other one I'll throw out there: there is also an isolated JTAG tool out there if you ever really need that (probably overkill for this though, but I know smartgrid guys that use this): https://www.olimex.com/Products/MSP430/JTAG/MSP430-JTAG-ISO-MK2/
  13. Like
    KatiePier got a reaction from thomassss in BSL   
    @@thomassss
    The BSL password is simply the 32-bytes from 0xFFE0 through 0xFFFF (see www.ti.com/lit/pdf/slau319 section 2.4.4.3). Note that this area also contains the interrupt vector table. So if you look at the binary image that your code generates, you'll probably see that at least some of these bytes are already filled in, so by default there is already some of a password (just maybe not a very strong one - most of it might be FFs). You should be able to modify addresses that are not used for pointing to interrupt vectors if you like to have a different password. Safest way to do this would probably just be to make dummy ISRs for each of your unused interrupt vectors and the placement of these is going to fill in the addresses in the vector table and therefore change your password. If you really wanted to get particular about what your password is you could explicitly place the vectors at particular addresses instead of having the linker choose where they go, but that starts to get trickier - just having these will at least give you a longer password even if the linker chooses where to put them.
     
    And these addresses can simply be programmed in using JTAG or SBW - indeed, if you have any interrupts in your program (and the reset vector will get filled anyway), then your JTAG/SBW is already programming this area (0xFFE0-FFFF) with something and therefore there is already some password on your BSL. If you are generating a TI-txt or hex file that you're programming in using MSP430Flasher or Elprotronic software or something, then as long as these addresses have something in them in the file then your BSL password is already getting set to something.
     
    Regards,
    Katie
  14. Like
    KatiePier reacted to zeke in External power supply on MSP430F5529-LP boosterpack connector?   
    I have the same version of LP board as you (V1.4).
     
    You have to pull the SBWRST and SBWTST jumpers as well or else it will not work because the MSP will be held in reset by the unpowered eZ-FET lite circuitry.
     
    Just pull out all of those jumpers then apply 3V to the board at either at J10:3(3V3) or at J1:1(3V3).
     
    Here is the LP schematic for reference. It's V1.5 but it will work for this conversation.
    MSP-EXP430F5529LP_Schematic.pdf
  15. Like
    KatiePier reacted to Fred in Scan Interface Applications - Five Members Win A Target Board And An MSP-FET   
    MSP-FET arrived here in the UK. TI are bloody awesome, aren't they? 
  16. Like
    KatiePier reacted to Fred in Scan Interface Applications - Five Members Win A Target Board And An MSP-FET   
    The EnergyTrace stuff is the thing that's impressed me the most so far. (Enable the EnergyTrace++ option in CCS if you haven't already.) More so than the ESI if I'm honest.
  17. Like
    KatiePier reacted to rockets4kids in Making commercial electronics, self-financed - steps?   
    The first thing you are going to need to qualify is whether you are intenting to sell a component or a finished product.  If you are selling a component you (generally) do not need to worry about FCC approval.  If you are selling a product, you do.  This makes a world of difference in your overall costs.
  18. Like
    KatiePier reacted to greeeg in Programming the MSP430FR5969   
    The MSP430G launchpads have a horrible old FET interface. It only officially supports the G series (but some older ones not even that).
     
    The F5529LP and the FR5969LP feature a newer much more advanced FET which supports being updated by the PC to support new ICs.
     
    One thing to note is that because your target is an FR chip it cant and doesn't require being erased before programming. Can you successfully program your target with the 5969LP?
  19. Like
    KatiePier got a reaction from bluehash in Updating Software using MSP430 USB BSL   
    For others reference, looks like the same question is here: http://e2e.ti.com/support/microcontrollers/msp430/f/166/t/364546.aspx
     
    @@paddukoti could you share how you found to fix your problem in case other people run into the same issue later?
     
    -Katie
  20. Like
    KatiePier got a reaction from zborgerd in Could not communicate with FET error = 35   
    My vote goes for the firmware update being needed - there's some more links here with more details: http://e2e.ti.com/support/microcontrollers/msp430/f/166/p/364413/1281328.aspx#1281328
     
    Some of the Rev 1.4 launchpads will need updates, others won't, depending on how old they are and which firmware they had: http://e2e.ti.com/support/microcontrollers/msp430/f/166/p/97931/364901.aspx
     
    The fact that he was able to program another part (and I'm guessing the other part was the G2231 that came with the older launchpads even though he just said "G223" in this post) that is a G2xx1 device and so would be programmable without an update. This makes me highly suspect it is just needing the firmware update: http://processors.wiki.ti.com/index.php/MSP430_LaunchPad_Firmware_Update
     
    @zborgerd:
     
    The firmware update got implemented when G2xx2 were coming out I believe, but when we did the update we made sure the firmware would support both G2xx2 and G2xx3. So there are 1.4 launchpads that predate G2xx3 that would still have support for it. There are more details in one of the links I put above, from when the firmware update was first being released about which LPs are affected.
     
    -Katie
  21. Like
    KatiePier reacted to ILAMtitan in First actual fried MSP430   
    You got off easy.  I do a lot of work with mains voltage, and learned my lesson about debugging without an isolated interface early on.  THis one blew out my laptop's dock as well in the process.
     

  22. Like
    KatiePier reacted to pine in Bread Board & wishful thinking   
    LED's for each line of connections, lights up when there that bank of line is high voltage, like those on network routers and switches.
  23. Like
    KatiePier reacted to chicken in Bread Board & wishful thinking   
    Integrated logic analyzer and basic scope that let's you look at the row-signals via USB connected PC.
  24. Like
    KatiePier got a reaction from guybarash in PWM input   
    Hi @@guybarash,
     
    The family user's guide is definitely where you want to look for more details about timer operation and the registers and bits that control these functions, just as @@roadrunner84 recommended. However, the SLAU144 document is for the 2xx family of devices - for the F5529, you will want to look at SLAU208 which is the user's guide for the F5xx/6xx family of devices.
     
    For timer A operation this shouldn't really matter as timer A is pretty much the same across families, but there are other modules that differ between the two families (clock system, power management, etc) so this is definitely the better document to look at in your particular case.
     
    Regards,
    Katie
  25. Like
    KatiePier reacted to roadrunner84 in PWM input   
    Oops, sorry. I wasn't paying enough attention I guess. SLAU208 it is then
×
×
  • Create New...