Thanks Xavi, I look forward to getting the installation instructions and code.
I have an update for my problem with tdspecs. When I invoke msp430-gcc using the output obtained when I run make with CFLAGS+=-v make telosb, and change specs=/usr/lib/ncc/tdspecs to specs=c:/\cygwin/\usr/\lib/\ncc/\tdspecs, it gets past the error of no such file or directory, but has a whole slurry of new issues beginning with an uknown *.h file. So the original problem appears to be in the presentation of the path format of specs. I am now in the process of finding where tinyos sets specs to try changing it. I also had to add my ncc directory to PATH. Hugh From: Xavier Orduña [mailto:[EMAIL PROTECTED] Sent: Monday, October 20, 2008 4:29 PM To: Hugh Hartwig Cc: Gracinda García Lago; [email protected] Subject: Re: [Tinyos-help] Migrating to a new microcontroller Hi Hugh, I have a working version of mspgcc and verified code for family 2 (msp430X). Now and tomorrow it is impossible for me to upload it. On wednesday I send to you all the instructions and code. Xavi ----------------------------- http://www.alcim.net On Mon, Oct 20, 2008 at 11:25 PM, Hugh Hartwig <[EMAIL PROTECTED]> wrote: Xavi, I am interested in the MSP430 specific code for the msp430F261x. Has this been placed on the contrib-cvs? I am also having trouble getting the latest version of MSP430-gcc in your link below to work for either tinyos-1.x or tinyos-2.x. I keep getting the error: "/usr/lib/ncc/tdspecs: No such file or directory" even though the directory does exist. Do you have any ideas why this is happening? Thanks, Hugh From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Xavier Orduña Sent: Wednesday, June 18, 2008 7:20 AM To: Gracinda García Lago Cc: [email protected] Subject: Re: [Tinyos-help] Migrating to a new microcontroller Hi Gracinda, If you use windows, you can use an already compiled and packaged version of mspgcc: http://sourceforge.net/project/showfiles.php?group_id=42303 <http://sourceforge.net/project/showfiles.php?group_id=42303&package_id=6858 4> &package_id=68584 It supports your micro. And forget about updating separately binutils, etc ... Xavi www.alcim.net Buscant sempre nous reptes, alguna proposta? On Wed, Jun 18, 2008 at 2:22 PM, Gracinda García Lago <[EMAIL PROTECTED]> wrote: Hi Xavi, Regarding to first step... I was looking for information in <http://mspgcc.sf.net/> mspgcc.sf.net, the webmaster told me that they had a patch tha supports msp430F2617 micro. Finally I found it and it was a patch for binutils v1.17. (http://mspgcc.cvs.sourceforge.net/mspgcc/packaging/patches/). Boomerang v2.0.2 uses binutils v1.16, so, first step I tried to follow was upgrading binutils from v1.16 to v1.17, but I went down with this ship. I didn´t know how to upgrade binutils v1.17 and after this, upgrade v1.17 with the patch. I tried to compile binutils v1.17 (configure, make and make install), but it didn´t work in cygwin.Do you know how to do it? I am not an expert in linux. You have told me that I have to upgrade mspgcc , but mspgcc includes gcc, binutils and gdb, doesn´t it? Do I have to upgrade everything or only binutils? Best regards and thank you for your time! Gracinda _____ De: Xavier Orduña [mailto:[EMAIL PROTECTED] Enviado el: martes, 17 de junio de 2008 15:18 Para: Gracinda García Lago CC: [email protected] Asunto: Re: [Tinyos-help] Migrating to a new microcontroller Hi Gracinda, Yes, I'm working with tinyos 2.0. Let's go step by step. To make msp430F2617 with Tinyos (event boomerang, 1.x, or 2.x). You must: - upgrade mspgcc (because the version distributed by default does not support this new msp430). (this includes the upgrade of nesC to use a different separator than $). - change files relating to specific msp430 code. The main difference between msp430F1 and msp430F2 is the new USCI component. - create a new platform in the tinyos toolchain. Regarding to step 1, if you use windows just download new mspgcc from mspgcc.sf.net, if not, you can build from sources or let me know and I will post to my tinyos contrib folder. Regarding to step 2, boomerang has related code to msp430 in moteiv/tos/platform, you must change there all the code related to UART, I2C and SPI. (and DCO clock calibration). Regarding to step 3, I have no idea of how to do it in boomerang. If you decide to change to tinyos 2.x, I've ported most part of the code, created a new msp430F2617 based platform, and I have a quite tested release (for my specific platform), maybe I can publish and early release too on my contrib code directory. Regards, Xavi www.alcim.net Buscant sempre nous reptes, alguna proposta? ---------- Forwarded message ---------- From: Gracinda García Lago <[EMAIL PROTECTED]> Date: Tue, Jun 17, 2008 at 2:42 PM Subject: RE: [Tinyos-help] Migrating to a new microcontroller To: Xavier Orduña <[EMAIL PROTECTED]> Cc: [email protected] Xavi, thank you for the information. I am using Boomerang 2.0.2 and it is tinyos v1.1.15. And this version doesn´t support msp430x2617. I think you are using TinyOS 2.0, aren´t you? Do you know how can I upgrade mspgcc (I am using Windows) to make it support msp430x2617 but using TinyOS v1.1.15? Can I install the latest version for this TinyOS or I need to install tinyos v2.0 before? Regards, _____ De: Xavier Orduña [mailto:[EMAIL PROTECTED] Enviado el: viernes, 13 de junio de 2008 10:42 Para: Gracinda García Lago CC: [email protected] Asunto: Re: [Tinyos-help] Migrating to a new microcontroller Hi, I don't know about using boomerang instead of tinyos. Let me explain my procedure to get msp430x2617 work in tinyos and then maybe we can find some similarities. Support for msp430x2617 it has been already included in mspgcc distribution. Do you need no patch. If you are using linux you can checkout last cvs and compile. (or ask me and I can send you an already compiled version). If you are using windows just download the last installer version. To make tinyos to use the new mspgcc, I've just changed the folder msp430 in the tinyos distribution, for a new one including the last mspgcc. Then, you have to check you have nesc 1.2.8 (or download there: http://www.isis.vanderbilt.edu/projects/NEST/tinyos-2.x-iris/tools/release/e xternal-tools/). Add the flag "-fnesc-separator=__" in msp.rules (folder tos/support/make/msp). And change the flag that indicates cpu. Regading to msp430X specific code, you have to change some things to make it work, If you are interested I can put the code in the contrib-cvs. I hope this fast explanation helps you in your problems! Xavi www.alcim.net Buscant sempre nous reptes, alguna proposta? On Fri, Jun 13, 2008 at 9:31 AM, Gracinda García Lago <[EMAIL PROTECTED]> wrote: Hi! I am trying to migrate to new microcontroller msp430F261x. I am using Boomerang 2.0.2 (binutils v2.16). I have found a patch (http://mspgcc.sourceforge.net/) that includes the msp430x261x, but this patch is for binutils v2.17. Have you used this patch? Do you know if it is possible to upgrade binutilsv2.16 in Boomerang 2.0.2 to v2.17? how? I have also installed Boomerang v2.0.4 (binutils v2.17) and after I have installed the patch but I got error messages. When I have reviewed the patch, I have checked modifications in files that I don´t find in my directory tree. In the directory tree I have found another files related to the linker and hardware ( for example ldscripts, msp430x1611.xu), but a new file for the new micro is not included in the patch, I don´t know if the patch will generate these scripts. So, I am confused about binutils package, the patch and the directory tree I have... I hope you can help me or clarify something! Best regards
_______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
