rjo_ said...
You are very close to ver 1.0 as far as I'm concerned[noparse]:)[/noparse]
It won't be a 1.0 until I get background/syntax highlighting, block group indent and code folding working as close to the way propeller tool does it as I can.
When I get that working, I'll be cracking that cold bottle I have in the fridge and calling it done.
you can ignore all of that stuff for the Mac... if someone wants it... let them add it themselves...
It is really easy to add a fancy text editor on the mac and customize it ... and then your compiler can be driven externally by that text editor.
By the way... please ignore everything in my first post of the day... I don't know what I did... but the Screen terminal is now working flawless for me[noparse]:)[/noparse]
I can exit... bst finds my prop... etc. etc. IT's a MIRacle[noparse]:)[/noparse]
exit using command-a command-\
to reset prop from Screen use command-a and then B (hold your shift key down)
It is as though I've died and gone to heaven[noparse]:)[/noparse]
Rich
As far as I'm concerned bst is version 1 on the Mac.
evanh said...
Well, I've finally bought my first Parallax product. [noparse]:)[/noparse] Two ICs + PropClip + PropRPM board.
It's all arrived in a well packaged parcel. [noparse]:)[/noparse] That was on 6 Oct, today is 11 Oct. Airmail from USA to NZ in 5 days is not bad at all.
I've tried out bst a little, and it worked fine for me. I've also downloaded bstc and will give that a try as well. Previously I've tried parallels and crossover, but this tool seems like it could be the way to go for everyday OS X propeller development. It will make backups and system maintenance easier, and it's quite efficient compared to the alternatives.
Can anyone recommend the easiest way to get all of the libraries and examples that come with the propeller tool into the Mac environment and usable with bst? Is there a five second solution?
Any other miscellaneous Mac tips particular to the use of the bst tools?
Since the use of screen was mentioned previously, I'll give a little tip tweaked from macosxhints.com. For any OS-X users that want a little screen hand holding - copy and paste this into the script editor. Compile and run to verify, then you can save it as an application. Tweak some of the settings based on your tastes and how you use it - e.g. if you're always using the same baudrate or serial driver then save some time and hardcode them.
set baudList to {1200, 2400, 4800, 4800, 9600, 19200, 38400, 57600, 115200, 230400}
set baudRate to (choose from list baudList default items {38400})
tell application "Terminal"
set serialDevices to (do shell script "ls /dev/cu*")
set theDeviceList to (paragraphs of serialDevices) as list
set theDevice to (choose from list theDeviceList)
do script "screen " & theDevice & " " & baudRate
set number of rows of window 1 to 100
set number of columns of window 1 to 80
set background color of window 1 to "black"
set normal text color of window 1 to "green"
set custom title of window 1 to "SerialOut"
display dialog "To reset the propeller <ctrl-a> then <B>, to quit your terminal session type <ctrl-a> then <ctrl-\\>"
end tell
KeithE said...
I've tried out bst a little, and it worked fine for me. I've also downloaded bstc and will give that a try as well. Previously I've tried parallels and crossover, but this tool seems like it could be the way to go for everyday OS X propeller development. It will make backups and system maintenance easier, and it's quite efficient compared to the alternatives.
Can anyone recommend the easiest way to get all of the libraries and examples that come with the propeller tool into the Mac environment and usable with bst? Is there a five second solution?
Here is a zip file containing _all_ the spin files that accompany Propeller Tool v1.2
I figure that
A) they appear to be under the MIT license, and I'm posting Parallax Code on a Parallax site
.. it should probably be safe to distribute.
I just installed Propeller Tool V1.2 under Wine and zipped up the resulting spin files.
Don't use the font that Propeller Tool installs though, it's broken on non Windows OS.
Use the one from the propeller Wiki (it contains a link to the forum here somewhere where the fixed font lives)
I was happy to learn the latest version of bst now works on my OSX 10.4.11 G4 machine. It still complains about the Parallax.TTF font on startup (even though I've installed the font from the wiki page you've listed). I'll put it thru it's paces this weekend.
Now that I've got a Prop to play with I've worked out that the purpose of the "Compiler Searchpaths" is for finding the listed spin OBJects to include.
Next - I haven't seen this mentioned but CTRL shortcuts aren't working. I first noticed CTRL-F10 not running the tokeniser but now I've noticed CTRL-S is also not saving my work.
evanh said...
Next - I haven't seen this mentioned but CTRL shortcuts aren't working. I first noticed CTRL-F10 not running the tokeniser but now I've noticed CTRL-S is also not saving my work.
Menus are working fine.
I'm using Kbuntu 8.04.
Yep, thanks Evanh.. I've been working on getting the shortcut keys set up to linux/mac standards and I may well have broken them.
I'll ensure they are fixed for the next release.
I was happy to learn the latest version of bst now works on my OSX 10.4.11 G4 machine. It still complains about the Parallax.TTF font on startup (even though I've installed the font from the wiki page you've listed). I'll put it thru it's paces this weekend.
Great job
Forrest
Thanks Forrest, could I trouble you to E-mail me a copy of your faulty font? I'd like to try and figure out why it's broken.
I happen to have a 10.4.11 G4 at home (how lucky is that) so I can really figure out what is happening.
>Here is a zip file containing _all_ the spin files that accompany Propeller Tool v1.2
Thanks a lot - for some reason I couldn't find the files in my Crossover (Wine based) directories. I could browse them in the Propeller tool, but not actually find a library/example directory to tar up.
I'm going to reorganize my office/lab space and then try some simple things out later in the day.
Using the new version all afternoon without any serious crashes. NICE!
I've had to re-detect the propeller a couple times, not a serious issue.
The crash recovery thought that I needed to recover once when I closed the app and opened something else.
Thanks for including the right-click close option.
How about a little code for not opening "Untitled" when another piece of spin is loaded with double-click?
(Also working fine now)
Question: Why Ctrl+10 and Ctrl+11 instead of just F10 and F11?
Can't wait to see the syntax highlighting! Super impressive work!
Using the new version all afternoon without any serious crashes. NICE!
I've had to re-detect the propeller a couple times, not a serious issue.
The crash recovery thought that I needed to recover once when I closed the app and opened something else.
Great stuff [noparse]:)[/noparse]
Oldbitcollector said...
Thanks for including the right-click close option.
How about a little code for not opening "Untitled" when another piece of spin is loaded with double-click?
(Also working fine now)
Ahh yes, I'll make sure that is fixed in the next rev.
Oldbitcollector said...
Question: Why Ctrl+10 and Ctrl+11 instead of just F10 and F11?
That is an easy one. I use Ubuntu standard (Gnome) and the WM hijacks F10 and F11. I can't seem to override that, so instead of downloading the prop it pops up the WM menu.
It's something I'm looking at, but at the moment I'm kinda otherwise occupied.
Cluso99 said...
BradC: Presume with Praxis's development you abandoned Windows???
Not at all, the Win32 branch will fall out of the stuff I'm doing anyway. I've just been concentrating on getting the Mac / Linux stuff polished up and working well before I complete the Win32 port.
I'm just after an IDE / compiler suite that works well across all my platforms. Windows is not one I use, but I kinda want to support anyway (particularly the old versions).
I was happy to learn the latest version of bst now works on my OSX 10.4.11 G4 machine. It still complains about the Parallax.TTF font on startup (even though I've installed the font from the wiki page you've listed). I'll put it thru it's paces this weekend.
Great job
Forrest
Thanks Forrest, could I trouble you to E-mail me a copy of your faulty font? I'd like to try and figure out why it's broken.
I happen to have a 10.4.11 G4 at home (how lucky is that) so I can really figure out what is happening.
brad at fnarfbargle dot com..
Cheers [noparse]:)[/noparse]
bst is complaining about the Parallax TTF font I downloaded from the link at the very bottom of this page propeller.wikispaces.com/Propeller+Font I installed the font with Font Book. Font Book checked it and verifies there's no problem with the font.
bst is complaining about the Parallax TTF font I downloaded from the link at the very bottom of this page propeller.wikispaces.com/Propeller+Font I installed the font with Font Book. Font Book checked it and verifies there's no problem with the font.
Hrm.. that's not much fun at all. If it complains it means that if it was not going to complain, it was going to crash.
I'll have to investigate a bit deeper, but I'm 8000km away from my G4 for another week.
I promise I'll get it fixed as soon as I can (if I can)
I've had to re-detect the propeller a couple times, not a serious issue.
If you have 5 minutes, would you mind running this test program for me?
It looks for the Propeller in the default place on linux (/dev/ttyUSB*) and tried the first port it finds.
All it does it try to detect the propeller 1000 times in a row (takes about 2 minutes), and will tell you how many times the detection failed.
On my 2 available test machines here (both Linux intel laptops) I get 0 failures, but if you are having to detect the prop several times then I anticipate some timing issues with your particular setup. If I can figure out what they are it'll make it easier for me to fix [noparse]:)[/noparse] 100% reliability is not just a good idea.. it's a goal.
Will run the test program later today as soon as I get a chance to set everything up.
Figured out why I was getting crash recovery messages..
Double click and open a .spin file. (no problem)
Make some changes to it and don't save it.
Minimize BST and double click another .spin file.
It opens another instance of BST and assumes that
the unsaved tab in the other program has crashed
and needs to be recovered instead of opening a
new tab in the existing BST already running.
Also found a program that doesn't seem to work.
Try downloading Gridrunner from http://forums.parallax.com/showthread.php?p=732651
and Ctrl-F10. On mine it drives the CPU up and
never seems to finish. Tried it twice and had to
power down the machine to clear things up.
Well, the Gridrunner code does have a few tricks up it's sleeve...
The code I borrowed from Coley sets the clock on the fly to be able to run on different boards.
Have a look at the HWDetect function, it could be a likely culprit...
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Living on the planet Earth might be expensive but it includes a free trip around the sun every year...
Experience level:
[noparse][[/noparse] ] Let's connect the motor to pin 1, it's a 6V motor so it should be fine.
[noparse][[/noparse] ] OK, I got my resistors hooked up with the LEDs.
[noparse][[/noparse]X] I got the Motor hooked up with the H-bridge and the 555 is supplying the PWM.
[noparse][[/noparse] ] Now, if I can only program the BOE-BOT to interface with he Flux Capacitor.
[noparse][[/noparse] ] I dream in SX28 assembler...
Bamse said...
Well, the Gridrunner code does have a few tricks up it's sleeve...
The code I borrowed from Coley sets the clock on the fly to be able to run on different boards.
Have a look at the HWDetect function, it could be a likely culprit...
Yeah, I downloaded it from the page linked, but it compiles fine for me here with bst and bstc. I've asked OBC to sent me a zip file of his stuff that dies to see if I can reproduce it.
If any code can be broken.. I'm your guy.. <SMIRK> [noparse]:)[/noparse]
I'm pretty good at finding ways to break things that the
author never tried (or even intended for that matter)
Seriously, you have done a huge amount of work
here in a short time. BST is nearing "insanely great"
status very quickly. I'm looking at helping put
together a small linux box for someone starting
with the propeller using BST.
I'm using the serial terminal that comes with
Ubuntu. Have you considered a PST type
terminal that will permit easy connect/disconnect
for use with this down the road?
I'm using the serial terminal that comes with
Ubuntu. Have you considered a PST type
terminal that will permit easy connect/disconnect
for use with this down the road?
OBC
Yes, you might just find serial terminal(s) built into the next version (along with one or two other tweaks and features).
Thanks for the encouragement OBC, it's nice to know people use this stuff [noparse]:)[/noparse]
This is my first program written entirely in the tool and I have one annoying bug that I just figured out.
If I forget to declare a local variable (which I have done more than once), I get an access violation when I try to compile...
See the two spin files attached...
The only difference is that the one that works has the variable declared in clear_Display...
PUB clear_Display | i
Keep up the good work...
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Living on the planet Earth might be expensive but it includes a free trip around the sun every year...
Experience level:
[noparse][[/noparse] ] Let's connect the motor to pin 1, it's a 6V motor so it should be fine.
[noparse][[/noparse] ] OK, I got my resistors hooked up with the LEDs.
[noparse][[/noparse]X] I got the Motor hooked up with the H-bridge and the 555 is supplying the PWM.
[noparse][[/noparse] ] Now, if I can only program the BOE-BOT to interface with he Flux Capacitor.
[noparse][[/noparse] ] I dream in SX28 assembler...
I must say, I ignored this thread for awhile, so I'm late to the party. But here's my story....
Last year I bought a new Dell laptop, it came with Vista preloaded (I know, blah!, I seriously think it's the crappiest piece of bloatware that micro$oft ever wrote) I loaded Ubuntu onto a partition and dual boot it.
Yesterday, Windows started spontaneously rebooting itself every 5 minutes, but Ubuntu still works fine.
So I wanted to use Propeller Tool... I was eyeing my wife's laptop, but....
it's pink
she gave me a look that means "don't even think about it"
Then I remembered this thread. I downloaded the executable, plugged in a PropPlug and a Propeller, and it immediately found the Propeller, and 30 seconds later, I downloaded a program to a Propeller. I almost didn't believe my eyes, thet you came up with a compiler and Programmer all in one, that runs on Linux! After hearing the horror storied of others trying to get the Propeller Tool to work with Wine, Parallels, etc, I didn't even want to attempt it.
The only problem I found was the font issue, characters seem to be overlapping each other. I'll play around with it tonight and see if I download the Parallax font from the Wiki and find the right place to put it.
What I'm saying is.... Great job! It's much appreciated! Maybe I can just get rid of windows all together now!
Brian
Post Edited (parts-man73) : 10/13/2008 8:24:52 PM GMT
Bamse said...
This is my first program written entirely in the tool and I have one annoying bug that I just figured out.
If I forget to declare a local variable (which I have done more than once), I get an access violation when I try to compile...
Fabulous bug report. Can reproduce it an will have it fixed in the next release. (which is probably another couple of days away at the moment).
In the meantime. "Don't do that" [noparse]:)[/noparse]
Did the autorecovery stuff work for you or are you saving all your work prior to compiling?
parts-man73 said...
I loaded Ubuntu onto a partition and dual boot it.
......
The only problem I found was the font issue, characters seem to be overlapping each other. I'll play around with it tonight and see if I download the Parallax font from the Wiki and find the right place to put it.
Ubuntu? Grab the font from the link in the Wiki and put it in
~/.fonts
The easy way is to log out and log back in again (or reboot). There is another way to get it to ra-cache the fonts but I forget off the top of my head.
Nice to know it's working for you [noparse]:)[/noparse]
Comments
It won't be a 1.0 until I get background/syntax highlighting, block group indent and code folding working as close to the way propeller tool does it as I can.
When I get that working, I'll be cracking that cold bottle I have in the fridge and calling it done.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Pull my finger!
It is really easy to add a fancy text editor on the mac and customize it ... and then your compiler can be driven externally by that text editor.
By the way... please ignore everything in my first post of the day... I don't know what I did... but the Screen terminal is now working flawless for me[noparse]:)[/noparse]
I can exit... bst finds my prop... etc. etc. IT's a MIRacle[noparse]:)[/noparse]
exit using command-a command-\
to reset prop from Screen use command-a and then B (hold your shift key down)
It is as though I've died and gone to heaven[noparse]:)[/noparse]
Rich
As far as I'm concerned bst is version 1 on the Mac.
Rich
It's all arrived in a well packaged parcel. [noparse]:)[/noparse] That was on 6 Oct, today is 11 Oct. Airmail from USA to NZ in 5 days is not bad at all.
Can anyone recommend the easiest way to get all of the libraries and examples that come with the propeller tool into the Mac environment and usable with bst? Is there a five second solution?
Any other miscellaneous Mac tips particular to the use of the bst tools?
Since the use of screen was mentioned previously, I'll give a little tip tweaked from macosxhints.com. For any OS-X users that want a little screen hand holding - copy and paste this into the script editor. Compile and run to verify, then you can save it as an application. Tweak some of the settings based on your tastes and how you use it - e.g. if you're always using the same baudrate or serial driver then save some time and hardcode them.
set baudList to {1200, 2400, 4800, 4800, 9600, 19200, 38400, 57600, 115200, 230400}
set baudRate to (choose from list baudList default items {38400})
tell application "Terminal"
set serialDevices to (do shell script "ls /dev/cu*")
set theDeviceList to (paragraphs of serialDevices) as list
set theDevice to (choose from list theDeviceList)
do script "screen " & theDevice & " " & baudRate
set number of rows of window 1 to 100
set number of columns of window 1 to 80
set background color of window 1 to "black"
set normal text color of window 1 to "green"
set custom title of window 1 to "SerialOut"
display dialog "To reset the propeller <ctrl-a> then <B>, to quit your terminal session type <ctrl-a> then <ctrl-\\>"
end tell
Here is a zip file containing _all_ the spin files that accompany Propeller Tool v1.2
I figure that
A) they appear to be under the MIT license, and
.. it should probably be safe to distribute.
I just installed Propeller Tool V1.2 under Wine and zipped up the resulting spin files.
Don't use the font that Propeller Tool installs though, it's broken on non Windows OS.
Use the one from the propeller Wiki (it contains a link to the forum here somewhere where the fixed font lives)
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Pull my finger!
I was happy to learn the latest version of bst now works on my OSX 10.4.11 G4 machine. It still complains about the Parallax.TTF font on startup (even though I've installed the font from the wiki page you've listed). I'll put it thru it's paces this weekend.
Great job
Forrest
Happy happy.
Menus are working fine.
I'm using Kbuntu 8.04.
Yep, thanks Evanh.. I've been working on getting the shortcut keys set up to linux/mac standards and I may well have broken them.
I'll ensure they are fixed for the next release.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Pull my finger!
Thanks Forrest, could I trouble you to E-mail me a copy of your faulty font? I'd like to try and figure out why it's broken.
I happen to have a 10.4.11 G4 at home (how lucky is that) so I can really figure out what is happening.
brad at fnarfbargle dot com..
Cheers [noparse]:)[/noparse]
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Pull my finger!
Thanks a lot - for some reason I couldn't find the files in my Crossover (Wine based) directories. I could browse them in the Propeller tool, but not actually find a library/example directory to tar up.
I'm going to reorganize my office/lab space and then try some simple things out later in the day.
Using the new version all afternoon without any serious crashes. NICE!
I've had to re-detect the propeller a couple times, not a serious issue.
The crash recovery thought that I needed to recover once when I closed the app and opened something else.
Thanks for including the right-click close option.
How about a little code for not opening "Untitled" when another piece of spin is loaded with double-click?
(Also working fine now)
Question: Why Ctrl+10 and Ctrl+11 instead of just F10 and F11?
Can't wait to see the syntax highlighting! Super impressive work!
OBC
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
New to the Propeller?
Getting started with a Propeller Protoboard?
Check out: Introduction to the Proboard & Propeller Cookbook 1.4
Updates to the Cookbook are now posted to: Propeller.warrantyvoid.us
Got an SD card connected? - PropDOS
Post Edited (Oldbitcollector) : 10/12/2008 8:20:52 PM GMT
Great stuff [noparse]:)[/noparse]
Ahh yes, I'll make sure that is fixed in the next rev.
That is an easy one. I use Ubuntu standard (Gnome) and the WM hijacks F10 and F11. I can't seem to override that, so instead of downloading the prop it pops up the WM menu.
It's something I'm looking at, but at the moment I'm kinda otherwise occupied.
Glad it's working for you [noparse]:)[/noparse]
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Pull my finger!
Not at all, the Win32 branch will fall out of the stuff I'm doing anyway. I've just been concentrating on getting the Mac / Linux stuff polished up and working well before I complete the Win32 port.
I'm just after an IDE / compiler suite that works well across all my platforms. Windows is not one I use, but I kinda want to support anyway (particularly the old versions).
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Pull my finger!
bst is complaining about the Parallax TTF font I downloaded from the link at the very bottom of this page propeller.wikispaces.com/Propeller+Font I installed the font with Font Book. Font Book checked it and verifies there's no problem with the font.
Hrm.. that's not much fun at all. If it complains it means that if it was not going to complain, it was going to crash.
I'll have to investigate a bit deeper, but I'm 8000km away from my G4 for another week.
I promise I'll get it fixed as soon as I can (if I can)
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Pull my finger!
If you have 5 minutes, would you mind running this test program for me?
It looks for the Propeller in the default place on linux (/dev/ttyUSB*) and tried the first port it finds.
All it does it try to detect the propeller 1000 times in a row (takes about 2 minutes), and will tell you how many times the detection failed.
On my 2 available test machines here (both Linux intel laptops) I get 0 failures, but if you are having to detect the prop several times then I anticipate some timing issues with your particular setup. If I can figure out what they are it'll make it easier for me to fix [noparse]:)[/noparse] 100% reliability is not just a good idea.. it's a goal.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Pull my finger!
Figured out why I was getting crash recovery messages..
Double click and open a .spin file. (no problem)
Make some changes to it and don't save it.
Minimize BST and double click another .spin file.
It opens another instance of BST and assumes that
the unsaved tab in the other program has crashed
and needs to be recovered instead of opening a
new tab in the existing BST already running.
Also found a program that doesn't seem to work.
Try downloading Gridrunner from
http://forums.parallax.com/showthread.php?p=732651
and Ctrl-F10. On mine it drives the CPU up and
never seems to finish. Tried it twice and had to
power down the machine to clear things up.
OBC
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
New to the Propeller?
Getting started with a Propeller Protoboard?
Check out: Introduction to the Proboard & Propeller Cookbook 1.4
Updates to the Cookbook are now posted to: Propeller.warrantyvoid.us
Got an SD card connected? - PropDOS
The code I borrowed from Coley sets the clock on the fly to be able to run on different boards.
Have a look at the HWDetect function, it could be a likely culprit...
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Living on the planet Earth might be expensive but it includes a free trip around the sun every year...
Experience level:
[noparse][[/noparse] ] Let's connect the motor to pin 1, it's a 6V motor so it should be fine.
[noparse][[/noparse] ] OK, I got my resistors hooked up with the LEDs.
[noparse][[/noparse]X] I got the Motor hooked up with the H-bridge and the 555 is supplying the PWM.
[noparse][[/noparse] ] Now, if I can only program the BOE-BOT to interface with he Flux Capacitor.
[noparse][[/noparse] ] I dream in SX28 assembler...
/Bamse
Yeah, I downloaded it from the page linked, but it compiles fine for me here with bst and bstc. I've asked OBC to sent me a zip file of his stuff that dies to see if I can reproduce it.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Pull my finger!
I'm pretty good at finding ways to break things that the
author never tried (or even intended for that matter)
Seriously, you have done a huge amount of work
here in a short time. BST is nearing "insanely great"
status very quickly. I'm looking at helping put
together a small linux box for someone starting
with the propeller using BST.
I'm using the serial terminal that comes with
Ubuntu. Have you considered a PST type
terminal that will permit easy connect/disconnect
for use with this down the road?
OBC
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
New to the Propeller?
Getting started with a Propeller Protoboard?
Check out: Introduction to the Proboard & Propeller Cookbook 1.4
Updates to the Cookbook are now posted to: Propeller.warrantyvoid.us
Got an SD card connected? - PropDOS
Yes, you might just find serial terminal(s) built into the next version (along with one or two other tweaks and features).
Thanks for the encouragement OBC, it's nice to know people use this stuff [noparse]:)[/noparse]
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Pull my finger!
Just want to say thanks one more time...
This is my first program written entirely in the tool and I have one annoying bug that I just figured out.
If I forget to declare a local variable (which I have done more than once), I get an access violation when I try to compile...
See the two spin files attached...
The only difference is that the one that works has the variable declared in clear_Display...
PUB clear_Display | i
Keep up the good work...
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Living on the planet Earth might be expensive but it includes a free trip around the sun every year...
Experience level:
[noparse][[/noparse] ] Let's connect the motor to pin 1, it's a 6V motor so it should be fine.
[noparse][[/noparse] ] OK, I got my resistors hooked up with the LEDs.
[noparse][[/noparse]X] I got the Motor hooked up with the H-bridge and the 555 is supplying the PWM.
[noparse][[/noparse] ] Now, if I can only program the BOE-BOT to interface with he Flux Capacitor.
[noparse][[/noparse] ] I dream in SX28 assembler...
/Bamse
Last year I bought a new Dell laptop, it came with Vista preloaded (I know, blah!, I seriously think it's the crappiest piece of bloatware that micro$oft ever wrote) I loaded Ubuntu onto a partition and dual boot it.
Yesterday, Windows started spontaneously rebooting itself every 5 minutes, but Ubuntu still works fine.
So I wanted to use Propeller Tool... I was eyeing my wife's laptop, but....
Then I remembered this thread. I downloaded the executable, plugged in a PropPlug and a Propeller, and it immediately found the Propeller, and 30 seconds later, I downloaded a program to a Propeller. I almost didn't believe my eyes, thet you came up with a compiler and Programmer all in one, that runs on Linux! After hearing the horror storied of others trying to get the Propeller Tool to work with Wine, Parallels, etc, I didn't even want to attempt it.
The only problem I found was the font issue, characters seem to be overlapping each other. I'll play around with it tonight and see if I download the Parallax font from the Wiki and find the right place to put it.
What I'm saying is.... Great job! It's much appreciated! Maybe I can just get rid of windows all together now!
Brian
Post Edited (parts-man73) : 10/13/2008 8:24:52 PM GMT
Fabulous bug report. Can reproduce it an will have it fixed in the next release. (which is probably another couple of days away at the moment).
In the meantime. "Don't do that" [noparse]:)[/noparse]
Did the autorecovery stuff work for you or are you saving all your work prior to compiling?
Glad it's working for you.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Pull my finger!
Ubuntu? Grab the font from the link in the Wiki and put it in
~/.fonts
The easy way is to log out and log back in again (or reboot). There is another way to get it to ra-cache the fonts but I forget off the top of my head.
Nice to know it's working for you [noparse]:)[/noparse]
Cheers!
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Pull my finger!