![]() |
Development enviroments orther than MPLAB
It took me all of five minutes to decide that there is no way I would use the MPLAB IDE to program the robot this year. Every part of it made me angry (especialy the ultra-long load times on my crappy old notebook), so I started using gVim + cygwin + make.
What are other people using to program it? |
Re: Development enviroments orther than MPLAB
wine+mcc18+makefile+ifi_picloader
works way better than MPLAB since I can use vim or kate or whatever else I want, and the cli bootloader feels less clumsy than ifi's loader. |
Re: Development enviroments orther than MPLAB
i would do something else, but im too lazy
|
Re: Development enviroments orther than MPLAB
horray for vim, the true "programmer's text editor"
|
Re: Development enviroments orther than MPLAB
Quote:
(you know youve been coding with vim too long when you start hitting j and k when your on the web... Thank heaven FireFox knows to start searching when you hit /) |
Re: Development enviroments orther than MPLAB
Quote:
|
Re: Development enviroments orther than MPLAB
Actually, I find vim scary. ;)
My team used MPLAB + Windows since I was the only one with Linux on their machine. Plus, I didn't find out until later that others got the IFI_Loader to work with WINE with no major problems. |
Re: Development enviroments orther than MPLAB
afaik, the ifi loader still doesn't work through wine. A new one was coded from scratch to do the job.
|
Re: Development enviroments orther than MPLAB
Same thing. ;)
|
Re: Development enviroments orther than MPLAB
I used the MPLAB IDE with windows cuz I was way to lazy to use anything else, I mean most of my code is just the default; My team was kinda picky about having it working b4 we shipped;
|
Re: Development enviroments orther than MPLAB
The bot barely worked when we shipped. And the code was screwed up so badly that the controller gave us a red-green. (RGOD!) Or an infinate loop.
|
Re: Development enviroments orther than MPLAB
:ahh: Thats nothing all our robot did when we shipped it was spin in a circle. cuz the stupid build team put one of the fricking moters in backwards. I think that when we get there i can download a code that works but we will literally be testing it on our bot for the first time then. If anything goes wrong i am sure that all you programers out there know that it is me who will be blamed for screwing it up, even though if the builders whould have put it in right it would not have been a problem. :ahh:
|
Re: Development enviroments orther than MPLAB
Our situation is sort of weird. I definitely like where we went with the robot and if it turns out correctly, look out for Miss Daisy. We didn't make too many modications to the code, not enough to warrant switching from Windows or anything. The problem is that our code hadn't been tested with the robot at all before we shipped. But we have some good programmers and I think that we will definitely turn out okay. See ya at Chesapeake.
|
Re: Development enviroments orther than MPLAB
Wow, I didn't realize how many teams actually had code that didn't work at ship. :ahh: This is my first year competing. :)
Surprisingly, even though we are rookies, we still got all our OI code tested and our main automous mode. :p |
Re: Development enviroments orther than MPLAB
Vim? Fwah.
I used vi (not vim) and make. Not GNU make either. Microsoft NMAKE. If I had access to a Mac, I would use Subethaedit, but I don't. If somebody were to port Subethaedit to Windows, I would regard them in the ranks of Cerf. |
Re: Development enviroments orther than MPLAB
I voted for MPLAB, but I just did MSC++ .NET, and I'm really happy. :D Now that's an IDE.
|
Re: Development enviroments orther than MPLAB
Quote:
As my old signature used to say, "I'm not anti-Microsoft, I'm just pro-quality." :) Yeah, MSC++ .NET is great (surprisingly, a good Microsoft product). The only reason I didn't use it is MPLAB allowed quick access to the compiler, while MSC++ .NET isn't custimizable for that sort of thing. Next year I'm going to find something better for our controls team to use. :) |
Re: Development enviroments orther than MPLAB
GVim/Vim + Cygwin + IDE for compilation. Don't have access to a linux computer other than at home for programming, and too lazy to figure out how to use MCC's command line.
|
Re: Development enviroments orther than MPLAB
Compared with the general rabble, Microsoft almost caters to developers.
|
Re: Development enviroments orther than MPLAB
Its too bad that only 3 voted for linux...Most of my team is affraid of it, including the other programmer, so im stuck using windows at the competitions...
|
Re: Development enviroments orther than MPLAB
I use ActiveState's Komodo a lot, otherwise Eclipse is worth a good look. Both are available under Linux or Windows. KDevelop under Linux is also worth a good look.
A lot of bots didn't work right off the bat at the early competitions, because people didn't follow the latest IFI/FIRST news about software updates and weird initial states upon RC startup. As for NMAKE, it's piece of $@#$@#$@#$@#. Gnu MAKE is available for Windows as well. Though I think it's high time that somebody come out with a better MAKE one of these days. |
Re: Development enviroments orther than MPLAB
We decided early on to scrap the MPLAB IDE and use cygwin & make instead. After a month or so I finally convinced the other mentors to use VIM. Now we're actually teaching the students how to use it.
An invaluable development tool I found a few years ago is cscope (http://cscope.sourceforge.net/). It parses all the source & header files in your build and creates a 'database' that allows you to quickly jump to a function definition, find all calls of a function, find all references to a symbol, etc. Even better you can integrate it with VIM so all you have to do is put your curser on a function call, hit <ctl>] and you're now at the function definition; hit g<ctl>\ and you have a list of all occurrances of the symbol under the cursor. I'd probably be half as productive at work if I didn't have VIM & cscope. Give it a try. If you need help send me a PM or start a new thread. |
Re: Development enviroments orther than MPLAB
I got our code working the day of shipping this year (goes to show how having access to the robot is a good thing eh). Last year however, we never really had the time to test, so we got to our regonal, and didn't move for hte first 2 practice matchs. Seems auto code didn't work right, go figure. :p
|
Re: Development enviroments orther than MPLAB
Cool! I like that. MS has been doing it for awhile, but it's nice to now someone else is.
|
Re: Development enviroments orther than MPLAB
Quote:
|
Re: Development enviroments orther than MPLAB
Ok I admit that is worse then what I had, but it is kinda funny; you must admit :D
But your team didn't know how well the code worked when you shipped yours, they knew that mine just made it spin around and around which was definatly not a confidence booster. But I am hopeing to have it compile :ahh: Today. This code that I have now better work or you may not see me at any compitions cuz my team will have killed me. :ahh: |
Re: Development enviroments orther than MPLAB
Quote:
Code:
// Set the left and right drive motors to the specified speed values.This chunk of code is the only place that has to keep track of "bigger than 127 goes forward, less is backward, proportional to the difference" or the other way around if either motor is wired the other way. It's much easier to read "SetDriveMotors(10, -10)" than "pwm01 = 137; pwm02 = 117;" and know that it's asking for a slow right turn. If one of the motors gets wired backwards, it's trivial to change the +/- for that motor in one well-defined place. (We also put polarized connectors on the motors, so that motors can't get reversed for anything less than a motor replacement.) It's also trivial to move the drive motor to a different PWM if need be. The software team gets so little time with the working robot, it doesn't pay to spend time and energy blaming the build/electronics team for something being backwards. If you keep the knowledge localized in the code, it's trivial to adjust, compile and download. This is especially handy if you just finished a big repair two minutes before the next match and there's no time to crawl back in and reverse a couple of wires. |
Re: Development enviroments orther than MPLAB
Quote:
|
Re: Development enviroments orther than MPLAB
Quote:
|
Re: Development enviroments orther than MPLAB
eh... I'm lazy... BTW Does anyone know what the heck is up with this error in mplink?
"Error - could not find file 'clib.lib'" I keep getting that when I try to compile on my own computer. I checked and clib.lib is right where it's supposed to be. Does it matter that I'm using the demo of c18? |
Re: Development enviroments orther than MPLAB
I've been trying to find out how to make a new platform for MS VC++ (in the new project dialog, the checked listbox down in the lower right). Unfortunately, I have had literaly no luck. Mine just says Win32. Any Ideas? [This includes MSDN and e-mailing a sugestion to the How-to group]
|
Re: Development enviroments orther than MPLAB
Under Linux, how do you compile your code? I heard about using make, but how?
|
Re: Development enviroments orther than MPLAB
Recently changed to Cygwin+Makefile+Vim
|
Re: Development enviroments orther than MPLAB
Quote:
|
Re: Development enviroments orther than MPLAB
Quote:
1) get mcc and the IFI loader working under wine 2) make a makefile that compiles everything. 1) Has been done many times, and there is a thread on it here: http://www.chiefdelphi.com/forums/sh...ght=wine+linux 2) I have written one that works under windows + cygwin, and wont take too much hacking to get it to run under linux. You can see it here: http://www.chiefdelphi.com/forums/sh...light=makefile I think I have done a pretty good job of commenting it, so it shouldent be that hard. Good luck! |
Re: Development enviroments orther than MPLAB
There are several other IDEs for PICMicro processors.
Check out MPLAB 5.7, which is supposed to be a lot less buggy: http://www.microchip.com/1010/pline/...ab5x/index.htm SourceBoost IDE (which I haven't tried yet, but he's also got C++ and Pascal compilers) http://www.picant.com/c2cpp/cpp.html MPLAB 6.50 just came out which should fix several bugs and adds some new features http://www.microchip.com/1010/pline/...lab6/index.htm HI-TIDE by some company whom I've never heard of: http://www.htsoft.com/products/hitide/picc18.htm Just takes a little searching around :) |
Re: Development enviroments orther than MPLAB
Quote:
What do you mean by "the general rabble"?! I sincerely hope you don't mean linux! Please report to the nearest Microsoft Deprogramming Center: ESR's Propaganda Post Slashdot: News for Linux Zealots The GNU Website: 'Nuff said ;) |
| All times are GMT -5. The time now is 00:12. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi