> There are many 16/32bit MCUs which will benefit from OpenOCD if
> they are supported. Most popular non-ARM ones I can think of are Renesas
> M16C/32C, H8/H8S/H8SX, Infineon XC166/XE166, TI MSP430.
I have developped JTAG support for MSP430 in versaloon, as I know, JTAG 
chain of MSP430 isn't standard JTAG. So I don't think it possible to support 
MSP430 in OpenOCD.

2009-05-25 



Best Regards, Simon Qian

SimonQian(simonq...@simonqian.com) ---- www.SimonQian.com



发件人: Xiaofan Chen 
发送时间: 2009-05-25  11:28:33 
收件人: michelcatudal 
抄送: openocd-development 
主题: Re: [Openocd-development] support avr32 
 
2009/5/25 Michel Catudal <michelcatu...@gmail.com>:
> David Brownell a �crit :
>> ? AVR32-specific support. �Probably not just the AP7 devices,
>> ?�but also the UC3 flavors (since those seem to be getting
>> ?�the engineering work nowadays).
>>
> I would agree with that. From what I have read the AVR32 is likely to
> compete with NEC's V850 and Cortex devices in the next few years.
ColdFire V1 and V2/V3/V4 support will be nice as well.
> The devices with CAN are supposed to come out shortly. This will make
> this device very important for us Engineers.
> Support for OpenOCD will be very usefull.
>
There are many 16/32bit MCUs which will benefit from OpenOCD if
they are supported. Most popular non-ARM ones I can think of are Renesas
M16C/32C, H8/H8S/H8SX, Infineon XC166/XE166, TI MSP430.
Just look at this chart for top 10 MCU vendors.
http://www.eetasia.com/ART_8800570077_1034362_NT_9b19f76b.HTM
http://www.eetasia.com/STATIC/ARTICLE_IMAGES/200904/EEOL_2009APR17_CTRLD_NT_01.gif
I guess that this will take a long time.
-- 
Xiaofan http://mcuee.blogspot.com
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to