Rajesh,

Logic recommends using the RealView Multi-ICE.

http://www.arm.com/products/DevTools/MultiICE.html

Pricing can be found here.

http://www.arm.com/products/DevTools/pricing-devtools.html

Regards,

Hi aaron,

thanks for the response.

i did a bit of analysis on this and found signum's JTAGjet pretty good (especially the chameleon debugger package).
do u recommend this option.

also, sorry but i've posted another query regarding booting from internal BootROM and downloading 4k of code thru UART2.

we were looking at this feature for development needs, but as of now it doesn't seem to work...any ideas!!

regards,
rajesh

This thread is really old, but I wanted to add something to it anyway.

Logic started ARM-based development using the Mulit-ICE debugger along with some of the MacCraigor tools (Raven and Wiggler I believe).

After Marc Singer convinced me to try the BDI-2000 emulator from Abatron, I can quite confidently say that we will never go back to using anything else. The Abatron is a great emulator and worth every penny. It's network interfacing is excellent, it has a great little scripting language to help you debug your board setup, it works out of the box as a GDB target, etc. etc.

Also, if you do development on multiple CPU architectures like we do, you can get different sets of firmware for the BDI-2000 to support each of your individual targets. Currently, we are using the same Abatron BDI 2000 to work with; ARM, XScale, and ColdFire based hardware.

Regards,
--mikee

Hi,

I'm also useing the BDI 2000 but with this board (Sharp Zoom SDK) there are sporadic problems with the JTAG access/connection. Sometimes the Bypass check is ok but mostly it fails. Even if the JTAG connection has been established it crashes after a few minutes sometimes.

Any hints?
THX.

You shouldn't be having any trouble with the JTAG connection. Are the jumpers set correctly? Refer to the kit's user guide to ensure that the jumpers on the base-board are set in the proper position for JTAG operation.

Also, ensure that the Card Engine is firmly seated on the SDK.

--mikee

Thank you! Your were right! The Card Engine wasn't firmly seated!