This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
I went down the same path as you, we purchased a wiggler, it works but it's a toy, and when we had problem getting their OCDLibRemote working support was non-existant. I suppose it says so on the website, but you would expect to get a liitle help at least. We decided it definetly wasn't going to work for us, so we got the BDI. I haven't looked back since. It's saved us thousands in development time, at one stage we needed a feature to load the mmu tables into our ARM core before initalising it. the BDI guys sent us a patch within a few days. We also regularly get new firmware with added features. As for the TFTPD thing, I see it as a feature not a bug. The bdi just picks up the bdi config from our main server, when we work on another project, just telnet into the bdi change the filename and off you go. The telnet has also enabled saved us hours bringing up new boards, I love it. We also use the telnet memory test a lot, it let's us do bus integrity/timing checking in a snap. my 2 cents Nic > Well, the project I'm working on is definitely more than a "hobby" king > of thing. Still, the BDI2000 is quite expensive. I think the real > question is: What does it have that the "Raven" doesn't, that would > justify more than doubling the cost for this equipment? > > - Toralf ------------------------------------------------- ------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |