Sorry, I didn't reply earlier. On Tue, Mar 30, 2010 at 1:40 AM, Mike Frysinger <[email protected]> wrote: > On Monday 29 March 2010 06:32:46 Benjamin Henrion wrote: >> Just to say that a friend of mine had an ICEBear cable, so I >> discovered it was a yet-another-FTDI2232-based: >> >> http://hackerspace.be/Icebear_jtag >> >> I spent some time searching for documentation on the ICEBear+urjtag, >> but I did not found that much. > > it is wired up slightly differently from the gnICE, and the creator of the > ICEBear has no interest in supporting open source tools -- he has his own > closed source forks of things (perfectly legal as they're BSD and such) that > are "faster" and only work with the ICEBear, so he wants people to pay the > extra $$$ for it. > I think "faster" might not even be true now compared ICEBear + proprietary software to gnICE + urjtag + gdbproxy. Even there is gnICE+ now, which is based on ft2232h, i.e. supports high speed USB.
> it should be trivial to use the gnICE examples and maybe switch one or two > bits, but since the device is geared towards Blackfin parts, might as well > just buy the much cheaper gnICE/gnICE+ ... > > during early gnICE testing, we did resolder one of the pins on a few ICEBears > so that it worked the same as the gnICE and thus "just worked" with the rest > of the software stack, but once the gnICE was stable, we havent bothered with > the ICEBear since. You can use a multimeter to detect the pin connection. It should be easy. Jie ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ UrJTAG-development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/urjtag-development
