bluehash 1,581 Posted September 11, 2014 Author Share Posted September 11, 2014 Addresses sent out. Please update this page when you receive your kits! Quote Link to post Share on other sites
abecedarian 330 Posted September 12, 2014 Share Posted September 12, 2014 (edited) Just received the MSP-FET; no sign of the EVM yet. I'll update this post when it arrives. Edit Sept. 15, 2014: MSP430 board arrived, and carries with it "Rev C" chips so my concerns below were unfounded. Edited September 15, 2014 by abecedarian Quote Link to post Share on other sites
Fred 453 Posted September 12, 2014 Share Posted September 12, 2014 That was quick! I suspect mine may spend a little while getting to the UK. I hope it doesn't get stuck in customs whilst they demand taxes, handling fees, etc. I've been enjoying reading up on the ESI. It seems quite difficult to start with and I was beginning to wonder if it was actually more complicated than one of the smaller MSP430s. The reference designs actually make things clearer than the datasheet. Well worth looking at. Quote Link to post Share on other sites
abecedarian 330 Posted September 12, 2014 Share Posted September 12, 2014 (edited) I hope http://processors.wiki.ti.com/index.php/MSP_Debug_Stack?keyMatch=msp-fet&tisearch=Search-EN#Releases isn't going to be a problem.... MSP Debug Stack release 3.4.2.7, Sept. 3, 2014: Early MSP430FR6989 family silicon (older than revision C) is no longer supported I'm using the latest CCS6 so this DLL is installed, so if the chips are older revisions, I'll need to grab an older CCS release. *edit- anticipating needing 3 'stations', I requested samples, just received, and did receive "C" revision, so at least one will work. Now, to generate the part so I can do the schematics. *edit 2- concerns were unfounded. Kit arrived with REV C chips. Edited September 15, 2014 by abecedarian Quote Link to post Share on other sites
greeeg 460 Posted September 15, 2014 Share Posted September 15, 2014 Was sitting at home all afternoon, went to check the mail and found that fedex had tried to deliver, but I missed them. I'm reminded of this They're re-delivering tomorrow, so hopefully I'll catch them then. If it's like others this is likely only the MSP-FET. tripwire and rampadc 2 Quote Link to post Share on other sites
abecedarian 330 Posted September 15, 2014 Share Posted September 15, 2014 In case anyone is looking for it, an Eagle part for the MSP430FR6989 has been posted by Dennis over on the E2E forums: http://e2e.ti.com/support/microcontrollers/msp430/f/166/p/368772/1297017.aspx#1297017 bluehash 1 Quote Link to post Share on other sites
Automate 69 Posted September 16, 2014 Share Posted September 16, 2014 Got my MSP-FET today. Thanks TI. Anybody know if the MSP-TS430PZ100 will come with a MSP430FR6989 or do we need to order a samples? Quote Link to post Share on other sites
abecedarian 330 Posted September 16, 2014 Share Posted September 16, 2014 (edited) Got my MSP-FET today. Thanks TI. Anybody know if the [/size]MSP-TS430PZ100 will come with a MSP430FR6989 or do we need to order a samples?@@Automate - I received one earlier today and the PZ100D comes with 2 FR6989, and a 32.768KHz crystal, as well as four 1x25 pin male and four 1x25 female headers. The chips were Rev C so there should be no issues with the latest MSP-FET interface / MSP Debug firmware. The kit has a YAMAICHI socket for 100LQFP, has through-hole vias for a reset switch and a user-function switch, the latter connected to P1.3 and requiring a 47K 0805 resistor be placed, and pads for LED's that would connect to P1.1 and P1.2 through unpopulated 330R 0805 resistors. The crystal pads, yes there are two, do not have capacitors or resistors in place- those pads are 0805, and the crystal supplied is the same as what comes with the G2 LaunchPad. Under CCS6, when the debug interface was set up, it did prompt me to update the firmware on the MSP-FET, so I would expect that to happen with anyone using the latest CCS release. slau278s, pages 123-125, has the schematic and BOM for the board. *edit to add, in case my rambling wasn't 'clear', the LEDs, crystals, switches, resistors and capacitors I mentioned above are not populated, and only the crystal, two FR6989 chips and male/female headers come with it. The MSP-FET comes with a USB cable and JTAG cable. Both come with the standard disclaimers regarding use in controlled environments and such for various countries, and code usage / license information. TI compiler with CCS and IAR code usage limits are not 'relaxed' so one should consider that when developing. The TI reference with optical detector code compiles to under 4KB, including using the LCD interface peripheral so there is some room to wiggle. Edited September 16, 2014 by abecedarian Automate 1 Quote Link to post Share on other sites
greeeg 460 Posted September 16, 2014 Share Posted September 16, 2014 It makes sense they're not populated as its for developing your application. And shouldn't assume that's the pins you'll use for buttons/LEDs. You could start using msp430-elf gcc. Assuming its bug free now that it's out of beta. It would let you use all of the available FRAM goodness!! Its a seamless install from CCS6. Quote Link to post Share on other sites
abecedarian 330 Posted September 16, 2014 Share Posted September 16, 2014 It makes sense most of the components are not populated as its for developing your application. And shouldn't assume that's the pins you'll use for buttons/LEDs. You could start using msp430-elf gcc. Assuming its bug free now that it's out of beta. It would let you use all of the available FRAM goodness!! Its a seamless install from CCS6. I wouldn't necessarily say it's bug free. @@pabigot and @@Rickta59 have already found either bugs, or bug-fixes, that have not been applied to the latest release. Still, I find my use case likely not bumping the code limit. And, I agree with the rationale behind not populating most of those ancillaries. But, it is safe to assume that the crystals aren't going to use different pins, just that they might not be used. Being that they are somewhat dependent on the capacitance in their traces and such, similarly it makes sense to not include them on the board by default. But designing for, and then omitting the RESET button? Quote Link to post Share on other sites
Rickta59 589 Posted September 16, 2014 Share Posted September 16, 2014 For the record, they have fixed the issues I had. Except for the one about long symbol names and that one is only likely to affect the less than .001% of people using really long c++ template names and coding for the msp430. Oh and that person fixed his version by recompiling from source. greeeg and abecedarian 2 Quote Link to post Share on other sites
greeeg 460 Posted September 16, 2014 Share Posted September 16, 2014 Looks like I've received mine out of order from everyone else. Just got my TS430PZ100D kit, but the MSP-FET must still be finding its way down here. Edit: I have life. A reminder to everyone else. That the LOCKLPM5 bit in PM5CTL (I needed PM5CTL0) needs to be cleared to release pins from high-Z state. I was stuck scratching my head, since it's been awhile since working with FRAM MSP's chicken and tripwire 2 Quote Link to post Share on other sites
Fred 453 Posted September 16, 2014 Share Posted September 16, 2014 Same as @@greeeg - the TS430PZ100D arrived here in the UK. I was glad to see that it came via the Netherlands as was listed as an engineering sample (which I suppose it is) so there was no hassle with customs. I might have got caught by the LOCKLPM5 issue but I decided to test it out with the blinky code that CCS can create for you which includes clearing this. Quote Link to post Share on other sites
pabigot 355 Posted September 16, 2014 Share Posted September 16, 2014 I wouldn't necessarily say it's bug free. @@pabigot and @@Rickta59 have already found either bugs, or bug-fixes, that have not been applied to the latest release. There are still plenty of infelicities, if not bugs, but for the record I intend to use msp430-elf for all my own future development. I do, however, build my own from upstream gcc to which RedHat doesn't always promptly push their updates (e.g. the large memory support in the current TI release hasn't been upstreamed yet). I also have a local git archive that tracks all the TI public releases (source and headers), which I'll put on github next time I'm working MSP430. Makes it easier to figure out what changed with each release (and what's not yet pushed upstream). greeeg, timotet, abecedarian and 1 other 4 Quote Link to post Share on other sites
Automate 69 Posted September 19, 2014 Share Posted September 19, 2014 Got my target board today so need to get in gear and start my project log this weekend. abecedarian 1 Quote Link to post Share on other sites
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.