![]() |
Computer Solutions Ltd | ||
Celebrating over 28 years |
|||
ABATRON
BDI300 JTAG Debugger
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
BDI 3000 - New products to receive literature fill in request
|
| 1.5MBytes/sec download speed, 32 MHz JTAG link and target voltage down to 1.2v
|
BDM and JTAG interfaces provide a lot of ICE functionality at a very low cost.

Silicon manufacturers offer more and more on-chip debugging features with new processors. This capability, implemented in various processors under such names as Background Debug Mode (BDM), JTAG and on-chip emulation, puts basic debugging functions on the chip itself. With BDM or JTAG debug port, you can control and monitor the microprocessor through these on-chip debugging services. This debugging mode runs even when the target system crashes and enables developers to continue investigating the cause of the crash. You won't waste time and target resources with a software ROM monitor, and you eliminate the cabling problems typical of ICEs.
The Abatron BDM/JTAG interfaces range from the low cost BDI1000 to the ultra fast BDI3000 which was launched in Jan 2008.
The BDI3000 features a 10/100 Ethernet link and a maximum JTAG link speed of 32MHz making it possible to load code for debugging at up to 1.5MBytes/sec. Target voltages of 1.2-5V are supported as are variable clock speeds.
To find out which Abatron device will best suite your requirements fill in request .
These devices can be used to solve a wide range of development needs-
Using the GCC compiler ? then they will run with the GNU Debugger
Using the Debugger that is supplied with your compiler ? they run with:-
CodeWarrior, IAR, X-Ray, Accelerated Technology, Tornado, SeeCode, ARM ADW/AXDJust want to program on chip or external Flash ?
Need to use the BDM/JTAG interface as part of your ATE process and to write your own C drivers
| Target CPU |
(KBytes/s) |
(KBytes/s) |
|
| HC812A4 |
|
N.A. | N.A. |
| PPC405GP |
|
|
|
| PPC440EP |
|
600 | |
| MC68360 |
|
|
N.A. |
| MPC855 |
|
950 | |
| MPC860 |
|
|
|
| ColdFire MCF5206e / MCF5307 |
|
|
1100 |
| M-CORE |
|
|
N.A. |
| MPC5554 |
|
|
600 |
| MPC8260 | N.A. |
|
|
| MPC8280 | N.A. | 170 | |
| MPC8349 | N.A. | 1300 | |
| MPC8548 | N.A. | 1300 | |
| ARM7TDMI |
|
|
900 |
| ARM11 |
|
|
1000 |
| XScale |
|
|
1600 |
| MIPS32 | N.A |
|
600 |
| Target Configuration | (KBytes/s) |
(KBytes/s) |
(KBytes/s) |
| HC912B32 / HC12 Internal Flash @ 8 MHz |
|
|
N.A. |
| HCS12 Internal Flash / HCS12DP256 @ 24 MHz |
|
|
N.A. |
| HC812A4 / AMD 29F010 x 16 bit |
|
|
N.A. |
| MPC860 @ 50 MHz / AMD 29F040 x 32 bit |
|
|
|
| MPC8260 @ 40 MHz / LH 28F016 x 32 bit |
|
|
|
| MPC68360 @ 25 MHz / AMD 29F016 x 32 bit |
|
|
N.A. |
| AT91R40008 @ 66 MHz / AT49BV1614 x 16 bit |
|
|
|
| MPC8349E MDS / I28F640J3 / 16-bit | N.A. | 124 | |
| EVKIT 405EP / AM29LV160DB / 16-bit | 180 | ||
| M5329EVB / I28F160C3 / 16-bit | N.A. | 110 | |
| PXA250 / I28F128J3 / 32-bit | 220 | ||
| ARM7TDMI / SST39VF400 / 16-bit | 130 | ||
| MPC8560ADS / I28F640J3 / 32-bit | N.A. | 190 | |
| MPC8260FADS / LH28F016 / 32-bit | N.A. | 110 | |
| DB1100(MIPS32) / AM29LV640MH/L / 32-bit | N.A. | 104 |
For more details of specific packages -
Using the GCC compiler ? then they will run with the GNU Debugger
Using the Debugger that is supplied with your compiler ? they run with:-
CodeWarrior, IAR, X-Ray, Tornado, SeeCode, ARM ADW/AXDJust want to program on chip or external Flash ?
Need to use the BDM/JTAG interface as part of your ATE process and to write your own C drivers
| Home | Shop | Products | Supported Chips | Information Zone | Contact | Site Map |
| Computer Solutions Ltd 1a New Haw Road, Addlestone, Surrey KT15 2BZ, England |
|
| Telephone: +44 (0) 1932 829460 | Fax: +44 (0) 1932 840603 |
| Email: sales@computer-solutions.co.uk | Web: www.computer-solutions.co.uk |
| Copyright © 2008 Computer Solutions Ltd | |