One request for BST, is it possible to add a close button onto each tab? Nothing important, just one of those things i wish was there. Latest release has run like a charm so far. Most of my usage has been on XP.
The close button on Tab is something I've been looking at, but to make it consistent I need to make owner drawn tabs for OSX (like Safari) and I'm not quite up to that chapter in "OSX GUI programming for dummies" yet [noparse];)[/noparse]
It's something that is pretty high on my list, but I've just not got there yet.
This latest version _should_ have *much* faster and more reliable downloads on Windows, especially if you turn on the double baud rate option in the compiler options
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Cardinal Fang! Fetch the comfy chair.
Hi Brad.
First of all, thanks for all the hard work on the compiler...
I recently upgraded to 0.17 and I started working on a PRG loader for the C=64.
The code is far from finished and have a lot of errors.
However when I try to compile the program, the progress bar comes up and then it hangs.
I logged out to close down 0.17, downloaded 0.16 and tried again, this time the 0.16 gives me an "Access Violation" when I try to compile...
Just wonder if you could have a look at it when you have a minute...
I'm running Ubuntu 8.04 and using the Linux version of BST...
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
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...
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
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...
Thanks Bamse. I made some changes to the way a spin method line is parsed to fix another bug and must have broken it.
I have two other fixes for bugs sevs picked up and I'll have a pre-release out with it all fixed today.
I've decided my QA process is taking too long between releases, so I'm going to start dropping -preX builds as bugs get fixed for those that get bitten by them.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Cardinal Fang! Fetch the comfy chair.
In future, all pre-release builds for any of the bst series of tools will be dropped in this directory.
I intend the pre-release builds to be lightly tested snapshots of my development process, they have not been exposed to any of my QA testing aside from a quick compiler regression test (on x86 linux only) and some brief functionality testing. This allows me to get builds done from my laptop when I'm away from my QA environment and try and get a more rapid response to critical crash bugs out faster.
Unless you are a Windows user with mis-behaving recovery files, or getting caught with the compiler bug Bamse identified, there is zero functional reason to upgrade to 0.18-pre1.
Current Changes :
I made a blue with the Windows build and the way it removed redundant auto-recovery files that sevs identified. I'm not sure it will affect many Windows users, but it had an oddity with the way a Windows users "Home" directory was located.
I've tried to enable the opening of project files from a drag and drop event or icon / association click from the file manager.
I've fixed the compiler bug Bamse found above.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Cardinal Fang! Fetch the comfy chair.
I have just started using Linux Mint because of BST (v0.17) and I loveit [noparse]:)[/noparse]
I have a feature request which may or may not of already been mentioned...I havent read through all 21 pages :P
Is it possible to add the shift+tab feature to shift a selected block of code back 1 tab? Like in the proptool.
It's already there.. it's Ctrl-Shift-I to indent and Ctrl-Shift-U to un-indent.
Being cross platform means having to compromise a little on ket-shortcuts unfortunately.
I _really_ need to sit down and document this stuff.... can anyone insert some more hours into my days?
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Cardinal Fang! Fetch the comfy chair.
I've noticed also that the compiler picks up on a few issues with my programming which the proptool didnt [noparse]:)[/noparse]
Like trying to perform 'if p == 0.0', gives me a compile error. Forces me to use the floating math compare [noparse]:)[/noparse]
Oh? The PropTool allows that? I guess I should too then, I just figured it was a _very_ easy programming mistake to make that would likely lead to confusion.
I guess comparing a static float value to a variable is legal...
Thanks for the pointer, I'm going to have to see how far I can bend the Parallax compiler and try to comply..
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Cardinal Fang! Fetch the comfy chair.
I just tried out the IDE on Mac OS X and found that pressing the tab key to indent my code causes an access violation. Is this because of something I'm doing wrong or is this a bug in the IDE?
MachMan said...
I just tried out the IDE on Mac OS X and found that pressing the tab key to indent my code causes an access violation. Is this because of something I'm doing wrong or is this a bug in the IDE?
I'm not sure. I'd say with 99% certainty it's not something you are doing wrong and a bug in my code.
Which version of OSX, which architecture (Intel or PowerPC) and which version of BST?
I made some very intrusive and significant changes for the 0.17 release that is specifically linked to the TAB key, so it's quite likely I have a bug there.
Can you also give me a step by step as to how I can reproduce it..
ie.. load this file I have attached here, place the cursor on line 15, column 12 and press Tab.
Also, have a look in the IDE options and let me know which tab configuration you have selected (Standard, Smart or Parallax compatible). Have you changed any of the Tab stops in the configuration dialog?
<edit> Do you have the colour syntax highlighter turned on? I just found a potential crasher if it's disabled (Parallax style tabs *require* the syntax highlighter be enabled).
.. Just on that, does _anyone_ not have the highlighter enabled? So much stuff relies on it I'm considering removing the option to disable it.
Nevermind, it's a *huge* hole in my TAB code and the way it interacts with the highlighter. I'm sitting here in wonder that it *ever* worked. I'll have a fix out shortly.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Cardinal Fang! Fetch the comfy chair.
This crash should only manifest itself when you are at the top of a page and are above any block definitions. I'd never seen it as all my code these days starts with CON right at the top.
It's not a bad upgrade though as it is a nasty crash and can potentially lose you work even if you do have periodic auto-recovery save turned on (which I highly recommend)
Anyway, as I asked above, is anyone _not_ using the highlighter? I've got the speed up now to a point where the highlighter makes negligible impact. The speed issues on GTK2 are related to the font rendering and not the colours.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Cardinal Fang! Fetch the comfy chair.
This crash should only manifest itself when you are at the top of a page and are above any block definitions. I'd never seen it as all my code these days starts with CON right at the top.
It's not a bad upgrade though as it is a nasty crash and can potentially lose you work even if you do have periodic auto-recovery save turned on (which I highly recommend)
Anyway, as I asked above, is anyone _not_ using the highlighter? I've got the speed up now to a point where the highlighter makes negligible impact. The speed issues on GTK2 are related to the font rendering and not the colours.
Thanks, that fixed it. The only reason I wasn't using the highlighter is that I hadn't got around to turning it on.
Compiler relaxed so that using a raw float in a spin expression is not an error (the Parallax compiler allows it) however it *is* still a warning
to try and prevent this : http://forums.parallax.com/showthread.php?p=790611
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Cardinal Fang! Fetch the comfy chair.
It is very nice propose from You.
And it is very fine Tool to.
But only if it stil is posible to ad more posts to this.
Christoffer
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔ Nothing is impossible, there are only different degrees of difficulty. For every stupid question there is at least one intelligent answer. Don't guess - ask instead. If you don't ask you won't know. If your gonna construct something, make it·as simple as·possible yet as versatile as posible.
Does anybody have a preference one way or another?
Ken Gracey
G'day Ken,
Maybe what we need is a simple sticky with a list of third party Propeller tools (A little like the thread Cluso99 created)? That way we can simply insert links to the tools as they evolve.
Another option would be a tool announcement thread where we can post update announcements as they come available. I'm not sure about the utility of this particular thread to a new user, but I use it regularly as a development history and archive. The top post is important though as that contains the changelog and links. I wonder if we just replicate that post into a sticky.
It is becoming a bit of a pain to maintain the three separate threads for the three tool sets, but I've been loathe to create a consolidated thread as the development history is still spread among the other threads.
On a brighter note, I did get off my backside and actually create a dedicated web page for the bst tools, so they have something a little nicer than just a dump directory.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Cardinal Fang! Fetch the comfy chair.
It is posible to have in it RAW ASM compile with only BIN file that have
1. 16 positions in start of it wil come from VAR section (External Variables + 1 place Driver type - User defined in first Variable.)
If I not have that many Variables BIN/DAT wil stil have same start position in it
2. Rest of Bin file is DAT section (Totaly always 2KBytes) To posiblity to place them in upper half of 512 EEProm for load on fly
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔ Nothing is impossible, there are only different degrees of difficulty. For every stupid question there is at least one intelligent answer. Don't guess - ask instead. If you don't ask you won't know. If your gonna construct something, make it·as simple as·possible yet as versatile as posible.
It is posible to have in it RAW ASM compile with only BIN file that have
1. 16 positions in start of it wil come from VAR section (External Variables + 1 place Driver type - User defined in first Variable.)
If I not have that many Variables BIN/DAT wil stil have same start position in it
2. Rest of Bin file is DAT section (Totaly always 2KBytes) To posiblity to place them in upper half of 512 EEProm for load on fly
I'm not quite sure I grasp precisely what you are after, but bstc has an option (-c) that creates only a .dat file from the DAT section in the first object. You could achieve what you want by
DAT
Vars long[noparse][[/noparse]16]
code org
...blah
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Cardinal Fang! Fetch the comfy chair.
My one question .. Must I always reserve 16 Long For at have same position in .DAT file of "Code Org"
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔ Nothing is impossible, there are only different degrees of difficulty. For every stupid question there is at least one intelligent answer. Don't guess - ask instead. If you don't ask you won't know. If your gonna construct something, make it·as simple as·possible yet as versatile as posible.
My one question .. Must I always reserve 16 Long For at have same position in .DAT file of "Code Org"
No, no.. not at all. I put that there as an example as you mentioned you had 16 variables to place at the start of the block.
The (-c) option just takes the entire DAT section and exports it as a binary file.
(it was designed for exporting binary blocks for inclusion into C files to provide PASM drivers)
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Cardinal Fang! Fetch the comfy chair.
It is litle more that I wil to know.
It give me that posiblites I wil have but it is not from C I wil use them but Spin
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔ Nothing is impossible, there are only different degrees of difficulty. For every stupid question there is at least one intelligent answer. Don't guess - ask instead. If you don't ask you won't know. If your gonna construct something, make it·as simple as·possible yet as versatile as posible.
I'm testing BST v0.18 pre 3 on Mac OS X (.5.6, Intel) and I found some isses I was not having with 0.17:
- Firstly it takes way longer to start, the icon just bounces on the Dock till I tap over it. The first time, following times It just starts normally without
even bouncing.
- If you double-tap on the very first icon on tree panel you either get an Access violation error or it terminates bst without error indication:
I can't reproduce this on a PPC running 10.4, but I can certainly reproduce it on 10.5 on an Intel machine.
I've got to update the version of X-Code on my Intel box as Instruments keeps locking up, but as soon as I can get it working I'll figure out what is going on.
On 10.4 400Mhz PPC bst takes about 2 seconds to open. On my dual core 1.8Ghz OSX 10.5 box it's taking about 15-20 seconds. Something is very wrong with the 10.5 specific code it seems.
Thanks for the report, I'll see what I can do. Shame X-code is a 1GB download and you need all of it just to get Instruments.. grumble..
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Cardinal Fang! Fetch the comfy chair.
Brad, is there any way to trick BST to quasi-support LMM? I have a couple hundred lines of code that are running much faster than needed, and I need more room in my cog RAM to make a single Cog IMU/Kalman filter complete with ADC code.
The code I want to move out of the cog RAM looks like :
It's all just movs and calls, there's no need to jump anywhere outside of the COG. The cog RAM would still have all the floating point routines and variables. I though I could just hand assemble the above routines to ensure that all the source and destination address would be correct, but that's guaranteed to give me errors. Can you think of anyway to ensure the symbol address are correct?
thanks,
Jay
EDIT.
Forgot to say, I'd implement the LMM functionality. I'm wondering how to keep the addresses correct.
Post Edited (Jay Kickliter) : 3/27/2009 11:42:19 AM GMT
Comments
The close button on Tab is something I've been looking at, but to make it consistent I need to make owner drawn tabs for OSX (like Safari) and I'm not quite up to that chapter in "OSX GUI programming for dummies" yet [noparse];)[/noparse]
It's something that is pretty high on my list, but I've just not got there yet.
This latest version _should_ have *much* faster and more reliable downloads on Windows, especially if you turn on the double baud rate option in the compiler options
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Cardinal Fang! Fetch the comfy chair.
First of all, thanks for all the hard work on the compiler...
I recently upgraded to 0.17 and I started working on a PRG loader for the C=64.
The code is far from finished and have a lot of errors.
However when I try to compile the program, the progress bar comes up and then it hangs.
I logged out to close down 0.17, downloaded 0.16 and tried again, this time the 0.16 gives me an "Access Violation" when I try to compile...
Just wonder if you could have a look at it when you have a minute...
I'm running Ubuntu 8.04 and using the Linux version of BST...
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
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
Change.
PUB start()
to
PUB start
And it will not crash during compilation...
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
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
I have two other fixes for bugs sevs picked up and I'll have a pre-release out with it all fixed today.
I've decided my QA process is taking too long between releases, so I'm going to start dropping -preX builds as bugs get fixed for those that get bitten by them.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Cardinal Fang! Fetch the comfy chair.
In future, all pre-release builds for any of the bst series of tools will be dropped in this directory.
I intend the pre-release builds to be lightly tested snapshots of my development process, they have not been exposed to any of my QA testing aside from a quick compiler regression test (on x86 linux only) and some brief functionality testing. This allows me to get builds done from my laptop when I'm away from my QA environment and try and get a more rapid response to critical crash bugs out faster.
Unless you are a Windows user with mis-behaving recovery files, or getting caught with the compiler bug Bamse identified, there is zero functional reason to upgrade to 0.18-pre1.
Current Changes :
I made a blue with the Windows build and the way it removed redundant auto-recovery files that sevs identified. I'm not sure it will affect many Windows users, but it had an oddity with the way a Windows users "Home" directory was located.
I've tried to enable the opening of project files from a drag and drop event or icon / association click from the file manager.
I've fixed the compiler bug Bamse found above.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Cardinal Fang! Fetch the comfy chair.
www.fnarfbargle.com/bst.html
I'm not much of a web developer (or in fact any developer) so suggestions are most welcome.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Cardinal Fang! Fetch the comfy chair.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Links to other interesting threads:
· Home of the MultiBladeProps:· SixBladeProp, TriBladeProp
· Prop Tools under Development or Completed (Index)
· Emulators (Micros eg Altair, and Terminals eg VT100) - index
· Search the Propeller forums (via Google)
My cruising website is: ·www.bluemagic.biz·· MultiBladeProp is: www.bluemagic.biz/cluso.htm
I have just started using Linux Mint because of BST (v0.17) and I loveit [noparse]:)[/noparse]
I have a feature request which may or may not of already been mentioned...I havent read through all 21 pages :P
Is it possible to add the shift+tab feature to shift a selected block of code back 1 tab? Like in the proptool.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
-Alec
Velden in N scale
It's already there.. it's Ctrl-Shift-I to indent and Ctrl-Shift-U to un-indent.
Being cross platform means having to compromise a little on ket-shortcuts unfortunately.
I _really_ need to sit down and document this stuff.... can anyone insert some more hours into my days?
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Cardinal Fang! Fetch the comfy chair.
I've noticed also that the compiler picks up on a few issues with my programming which the proptool didnt [noparse]:)[/noparse]
Like trying to perform 'if p == 0.0', gives me a compile error. Forces me to use the floating math compare [noparse]:)[/noparse]
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
-Alec
Velden in N scale
I've noticed also that the compiler picks up on a few issues with my programming which the proptool didnt [noparse]:)[/noparse]
Like trying to perform 'if p == 0.0', gives me a compile error. Forces me to use the floating math compare [noparse]:)[/noparse]
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
-Alec
Velden in N scale
Oh? The PropTool allows that? I guess I should too then, I just figured it was a _very_ easy programming mistake to make that would likely lead to confusion.
I guess comparing a static float value to a variable is legal...
Thanks for the pointer, I'm going to have to see how far I can bend the Parallax compiler and try to comply..
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Cardinal Fang! Fetch the comfy chair.
I'm not sure. I'd say with 99% certainty it's not something you are doing wrong and a bug in my code.
Which version of OSX, which architecture (Intel or PowerPC) and which version of BST?
I made some very intrusive and significant changes for the 0.17 release that is specifically linked to the TAB key, so it's quite likely I have a bug there.
Can you also give me a step by step as to how I can reproduce it..
ie.. load this file I have attached here, place the cursor on line 15, column 12 and press Tab.
Also, have a look in the IDE options and let me know which tab configuration you have selected (Standard, Smart or Parallax compatible). Have you changed any of the Tab stops in the configuration dialog?
<edit> Do you have the colour syntax highlighter turned on? I just found a potential crasher if it's disabled (Parallax style tabs *require* the syntax highlighter be enabled).
.. Just on that, does _anyone_ not have the highlighter enabled? So much stuff relies on it I'm considering removing the option to disable it.
Nevermind, it's a *huge* hole in my TAB code and the way it interacts with the highlighter. I'm sitting here in wonder that it *ever* worked. I'll have a fix out shortly.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Cardinal Fang! Fetch the comfy chair.
Post Edited (BradC) : 3/9/2009 7:58:35 AM GMT
www.fnarfbargle.com/bst/snapshots
This crash should only manifest itself when you are at the top of a page and are above any block definitions. I'd never seen it as all my code these days starts with CON right at the top.
It's not a bad upgrade though as it is a nasty crash and can potentially lose you work even if you do have periodic auto-recovery save turned on (which I highly recommend)
Anyway, as I asked above, is anyone _not_ using the highlighter? I've got the speed up now to a point where the highlighter makes negligible impact. The speed issues on GTK2 are related to the font rendering and not the colours.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Cardinal Fang! Fetch the comfy chair.
Thanks, that fixed it. The only reason I wasn't using the highlighter is that I hadn't got around to turning it on.
Oh my, I had forgotten that still defaulted to disabled. Thanks for the poke!
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Cardinal Fang! Fetch the comfy chair.
highlighter enabled by default.
Compiler relaxed so that using a raw float in a spin expression is not an error (the Parallax compiler allows it) however it *is* still a warning
to try and prevent this : http://forums.parallax.com/showthread.php?p=790611
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Cardinal Fang! Fetch the comfy chair.
We should really promote this development thread or http://forums.parallax.com/forums/default.aspx?f=25&m=297566 where the tools are available for download to become a sticky.
Does anybody have a preference one way or another?
Ken Gracey
It is very nice propose from You.
And it is very fine Tool to.
But only if it stil is posible to ad more posts to this.
Christoffer
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Nothing is impossible, there are only different degrees of difficulty.
For every stupid question there is at least one intelligent answer.
Don't guess - ask instead.
If you don't ask you won't know.
If your gonna construct something, make it·as simple as·possible yet as versatile as posible.
Sapieha
Sticky threads don't need to be locked; you could post the same way, forever, even if it were made sticky.
Sincerely,
Ken
G'day Ken,
Maybe what we need is a simple sticky with a list of third party Propeller tools (A little like the thread Cluso99 created)? That way we can simply insert links to the tools as they evolve.
Another option would be a tool announcement thread where we can post update announcements as they come available. I'm not sure about the utility of this particular thread to a new user, but I use it regularly as a development history and archive. The top post is important though as that contains the changelog and links. I wonder if we just replicate that post into a sticky.
It is becoming a bit of a pain to maintain the three separate threads for the three tool sets, but I've been loathe to create a consolidated thread as the development history is still spread among the other threads.
On a brighter note, I did get off my backside and actually create a dedicated web page for the bst tools, so they have something a little nicer than just a dump directory.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Cardinal Fang! Fetch the comfy chair.
I have one question on Yours Spin/PASM compiler.
It is posible to have in it RAW ASM compile with only BIN file that have
1. 16 positions in start of it wil come from VAR section (External Variables + 1 place Driver type - User defined in first Variable.)
If I not have that many Variables BIN/DAT wil stil have same start position in it
2. Rest of Bin file is DAT section (Totaly always 2KBytes) To posiblity to place them in upper half of 512 EEProm for load on fly
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Nothing is impossible, there are only different degrees of difficulty.
For every stupid question there is at least one intelligent answer.
Don't guess - ask instead.
If you don't ask you won't know.
If your gonna construct something, make it·as simple as·possible yet as versatile as posible.
Sapieha
I'm not quite sure I grasp precisely what you are after, but bstc has an option (-c) that creates only a .dat file from the DAT section in the first object. You could achieve what you want by
DAT
Vars long[noparse][[/noparse]16]
code org
...blah
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Cardinal Fang! Fetch the comfy chair.
That info I question on.
My one question .. Must I always reserve 16 Long For at have same position in .DAT file of "Code Org"
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Nothing is impossible, there are only different degrees of difficulty.
For every stupid question there is at least one intelligent answer.
Don't guess - ask instead.
If you don't ask you won't know.
If your gonna construct something, make it·as simple as·possible yet as versatile as posible.
Sapieha
No, no.. not at all. I put that there as an example as you mentioned you had 16 variables to place at the start of the block.
The (-c) option just takes the entire DAT section and exports it as a binary file.
(it was designed for exporting binary blocks for inclusion into C files to provide PASM drivers)
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Cardinal Fang! Fetch the comfy chair.
Thanks.
It is litle more that I wil to know.
It give me that posiblites I wil have but it is not from C I wil use them but Spin
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Nothing is impossible, there are only different degrees of difficulty.
For every stupid question there is at least one intelligent answer.
Don't guess - ask instead.
If you don't ask you won't know.
If your gonna construct something, make it·as simple as·possible yet as versatile as posible.
Sapieha
I'm testing BST v0.18 pre 3 on Mac OS X (.5.6, Intel) and I found some isses I was not having with 0.17:
- Firstly it takes way longer to start, the icon just bounces on the Dock till I tap over it. The first time, following times It just starts normally without
even bouncing.
- If you double-tap on the very first icon on tree panel you either get an Access violation error or it terminates bst without error indication:
I'll probably go back to 0.17.
Oh, that's UGLY! Yes, I'd go back to 0.17 too.
I can't reproduce this on a PPC running 10.4, but I can certainly reproduce it on 10.5 on an Intel machine.
I've got to update the version of X-Code on my Intel box as Instruments keeps locking up, but as soon as I can get it working I'll figure out what is going on.
On 10.4 400Mhz PPC bst takes about 2 seconds to open. On my dual core 1.8Ghz OSX 10.5 box it's taking about 15-20 seconds. Something is very wrong with the 10.5 specific code it seems.
Thanks for the report, I'll see what I can do. Shame X-code is a 1GB download and you need all of it just to get Instruments.. grumble..
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Cardinal Fang! Fetch the comfy chair.
The code I want to move out of the cog RAM looks like :
mov fnumA, q_m mov fnumB, q_bias call #_fsub mov q, fnumA 'Pdot_Roll[noparse][[/noparse]0] := fMath.FSub(fMath.FSub( Q_angle, P_Roll ), P_Roll) {39 uS} mov fnumA, q_angle mov fnumB, p1 call #_fsub mov fnumB, p2 call #_fsub mov pd0, fnumAIt's all just movs and calls, there's no need to jump anywhere outside of the COG. The cog RAM would still have all the floating point routines and variables. I though I could just hand assemble the above routines to ensure that all the source and destination address would be correct, but that's guaranteed to give me errors. Can you think of anyway to ensure the symbol address are correct?
thanks,
Jay
EDIT.
Forgot to say, I'd implement the LMM functionality. I'm wondering how to keep the addresses correct.
Post Edited (Jay Kickliter) : 3/27/2009 11:42:19 AM GMT