Steve, Sorry, I haven't notice the date. My fault. The rest is absolutely right. Opencall.org was unreachable. I have no idea why. All the sourceforge.net mirrors had (may be still have) the version with no 16x support. I asked developers, mailing list several times and got nothing. That was the reality.
Regards, Dmitriy Korovkin -----Original Message----- From: mspgcc-users-ad...@lists.sourceforge.net [mailto:mspgcc-users-ad...@lists.sourceforge.net] Sent: Tuesday, October 19, 2004 5:43 PM To: mspgcc-users@lists.sourceforge.net Subject: Re: [Mspgcc-users] Re: Stack initialized to incorrect address on MSP430F1611 Hi Dmitriy, Have you noticed the dates on the files on opencall.org? That is when the files were put there, and those are not the first to support the 1610, 1611 and 1612. The last update was because of issues with newer revisions of the FG43x. opencall.org was down for one week in the summer. That is all. Regards, Steve dkorov...@luxoft.com wrote: >Steve, we have enough talkings about this. Msp430x16x chips were >supported for months/years/centuries, but WITH NO ENGINEERING SAMPLES. >That was the key problem we tried you to understand. You personally kept >deep silence when I asked you. Some guys from small former soviet >republics started joking about "bad smiths". That "right" ftp server >opencall with the most correct and new version was down. So that was the >real situation. I don't want other guys to suffer from the same >situation and help them to do development not knocking doors of "the >great gurus". >Thank you that at last you decided to pay an attention to the problems >of other developers. It's better late than never, right? >Thanks, >Dmitriy Korovkin > >-----Original Message----- >From: mspgcc-users-ad...@lists.sourceforge.net >[mailto:mspgcc-users-ad...@lists.sourceforge.net] >Sent: Tuesday, October 19, 2004 5:26 PM >To: mspgcc-users@lists.sourceforge.net >Subject: Re: [Mspgcc-users] Re: Stack initialized to incorrect address >on MSP430F1611 > >dkorov...@luxoft.com wrote: > > > >>Hi Robert, >> >>I can give you the following idea. >> >>Take binutils with version >= 2.15 FROM GNU site (noone knows what >>RedHat have done and if it really works). Apply my patch to add >>msp430x1611 support from >> >> >> >https://sourceforge.net/tracker/download.php?group_id=42303&atid=432703 & >file_id=100003&aid=1020679 > > ><https://sourceforge.net/tracker/download.php?group_id=42303&atid=43270 3 >&file_id=100003&aid=1020679> > > >>This works on our site. Feel free to contact me if you have problems >>with this. >> >>We also forced TI guys to add the real support for msp430x16x devices >>in their msp430-gdbproxy. You may download it from >>ftp://ftp.opencall.org/pub/. But this server is really slow and often >>fails, so feel free to contact me if you need a Linux version of this >>server. >> >> >> >1611 support in gdbproxy has been available for months, without any >forcing. > >Regards, >Steve > > ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
