fluffy 3 Posted June 24, 2011 Share Posted June 24, 2011 Couldn't find anything in a quick Google, nor in a search of this board. Anyone know if/when the new FRAM 430 parts, such as the one on the MSP-EXP430FR5739 dev board will be supported by mspgcc under Linux? Thanks. Quote Link to post Share on other sites
zeke 693 Posted June 24, 2011 Share Posted June 24, 2011 I don't know if they hang out here or not. It's probably best to contact the mspgcc crew directly at their website. Also, the TI.com/fram site says that there are no stock on the FR5739 yet. And, in the MSP-EXP430FR5739 box contains a waiver form that declares the FR5739 an Experimental Product. That means that they won't let anyone have production quantities of the device without signing this waiver. It's not completely characterized and tested yet. So, I think that the mspgcc crew are probably going to have to buy one of these FRAM boards and do the work. Quote Link to post Share on other sites
hvontres 22 Posted June 25, 2011 Share Posted June 25, 2011 Couldn't find anything in a quick Google, nor in a search of this board. Anyone know if/when the new FRAM 430 parts, such as the one on the MSP-EXP430FR5739 dev board will be supported by mspgcc under Linux? Thanks. It looks like the uniarch version of mspgcc has headder files for it. Unfortunately, mspdebug doesn't support it yet and I have not had a chance to see if I can get it to work. Quote Link to post Share on other sites
penguinator 0 Posted June 25, 2011 Share Posted June 25, 2011 I've got one of the MSP430FR5739 experimenter boards and have been trying to get mspdebug working on it. (mspgcc seems to work fine for this part, though I haven't tested the result) Currently I can run the program and get possibly correct register outputs, but programming doesn't work yet. Attached are some usb sniffs from code composer studio talking to the chip, if that helps anyone. I also sent this to the guy who wrote mspdebug, and have heard of other people contacting him, so maybe he'll get around to adding this soon. usblog.zip Quote Link to post Share on other sites
zborgerd 62 Posted June 26, 2011 Share Posted June 26, 2011 I have also had luck compiling a simple program with the new header files. I've tried mspdebug with the "--force-fet-id" option. This seems to work but the program memory start address is different than a few of the chips I've tried. I've tried to look at the datasheet but I'm getting errors on the TI site. Not sure if it's just temporarily down or something else. I managed to burn up the demo program by trying to write to it, so it appears that I've at least done *something*... Not that I am suggesting that someone else do the same, but it appears that it is at least possible to initialize FET on this board. I'm out of time to hack on it for the night though. Quote Link to post Share on other sites
fluffy 3 Posted June 26, 2011 Author Share Posted June 26, 2011 Thanks to all who have posted info or are working on this. I really appreciate the information. Quote Link to post Share on other sites
penguinator 0 Posted June 27, 2011 Share Posted June 27, 2011 zborgerd, I got the same results. It blows away the code on there when trying to erase. I wonder if maybe it's erasing correctly, but mspdebug doesn't handle the response from the fet properly. Daniel Beer, the maintainer of mspdebug sent me a patch to test, but it didn't really seem to make any difference over using the --force-fet-id option. I guess well see what he comes up with next. Quote Link to post Share on other sites
zborgerd 62 Posted June 27, 2011 Share Posted June 27, 2011 zborgerd, I got the same results. It blows away the code on there when trying to erase. I wonder if maybe it's erasing correctly, but mspdebug doesn't handle the response from the fet properly. Daniel Beer, the maintainer of mspdebug sent me a patch to test, but it didn't really seem to make any difference over using the --force-fet-id option. I guess well see what he comes up with next. It seems to be erasing at least part of the old program. I wanted to dig back into it today but didn't get a chance. I'm hoping to be able to try it out this weekend. I'd love to get my hands on the patch. Is it just a modification to fet_db.c? Does the debugger fire up and ID it correctly (in spite of the write failure)? Quote Link to post Share on other sites
djhuft 0 Posted July 4, 2011 Share Posted July 4, 2011 Very good guys. I've got the FRAM dev board too and was just fiddling around trying to get gcc to work. Any updates are greatly appreciated. By the way, I assume you are using the June 12, 2011 (20110612) version of the compiler, right? Quote Link to post Share on other sites
penguinator 0 Posted July 9, 2011 Share Posted July 9, 2011 The mspdebug git repo has been updated with code that seems to mostly support the fr5739 boards. The 'load' command definitely works, which is very useful. Quote Link to post Share on other sites
Fe2o3Fish 33 Posted July 17, 2011 Share Posted July 17, 2011 Took some time off from my networking toys to pull my Framinator or Fraunchpad out of its box. I got the the latest MSPGCC and MSPDEBUG compiled and woiking on my Linux laptop. I are one happy camper! vim+make+compiler and I be happy!!! A big Texas THANK YOU for those involved! 'preciate it! -Rusty- Quote Link to post Share on other sites
djhuft 0 Posted July 20, 2011 Share Posted July 20, 2011 Great! It looks like I was just a couple of days ahead of this. Daniel Beer updated the mspdebug repo with support for the 5739 shortly after I posted. Anyway, I can't wait to get this thing up and running. I guess its worth noting for those like me who are new to the 430 line and its GCC toolchain, the best place to get mspdebug is probably Beer's page. I spent quite a bit of time fiddling around with outdated versions before I went straight to the source. Quote Link to post Share on other sites
amstan 18 Posted July 30, 2011 Share Posted July 30, 2011 There was a bug in the new version of mspdebug on ubuntu where the cdc-acm driver would interfiere. This was fixed in the latest git(a5def5cf92c96b286024a72cdf24c814530373ac). So i got to program the board, but it doesn't seem to work. I tried turning on the leds from P3. Anyone know what's wrong with this code? Quote Link to post Share on other sites
oPossum 1,083 Posted July 30, 2011 Share Posted July 30, 2011 P3DIR = 0xF0; P3OUT = 0xF0; jsolarski 1 Quote Link to post Share on other sites
amstan 18 Posted July 30, 2011 Share Posted July 30, 2011 P3DIR = 0xF0; P3OUT = 0xF0; NOO! Why do i always get owned by 1 char bugs? 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.