| Author |
 Topic  |
|
Gar Bage
Posting Profoundly
108 Posts |
 Posted - 09/25/2004 : 07:10:18 AM
|
You'll find an updated HOWTO here
It is editable by anyone. If you find something wrong, or you like to comment or extend any topic, don't be afraid of the wiki and just do so.
Edited:
* Removed huge topic contents
* Added link to Wiki Topic
-- Help put peace in the world. Buck Fush, Bill Kush. |
Edited by - Gar Bage on 10/17/2004 11:48:08 AM
|
Your quick response to this post: (4 total votes)
I agree (100%)
I disagree (0%)
|
|
|
SilentGuy
Posting is for Closers
31 Posts |
Posted - 09/25/2004 : 07:22:20 AM
|
| nice, thank's a lot... i just ordered a neuros and i thought "hey, let's look at the sourcecode to pass time till it arrives" but i was kinda unsure how exactly to use it... |
Your quick response to this post: (0 total votes)
I agree (0%)
I disagree (0%) |
 |
|
|
k-mouse
Likes to Post
20 Posts |
Posted - 09/25/2004 : 7:07:21 PM
|
I have done everything you said, step by step. But when I got to the point where you're suppose to open the Project File in the CCS IDE, I kept getting this error message:
quote:
---------------------------
Code Composer Studio
---------------------------
No build tools were found.
Cannot open project "C:\ti\myprojects\neuros-firmware\ccs_projects\Main_APP\Neuros200\Neuros200.pjt":
try re-installing the application.
---------------------------
OK
---------------------------
I just installed the Code Composer application, so I see no reason to do that again.
What can I do about this problem? |
Your quick response to this post: (0 total votes)
I agree (0%)
I disagree (0%) |
|
|
|
k-mouse
Likes to Post
20 Posts |
Posted - 09/26/2004 : 3:15:28 PM
|
Does nobody know what this problem could be??
Could it have something to do with the firmware I downloaded, or is it some kind of problem with the CCS application?
Does anybody else have this problem?
Edit: After googling a while, I could only find one other (chinese(simplified)) guy with the same problem. But, as far as I understood the translation* of it, they did not found any solution (but I may be wrong).
* Links:
http://babelfish.altavista.com/
http://216.239.59.104/search?q=cache:bbs.dspdsp.com/bbs/showtopic.asp%3FTOPIC_ID%3D3091 |
Edited by - k-mouse on 09/26/2004 3:55:40 PM |
Your quick response to this post: (0 total votes)
I agree (0%)
I disagree (0%) |
|
|
|
qvack_82
Posting is for Closers
79 Posts |
Posted - 09/26/2004 : 8:21:28 PM
|
quote:
Originally posted by k-mouse
Does nobody know what this problem could be??
Could it have something to do with the firmware I downloaded, or is it some kind of problem with the CCS application?
It could be the firmware, check out the neuros-firmware/ccs_projects/buildtools
directory for the following files:
bootversion.exe
hexmerger.exe
word2byte.exe
Image.exe
emuflash.exe
readme.txt
If that's the buildtools it's complaining about, you'll need them. Other than that, all I can suggest is to try reinstalling CCStudio.
Cheers
Paul
pwarren.php-help.com |
Your quick response to this post: (0 total votes)
I agree (0%)
I disagree (0%) |
|
|
|
k-mouse
Likes to Post
20 Posts |
Posted - 09/26/2004 : 10:12:45 PM
|
Thanks for reply
All the files in the build-tools directory are where they should be...
I have tried to completely uninstall, and install CCS again, but with no luck at all.
Btw, the same problem occurs when I'm trying to make a "New Project". And it happens no matter what kind of chip is selected, so I guess the problem is located somewhere in CCS. |
Your quick response to this post: (0 total votes)
I agree (0%)
I disagree (0%) |
|
|
|
chad(at)gambit.net
Posting Profoundly
111 Posts |
Posted - 10/06/2004 : 11:59:48 AM
|
| I know this is probably asking a bit much, but can we get a changelog for the compiled .hex you have on Sourceforge? Or is it compiled as-is from the released source? |
Your quick response to this post: (0 total votes)
I agree (0%)
I disagree (0%) |
|
|
|
webkid
Posting Mania
1590 Posts |
Posted - 10/06/2004 : 12:30:03 PM
|
| The garbage branch has a changelog, and outside of that, yes, I believe that is the compiled hex of the open source version (ie, running that binary shouldn't contain any closed source material, AFAIK) |
Your quick response to this post: (0 total votes)
I agree (0%)
I disagree (0%) |
|
|
|
Gar Bage
Posting Profoundly
108 Posts |
Posted - 10/06/2004 : 4:10:43 PM
|
The ongoing woid.hex releases posted on the garbage branch on sourceforge are, each and everyone of them, built from the most recent code (available from CVS as well) that you will find on that branch at the very time they were built.
I try to build and upload a new version everytime i commit a change to that branch. And i do reflect the changes done to each and every release on the CHANGELOG file located on CVS, and on CVS commit logs as well. The changes can also be monitored in detail by CVS diffing.
If you want to test my changes out, i highly recommend to try and build your own firmware, from the sources. That's why i wrote this draft. That's why i post the sources. The binary releases are only posted for convenience. Maybe in a week or two i won't post binary releases no more, or maybe i will continue to do so. You shouldn't depend on my mood.
And please, keep these in mind:
- I DO NOT test all the binary builds, though. I myself use a different localized build (in Spanish), and, as the code base remain mostly the same, some problems with memory allocation (menus and such) can happen.
- I DO NOT guarantee the CVS builds will work at all. They are test releases, based on an experimental branch. The garbage builds are not release builds, and you shouldn't take them as such. If I make a change that could remotely damage the storage on your Neuros (such as filesystem changes, or the like) i'd try and warn about it on the CHANGELOG and on the commit logs, but it's you who should be aware of that.
- Digital Innovations/Neuros Audio LLC holds NO responsability on the firwmare built from the SourceForge project. They support us, and feed us with new releases and with some good advices and direction guidelines. That's all. You should not yell at them in the unlikely case that something went completely wrong with our Open Source firmware.
In a near future a release build will be 'officially' released by the project admin. Those release builds will be well packaged, well tested, and fully documented. If you're an average user who wants to stay in the safe side, you should wait for those.
Enjoy your Neuros as much as i do, dudes.
-- Help put peace in the world. Buck Fush, Bill Kush. |
Edited by - Gar Bage on 10/06/2004 4:14:25 PM |
Your quick response to this post: (1 total votes)
I agree (100%)
I disagree (0%) |
|
|
|
Sean Starkey
Posting Mania
848 Posts |
|
|
findbuddha
Likes to Post
11 Posts |
Posted - 10/06/2004 : 5:29:00 PM
|
Gar Bage, please keep releasing binaries! Or maybe someone else could post builds. Otherwise us linux users have no way of using the new firmwares (until the gcc target is done).
------------
Watching the weather change |
Your quick response to this post: (0 total votes)
I agree (0%)
I disagree (0%) |
|
|
|
noiz
Posting Mania
921 Posts |
Posted - 10/06/2004 : 5:32:05 PM
|
just wondering if there is a way to have alerts sent to your email when garbage releases a new version of his firmware (i dont really know sourceforge that well)?
-noiz |
Your quick response to this post: (0 total votes)
I agree (0%)
I disagree (0%) |
|
|
|
webkid
Posting Mania
1590 Posts |
Posted - 10/06/2004 : 6:03:36 PM
|
| Encosion set up a thread for that kind of thing a while back. It got a little hijacked recently, though. |
Your quick response to this post: (0 total votes)
I agree (0%)
I disagree (0%) |
|
|
|
RatFink
Just Posting
1 Posts |
Posted - 10/11/2004 : 08:26:42 AM
|
quote:
Originally posted by k-mouse
Thanks for reply
All the files in the build-tools directory are where they should be...
I have tried to completely uninstall, and install CCS again, but with no luck at all.
Btw, the same problem occurs when I'm trying to make a "New Project". And it happens no matter what kind of chip is selected, so I guess the problem is located somewhere in CCS.
Make absolutely sure you have the tools or the 5000 series DSPs and not for the 6000, OMAP or 2000 series. While not certain if that is the cuase, you will get that error if you load the project in CCS not for the 5000 series.
Good luck |
Edited by - RatFink on 10/11/2004 08:28:24 AM |
Your quick response to this post: (1 total votes)
I agree (100%)
I disagree (0%) |
|
|
|
Thadius
Just Posting
6 Posts |
Posted - 10/15/2004 : 11:40:54 PM
|
I'm new to this whole thing and am following the instructions to start looking at the source code.
It's going to take me a while just to get a basic understanding of how the whole process works.
Will I have to spend a ridiculous amount of money on software if I want to keep working on things after the 90 day trial period is up on my Free Trial software?
|
Your quick response to this post: (0 total votes)
I agree (0%)
I disagree (0%) |
|
|
|
webkid
Posting Mania
1590 Posts |
Posted - 10/16/2004 : 01:01:48 AM
|
| Yes. It will actually cost you a rediculous amount of money to keep the compiler working after the 90 trial. It's a huge dissapointment, but it's the reality of the business. As I am sure has been noted on this thread (I can't be bothered to read it all again) there's a gcc port in the works. Given the amount of progress I've seen on it lately (ie, none) I would say you'll be out $1,000 or out a compiler in three months. Sorry man. |
Your quick response to this post: (0 total votes)
I agree (0%)
I disagree (0%) |
|
|
|
SilentGuy
Posting is for Closers
31 Posts |
Posted - 10/18/2004 : 11:52:08 AM
|
I just loaded the CCS tools and the newest garbage sources from cvs and then tried build etc... building in CCS went fine, but i got some errors from the make.bat... about missing .hex files and stuff... but the make.bar did create a woid_flash.hex...
now i'm unsure if i should try using it... what would happen is something went wrong? would my neuros tell me this while trying to flash? and if not, what will the neuros to with a faulty firmware? |
Your quick response to this post: (0 total votes)
I agree (0%)
I disagree (0%) |
|
|
|
webkid
Posting Mania
1590 Posts |
Posted - 10/18/2004 : 12:21:08 PM
|
mgao claims that it is nearly impossible to "brick" your Neuros in an unrecoverable way. You should be able to unplug your Neuros, unattach the backpack, let it sit for a minute, plug the backpack back in, press down+play, and load another firmware.
That said, it only makes woid_flash.hex from copying from another directory. Investigate the problem before you go loading that one. |
Your quick response to this post: (0 total votes)
I agree (0%)
I disagree (0%) |
|
|
|
loup
Posting is for Closers
69 Posts |
Posted - 10/18/2004 : 11:38:22 PM
|
| I want to download the compiler but unfortunately the according to my download manager it's not resumable. |
Your quick response to this post: (0 total votes)
I agree (0%)
I disagree (0%) |
|
|
|
webkid
Posting Mania
1590 Posts |
Posted - 10/19/2004 : 12:28:32 AM
|
PayPal me $5 and I'll send it to you on CD. Better yet, if you want to go and get some coffee, you can have it for the price of one Mocha.
Know where Dinky Town is? |
Your quick response to this post: (0 total votes)
I agree (0%)
I disagree (0%) |
|
|
|
loup
Posting is for Closers
69 Posts |
Posted - 10/19/2004 : 12:37:02 AM
|
 I was actually gonna ask you if you lived in dinkytown when you said you lived in a college area part of town |
Your quick response to this post: (0 total votes)
I agree (0%)
I disagree (0%) |
|
|
|
Topic |
|
HOWTO Compile your own Neuros Firmware
Forum Locked
