Yes, but I would need to download all of propgcc to get it.. and in any case I wanted something with very little complexity and extremely self-contained, and modifyable the way I wanted it. Finally, writing such tools is something I like, if I couldn't do any programming I wouldn't have worked with microcontrollers in the first place.
I can certainly agree with that! Are you going to post the code for your loader?
I'm not sure why Parallax hasn't moved propgcc to github. I don't see any reason not to.
I don't understand how this works out. Using github requires exporting the current Mercurial repository to git. Meanwhile the upstream GCC is maintained in Subversion as far as I can tell.
One could imagine that one day the Propeller targets could be accepted into the mainstream GCC project. That would then require exporting a git repo in to Subversion.
All seems very tortuous and round about to me.
Even if prop-gcc never makes it back upstream how does it keep up to date with GCC changes? Does it? Will it?
I don't understand how this works out. Using github requires exporting the current Mercurial repository to git. Meanwhile the upstream GCC is maintained in Subversion as far as I can tell.
One could imagine that one day the Propeller targets could be accepted into the mainstream GCC project. That would then require exporting a git repo in to Subversion.
All seems very tortuous and round about to me.
Even if prop-gcc never makes it back upstream how does it keep up to date with GCC changes? Does it? Will it?
There is a tool on github for importing Subversion archives. I did a trial run of this and was able to import the propgcc project to github in about half an hour.
Unfortunately, I am not able to import propgcc into the Parallax github account so this is just a dry run but you can try making a clone to see if everything worked as expected.
That is cool that the import works painlessly. I'll try and clone and build it if I ever get a free moment.
One could invite Parallax to take ownership of such a repo. Github has a mechanism to transfer repo ownership. You invite the new owner, they accept, within some few days time out, job done.
However Parallax is not much in tune with this. Chip and I were discussing Parallax taking over my "de-tabbed" P1 Verilog repo a little while back. But then they put up their own any way.
Can you get the other devs to switch to the git repo though?
Hi Frida, I am in the process of rewriting PropellerIDE's interface to the compiler and loader. This should be fixed (or at least broken differently =P) in the next release.
There is a tool on github for importing Subversion archives. I did a trial run of this and was able to import the propgcc project to github in about half an hour.
Unfortunately, I am not able to import propgcc into the Parallax github account so this is just a dry run but you can try making a clone to see if everything worked as expected.
Hi David, it should only take a quick email to Jeff Martin to get your project moved into the Parallax github. Once Jeff approves it, you will have admin privileges for the project immediately after transferring it over.
Hi Frida, I am in the process of rewriting PropellerIDE's interface to the compiler and loader. This should be fixed (or at least broken differently =P) in the next release.
I wonder if it would be worth trying to use just the ploader.c portion of p1load in PropellerIDE. That way there won't be a need to close the serial port after downloading. Can you give me the link to the PropellerIDE github repository? I'll check it out and see what might be involved with linking loader code directly into the app.
I wonder if it would be worth trying to use just the ploader.c portion of p1load in PropellerIDE. That way there won't be a need to close the serial port after downloading. Can you give me the link to the PropellerIDE github repository? I'll check it out and see what might be involved with linking loader code directly into the app.
Having the loader integrated instead of a separate application would be very nice indeed. I must warn you that this part of the code is currently undergoing major refactoring as I separate the build steps from the main window, so it's probably going to look pretty different in a couple days. Though I am eager to see how easy integration with the new library will be.
I just tried it on my Windows 7 machine -- got an error dialog that it couldn't start the loader.
Hi Jon,
Thanks for trying. It sounds like I'm going to need to install PropellerIDE in my Windows VM to figure this one out. I've only run p1load from the command line so far.
Just to be clear, p1load.exe runs fine from a command-prompt window. It just appears that p1load.exe is not being executed correctly from PropellerIDE on my Windows machine.
I pointed out 2 or 3 times that the problem isn't p1load, but the problem appears to be in PropellerIDE. Brett Weir commented that the problem was in the path separators, and that he had checked in a fix.
What the issue actually was is that I had moved some code around and had a problem with passing the wrong path separators to the loader. It's fixed in my branch in the following commit if anyone is interested in building it before I make another release: https://github.com/bweir/PropellerIDE/commit/5442b0349eb42078487c96239f0b7e00a292be81
I pointed out 2 or 3 times that the problem isn't p1load, but the problem appears to be in PropellerIDE. Brett Weir commented that the problem was in the path separators, and that he had checked in a fix.
Would it be possible to get a new binary of PropellerIDE with the fix in it? PropellerIDE is now highlighted on the main forums.parallax.com webpage, and the Windows version doesn't even work. It would seem to be a bit embarrassing for Parallax.
Would it be possible to get a new binary of PropellerIDE with the fix in it? PropellerIDE is now highlighted on the main forums.parallax.com webpage, and the Windows version doesn't even work. It would seem to be a bit embarrassing for Parallax.
I guess I can build a Windows version if I know which repository has the p1load launching fix.
Would it be possible to get a new binary of PropellerIDE with the fix in it? PropellerIDE is now highlighted on the main forums.parallax.com webpage, and the Windows version doesn't even work. It would seem to be a bit embarrassing for Parallax.
Oh, no, it is? ? >.< Okay, I'll make a new release by evenings end then. *gulp*
Brett, thanks for posting the new release. I installed it on my Windows XP machine, and the loader now works! I did have to fiddle around with the Symantec virus checker to run the installer, but that's normal for new programs. I also noticed that a DOS window pops up along with the normal GUI window. It looks like it displays the command-line parameters whenever I do a compile or load.
Brett, thanks for posting the new release. I installed it on my Windows XP machine, and the loader now works! I did have to fiddle around with the Symantec virus checker to run the installer, but that's normal for new programs. I also noticed that a DOS window pops up along with the normal GUI window. It looks like it displays the command-line parameters whenever I do a compile or load.
Ahhh, I must have let a CONFIG += console slip in, and Windows doesn't support true dual-mode GUI/console apps. =|
I haven't been too worried about it since everything is still under heavy development, but I suppose it's time I properly set up debug/release builds, with all the fancy things like oprofile and gdb enabled in the debug build. Then little slips like this won't happen any more.
I also need to start thinking about a test suite. That requires a test rack. Currently Linux is the only platform with a fully automated release process; lifecycle management is much more annoying on other platforms. Mac with its strict policy against virtualization, and Windows with, well, being completely different from the other platforms. Embedded platforms will be another challenge altogether.
But these things will help improve output consistency.
Looking good! It compiles a couple of my programs and downloads and programs eeprom fine. The highlighted colors of the test looks great.
When PropellerIDE re-opens, it does not recall the directory the source is in from the previous time it was used.
Is it possible to recall the last used source directory, or alternately, add an option in settings for the default source directory? (I do not have my source under the Programs/PropellerIDE/ directory).
I would also like to be able to set different tab settings for DAT and PRI/PUB in particular.
Brett,
Each time I try to build my code within PropellerIDE (F9) and there is a compile error a new instance of my code is added to the tabs at the top of the screen.
Also is it possible to have the COM port on the terminal user definable. I have several projects that have secondary comms (backdoor) to allow the primary port to be used with supporting software.
Cheers
Brian
Looking good! It compiles a couple of my programs and downloads and programs eeprom fine. The highlighted colors of the test looks great.
When PropellerIDE re-opens, it does not recall the directory the source is in from the previous time it was used.
Is it possible to recall the last used source directory, or alternately, add an option in settings for the default source directory? (I do not have my source under the Programs/PropellerIDE/ directory).
I would also like to be able to set different tab settings for DAT and PRI/PUB in particular.
Ahhh! 0.0.0 on Windows is fixed in the master now, thanks! Also, I feel that "Spin" is an unambiguous identifier since PASM code is always within a Spin object and doesn't exist by itself in this environment. And Spin/PASM means the about dialog has to explain what PASM means in the first place, which doesn't really belong there. So I will keep it the way it is.
Last used directory was marked for deletion during refactoring but will be re-implemented soon. I would like some feedback on that feature though. Would you guys want last used directory to be managed on a per-file basis, or a single last-used directory for the whole application? I also plan to make the library file the default path when none other is found. How does that sound?
I don't fully understand your last suggestion. What do you mean by different tab settings?
Brett,
Each time I try to build my code within PropellerIDE (F9) and there is a compile error a new instance of my code is added to the tabs at the top of the screen.
Also is it possible to have the COM port on the terminal user definable. I have several projects that have secondary comms (backdoor) to allow the primary port to be used with supporting software.
Cheers
Brian
Ah, that first one is fixed in the master already and will be included in the next release.
The serial terminal will be subject to significant rework very soon; work which has not been started. I am very interested in having the port chosen in the terminal window itself instead of by the main window also, so that's on my todo list. I would also like the ability to open as many terminal windows as I want.
Comments
One could imagine that one day the Propeller targets could be accepted into the mainstream GCC project. That would then require exporting a git repo in to Subversion.
All seems very tortuous and round about to me.
Even if prop-gcc never makes it back upstream how does it keep up to date with GCC changes? Does it? Will it?
https://github.com/dbetz/propgcc
Unfortunately, I am not able to import propgcc into the Parallax github account so this is just a dry run but you can try making a clone to see if everything worked as expected.
That is cool that the import works painlessly. I'll try and clone and build it if I ever get a free moment.
One could invite Parallax to take ownership of such a repo. Github has a mechanism to transfer repo ownership. You invite the new owner, they accept, within some few days time out, job done.
However Parallax is not much in tune with this. Chip and I were discussing Parallax taking over my "de-tabbed" P1 Verilog repo a little while back. But then they put up their own any way.
Can you get the other devs to switch to the git repo though?
http://forums.parallax.com/showthread.php/157834-LameStation-is-the-new-maintainer-of-Propeller-IDE?p=1300598&viewfull=1#post1300598
Hi Frida, I am in the process of rewriting PropellerIDE's interface to the compiler and loader. This should be fixed (or at least broken differently =P) in the next release.
Hi David, it should only take a quick email to Jeff Martin to get your project moved into the Parallax github. Once Jeff approves it, you will have admin privileges for the project immediately after transferring it over.
Thanks,
David
p1load.zip
So here is the main stable repository: https://github.com/parallaxinc/PropellerIDE
And here is my unstable WIP repository: https://github.com/bweir/PropellerIDE
Having the loader integrated instead of a separate application would be very nice indeed. I must warn you that this part of the code is currently undergoing major refactoring as I separate the build steps from the main window, so it's probably going to look pretty different in a couple days. Though I am eager to see how easy integration with the new library will be.
Oh sweet! I can try it out tomorrow when I'm in front of a Windows box again. =P
I just tried it on my Windows 7 machine -- got an error dialog that it couldn't start the loader.
Thanks for trying. It sounds like I'm going to need to install PropellerIDE in my Windows VM to figure this one out. I've only run p1load from the command line so far.
Thank you. >.<
Is this fix in the Parallax github repository or do I need to check out your repository to get it?
Thanks,
David
Oh, no, it is? ? >.< Okay, I'll make a new release by evenings end then. *gulp*
The fix is in my private repo but I'll move it over within a couple hours to the main one.
Ahhh, I must have let a CONFIG += console slip in, and Windows doesn't support true dual-mode GUI/console apps. =|
I haven't been too worried about it since everything is still under heavy development, but I suppose it's time I properly set up debug/release builds, with all the fancy things like oprofile and gdb enabled in the debug build. Then little slips like this won't happen any more.
I also need to start thinking about a test suite. That requires a test rack. Currently Linux is the only platform with a fully automated release process; lifecycle management is much more annoying on other platforms. Mac with its strict policy against virtualization, and Windows with, well, being completely different from the other platforms. Embedded platforms will be another challenge altogether.
But these things will help improve output consistency.
Going to give it a run now
When PropellerIDE re-opens, it does not recall the directory the source is in from the previous time it was used.
Is it possible to recall the last used source directory, or alternately, add an option in settings for the default source directory? (I do not have my source under the Programs/PropellerIDE/ directory).
I would also like to be able to set different tab settings for DAT and PRI/PUB in particular.
Each time I try to build my code within PropellerIDE (F9) and there is a compile error a new instance of my code is added to the tabs at the top of the screen.
Also is it possible to have the COM port on the terminal user definable. I have several projects that have secondary comms (backdoor) to allow the primary port to be used with supporting software.
Cheers
Brian
Ahhh! 0.0.0 on Windows is fixed in the master now, thanks! Also, I feel that "Spin" is an unambiguous identifier since PASM code is always within a Spin object and doesn't exist by itself in this environment. And Spin/PASM means the about dialog has to explain what PASM means in the first place, which doesn't really belong there. So I will keep it the way it is.
Last used directory was marked for deletion during refactoring but will be re-implemented soon. I would like some feedback on that feature though. Would you guys want last used directory to be managed on a per-file basis, or a single last-used directory for the whole application? I also plan to make the library file the default path when none other is found. How does that sound?
I don't fully understand your last suggestion. What do you mean by different tab settings?
Ah, that first one is fixed in the master already and will be included in the next release.
The serial terminal will be subject to significant rework very soon; work which has not been started. I am very interested in having the port chosen in the terminal window itself instead of by the main window also, so that's on my todo list. I would also like the ability to open as many terminal windows as I want.
Thanks for the feedback!