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] |
Excerpted from Bill Gatliff's comments:Not a problem, as I said elsewhere. In fact, I prefer using TFTP to lots of messing around with config tools, or running special software to interface to the unit in normal operation.Oh, and the BDI2000 doesn't care what my host workstation is, as long as it's running plain vanilla gdb. No modules, no proxy libraries, no futzing around at all.
Well, not completely true. Your workstation must be running a TFTP server so the BDI2000 can read its configuration file when it boots. The s/w distribution came with a server for NT. I was running on Linux and it took a little "futzing around" to get the Linux distribution server installed and running properly.
I was actually under the impression that the Jeeni would be just as expensive as the BDI2000, but perhaps I was thinking about the Majic?
Our target is an ARM7. I've got an EPI Jeeni, and have used a borrowed BDI2000 on a very limited basis. My impressions: The BDI is more of a pain to set up, but seems more flexible and configurable after you climb the curve. Both work great with gdb, and you can't complain about the ethernet download speeds. At ~$1500 for the Jeeni vs. ~$2400 for the BDI2000, the Jeeni seems like the better deal if you are targeting ARM.
------ 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] |